Your message dated Fri, 18 Jul 2025 17:24:38 +0200 with message-id <aHpnNjeGzmiSMODW@fenchel> and subject line Re: Bug#1070258: release-notes: Approach to managing other package managers when upgrading needs documentation has caused the Debian Bug report #1070258, regarding release-notes: Approach to managing other package managers when upgrading needs documentation 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 owner@bugs.debian.org immediately.) -- 1070258: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070258 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: release-notes: Approach to managing other package managers when upgrading needs documentation
- From: Manny <debbug.release-notes@sideload.33mail.com>
- Date: Thu, 2 May 2024 22:34:30 +0200
- Message-id: <20240502203430.zobgshwdhn3jfcl5@cypher.ruins>
Package: release-notes Severity: normal X-Debbugs-Cc: debbug.release-notes@sideload.33mail.com One of the ways I got burnt in the Bullseye → Bookworm full-upgrade is documented here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070203 There was no signal given before, during, or after the upgrade warning that the non-debian python app “argostranslate” would be ruined. It was just a surprise the next time the app was needed that it no longer functioned. I’m not sure if the release notes could give any detailed guidance, but users should probably be instructed to minimally become aware of packages that are at risk. These existing sections are probably relevant: 4.2.6. Remove non-Debian packages 4.2.13. Check package status Perhaps users should probably be instructed to run: $ pip list $ pip3 list $ pipx list to at least become aware of non-Debian packages that might be impacted so they can be reminded to give some thought to it. IMO it’s sensible to save the lists from that output to a file and then refer to it post-upgrade to test these fragile apps so the nasty surprise of lost functionality does not manifest at the time that they need to use it, which is about the worst time to discover the loss. Rust also has its own package manager (cargo), as does emacs. I have no idea if they have the same special needs that pip does. I don’t think cargo gives a listing mechanism so perhaps nothing can be done there.
--- End Message ---
--- Begin Message ---
- To: Justin B Rye <justin.byam.rye@gmail.com>, 1070258-done@bugs.debian.org
- Cc: Manny <debbug.release-notes@sideload.33mail.com>
- Subject: Re: Bug#1070258: release-notes: Approach to managing other package managers when upgrading needs documentation
- From: Jochen Sprickerhof <jspricke@debian.org>
- Date: Fri, 18 Jul 2025 17:24:38 +0200
- Message-id: <aHpnNjeGzmiSMODW@fenchel>
- In-reply-to: <Zje1F_aQlcQmyvdD@jbr.me.uk>
- References: <20240502203430.zobgshwdhn3jfcl5@cypher.ruins> <20240502203430.zobgshwdhn3jfcl5@cypher.ruins> <Zje1F_aQlcQmyvdD@jbr.me.uk>
* Justin B Rye <justin.byam.rye@gmail.com> [2024-05-05 17:34]:Manny wrote:One of the ways I got burnt in the Bullseye → Bookworm full-upgrade is documented here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070203 There was no signal given before, during, or after the upgrade warning that the non-debian python app “argostranslate” would be ruined. It was just a surprise the next time the app was needed that it no longer functioned.The Debian package-management system can never guarantee that software it doesn't know about will continue to work through an upgrade (even to a new backport kernel, never mind a whole new stable release).Agreed and the release-notes is not the place to document third party systems apart from what is in section 4 already, thus closing.Cheers JochenAttachment: signature.asc
Description: PGP signature
--- End Message ---