Bug#707560: libucommon6-dbg and libucommon5-dbg: error when trying to install together

2013-06-03 Thread Jonas Smedegaard
Quoting Mark Purcell (2013-06-02 11:01:06)
 Could I suggest that do not version the -dbg package.
 
 Whilst there is a use to have the library package versioned, there is 
 little to be gained by versioning the -dbg package, and it does lead 
 to ongoing conflicts like this one.

Thanks - that sounds sensible!


 - Jonas

-- 
 * Jonas Smedegaard - idealist  Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


signature.asc
Description: signature


Bug#707560: libucommon6-dbg and libucommon5-dbg: error when trying to install together

2013-06-03 Thread Julien Cristau
On Sun, Jun  2, 2013 at 19:01:06 +1000, Mark Purcell wrote:

 On Thu, 9 May 2013 14:23:36 Ralf Treinen wrote:
  Version: libucommon5-dbg/5.2.2-4
  Version: libucommon6-dbg/6.0.4-1
 
 Jonas,
 
 Could I suggest that do not version the -dbg package.
 
 Whilst there is a use to have the library package versioned, 
 there is little to be gained by versioning the -dbg package, 
 and it does lead to ongoing conflicts like this one.
 
It only leads to conflicts if you put debug symbols for non-versioned
files in it (just like with shared library packages).  And if you don't
use build-id.

Cheers,
Julien


signature.asc
Description: Digital signature


Bug#707560: libucommon6-dbg and libucommon5-dbg: error when trying to install together

2013-06-03 Thread Mark Purcell
On Mon, 3 Jun 2013 20:31:58 Julien Cristau wrote:
  Whilst there is a use to have the library package versioned, 
  there is little to be gained by versioning the -dbg package, 
  and it does lead to ongoing conflicts like this one.
 
 It only leads to conflicts if you put debug symbols for non-versioned
 files in it (just like with shared library packages).  And if you don't
 use build-id.

Julien,

It is my experience that an non versioned -dbg package that has a 
Depends: libX (= ${binary:Version}) will not cause such conflicts.

How do you use build-id?

Mark


signature.asc
Description: This is a digitally signed message part.


Bug#707560: libucommon6-dbg and libucommon5-dbg: error when trying to install together

2013-06-03 Thread Julien Cristau
On Tue, Jun  4, 2013 at 06:24:32 +1000, Mark Purcell wrote:

 How do you use build-id?
 
Easiest is probably 'echo 9  debian/compat' and dh_strip will do that.

Cheers,
Julien


signature.asc
Description: Digital signature


Bug#707560: libucommon6-dbg and libucommon5-dbg: error when trying to install together

2013-06-02 Thread Mark Purcell
On Thu, 9 May 2013 14:23:36 Ralf Treinen wrote:
 Version: libucommon5-dbg/5.2.2-4
 Version: libucommon6-dbg/6.0.4-1

Jonas,

Could I suggest that do not version the -dbg package.

Whilst there is a use to have the library package versioned, 
there is little to be gained by versioning the -dbg package, 
and it does lead to ongoing conflicts like this one.

Mark


signature.asc
Description: This is a digitally signed message part.


Bug#707560: libucommon6-dbg and libucommon5-dbg: error when trying to install together

2013-05-09 Thread Ralf Treinen
Package: libucommon5-dbg,libucommon6-dbg
Version: libucommon5-dbg/5.2.2-4
Version: libucommon6-dbg/6.0.4-1
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite

Date: 2013-05-09
Architecture: amd64
Distribution: sid

Hi,

automatic installation tests of packages that share a file and at the
same time do not conflict by their package dependency relationships has
detected the following problem:


WARNING: The following packages cannot be authenticated!
  libucommon5 libucommon6 libucommon5-dbg libucommon6-dbg
Authentication warning overridden.
Can not write log, openpty() failed (/dev/pts not mounted?)
Selecting previously unselected package libucommon5.
(Reading database ... 10797 files and directories currently installed.)
Unpacking libucommon5 (from .../libucommon5_5.2.2-4_amd64.deb) ...
Selecting previously unselected package libucommon6.
Unpacking libucommon6 (from .../libucommon6_6.0.4-1_amd64.deb) ...
Selecting previously unselected package libucommon5-dbg.
Unpacking libucommon5-dbg (from .../libucommon5-dbg_5.2.2-4_amd64.deb) ...
Selecting previously unselected package libucommon6-dbg.
Unpacking libucommon6-dbg (from .../libucommon6-dbg_6.0.4-1_amd64.deb) ...
dpkg: error processing 
/var/cache/apt/archives/libucommon6-dbg_6.0.4-1_amd64.deb (--unpack):
 trying to overwrite '/usr/lib/debug/usr/bin/car', which is also in package 
libucommon5-dbg 5.2.2-4
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Errors were encountered while processing:
 /var/cache/apt/archives/libucommon6-dbg_6.0.4-1_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)


This is a serious bug as it makes installation fail, and violates
sections 7.6.1 and 10.1 of the policy. An optimal solution would
consist in only one of the packages installing that file, and renaming
or removing the file in the other package. Depending on the
circumstances you might also consider Replace relations or file
diversions. If the conflicting situation cannot be resolved then, as a
last resort, the two packages have to declare a mutual
Conflict. Please take into account that Replaces, Conflicts and
diversions should only be used when packages provide different
implementations for the same functionality.

Here is a list of files that are known to be shared by both packages
(according to the Contents file for sid/amd64, which may be
slightly out of sync):

  /usr/lib/debug/usr/bin/args
  /usr/lib/debug/usr/bin/car
  /usr/lib/debug/usr/bin/mdsum
  /usr/lib/debug/usr/bin/pdetach
  /usr/lib/debug/usr/bin/scrub-files
  /usr/lib/debug/usr/bin/sockaddr
  /usr/lib/debug/usr/bin/zerofill

This bug has been filed against both packages. If you, the maintainers of
the two packages in question, have agreed on which of the packages will
resolve the problem please reassign the bug to that package. You may then
also register in the BTS that the other package is affected by the bug.

-Ralf.

PS: for more information about the detection of file overwrite errors
of this kind see http://edos.debian.net/file-overwrites/.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org