Your message dated Tue, 16 Mar 2021 12:48:24 +0000 with message-id <e1lm97y-0006ks...@fasolo.debian.org> and subject line Bug#985347: fixed in bmake 20200710-8 has caused the Debian Bug report #985347, regarding bmake: missing Conflicts: bsdowl (<< 2.2.2-1.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.) -- 985347: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985347 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: bmake Version: 20200710-7 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Control: affects -1 + bsdowl 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. >From the attached log (scroll to the bottom...): Preparing to unpack .../021-bmake_20200710-7_amd64.deb ... rmdir: failed to remove '/usr/share/mk': No such file or directory Found a broken /usr/share/mk directory, unable to fix. bmake will not be able to find sys.mk Unpacking bmake (20200710-7) over (20160220-2+b1) ... dpkg: error processing archive /tmp/apt-dpkg-install-i1H4Us/021-bmake_20200710-7_amd64.deb (--unpack): trying to overwrite '/usr/share/mk', which is also in package bsdowl 2.2.2-1 Please add a versioned Conflicts in this case. We need to bsdowl package to be removed (or upgraded) s.t. the conflicting files are removed. Just deconfiguring the package (as could be done by apt with Breaks) is not sufficient. Lintian may give a warning about versioned Conflicts, you can override that. A bsdowl 2.2.2-1.2 package does not yet exist in the archive, but it would be the earliest version that could fix these issues. cheers, Andreas
bsdowl_None.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---Source: bmake Source-Version: 20200710-8 Done: Andrej Shadura <andre...@debian.org> We believe that the bug you reported is fixed in the latest version of bmake, 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 985...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andrej Shadura <andre...@debian.org> (supplier of updated bmake 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 ftpmas...@ftp-master.debian.org) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Format: 1.8 Date: Tue, 16 Mar 2021 13:36:16 +0100 Source: bmake Architecture: source Version: 20200710-8 Distribution: unstable Urgency: medium Maintainer: Andrej Shadura <andre...@debian.org> Changed-By: Andrej Shadura <andre...@debian.org> Closes: 985347 Changes: bmake (20200710-8) unstable; urgency=medium . * preinst: Properly deal with other packages installing files under /usr/share/mk (Closes: #985347) * Fix day-of-week for changelog entry 1.45-7. * Update standards version to 4.5.0, no changes needed. Checksums-Sha1: f96d956e3538fcdda2164f311922e4d15e9311ce 1339 bmake_20200710-8.dsc 854f6a776fb657269c7f1588caeb0b19eac3a077 36896 bmake_20200710-8.debian.tar.xz Checksums-Sha256: 234636b3991c5e9b6adf10c82305002042d6644cb802c69dc4cb63f3232df9ea 1339 bmake_20200710-8.dsc 6aae79a89443166c6dd284ec4d1c0c4176e17f404be6d6992445a22aaef046f5 36896 bmake_20200710-8.debian.tar.xz Files: 7cb56fc9b0396d3fef1881fb52c7334c 1339 devel optional bmake_20200710-8.dsc 9191bf5e5be0ab0ea98970aac6ec2e72 36896 devel optional bmake_20200710-8.debian.tar.xz -----BEGIN PGP SIGNATURE----- iHUEARYIAB0WIQSD3NF/RLIsyDZW7aHoRGtKyMdyYQUCYFCmegAKCRDoRGtKyMdy YcpfAQDO2gPFE4d2TYiMGP4r0scMoeZ8Z+09xfX/D0/qtAHGRgD/Znj5D0JoKMJc 5r2FWhdVHWc6vaPQzr827Y6/xJHNnAc= =/wnM -----END PGP SIGNATURE-----
--- End Message ---
