Bug#796863: libassa3.5-5v5 and libassa-3.5-5v5: error when trying to install together

[Niels Thykier]

On Wed, 26 Aug 2015 07:11:14 +1000 Riley Baird
 wrote:
> On Tue, 25 Aug 2015 11:54:00 -0400
> Eric Dorland  wrote:
> 
> > * Riley Baird (bm-2cvqnduybau5do2dfjtrn7zbaj246s4...@bitmessage.ch) wrote:
> > > This is listed in the FTP master's cruft report, so if I'm correct, it
> > > shouldn't be necessary to request a removal from unstable.
> > 
> > Yeah and you have the right conflicts/replaces. I'm surprised it's
> > complaining about this.
> 
> No, at the moment, it is possible to simultaneously install these
> conflicting packages because someone made a NMU just before or after you
> uploaded my package, but they didn't add the hyphen between "libassa"
> and "3", so now we have libassa3.5-5v5 and libassa-3.5-5v5.

Hi,

What is the status on adding these Conflicts/Replaces?  This bug will
soon be the only thing blocking libassa's transition to testing.

Thanks,
~Niels




signature.asc
Description: OpenPGP digital signature

Bug#796863: libassa3.5-5v5 and libassa-3.5-5v5: error when trying to install together

[Riley Baird]

On Sun, 06 Sep 2015 13:37:44 +0200
Niels Thykier  wrote:

> On Wed, 26 Aug 2015 07:11:14 +1000 Riley Baird
>  wrote:
> > On Tue, 25 Aug 2015 11:54:00 -0400
> > Eric Dorland  wrote:
> > 
> > > * Riley Baird (bm-2cvqnduybau5do2dfjtrn7zbaj246s4...@bitmessage.ch) wrote:
> > > > This is listed in the FTP master's cruft report, so if I'm correct, it
> > > > shouldn't be necessary to request a removal from unstable.
> > > 
> > > Yeah and you have the right conflicts/replaces. I'm surprised it's
> > > complaining about this.
> > 
> > No, at the moment, it is possible to simultaneously install these
> > conflicting packages because someone made a NMU just before or after you
> > uploaded my package, but they didn't add the hyphen between "libassa"
> > and "3", so now we have libassa3.5-5v5 and libassa-3.5-5v5.
> What is the status on adding these Conflicts/Replaces?  This bug will
> soon be the only thing blocking libassa's transition to testing.

We don't need to add any more Conflicts/Replaces.

libassa3.5-5v5 and libassa-3.5-5v5 both only exist in unstable at the
moment. They come from different versions of the same source package.
Only libassa-3.5-5v5 will make it into testing. For a person running
testing, it will be impossible to have the problem which Ralf described.


pgp4ZCap8c5OZ.pgp
Description: PGP signature

Bug#796863: libassa3.5-5v5 and libassa-3.5-5v5: error when trying to install together

[Eric Dorland]

* Riley Baird (bm-2cvqnduybau5do2dfjtrn7zbaj246s4...@bitmessage.ch) wrote:
 This is listed in the FTP master's cruft report, so if I'm correct, it
 shouldn't be necessary to request a removal from unstable.

Yeah and you have the right conflicts/replaces. I'm surprised it's
complaining about this.

-- 
Eric Dorland e...@kuroneko.ca
43CF 1228 F726 FD5B 474C  E962 C256 FBD5 0022 1E93


signature.asc
Description: Digital signature

Bug#796863: libassa3.5-5v5 and libassa-3.5-5v5: error when trying to install together

[Riley Baird]

This is listed in the FTP master's cruft report, so if I'm correct, it
shouldn't be necessary to request a removal from unstable.


pgpYFjU8d9MhT.pgp
Description: PGP signature

Bug#796863: libassa3.5-5v5 and libassa-3.5-5v5: error when trying to install together

[Riley Baird]

On Tue, 25 Aug 2015 11:54:00 -0400
Eric Dorland e...@debian.org wrote:

 * Riley Baird (bm-2cvqnduybau5do2dfjtrn7zbaj246s4...@bitmessage.ch) wrote:
  This is listed in the FTP master's cruft report, so if I'm correct, it
  shouldn't be necessary to request a removal from unstable.
 
 Yeah and you have the right conflicts/replaces. I'm surprised it's
 complaining about this.

No, at the moment, it is possible to simultaneously install these
conflicting packages because someone made a NMU just before or after you
uploaded my package, but they didn't add the hyphen between libassa
and 3, so now we have libassa3.5-5v5 and libassa-3.5-5v5.


pgpZ7BH1gcQwM.pgp
Description: PGP signature

Bug#796863: libassa3.5-5v5 and libassa-3.5-5v5: error when trying to install together

[Ralf Treinen]

Package: libassa-3.5-5v5,libassa3.5-5v5
Version: libassa-3.5-5v5/3.5.1-6
Version: libassa3.5-5v5/3.5.1-4.1
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite

Date: 2015-08-24
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:


Selecting previously unselected package gcc-5-base:amd64.
(Reading database ... 10899 files and directories currently installed.)
Preparing to unpack .../gcc-5-base_5.2.1-15_amd64.deb ...
Unpacking gcc-5-base:amd64 (5.2.1-15) ...
Setting up gcc-5-base:amd64 (5.2.1-15) ...
(Reading database ... 10906 files and directories currently installed.)
Preparing to unpack .../libstdc++6_5.2.1-15_amd64.deb ...
Unpacking libstdc++6:amd64 (5.2.1-15) over (4.8.2-19) ...
Setting up libstdc++6:amd64 (5.2.1-15) ...
Processing triggers for libc-bin (2.19-19) ...
Selecting previously unselected package libassa-3.5-5v5:amd64.
(Reading database ... 10920 files and directories currently installed.)
Preparing to unpack .../libassa-3.5-5v5_3.5.1-6_amd64.deb ...
Unpacking libassa-3.5-5v5:amd64 (3.5.1-6) ...
Selecting previously unselected package libassa3.5-5v5:amd64.
Preparing to unpack .../libassa3.5-5v5_3.5.1-4.1_amd64.deb ...
Unpacking libassa3.5-5v5:amd64 (3.5.1-4.1) ...
dpkg: error processing archive 
/var/cache/apt/archives/libassa3.5-5v5_3.5.1-4.1_amd64.deb (--unpack):
 trying to overwrite '/usr/lib/x86_64-linux-gnu/libassa-3.5.so.5.0.1', which is 
also in package libassa-3.5-5v5:amd64 3.5.1-6
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Errors were encountered while processing:
 /var/cache/apt/archives/libassa3.5-5v5_3.5.1-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/x86_64-linux-gnu/libassa-3.5.so.5
  /usr/lib/x86_64-linux-gnu/libassa-3.5.so.5.0.1

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://qa.debian.org/dose/file-overwrites.html.