I finally took some time to try and reproduce the described bug, but got no success with that. Here is how it happened for me: 1. I create a bookworm chroot with network-manager-gnome installed in it. 2. I check that network-manager-gnome is marked as manually installed. 3. I update the sources, and upgrade the systen to Trixie. As expected, network-manager-applet is pulled as a dependency. 4. I check that network-manager-gnome is a candidate for removal. And at step 4. is where I get a difference: while network-manager-gnome is indeed a candidate for removal, network-manager-applet on the other hand is not. So this package inherited the "manually installed" status from its parent package. The end result is that the obsolete package is removed, and the new package replacing it is kept. Exactly what we want. Finding configuration differences between the system where this bug has been noticed and the chroot I used to try (and fail) to reproduce it might tell use what trigger the unwanted autoremoval. If it can help, here is how I generated the chroot used to run my tests: mmdebstrap --aptopt='Acquire::http::Proxy "http://apt.vv221.fr:3142";' --include=network-manager-gnome bookworm /tmp/test-chroot http://mirror.gitoyen.net/debian Removing options that are specific to my system, that would become: mmdebstrap --include=network-manager-gnome bookworm /tmp/test-chroot The only commands run in that chroot are: apt-mark showmanual network-manager-gnome sed -i 's/bookworm/trixie/g' /etc/apt/sources.list apt-get update apt-get full-upgrade apt-get autoremove apt-mark showmanual network-manager-applet
Attachment:
signature.asc
Description: PGP signature