Bug#1064838: New package names break APT safety features, ability to co-install different ABIs
On Mon, Feb 26, 2024 at 02:20:41PM +0100, Julian Andres Klode wrote:
> After we had discussed the new proposal a couple months ago and were
> left with severe open questions and concerns it seems that these have
> been ignored and the packages uploaded anyway, breaking APT's algorithm
> that ensures the currently booted kernel is not offered for removal, as
> well as possibly others.
The change for that is not even in. Where do you see it?
| $ dpkg -l linux-image-$(uname -r)
| Desired=Unknown/Install/Remove/Purge/Hold
| | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
| |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
| ||/ Name Version Architecture Description
| +++-===========================-============-============-===================================
| ii linux-image-6.7-cloud-amd64 6.7.4-1~exp1 amd64 Linux 6.7 for x86-64 cloud (signed)
Also #1060109 is still unanswered.
> In addition, this means that the ABI changes within the same package
> names, causing different ABIs to no longer be co-installable, which can
> have drastic effect on thef function of systems:
I asked you several times now: please show a problem. And I also told
you this does not work within the confines of Debian. And neither did
the kernel team provide this guarantee in the past.
So I only see a way forward by preserving modules outside of the normal
package lifecycle. Something that is ephemeral and so cleaned up
automatically on shutdown.
Bastian
--
Spock: The odds of surviving another attack are 13562190123 to 1, Captain.
Reply to: