Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.bugs.rc > #383583
| From | Helmut Grohne <helmut@subdivi.de> |
|---|---|
| Newsgroups | linux.debian.bugs.rc |
| Subject | Bug#1095202: nfs-common: file loss in upgrade due to /usr-move (DEP17 P1) |
| Date | 2025-02-05 08:40 +0100 |
| Message-ID | <KcIaR-ewCX-5@gated-at.bofh.it> (permalink) |
| Organization | linux.* mail to news gateway |
[Multipart message — attachments visible in raw view] - view raw
Package: nfs-common Version: 1:2.8.2-2~exp1 Severity: serious Justification: file loss in upgrade scenario Tags: patch User: helmutg@debian.org Usertags: dep17p1 Hi Salvatore, thanks for raising nfs-common ahead of upload and going via experimental. Indeed, dumat flags /usr/lib/systemd/system/nfs-blkmap.service as a file possibly lost in an upgrade. To experience this loss, you should install nfs-kernel-server from bookworm and then unpack nfs-common from experimental before upgrading nfs-kernel-server. I am proposing a composite mitigation. Upgrading Breaks+Replaces to Conflicts mostly prevents concurrent unpacks except in rare circumstances. Indeed, my testing reveals that this causes apt to upgrade nfs-kernel-server before nfs-common in one of the relevant scenarios. Rarely, dpkg may unpack nfs-common before nfs-kernel-server despite the declared conflict. In this situation, a protective diversion will prevent the file loss. I am attaching a patch and my test cases for your convenience. If you replace the package version with the one from the archive, you should see it fail. Helmut
Back to linux.debian.bugs.rc | Previous | Next — Next in thread | Find similar | Unroll thread
Bug#1095202: nfs-common: file loss in upgrade due to /usr-move (DEP17 P1) Helmut Grohne <helmut@subdivi.de> - 2025-02-05 08:40 +0100 Bug#1095202: marked as done (nfs-common: file loss in upgrade due to /usr-move (DEP17 P1)) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2025-02-05 17:00 +0100
csiph-web