Your message dated Wed, 23 Feb 2022 11:02:14 +0100
with message-id <164561053431.2636895.13903813753663682...@auryn.jones.dk>
and subject line Re: [Pkg-javascript-devel] Bug#1006214: Bug#1006205:
node-md5-hex: ships files already provided by node-blueimp-md5
has caused the Debian Bug report #1006214,
regarding node-blueimp-md5: missing Breaks+Replaces: node-md5-hex (<<
3.0.1+~2.19.0-2~)
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 ow...@bugs.debian.org
immediately.)
--
1006214: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006214
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: node-md5-hex
Version: 3.0.1+~2.19.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite other packages files.
>From the attached log (scroll to the bottom...):
Preparing to unpack .../node-md5-hex_3.0.1+~2.19.0-1_all.deb ...
Unpacking node-md5-hex (3.0.1+~2.19.0-1) ...
dpkg: error processing archive
/var/cache/apt/archives/node-md5-hex_3.0.1+~2.19.0-1_all.deb (--unpack):
trying to overwrite '/usr/share/nodejs/blueimp-md5/js/md5.js', which is also
in package node-blueimp-md5 2.19.0~ds-2
Errors were encountered while processing:
/var/cache/apt/archives/node-md5-hex_3.0.1+~2.19.0-1_all.deb
These files are shipped by both packages:
/usr/share/nodejs/blueimp-md5/js/md5.js
/usr/share/nodejs/blueimp-md5/package.json
cheers,
Andreas
node-blueimp-md5=2.19.0~ds-2_node-md5-hex=3.0.1+~2.19.0-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Quoting Jonas Smedegaard (2022-02-21 14:54:48)
> Quoting Andreas Beckmann (2022-02-21 13:55:20)
> > node-blueimp-md5 was only recently uploaded to the archive.
> > Therefore node-md5-hex needs to stop bundling it and use the
> > separately packaged node-blueimp-md5 instead.
> >
> > node-blueimp-md5 needs Breaks+Replaces against node-md5-hex versions
> > that bundled node-blueimp-md5 content. (The version (<<
> > 3.0.1+~2.19.0-2~) is only a guess.)
>
> Makes sense.
>
> For the record, despite this bug being release-critical, my plan is to
> do exactly nothing about it, since I expect to be able to close it
> (with zero changes to node-blueimp-md5) about a week from now when I
> expect node-md5-hex to no longer provide blueimp-md5 in any supported
> branches of Debian.
As expected, this issue is now resolved by fixed node-md5-hex having
migrated to testing: No need to declare Breaks in node-blueimp-md5.
Closing.
- 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
--- End Message ---
