[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#406485: marked as done (file conflicts between dcc-milter and synce-dccm )

Your message dated Fri, 14 Mar 2008 17:32:05 +0000
with message-id <E1JaDlF-00064u-N3@ries.debian.org>
and subject line Bug#406485: fixed in synce-dccm 0.9.1-4
has caused the Debian Bug report #406485,
regarding file conflicts between dcc-milter and synce-dccm 
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
406485: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=406485
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: dcc-milter, synce-dccm 
Severity: serious
Justification: file conflict between packages

hi,

both dcc-milter and synce-dccm ship `/usr/bin/dccm' but do not conflict
or add i diversion, thus can't be installed on the same environment:

 dpkg: error processing /var/cache/apt/archives/dcc-milter_1.3.42-4_amd64.deb (--unpack):
 trying to overwrite `/usr/bin/dccm', which is also in package synce-dccm
 dpkg-deb: subprocess paste killed by signal (Broken pipe)
 Errors were encountered while processing:
  /var/cache/apt/archives/dcc-milter_1.3.42-4_amd64.deb
 E: Sub-process /usr/bin/dpkg returned an error code (1)

bye,
    - michael

--- End Message ---
--- Begin Message --- 
Source: synce-dccm
Source-Version: 0.9.1-4

We believe that the bug you reported is fixed in the latest version of
synce-dccm, which is due to be installed in the Debian FTP archive:

synce-dccm_0.9.1-4.diff.gz
  to pool/main/s/synce-dccm/synce-dccm_0.9.1-4.diff.gz
synce-dccm_0.9.1-4.dsc
  to pool/main/s/synce-dccm/synce-dccm_0.9.1-4.dsc
synce-dccm_0.9.1-4_i386.deb
  to pool/main/s/synce-dccm/synce-dccm_0.9.1-4_i386.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 406485@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Barry deFreese <bddebian@comcast.net> (supplier of updated synce-dccm package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Sun, 09 Mar 2008 00:42:35 -0500
Source: synce-dccm
Binary: synce-dccm
Architecture: source i386
Version: 0.9.1-4
Distribution: unstable
Urgency: low
Maintainer: Debian QA Group <packages@qa.debian.org>
Changed-By: Barry deFreese <bddebian@comcast.net>
Description: 
 synce-dccm - Daemon to keep a connection to your WinCE device up
Closes: 406485
Changes: 
 synce-dccm (0.9.1-4) unstable; urgency=low
 .
   * QA upload.
     + Set maintainer to Debian QA Group <packages@qa.debian.org>.
   * Move /usr/bin/dccm to /usr/bin/synce-dccm. (Closes: #406485).
     + Suggested by synce upstream as done in other synce packages.
   * Bump debhelper build-dep to 5.
   * Move DH_COMPAT from rules to compat and set to 5.
   * Make clean not ignore errors.
   * Remove unused debhelper commands from rules.
   * Remove unneeded .dirs file.
   * Bump Standards Version to 3.7.3. (No changes needed).
Files: 
 1be1dc1bc3e2338046e131de3fd811fd 627 otherosfs optional synce-dccm_0.9.1-4.dsc
 6cfa1c00f60f24cba4adb45db98b1680 19500 otherosfs optional synce-dccm_0.9.1-4.diff.gz
 52cd7e1c344c6df94e9944275bb1b136 14244 otherosfs optional synce-dccm_0.9.1-4_i386.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFH2rSqriZpaaIa1PkRAmlrAKCIRzTXODAw/WwM9A0bmMjkvQYSswCdGyQ7
ZBkD1oGsM2zl44roha2qMJU=
=2qFy
-----END PGP SIGNATURE-----

--- End Message ---
Reply to: