Bug#1034971: lxd-client: missing Breaks+Replaces for lxc when upgrading from bullseye
Hi Mathias, On Fri, Apr 28, 2023 at 02:32:10AM +, Mathias Gibbens wrote: > It looks like you're trying to install the version of lxd from > testing on a bullseye system? Mixing packages from different releases > isn't supported [1]. Furthermore, there hasn't yet been a stable In fact this is supported as a partial upgrade. The situation of mixing packages from stable and testing is very common and happens during and dist-upgrade. > release of Debian that shipped lxd, so there's no way lxd-client might > be upgraded before lxc when upgrading from bullseye to bookworm. As > such, I don't know if it's really worthwhile to try to address this > situation that would only occur when the end-user has already broken > key assumptions about how their system is configured. That's indeed a better argument. It is non-trivial to rule out the scenario in bookworm Depends or Recommends lxd and thus pulls lxd into the upgrade scenario. > The packaging of lxc was updated during the bookworm development > cycle to properly name its bash completion file and de-conflict with > lxd packaging [2]. Upgrading lxc packages from bullseye -> bookworm > should work smoothly; after the upgrade is complete users will then > also be able to `apt install lxd` if they so wish, and they won't > encounter the packaging conflict. This is a good reason for why the effects should be minor. It still is not clear whether something in the upgrade would be able to pull lxd and thus trigger the situation. In any case, the reasoning seems sufficient to me to downgrade the severity to important. After bookworm is released, the bug can be closed in any case as we don't support skip upgrades. > Does that address your concern? Partially. Helmut
Bug#1034939: librust---dev: missing Breaks+Replaces for librust-mio-dev when upgrading from bullseye
Hi Peter, On Fri, Apr 28, 2023 at 01:24:16AM +0100, Peter Green wrote: > Summarising a number of bug reports by Helmut Ghrone: > > > Please ensure that librust---dev has sufficient Breaks and > > Replaces declarations. > > The issue specifically appears to be that the breaks+replaces are declared > against a virtual package, it seems dpkg is honoring the breaks against the > virtual package but not the replaces. So it correctly marks the package from > stable as broken, but fails to actually unpack the package from testing. Thanks for looking into this so quickly. I concur: The Breaks are ok, but the Replaces are not. Debian policy section 7.6.1 explicitly says that Replaces don't work on virtual packages. > Declaring against the physical package is also problematic becase Debian > package > relationships don't support version ranges. What this would likely mean in > practice is it would be possible to co-install the "current" semver alongside > one previous semver, but it would not be possible to co-install two different > previous semvers. Can you go into more detail as to what you mean with "don't support version ranges"? In principle, you could declare the Replacs to be slightly broader than necessary (i.e. instead of declaring against the specific range, you can replace all old packages). Do you agree that this is feasible? > Another option may be to use "Conflicts" instead of "Breaks". This should > force > the old package to be upgraded or removed before the semver-specific package > can be unpacked. It's a big hammer. It'll work. It's a hammer we're looking into as part of the DEP 17 thread on debian-de...@lists.debian.org currently, but I recommend avoiding it if possible. Possible it seems in this case. > I feel the timing of these bugs is very unfortunate. I don't object to > people running QA checks, but it's generally easier to deal with bugs if > they are reported earlier in the freeze process. The timing of these bugs > leaves little time for discussion if we are to get the fixes in before the > full freeze. I am sorry about that. This is a side-effect of earlier discussions having stalled and only recently been picked up. However, these tests should likely be running more continuously. > As I see it we have a few options to deal with this for bookworm. > > 1. Make debcargo Use Conflicts instead of Breaks. > 2. Make debcargo declare Breaks/Replaces against the physical package >version using a << dependency. This will allow the non-semver suffixed >package to be installed alongside one semver-suffixed package, but with >our current virtual packages scheme would not allow two semver-suffixed >packages of the same crate to be coinstalled. > 3. Add manual breaks/replaces for the versions in bullseye, this will >paper over the issue for bullseye-bookworm upgrades, but is not a long >term fix. 4. Continue to use Breaks the way they are. Declare Replaces against the physical package using a << relation. This would not allow the semver-suffixed package to be installed alongside, but Breaks and Replaces would no longer match up and that could make lintian unhappy. 5. In a different bug, Samuel Thibault observed that the target package was not part of bullseye. As such, an upgrade scenario involving it was unlikely. All of the 6 affected librus-*-dev packages are not part of bullseye. We could argue that the risk of these effects showing up in practice is not big enough to warrant an invasive fix. Rather, we'd downgrade them to important (and upgrade to serious when we see them in the wild) and close them after bookworm (since we don't support skip upgrades). > Do any other members of the rust team have an opinion on this? I'm > personally inclined towards option 1 and intend to implement it if > noone objects in the next couple of days. Let me know if you see 4 as a viable option. > Do the release team have an opinion on this? It looks like only one of > the packages involved (rust-env-logger-0.7) is a key package. I filed these as serious, because these are policy violations with a trivial fix. You made it quite clear that the premise of the fix being trivial is false here. If the cure is worse than the symptoms, maybe we should consider not applying the cure and select option 5. Helmut
Processed: bug 1034088 is forwarded to https://github.com/cyrusimap/cyrus-imapd/issues/4493
Processing commands for cont...@bugs.debian.org:
> forwarded 1034088 https://github.com/cyrusimap/cyrus-imapd/issues/4493
Bug #1034088 {Done: Yadd } [src:cyrus-imapd] cyrus-imapd:
fails to clean after successful build: No rule to make target 'Makefile.PL',
needed by 'Makefile'.
Set Bug forwarded-to-address to
'https://github.com/cyrusimap/cyrus-imapd/issues/4493'.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1034088: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034088
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1034088: marked as done (cyrus-imapd: fails to clean after successful build: No rule to make target 'Makefile.PL', needed by 'Makefile'.)
Your message dated Fri, 28 Apr 2023 04:34:19 + with message-id and subject line Bug#1034088: fixed in cyrus-imapd 3.8.0~rc1-1 has caused the Debian Bug report #1034088, regarding cyrus-imapd: fails to clean after successful build: No rule to make target 'Makefile.PL', needed by 'Makefile'. 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.) -- 1034088: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034088 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: cyrus-imapd Version: 3.8.0~beta2-1 Severity: serious Justification: fails to build from source twice in a row Hi, cyrus-imapd/experimental fails to clean after a successful build. (I didn't verify whether the package in sid has the same problem.) ... Making distclean in perl/annotator make[2]: Entering directory '/build/cyrus-imapd-3.8.0~beta2/perl/annotator' make[2]: *** No rule to make target 'Makefile.PL', needed by 'Makefile'. Stop. make[2]: Leaving directory '/build/cyrus-imapd-3.8.0~beta2/perl/annotator' make[1]: *** [Makefile:7537: distclean-recursive] Error 1 make[1]: Leaving directory '/build/cyrus-imapd-3.8.0~beta2' dh_auto_clean: error: make -j3 distclean returned exit code 2 make: *** [debian/rules:57: clean] Error 25 Andreas cyrus-imapd_3.8.0~beta2-1_twice.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: cyrus-imapd Source-Version: 3.8.0~rc1-1 Done: Yadd We believe that the bug you reported is fixed in the latest version of cyrus-imapd, 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 1034...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Yadd (supplier of updated cyrus-imapd 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: SHA512 Format: 1.8 Date: Fri, 28 Apr 2023 08:01:22 +0400 Source: cyrus-imapd Architecture: source Version: 3.8.0~rc1-1 Distribution: experimental Urgency: medium Maintainer: Debian Cyrus Team Changed-By: Yadd Closes: 1034088 Changes: cyrus-imapd (3.8.0~rc1-1) experimental; urgency=medium . * Update dependencies: drop lsb-base (provided by sysvinit-utils which is an essential package) * New upstream version 3.8.0~rc1 * Unfuzz patches * Fix clean (Closes: #1034088) Checksums-Sha1: c16c87e809ddb025dc35212b529c42e9f8c8c33a 5469 cyrus-imapd_3.8.0~rc1-1.dsc 920d1f0384f4c6b25a9cfa361502fc88b6baa73a 14148494 cyrus-imapd_3.8.0~rc1.orig.tar.gz 5e0de8125df2b2d7db5c9dec83f4ee876491f5e2 488 cyrus-imapd_3.8.0~rc1.orig.tar.gz.asc 965b2edc6c35b218a4b353d9041ad32c52f6bcbe 87336 cyrus-imapd_3.8.0~rc1-1.debian.tar.xz Checksums-Sha256: fb3ff5013580a582560fe9ce261ecaf402814d89d2b236b735c200b3d3ecea41 5469 cyrus-imapd_3.8.0~rc1-1.dsc d98823398f92887b0295054d2e7efb9cc3ee32da2b033c7c88e48c506a1d8bf8 14148494 cyrus-imapd_3.8.0~rc1.orig.tar.gz f43bdb185f13a04050e79b8f0104fe1e1ca8f03e30abc45303d5a16af3c2de8a 488 cyrus-imapd_3.8.0~rc1.orig.tar.gz.asc 6f75fbeef921a9c48453ee03f9b7e278bf480f7ce3442adcc7f12cb9f86f8536 87336 cyrus-imapd_3.8.0~rc1-1.debian.tar.xz Files: 256300d1201215806b9acd9be56003cc 5469 mail optional cyrus-imapd_3.8.0~rc1-1.dsc adc5ae6f533100dbe39268b9a442aa71 14148494 mail optional cyrus-imapd_3.8.0~rc1.orig.tar.gz cbe96dd8be3e42efe084f43f2183c508 488 mail optional cyrus-imapd_3.8.0~rc1.orig.tar.gz.asc 0b293ac39f4e4e02c3e0df8fadf9c4df 87336 mail optional cyrus-imapd_3.8.0~rc1-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAmRLRoIACgkQ9tdMp8mZ 7ukTfQ//ZoyjXxNjbDZtPserpoT0V1fv+asWZdcVlO7ePlrV1GJ6RlE3mCbxInIZ wrrTzyPFaKmr9qCEl/MHU81b501NtgmgFTPJnLLJPE9siwCmf2tnnO9ENa/RZfT3 FtCJhuH2IobEEHeXdYFb2RhW2jGbzYAdMN9jASDVVa6IwaGEjc5QJYTtMWE4hwfX tCj2gF8VJpA5M/ufSIM2wUTdDeQtW29jjfh7jfyju1bS7RiD7CyV2wg75RuZrj4C ILhLW2EGbcToUddmzIIjQAmTRMtwKXAHf0CMjEiIk9JxDUEZ7b4BJU8vj2L0qikb xj7+KmXZSktn0rHnBx3k2SX7QNbeGAgC4OA58t3CA4aVX9Mbmsw+e12DjlHO3Yhb ast/ExQRqjNFBUVZHysEKWpCa/LgfGr56WsiWixQ9jlh3YbkKVfdSaERigUHEQHy serJLuTvrdJOkcUE+nIpyLUX0sDjpyKpFoPct3InV5wna3zpoIEXUUPM8xJHHBF2 risvZroZXn87fxL6VlL4mA71sHU3ffALFnLqtsueLHktxeK0cFF5LHRz2uBSegmb dvDqRrmR1nVSO9hKZ1YAheblQVgau3xW8BGXN6hhTopRmrvJeknhxV+sA7A5BCvO
Processed: closing 997084
Processing commands for cont...@bugs.debian.org: > close 997084 Bug #997084 [src:node-handlebars] node-handlebars: FTBFS: build hangs Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 997084: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997084 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1034945: marked as done (node-npm-run-path: missing Breaks+Replaces for node-execa when upgrading from bullseye)
Your message dated Fri, 28 Apr 2023 03:33:55 + with message-id and subject line Bug#1034945: fixed in node-npm-run-path 5.1.0+~4.0.0-8 has caused the Debian Bug report #1034945, regarding node-npm-run-path: missing Breaks+Replaces for node-execa when upgrading from bullseye 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.) -- 1034945: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034945 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: node-npm-run-path Version: 5.1.0+~4.0.0-7 Severity: serious Justification: dpkg unpack error Attempting to unpack node-npm-run-path/5.1.0+~4.0.0-7 from Debian bookworm on a minimal Debian bullseye with node-execa/4.1.0+dfsg+~cs19.3.6-5 installed, causes an unpack error from dpkg due to /usr/share/nodejs/path-key/index.d.ts being contained in both packages. | dpkg: considering deconfiguration of node-execa, which would be broken by installation of node-npm-run-path ... | dpkg: yes, will deconfigure node-execa (broken by node-npm-run-path) | (Reading database ... 4965 files and directories currently installed.) | Preparing to unpack .../node-npm-run-path_5.1.0+~4.0.0-7_all.deb ... | De-configuring node-execa (4.1.0+dfsg+~cs19.3.6-5) ... | Unpacking node-npm-run-path (5.1.0+~4.0.0-7) over (2.0.2-2) ... | dpkg: error processing archive ./node-npm-run-path_5.1.0+~4.0.0-7_all.deb (--unpack): | trying to overwrite '/usr/share/nodejs/path-key/index.d.ts', which is also in package node-execa 4.1.0+dfsg+~cs19.3.6-5 | Errors were encountered while processing: | ./node-npm-run-path_5.1.0+~4.0.0-7_all.deb Please ensure that node-npm-run-path has sufficient Breaks and Replaces declarations. Helmut --- End Message --- --- Begin Message --- Source: node-npm-run-path Source-Version: 5.1.0+~4.0.0-8 Done: Yadd We believe that the bug you reported is fixed in the latest version of node-npm-run-path, 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 1034...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Yadd (supplier of updated node-npm-run-path 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: SHA512 Format: 1.8 Date: Fri, 28 Apr 2023 07:08:33 +0400 Source: node-npm-run-path Architecture: source Version: 5.1.0+~4.0.0-8 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Yadd Closes: 1034945 Changes: node-npm-run-path (5.1.0+~4.0.0-8) unstable; urgency=medium . * Team upload * Duplicate Breaks field with Replaces (Closes: #1034945) Checksums-Sha1: 8810ec925ef3603f71188fead48b9c37fcb6e909 2493 node-npm-run-path_5.1.0+~4.0.0-8.dsc cd1ee57a06c4b990d2270e3c72348871be371224 4952 node-npm-run-path_5.1.0+~4.0.0-8.debian.tar.xz Checksums-Sha256: 34d340b719f20a562dc8caf9b98526c201193b1b15689355f9a428eb7c0578e2 2493 node-npm-run-path_5.1.0+~4.0.0-8.dsc 4bb31b95aa4bb035b2836fc824c9933638addc6b27aa8d87fc7eb3dfc289ee11 4952 node-npm-run-path_5.1.0+~4.0.0-8.debian.tar.xz Files: b7ce1172e432561defe03fc6c31e7f19 2493 javascript optional node-npm-run-path_5.1.0+~4.0.0-8.dsc d50a02ad187b03baf4083cebd76fb583 4952 javascript optional node-npm-run-path_5.1.0+~4.0.0-8.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAmRLOS0ACgkQ9tdMp8mZ 7uli1BAAjojQtv6+BpsSAkm6vaHEi+O2Q5Z+pJj/xEGC4/RbTn0PFRT1CbhJx1AV DRqzG62dZr2LSQPboMwQLy4DCQ9oNM78WJm21c68ES3IXJeIjb8g2u29h6KH9Yw5 u3vrfiJanBR7aR2Jk3VgoMI7FFeEwMY6LQfXnacZN8yNzwUA+aZRlbsb4nqRGx7e bfCzVZhEvX27rtbyj8y/I5rFiLHifcZHF58CGIuj3Vo6oPnaQS2R2Tm1Pj6LRYMg InsbfovJU4M5gJlomHreOfN51OQDLP82i9VSO1/T1XrWTWESv3+mzkkBFC1VUzxN bUbd8zITb4+L7fCooi+BSjPt5qeTNYG2irigUAcfXNZffbilpSIgdYLGqytLY61Q kvncCsYMj850Q48IkqNM5H5ADzr2lwmWoUCeSmUkhZVXiJkKogFH+rub4NCS820p rFB/y1GAqzVL37kXF2BWfFzE6Pt/BOaAD4C4F3OVB5jIlqPiE2+x460L+tqnu/yQ FYoC1SiAEI5zBzVyB08SNN1u1ipT1Amh+LvSEptsExAAg0FiQzmvg567QuDJhUjg AUS4sEphkXRqioUVa3Eb89iquIUhoOiOpep54Lz9KRWLPuBDskKZTUrmUeoaKREW EUyMHTp+vEzLr1kaJXOTl1OOT19uy/y9oQiv8o0bungOV7gbcOM= =cD/V -END PGP SIGNATURE End Message ---
Bug#1034933: marked as done (node-whatwg-fetch: missing Breaks+Replaces for libjs-fetch when upgrading from bullseye)
Your message dated Fri, 28 Apr 2023 03:34:10 + with message-id and subject line Bug#1034933: fixed in node-whatwg-fetch 3.6.2-7 has caused the Debian Bug report #1034933, regarding node-whatwg-fetch: missing Breaks+Replaces for libjs-fetch when upgrading from bullseye 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.) -- 1034933: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034933 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: node-whatwg-fetch Version: 3.6.2-6 Severity: serious Justification: dpkg unpack error Attempting to unpack node-whatwg-fetch/3.6.2-6 from Debian bookworm on a minimal Debian bullseye with libjs-fetch/3.5.0-1 installed, causes an unpack error from dpkg due to /usr/share/nodejs/whatwg-fetch/fetch.js being contained in both packages. | Selecting previously unselected package node-whatwg-fetch. | dpkg: considering deconfiguration of libjs-fetch, which would be broken by installation of node-whatwg-fetch ... | dpkg: yes, will deconfigure libjs-fetch (broken by node-whatwg-fetch) | (Reading database ... 4693 files and directories currently installed.) | Preparing to unpack .../node-whatwg-fetch_3.6.2-6_all.deb ... | De-configuring libjs-fetch (3.5.0-1) ... | Unpacking node-whatwg-fetch (3.6.2-6) ... | dpkg: error processing archive ./node-whatwg-fetch_3.6.2-6_all.deb (--unpack): | trying to overwrite '/usr/share/nodejs/whatwg-fetch/fetch.js', which is also in package libjs-fetch 3.5.0-1 | Errors were encountered while processing: | ./node-whatwg-fetch_3.6.2-6_all.deb Please ensure that node-whatwg-fetch has sufficient Breaks and Replaces declarations. Helmut --- End Message --- --- Begin Message --- Source: node-whatwg-fetch Source-Version: 3.6.2-7 Done: Yadd We believe that the bug you reported is fixed in the latest version of node-whatwg-fetch, 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 1034...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Yadd (supplier of updated node-whatwg-fetch 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: SHA512 Format: 1.8 Date: Fri, 28 Apr 2023 07:13:09 +0400 Source: node-whatwg-fetch Built-For-Profiles: nocheck Architecture: source Version: 3.6.2-7 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Yadd Closes: 1034933 Changes: node-whatwg-fetch (3.6.2-7) unstable; urgency=medium . * Team upload * Duplicate Breaks field with Replaces (Closes: #1034933) Checksums-Sha1: 713075472b9a5856354f87e66768c4ddffe4e663 2082 node-whatwg-fetch_3.6.2-7.dsc c4518e24f880a1f8daa3baccb9c6e41b2e263868 3096 node-whatwg-fetch_3.6.2-7.debian.tar.xz Checksums-Sha256: bc9dfd8d973dc85647a7ee6bb13844258507d3ab92d12968128535e86e05e659 2082 node-whatwg-fetch_3.6.2-7.dsc b7cc9a50e4f11dd313bfc24d356aafa870f88dfcb1a335b7fdd6a36bb47fcd3d 3096 node-whatwg-fetch_3.6.2-7.debian.tar.xz Files: 9a07dd7b3eb2e0ac44e8f7feda1f3fdd 2082 javascript optional node-whatwg-fetch_3.6.2-7.dsc b9d179d55576baa39ebf1441468b92cd 3096 javascript optional node-whatwg-fetch_3.6.2-7.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAmRLOwAACgkQ9tdMp8mZ 7unHtxAAlM0JuRfS3mcxG6LGzGOrBBpc9ZMdxPVi0o59USGKztRSFd5IuEXpM6EH zFrRhI3z+EJW0dZWwstLw3gwPYxQL7pmVpxBPRPLqDXgol1P3IpgZr65DIB7a7RD 3kW7K7uN94CpGObL4sFM3qecUR21dOC+/DTRC6nAmLZgjkggcLFMVKf04w0qx5CF 6oLL9cbrQHR9lGUTFdTaG/8s20QIYPsbMGuZMlnEbb4W/ev8BVgK9EZpnmX+fk2c 77mRbXh1I8K4Q7xgqgFKXKmvflL+9Lr2x5PyWk3e1KfNtXF9K5k6e+f2zf0j3pLk ak4SGMWlcBCzA4VQmgoYBAvUQtJtDmcW27wMIKXdZT53WiaBoVDtzg/fYR5iKbaS z0ULHnnZAtgECkpz6+tcWrXEIzEnLT0LV7RWQHHoWflNssziQrFCDPX1/sBdd2MG fn75yYOqbFmciMJdkfNxYbdo052GSeXfxYzEjrCLX6RM7CP7DY4Z1JLfvL0xVvJu /gQ1VnmYgNhMCX1z1NKBEIVGJYVVevFzvm8qv0QKuLszILKsjo9nNMGEJYL/mutT LONOwqsM+TJ9Zh70d2b4ISpAc9Qwg1duAQTPHCjSgbEAoICDRKGIWT2f0rXejy4X C1jHi8XJLcTRO+3fYVrlFiMrGYSa3Bp7rpLMG2dyQTVTIKYmReo= =GOiN -END PGP SIGNATURE End Message ---
Bug#1034933: marked as pending in node-whatwg-fetch
Control: tag -1 pending Hello, Bug #1034933 in node-whatwg-fetch reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/node-whatwg-fetch/-/commit/daacd10cf7b3a9b322664239af853e5603952074 Duplicate Breaks field with Replaces Closes: #1034933 (this message was generated automatically) -- Greetings https://bugs.debian.org/1034933
Processed: Bug#1034933 marked as pending in node-whatwg-fetch
Processing control commands: > tag -1 pending Bug #1034933 [node-whatwg-fetch] node-whatwg-fetch: missing Breaks+Replaces for libjs-fetch when upgrading from bullseye Added tag(s) pending. -- 1034933: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034933 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1035008: marked as done (node-jest-worker: missing Breaks+Replaces for jest when upgrading from bullseye)
Your message dated Fri, 28 Apr 2023 03:19:54 + with message-id and subject line Bug#1035008: fixed in node-jest 29.3.1~ds1+~cs70.48.25-2 has caused the Debian Bug report #1035008, regarding node-jest-worker: missing Breaks+Replaces for jest when upgrading from bullseye 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.) -- 1035008: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035008 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: node-jest-worker Version: 29.3.1~ds1+~cs70.48.25-1 Severity: serious Justification: dpkg unpack error Attempting to unpack node-jest-worker/29.3.1~ds1+~cs70.48.25-1 from Debian bookworm on a minimal Debian bullseye with jest/26.6.3+repack+~cs64.44.39-3 installed, causes an unpack error from dpkg due to /usr/share/nodejs/@jest/types/build/Circus.d.ts being contained in both packages. | dpkg: considering deconfiguration of jest, which would be broken by installation of node-jest-worker ... | dpkg: yes, will deconfigure jest (broken by node-jest-worker) | (Reading database ... 21294 files and directories currently installed.) | Preparing to unpack .../node-jest-worker_29.3.1~ds1+~cs70.48.25-1_all.deb ... | De-configuring jest (26.6.3+repack+~cs64.44.39-3) ... | Unpacking node-jest-worker (29.3.1~ds1+~cs70.48.25-1) over (26.6.3+repack+~cs64.44.39-3) ... | dpkg: error processing archive ./node-jest-worker_29.3.1~ds1+~cs70.48.25-1_all.deb (--unpack): | trying to overwrite '/usr/share/nodejs/@jest/types/build/Circus.d.ts', which is also in package jest 26.6.3+repack+~cs64.44.39-3 | Errors were encountered while processing: | ./node-jest-worker_29.3.1~ds1+~cs70.48.25-1_all.deb Please ensure that node-jest-worker has sufficient Breaks and Replaces declarations. Helmut --- End Message --- --- Begin Message --- Source: node-jest Source-Version: 29.3.1~ds1+~cs70.48.25-2 Done: Yadd We believe that the bug you reported is fixed in the latest version of node-jest, 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 1035...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Yadd (supplier of updated node-jest 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: SHA512 Format: 1.8 Date: Fri, 28 Apr 2023 06:42:41 +0400 Source: node-jest Built-For-Profiles: nocheck Architecture: source Version: 29.3.1~ds1+~cs70.48.25-2 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Yadd Closes: 1035008 Changes: node-jest (29.3.1~ds1+~cs70.48.25-2) unstable; urgency=medium . * Duplicate Breaks field with Replaces (Closes: #1035008) Checksums-Sha1: bf21441edf19fe51877c05193a9bdc17ec44f218 12605 node-jest_29.3.1~ds1+~cs70.48.25-2.dsc efd05ea0274d344cd21428dd34fcddb8c46cbd85 147844 node-jest_29.3.1~ds1+~cs70.48.25-2.debian.tar.xz Checksums-Sha256: 7faad65375859275d774dd2becb898168a3f5820101c80d508b4ea3ca5cb88c7 12605 node-jest_29.3.1~ds1+~cs70.48.25-2.dsc 532c31ff5e60f16cec1b5fea17376b734a776c4fbcb68c35c489d52639ead804 147844 node-jest_29.3.1~ds1+~cs70.48.25-2.debian.tar.xz Files: adcd2cb4f03b9e041a5216edcd9a5db5 12605 javascript optional node-jest_29.3.1~ds1+~cs70.48.25-2.dsc 1e57eea360c6d7a3e32f23db4239d110 147844 javascript optional node-jest_29.3.1~ds1+~cs70.48.25-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAmRLN4cACgkQ9tdMp8mZ 7uknTBAAgNQioI3HMJdj3o+GiZ25+PdVa2+mynHyKqyadCKZLd2zrB0ydEOv4pib 0wcRK1/H/Daxu4v7bNQjr6S5XcTEuX2AMYMxrxAQ/u3CZKzyrq8mp4yxL7LcTM1f mEh3WXpfh4iAMJe7HQqk9ggDUC62tUld3jD/27pgSi8HIVldnYAQZspWxPzhkCNL GjlYLBEy3dEoCnqRHHWM8gpwWJKttMpctOHtexvhs7yLgh0wqSvm7SiBKpJTXU7c sX0Igau1UnsnBDMuwH8uaeZ9ifRC5ey+SPuuthMkdqtvHdiy3PRluSe8FZ5p3BC6 /WhO//+fqkTDjLBziOsFbL8pAwNlESkP7tW/pS88t7AjSGycozSx9+Fy/ZDgur2g DXPpzvAyVWwZwVEpDWtcapwP5dWCFCUQGZrPucAqSx6foApnESeEkB9Cuj8Ztooc uFYazrmk0zhqP9RrLWmXW5Tzp9zEetnp112ZqYWICb9QoK0Y9SrFSXCZHTLZIjDz uaY8i/IaX79Vae4jUIx5/PD/o63hE9LiqpGZVqtM6QVu6YJ5ymhZ2/TszS87+nx8 17EjqkPAP0tTcEHLONNT9FqJd7imkXKFwQmRStpV0uaBbG67w9BQoeusFiOuscvO Ge+sgHYxMGKdMs8SiZfNygclb07Ky9flpbx5eyrj8IWxXYOBBAo= =zmY9 -END PGP SIGNATURE End Message ---
Bug#1035000: marked as done (node-core-js-pure: missing Breaks+Replaces for node-core-js when upgrading from bullseye)
Your message dated Fri, 28 Apr 2023 03:19:08 + with message-id and subject line Bug#1035000: fixed in node-core-js 3.26.1-2 has caused the Debian Bug report #1035000, regarding node-core-js-pure: missing Breaks+Replaces for node-core-js when upgrading from bullseye 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.) -- 1035000: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035000 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: node-core-js-pure Version: 3.26.1-1 Severity: serious Justification: dpkg unpack error Attempting to unpack node-core-js-pure/3.26.1-1 from Debian bookworm on a minimal Debian bullseye with node-core-js/3.8.2-2 installed, causes an unpack error from dpkg due to /usr/share/nodejs/core-js-pure/configurator.js being contained in both packages. | Selecting previously unselected package node-core-js-pure. | dpkg: considering deconfiguration of node-core-js, which would be broken by installation of node-core-js-pure ... | dpkg: yes, will deconfigure node-core-js (broken by node-core-js-pure) | (Reading database ... 7666 files and directories currently installed.) | Preparing to unpack .../node-core-js-pure_3.26.1-1_all.deb ... | De-configuring node-core-js (3.8.2-2) ... | Unpacking node-core-js-pure (3.26.1-1) ... | dpkg: error processing archive ./node-core-js-pure_3.26.1-1_all.deb (--unpack): | trying to overwrite '/usr/share/nodejs/core-js-pure/configurator.js', which is also in package node-core-js 3.8.2-2 | dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) | Errors were encountered while processing: | ./node-core-js-pure_3.26.1-1_all.deb Please ensure that node-core-js-pure has sufficient Breaks and Replaces declarations. Helmut --- End Message --- --- Begin Message --- Source: node-core-js Source-Version: 3.26.1-2 Done: Yadd We believe that the bug you reported is fixed in the latest version of node-core-js, 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 1035...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Yadd (supplier of updated node-core-js 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: SHA512 Format: 1.8 Date: Fri, 28 Apr 2023 06:52:43 +0400 Source: node-core-js Architecture: source Version: 3.26.1-2 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Yadd Closes: 1034947 1034980 1034989 1035000 Changes: node-core-js (3.26.1-2) unstable; urgency=medium . * Team upload * Duplicate Breaks fields with Replaces (Closes: #1034980, #1034989, 1035000, #1034947) Checksums-Sha1: 63b76d3304a0f1c8971875ac85d636e86d0282cc 2447 node-core-js_3.26.1-2.dsc 547b85d0d69daa5ed40e05941b9f2ccdc425dfbb 8136 node-core-js_3.26.1-2.debian.tar.xz Checksums-Sha256: fcfbcb5f8cf91126529ba02c9777e4aa77e892540efd6e4627d021a511b65aa9 2447 node-core-js_3.26.1-2.dsc f695f686f142c712e3345b4f47be0512dc9b8b896e3d134fb770386dee151f59 8136 node-core-js_3.26.1-2.debian.tar.xz Files: be10841c312d4f8b14e54a7810288e8d 2447 javascript optional node-core-js_3.26.1-2.dsc e6aff033c0bfbe04fbccce8079957b2d 8136 javascript optional node-core-js_3.26.1-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAmRLN50ACgkQ9tdMp8mZ 7ukhjRAAk2EI89bCZwGKnT7lEgeplwbS5CO7wGqKCKRNQMAbpFlwhjDye5jqoEy8 vleJRpC4DenLuiv7tveewRbaW1ckLrAKSWb+k3Z3IdiLC4uoi/w/7SjHvZaDsb2J h+iGxQ+E4mEKup6zH2Ro2KXYJLJwkY7c5RBppDEdmYhFwZl8kNPM5O7jeJEBLQyq bKZTBruhdEku3SdVC04/zrwt9XBpJW7gz1vUOZhZ7evIKvVckjRGWbuSN4oCqe98 UcfEe+vLfH/YviEkQFcQxP9YYFKfE9kSgFEinSa+3Yt2O/xOGy5r/ExUrQoAUmOs f4dLTOhXu3OV3OWafoKSsUgMs0CBrByDgSbBFxRs3uCVeV+3sGpfJCt2MUMhGOmr F11uHD+MPsyPHjiFIyFZtYMvAs2ig1p3WVmJi8BsAzrodfiqBxwwBmrl7v5qI3Sx izIgC3ulzzwa2DlpqbuJsLh5u3+0BxLoUwVIx2w3J/k8nmEDYYMGpulod4oDgzho 9VF38VcJIQQuCPKl59TUT0ab9XizqCHAOGycmMuODHyHjB0lQokQ7vZ8PJ4p9fha aOODVxpMPJClLGCHlKIjRInkqtCPUETfR3Z+5PqiycduDF6Ps5QPNF9P0Ii+uR+t LMWH9mktuKLE2H8pU5ItjkkBXf6JESdT5nfeuwSHoHQr7EetY9E= =/GQk -END PGP SIGNATURE End Message ---
Bug#1034989: marked as done (node-core-js-bundle: missing Breaks+Replaces for node-core-js when upgrading from bullseye)
Your message dated Fri, 28 Apr 2023 03:19:08 + with message-id and subject line Bug#1034989: fixed in node-core-js 3.26.1-2 has caused the Debian Bug report #1034989, regarding node-core-js-bundle: missing Breaks+Replaces for node-core-js when upgrading from bullseye 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.) -- 1034989: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034989 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: node-core-js-bundle Version: 3.26.1-1 Severity: serious Justification: dpkg unpack error Attempting to unpack node-core-js-bundle/3.26.1-1 from Debian bookworm on a minimal Debian bullseye with node-core-js/3.8.2-2 installed, causes an unpack error from dpkg due to /usr/share/nodejs/core-js-bundle/package.json being contained in both packages. | Selecting previously unselected package node-core-js-bundle. | dpkg: considering deconfiguration of node-core-js, which would be broken by installation of node-core-js-bundle ... | dpkg: yes, will deconfigure node-core-js (broken by node-core-js-bundle) | (Reading database ... 7666 files and directories currently installed.) | Preparing to unpack .../node-core-js-bundle_3.26.1-1_all.deb ... | De-configuring node-core-js (3.8.2-2) ... | Unpacking node-core-js-bundle (3.26.1-1) ... | dpkg: error processing archive ./node-core-js-bundle_3.26.1-1_all.deb (--unpack): | trying to overwrite '/usr/share/nodejs/core-js-bundle/package.json', which is also in package node-core-js 3.8.2-2 | Errors were encountered while processing: | ./node-core-js-bundle_3.26.1-1_all.deb Please ensure that node-core-js-bundle has sufficient Breaks and Replaces declarations. Helmut --- End Message --- --- Begin Message --- Source: node-core-js Source-Version: 3.26.1-2 Done: Yadd We believe that the bug you reported is fixed in the latest version of node-core-js, 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 1034...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Yadd (supplier of updated node-core-js 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: SHA512 Format: 1.8 Date: Fri, 28 Apr 2023 06:52:43 +0400 Source: node-core-js Architecture: source Version: 3.26.1-2 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Yadd Closes: 1034947 1034980 1034989 1035000 Changes: node-core-js (3.26.1-2) unstable; urgency=medium . * Team upload * Duplicate Breaks fields with Replaces (Closes: #1034980, #1034989, 1035000, #1034947) Checksums-Sha1: 63b76d3304a0f1c8971875ac85d636e86d0282cc 2447 node-core-js_3.26.1-2.dsc 547b85d0d69daa5ed40e05941b9f2ccdc425dfbb 8136 node-core-js_3.26.1-2.debian.tar.xz Checksums-Sha256: fcfbcb5f8cf91126529ba02c9777e4aa77e892540efd6e4627d021a511b65aa9 2447 node-core-js_3.26.1-2.dsc f695f686f142c712e3345b4f47be0512dc9b8b896e3d134fb770386dee151f59 8136 node-core-js_3.26.1-2.debian.tar.xz Files: be10841c312d4f8b14e54a7810288e8d 2447 javascript optional node-core-js_3.26.1-2.dsc e6aff033c0bfbe04fbccce8079957b2d 8136 javascript optional node-core-js_3.26.1-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAmRLN50ACgkQ9tdMp8mZ 7ukhjRAAk2EI89bCZwGKnT7lEgeplwbS5CO7wGqKCKRNQMAbpFlwhjDye5jqoEy8 vleJRpC4DenLuiv7tveewRbaW1ckLrAKSWb+k3Z3IdiLC4uoi/w/7SjHvZaDsb2J h+iGxQ+E4mEKup6zH2Ro2KXYJLJwkY7c5RBppDEdmYhFwZl8kNPM5O7jeJEBLQyq bKZTBruhdEku3SdVC04/zrwt9XBpJW7gz1vUOZhZ7evIKvVckjRGWbuSN4oCqe98 UcfEe+vLfH/YviEkQFcQxP9YYFKfE9kSgFEinSa+3Yt2O/xOGy5r/ExUrQoAUmOs f4dLTOhXu3OV3OWafoKSsUgMs0CBrByDgSbBFxRs3uCVeV+3sGpfJCt2MUMhGOmr F11uHD+MPsyPHjiFIyFZtYMvAs2ig1p3WVmJi8BsAzrodfiqBxwwBmrl7v5qI3Sx izIgC3ulzzwa2DlpqbuJsLh5u3+0BxLoUwVIx2w3J/k8nmEDYYMGpulod4oDgzho 9VF38VcJIQQuCPKl59TUT0ab9XizqCHAOGycmMuODHyHjB0lQokQ7vZ8PJ4p9fha aOODVxpMPJClLGCHlKIjRInkqtCPUETfR3Z+5PqiycduDF6Ps5QPNF9P0Ii+uR+t LMWH9mktuKLE2H8pU5ItjkkBXf6JESdT5nfeuwSHoHQr7EetY9E= =/GQk -END PGP SIGNATURE End Message ---
Bug#1034984: marked as done (node-parse5-htmlparser2-tree-adapter: missing Breaks+Replaces for node-cheerio when upgrading from bullseye)
Your message dated Fri, 28 Apr 2023 03:20:02 + with message-id and subject line Bug#1034984: fixed in node-parse5 7.1.2+dfsg-2 has caused the Debian Bug report #1034984, regarding node-parse5-htmlparser2-tree-adapter: missing Breaks+Replaces for node-cheerio when upgrading from bullseye 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.) -- 1034984: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034984 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: node-parse5-htmlparser2-tree-adapter Version: 7.1.2+dfsg-1 Severity: serious Justification: dpkg unpack error Attempting to unpack node-parse5-htmlparser2-tree-adapter/7.1.2+dfsg-1 from Debian bookworm on a minimal Debian bullseye with node-cheerio/1.0.0~rc~5+~cs6.1.2-4 installed, causes an unpack error from dpkg due to /usr/share/nodejs/parse5-htmlparser2-tree-adapter/package.json being contained in both packages. | Selecting previously unselected package node-parse5-htmlparser2-tree-adapter. | dpkg: considering deconfiguration of node-jsdom, which would be broken by installation of node-parse5-htmlparser2-tree-adapter ... | dpkg: yes, will deconfigure node-jsdom (broken by node-parse5-htmlparser2-tree-adapter) | (Reading database ... 7213 files and directories currently installed.) | Preparing to unpack .../node-parse5-htmlparser2-tree-adapter_7.1.2+dfsg-1_all.deb ... | De-configuring node-jsdom (16.4.0+~cs77.17.35-3) ... | Unpacking node-parse5-htmlparser2-tree-adapter (7.1.2+dfsg-1) ... | dpkg: error processing archive ./node-parse5-htmlparser2-tree-adapter_7.1.2+dfsg-1_all.deb (--unpack): | trying to overwrite '/usr/share/nodejs/parse5-htmlparser2-tree-adapter/package.json', which is also in package node-cheerio 1.0.0~rc~5+~cs6.1.2-4 | Errors were encountered while processing: | ./node-parse5-htmlparser2-tree-adapter_7.1.2+dfsg-1_all.deb Please ensure that node-parse5-htmlparser2-tree-adapter has sufficient Breaks and Replaces declarations. Helmut --- End Message --- --- Begin Message --- Source: node-parse5 Source-Version: 7.1.2+dfsg-2 Done: Yadd We believe that the bug you reported is fixed in the latest version of node-parse5, 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 1034...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Yadd (supplier of updated node-parse5 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: SHA512 Format: 1.8 Date: Fri, 28 Apr 2023 06:58:41 +0400 Source: node-parse5 Architecture: source Version: 7.1.2+dfsg-2 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Yadd Closes: 1034984 Changes: node-parse5 (7.1.2+dfsg-2) unstable; urgency=medium . * Team upload * Add missing Breaks+Replaces against node-cheerio (Closes: #1034984) Checksums-Sha1: 4ad2fde23cea439078a1d3b646ed41e3c930100b 2622 node-parse5_7.1.2+dfsg-2.dsc 2762994f1cbc7f5a3ed0c94f212af41184e6df91 4544 node-parse5_7.1.2+dfsg-2.debian.tar.xz Checksums-Sha256: 0cc6bf8e8d56b2f9da251413f754abac8a9193c899f376022ec4d63f5efa97dd 2622 node-parse5_7.1.2+dfsg-2.dsc ae08156f324544c75c2cd64dcd869de44f26fe63aa7d3f9473e9a4d1446bd725 4544 node-parse5_7.1.2+dfsg-2.debian.tar.xz Files: c39aa30b0b66bca675203c2386ff6066 2622 javascript optional node-parse5_7.1.2+dfsg-2.dsc 67e9fd49a7b789227dab1deb84376c76 4544 javascript optional node-parse5_7.1.2+dfsg-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAmRLOCAACgkQ9tdMp8mZ 7uk7Ng/9GE6YU3vvj095s4WsDvvn9URW0Spn8vh2v4JsJm1W83hrIUSrWFBptyjE f6QbmeKyTpkqydqKeZbCLtYbGAog25umikUlrjWlDdwiE3V8cteVctyUVuYvvi3M o/z/Sw5Cm7C3ybiHvqRrrR8dlUhmAOMrcMV1g+Mj0KkBAcypPp734azmJYgmlSec 3dqEtLcDkNopbRL7/c2z2m4VM2MO2V24Iuq+AQftR7CyUiWm43WD6VkLDj6UagM2 DIg8UxXR56iSCWx8GgtBXPuev+7QMvYXSwhWpDVvF/W0fDasaqLc4YCvkCcZ9nGz 5cNAIMQGtb78j6mrpmJ+GHRfJLqblWWca5aYQUMi55cyEnnAIYOwlau63fj2Gq4J SQgr9STrkOYbr2DSciIC/3Ltlpj0HvaP+jqex+hGtyY0U+W+4EwwVl3HVMhQUde7 LvBUCFRhdamH8YX08xNo4+qbjlh7sKxDn6Xr14taIQ2hNSK6oCvmVmBavfO4InAK 224TxaTkaXEhMt7lMO30UQFlgOBBlNXzPO9wjLUo/XDwf6AtnV8vtD3OD9B1PLya 3vUBtm90oXFhuqJS2PQ80AlM8gG4v9A2DNfBSrrHuIl9rOy9TcKUmPNFSjkKs+Gu
Bug#1034980: marked as done (node-core-js-builder: missing Breaks+Replaces for node-core-js when upgrading from bullseye)
Your message dated Fri, 28 Apr 2023 03:19:08 + with message-id and subject line Bug#1034980: fixed in node-core-js 3.26.1-2 has caused the Debian Bug report #1034980, regarding node-core-js-builder: missing Breaks+Replaces for node-core-js when upgrading from bullseye 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.) -- 1034980: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034980 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: node-core-js-builder Version: 3.26.1-1 Severity: serious Justification: dpkg unpack error Attempting to unpack node-core-js-builder/3.26.1-1 from Debian bookworm on a minimal Debian bullseye with node-core-js/3.8.2-2 installed, causes an unpack error from dpkg due to /usr/share/nodejs/core-js-builder/config.js being contained in both packages. | Selecting previously unselected package node-core-js-builder. | dpkg: considering deconfiguration of node-core-js, which would be broken by installation of node-core-js-builder ... | dpkg: yes, will deconfigure node-core-js (broken by node-core-js-builder) | (Reading database ... 7666 files and directories currently installed.) | Preparing to unpack .../node-core-js-builder_3.26.1-1_all.deb ... | De-configuring node-core-js (3.8.2-2) ... | Unpacking node-core-js-builder (3.26.1-1) ... | dpkg: error processing archive ./node-core-js-builder_3.26.1-1_all.deb (--unpack): | trying to overwrite '/usr/share/nodejs/core-js-builder/config.js', which is also in package node-core-js 3.8.2-2 | Errors were encountered while processing: | ./node-core-js-builder_3.26.1-1_all.deb Please ensure that node-core-js-builder has sufficient Breaks and Replaces declarations. Helmut --- End Message --- --- Begin Message --- Source: node-core-js Source-Version: 3.26.1-2 Done: Yadd We believe that the bug you reported is fixed in the latest version of node-core-js, 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 1034...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Yadd (supplier of updated node-core-js 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: SHA512 Format: 1.8 Date: Fri, 28 Apr 2023 06:52:43 +0400 Source: node-core-js Architecture: source Version: 3.26.1-2 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Yadd Closes: 1034947 1034980 1034989 1035000 Changes: node-core-js (3.26.1-2) unstable; urgency=medium . * Team upload * Duplicate Breaks fields with Replaces (Closes: #1034980, #1034989, 1035000, #1034947) Checksums-Sha1: 63b76d3304a0f1c8971875ac85d636e86d0282cc 2447 node-core-js_3.26.1-2.dsc 547b85d0d69daa5ed40e05941b9f2ccdc425dfbb 8136 node-core-js_3.26.1-2.debian.tar.xz Checksums-Sha256: fcfbcb5f8cf91126529ba02c9777e4aa77e892540efd6e4627d021a511b65aa9 2447 node-core-js_3.26.1-2.dsc f695f686f142c712e3345b4f47be0512dc9b8b896e3d134fb770386dee151f59 8136 node-core-js_3.26.1-2.debian.tar.xz Files: be10841c312d4f8b14e54a7810288e8d 2447 javascript optional node-core-js_3.26.1-2.dsc e6aff033c0bfbe04fbccce8079957b2d 8136 javascript optional node-core-js_3.26.1-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAmRLN50ACgkQ9tdMp8mZ 7ukhjRAAk2EI89bCZwGKnT7lEgeplwbS5CO7wGqKCKRNQMAbpFlwhjDye5jqoEy8 vleJRpC4DenLuiv7tveewRbaW1ckLrAKSWb+k3Z3IdiLC4uoi/w/7SjHvZaDsb2J h+iGxQ+E4mEKup6zH2Ro2KXYJLJwkY7c5RBppDEdmYhFwZl8kNPM5O7jeJEBLQyq bKZTBruhdEku3SdVC04/zrwt9XBpJW7gz1vUOZhZ7evIKvVckjRGWbuSN4oCqe98 UcfEe+vLfH/YviEkQFcQxP9YYFKfE9kSgFEinSa+3Yt2O/xOGy5r/ExUrQoAUmOs f4dLTOhXu3OV3OWafoKSsUgMs0CBrByDgSbBFxRs3uCVeV+3sGpfJCt2MUMhGOmr F11uHD+MPsyPHjiFIyFZtYMvAs2ig1p3WVmJi8BsAzrodfiqBxwwBmrl7v5qI3Sx izIgC3ulzzwa2DlpqbuJsLh5u3+0BxLoUwVIx2w3J/k8nmEDYYMGpulod4oDgzho 9VF38VcJIQQuCPKl59TUT0ab9XizqCHAOGycmMuODHyHjB0lQokQ7vZ8PJ4p9fha aOODVxpMPJClLGCHlKIjRInkqtCPUETfR3Z+5PqiycduDF6Ps5QPNF9P0Ii+uR+t LMWH9mktuKLE2H8pU5ItjkkBXf6JESdT5nfeuwSHoHQr7EetY9E= =/GQk -END PGP SIGNATURE End Message ---
Bug#1034947: marked as done (node-core-js-compat: missing Breaks+Replaces for node-core-js when upgrading from bullseye)
Your message dated Fri, 28 Apr 2023 03:19:08 + with message-id and subject line Bug#1034947: fixed in node-core-js 3.26.1-2 has caused the Debian Bug report #1034947, regarding node-core-js-compat: missing Breaks+Replaces for node-core-js when upgrading from bullseye 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.) -- 1034947: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034947 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: node-core-js-compat Version: 3.26.1-1 Severity: serious Justification: dpkg unpack error Attempting to unpack node-core-js-compat/3.26.1-1 from Debian bookworm on a minimal Debian bullseye with node-core-js/3.8.2-2 installed, causes an unpack error from dpkg due to /usr/share/nodejs/core-js-compat/compat.js being contained in both packages. | Selecting previously unselected package node-core-js-compat. | dpkg: considering deconfiguration of node-core-js, which would be broken by installation of node-core-js-compat ... | dpkg: yes, will deconfigure node-core-js (broken by node-core-js-compat) | (Reading database ... 7666 files and directories currently installed.) | Preparing to unpack .../node-core-js-compat_3.26.1-1_all.deb ... | De-configuring node-core-js (3.8.2-2) ... | Unpacking node-core-js-compat (3.26.1-1) ... | dpkg: error processing archive ./node-core-js-compat_3.26.1-1_all.deb (--unpack): | trying to overwrite '/usr/share/nodejs/core-js-compat/compat.js', which is also in package node-core-js 3.8.2-2 | Errors were encountered while processing: | ./node-core-js-compat_3.26.1-1_all.deb Please ensure that node-core-js-compat has sufficient Breaks and Replaces declarations. Helmut --- End Message --- --- Begin Message --- Source: node-core-js Source-Version: 3.26.1-2 Done: Yadd We believe that the bug you reported is fixed in the latest version of node-core-js, 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 1034...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Yadd (supplier of updated node-core-js 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: SHA512 Format: 1.8 Date: Fri, 28 Apr 2023 06:52:43 +0400 Source: node-core-js Architecture: source Version: 3.26.1-2 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Yadd Closes: 1034947 1034980 1034989 1035000 Changes: node-core-js (3.26.1-2) unstable; urgency=medium . * Team upload * Duplicate Breaks fields with Replaces (Closes: #1034980, #1034989, 1035000, #1034947) Checksums-Sha1: 63b76d3304a0f1c8971875ac85d636e86d0282cc 2447 node-core-js_3.26.1-2.dsc 547b85d0d69daa5ed40e05941b9f2ccdc425dfbb 8136 node-core-js_3.26.1-2.debian.tar.xz Checksums-Sha256: fcfbcb5f8cf91126529ba02c9777e4aa77e892540efd6e4627d021a511b65aa9 2447 node-core-js_3.26.1-2.dsc f695f686f142c712e3345b4f47be0512dc9b8b896e3d134fb770386dee151f59 8136 node-core-js_3.26.1-2.debian.tar.xz Files: be10841c312d4f8b14e54a7810288e8d 2447 javascript optional node-core-js_3.26.1-2.dsc e6aff033c0bfbe04fbccce8079957b2d 8136 javascript optional node-core-js_3.26.1-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAmRLN50ACgkQ9tdMp8mZ 7ukhjRAAk2EI89bCZwGKnT7lEgeplwbS5CO7wGqKCKRNQMAbpFlwhjDye5jqoEy8 vleJRpC4DenLuiv7tveewRbaW1ckLrAKSWb+k3Z3IdiLC4uoi/w/7SjHvZaDsb2J h+iGxQ+E4mEKup6zH2Ro2KXYJLJwkY7c5RBppDEdmYhFwZl8kNPM5O7jeJEBLQyq bKZTBruhdEku3SdVC04/zrwt9XBpJW7gz1vUOZhZ7evIKvVckjRGWbuSN4oCqe98 UcfEe+vLfH/YviEkQFcQxP9YYFKfE9kSgFEinSa+3Yt2O/xOGy5r/ExUrQoAUmOs f4dLTOhXu3OV3OWafoKSsUgMs0CBrByDgSbBFxRs3uCVeV+3sGpfJCt2MUMhGOmr F11uHD+MPsyPHjiFIyFZtYMvAs2ig1p3WVmJi8BsAzrodfiqBxwwBmrl7v5qI3Sx izIgC3ulzzwa2DlpqbuJsLh5u3+0BxLoUwVIx2w3J/k8nmEDYYMGpulod4oDgzho 9VF38VcJIQQuCPKl59TUT0ab9XizqCHAOGycmMuODHyHjB0lQokQ7vZ8PJ4p9fha aOODVxpMPJClLGCHlKIjRInkqtCPUETfR3Z+5PqiycduDF6Ps5QPNF9P0Ii+uR+t LMWH9mktuKLE2H8pU5ItjkkBXf6JESdT5nfeuwSHoHQr7EetY9E= =/GQk -END PGP SIGNATURE End Message ---
Bug#1034924: marked as done (node-strip-eof: missing Breaks+Replaces for node-execa when upgrading from bullseye)
Your message dated Fri, 28 Apr 2023 03:20:09 + with message-id and subject line Bug#1034924: fixed in node-strip-eof 3.0.0-5 has caused the Debian Bug report #1034924, regarding node-strip-eof: missing Breaks+Replaces for node-execa when upgrading from bullseye 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.) -- 1034924: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034924 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: node-strip-eof Version: 3.0.0-4 Severity: serious Justification: dpkg unpack error Attempting to unpack node-strip-eof/3.0.0-4 from Debian bookworm on a minimal Debian bullseye with node-execa/4.1.0+dfsg+~cs19.3.6-5 installed, causes an unpack error from dpkg due to /usr/share/nodejs/strip-final-newline/index.js being contained in both packages. | Selecting previously unselected package node-strip-eof. | dpkg: considering deconfiguration of node-execa, which would be broken by installation of node-strip-eof ... | dpkg: yes, will deconfigure node-execa (broken by node-strip-eof) | (Reading database ... 4965 files and directories currently installed.) | Preparing to unpack .../node-strip-eof_3.0.0-4_all.deb ... | De-configuring node-execa (4.1.0+dfsg+~cs19.3.6-5) ... | Unpacking node-strip-eof (3.0.0-4) ... | dpkg: error processing archive ./node-strip-eof_3.0.0-4_all.deb (--unpack): | trying to overwrite '/usr/share/nodejs/strip-final-newline/index.js', which is also in package node-execa 4.1.0+dfsg+~cs19.3.6-5 | Errors were encountered while processing: | ./node-strip-eof_3.0.0-4_all.deb Please ensure that node-strip-eof has sufficient Breaks and Replaces declarations. Helmut --- End Message --- --- Begin Message --- Source: node-strip-eof Source-Version: 3.0.0-5 Done: Yadd We believe that the bug you reported is fixed in the latest version of node-strip-eof, 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 1034...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Yadd (supplier of updated node-strip-eof 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: SHA512 Format: 1.8 Date: Fri, 28 Apr 2023 06:54:14 +0400 Source: node-strip-eof Architecture: source Version: 3.0.0-5 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Yadd Closes: 1034924 Changes: node-strip-eof (3.0.0-5) unstable; urgency=medium . * Team upload * Duplicate Breaks field with Replaces (Closes: #1034924) Checksums-Sha1: 0656e674863da72eb9f0e2509049ce34597d17d4 2070 node-strip-eof_3.0.0-5.dsc a7fcf949454ef30b092bb660c4f2b43df8ac2a84 4036 node-strip-eof_3.0.0-5.debian.tar.xz Checksums-Sha256: e3cc5eb59188d841781f206103e3cf285c4b097eb55d4a1f6a56ae8d2c070071 2070 node-strip-eof_3.0.0-5.dsc 8a3e217224d58106a5f89990cf4d7efb8cb42053df98afde9344ed55aa50cd65 4036 node-strip-eof_3.0.0-5.debian.tar.xz Files: dad4af7065b42bf84d02181bde800499 2070 javascript optional node-strip-eof_3.0.0-5.dsc 89a78bc54d097069bee46cfc1393d59b 4036 javascript optional node-strip-eof_3.0.0-5.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAmRLN7IACgkQ9tdMp8mZ 7ul+yg/+NeC2tBF/tWxCBShahwBgvXFD/vy8G3pYoDwbimfUTl8UJg4sbCnl2B8H WkHzOCtL2i2zZHLpucUqrlIbeNYy5BcYpk/2NJrDx44lpZJBDDM5gd42kE4Bq/cS Ki/gqRfAjkSyKb6qTsVWmdVKoJECJlQIVgrnm5p1Azqe5lgykd1tXmZAQTNjc96n qO2uawbnQl3RXXCGUGt+Q7NDaCTOY7vP0KTOJAzMv+WIR6NS5Ol3URnEmn6Z+RuC didzAxJDqpW4izYnnR2pnJ8x6m6UBBqrTRVeST11N6o+3hbh6uktLv49K7ivvn/e UOFpH8NxPTmNWwPxI8Aa1j9L4cdq16/nJi1mQbJDKi5RSATeSpXn00UTMsppLCEz NOtfaGomb3LPRaBwlmWdyhjQe2eZixMOyb/ibkVSSIJ1yWEWFQTNTataMU8yqgU2 NmqVvfnIvOCWMnKvcJs0gXsgaTo3AVLInTgVCZsFGsSwMYPBQKRU9VrKAAI3D44A ljfbOiMjsupsT0mYsIue9H6r27qqAh4klV2FPZ/+xspFFaO0/bH9f0Zp4FRJRVFZ y3OfHnGyMJPw37S5Q/3i2ZpJ45i/KP4DFwrtGTRGhMdMY1m0ejz1FkbjhKBFsItr 8MYT7WQhnaNBXwC0C/hi31p+ryZx/xRqAKS90JQaVhH75JRuCV0= =tyTJ -END PGP SIGNATURE End Message ---
Processed: Bug#1035008 marked as pending in node-jest
Processing control commands: > tag -1 pending Bug #1035008 [node-jest-worker] node-jest-worker: missing Breaks+Replaces for jest when upgrading from bullseye Added tag(s) pending. -- 1035008: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035008 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#1034989 marked as pending in node-core-js
Processing control commands: > tag -1 pending Bug #1034989 [node-core-js-bundle] node-core-js-bundle: missing Breaks+Replaces for node-core-js when upgrading from bullseye Added tag(s) pending. -- 1034989: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034989 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1035008: marked as pending in node-jest
Control: tag -1 pending Hello, Bug #1035008 in node-jest reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/node-jest/-/commit/f559936253cee8312557e7fe40093621254e1b58 Duplicate Breaks field with Replaces Closes: #1035008 (this message was generated automatically) -- Greetings https://bugs.debian.org/1035008
Bug#1034924: marked as pending in node-strip-eof
Control: tag -1 pending Hello, Bug #1034924 in node-strip-eof reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/node-strip-eof/-/commit/ee904a276308d05dcc32ec5502f021c5e64522d1 Duplicate Breaks field with Replaces Closes: #1034924 (this message was generated automatically) -- Greetings https://bugs.debian.org/1034924
Processed: Bug#1034924 marked as pending in node-strip-eof
Processing control commands: > tag -1 pending Bug #1034924 [node-strip-eof] node-strip-eof: missing Breaks+Replaces for node-execa when upgrading from bullseye Added tag(s) pending. -- 1034924: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034924 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1034989: marked as pending in node-core-js
Control: tag -1 pending Hello, Bug #1034989 in node-core-js reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/node-core-js/-/commit/4717dd936100e0e839258a9cb2b2242ef26ac893 Duplicate Breaks fields with Replaces Closes: #1034980, #1034989, 1035000, #1034947 (this message was generated automatically) -- Greetings https://bugs.debian.org/1034989
Bug#1034971: lxd-client: missing Breaks+Replaces for lxc when upgrading from bullseye
Hi Helmut, On Thu, 27 Apr 2023 15:00:05 +0200 Helmut Grohne wrote: > Attempting to unpack lxd-client/5.0.2-3+b2 from Debian bookworm > on a minimal Debian bullseye with lxc/1:4.0.6-2+deb11u1 > installed, causes an unpack error from dpkg due to > /usr/share/bash-completion/completions/lxc being contained in both packages. It looks like you're trying to install the version of lxd from testing on a bullseye system? Mixing packages from different releases isn't supported [1]. Furthermore, there hasn't yet been a stable release of Debian that shipped lxd, so there's no way lxd-client might be upgraded before lxc when upgrading from bullseye to bookworm. As such, I don't know if it's really worthwhile to try to address this situation that would only occur when the end-user has already broken key assumptions about how their system is configured. The packaging of lxc was updated during the bookworm development cycle to properly name its bash completion file and de-conflict with lxd packaging [2]. Upgrading lxc packages from bullseye -> bookworm should work smoothly; after the upgrade is complete users will then also be able to `apt install lxd` if they so wish, and they won't encounter the packaging conflict. > Please ensure that lxd-client has sufficient Breaks and Replaces declarations. Does that address your concern? Mathias [1] -- https://wiki.debian.org/DontBreakDebian [2] -- https://bugs.debian.org/1010843 signature.asc Description: This is a digitally signed message part
Bug#1034939: librust---dev: missing Breaks+Replaces for librust-mio-dev when upgrading from bullseye
Summarising a number of bug reports by Helmut Ghrone: Please ensure that librust---dev has sufficient Breaks and Replaces declarations. The issue specifically appears to be that the breaks+replaces are declared against a virtual package, it seems dpkg is honoring the breaks against the virtual package but not the replaces. So it correctly marks the package from stable as broken, but fails to actually unpack the package from testing. Declaring against the physical package is also problematic becase Debian package relationships don't support version ranges. What this would likely mean in practice is it would be possible to co-install the "current" semver alongside one previous semver, but it would not be possible to co-install two different previous semvers. Another option may be to use "Conflicts" instead of "Breaks". This should force the old package to be upgraded or removed before the semver-specific package can be unpacked. I feel the timing of these bugs is very unfortunate. I don't object to people running QA checks, but it's generally easier to deal with bugs if they are reported earlier in the freeze process. The timing of these bugs leaves little time for discussion if we are to get the fixes in before the full freeze. As I see it we have a few options to deal with this for bookworm. 1. Make debcargo Use Conflicts instead of Breaks. 2. Make debcargo declare Breaks/Replaces against the physical package version using a << dependency. This will allow the non-semver suffixed package to be installed alongside one semver-suffixed package, but with our current virtual packages scheme would not allow two semver-suffixed packages of the same crate to be coinstalled. 3. Add manual breaks/replaces for the versions in bullseye, this will paper over the issue for bullseye-bookworm upgrades, but is not a long term fix. Do any other members of the rust team have an opinion on this? I'm personally inclined towards option 1 and intend to implement it if noone objects in the next couple of days. Do the release team have an opinion on this? It looks like only one of the packages involved (rust-env-logger-0.7) is a key package.
Bug#1034923: marked as done (libdtkcommon-dev: missing Breaks+Replaces for libdtkcore-dev when upgrading from bullseye)
Your message dated Thu, 27 Apr 2023 23:33:47 + with message-id and subject line Bug#1034923: fixed in dtkcommon 5.5.23-2 has caused the Debian Bug report #1034923, regarding libdtkcommon-dev: missing Breaks+Replaces for libdtkcore-dev when upgrading from bullseye 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.) -- 1034923: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034923 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libdtkcommon-dev Version: 5.5.23-1 Severity: serious Justification: dpkg unpack error Attempting to unpack libdtkcommon-dev/5.5.23-1 from Debian bookworm on a minimal Debian bullseye with libdtkcore-dev/5.2.2.5-3 installed, causes an unpack error from dpkg due to /usr/lib/x86_64-linux-gnu/qt5/mkspecs/features/dtk_build.prf being contained in both packages. | Selecting previously unselected package libdtkcommon-dev. | dpkg: considering deconfiguration of libdtkcore-dev:amd64, which would be broken by installation of libdtkcommon-dev ... | dpkg: yes, will deconfigure libdtkcore-dev:amd64 (broken by libdtkcommon-dev) | (Reading database ... 6007 files and directories currently installed.) | Preparing to unpack .../libdtkcommon-dev_5.5.23-1_amd64.deb ... | De-configuring libdtkcore-dev:amd64 (5.2.2.5-3) ... | Unpacking libdtkcommon-dev (5.5.23-1) ... | dpkg: error processing archive ./libdtkcommon-dev_5.5.23-1_amd64.deb (--unpack): | trying to overwrite '/usr/lib/x86_64-linux-gnu/qt5/mkspecs/features/dtk_build.prf', which is also in package libdtkcore-dev:amd64 5.2.2.5-3 | Errors were encountered while processing: | ./libdtkcommon-dev_5.5.23-1_amd64.deb Please ensure that libdtkcommon-dev has sufficient Breaks and Replaces declarations. Helmut --- End Message --- --- Begin Message --- Source: dtkcommon Source-Version: 5.5.23-2 Done: Boyuan Yang We believe that the bug you reported is fixed in the latest version of dtkcommon, 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 1034...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Boyuan Yang (supplier of updated dtkcommon 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: SHA512 Format: 1.8 Date: Thu, 27 Apr 2023 19:12:02 -0400 Source: dtkcommon Architecture: source Version: 5.5.23-2 Distribution: unstable Urgency: high Maintainer: Debian Deepin Packaging Team Changed-By: Boyuan Yang Closes: 1034923 1034997 Changes: dtkcommon (5.5.23-2) unstable; urgency=high . * Team upload. * debian/control: Add missing Replaces: relationship: + libdtkcommon to libdtkcore5 (<< 5.4.10), libdtkgui5 (<< 5.4.10) + libdtkcommon-dev to libdtkcore-dev (<< 5.4.10) (Closes: #1034923, #1034997) Checksums-Sha1: 76bef30f16e4bff974bcc75f0364db9d80f28430 2090 dtkcommon_5.5.23-2.dsc cafe7e022af4d415c22ecaea0fbfd173ffbc8e7d 26057 dtkcommon_5.5.23.orig.tar.gz 38cc5825d259b5dbf7fc67e196c635ecb93c3904 2608 dtkcommon_5.5.23-2.debian.tar.xz 6fe76fc860686b527bef28743e34aa9e1c402467 12171 dtkcommon_5.5.23-2_amd64.buildinfo Checksums-Sha256: 3e962d43ba6263f174853cd173a383f8c01c3b05ea0a1e7c3cdb58b2f357 2090 dtkcommon_5.5.23-2.dsc 2393139e8712b0d82c04cc3eaff7bd6ad48aa87bba0d7ee5dd34edd6e49a5285 26057 dtkcommon_5.5.23.orig.tar.gz 2287e83f5d423ea2d4b79a09901e51052254d0f3fee43f777f1457575e5422b8 2608 dtkcommon_5.5.23-2.debian.tar.xz a8b2430a8d3241a98bca8ca120f7f50412f03d7c7b86b7515f3d2722d815 12171 dtkcommon_5.5.23-2_amd64.buildinfo Files: 2b07ddb8b1bc11090781e6eb055cf95a 2090 libdevel optional dtkcommon_5.5.23-2.dsc 204827cf1699935f8fab06586cc0a231 26057 libdevel optional dtkcommon_5.5.23.orig.tar.gz 4c60d5523a4afbd3fcd11ad55fda897d 2608 libdevel optional dtkcommon_5.5.23-2.debian.tar.xz 5aed8edbbd7cd8e616475077c721bb2b 12171 libdevel optional dtkcommon_5.5.23-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAmRLAjkACgkQwpPntGGC Ws5plA//cczo/LEJKoYGIr80a8nMNK2WrbUq46I3N5dpoLy4xFshNxRqvgHlKVbT ButJr8FOFGJ/RP2SRNXWQJWB4PHEjMPsfQV1EgaOGOpwn5jO3oXKowy8pMVr5z5A nAYOsopNBge1UwD8iiLnZ30wvkT0co3F5N0XPCfTNb6+gjQK7IzmUmWlwzXZDzTK
Bug#1034997: marked as done (libdtkcommon: missing Breaks+Replaces for libdtkcore5 when upgrading from bullseye)
Your message dated Thu, 27 Apr 2023 23:33:47 + with message-id and subject line Bug#1034997: fixed in dtkcommon 5.5.23-2 has caused the Debian Bug report #1034997, regarding libdtkcommon: missing Breaks+Replaces for libdtkcore5 when upgrading from bullseye 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.) -- 1034997: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034997 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libdtkcommon Version: 5.5.23-1 Severity: serious Justification: dpkg unpack error Attempting to unpack libdtkcommon/5.5.23-1 from Debian bookworm on a minimal Debian bullseye with libdtkcore5/5.2.2.5-3 installed, causes an unpack error from dpkg due to /usr/share/glib-2.0/schemas/com.deepin.dtk.gschema.xml being contained in both packages. | Selecting previously unselected package libdtkcommon. | dpkg: considering deconfiguration of libdtkcore5:amd64, which would be broken by installation of libdtkcommon ... | dpkg: yes, will deconfigure libdtkcore5:amd64 (broken by libdtkcommon) | (Reading database ... 5903 files and directories currently installed.) | Preparing to unpack .../libdtkcommon_5.5.23-1_amd64.deb ... | De-configuring libdtkcore5:amd64 (5.2.2.5-3) ... | Unpacking libdtkcommon (5.5.23-1) ... | dpkg: error processing archive ./libdtkcommon_5.5.23-1_amd64.deb (--unpack): | trying to overwrite '/usr/share/glib-2.0/schemas/com.deepin.dtk.gschema.xml', which is also in package libdtkcore5:amd64 5.2.2.5-3 | Processing triggers for libc-bin (2.31-13+deb11u5) ... | Processing triggers for libglib2.0-0:amd64 (2.66.8-1) ... | Errors were encountered while processing: | ./libdtkcommon_5.5.23-1_amd64.deb Please ensure that libdtkcommon has sufficient Breaks and Replaces declarations. Helmut --- End Message --- --- Begin Message --- Source: dtkcommon Source-Version: 5.5.23-2 Done: Boyuan Yang We believe that the bug you reported is fixed in the latest version of dtkcommon, 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 1034...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Boyuan Yang (supplier of updated dtkcommon 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: SHA512 Format: 1.8 Date: Thu, 27 Apr 2023 19:12:02 -0400 Source: dtkcommon Architecture: source Version: 5.5.23-2 Distribution: unstable Urgency: high Maintainer: Debian Deepin Packaging Team Changed-By: Boyuan Yang Closes: 1034923 1034997 Changes: dtkcommon (5.5.23-2) unstable; urgency=high . * Team upload. * debian/control: Add missing Replaces: relationship: + libdtkcommon to libdtkcore5 (<< 5.4.10), libdtkgui5 (<< 5.4.10) + libdtkcommon-dev to libdtkcore-dev (<< 5.4.10) (Closes: #1034923, #1034997) Checksums-Sha1: 76bef30f16e4bff974bcc75f0364db9d80f28430 2090 dtkcommon_5.5.23-2.dsc cafe7e022af4d415c22ecaea0fbfd173ffbc8e7d 26057 dtkcommon_5.5.23.orig.tar.gz 38cc5825d259b5dbf7fc67e196c635ecb93c3904 2608 dtkcommon_5.5.23-2.debian.tar.xz 6fe76fc860686b527bef28743e34aa9e1c402467 12171 dtkcommon_5.5.23-2_amd64.buildinfo Checksums-Sha256: 3e962d43ba6263f174853cd173a383f8c01c3b05ea0a1e7c3cdb58b2f357 2090 dtkcommon_5.5.23-2.dsc 2393139e8712b0d82c04cc3eaff7bd6ad48aa87bba0d7ee5dd34edd6e49a5285 26057 dtkcommon_5.5.23.orig.tar.gz 2287e83f5d423ea2d4b79a09901e51052254d0f3fee43f777f1457575e5422b8 2608 dtkcommon_5.5.23-2.debian.tar.xz a8b2430a8d3241a98bca8ca120f7f50412f03d7c7b86b7515f3d2722d815 12171 dtkcommon_5.5.23-2_amd64.buildinfo Files: 2b07ddb8b1bc11090781e6eb055cf95a 2090 libdevel optional dtkcommon_5.5.23-2.dsc 204827cf1699935f8fab06586cc0a231 26057 libdevel optional dtkcommon_5.5.23.orig.tar.gz 4c60d5523a4afbd3fcd11ad55fda897d 2608 libdevel optional dtkcommon_5.5.23-2.debian.tar.xz 5aed8edbbd7cd8e616475077c721bb2b 12171 libdevel optional dtkcommon_5.5.23-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAmRLAjkACgkQwpPntGGC Ws5plA//cczo/LEJKoYGIr80a8nMNK2WrbUq46I3N5dpoLy4xFshNxRqvgHlKVbT ButJr8FOFGJ/RP2SRNXWQJWB4PHEjMPsfQV1EgaOGOpwn5jO3oXKowy8pMVr5z5A nAYOsopNBge1UwD8iiLnZ30wvkT0co3F5N0XPCfTNb6+gjQK7IzmUmWlwzXZDzTK
Bug#1034228: marked as done (zcfan: dh_installsystemd doesn't handle files in /usr/lib/systemd/system)
Your message dated Thu, 27 Apr 2023 22:19:41 + with message-id and subject line Bug#1034228: fixed in zcfan 1.2.1-2 has caused the Debian Bug report #1034228, regarding zcfan: dh_installsystemd doesn't handle files in /usr/lib/systemd/system 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.) -- 1034228: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034228 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: zcfan Version: 1.2.1-1 Severity: serious Tags: sid bookworm User: debhel...@packages.debian.org Usertags: systemd-files-in-usr-bookworm Dear Maintainer, It seems that your package zcfan is shipping files (.service, .socket or .timer) in /usr/lib/systemd/system. This is not supported by the version of dh_installsystemd/debhelper currently in unstable and bookworm (See: #1031695). That means that currently your service might not be enabled at boot and/or started as expected. With the freeze currently in effect, debhelper will not be fixed for bookworm. As a result, could you please move these files to /lib/systemd/system instead so they are properly detected by debhelper? As soon as debhelper is supporting (not until bookworm+1 aka Trixie) you will be able to move them back to the newer location. Note that bookworm is currently in hard freeze, please limit the changes you are uploading to the ones fixing RC bugs. Also note that you might have to request a freeze exception to the release team. See: https://release.debian.org/testing/freeze_policy.html Feel free to contact me if you have any questions. Kind regards, Laurent Bigonville The list of packages has been generated with the following command: apt-file search -x '^/usr/lib/systemd/system/.*\.(service|timer|socket)$'|cut -d: -f1|sort -u --- End Message --- --- Begin Message --- Source: zcfan Source-Version: 1.2.1-2 Done: Michel Alexandre Salim We believe that the bug you reported is fixed in the latest version of zcfan, 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 1034...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michel Alexandre Salim (supplier of updated zcfan 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: Thu, 27 Apr 2023 16:52:29 -0500 Source: zcfan Architecture: source Version: 1.2.1-2 Distribution: unstable Urgency: medium Maintainer: Michel Alexandre Salim Changed-By: Michel Alexandre Salim Closes: 1017980 1032418 1034228 Changes: zcfan (1.2.1-2) unstable; urgency=medium . * Mark as conflicting with thinkfan (Closes: #1017980) * Update Standards-Version to 4.6.2 * Don't enable by default, like thinkfan (Closes: #1032418) * Workaround for dh_installsystemd (Closes: #1034228) Checksums-Sha1: 012ddac3d34f0685e7ceb5a7494f828b5936f175 1234 zcfan_1.2.1-2.dsc 0563cefe087ba808ba2239ccbe71b2e314d59192 6140 zcfan_1.2.1.orig.tar.gz 6dfa54ed93d0049306470061489887e942e8b976 3284 zcfan_1.2.1-2.debian.tar.xz e48e06a3321c83c470cd4d89e109e4d66a62a3c6 4898 zcfan_1.2.1-2_source.buildinfo Checksums-Sha256: e1b11b44b9655b8deb15ffc2a68e2607d5d83c732ce79d6db395c7e046498362 1234 zcfan_1.2.1-2.dsc c42de1357d970381bb7898c82e0adfe067200c98842c78d36c2c5679fbbe50c8 6140 zcfan_1.2.1.orig.tar.gz dbbf86293730caac8d186dcb165dc40aaeb6b2de3610f914eca61e3fbc6f4989 3284 zcfan_1.2.1-2.debian.tar.xz 6c890161f211548c294d691c5989ca50b2871c8f6bb5af34c6e312690c4833c1 4898 zcfan_1.2.1-2_source.buildinfo Files: 1cd518dba7b6ac6a678febeedd3599d2 1234 utils optional zcfan_1.2.1-2.dsc eef4f7f6d24317a8ecd211e2c80e033c 6140 utils optional zcfan_1.2.1.orig.tar.gz 88118555c4ee3a6be451ba15733bcd78 3284 utils optional zcfan_1.2.1-2.debian.tar.xz 3621b224c1fc1e07916948d76509dff9 4898 utils optional zcfan_1.2.1-2_source.buildinfo -BEGIN PGP SIGNATURE- iHUEARYIAB0WIQRdzi5+nDsc/9M1wdeLIp0vfMwE8gUCZErupwAKCRCLIp0vfMwE 8m9sAQDTCChXdOVFr0NBtrKKK9vTHWC20rRDWoUfISNkpNHGtAEAiXm10Jh6x6gN zms6aSg1sM8XAKrKCv+AalJJX5I0oQc= =HRt/ -END PGP SIGNATURE End Message ---
Bug#1035008: [Pkg-javascript-devel] Bug#1035008: node-jest-worker: missing Breaks+Replaces for jest when upgrading from bullseye
On Thu, Apr 27, 2023 at 10:03:00PM +0400, Yadd wrote: > node-jest-worker has already > > Breaks: jest (<< 29.1.2~ds1+~cs70.47.21-1~) > > how it is possible to have this issue ? Breaks prevents both packages from being configured concurrently, so installing node-jest-worker will cause jest to be deconfigured (and later removed). However the packages can still be unpacked concurrently. To avoid concurrent unpacks, one can use Conflicts instead of Breaks, but this makes upgrades more difficult for apt. Instead, you should add Replaces: jest (<< ...) to tell apt that during such a concurrent unpack, node-jest-worker is allowed to "steal" files from jest. This is detailed in policy section 7.6. Hope it helps. Helmut
Bug#1035008: [Pkg-javascript-devel] Bug#1035008: node-jest-worker: missing Breaks+Replaces for jest when upgrading from bullseye
On 4/27/23 16:59, Helmut Grohne wrote: Package: node-jest-worker Version: 29.3.1~ds1+~cs70.48.25-1 Severity: serious Justification: dpkg unpack error Attempting to unpack node-jest-worker/29.3.1~ds1+~cs70.48.25-1 from Debian bookworm on a minimal Debian bullseye with jest/26.6.3+repack+~cs64.44.39-3 installed, causes an unpack error from dpkg due to /usr/share/nodejs/@jest/types/build/Circus.d.ts being contained in both packages. | dpkg: considering deconfiguration of jest, which would be broken by installation of node-jest-worker ... | dpkg: yes, will deconfigure jest (broken by node-jest-worker) | (Reading database ... 21294 files and directories currently installed.) | Preparing to unpack .../node-jest-worker_29.3.1~ds1+~cs70.48.25-1_all.deb ... | De-configuring jest (26.6.3+repack+~cs64.44.39-3) ... | Unpacking node-jest-worker (29.3.1~ds1+~cs70.48.25-1) over (26.6.3+repack+~cs64.44.39-3) ... | dpkg: error processing archive ./node-jest-worker_29.3.1~ds1+~cs70.48.25-1_all.deb (--unpack): | trying to overwrite '/usr/share/nodejs/@jest/types/build/Circus.d.ts', which is also in package jest 26.6.3+repack+~cs64.44.39-3 | Errors were encountered while processing: | ./node-jest-worker_29.3.1~ds1+~cs70.48.25-1_all.deb Please ensure that node-jest-worker has sufficient Breaks and Replaces declarations. Helmut Hi, node-jest-worker has already Breaks: jest (<< 29.1.2~ds1+~cs70.47.21-1~) how it is possible to have this issue ?
Bug#1034957: marked as done (qtxdg-tools: missing Breaks+Replaces for qtxdg-dev-tools when upgrading from bullseye)
Your message dated Thu, 27 Apr 2023 16:37:31 + with message-id and subject line Bug#1034957: fixed in qtxdg-tools 3.10.0-2 has caused the Debian Bug report #1034957, regarding qtxdg-tools: missing Breaks+Replaces for qtxdg-dev-tools when upgrading from bullseye 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.) -- 1034957: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034957 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: qtxdg-tools Version: 3.10.0-1 Severity: serious Justification: dpkg unpack error Attempting to unpack qtxdg-tools/3.10.0-1 from Debian bookworm on a minimal Debian bullseye with qtxdg-dev-tools/3.6.0-1 installed, causes an unpack error from dpkg due to /usr/bin/qtxdg-mat being contained in both packages. | Selecting previously unselected package qtxdg-tools. | (Reading database ... 9080 files and directories currently installed.) | Preparing to unpack .../qtxdg-tools_3.10.0-1_amd64.deb ... | Unpacking qtxdg-tools (3.10.0-1) ... | dpkg: error processing archive ./qtxdg-tools_3.10.0-1_amd64.deb (--unpack): | trying to overwrite '/usr/bin/qtxdg-mat', which is also in package qtxdg-dev-tools 3.6.0-1 | Errors were encountered while processing: | ./qtxdg-tools_3.10.0-1_amd64.deb Please ensure that qtxdg-tools has sufficient Breaks and Replaces declarations. Helmut --- End Message --- --- Begin Message --- Source: qtxdg-tools Source-Version: 3.10.0-2 Done: ChangZhuo Chen (陳昌倬) We believe that the bug you reported is fixed in the latest version of qtxdg-tools, 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 1034...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. ChangZhuo Chen (陳昌倬) (supplier of updated qtxdg-tools 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: SHA512 Format: 1.8 Date: Fri, 28 Apr 2023 00:10:21 +0800 Source: qtxdg-tools Architecture: source Version: 3.10.0-2 Distribution: unstable Urgency: medium Maintainer: LXQt Packaging Team Changed-By: ChangZhuo Chen (陳昌倬) Closes: 1034957 Changes: qtxdg-tools (3.10.0-2) unstable; urgency=medium . * Add missing Breaks/Replaces (Closes: #1034957) Checksums-Sha1: 09ade98a9854dd623d2e68fd752262f2b470faa8 2387 qtxdg-tools_3.10.0-2.dsc b40fb091d4e95fb2761311e10a13d1ff3c0a9baa 5612 qtxdg-tools_3.10.0-2.debian.tar.xz 34c958bde7ed262a068d5ad638286bee7b509885 12591 qtxdg-tools_3.10.0-2_amd64.buildinfo Checksums-Sha256: 8385509cb7f669e9a7a9cd375091bd92dbdfb74d251feb5ba5cddb2840ccdef9 2387 qtxdg-tools_3.10.0-2.dsc 354c6144b10f1eb3737a4103202f707da8bb76f36f918fc1cf26edf2cc079edd 5612 qtxdg-tools_3.10.0-2.debian.tar.xz bd94b1486f6e0cb5ebc369ed8b0236fe33e46aefa5e3614bd266d68927f500a0 12591 qtxdg-tools_3.10.0-2_amd64.buildinfo Files: fc7abd2e81ac63e6c138d55281ef19fc 2387 libs optional qtxdg-tools_3.10.0-2.dsc 7bc42e0730caa0931c9932827787fbf9 5612 libs optional qtxdg-tools_3.10.0-2.debian.tar.xz cafea9de67b195735554ca367badf8ac 12591 libs optional qtxdg-tools_3.10.0-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEugQ0bcLh/mPHkIeTzGWwzewnXVsFAmRKnvsACgkQzGWwzewn XVtrcxAAugoKQwqZThVOsGHwLP3dhcYU3tN3fj1fK254+cxz9O44zEcKmEEAwlua scnt2ZpueJ84W5MTE43D+xnNP8pM8hAxuhm/FmiEpk5E4B4MD3IeFr90UCnpW2Rc 8iu86OD4ndKZuSkvz/oKQJfpPfbLoNoybgcZBUfPeWcaf5MciKS6htkkF1H3XaNx 58R46drY/TDqqwZ4IFCCjBazdCpwNmCUeq40V/dXv38asLKgi7zp/ykFbYvgkDqq sq06tpmf+/FppQ3EhaSC0ysKbDXTLOf30ETqLucdijt+7MWVaDXKae/d1yPcrxFF h3NuKN32EjGQ6j2M4evecCy6TU09Zpnv5jrihZxinkG67YDvmQEZfEMK91URKhE0 3BJSI9MKXG0g7c4iTLAG7I7wiJFsVaqFdGG2VwcurZDsKkIP49i3UNtpCfIkf2GX 1spusY06wZ9SF3m1AGAWN2s87+xqbpXBOYO0DH486GLVXfy4AcbUoTEUIz8One9K 1RJp7+O40s60J8v6xkFFQMfZ6W4/e924lNPlJCHtb5OSk56s87QpTW6qhEiW5FzP /7n1mlv8IZuEvzcVrMvSOk8kN+GK6wIUBjhp4xjvFc/iCWZt17fzLrRLlNlPwhad G0gajZViCXYYSYgJYbwUEXPhPZ7G8ioG0xwACOo5VhUlBeni0xc= =2Y3q -END PGP SIGNATURE End Message ---
Bug#1034962: marked as done (libg2c-dev: missing Breaks+Replaces for libgrib2c-dev when upgrading from bullseye)
Your message dated Thu, 27 Apr 2023 15:49:07 + with message-id and subject line Bug#1034962: fixed in g2clib 1.7.0-3 has caused the Debian Bug report #1034962, regarding libg2c-dev: missing Breaks+Replaces for libgrib2c-dev when upgrading from bullseye 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.) -- 1034962: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034962 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libg2c-dev Version: 1.7.0-2 Severity: serious Justification: dpkg unpack error Attempting to unpack libg2c-dev/1.7.0-2 from Debian bookworm on a minimal Debian bullseye with libgrib2c-dev/1.6.2-2 installed, causes an unpack error from dpkg due to /usr/include/grib2.h being contained in both packages. | Selecting previously unselected package libg2c-dev:amd64. | dpkg: considering deconfiguration of libgrib2c-dev:amd64, which would be broken by installation of libg2c-dev:amd64 ... | dpkg: yes, will deconfigure libgrib2c-dev:amd64 (broken by libg2c-dev:amd64) | (Reading database ... 4709 files and directories currently installed.) | Preparing to unpack ./libg2c-dev_1.7.0-2_amd64.deb ... | De-configuring libgrib2c-dev:amd64 (1.6.2-2) ... | Unpacking libg2c-dev:amd64 (1.7.0-2) ... | dpkg: error processing archive ./libg2c-dev_1.7.0-2_amd64.deb (--unpack): | trying to overwrite '/usr/include/grib2.h', which is also in package libgrib2c-dev:amd64 1.6.2-2 | Errors were encountered while processing: | ./libg2c-dev_1.7.0-2_amd64.deb Please ensure that libg2c-dev has sufficient Breaks and Replaces declarations. Helmut --- End Message --- --- Begin Message --- Source: g2clib Source-Version: 1.7.0-3 Done: Alastair McKinstry We believe that the bug you reported is fixed in the latest version of g2clib, 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 1034...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alastair McKinstry (supplier of updated g2clib 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: Thu, 27 Apr 2023 16:30:55 +0100 Source: g2clib Architecture: source Version: 1.7.0-3 Distribution: unstable Urgency: medium Maintainer: Alastair McKinstry Changed-By: Alastair McKinstry Closes: 1034962 Changes: g2clib (1.7.0-3) unstable; urgency=medium . * Typo: Replaces: libgrib2c-dev not libgrib2d-dev. Closes: #1034962 Checksums-Sha1: 9f1b02bc32dc0182d54a96144767f3492bc25eae 1977 g2clib_1.7.0-3.dsc 28863309a1a6b034722dcebb4bdf79c0f7b81ed9 5004 g2clib_1.7.0-3.debian.tar.xz Checksums-Sha256: 226f917ed0e13702e62c0cf7d634c45ff1b9ea7452fe055df45fd8cd0058c4bb 1977 g2clib_1.7.0-3.dsc 01803b6d0b89c9066b4721f1ff8c012060ab29672fb9f110593b4e08a7d23561 5004 g2clib_1.7.0-3.debian.tar.xz Files: fbb1d6e0cbf4e388e7d935537c03625c 1977 utils optional g2clib_1.7.0-3.dsc c760a4edac8128e6e3e3dc776e617f5a 5004 utils optional g2clib_1.7.0-3.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEgjg86RZbNHx4cIGiy+a7Tl2a06UFAmRKldwACgkQy+a7Tl2a 06VHhw/6AgW4Rge662qNS5LwaYbVIjo3JzQpnK0y5tErU2Iy7eyF/kj1fGQp2lbS KoBKww1G+JLZc4qQuwtYhsGjC8/RyaFOXqqO3a5hYq/P520MevcKuQggfwAoBix3 CpJaTe4Ftr2GLMm2A1YFKEavx+zlD9qonpNFzPUigGXet0Ksxi1clRqSIOQs4Z5y TVPK5sGP5LQxKDX0rPkrZG/ZV207WKcOR1xDUJhgkV0JVB7J3F20BKHdXkJKF/qH uzGVPT4LRp7Xjxu5lyruHzhgWZFvQvlf0e/0UNY3F0XtRPxDvSC4KP17PDYXqjCk ASuGnD0/fDFmQODppGUsUr0gLNtfzyZijM9JXB3XqRp5tdZ5AXfPfPGOib33EJ5m G1UNFWghwrtq5dRd8WPouvC8zw44CQ7TkqDGvwWIhCAFWRkbXvz9QJvnRZH9wguG CnhKIXgAL6LDUaD28j4ofTR67kccsRFNqCMk4lHFt2EM8Hwn/9rS7ecYabSmB8Pl 55HD7dVfCOYWqatjLijTDxPrMS1plnO085y+1KY7vc6UDg6u8aoV5zqMZqeaemkt 4kE7g0pgZ1acCzYOY5AIkceNhyiOIw17J8cAN1O2Gi4axnvc1XTLFVhiOPGXm+Zm oBDkIAbel9642/u7+cP+Nlz332r3BKunKSipXdvDhg06og5ECSc= =3JjU -END PGP SIGNATURE End Message ---
Bug#1034942: marked as done (pdl: missing Breaks+Replaces for libpdl-stats-perl when upgrading from bullseye)
Your message dated Thu, 27 Apr 2023 15:06:35 + with message-id and subject line Bug#1034942: fixed in pdl 1:2.081-2 has caused the Debian Bug report #1034942, regarding pdl: missing Breaks+Replaces for libpdl-stats-perl when upgrading from bullseye 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.) -- 1034942: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034942 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: pdl Version: 1:2.081-1+b1 Severity: serious Justification: dpkg unpack error Attempting to unpack pdl/1:2.081-1+b1 from Debian bookworm on a minimal Debian bullseye with libpdl-stats-perl/0.76-1 installed, causes an unpack error from dpkg due to /usr/share/man/man3/PDL::GSL::CDF.3pm.gz being contained in both packages. | (Reading database ... 7926 files and directories currently installed.) | Preparing to unpack ./pdl_1%3a2.081-1+b1_amd64.deb ... | Unpacking pdl (1:2.081-1+b1) over (1:2.025-1) ... | dpkg: error processing archive ./pdl_1%3a2.081-1+b1_amd64.deb (--unpack): | trying to overwrite '/usr/share/man/man3/PDL::GSL::CDF.3pm.gz', which is also in package libpdl-stats-perl 0.76-1 | dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) | Errors were encountered while processing: | ./pdl_1%3a2.081-1+b1_amd64.deb Please ensure that pdl has sufficient Breaks and Replaces declarations. Helmut --- End Message --- --- Begin Message --- Source: pdl Source-Version: 1:2.081-2 Done: Bas Couwenberg We believe that the bug you reported is fixed in the latest version of pdl, 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 1034...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bas Couwenberg (supplier of updated pdl 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: SHA512 Format: 1.8 Date: Thu, 27 Apr 2023 15:54:44 +0200 Source: pdl Architecture: source Version: 1:2.081-2 Distribution: unstable Urgency: medium Maintainer: Debian Perl Group Changed-By: Bas Couwenberg Closes: 1034942 Changes: pdl (1:2.081-2) unstable; urgency=medium . * Team upload. . [ Bas Couwenberg ] * Add Rules-Requires-Root to control file. * Add a debhelper sequence to run dh_pdl. * Bump Standards-Version to 4.6.2, no changes. * Add Breaks/Replaces on libpdl-stats-perl to fix upgrade. (closes: #1034942) . [ Debian Janitor ] * Update lintian override info to new format: + debian/source/lintian-overrides: line 2 + debian/pdl.lintian-overrides: line 6, 10, 22, 28 * Use secure URI in Homepage field. Checksums-Sha1: c5ba02fca54ee5b45570c2e84c1432177302dc62 2439 pdl_2.081-2.dsc fbf6297fd635ab933fa4a9638149229f5aa6bc41 30444 pdl_2.081-2.debian.tar.xz dda993bc541683e72e739e9e8e329c664ae83c10 13860 pdl_2.081-2_amd64.buildinfo Checksums-Sha256: 46538764ec9294c85697ff482b1682d22265e84b6bca842a988c52412abe6d75 2439 pdl_2.081-2.dsc 47c85d5d06533b1ec090d9bd80f42c893565d7b3d20e2dc9d64b3b1b6bcb4ece 30444 pdl_2.081-2.debian.tar.xz 4d9dd05638cffeb0e5e82a81418edafbc712ad4160aeeae3773ae28a4c9b6fb7 13860 pdl_2.081-2_amd64.buildinfo Files: ed07e67f78fec117afe2eb917870fae2 2439 math optional pdl_2.081-2.dsc aef6ac154c3bfead8d436b01bc38bd93 30444 math optional pdl_2.081-2.debian.tar.xz d434ff21f55ec7bbf78d5ecd93f64ed6 13860 math optional pdl_2.081-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEgYLeQXBWQI1hRlDRZ1DxCuiNSvEFAmRKiHUACgkQZ1DxCuiN SvF1QA/8CF8gieFRW26f7Myi76t92txDW8GXMXR0We5lEI+OfkLsU2mGXdXe2Pef aLWUVnFwtIyxQ9lVaVR2FhwtCJYVXW5oJ2tg+9iEHHLZdhEvaoKOKfYbIweJq2W5 1y5bLskDkHZ+EDYJAl0daS85aC9bmeyIOFHsY0xqIpjSKt95N9RnMpJz0WNq1k8b pFugKeyQ9hxM0NojIp5draiPRxbndKdnf1f9iIMF7QZ4TXyGTTT+VVf1EsrJnXqr 8h3+n90bBlHZPKVPgTyiZbh5emG7aTKt9MSVpKTQyk+SzIgLs8a14dvpyFhG0wMX 18ldc16IDVLZw8RbpKm/H/bVqUBdjbPWSUuYiZwAbuvgw1SzBoF8WBOa0Ztdb3uS iFgPVXBQOg8o9F5YquUzNeXtlI7dtt5im3YJHNEl27RuyhxkjTEbF5eq0CjVO8fA PlJKN0tpleRBpAn78XeUmKtdEFrnZ3vq2q6xQHYYJ+N3pSLdcyMhstjbP2a9Mk57 L8mb2IYD8ogdlkbFNYIZQzBZ4E1Di/Yas7xbiD1r/ksBJPkFg20aSiExZu4ErZDd dt7aXLkbjzDU1Qo3RRrmby9oMcvyvrkX/J9Oi+Ub51T2wXjPL8n1Ju7wYKPhm6dl GH1misz2kkhlJx45ojGP2IltQchVCUuzkDpKCmj4GO52zuFhtr0= =hFTq -END PGP
Processed: Bug#1034942 marked as pending in pdl
Processing control commands: > tag -1 pending Bug #1034942 [pdl] pdl: missing Breaks+Replaces for libpdl-stats-perl when upgrading from bullseye Ignoring request to alter tags of bug #1034942 to the same tags previously set -- 1034942: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034942 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1034942: marked as pending in pdl
Control: tag -1 pending Hello, Bug #1034942 in pdl reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/perl-team/modules/packages/pdl/-/commit/a1744458fa172cf7097d977e02b01cbf85b60a27 Add Breaks/Replaces on libpdl-stats-perl to fix upgrade. (closes: #1034942) (this message was generated automatically) -- Greetings https://bugs.debian.org/1034942
Bug#1035001: marked as done (wbar: missing Breaks+Replaces for wbar-config when upgrading from bullseye)
Your message dated Thu, 27 Apr 2023 14:37:37 + with message-id and subject line Bug#1035001: fixed in wbar 2.3.4-13 has caused the Debian Bug report #1035001, regarding wbar: missing Breaks+Replaces for wbar-config when upgrading from bullseye 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.) -- 1035001: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035001 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: wbar Version: 2.3.4-12 Severity: serious Justification: dpkg unpack error Attempting to unpack wbar/2.3.4-12 from Debian bookworm on a minimal Debian bullseye with wbar-config/2.3.4-10 installed, causes an unpack error from dpkg due to /usr/share/wbar/glade/wbar.glade being contained in both packages. | (Reading database ... 12816 files and directories currently installed.) | Preparing to unpack ./wbar_2.3.4-12_amd64.deb ... | Unpacking wbar (2.3.4-12) over (2.3.4-10) ... | dpkg: error processing archive ./wbar_2.3.4-12_amd64.deb (--unpack): | trying to overwrite '/usr/share/wbar/glade/wbar.glade', which is also in package wbar-config 2.3.4-10 | Processing triggers for hicolor-icon-theme (0.17-2) ... | Errors were encountered while processing: | ./wbar_2.3.4-12_amd64.deb Please ensure that wbar has sufficient Breaks and Replaces declarations. Helmut --- End Message --- --- Begin Message --- Source: wbar Source-Version: 2.3.4-13 Done: Markus Koschany We believe that the bug you reported is fixed in the latest version of wbar, 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 1035...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Markus Koschany (supplier of updated wbar 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: SHA512 Format: 1.8 Date: Thu, 27 Apr 2023 15:44:41 +0200 Source: wbar Architecture: source Version: 2.3.4-13 Distribution: unstable Urgency: medium Maintainer: Markus Koschany Changed-By: Markus Koschany Closes: 1035001 Changes: wbar (2.3.4-13) unstable; urgency=medium . * Do not install wbar.glade because it is not required and breaks wbar on upgrade from Bullseye to Bookworm (leftover from the wbar-config removal). Thanks to Helmut Grohne for the report. (Closes: #1035001) Checksums-Sha1: 91be34e23130001515d60e3ea82c17da6e43298f 2002 wbar_2.3.4-13.dsc 1a2cf4ad82b1c360b5ed0a51d7965cd3f75ba92c 8352 wbar_2.3.4-13.debian.tar.xz ee28672b1e723aa4bbfecb9b6f70980369d20de8 12580 wbar_2.3.4-13_amd64.buildinfo Checksums-Sha256: d15d650dc5a15c52bb025abdd2e46663686bfc8c81d1f5a6e86d044c1230bf3d 2002 wbar_2.3.4-13.dsc efcb6b66370e3b6c659717dcc58753b032d8e385b5aab0b202cf997b385420ec 8352 wbar_2.3.4-13.debian.tar.xz 90703f5483655a84198e3cf373f5179f521917e4536c4af2868dc76e3e7a9fb0 12580 wbar_2.3.4-13_amd64.buildinfo Files: 3226fa0b2b5027b7a1a8701dc75aec0e 2002 x11 optional wbar_2.3.4-13.dsc dc880f9571fddf8cb82208bb23542779 8352 x11 optional wbar_2.3.4-13.debian.tar.xz e178fa2367bbf7ddcdd16fb43d2060d8 12580 x11 optional wbar_2.3.4-13_amd64.buildinfo -BEGIN PGP SIGNATURE- iQKjBAEBCgCNFiEErPPQiO8y7e9qGoNf2a0UuVE7UeQFAmRKf6hfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEFD RjNEMDg4RUYzMkVERUY2QTFBODM1RkQ5QUQxNEI5NTEzQjUxRTQPHGFwb0BkZWJp YW4ub3JnAAoJENmtFLlRO1HkENgP/RE3OHAzmX4uEnY8HDRTlUGdzFNYekGWuz8a KBRcSkhZBryJauWtGbjvhDWIxDPteDemmReDFO48ZD7+WkiQfL5agKhXVlH0gswa 0XFXmzrft3LaC7JSGuORThik9NtmMKVaoGEZZdmlO/mUF75p1W6J0OGHdAR3rmix Sof+zkd6nmpNB3VnDm8K7nCcxj2hSuvn07zj6Sd+THnRh/cIlBLkwuDTGLrXX3aw AnSPAYRw0+N+RbW5PTNe7aGc9B45kfHlnjUWrZ9fEAYS709MeRE+/PS4LrroprXL 9DGXQC6l65MIumV/BmHuumtOguPRzwbtNQT/6XS5ytrhcmKtihZlPeSK1I7u/SAh /dFCUBTe46qUbyszbzEr0nZi8/7Bw/6UkkwW2Zn2FVbao63oJs/UmpJPT2QQYsGF y3ywNEFm177x2s9Ifj4s1WiAjK9oWCnXqCzFS4CIyKfgiRqg/x2C2vwSQjcjPCkn MknxU6/VZn00/JLx54q6loriwaAwBvYufx3E+EFz6WGOran1hhL7U0hvqqZBPsjb SsNBmL0auCeJDab1wHlD5k0+BKKC2nMCIIDuFA4khsLMnVzBNLy0bedMPM90Lgxq poZJhj83ZPEfnH/lIA0wKITxjKT0odZ/naMH2LsdI4cmqZimeTREy7zI39+1SW+o 5iRUTp2E =SJHN -END PGP SIGNATURE End Message ---
Bug#1034972: marked as done (python3-hfst: missing Breaks+Replaces for python3-libhfst when upgrading from bullseye)
Your message dated Thu, 27 Apr 2023 14:34:44 + with message-id and subject line Bug#1034972: fixed in hfst 3.16.0-5 has caused the Debian Bug report #1034972, regarding python3-hfst: missing Breaks+Replaces for python3-libhfst when upgrading from bullseye 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.) -- 1034972: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034972 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-hfst Version: 3.16.0-4+b3 Severity: serious Justification: dpkg unpack error Attempting to unpack python3-hfst/3.16.0-4+b3 from Debian bookworm on a minimal Debian bullseye with python3-libhfst/3.15.1-2+b5 installed, causes an unpack error from dpkg due to /usr/lib/python3/dist-packages/hfst/__init__.py being contained in both packages. | Selecting previously unselected package python3-hfst. | (Reading database ... 7327 files and directories currently installed.) | Preparing to unpack .../python3-hfst_3.16.0-4+b3_amd64.deb ... | Unpacking python3-hfst (3.16.0-4+b3) ... | dpkg: error processing archive ./python3-hfst_3.16.0-4+b3_amd64.deb (--unpack): | trying to overwrite '/usr/lib/python3/dist-packages/hfst/__init__.py', which is also in package python3-libhfst 3.15.1-2+b5 | dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) | Errors were encountered while processing: | ./python3-hfst_3.16.0-4+b3_amd64.deb Please ensure that python3-hfst has sufficient Breaks and Replaces declarations. Helmut --- End Message --- --- Begin Message --- Source: hfst Source-Version: 3.16.0-5 Done: Tino Didriksen We believe that the bug you reported is fixed in the latest version of hfst, 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 1034...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Tino Didriksen (supplier of updated hfst 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: SHA512 Format: 1.8 Date: Thu, 27 Apr 2023 15:46:23 +0200 Source: hfst Architecture: source Version: 3.16.0-5 Distribution: unstable Urgency: medium Maintainer: Debian Science Team Changed-By: Tino Didriksen Closes: 1034972 Changes: hfst (3.16.0-5) unstable; urgency=medium . * Add Breaks+Replaces (Closes: #1034972) Checksums-Sha1: a0968221e161df675dcedf34f26d1ae66b962ff1 2332 hfst_3.16.0-5.dsc 044b6abfac1ed58ddb197051e5b6fb6fd95c9733 8452 hfst_3.16.0-5.debian.tar.xz 4cb550524251611bdbea92c25771d73f6f04df33 7105 hfst_3.16.0-5_source.buildinfo Checksums-Sha256: 1a438daeba24dc82cdf80dacb93eb6d4fd797503c76c82a2d901b84d1b731fea 2332 hfst_3.16.0-5.dsc 6912791ccc946247827f4f9adae9a5e7030806a11a6dfe0c8b7693e7483ae0ca 8452 hfst_3.16.0-5.debian.tar.xz 4a3c0c0b62714169feb025f448890b8e53894638b61ddb08d391ff7c8f916d51 7105 hfst_3.16.0-5_source.buildinfo Files: dd5ed2231784c002f8074926c1b2d86e 2332 science optional hfst_3.16.0-5.dsc 1e44ea9c3b8397c3bb3404b0cc076266 8452 science optional hfst_3.16.0-5.debian.tar.xz 46f0eb0dc4ee562e1e03d3baeb4d08ed 7105 science optional hfst_3.16.0-5_source.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCgAwFiEEPM9UTIHRuWAtu3CGuXR64aaovegFAmRKgEASHHRpbm9AZGlk cmlrc2VuLmNjAAoJELl0euGmqL3oRrsP/Rtrljd3arljGAjFqMgQpdSeSp2O0xP2 cjQvSl+JLAmT7VenfIG8Q9iLYZMD7s+aV2TZU5rL4LQm5H9OEghspYcuQl0m9szr m8NTp/+LaNCVcJCbPpTpe+JrWzY82+beYP+IbsSO630wMgXZBk1ap5kV9fCFJREt cwUwfvs2n1LP9K9/Vr4FDpRUtkzB88xBJ/f+s/rWi8ET43N0kdcBdzJzaORbCsD1 eH8Ge40DYu/3N6DRJluvzOO+LWP7XFixBBecUcLQ9pE5w1XD6zS4SwgWXFrUMtM3 hZnpJinZSyFgq6jqgpZY/z9IHni8mEoN/tzVKwtuw9xk6CJz6fB2ZKgxNa80bZnG BVNtZFN2aul+l36xak3Opk6GHnk3G1m33Dr9ywbe2Ftkw0KKzxwgeKGA9cnNe77i W8SL+TzwDy8Cu2G26ADUAWUovpC3rw3MveLLpKh21QwmZVKXpBl/7WcEnezr5tFZ hTDsqMMdScvf9IpbliPyMI263mXYltOxAphGJmXkA5dZMBdYxVwaAok3pBrgDiR0 mkzugWxVngd2TrjYLZTFnuEO7tvSS7MOAX8fdZraeQH/inXqIWUtnDwPjhsyyGFO 5tcMWrSIcsWCn2pxxd1RRLEoVilsdBlUWZ1d+1B5zLJzK5j7rffPGGBmnauV+ad3 hH1bybJoOPza =L9vy -END PGP SIGNATURE End Message ---
Bug#1034956: marked as done (libeztrace0: missing Breaks+Replaces for libeztrace-dev when upgrading from bullseye)
Your message dated Thu, 27 Apr 2023 14:34:17 + with message-id and subject line Bug#1034956: fixed in eztrace 2.0+repack-12 has caused the Debian Bug report #1034956, regarding libeztrace0: missing Breaks+Replaces for libeztrace-dev when upgrading from bullseye 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.) -- 1034956: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034956 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libeztrace0 Version: 2.0+repack-11 Severity: serious Justification: dpkg unpack error Attempting to unpack libeztrace0/2.0+repack-11 from Debian bookworm on a minimal Debian bullseye with libeztrace-dev/1.1-10-2 installed, causes an unpack error from dpkg due to /usr/lib/x86_64-linux-gnu/libeztrace-memory.so being contained in both packages. | (Reading database ... 5608 files and directories currently installed.) | Preparing to unpack .../libeztrace0_2.0+repack-11_amd64.deb ... | Unpacking libeztrace0:amd64 (2.0+repack-11) over (1.1-10-2) ... | dpkg: error processing archive ./libeztrace0_2.0+repack-11_amd64.deb (--unpack): | trying to overwrite '/usr/lib/x86_64-linux-gnu/libeztrace-memory.so', which is also in package libeztrace-dev:amd64 1.1-10-2 | dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) | Processing triggers for libc-bin (2.31-13+deb11u5) ... | Errors were encountered while processing: | ./libeztrace0_2.0+repack-11_amd64.deb Please ensure that libeztrace0 has sufficient Breaks and Replaces declarations. Helmut --- End Message --- --- Begin Message --- Source: eztrace Source-Version: 2.0+repack-12 Done: Samuel Thibault We believe that the bug you reported is fixed in the latest version of eztrace, 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 1034...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Samuel Thibault (supplier of updated eztrace 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: SHA512 Format: 1.8 Date: Thu, 27 Apr 2023 16:07:04 +0200 Source: eztrace Architecture: source Version: 2.0+repack-12 Distribution: unstable Urgency: medium Maintainer: Samuel Thibault Changed-By: Samuel Thibault Closes: 1034956 Changes: eztrace (2.0+repack-12) unstable; urgency=medium . * control: Add missing breaks+replaces between libeztrace0 and libeztrace-dev, missed when moving /usr/lib/*/*.so from the latter to the former (Closes: Bug#1034956) Checksums-Sha1: a1fa217f28d85cd2753b07fd98431a619b5fca00 2559 eztrace_2.0+repack-12.dsc c7c66f7beb8009701be2a7daaa4e05fcbec5e8b5 30300 eztrace_2.0+repack-12.debian.tar.xz f3a77d6e9ba7bc7a75d876b4f38ee6dd487d641a 11230 eztrace_2.0+repack-12_amd64.buildinfo Checksums-Sha256: 43ff0fcaac130c8f846ef9f79ba5e3c6e8dcd347a9ee3fe025f23931610ba340 2559 eztrace_2.0+repack-12.dsc d1e4d1804d7658855aac156e9bd03281ca047a93da3767296e8fe7dac918d17a 30300 eztrace_2.0+repack-12.debian.tar.xz 231e7bfcfad9db1ce4bbc5cb5711920a7deab3ad35d74bde0a0a8c7ae608fcc0 11230 eztrace_2.0+repack-12_amd64.buildinfo Files: 1862c1a73eb0c1027ec3301306a70d07 2559 devel optional eztrace_2.0+repack-12.dsc 4cdc9549d5b412c3656ca9e9c94a9a9a 30300 devel optional eztrace_2.0+repack-12.debian.tar.xz 1feafeea1fb8b5e61feb20d641b9a05e 11230 devel optional eztrace_2.0+repack-12_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEi6MnFvk67auaclLJ5pG0tXV4H2IFAmRKgukACgkQ5pG0tXV4 H2LitQ/9GL2+a/s2iAIgaLi8KEBH7eE0qPKFGiuKxpH2piUHup+h3nm7BmKXxGOc A4K5gBFrVVOXozpb3a2Z2wjgUcn4s988rE4Am3JGJcco3GHC34X+3PNO7ASGXX3k v3SrADwxk+2km5SWNmzdRjvenLb4QsCwBM3AQJfKUXhjyMOgVcyX5rqbmLUaiFXp FS77McbHfvL2oR+mDe6mYfrD7L3O/W7H0dM81j+qDMOEu+3G+tHkwlopE+w6/R9I UzUbsdgURdWV+VHbr0c9W3YDLnnJZnaZUmtXpIxJUQQI+RsWZ4TkYE9/87/eNZXm ktICc6JrqRCxLH6XfuTm1XFfiQ6PcmMkA0Ypwyxo/rT077oHN3PB9UEvWuRRHnIH sUlDAWh/uHws9xCotSGXy61tOpYCuJ6dJOoCI8d/a2ZMztaN7DM1LZ07K6ZLdHtc 1qNsMbzNuuHDo8zfaFaALt7eG0BdcQOEI99GGPX8AZyO6yysv6yfT1qmK+QCYxsR mfqq/3iqGi+j67ULvH4cxImpN9HlBsYooTgFAvzehhynF7q9c6e8hJiuIfdZweat RgrHUI8WQX7zleEYHrkx0brl/u03/ahN5WZe643sw+xx/F6tGXFt4uVAUssExOOu OvAQhiOLQCANROGf2j7Nm+17T87vkf2mgvdUIP8OY9dfxad3yDU= =2lvg -END PGP SIGNATURE End Message ---
Bug#1034929: marked as done (apertium-lex-tools-dev: missing Breaks+Replaces for apertium-lex-tools when upgrading from bullseye)
Your message dated Thu, 27 Apr 2023 14:34:06 + with message-id and subject line Bug#1034929: fixed in apertium-lex-tools 0.4.2-2 has caused the Debian Bug report #1034929, regarding apertium-lex-tools-dev: missing Breaks+Replaces for apertium-lex-tools when upgrading from bullseye 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.) -- 1034929: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034929 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: apertium-lex-tools-dev Version: 0.4.2-1+b2 Severity: serious Justification: dpkg unpack error Attempting to unpack apertium-lex-tools-dev/0.4.2-1+b2 from Debian bookworm on a minimal Debian bullseye with apertium-lex-tools/0.2.7-1 installed, causes an unpack error from dpkg due to /usr/bin/lrx-comp being contained in both packages. | Selecting previously unselected package apertium-lex-tools-dev. | (Reading database ... 4721 files and directories currently installed.) | Preparing to unpack .../apertium-lex-tools-dev_0.4.2-1+b2_amd64.deb ... | Unpacking apertium-lex-tools-dev (0.4.2-1+b2) ... | dpkg: error processing archive ./apertium-lex-tools-dev_0.4.2-1+b2_amd64.deb (--unpack): | trying to overwrite '/usr/bin/lrx-comp', which is also in package apertium-lex-tools 0.2.7-1 | Errors were encountered while processing: | ./apertium-lex-tools-dev_0.4.2-1+b2_amd64.deb Please ensure that apertium-lex-tools-dev has sufficient Breaks and Replaces declarations. Helmut --- End Message --- --- Begin Message --- Source: apertium-lex-tools Source-Version: 0.4.2-2 Done: Tino Didriksen We believe that the bug you reported is fixed in the latest version of apertium-lex-tools, 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 1034...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Tino Didriksen (supplier of updated apertium-lex-tools 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: SHA512 Format: 1.8 Date: Thu, 27 Apr 2023 15:38:15 +0200 Source: apertium-lex-tools Architecture: source Version: 0.4.2-2 Distribution: unstable Urgency: medium Maintainer: Debian Science Team Changed-By: Tino Didriksen Closes: 1034929 Changes: apertium-lex-tools (0.4.2-2) unstable; urgency=medium . * Add Breaks+Replaces (Closes: 1034929) Checksums-Sha1: 3e6bf99505cb5953c328d797ece6ee070d09740b 2459 apertium-lex-tools_0.4.2-2.dsc 233c6f452cb04703a178b3faafc1c96feb0cf4a5 3916 apertium-lex-tools_0.4.2-2.debian.tar.xz a5b952b73829de97851f8e67e63949c9695075d2 7162 apertium-lex-tools_0.4.2-2_source.buildinfo Checksums-Sha256: 99645cbf4a5c95fc197070dbddb7170a3c5e2d7d5a1feb179f22a0bc9e079ce7 2459 apertium-lex-tools_0.4.2-2.dsc d0f9c26642f9e2e96f1d440a8b0b97aabbf5c0c4a41da44ddf8d065ad15ad4fe 3916 apertium-lex-tools_0.4.2-2.debian.tar.xz 651cda37d4376aa1248b0883f11a025c5623e9cff9dfff7c58da760ea318e3e0 7162 apertium-lex-tools_0.4.2-2_source.buildinfo Files: a9c2d14697e04f3e78066ab568302080 2459 science optional apertium-lex-tools_0.4.2-2.dsc 97b4af7f798b1dfd2516e178b82e8287 3916 science optional apertium-lex-tools_0.4.2-2.debian.tar.xz e1ab884702eb41700568926b1f3b3604 7162 science optional apertium-lex-tools_0.4.2-2_source.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCgAwFiEEPM9UTIHRuWAtu3CGuXR64aaovegFAmRKftcSHHRpbm9AZGlk cmlrc2VuLmNjAAoJELl0euGmqL3ooNUQALPwxS3v9PxkUmJXqg4tjA4DtQfCGFSX N3GqvDQDemsSdYZmaNrbFEOir7F5llIhxl9jx6mxBIGwDWMADRMxrrWm/lJb3dZf IEoa6i3e3baNNLXf53mE0RxgcLQRBJ7GA5SWR6NLVrCI/1XwoZ6mMILk8p47jtsH ddm34/mGVNGsBBH+V0Nj+an0QQFonKA0SyRjWEJOLB1l/lVz2IGNq8qQatr0/WhI iy5SJaLR9v+mXGalNUTF8ZTa5yUdU8iT6j9trtj5n7FuqWsqvDfcIoMPL3OFrLRx LrGEck8ZghwIKA9jNAZM2t7m+Gt5Rzp34GNdqMYTQuONrIJSvX/cphXoZGdGGyKP aCU6XjmwsbLTi2FOvS48yCyhEhYV0ZpzEodQlSSv1OrEqKz6TwFkvy4nz+/l6Omx YSttTiXRqShLsFncHwKtmR12+OZW5KXqjGDe8QiJdNb50u6vgBpLKpFEcFcFtRNX YmsDT70EseSOO2G8B7jqZM2HU3YcbnDTecwe7tbxa0Fgw959oK1GRIhgI8tMLesR XEYjqw4ZW/lO5NWq63vMPlSwcpW2YEkoeiZfxgYG0f13frthCwMRGCreumZu7AkR g3k2R7tBodVQ20IlH18Qcbvg/bdgVSHHfz8is93OKAAJ35CsH6tpEejxsdXTwlaf OOtojnFAy0wq =H0yl -END PGP SIGNATURE End Message ---
Processed: Re: Bug#1034942: pdl: missing Breaks+Replaces for libpdl-stats-perl when upgrading from bullseye
Processing control commands: > tags -1 pending Bug #1034942 [pdl] pdl: missing Breaks+Replaces for libpdl-stats-perl when upgrading from bullseye Added tag(s) pending. -- 1034942: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034942 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1034942: pdl: missing Breaks+Replaces for libpdl-stats-perl when upgrading from bullseye
Control: tags -1 pending On 4/27/23 14:58, Helmut Grohne wrote: Attempting to unpack pdl/1:2.081-1+b1 from Debian bookworm on a minimal Debian bullseye with libpdl-stats-perl/0.76-1 installed, causes an unpack error from dpkg due to /usr/share/man/man3/PDL::GSL::CDF.3pm.gz being contained in both packages. libpdl-stats-perl (0.82-3) in bookworm no longer includes the PDL::GSL::CDF files, but that can only be installed after the pdl (1:2.081-1). The CDF files are no longer included since libpdl-stats-perl (0.77-1~exp1). The issue is fixed in git and a new upload to unstable will follow shortly. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#1035013: libanet7-dev: missing Breaks+Replaces for libanet5-dev when upgrading from bullseye
Package: libanet7-dev Version: 0.4.3-2 Severity: serious Justification: dpkg unpack error Attempting to unpack libanet7-dev/0.4.3-2 from Debian bookworm on a minimal Debian bullseye with libanet5-dev/0.4.2-4 installed, causes an unpack error from dpkg due to /usr/lib/x86_64-linux-gnu/ada/adalib/anet/anet-arp.ali being contained in both packages. | Selecting previously unselected package libanet7-dev. | (Reading database ... 9228 files and directories currently installed.) | Preparing to unpack .../libanet7-dev_0.4.3-2_amd64.deb ... | Unpacking libanet7-dev (0.4.3-2) ... | dpkg: error processing archive ./libanet7-dev_0.4.3-2_amd64.deb (--unpack): | trying to overwrite '/usr/lib/x86_64-linux-gnu/ada/adalib/anet/anet-arp.ali', which is also in package libanet5-dev 0.4.2-4 | dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) | Errors were encountered while processing: | ./libanet7-dev_0.4.3-2_amd64.deb Please ensure that libanet7-dev has sufficient Breaks and Replaces declarations. Helmut
Bug#1035009: libocct-data-exchange-dev: missing Breaks+Replaces for liboce-modeling-dev when upgrading from bullseye
Package: libocct-data-exchange-dev Version: 7.6.3+dfsg1-5 Severity: serious Justification: dpkg unpack error Attempting to unpack libocct-data-exchange-dev/7.6.3+dfsg1-5 from Debian bookworm on a minimal Debian bullseye with liboce-modeling-dev/0.18.3-1 installed, causes an unpack error from dpkg due to /usr/lib/x86_64-linux-gnu/libTKIGES.so being contained in both packages. | Selecting previously unselected package libocct-data-exchange-dev:amd64. | (Reading database ... 17251 files and directories currently installed.) | Preparing to unpack .../libocct-data-exchange-dev_7.6.3+dfsg1-5_amd64.deb ... | Unpacking libocct-data-exchange-dev:amd64 (7.6.3+dfsg1-5) ... | dpkg: error processing archive ./libocct-data-exchange-dev_7.6.3+dfsg1-5_amd64.deb (--unpack): | trying to overwrite '/usr/lib/x86_64-linux-gnu/libTKIGES.so', which is also in package liboce-modeling-dev:amd64 0.18.3-1 | Errors were encountered while processing: | ./libocct-data-exchange-dev_7.6.3+dfsg1-5_amd64.deb Please ensure that libocct-data-exchange-dev has sufficient Breaks and Replaces declarations. Helmut
Bug#1035012: libzmat-dev: missing Breaks+Replaces for libzmat1-dev when upgrading from bullseye
Package: libzmat-dev Version: 0.9.8+ds-7 Severity: serious Justification: dpkg unpack error Attempting to unpack libzmat-dev/0.9.8+ds-7 from Debian bookworm on a minimal Debian bullseye with libzmat1-dev/0.9.8+ds-3 installed, causes an unpack error from dpkg due to /usr/include/zmatlib.f90 being contained in both packages. | Selecting previously unselected package libzmat-dev:amd64. | (Reading database ... 4701 files and directories currently installed.) | Preparing to unpack .../libzmat-dev_0.9.8+ds-7_amd64.deb ... | Unpacking libzmat-dev:amd64 (0.9.8+ds-7) ... | dpkg: error processing archive ./libzmat-dev_0.9.8+ds-7_amd64.deb (--unpack): | trying to overwrite '/usr/include/zmatlib.f90', which is also in package libzmat1-dev:amd64 0.9.8+ds-3 | Errors were encountered while processing: | ./libzmat-dev_0.9.8+ds-7_amd64.deb Please ensure that libzmat-dev has sufficient Breaks and Replaces declarations. Helmut
Bug#1035008: node-jest-worker: missing Breaks+Replaces for jest when upgrading from bullseye
Package: node-jest-worker Version: 29.3.1~ds1+~cs70.48.25-1 Severity: serious Justification: dpkg unpack error Attempting to unpack node-jest-worker/29.3.1~ds1+~cs70.48.25-1 from Debian bookworm on a minimal Debian bullseye with jest/26.6.3+repack+~cs64.44.39-3 installed, causes an unpack error from dpkg due to /usr/share/nodejs/@jest/types/build/Circus.d.ts being contained in both packages. | dpkg: considering deconfiguration of jest, which would be broken by installation of node-jest-worker ... | dpkg: yes, will deconfigure jest (broken by node-jest-worker) | (Reading database ... 21294 files and directories currently installed.) | Preparing to unpack .../node-jest-worker_29.3.1~ds1+~cs70.48.25-1_all.deb ... | De-configuring jest (26.6.3+repack+~cs64.44.39-3) ... | Unpacking node-jest-worker (29.3.1~ds1+~cs70.48.25-1) over (26.6.3+repack+~cs64.44.39-3) ... | dpkg: error processing archive ./node-jest-worker_29.3.1~ds1+~cs70.48.25-1_all.deb (--unpack): | trying to overwrite '/usr/share/nodejs/@jest/types/build/Circus.d.ts', which is also in package jest 26.6.3+repack+~cs64.44.39-3 | Errors were encountered while processing: | ./node-jest-worker_29.3.1~ds1+~cs70.48.25-1_all.deb Please ensure that node-jest-worker has sufficient Breaks and Replaces declarations. Helmut
Bug#1035011: libahven11-dev: missing Breaks+Replaces for libahven9-dev when upgrading from bullseye
Package: libahven11-dev Version: 2.8-6 Severity: serious Justification: dpkg unpack error Attempting to unpack libahven11-dev/2.8-6 from Debian bookworm on a minimal Debian bullseye with libahven9-dev/2.8-1 installed, causes an unpack error from dpkg due to /usr/lib/x86_64-linux-gnu/ada/adalib/ahven/ahven-astrings.ali being contained in both packages. | Selecting previously unselected package libahven11-dev. | (Reading database ... 9179 files and directories currently installed.) | Preparing to unpack .../libahven11-dev_2.8-6_amd64.deb ... | Unpacking libahven11-dev (2.8-6) ... | dpkg: error processing archive ./libahven11-dev_2.8-6_amd64.deb (--unpack): | trying to overwrite '/usr/lib/x86_64-linux-gnu/ada/adalib/ahven/ahven-astrings.ali', which is also in package libahven9-dev 2.8-1 | dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) | Errors were encountered while processing: | ./libahven11-dev_2.8-6_amd64.deb Please ensure that libahven11-dev has sufficient Breaks and Replaces declarations. Helmut
Bug#1035010: libgnatcoll-postgres3-dev: missing Breaks+Replaces for libgnatcoll-postgres1-dev when upgrading from bullseye
Package: libgnatcoll-postgres3-dev Version: 23.0.0-3 Severity: serious Justification: dpkg unpack error Attempting to unpack libgnatcoll-postgres3-dev/23.0.0-3 from Debian bookworm on a minimal Debian bullseye with libgnatcoll-postgres1-dev/21.0.0-6 installed, causes an unpack error from dpkg due to /usr/lib/x86_64-linux-gnu/ada/adalib/gnatcoll_postgres/gnatcoll-sql-postgres.ali being contained in both packages. | Selecting previously unselected package libgnatcoll-postgres3-dev. | (Reading database ... 10135 files and directories currently installed.) | Preparing to unpack .../libgnatcoll-postgres3-dev_23.0.0-3_amd64.deb ... | Unpacking libgnatcoll-postgres3-dev (23.0.0-3) ... | dpkg: error processing archive ./libgnatcoll-postgres3-dev_23.0.0-3_amd64.deb (--unpack): | trying to overwrite '/usr/lib/x86_64-linux-gnu/ada/adalib/gnatcoll_postgres/gnatcoll-sql-postgres.ali', which is also in package libgnatcoll-postgres1-dev 21.0.0-6 | dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) | Errors were encountered while processing: | ./libgnatcoll-postgres3-dev_23.0.0-3_amd64.deb Please ensure that libgnatcoll-postgres3-dev has sufficient Breaks and Replaces declarations. Helmut
Bug#1035007: davmail-server: missing Breaks+Replaces for davmail when upgrading from bullseye
Package: davmail-server Version: 6.0.1.3390-6 Severity: serious Justification: dpkg unpack error Attempting to unpack davmail-server/6.0.1.3390-6 from Debian bookworm on a minimal Debian bullseye with davmail/5.5.1.3299-5 installed, causes an unpack error from dpkg due to /etc/davmail/davmail.properties being contained in both packages. | Selecting previously unselected package davmail-server. | dpkg: considering deconfiguration of davmail, which would be broken by installation of davmail-server ... | dpkg: yes, will deconfigure davmail (broken by davmail-server) | (Reading database ... 6734 files and directories currently installed.) | Preparing to unpack .../davmail-server_6.0.1.3390-6_all.deb ... | De-configuring davmail (5.5.1.3299-5) ... | Unpacking davmail-server (6.0.1.3390-6) ... | dpkg: error processing archive ./davmail-server_6.0.1.3390-6_all.deb (--unpack): | trying to overwrite '/etc/davmail/davmail.properties', which is also in package davmail 5.5.1.3299-5 | dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) | invoke-rc.d: could not determine current runlevel | invoke-rc.d: policy-rc.d denied execution of restart. | Errors were encountered while processing: | ./davmail-server_6.0.1.3390-6_all.deb Please ensure that davmail-server has sufficient Breaks and Replaces declarations. Helmut
Bug#1035006: libflorist2022-dev: missing Breaks+Replaces for libflorist2020-dev when upgrading from bullseye
Package: libflorist2022-dev Version: 2022.0.1~20220616-2 Severity: serious Justification: dpkg unpack error Attempting to unpack libflorist2022-dev/2022.0.1~20220616-2 from Debian bookworm on a minimal Debian bullseye with libflorist2020-dev/2017-9 installed, causes an unpack error from dpkg due to /usr/lib/x86_64-linux-gnu/ada/adalib/florist/ada_streams.ali being contained in both packages. | Selecting previously unselected package libflorist2022-dev. | (Reading database ... 9336 files and directories currently installed.) | Preparing to unpack .../libflorist2022-dev_2022.0.1~20220616-2_amd64.deb ... | Unpacking libflorist2022-dev (2022.0.1~20220616-2) ... | dpkg: error processing archive ./libflorist2022-dev_2022.0.1~20220616-2_amd64.deb (--unpack): | trying to overwrite '/usr/lib/x86_64-linux-gnu/ada/adalib/florist/ada_streams.ali', which is also in package libflorist2020-dev 2017-9 | dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) | Errors were encountered while processing: | ./libflorist2022-dev_2022.0.1~20220616-2_amd64.deb Please ensure that libflorist2022-dev has sufficient Breaks and Replaces declarations. Helmut
Bug#1035005: uwsgi-plugin-jvm-openjdk-17: missing Breaks+Replaces for uwsgi-plugin-jvm-openjdk-11 when upgrading from bullseye
Package: uwsgi-plugin-jvm-openjdk-17 Version: 2.0.21-5 Severity: serious Justification: dpkg unpack error Attempting to unpack uwsgi-plugin-jvm-openjdk-17/2.0.21-5 from Debian bookworm on a minimal Debian bullseye with uwsgi-plugin-jvm-openjdk-11/2.0.19.1-7.1 installed, causes an unpack error from dpkg due to /usr/share/java/uwsgi.jar being contained in both packages. | Selecting previously unselected package uwsgi-plugin-jvm-openjdk-17. | (Reading database ... 6132 files and directories currently installed.) | Preparing to unpack .../uwsgi-plugin-jvm-openjdk-17_2.0.21-5_amd64.deb ... | Unpacking uwsgi-plugin-jvm-openjdk-17 (2.0.21-5) ... | dpkg: error processing archive ./uwsgi-plugin-jvm-openjdk-17_2.0.21-5_amd64.deb (--unpack): | trying to overwrite '/usr/share/java/uwsgi.jar', which is also in package uwsgi-plugin-jvm-openjdk-11 2.0.19.1-7.1 | Errors were encountered while processing: | ./uwsgi-plugin-jvm-openjdk-17_2.0.21-5_amd64.deb Please ensure that uwsgi-plugin-jvm-openjdk-17 has sufficient Breaks and Replaces declarations. Helmut
Bug#1035004: libalog8-dev: missing Breaks+Replaces for libalog6-dev when upgrading from bullseye
Package: libalog8-dev Version: 0.6.2-2 Severity: serious Justification: dpkg unpack error Attempting to unpack libalog8-dev/0.6.2-2 from Debian bookworm on a minimal Debian bullseye with libalog6-dev/0.6.1-4 installed, causes an unpack error from dpkg due to /usr/lib/x86_64-linux-gnu/ada/adalib/alog/alog-active_logger.ali being contained in both packages. | Selecting previously unselected package libalog8-dev. | (Reading database ... 9183 files and directories currently installed.) | Preparing to unpack .../libalog8-dev_0.6.2-2_amd64.deb ... | Unpacking libalog8-dev (0.6.2-2) ... | dpkg: error processing archive ./libalog8-dev_0.6.2-2_amd64.deb (--unpack): | trying to overwrite '/usr/lib/x86_64-linux-gnu/ada/adalib/alog/alog-active_logger.ali', which is also in package libalog6-dev 0.6.1-4 | dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) | Errors were encountered while processing: | ./libalog8-dev_0.6.2-2_amd64.deb Please ensure that libalog8-dev has sufficient Breaks and Replaces declarations. Helmut
Bug#1035003: python3-meep-openmpi: missing Breaks+Replaces in multiple situations when upgrading from bullseye
Package: python3-meep-openmpi Version: 1.25.0-1+b1 Severity: serious Justification: dpkg unpack error Attempting to unpack python3-meep-openmpi/1.25.0-1+b1 from Debian bookworm on a minimal Debian bullseye with python3-meep-mpi-default/1.17.1-2 installed, causes an unpack error from dpkg due to /usr/lib/python3/dist-packages/meep/__init__.py being contained in both packages. | Selecting previously unselected package python3-meep-openmpi. | (Reading database ... 9458 files and directories currently installed.) | Preparing to unpack .../python3-meep-openmpi_1.25.0-1+b1_amd64.deb ... | Unpacking python3-meep-openmpi (1.25.0-1+b1) ... | dpkg: error processing archive ./python3-meep-openmpi_1.25.0-1+b1_amd64.deb (--unpack): | trying to overwrite '/usr/lib/python3/dist-packages/meep/__init__.py', which is also in package python3-meep-mpi-default 1.17.1-2 | dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) | Processing triggers for libc-bin (2.31-13+deb11u5) ... | Errors were encountered while processing: | ./python3-meep-openmpi_1.25.0-1+b1_amd64.deb Attempting to unpack python3-meep-openmpi/1.25.0-1+b1 from Debian bookworm on a minimal Debian bullseye with python3-meep/1.17.1-1 installed, causes an unpack error from dpkg due to /usr/lib/python3/dist-packages/meep/__init__.py being contained in both packages. | Selecting previously unselected package python3-meep-openmpi. | (Reading database ... 8718 files and directories currently installed.) | Preparing to unpack .../python3-meep-openmpi_1.25.0-1+b1_amd64.deb ... | Unpacking python3-meep-openmpi (1.25.0-1+b1) ... | dpkg: error processing archive ./python3-meep-openmpi_1.25.0-1+b1_amd64.deb (--unpack): | trying to overwrite '/usr/lib/python3/dist-packages/meep/__init__.py', which is also in package python3-meep 1.17.1-1 | dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) | Processing triggers for libc-bin (2.31-13+deb11u5) ... | Errors were encountered while processing: | ./python3-meep-openmpi_1.25.0-1+b1_amd64.deb Please ensure that python3-meep-openmpi has sufficient Breaks and Replaces declarations. Helmut
Bug#1035002: libgnatcoll-readline21-dev: missing Breaks+Replaces for libgnatcoll-readline19-dev when upgrading from bullseye
Package: libgnatcoll-readline21-dev Version: 23.0.0-5 Severity: serious Justification: dpkg unpack error Attempting to unpack libgnatcoll-readline21-dev/23.0.0-5 from Debian bookworm on a minimal Debian bullseye with libgnatcoll-readline19-dev/21.0.0-4 installed, causes an unpack error from dpkg due to /usr/lib/x86_64-linux-gnu/ada/adalib/gnatcoll_readline/gnatcoll-readline.ali being contained in both packages. | Selecting previously unselected package libgnatcoll-readline21-dev. | (Reading database ... 10158 files and directories currently installed.) | Preparing to unpack .../libgnatcoll-readline21-dev_23.0.0-5_amd64.deb ... | Unpacking libgnatcoll-readline21-dev (23.0.0-5) ... | dpkg: error processing archive ./libgnatcoll-readline21-dev_23.0.0-5_amd64.deb (--unpack): | trying to overwrite '/usr/lib/x86_64-linux-gnu/ada/adalib/gnatcoll_readline/gnatcoll-readline.ali', which is also in package libgnatcoll-readline19-dev 21.0.0-4 | Errors were encountered while processing: | ./libgnatcoll-readline21-dev_23.0.0-5_amd64.deb Please ensure that libgnatcoll-readline21-dev has sufficient Breaks and Replaces declarations. Helmut
Bug#1035001: wbar: missing Breaks+Replaces for wbar-config when upgrading from bullseye
Package: wbar Version: 2.3.4-12 Severity: serious Justification: dpkg unpack error Attempting to unpack wbar/2.3.4-12 from Debian bookworm on a minimal Debian bullseye with wbar-config/2.3.4-10 installed, causes an unpack error from dpkg due to /usr/share/wbar/glade/wbar.glade being contained in both packages. | (Reading database ... 12816 files and directories currently installed.) | Preparing to unpack ./wbar_2.3.4-12_amd64.deb ... | Unpacking wbar (2.3.4-12) over (2.3.4-10) ... | dpkg: error processing archive ./wbar_2.3.4-12_amd64.deb (--unpack): | trying to overwrite '/usr/share/wbar/glade/wbar.glade', which is also in package wbar-config 2.3.4-10 | Processing triggers for hicolor-icon-theme (0.17-2) ... | Errors were encountered while processing: | ./wbar_2.3.4-12_amd64.deb Please ensure that wbar has sufficient Breaks and Replaces declarations. Helmut
Bug#1035000: node-core-js-pure: missing Breaks+Replaces for node-core-js when upgrading from bullseye
Package: node-core-js-pure Version: 3.26.1-1 Severity: serious Justification: dpkg unpack error Attempting to unpack node-core-js-pure/3.26.1-1 from Debian bookworm on a minimal Debian bullseye with node-core-js/3.8.2-2 installed, causes an unpack error from dpkg due to /usr/share/nodejs/core-js-pure/configurator.js being contained in both packages. | Selecting previously unselected package node-core-js-pure. | dpkg: considering deconfiguration of node-core-js, which would be broken by installation of node-core-js-pure ... | dpkg: yes, will deconfigure node-core-js (broken by node-core-js-pure) | (Reading database ... 7666 files and directories currently installed.) | Preparing to unpack .../node-core-js-pure_3.26.1-1_all.deb ... | De-configuring node-core-js (3.8.2-2) ... | Unpacking node-core-js-pure (3.26.1-1) ... | dpkg: error processing archive ./node-core-js-pure_3.26.1-1_all.deb (--unpack): | trying to overwrite '/usr/share/nodejs/core-js-pure/configurator.js', which is also in package node-core-js 3.8.2-2 | dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) | Errors were encountered while processing: | ./node-core-js-pure_3.26.1-1_all.deb Please ensure that node-core-js-pure has sufficient Breaks and Replaces declarations. Helmut
Bug#1034977: libncursesada11-dev: missing Breaks+Replaces for libncursesada9-dev when upgrading from bullseye
Package: libncursesada11-dev Version: 6.3.20211021-7 Severity: serious Justification: dpkg unpack error Attempting to unpack libncursesada11-dev/6.3.20211021-7 from Debian bookworm on a minimal Debian bullseye with libncursesada9-dev/6.2.20200212-4 installed, causes an unpack error from dpkg due to /usr/lib/x86_64-linux-gnu/ada/adalib/ncursesada/terminal_interface-curses-aux.ali being contained in both packages. | Selecting previously unselected package libncursesada11-dev. | (Reading database ... 9360 files and directories currently installed.) | Preparing to unpack .../libncursesada11-dev_6.3.20211021-7_amd64.deb ... | Unpacking libncursesada11-dev (6.3.20211021-7) ... | dpkg: error processing archive ./libncursesada11-dev_6.3.20211021-7_amd64.deb (--unpack): | trying to overwrite '/usr/lib/x86_64-linux-gnu/ada/adalib/ncursesada/terminal_interface-curses-aux.ali', which is also in package libncursesada9-dev 6.2.20200212-4 | dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) | Errors were encountered while processing: | ./libncursesada11-dev_6.3.20211021-7_amd64.deb Please ensure that libncursesada11-dev has sufficient Breaks and Replaces declarations. Helmut
Bug#1034999: librust-sha3-0.9-dev: missing Breaks+Replaces for librust-sha3-dev when upgrading from bullseye
Package: librust-sha3-0.9-dev Version: 0.9.1-1+b1 Severity: serious Justification: dpkg unpack error Attempting to unpack librust-sha3-0.9-dev/0.9.1-1+b1 from Debian bookworm on a minimal Debian bullseye with librust-sha3-dev/0.9.1-1 installed, causes an unpack error from dpkg due to /usr/share/cargo/registry/sha3-0.9.1/.cargo-checksum.json being contained in both packages. | Selecting previously unselected package librust-sha3-0.9-dev:amd64. | dpkg: considering deconfiguration of librust-sha3-dev:amd64, which would be broken by installation of librust-sha3-0.9-dev:amd64 ... | dpkg: yes, will deconfigure librust-sha3-dev:amd64 (broken by librust-sha3-0.9-dev:amd64) | (Reading database ... 4873 files and directories currently installed.) | Preparing to unpack .../librust-sha3-0.9-dev_0.9.1-1+b1_amd64.deb ... | De-configuring librust-sha3-dev:amd64 (0.9.1-1) ... | Unpacking librust-sha3-0.9-dev:amd64 (0.9.1-1+b1) ... | dpkg: error processing archive ./librust-sha3-0.9-dev_0.9.1-1+b1_amd64.deb (--unpack): | trying to overwrite '/usr/share/cargo/registry/sha3-0.9.1/.cargo-checksum.json', which is also in package librust-sha3-dev:amd64 0.9.1-1 | dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) | Errors were encountered while processing: | ./librust-sha3-0.9-dev_0.9.1-1+b1_amd64.deb Please ensure that librust-sha3-0.9-dev has sufficient Breaks and Replaces declarations. Helmut
Bug#1034998: pcp-export-pcp2elasticsearch: missing Breaks+Replaces for pcp when upgrading from bullseye
Package: pcp-export-pcp2elasticsearch Version: 6.0.3-1 Severity: serious Justification: dpkg unpack error Attempting to unpack pcp-export-pcp2elasticsearch/6.0.3-1 from Debian bookworm on a minimal Debian bullseye with pcp/5.2.6-1 installed, causes an unpack error from dpkg due to /usr/bin/pcp2elasticsearch being contained in both packages. | Selecting previously unselected package pcp-export-pcp2elasticsearch. | dpkg: considering deconfiguration of pcp, which would be broken by installation of pcp-export-pcp2elasticsearch ... | dpkg: yes, will deconfigure pcp (broken by pcp-export-pcp2elasticsearch) | (Reading database ... 10064 files and directories currently installed.) | Preparing to unpack .../pcp-export-pcp2elasticsearch_6.0.3-1_amd64.deb ... | De-configuring pcp (5.2.6-1) ... | invoke-rc.d: could not determine current runlevel | invoke-rc.d: policy-rc.d denied execution of stop. | invoke-rc.d: could not determine current runlevel | invoke-rc.d: policy-rc.d denied execution of stop. | invoke-rc.d: could not determine current runlevel | invoke-rc.d: policy-rc.d denied execution of stop. | invoke-rc.d: could not determine current runlevel | invoke-rc.d: policy-rc.d denied execution of stop. | Unpacking pcp-export-pcp2elasticsearch (6.0.3-1) ... | dpkg: error processing archive ./pcp-export-pcp2elasticsearch_6.0.3-1_amd64.deb (--unpack): | trying to overwrite '/usr/bin/pcp2elasticsearch', which is also in package pcp 5.2.6-1 | dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) | invoke-rc.d: could not determine current runlevel | invoke-rc.d: policy-rc.d denied execution of start. | invoke-rc.d: could not determine current runlevel | invoke-rc.d: policy-rc.d denied execution of start. | Errors were encountered while processing: | ./pcp-export-pcp2elasticsearch_6.0.3-1_amd64.deb Please ensure that pcp-export-pcp2elasticsearch has sufficient Breaks and Replaces declarations. Helmut
Bug#1034997: libdtkcommon: missing Breaks+Replaces for libdtkcore5 when upgrading from bullseye
Package: libdtkcommon Version: 5.5.23-1 Severity: serious Justification: dpkg unpack error Attempting to unpack libdtkcommon/5.5.23-1 from Debian bookworm on a minimal Debian bullseye with libdtkcore5/5.2.2.5-3 installed, causes an unpack error from dpkg due to /usr/share/glib-2.0/schemas/com.deepin.dtk.gschema.xml being contained in both packages. | Selecting previously unselected package libdtkcommon. | dpkg: considering deconfiguration of libdtkcore5:amd64, which would be broken by installation of libdtkcommon ... | dpkg: yes, will deconfigure libdtkcore5:amd64 (broken by libdtkcommon) | (Reading database ... 5903 files and directories currently installed.) | Preparing to unpack .../libdtkcommon_5.5.23-1_amd64.deb ... | De-configuring libdtkcore5:amd64 (5.2.2.5-3) ... | Unpacking libdtkcommon (5.5.23-1) ... | dpkg: error processing archive ./libdtkcommon_5.5.23-1_amd64.deb (--unpack): | trying to overwrite '/usr/share/glib-2.0/schemas/com.deepin.dtk.gschema.xml', which is also in package libdtkcore5:amd64 5.2.2.5-3 | Processing triggers for libc-bin (2.31-13+deb11u5) ... | Processing triggers for libglib2.0-0:amd64 (2.66.8-1) ... | Errors were encountered while processing: | ./libdtkcommon_5.5.23-1_amd64.deb Please ensure that libdtkcommon has sufficient Breaks and Replaces declarations. Helmut
Bug#1034994: librust-semver-0.9-dev: missing Breaks+Replaces for librust-semver-dev when upgrading from bullseye
Package: librust-semver-0.9-dev Version: 0.9.0-3+b1 Severity: serious Justification: dpkg unpack error Attempting to unpack librust-semver-0.9-dev/0.9.0-3+b1 from Debian bookworm on a minimal Debian bullseye with librust-semver-dev/0.9.0-1+b1 installed, causes an unpack error from dpkg due to /usr/share/cargo/registry/semver-0.9.0/.cargo-checksum.json being contained in both packages. | Selecting previously unselected package librust-semver-0.9-dev:amd64. | dpkg: considering deconfiguration of librust-semver-dev:amd64, which would be broken by installation of librust-semver-0.9-dev:amd64 ... | dpkg: yes, will deconfigure librust-semver-dev:amd64 (broken by librust-semver-0.9-dev:amd64) | (Reading database ... 4714 files and directories currently installed.) | Preparing to unpack .../librust-semver-0.9-dev_0.9.0-3+b1_amd64.deb ... | De-configuring librust-semver-dev:amd64 (0.9.0-1+b1) ... | Unpacking librust-semver-0.9-dev:amd64 (0.9.0-3+b1) ... | dpkg: error processing archive ./librust-semver-0.9-dev_0.9.0-3+b1_amd64.deb (--unpack): | trying to overwrite '/usr/share/cargo/registry/semver-0.9.0/.cargo-checksum.json', which is also in package librust-semver-dev:amd64 0.9.0-1+b1 | Errors were encountered while processing: | ./librust-semver-0.9-dev_0.9.0-3+b1_amd64.deb Please ensure that librust-semver-0.9-dev has sufficient Breaks and Replaces declarations. Helmut
Bug#1034995: python-is-python3: missing Breaks+Replaces for python-dev-is-python2 when upgrading from bullseye
Package: python-is-python3 Version: 3.11.1-3 Severity: serious Justification: dpkg unpack error Attempting to unpack python-is-python3/3.11.1-3 from Debian bookworm on a minimal Debian bullseye with python-dev-is-python2/2.7.18-9 installed, causes an unpack error from dpkg due to /usr/bin/pydoc being contained in both packages. | Selecting previously unselected package python-is-python3. | dpkg: considering deconfiguration of python-is-python2, which would be broken by installation of python-is-python3 ... | dpkg: yes, will deconfigure python-is-python2 (broken by python-is-python3) | (Reading database ... 9300 files and directories currently installed.) | Preparing to unpack .../python-is-python3_3.11.1-3_all.deb ... | De-configuring python-is-python2 (2.7.18-9) ... | Unpacking python-is-python3 (3.11.1-3) ... | dpkg: error processing archive ./python-is-python3_3.11.1-3_all.deb (--unpack): | trying to overwrite '/usr/bin/pydoc', which is also in package python-dev-is-python2 2.7.18-9 | Errors were encountered while processing: | ./python-is-python3_3.11.1-3_all.deb Please ensure that python-is-python3 has sufficient Breaks and Replaces declarations. Helmut
Bug#1034996: libomemo0: missing Breaks+Replaces for libomemo-dev when upgrading from bullseye
Package: libomemo0 Version: 0.8.1-1 Severity: serious Justification: dpkg unpack error Attempting to unpack libomemo0/0.8.1-1 from Debian bookworm on a minimal Debian bullseye with libomemo-dev/0.7.0-1 installed, causes an unpack error from dpkg due to /usr/lib/x86_64-linux-gnu/libomemo.so being contained in both packages. | (Reading database ... 12426 files and directories currently installed.) | Preparing to unpack ./libomemo0_0.8.1-1_amd64.deb ... | Unpacking libomemo0:amd64 (0.8.1-1) over (0.7.0-1) ... | dpkg: error processing archive ./libomemo0_0.8.1-1_amd64.deb (--unpack): | trying to overwrite '/usr/lib/x86_64-linux-gnu/libomemo.so', which is also in package libomemo-dev:amd64 0.7.0-1 | Processing triggers for libc-bin (2.31-13+deb11u5) ... | Errors were encountered while processing: | ./libomemo0_0.8.1-1_amd64.deb Please ensure that libomemo0 has sufficient Breaks and Replaces declarations. Helmut
Bug#1034991: libgnatcoll-omp3-dev: missing Breaks+Replaces for libgnatcoll-omp1-dev when upgrading from bullseye
Package: libgnatcoll-omp3-dev Version: 23.0.0-5 Severity: serious Justification: dpkg unpack error Attempting to unpack libgnatcoll-omp3-dev/23.0.0-5 from Debian bookworm on a minimal Debian bullseye with libgnatcoll-omp1-dev/21.0.0-4 installed, causes an unpack error from dpkg due to /usr/lib/x86_64-linux-gnu/ada/adalib/gnatcoll_omp/a-cvgpso.ali being contained in both packages. | Selecting previously unselected package libgnatcoll-omp3-dev. | (Reading database ... 10018 files and directories currently installed.) | Preparing to unpack .../libgnatcoll-omp3-dev_23.0.0-5_amd64.deb ... | Unpacking libgnatcoll-omp3-dev (23.0.0-5) ... | dpkg: error processing archive ./libgnatcoll-omp3-dev_23.0.0-5_amd64.deb (--unpack): | trying to overwrite '/usr/lib/x86_64-linux-gnu/ada/adalib/gnatcoll_omp/a-cvgpso.ali', which is also in package libgnatcoll-omp1-dev 21.0.0-4 | Errors were encountered while processing: | ./libgnatcoll-omp3-dev_23.0.0-5_amd64.deb Please ensure that libgnatcoll-omp3-dev has sufficient Breaks and Replaces declarations. Helmut
Bug#1034993: software-properties-qt: missing Breaks+Replaces for software-properties-kde when upgrading from bullseye
Package: software-properties-qt Version: 0.99.30-4 Severity: serious Justification: dpkg unpack error Attempting to unpack software-properties-qt/0.99.30-4 from Debian bookworm on a minimal Debian bullseye with software-properties-kde/0.96.20.2-2.1 installed, causes an unpack error from dpkg due to /usr/share/software-properties/designer/dialog_add.ui being contained in both packages. | Selecting previously unselected package software-properties-qt. | (Reading database ... 11560 files and directories currently installed.) | Preparing to unpack .../software-properties-qt_0.99.30-4_all.deb ... | Unpacking software-properties-qt (0.99.30-4) ... | dpkg: error processing archive ./software-properties-qt_0.99.30-4_all.deb (--unpack): | trying to overwrite '/usr/share/software-properties/designer/dialog_add.ui', which is also in package software-properties-kde 0.96.20.2-2.1 | Errors were encountered while processing: | ./software-properties-qt_0.99.30-4_all.deb Please ensure that software-properties-qt has sufficient Breaks and Replaces declarations. Helmut
Bug#1034992: slurm-wlm-rrd-plugin: missing Breaks+Replaces for slurm-wlm-basic-plugins when upgrading from bullseye
Package: slurm-wlm-rrd-plugin Version: 22.05.8-3 Severity: serious Justification: dpkg unpack error Attempting to unpack slurm-wlm-rrd-plugin/22.05.8-3 from Debian bookworm on a minimal Debian bullseye with slurm-wlm-basic-plugins/20.11.7+really20.11.4-2+deb11u1 installed, causes an unpack error from dpkg due to /usr/lib/x86_64-linux-gnu/slurm-wlm/ext_sensors_rrd.so being contained in both packages. | Selecting previously unselected package slurm-wlm-rrd-plugin. | (Reading database ... 5770 files and directories currently installed.) | Preparing to unpack .../slurm-wlm-rrd-plugin_22.05.8-3_amd64.deb ... | Unpacking slurm-wlm-rrd-plugin (22.05.8-3) ... | dpkg: error processing archive ./slurm-wlm-rrd-plugin_22.05.8-3_amd64.deb (--unpack): | trying to overwrite '/usr/lib/x86_64-linux-gnu/slurm-wlm/ext_sensors_rrd.so', which is also in package slurm-wlm-basic-plugins 20.11.7+really20.11.4-2+deb11u1 | Errors were encountered while processing: | ./slurm-wlm-rrd-plugin_22.05.8-3_amd64.deb Please ensure that slurm-wlm-rrd-plugin has sufficient Breaks and Replaces declarations. Helmut
Bug#1034989: node-core-js-bundle: missing Breaks+Replaces for node-core-js when upgrading from bullseye
Package: node-core-js-bundle Version: 3.26.1-1 Severity: serious Justification: dpkg unpack error Attempting to unpack node-core-js-bundle/3.26.1-1 from Debian bookworm on a minimal Debian bullseye with node-core-js/3.8.2-2 installed, causes an unpack error from dpkg due to /usr/share/nodejs/core-js-bundle/package.json being contained in both packages. | Selecting previously unselected package node-core-js-bundle. | dpkg: considering deconfiguration of node-core-js, which would be broken by installation of node-core-js-bundle ... | dpkg: yes, will deconfigure node-core-js (broken by node-core-js-bundle) | (Reading database ... 7666 files and directories currently installed.) | Preparing to unpack .../node-core-js-bundle_3.26.1-1_all.deb ... | De-configuring node-core-js (3.8.2-2) ... | Unpacking node-core-js-bundle (3.26.1-1) ... | dpkg: error processing archive ./node-core-js-bundle_3.26.1-1_all.deb (--unpack): | trying to overwrite '/usr/share/nodejs/core-js-bundle/package.json', which is also in package node-core-js 3.8.2-2 | Errors were encountered while processing: | ./node-core-js-bundle_3.26.1-1_all.deb Please ensure that node-core-js-bundle has sufficient Breaks and Replaces declarations. Helmut
Bug#1034988: python3-meep: missing Breaks+Replaces in multiple situations when upgrading from bullseye
Package: python3-meep Version: 1.25.0-1+b1 Severity: serious Justification: dpkg unpack error Attempting to unpack python3-meep/1.25.0-1+b1 from Debian bookworm on a minimal Debian bullseye with python3-meep-mpi-default/1.17.1-2 installed, causes an unpack error from dpkg due to /usr/lib/python3/dist-packages/meep/__init__.py being contained in both packages. | Selecting previously unselected package python3-meep. | (Reading database ... 9458 files and directories currently installed.) | Preparing to unpack .../python3-meep_1.25.0-1+b1_amd64.deb ... | Unpacking python3-meep (1.25.0-1+b1) ... | dpkg: error processing archive ./python3-meep_1.25.0-1+b1_amd64.deb (--unpack): | trying to overwrite '/usr/lib/python3/dist-packages/meep/__init__.py', which is also in package python3-meep-mpi-default 1.17.1-2 | dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) | Processing triggers for libc-bin (2.31-13+deb11u5) ... | Errors were encountered while processing: | ./python3-meep_1.25.0-1+b1_amd64.deb Attempting to unpack python3-meep/1.25.0-1+b1 from Debian bookworm on a minimal Debian bullseye with python3-meep-openmpi/1.17.1-2 installed, causes an unpack error from dpkg due to /usr/lib/python3/dist-packages/meep/__init__.py being contained in both packages. | Selecting previously unselected package python3-meep. | (Reading database ... 9458 files and directories currently installed.) | Preparing to unpack .../python3-meep_1.25.0-1+b1_amd64.deb ... | Unpacking python3-meep (1.25.0-1+b1) ... | dpkg: error processing archive ./python3-meep_1.25.0-1+b1_amd64.deb (--unpack): | trying to overwrite '/usr/lib/python3/dist-packages/meep/__init__.py', which is also in package python3-meep-openmpi 1.17.1-2 | dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) | Processing triggers for libc-bin (2.31-13+deb11u5) ... | Errors were encountered while processing: | ./python3-meep_1.25.0-1+b1_amd64.deb Please ensure that python3-meep has sufficient Breaks and Replaces declarations. Helmut
Bug#1034985: libtemplates-parser16-dev: missing Breaks+Replaces for libtemplates-parser14-dev when upgrading from bullseye
Package: libtemplates-parser16-dev Version: 23.0.0-2 Severity: serious Justification: dpkg unpack error Attempting to unpack libtemplates-parser16-dev/23.0.0-2 from Debian bookworm on a minimal Debian bullseye with libtemplates-parser14-dev/21.0.0-2 installed, causes an unpack error from dpkg due to /usr/bin/templates2ada being contained in both packages. | Selecting previously unselected package libtemplates-parser16-dev. | (Reading database ... 9186 files and directories currently installed.) | Preparing to unpack .../libtemplates-parser16-dev_23.0.0-2_amd64.deb ... | Unpacking libtemplates-parser16-dev (23.0.0-2) ... | dpkg: error processing archive ./libtemplates-parser16-dev_23.0.0-2_amd64.deb (--unpack): | trying to overwrite '/usr/bin/templates2ada', which is also in package libtemplates-parser14-dev 21.0.0-2 | dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) | Errors were encountered while processing: | ./libtemplates-parser16-dev_23.0.0-2_amd64.deb Please ensure that libtemplates-parser16-dev has sufficient Breaks and Replaces declarations. Helmut
Bug#1034987: slurm-wlm-elasticsearch-plugin: missing Breaks+Replaces for slurm-wlm-basic-plugins when upgrading from bullseye
Package: slurm-wlm-elasticsearch-plugin Version: 22.05.8-3 Severity: serious Justification: dpkg unpack error Attempting to unpack slurm-wlm-elasticsearch-plugin/22.05.8-3 from Debian bookworm on a minimal Debian bullseye with slurm-wlm-basic-plugins/20.11.7+really20.11.4-2+deb11u1 installed, causes an unpack error from dpkg due to /usr/lib/x86_64-linux-gnu/slurm-wlm/jobcomp_elasticsearch.so being contained in both packages. | Selecting previously unselected package slurm-wlm-elasticsearch-plugin. | (Reading database ... 5770 files and directories currently installed.) | Preparing to unpack .../slurm-wlm-elasticsearch-plugin_22.05.8-3_amd64.deb ... | Unpacking slurm-wlm-elasticsearch-plugin (22.05.8-3) ... | dpkg: error processing archive ./slurm-wlm-elasticsearch-plugin_22.05.8-3_amd64.deb (--unpack): | trying to overwrite '/usr/lib/x86_64-linux-gnu/slurm-wlm/jobcomp_elasticsearch.so', which is also in package slurm-wlm-basic-plugins 20.11.7+really20.11.4-2+deb11u1 | Errors were encountered while processing: | ./slurm-wlm-elasticsearch-plugin_22.05.8-3_amd64.deb Please ensure that slurm-wlm-elasticsearch-plugin has sufficient Breaks and Replaces declarations. Helmut
Bug#1034986: xmorph: missing Breaks+Replaces for libmorph when upgrading from bullseye
Package: xmorph Version: 1:20150712-1 Severity: serious Justification: dpkg unpack error Attempting to unpack xmorph/1:20150712-1 from Debian bookworm on a minimal Debian bullseye with libmorph/1:20140707+nmu2.1 installed, causes an unpack error from dpkg due to /usr/share/man/man1/morph.1.gz being contained in both packages. | Selecting previously unselected package xmorph. | (Reading database ... 4692 files and directories currently installed.) | Preparing to unpack .../xmorph_1%3a20150712-1_amd64.deb ... | Unpacking xmorph (1:20150712-1) ... | dpkg: error processing archive ./xmorph_1%3a20150712-1_amd64.deb (--unpack): | trying to overwrite '/usr/share/man/man1/morph.1.gz', which is also in package libmorph 1:20140707+nmu2.1 | Errors were encountered while processing: | ./xmorph_1%3a20150712-1_amd64.deb Please ensure that xmorph has sufficient Breaks and Replaces declarations. Helmut
Bug#1034984: node-parse5-htmlparser2-tree-adapter: missing Breaks+Replaces for node-cheerio when upgrading from bullseye
Package: node-parse5-htmlparser2-tree-adapter Version: 7.1.2+dfsg-1 Severity: serious Justification: dpkg unpack error Attempting to unpack node-parse5-htmlparser2-tree-adapter/7.1.2+dfsg-1 from Debian bookworm on a minimal Debian bullseye with node-cheerio/1.0.0~rc~5+~cs6.1.2-4 installed, causes an unpack error from dpkg due to /usr/share/nodejs/parse5-htmlparser2-tree-adapter/package.json being contained in both packages. | Selecting previously unselected package node-parse5-htmlparser2-tree-adapter. | dpkg: considering deconfiguration of node-jsdom, which would be broken by installation of node-parse5-htmlparser2-tree-adapter ... | dpkg: yes, will deconfigure node-jsdom (broken by node-parse5-htmlparser2-tree-adapter) | (Reading database ... 7213 files and directories currently installed.) | Preparing to unpack .../node-parse5-htmlparser2-tree-adapter_7.1.2+dfsg-1_all.deb ... | De-configuring node-jsdom (16.4.0+~cs77.17.35-3) ... | Unpacking node-parse5-htmlparser2-tree-adapter (7.1.2+dfsg-1) ... | dpkg: error processing archive ./node-parse5-htmlparser2-tree-adapter_7.1.2+dfsg-1_all.deb (--unpack): | trying to overwrite '/usr/share/nodejs/parse5-htmlparser2-tree-adapter/package.json', which is also in package node-cheerio 1.0.0~rc~5+~cs6.1.2-4 | Errors were encountered while processing: | ./node-parse5-htmlparser2-tree-adapter_7.1.2+dfsg-1_all.deb Please ensure that node-parse5-htmlparser2-tree-adapter has sufficient Breaks and Replaces declarations. Helmut
Bug#1034983: pcp-export-pcp2json: missing Breaks+Replaces for pcp when upgrading from bullseye
Package: pcp-export-pcp2json Version: 6.0.3-1 Severity: serious Justification: dpkg unpack error Attempting to unpack pcp-export-pcp2json/6.0.3-1 from Debian bookworm on a minimal Debian bullseye with pcp/5.2.6-1 installed, causes an unpack error from dpkg due to /usr/bin/pcp2json being contained in both packages. | Selecting previously unselected package pcp-export-pcp2json. | dpkg: considering deconfiguration of pcp, which would be broken by installation of pcp-export-pcp2json ... | dpkg: yes, will deconfigure pcp (broken by pcp-export-pcp2json) | (Reading database ... 10064 files and directories currently installed.) | Preparing to unpack .../pcp-export-pcp2json_6.0.3-1_amd64.deb ... | De-configuring pcp (5.2.6-1) ... | invoke-rc.d: could not determine current runlevel | invoke-rc.d: policy-rc.d denied execution of stop. | invoke-rc.d: could not determine current runlevel | invoke-rc.d: policy-rc.d denied execution of stop. | invoke-rc.d: could not determine current runlevel | invoke-rc.d: policy-rc.d denied execution of stop. | invoke-rc.d: could not determine current runlevel | invoke-rc.d: policy-rc.d denied execution of stop. | Unpacking pcp-export-pcp2json (6.0.3-1) ... | dpkg: error processing archive ./pcp-export-pcp2json_6.0.3-1_amd64.deb (--unpack): | trying to overwrite '/usr/bin/pcp2json', which is also in package pcp 5.2.6-1 | dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) | invoke-rc.d: could not determine current runlevel | invoke-rc.d: policy-rc.d denied execution of start. | invoke-rc.d: could not determine current runlevel | invoke-rc.d: policy-rc.d denied execution of start. | Errors were encountered while processing: | ./pcp-export-pcp2json_6.0.3-1_amd64.deb Please ensure that pcp-export-pcp2json has sufficient Breaks and Replaces declarations. Helmut
Bug#1034979: libtexttools11-dev: missing Breaks+Replaces for libtexttools9-dev when upgrading from bullseye
Package: libtexttools11-dev Version: 2.1.0-25 Severity: serious Justification: dpkg unpack error Attempting to unpack libtexttools11-dev/2.1.0-25 from Debian bookworm on a minimal Debian bullseye with libtexttools9-dev/2.1.0-18 installed, causes an unpack error from dpkg due to /usr/lib/x86_64-linux-gnu/ada/adalib/texttools/common.ali being contained in both packages. | Selecting previously unselected package libtexttools11-dev. | (Reading database ... 9270 files and directories currently installed.) | Preparing to unpack .../libtexttools11-dev_2.1.0-25_amd64.deb ... | Unpacking libtexttools11-dev (2.1.0-25) ... | dpkg: error processing archive ./libtexttools11-dev_2.1.0-25_amd64.deb (--unpack): | trying to overwrite '/usr/lib/x86_64-linux-gnu/ada/adalib/texttools/common.ali', which is also in package libtexttools9-dev 2.1.0-18 | dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) | Errors were encountered while processing: | ./libtexttools11-dev_2.1.0-25_amd64.deb Please ensure that libtexttools11-dev has sufficient Breaks and Replaces declarations. Helmut
Bug#1034982: android-libnativehelper: missing Breaks+Replaces for android-libnativehelper-dev when upgrading from bullseye
Package: android-libnativehelper Version: 29.0.6-26 Severity: serious Justification: dpkg unpack error Attempting to unpack android-libnativehelper/29.0.6-26 from Debian bookworm on a minimal Debian bullseye with android-libnativehelper-dev/10.0.0+r36-2 installed, causes an unpack error from dpkg due to /usr/lib/x86_64-linux-gnu/android/libnativehelper.so being contained in both packages. | (Reading database ... 4717 files and directories currently installed.) | Preparing to unpack .../android-libnativehelper_29.0.6-26_amd64.deb ... | Unpacking android-libnativehelper:amd64 (29.0.6-26) over (10.0.0+r36-2) ... | dpkg: error processing archive ./android-libnativehelper_29.0.6-26_amd64.deb (--unpack): | trying to overwrite '/usr/lib/x86_64-linux-gnu/android/libnativehelper.so', which is also in package android-libnativehelper-dev 10.0.0+r36-2 | Processing triggers for libc-bin (2.31-13+deb11u5) ... | Errors were encountered while processing: | ./android-libnativehelper_29.0.6-26_amd64.deb Please ensure that android-libnativehelper has sufficient Breaks and Replaces declarations. Helmut
Bug#1034981: libgnatcoll-xref22-dev: missing Breaks+Replaces for libgnatcoll-xref20-dev when upgrading from bullseye
Package: libgnatcoll-xref22-dev Version: 23.0.0-3 Severity: serious Justification: dpkg unpack error Attempting to unpack libgnatcoll-xref22-dev/23.0.0-3 from Debian bookworm on a minimal Debian bullseye with libgnatcoll-xref20-dev/21.0.0-6 installed, causes an unpack error from dpkg due to /usr/lib/x86_64-linux-gnu/ada/adalib/gnatcoll_xref/gnatcoll-xref-database.ali being contained in both packages. | Selecting previously unselected package libgnatcoll-xref22-dev. | (Reading database ... 10115 files and directories currently installed.) | Preparing to unpack .../libgnatcoll-xref22-dev_23.0.0-3_amd64.deb ... | Unpacking libgnatcoll-xref22-dev (23.0.0-3) ... | dpkg: error processing archive ./libgnatcoll-xref22-dev_23.0.0-3_amd64.deb (--unpack): | trying to overwrite '/usr/lib/x86_64-linux-gnu/ada/adalib/gnatcoll_xref/gnatcoll-xref-database.ali', which is also in package libgnatcoll-xref20-dev 21.0.0-6 | dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) | Errors were encountered while processing: | ./libgnatcoll-xref22-dev_23.0.0-3_amd64.deb Please ensure that libgnatcoll-xref22-dev has sufficient Breaks and Replaces declarations. Helmut
Bug#1034980: node-core-js-builder: missing Breaks+Replaces for node-core-js when upgrading from bullseye
Package: node-core-js-builder Version: 3.26.1-1 Severity: serious Justification: dpkg unpack error Attempting to unpack node-core-js-builder/3.26.1-1 from Debian bookworm on a minimal Debian bullseye with node-core-js/3.8.2-2 installed, causes an unpack error from dpkg due to /usr/share/nodejs/core-js-builder/config.js being contained in both packages. | Selecting previously unselected package node-core-js-builder. | dpkg: considering deconfiguration of node-core-js, which would be broken by installation of node-core-js-builder ... | dpkg: yes, will deconfigure node-core-js (broken by node-core-js-builder) | (Reading database ... 7666 files and directories currently installed.) | Preparing to unpack .../node-core-js-builder_3.26.1-1_all.deb ... | De-configuring node-core-js (3.8.2-2) ... | Unpacking node-core-js-builder (3.26.1-1) ... | dpkg: error processing archive ./node-core-js-builder_3.26.1-1_all.deb (--unpack): | trying to overwrite '/usr/share/nodejs/core-js-builder/config.js', which is also in package node-core-js 3.8.2-2 | Errors were encountered while processing: | ./node-core-js-builder_3.26.1-1_all.deb Please ensure that node-core-js-builder has sufficient Breaks and Replaces declarations. Helmut
Bug#1034978: slurm-wlm-jwt-plugin: missing Breaks+Replaces for slurm-wlm-basic-plugins when upgrading from bullseye
Package: slurm-wlm-jwt-plugin Version: 22.05.8-3 Severity: serious Justification: dpkg unpack error Attempting to unpack slurm-wlm-jwt-plugin/22.05.8-3 from Debian bookworm on a minimal Debian bullseye with slurm-wlm-basic-plugins/20.11.7+really20.11.4-2+deb11u1 installed, causes an unpack error from dpkg due to /usr/lib/x86_64-linux-gnu/slurm-wlm/auth_jwt.so being contained in both packages. | Selecting previously unselected package slurm-wlm-jwt-plugin. | (Reading database ... 5770 files and directories currently installed.) | Preparing to unpack .../slurm-wlm-jwt-plugin_22.05.8-3_amd64.deb ... | Unpacking slurm-wlm-jwt-plugin (22.05.8-3) ... | dpkg: error processing archive ./slurm-wlm-jwt-plugin_22.05.8-3_amd64.deb (--unpack): | trying to overwrite '/usr/lib/x86_64-linux-gnu/slurm-wlm/auth_jwt.so', which is also in package slurm-wlm-basic-plugins 20.11.7+really20.11.4-2+deb11u1 | Errors were encountered while processing: | ./slurm-wlm-jwt-plugin_22.05.8-3_amd64.deb Please ensure that slurm-wlm-jwt-plugin has sufficient Breaks and Replaces declarations. Helmut
Bug#1034976: gensio-bin: missing Breaks+Replaces for libgensio-dev when upgrading from bullseye
Package: gensio-bin Version: 2.6.2-3 Severity: serious Justification: dpkg unpack error Attempting to unpack gensio-bin/2.6.2-3 from Debian bookworm on a minimal Debian bullseye with libgensio-dev/2.2.4-1 installed, causes an unpack error from dpkg due to /usr/share/man/man5/gensio.5.gz being contained in both packages. | Selecting previously unselected package gensio-bin. | dpkg: considering deconfiguration of libgensio0:amd64, which would be broken by installation of gensio-bin ... | dpkg: yes, will deconfigure libgensio0:amd64 (broken by gensio-bin) | (Reading database ... 4951 files and directories currently installed.) | Preparing to unpack ./gensio-bin_2.6.2-3_amd64.deb ... | De-configuring libgensio0:amd64 (2.2.4-1) ... | Unpacking gensio-bin (2.6.2-3) ... | dpkg: error processing archive ./gensio-bin_2.6.2-3_amd64.deb (--unpack): | trying to overwrite '/usr/share/man/man5/gensio.5.gz', which is also in package libgensio-dev:amd64 2.2.4-1 | Processing triggers for libc-bin (2.31-13+deb11u5) ... | Errors were encountered while processing: | ./gensio-bin_2.6.2-3_amd64.deb Please ensure that gensio-bin has sufficient Breaks and Replaces declarations. Helmut
Bug#1034975: libadacgi6-dev: missing Breaks+Replaces for libadacgi4-dev when upgrading from bullseye
Package: libadacgi6-dev Version: 1.6-31 Severity: serious Justification: dpkg unpack error Attempting to unpack libadacgi6-dev/1.6-31 from Debian bookworm on a minimal Debian bullseye with libadacgi4-dev/1.6-26+b1 installed, causes an unpack error from dpkg due to /usr/lib/x86_64-linux-gnu/ada/adalib/adacgi/cgi.ali being contained in both packages. | Selecting previously unselected package libadacgi6-dev. | (Reading database ... 9156 files and directories currently installed.) | Preparing to unpack .../libadacgi6-dev_1.6-31_amd64.deb ... | Unpacking libadacgi6-dev (1.6-31) ... | dpkg: error processing archive ./libadacgi6-dev_1.6-31_amd64.deb (--unpack): | trying to overwrite '/usr/lib/x86_64-linux-gnu/ada/adalib/adacgi/cgi.ali', which is also in package libadacgi4-dev 1.6-26+b1 | Errors were encountered while processing: | ./libadacgi6-dev_1.6-31_amd64.deb Please ensure that libadacgi6-dev has sufficient Breaks and Replaces declarations. Helmut
Bug#1034974: libgnatcoll-iconv21-dev: missing Breaks+Replaces for libgnatcoll-iconv19-dev when upgrading from bullseye
Package: libgnatcoll-iconv21-dev Version: 23.0.0-5 Severity: serious Justification: dpkg unpack error Attempting to unpack libgnatcoll-iconv21-dev/23.0.0-5 from Debian bookworm on a minimal Debian bullseye with libgnatcoll-iconv19-dev/21.0.0-4 installed, causes an unpack error from dpkg due to /usr/lib/x86_64-linux-gnu/ada/adalib/gnatcoll_iconv/gnatcoll-iconv.ali being contained in both packages. | Selecting previously unselected package libgnatcoll-iconv21-dev. | (Reading database ... 10013 files and directories currently installed.) | Preparing to unpack .../libgnatcoll-iconv21-dev_23.0.0-5_amd64.deb ... | Unpacking libgnatcoll-iconv21-dev (23.0.0-5) ... | dpkg: error processing archive ./libgnatcoll-iconv21-dev_23.0.0-5_amd64.deb (--unpack): | trying to overwrite '/usr/lib/x86_64-linux-gnu/ada/adalib/gnatcoll_iconv/gnatcoll-iconv.ali', which is also in package libgnatcoll-iconv19-dev 21.0.0-4 | Errors were encountered while processing: | ./libgnatcoll-iconv21-dev_23.0.0-5_amd64.deb Please ensure that libgnatcoll-iconv21-dev has sufficient Breaks and Replaces declarations. Helmut
Bug#1034971: lxd-client: missing Breaks+Replaces for lxc when upgrading from bullseye
Package: lxd-client Version: 5.0.2-3+b2 Severity: serious Justification: dpkg unpack error Attempting to unpack lxd-client/5.0.2-3+b2 from Debian bookworm on a minimal Debian bullseye with lxc/1:4.0.6-2+deb11u1 installed, causes an unpack error from dpkg due to /usr/share/bash-completion/completions/lxc being contained in both packages. | Selecting previously unselected package lxd-client. | dpkg: considering deconfiguration of lxc, which would be broken by installation of lxd-client ... | dpkg: yes, will deconfigure lxc (broken by lxd-client) | (Reading database ... 5457 files and directories currently installed.) | Preparing to unpack .../lxd-client_5.0.2-3+b2_amd64.deb ... | De-configuring lxc (1:4.0.6-2+deb11u1) ... | Unpacking lxd-client (5.0.2-3+b2) ... | dpkg: error processing archive ./lxd-client_5.0.2-3+b2_amd64.deb (--unpack): | trying to overwrite '/usr/share/bash-completion/completions/lxc', which is also in package lxc 1:4.0.6-2+deb11u1 | dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) | dpkg: warning: version 'in-favour' has bad syntax: version number does not start with digit | Errors were encountered while processing: | ./lxd-client_5.0.2-3+b2_amd64.deb Please ensure that lxd-client has sufficient Breaks and Replaces declarations. Helmut
Bug#1034973: pcp-export-pcp2zabbix: missing Breaks+Replaces for pcp when upgrading from bullseye
Package: pcp-export-pcp2zabbix Version: 6.0.3-1 Severity: serious Justification: dpkg unpack error Attempting to unpack pcp-export-pcp2zabbix/6.0.3-1 from Debian bookworm on a minimal Debian bullseye with pcp/5.2.6-1 installed, causes an unpack error from dpkg due to /usr/bin/pcp2zabbix being contained in both packages. | Selecting previously unselected package pcp-export-pcp2zabbix. | dpkg: considering deconfiguration of pcp, which would be broken by installation of pcp-export-pcp2zabbix ... | dpkg: yes, will deconfigure pcp (broken by pcp-export-pcp2zabbix) | (Reading database ... 10064 files and directories currently installed.) | Preparing to unpack .../pcp-export-pcp2zabbix_6.0.3-1_amd64.deb ... | De-configuring pcp (5.2.6-1) ... | invoke-rc.d: could not determine current runlevel | invoke-rc.d: policy-rc.d denied execution of stop. | invoke-rc.d: could not determine current runlevel | invoke-rc.d: policy-rc.d denied execution of stop. | invoke-rc.d: could not determine current runlevel | invoke-rc.d: policy-rc.d denied execution of stop. | invoke-rc.d: could not determine current runlevel | invoke-rc.d: policy-rc.d denied execution of stop. | Unpacking pcp-export-pcp2zabbix (6.0.3-1) ... | dpkg: error processing archive ./pcp-export-pcp2zabbix_6.0.3-1_amd64.deb (--unpack): | trying to overwrite '/usr/bin/pcp2zabbix', which is also in package pcp 5.2.6-1 | dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) | invoke-rc.d: could not determine current runlevel | invoke-rc.d: policy-rc.d denied execution of start. | invoke-rc.d: could not determine current runlevel | invoke-rc.d: policy-rc.d denied execution of start. | Errors were encountered while processing: | ./pcp-export-pcp2zabbix_6.0.3-1_amd64.deb Please ensure that pcp-export-pcp2zabbix has sufficient Breaks and Replaces declarations. Helmut
Bug#1034972: python3-hfst: missing Breaks+Replaces for python3-libhfst when upgrading from bullseye
Package: python3-hfst Version: 3.16.0-4+b3 Severity: serious Justification: dpkg unpack error Attempting to unpack python3-hfst/3.16.0-4+b3 from Debian bookworm on a minimal Debian bullseye with python3-libhfst/3.15.1-2+b5 installed, causes an unpack error from dpkg due to /usr/lib/python3/dist-packages/hfst/__init__.py being contained in both packages. | Selecting previously unselected package python3-hfst. | (Reading database ... 7327 files and directories currently installed.) | Preparing to unpack .../python3-hfst_3.16.0-4+b3_amd64.deb ... | Unpacking python3-hfst (3.16.0-4+b3) ... | dpkg: error processing archive ./python3-hfst_3.16.0-4+b3_amd64.deb (--unpack): | trying to overwrite '/usr/lib/python3/dist-packages/hfst/__init__.py', which is also in package python3-libhfst 3.15.1-2+b5 | dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) | Errors were encountered while processing: | ./python3-hfst_3.16.0-4+b3_amd64.deb Please ensure that python3-hfst has sufficient Breaks and Replaces declarations. Helmut
Bug#1034970: libgtkada22-dev: missing Breaks+Replaces for libgtkada20-dev when upgrading from bullseye
Package: libgtkada22-dev Version: 23.0.0-3 Severity: serious Justification: dpkg unpack error Attempting to unpack libgtkada22-dev/23.0.0-3 from Debian bookworm on a minimal Debian bullseye with libgtkada20-dev/21.0.0.785f3cf4-3 installed, causes an unpack error from dpkg due to /usr/lib/x86_64-linux-gnu/ada/adalib/gtkada/cairo-font_face.ali being contained in both packages. | Selecting previously unselected package libgtkada22-dev. | (Reading database ... 28489 files and directories currently installed.) | Preparing to unpack .../libgtkada22-dev_23.0.0-3_amd64.deb ... | Unpacking libgtkada22-dev (23.0.0-3) ... | dpkg: error processing archive ./libgtkada22-dev_23.0.0-3_amd64.deb (--unpack): | trying to overwrite '/usr/lib/x86_64-linux-gnu/ada/adalib/gtkada/cairo-font_face.ali', which is also in package libgtkada20-dev 21.0.0.785f3cf4-3 | dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) | Errors were encountered while processing: | ./libgtkada22-dev_23.0.0-3_amd64.deb Please ensure that libgtkada22-dev has sufficient Breaks and Replaces declarations. Helmut
Bug#1034969: terser: missing Breaks+Replaces for uglifyjs.terser when upgrading from bullseye
Package: terser Version: 5.16.4-1 Severity: serious Justification: dpkg unpack error Attempting to unpack terser/5.16.4-1 from Debian bookworm on a minimal Debian bullseye with uglifyjs.terser/4.1.2-8 installed, causes an unpack error from dpkg due to /usr/share/nodejs/terser/bin/uglifyjs being contained in both packages. | Selecting previously unselected package terser. | dpkg: considering deconfiguration of uglifyjs.terser, which would be broken by installation of terser ... | dpkg: yes, will deconfigure uglifyjs.terser (broken by terser) | (Reading database ... 4922 files and directories currently installed.) | Preparing to unpack ./terser_5.16.4-1_all.deb ... | De-configuring uglifyjs.terser (4.1.2-8) ... | Unpacking terser (5.16.4-1) ... | dpkg: error processing archive ./terser_5.16.4-1_all.deb (--unpack): | trying to overwrite '/usr/share/nodejs/terser/bin/uglifyjs', which is also in package uglifyjs.terser 4.1.2-8 | Errors were encountered while processing: | ./terser_5.16.4-1_all.deb Please ensure that terser has sufficient Breaks and Replaces declarations. Helmut
Bug#1034968: birdfont-common: missing Breaks+Replaces for birdfont when upgrading from bullseye
Package: birdfont-common Version: 2.32.3-1 Severity: serious Justification: dpkg unpack error Attempting to unpack birdfont-common/2.32.3-1 from Debian bookworm on a minimal Debian bullseye with birdfont/2.29.1-1 installed, causes an unpack error from dpkg due to /usr/share/birdfont/birdfont_window_icon.png being contained in both packages. | Selecting previously unselected package birdfont-common. | dpkg: considering deconfiguration of birdfont, which would be broken by installation of birdfont-common ... | dpkg: yes, will deconfigure birdfont (broken by birdfont-common) | (Reading database ... 17188 files and directories currently installed.) | Preparing to unpack .../birdfont-common_2.32.3-1_all.deb ... | De-configuring birdfont (2.29.1-1) ... | Unpacking birdfont-common (2.32.3-1) ... | dpkg: error processing archive ./birdfont-common_2.32.3-1_all.deb (--unpack): | trying to overwrite '/usr/share/birdfont/birdfont_window_icon.png', which is also in package birdfont 2.29.1-1 | dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) | Processing triggers for libc-bin (2.31-13+deb11u5) ... | Errors were encountered while processing: | ./birdfont-common_2.32.3-1_all.deb Please ensure that birdfont-common has sufficient Breaks and Replaces declarations. Helmut
Bug#1034967: gosa-plugins-systems: missing Breaks+Replaces in multiple situations when upgrading from bullseye
Package: gosa-plugins-systems Version: 2.8~git20211027.5741b8f-3 Severity: serious Justification: dpkg unpack error Attempting to unpack gosa-plugins-systems/2.8~git20211027.5741b8f-3 from Debian bookworm on a minimal Debian bullseye with gosa-plugin-mail/2.7.4+reloaded3-16 installed, causes an unpack error from dpkg due to /usr/share/gosa/plugins/admin/systems/services/imap/class_goImapServer.inc being contained in both packages. | Selecting previously unselected package gosa-plugins-systems. | dpkg: considering deconfiguration of gosa, which would be broken by installation of gosa-plugins-systems ... | dpkg: yes, will deconfigure gosa (broken by gosa-plugins-systems) | dpkg: considering deconfiguration of gosa-plugin-systems, which would be broken by installation of gosa-plugins-systems ... | dpkg: yes, will deconfigure gosa-plugin-systems (broken by gosa-plugins-systems) | (Reading database ... 12813 files and directories currently installed.) | Preparing to unpack .../gosa-plugins-systems_2.8~git20211027.5741b8f-3_all.deb ... | De-configuring gosa-plugin-systems (2.7.4+reloaded3-16) ... | De-configuring gosa (2.7.4+reloaded3-16) ... | Unpacking gosa-plugins-systems (2.8~git20211027.5741b8f-3) ... | Replacing files in old package gosa-plugin-systems (2.7.4+reloaded3-16) ... | dpkg: error processing archive ./gosa-plugins-systems_2.8~git20211027.5741b8f-3_all.deb (--unpack): | trying to overwrite '/usr/share/gosa/plugins/admin/systems/services/imap/class_goImapServer.inc', which is also in package gosa-plugin-mail 2.7.4+reloaded3-16 | apache2_invoke gosa: already enabled | apache2_invoke headers: already enabled | invoke-rc.d: could not determine current runlevel | invoke-rc.d: policy-rc.d denied execution of reload. | Updating class cache... | Updating internationalization... | ! Warning: you may need to reload your webservice! | Updating master image for theme 'default'libpng warning: iCCP: known incorrect sRGB profile | ..libpng warning: iCCP: known incorrect sRGB profile | libpng warning: iCCP: known incorrect sRGB profile | ..libpng warning: iCCP: known incorrect sRGB profile | .libpng warning: iCCP: known incorrect sRGB profile | .libpng warning: iCCP: known incorrect sRGB profile | ... | Calculating master image dimensions: 576x365 | Processinglibpng warning: iCCP: known incorrect sRGB profile | .libpng warning: iCCP: known incorrect sRGB profile | .libpng warning: iCCP: known incorrect sRGB profile | .libpng warning: iCCP: known incorrect sRGB profile | .libpng warning: iCCP: known incorrect sRGB profile | .libpng warning: iCCP: known incorrect sRGB profile | ...libpng warning: iCCP: known incorrect sRGB profile | .libpng warning: iCCP: known incorrect sRGB profile | .libpng warning: iCCP: known incorrect sRGB profile | .libpng warning: iCCP: known incorrect sRGB profile | .libpng warning: iCCP: known incorrect sRGB profile | .libpng warning: iCCP: known incorrect sRGB profile | .Writing styles... | Errors were encountered while processing: | ./gosa-plugins-systems_2.8~git20211027.5741b8f-3_all.deb Attempting to unpack gosa-plugins-systems/2.8~git20211027.5741b8f-3 from Debian bookworm on a minimal Debian bullseye with gosa-plugin-rsyslog/2.7.4+reloaded3-16 installed, causes an unpack error from dpkg due to /usr/share/gosa/plugins/admin/systems/services/rsyslog/class_rSyslogServer.inc being contained in both packages. | Selecting previously unselected package gosa-plugins-systems. | dpkg: considering deconfiguration of gosa, which would be broken by installation of gosa-plugins-systems ... | dpkg: yes, will deconfigure gosa (broken by gosa-plugins-systems) | dpkg: considering deconfiguration of gosa-plugin-systems, which would be broken by installation of gosa-plugins-systems ... | dpkg: yes, will deconfigure gosa-plugin-systems (broken by gosa-plugins-systems) | (Reading database ... 12583 files and directories currently installed.) | Preparing to unpack .../gosa-plugins-systems_2.8~git20211027.5741b8f-3_all.deb ... | De-configuring gosa-plugin-systems (2.7.4+reloaded3-16) ... | De-configuring gosa (2.7.4+reloaded3-16) ... | Unpacking gosa-plugins-systems (2.8~git20211027.5741b8f-3) ... | Replacing files in old package gosa-plugin-systems (2.7.4+reloaded3-16) ... | dpkg: error processing archive ./gosa-plugins-systems_2.8~git20211027.5741b8f-3_all.deb (--unpack): | trying to overwrite
Bug#1034966: pcp-doc: missing Breaks+Replaces for pcp when upgrading from bullseye
Package: pcp-doc Version: 6.0.3-1 Severity: serious Justification: dpkg unpack error Attempting to unpack pcp-doc/6.0.3-1 from Debian bookworm on a minimal Debian bullseye with pcp/5.2.6-1 installed, causes an unpack error from dpkg due to /usr/share/pcp/examples/pcp2spark/PCP2SparkStreamCollector.python being contained in both packages. | Selecting previously unselected package pcp-doc. | dpkg: considering deconfiguration of pcp, which would be broken by installation of pcp-doc ... | dpkg: yes, will deconfigure pcp (broken by pcp-doc) | (Reading database ... 10064 files and directories currently installed.) | Preparing to unpack ./pcp-doc_6.0.3-1_all.deb ... | De-configuring pcp (5.2.6-1) ... | invoke-rc.d: could not determine current runlevel | invoke-rc.d: policy-rc.d denied execution of stop. | invoke-rc.d: could not determine current runlevel | invoke-rc.d: policy-rc.d denied execution of stop. | invoke-rc.d: could not determine current runlevel | invoke-rc.d: policy-rc.d denied execution of stop. | invoke-rc.d: could not determine current runlevel | invoke-rc.d: policy-rc.d denied execution of stop. | Unpacking pcp-doc (6.0.3-1) ... | dpkg: error processing archive ./pcp-doc_6.0.3-1_all.deb (--unpack): | trying to overwrite '/usr/share/pcp/examples/pcp2spark/PCP2SparkStreamCollector.python', which is also in package pcp 5.2.6-1 | invoke-rc.d: could not determine current runlevel | invoke-rc.d: policy-rc.d denied execution of start. | invoke-rc.d: could not determine current runlevel | invoke-rc.d: policy-rc.d denied execution of start. | Errors were encountered while processing: | ./pcp-doc_6.0.3-1_all.deb Please ensure that pcp-doc has sufficient Breaks and Replaces declarations. Helmut
Bug#1034965: libxmlezout10-dev: missing Breaks+Replaces for libxmlezout8-dev when upgrading from bullseye
Package: libxmlezout10-dev Version: 1.06.2-9 Severity: serious Justification: dpkg unpack error Attempting to unpack libxmlezout10-dev/1.06.2-9 from Debian bookworm on a minimal Debian bullseye with libxmlezout8-dev/1.06.2-4+b1 installed, causes an unpack error from dpkg due to /usr/lib/x86_64-linux-gnu/ada/adalib/xmlezout/mckae-xml-ez_out-generic_medium.ali being contained in both packages. | Selecting previously unselected package libxmlezout10-dev. | (Reading database ... 9150 files and directories currently installed.) | Preparing to unpack .../libxmlezout10-dev_1.06.2-9_amd64.deb ... | Unpacking libxmlezout10-dev (1.06.2-9) ... | dpkg: error processing archive ./libxmlezout10-dev_1.06.2-9_amd64.deb (--unpack): | trying to overwrite '/usr/lib/x86_64-linux-gnu/ada/adalib/xmlezout/mckae-xml-ez_out-generic_medium.ali', which is also in package libxmlezout8-dev 1.06.2-4+b1 | Errors were encountered while processing: | ./libxmlezout10-dev_1.06.2-9_amd64.deb Please ensure that libxmlezout10-dev has sufficient Breaks and Replaces declarations. Helmut
Bug#1034963: gnuradio-dev: missing Breaks+Replaces for gr-soapy when upgrading from bullseye
Package: gnuradio-dev Version: 3.10.5.1-2 Severity: serious Justification: dpkg unpack error Attempting to unpack gnuradio-dev/3.10.5.1-2 from Debian bookworm on a minimal Debian bullseye with gr-soapy/2.1.3-2 installed, causes an unpack error from dpkg due to /usr/lib/x86_64-linux-gnu/libgnuradio-soapy.so being contained in both packages. | Selecting previously unselected package gnuradio-dev. | (Reading database ... 7723 files and directories currently installed.) | Preparing to unpack .../gnuradio-dev_3.10.5.1-2_amd64.deb ... | Unpacking gnuradio-dev (3.10.5.1-2) ... | dpkg: error processing archive ./gnuradio-dev_3.10.5.1-2_amd64.deb (--unpack): | trying to overwrite '/usr/lib/x86_64-linux-gnu/libgnuradio-soapy.so', which is also in package gr-soapy 2.1.3-2 | Errors were encountered while processing: | ./gnuradio-dev_3.10.5.1-2_amd64.deb Please ensure that gnuradio-dev has sufficient Breaks and Replaces declarations. Helmut
Bug#1034960: libgmpada12-dev: missing Breaks+Replaces for libgmpada10-dev when upgrading from bullseye
Package: libgmpada12-dev Version: 1.5-6 Severity: serious Justification: dpkg unpack error Attempting to unpack libgmpada12-dev/1.5-6 from Debian bookworm on a minimal Debian bullseye with libgmpada10-dev/1.4-2 installed, causes an unpack error from dpkg due to /usr/lib/x86_64-linux-gnu/ada/adalib/gmpada/gmp-binding.ali being contained in both packages. | Selecting previously unselected package libgmpada12-dev. | (Reading database ... 9197 files and directories currently installed.) | Preparing to unpack .../libgmpada12-dev_1.5-6_amd64.deb ... | Unpacking libgmpada12-dev (1.5-6) ... | dpkg: error processing archive ./libgmpada12-dev_1.5-6_amd64.deb (--unpack): | trying to overwrite '/usr/lib/x86_64-linux-gnu/ada/adalib/gmpada/gmp-binding.ali', which is also in package libgmpada10-dev 1.4-2 | dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) | Errors were encountered while processing: | ./libgmpada12-dev_1.5-6_amd64.deb Please ensure that libgmpada12-dev has sufficient Breaks and Replaces declarations. Helmut
Bug#1034964: libgnatcoll-sqlite21-dev: missing Breaks+Replaces for libgnatcoll-sqlite19-dev when upgrading from bullseye
Package: libgnatcoll-sqlite21-dev Version: 23.0.0-3 Severity: serious Justification: dpkg unpack error Attempting to unpack libgnatcoll-sqlite21-dev/23.0.0-3 from Debian bookworm on a minimal Debian bullseye with libgnatcoll-sqlite19-dev/21.0.0-6 installed, causes an unpack error from dpkg due to /usr/lib/x86_64-linux-gnu/ada/adalib/gnatcoll_sqlite/gnatcoll-sql-sqlite-builder.ali being contained in both packages. | Selecting previously unselected package libgnatcoll-sqlite21-dev. | (Reading database ... 10075 files and directories currently installed.) | Preparing to unpack .../libgnatcoll-sqlite21-dev_23.0.0-3_amd64.deb ... | Unpacking libgnatcoll-sqlite21-dev (23.0.0-3) ... | dpkg: error processing archive ./libgnatcoll-sqlite21-dev_23.0.0-3_amd64.deb (--unpack): | trying to overwrite '/usr/lib/x86_64-linux-gnu/ada/adalib/gnatcoll_sqlite/gnatcoll-sql-sqlite-builder.ali', which is also in package libgnatcoll-sqlite19-dev 21.0.0-6 | Errors were encountered while processing: | ./libgnatcoll-sqlite21-dev_23.0.0-3_amd64.deb Please ensure that libgnatcoll-sqlite21-dev has sufficient Breaks and Replaces declarations. Helmut
Bug#1034962: libg2c-dev: missing Breaks+Replaces for libgrib2c-dev when upgrading from bullseye
Package: libg2c-dev Version: 1.7.0-2 Severity: serious Justification: dpkg unpack error Attempting to unpack libg2c-dev/1.7.0-2 from Debian bookworm on a minimal Debian bullseye with libgrib2c-dev/1.6.2-2 installed, causes an unpack error from dpkg due to /usr/include/grib2.h being contained in both packages. | Selecting previously unselected package libg2c-dev:amd64. | dpkg: considering deconfiguration of libgrib2c-dev:amd64, which would be broken by installation of libg2c-dev:amd64 ... | dpkg: yes, will deconfigure libgrib2c-dev:amd64 (broken by libg2c-dev:amd64) | (Reading database ... 4709 files and directories currently installed.) | Preparing to unpack ./libg2c-dev_1.7.0-2_amd64.deb ... | De-configuring libgrib2c-dev:amd64 (1.6.2-2) ... | Unpacking libg2c-dev:amd64 (1.7.0-2) ... | dpkg: error processing archive ./libg2c-dev_1.7.0-2_amd64.deb (--unpack): | trying to overwrite '/usr/include/grib2.h', which is also in package libgrib2c-dev:amd64 1.6.2-2 | Errors were encountered while processing: | ./libg2c-dev_1.7.0-2_amd64.deb Please ensure that libg2c-dev has sufficient Breaks and Replaces declarations. Helmut
Bug#1034961: librust-mio-0.6-dev: missing Breaks+Replaces for librust-mio-dev when upgrading from bullseye
Package: librust-mio-0.6-dev Version: 0.6.23-2+b1 Severity: serious Justification: dpkg unpack error Attempting to unpack librust-mio-0.6-dev/0.6.23-2+b1 from Debian bookworm on a minimal Debian bullseye with librust-mio-dev/0.6.23-1 installed, causes an unpack error from dpkg due to /usr/share/cargo/registry/mio-0.6.23/.cargo-checksum.json being contained in both packages. | Selecting previously unselected package librust-mio-0.6-dev:amd64. | dpkg: considering deconfiguration of librust-mio-dev:amd64, which would be broken by installation of librust-mio-0.6-dev:amd64 ... | dpkg: yes, will deconfigure librust-mio-dev:amd64 (broken by librust-mio-0.6-dev:amd64) | (Reading database ... 5686 files and directories currently installed.) | Preparing to unpack .../librust-mio-0.6-dev_0.6.23-2+b1_amd64.deb ... | De-configuring librust-mio-dev:amd64 (0.6.23-1) ... | Unpacking librust-mio-0.6-dev:amd64 (0.6.23-2+b1) ... | dpkg: error processing archive ./librust-mio-0.6-dev_0.6.23-2+b1_amd64.deb (--unpack): | trying to overwrite '/usr/share/cargo/registry/mio-0.6.23/.cargo-checksum.json', which is also in package librust-mio-dev:amd64 0.6.23-1 | dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) | Errors were encountered while processing: | ./librust-mio-0.6-dev_0.6.23-2+b1_amd64.deb Please ensure that librust-mio-0.6-dev has sufficient Breaks and Replaces declarations. Helmut
Bug#1034959: libwmf-0.2-7-gtk: missing Breaks+Replaces for libwmf0.2-7-gtk when upgrading from bullseye
Package: libwmf-0.2-7-gtk Version: 0.2.12-5 Severity: serious Justification: dpkg unpack error Attempting to unpack libwmf-0.2-7-gtk/0.2.12-5 from Debian bookworm on a minimal Debian bullseye with libwmf0.2-7-gtk/0.2.8.4-17 installed, causes an unpack error from dpkg due to /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders/io-wmf.so being contained in both packages. | Selecting previously unselected package libwmf-0.2-7-gtk. | (Reading database ... 5413 files and directories currently installed.) | Preparing to unpack .../libwmf-0.2-7-gtk_0.2.12-5_amd64.deb ... | Unpacking libwmf-0.2-7-gtk (0.2.12-5) ... | dpkg: error processing archive ./libwmf-0.2-7-gtk_0.2.12-5_amd64.deb (--unpack): | trying to overwrite '/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders/io-wmf.so', which is also in package libwmf0.2-7-gtk 0.2.8.4-17 | Processing triggers for libgdk-pixbuf-2.0-0:amd64 (2.42.2+dfsg-1+deb11u1) ... | Errors were encountered while processing: | ./libwmf-0.2-7-gtk_0.2.12-5_amd64.deb Please ensure that libwmf-0.2-7-gtk has sufficient Breaks and Replaces declarations. Helmut
Bug#1034958: manpages-dev: missing Breaks+Replaces for inn2-dev when upgrading from bullseye
Package: manpages-dev Version: 6.03-1 Severity: serious Justification: dpkg unpack error Attempting to unpack manpages-dev/6.03-1 from Debian bookworm on a minimal Debian bullseye with inn2-dev/2.6.4-2 installed, causes an unpack error from dpkg due to /usr/share/man/man3/list.3.gz being contained in both packages. | Selecting previously unselected package manpages-dev. | (Reading database ... 4741 files and directories currently installed.) | Preparing to unpack ./manpages-dev_6.03-1_all.deb ... | Unpacking manpages-dev (6.03-1) ... | dpkg: error processing archive ./manpages-dev_6.03-1_all.deb (--unpack): | trying to overwrite '/usr/share/man/man3/list.3.gz', which is also in package inn2-dev 2.6.4-2 | dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) | Errors were encountered while processing: | ./manpages-dev_6.03-1_all.deb Please ensure that manpages-dev has sufficient Breaks and Replaces declarations. Helmut
Bug#1034957: qtxdg-tools: missing Breaks+Replaces for qtxdg-dev-tools when upgrading from bullseye
Package: qtxdg-tools Version: 3.10.0-1 Severity: serious Justification: dpkg unpack error Attempting to unpack qtxdg-tools/3.10.0-1 from Debian bookworm on a minimal Debian bullseye with qtxdg-dev-tools/3.6.0-1 installed, causes an unpack error from dpkg due to /usr/bin/qtxdg-mat being contained in both packages. | Selecting previously unselected package qtxdg-tools. | (Reading database ... 9080 files and directories currently installed.) | Preparing to unpack .../qtxdg-tools_3.10.0-1_amd64.deb ... | Unpacking qtxdg-tools (3.10.0-1) ... | dpkg: error processing archive ./qtxdg-tools_3.10.0-1_amd64.deb (--unpack): | trying to overwrite '/usr/bin/qtxdg-mat', which is also in package qtxdg-dev-tools 3.6.0-1 | Errors were encountered while processing: | ./qtxdg-tools_3.10.0-1_amd64.deb Please ensure that qtxdg-tools has sufficient Breaks and Replaces declarations. Helmut
Bug#1034956: libeztrace0: missing Breaks+Replaces for libeztrace-dev when upgrading from bullseye
Package: libeztrace0 Version: 2.0+repack-11 Severity: serious Justification: dpkg unpack error Attempting to unpack libeztrace0/2.0+repack-11 from Debian bookworm on a minimal Debian bullseye with libeztrace-dev/1.1-10-2 installed, causes an unpack error from dpkg due to /usr/lib/x86_64-linux-gnu/libeztrace-memory.so being contained in both packages. | (Reading database ... 5608 files and directories currently installed.) | Preparing to unpack .../libeztrace0_2.0+repack-11_amd64.deb ... | Unpacking libeztrace0:amd64 (2.0+repack-11) over (1.1-10-2) ... | dpkg: error processing archive ./libeztrace0_2.0+repack-11_amd64.deb (--unpack): | trying to overwrite '/usr/lib/x86_64-linux-gnu/libeztrace-memory.so', which is also in package libeztrace-dev:amd64 1.1-10-2 | dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) | Processing triggers for libc-bin (2.31-13+deb11u5) ... | Errors were encountered while processing: | ./libeztrace0_2.0+repack-11_amd64.deb Please ensure that libeztrace0 has sufficient Breaks and Replaces declarations. Helmut
Bug#1034954: python3-meep-mpi-default: missing Breaks+Replaces in multiple situations when upgrading from bullseye
Package: python3-meep-mpi-default Version: 1.25.0-1+b1 Severity: serious Justification: dpkg unpack error Attempting to unpack python3-meep-mpi-default/1.25.0-1+b1 from Debian bookworm on a minimal Debian bullseye with python3-meep-openmpi/1.17.1-2 installed, causes an unpack error from dpkg due to /usr/lib/python3/dist-packages/meep/__init__.py being contained in both packages. | Selecting previously unselected package python3-meep-mpi-default. | (Reading database ... 9458 files and directories currently installed.) | Preparing to unpack .../python3-meep-mpi-default_1.25.0-1+b1_amd64.deb ... | Unpacking python3-meep-mpi-default (1.25.0-1+b1) ... | dpkg: error processing archive ./python3-meep-mpi-default_1.25.0-1+b1_amd64.deb (--unpack): | trying to overwrite '/usr/lib/python3/dist-packages/meep/__init__.py', which is also in package python3-meep-openmpi 1.17.1-2 | dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) | Processing triggers for libc-bin (2.31-13+deb11u5) ... | Errors were encountered while processing: | ./python3-meep-mpi-default_1.25.0-1+b1_amd64.deb Attempting to unpack python3-meep-mpi-default/1.25.0-1+b1 from Debian bookworm on a minimal Debian bullseye with python3-meep/1.17.1-1 installed, causes an unpack error from dpkg due to /usr/lib/python3/dist-packages/meep/__init__.py being contained in both packages. | Selecting previously unselected package python3-meep-mpi-default. | (Reading database ... 8718 files and directories currently installed.) | Preparing to unpack .../python3-meep-mpi-default_1.25.0-1+b1_amd64.deb ... | Unpacking python3-meep-mpi-default (1.25.0-1+b1) ... | dpkg: error processing archive ./python3-meep-mpi-default_1.25.0-1+b1_amd64.deb (--unpack): | trying to overwrite '/usr/lib/python3/dist-packages/meep/__init__.py', which is also in package python3-meep 1.17.1-1 | dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) | Processing triggers for libc-bin (2.31-13+deb11u5) ... | Errors were encountered while processing: | ./python3-meep-mpi-default_1.25.0-1+b1_amd64.deb Please ensure that python3-meep-mpi-default has sufficient Breaks and Replaces declarations. Helmut
Bug#1034955: slurm-wlm-influxdb-plugin: missing Breaks+Replaces for slurm-wlm-basic-plugins when upgrading from bullseye
Package: slurm-wlm-influxdb-plugin Version: 22.05.8-3 Severity: serious Justification: dpkg unpack error Attempting to unpack slurm-wlm-influxdb-plugin/22.05.8-3 from Debian bookworm on a minimal Debian bullseye with slurm-wlm-basic-plugins/20.11.7+really20.11.4-2+deb11u1 installed, causes an unpack error from dpkg due to /usr/lib/x86_64-linux-gnu/slurm-wlm/acct_gather_profile_influxdb.so being contained in both packages. | Selecting previously unselected package slurm-wlm-influxdb-plugin. | (Reading database ... 5770 files and directories currently installed.) | Preparing to unpack .../slurm-wlm-influxdb-plugin_22.05.8-3_amd64.deb ... | Unpacking slurm-wlm-influxdb-plugin (22.05.8-3) ... | dpkg: error processing archive ./slurm-wlm-influxdb-plugin_22.05.8-3_amd64.deb (--unpack): | trying to overwrite '/usr/lib/x86_64-linux-gnu/slurm-wlm/acct_gather_profile_influxdb.so', which is also in package slurm-wlm-basic-plugins 20.11.7+really20.11.4-2+deb11u1 | Errors were encountered while processing: | ./slurm-wlm-influxdb-plugin_22.05.8-3_amd64.deb Please ensure that slurm-wlm-influxdb-plugin has sufficient Breaks and Replaces declarations. Helmut
Bug#1034953: libslopy-dev: missing Breaks+Replaces for slop when upgrading from bullseye
Package: libslopy-dev Version: 7.6-3+b1 Severity: serious Justification: dpkg unpack error Attempting to unpack libslopy-dev/7.6-3+b1 from Debian bookworm on a minimal Debian bullseye with slop/7.5-1+b1 installed, causes an unpack error from dpkg due to /usr/include/slop.hpp being contained in both packages. | Selecting previously unselected package libslopy-dev. | (Reading database ... 5263 files and directories currently installed.) | Preparing to unpack .../libslopy-dev_7.6-3+b1_amd64.deb ... | Unpacking libslopy-dev (7.6-3+b1) ... | dpkg: error processing archive ./libslopy-dev_7.6-3+b1_amd64.deb (--unpack): | trying to overwrite '/usr/include/slop.hpp', which is also in package slop 7.5-1+b1 | Errors were encountered while processing: | ./libslopy-dev_7.6-3+b1_amd64.deb Please ensure that libslopy-dev has sufficient Breaks and Replaces declarations. Helmut
