Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.bugs.dist > #1186701
| From | Matthew Vernon <matthewv@chiark.greenend.org.uk> |
|---|---|
| Newsgroups | linux.debian.bugs.dist |
| Subject | Bug#1060700: Requesting advice regarding the impact of problems caused by aliasing on declared Conflicts |
| Date | 2024-02-19 11:00 +0100 |
| Message-ID | <I98Bk-baK3-9@gated-at.bofh.it> (permalink) |
| References | <HVGCR-2KMn-1@gated-at.bofh.it> <HVGCR-2KMn-1@gated-at.bofh.it> <HXeVP-3Ipv-5@gated-at.bofh.it> <HVGCR-2KMn-1@gated-at.bofh.it> <HXeVP-3Ipv-5@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On 17/01/2024 14:07, Helmut Grohne wrote: > I somehow missed how Ben's libnfsidmap bug #1058937 works slightly > simpler. Given that $second has a conflict with the installed version of > $first, one can skip that second step and instead install $second > directly with dpkg -i. So no, this weird selections stuff is not > technically necessary. To check I have understood correctly: one may see loss of files when doing dpkg -i of a package where it Conflicts: with an installed package? If that's so, then I think it increases my unhappyness about this situation. I can understand "do upgrades with apt, that's the tooling for the job", and we had already talked about adding something to release notes to describe what manual actions that one might take during an upgrade were dangerous, but "dpkg -i foo.deb where foo.deb Conflicts with something you have installed" seems like the sort of thing one really might reasonably do during an upgrade that has got stuck for some reason or other. Regards, Matthew
Back to linux.debian.bugs.dist | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Bug#1060700: Requesting advice regarding the impact of problems caused by aliasing on declared Conflicts Helmut Grohne <helmut@subdivi.de> - 2024-01-13 08:30 +0100
Bug#1058937: Bug#1060700: Requesting advice regarding the impact of problems caused by aliasing on declared Conflicts Helmut Grohne <helmut@subdivi.de> - 2024-01-17 15:20 +0100
Bug#1060700: Requesting advice regarding the impact of problems caused by aliasing on declared Conflicts Matthew Vernon <matthewv@chiark.greenend.org.uk> - 2024-02-19 11:00 +0100
Bug#1060700: Requesting advice regarding the impact of problems caused by aliasing on declared Conflicts Helmut Grohne <helmut@subdivi.de> - 2024-02-19 12:20 +0100
Bug#1060700: Requesting advice regarding the impact of problems caused by aliasing on declared Conflicts Sam Hartman <hartmans@debian.org> - 2024-01-17 17:40 +0100
Bug#1060700: Requesting advice regarding the impact of problems caused by aliasing on declared Conflicts Helmut Grohne <helmut@subdivi.de> - 2024-01-17 18:40 +0100
Bug#1060700: Requesting advice regarding the impact of problems caused by aliasing on declared Conflicts Matthew Vernon <matthewv@chiark.greenend.org.uk> - 2024-02-19 11:00 +0100
Bug#1060700: Requesting advice regarding the impact of problems caused by aliasing on declared Conflicts Helmut Grohne <helmut@subdivi.de> - 2024-02-19 12:20 +0100
Bug#1060700: Requesting advice regarding the impact of problems caused by aliasing on declared Conflicts Sam Hartman <hartmans@debian.org> - 2024-02-20 16:30 +0100
Bug#1060700: Requesting advice regarding the impact of problems caused by aliasing on declared Conflicts Russ Allbery <rra@debian.org> - 2024-02-20 17:20 +0100
csiph-web