Your message dated Tue, 6 Aug 2024 21:28:15 +0200 with message-id <[email protected]> and subject line Re: Bug#1060700: Requesting advice regarding the impact of problems caused by aliasing on declared Conflicts has caused the Debian Bug report #1058937, regarding Conflicts with libnfsidmap{2,-regex} involving aliased file locations 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 [email protected] immediately.) -- 1058937: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058937 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: libnfsidmap1 Version: 1:2.5.4-1~exp1 Severity: serious As receently disvovered by Helmut Grohne, a conflict between binary packages does not ensure that the files of one will be removed before the files of the other are installed. This can result in file loss when the conflict involves aliased filenames rather than exactly the same filenames. This specific scenario exists when installing libnfsidmap1 as a replacement for libnfsidmap{2,-regex} packages. I was able to reproduce it with the following sequence of commands in a minimal bullseye amd64 chroot: # apt -y install usrmerge # apt -y install libnfsidmap{2,-regex} # sed -i 's/bullseye/bookworm/' /etc/apt/sources.list # apt update # apt -d -y install libnfsidmap1 # (cd /var/cache/apt/archives && \ dpkg -i libc{6,-bin}_2.36-9+deb12u3_amd64.deb \ libsasl2-{2,modules-db}_2.1.28+dfsg-10_amd64.deb \ libgmp10_2%3a6.2.1+dfsg1-1.1_amd64.deb \ libgnutls30_3.7.9-2_amd64.deb libldap-2.5-0_2.5.13+dfsg-5_amd64.deb) # dpkg -i /var/cache/apt/archives/libnfsidmap1_1%3a2.6.2-4_amd64.deb Ben.
--- End Message ---
--- Begin Message ---Control: tags -1 + wontfix On Wed, Jan 17, 2024 at 03:07:38PM +0100, Helmut Grohne wrote: > So all the evidence I found confirms the guess that the problem cannot > be observed with apt unless mutual conflicts exist. On the flip side, > simply installing a package that declares Conflicts occasionally > triggers this and if you happen to do this to a package that replaces > aliased files, then your files vanish. We now have more experience with similar cases. Some maintainers - including systemd - refused using protective diversions on the grounds that Conflicts should be good enough and that upgrades without apt are not supported. Practically speaking, the emerged consensus seems to more and more be that the extra cost of mitigating such cases is not warranted given the estimated risk. It seems very likely that we will not be able to handle all upgrades correctly and instead try to strike a good balance of getting the majority of upgrades right and providing tools to detect failure. As such, I am closing this bug to be consistent with other packages that also do not mitigate similar file loss scenarios. Please reopen if you disagree and we'll look into providing patches. Helmut
--- End Message ---
