Debian Bug report logs - #974046
ruby-launchy: missing Breaks+Replaces: launchy

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Andreas Beckmann <anbe@debian.org>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: ruby-launchy: missing Breaks+Replaces: launchy

Date: Mon, 09 Nov 2020 13:39:43 +0100

[Message part 1 (text/plain, inline)]

Package: ruby-launchy
Version: 2.5.0-2
Severity: serious
User: debian-qa@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'buster'.
It installed fine in 'buster', then the upgrade to 'bullseye' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces

From the attached log (scroll to the bottom...):

  Preparing to unpack .../ruby-launchy_2.5.0-2_all.deb ...
  Unpacking ruby-launchy (2.5.0-2) ...
  dpkg: error processing archive /var/cache/apt/archives/ruby-launchy_2.5.0-2_all.deb (--unpack):
   trying to overwrite '/usr/bin/launchy', which is also in package launchy 2.5-4
  Errors were encountered while processing:
   /var/cache/apt/archives/ruby-launchy_2.5.0-2_all.deb

The launchy package last existed in buster, it is gone from sid.


cheers,

Andreas

[launchy=2.5-4_ruby-launchy=2.5.0-2.log.gz (application/gzip, attachment)]

Message #10 received at 974046-close@bugs.debian.org (full text, mbox, reply):

From: Debian FTP Masters <ftpmaster@ftp-master.debian.org>

To: 974046-close@bugs.debian.org

Subject: Bug#974046: fixed in ruby-launchy 2.5.0-3

Date: Fri, 05 Feb 2021 09:34:41 +0000

Source: ruby-launchy
Source-Version: 2.5.0-3
Done: Utkarsh Gupta <utkarsh@debian.org>

We believe that the bug you reported is fixed in the latest version of
ruby-launchy, which is due to be installed in the Debian FTP archive.

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 974046@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Utkarsh Gupta <utkarsh@debian.org> (supplier of updated ruby-launchy 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@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Fri, 05 Feb 2021 14:42:10 +0530
Source: ruby-launchy
Architecture: source
Version: 2.5.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team <pkg-ruby-extras-maintainers@lists.alioth.debian.org>
Changed-By: Utkarsh Gupta <utkarsh@debian.org>
Closes: 974046
Changes:
 ruby-launchy (2.5.0-3) unstable; urgency=medium
 .
   * Team upload.
   * Add Breaks+Replaces for launchy. (Closes: #974046)
Checksums-Sha1:
 6ade4b088d6c8e1ec11742bb7a303acf2b6a12f3 2135 ruby-launchy_2.5.0-3.dsc
 d1bc352272ffdffad50ed69ae317c4022e893226 3532 ruby-launchy_2.5.0-3.debian.tar.xz
 2e156f037fb88e06d98de4af66c30363deef1abf 9937 ruby-launchy_2.5.0-3_amd64.buildinfo
Checksums-Sha256:
 dfb4bc0c580250c72ef64901042fc517beeec0dd4043024e6a13c96a733f96a5 2135 ruby-launchy_2.5.0-3.dsc
 db1ef6380ad24844a77256bcc9dda44583603351f4cc219e130628df1cbddf89 3532 ruby-launchy_2.5.0-3.debian.tar.xz
 5c1a0f4ddbb6f8e99dbf207db2021c3667d2a1a9333b47d9bb380bbcca4e85cb 9937 ruby-launchy_2.5.0-3_amd64.buildinfo
Files:
 7514de1bb80b1a63377ec0290b14f50a 2135 ruby optional ruby-launchy_2.5.0-3.dsc
 a6eab13dac178bf985aa161b578a15c4 3532 ruby optional ruby-launchy_2.5.0-3.debian.tar.xz
 482bfa62a97e2cd3b5393d24266c1dc0 9937 ruby optional ruby-launchy_2.5.0-3_amd64.buildinfo

-----BEGIN PGP SIGNATURE-----

iQJHBAEBCAAxFiEEbJ0QSEqa5Mw4X3xxgj6WdgbDS5YFAmAdDKYTHHV0a2Fyc2hA
ZGViaWFuLm9yZwAKCRCCPpZ2BsNLluhKEACu2hteo5Np6JhXsukRdE2xaNpHwQxg
51c4e1x819IrgsKdseZr+n7Xox1nVE9QMYIMo5ZVMFkDsUnB/4glevTInFxfkoVN
MS/443sG4xVMfYGLjmY0fd0jaOvE/Dm7Pd0TAqveqcLU0LRuvFCiqnbbJaMMLk8a
NlETH+Bk7eOGVHm0Qc7S2hEeO0M7Y/NKMmQSPgseG2dCl+RZkv6J2ctqHuXa2QCU
rZXdPfVjvuvP0n7nj+PNlHSztwh9TBlnrL3racXI/C4PTvy2go078qPmv8mHwMue
bit1/oM99SraUcajStghz9HckJ1EFu9I/AFp3E8Z/7xmJXcgULLxCWinBXbtQMcZ
80MshiiL7Q0LKBJTd0gSHYMZnfil4u0WUjSFttzdHft2kK/iqWirt05MBqgDAYuQ
grGt0WthTIUBZsB+LOCUqMQDcN1n9n60adULHLDCGgS0TsygDElLdv7Xh2myfCaN
/RYg7x2a1DB0+Qel+anSqQJ+m0Bfl5tqfD4uJgdYnKO+dsLnLhoULXiHVrFwEYIi
3d78RbtIXo+t4AnZs9+deXNyOEAM44fi/v7QkMIR56XlPvJHBvUZhBDipE70lTkg
Hp4i/YjjBa1LD2yyg6HRNR4IH9eReOnCD6KK3guy9VWqNLyBISBw8FinAST9aRyq
cMm8bwNxzWxNmw==
=/nZ9
-----END PGP SIGNATURE-----

Send a report that this bug log contains spam.