Hi, On Sid, building and installing locally modified packages for testing at the same version as in the archive, I am surprised that apt upgrade will reinstall any of those installed by the one from the archive. I did not remember such a "feature" in the past, unless my memory plays tricks on me:-).
Moreover, this is done without notifying "such dangerous case" to the user but just like usual upgrading.It could be interesting to alert on such upgrades if this was expected for security reasons (ie. not matching some signature of the official package). When there are many packages to upgrade it is difficult to see such cases in the list and may lose the one locally installed. Regards, Patrice patrice@kos-moceratops ~/l/debian> sudo dpkg -i pcsxr_1.9.94-6_amd64.deb (Reading database ... 723322 files and directories currently installed.) Preparing to unpack pcsxr_1.9.94-6_amd64.deb ... Unpacking pcsxr (1.9.94-6) over (1.9.94-6) ... Setting up pcsxr (1.9.94-6) ... Processing triggers for mailcap (3.74) ... Processing triggers for gnome-menus (3.36.0-1.1+b3) ... Processing triggers for desktop-file-utils (0.27-2) ... Processing triggers for man-db (2.13.0-1) ... patrice@kos-moceratops ~/l/debian> sudo apt upgrade ... Upgrading: pcsxr Summary: Upgrading: 1, Installing: 0, Removing: 0, Not Upgrading: 0 Download size: 666 kB Freed space: 24.6 kB Continue? [Y/n] Get:1 https://deb.debian.org/debian sid/main amd64 pcsxr amd64 1.9.94-6 [666 kB] Fetched 666 kB in 0s (1863 kB/s) (Reading database ... 723322 files and directories currently installed.) Preparing to unpack .../pcsxr_1.9.94-6_amd64.deb ... Unpacking pcsxr (1.9.94-6) over (1.9.94-6) ... Setting up pcsxr (1.9.94-6) ... Processing triggers for desktop-file-utils (0.27-2) ... Processing triggers for gnome-menus (3.36.0-1.1+b3) ... Processing triggers for man-db (2.13.0-1) ... Processing triggers for mailcap (3.74) ... Scanning processes... Scanning processor microcode... Scanning linux images... Running kernel seems to be up-to-date. The processor microcode seems to be up-to-date. No services need to be restarted. No containers need to be restarted. No user sessions are running outdated binaries. No VM guests are running outdated hypervisor (qemu) binaries on this host.
