Bug#1136641: debian-policy: do not require shared libraries to change package name with soname changes

Andrey Rakhmatullin <[email protected]> Fri, 15 May 2026 16:58:55 +0500

Newsgroups	gmane.linux.debian.devel.policy
Message-ID	<agcKfxaenB4gkYkA__26675.5469305039$1778846489$gmane$org@belkar.wrar.name>

On Fri, May 15, 2026 at 01:00:13PM +0200, Bill Allombert wrote:
>During an upgrade even if the file libfoo.so.N is removed, programs
>linked against libfoo.so.N might still be running and might still attempt to
>access files in libfoo-common or libfoo-bin.

I'm afraid that this is a well-known source of problems, and not 
restarting these programs is not supported in practice, whatever our 
Policy tries to do or not. It's so bad that there are
initiatives for upgrading packages only in single-user environment: 
https://docs.fedoraproject.org/en-US/kde/offlineupdates/

-- 
WBR, wRAR

signature.asc (application/pgp-signature, 894 B)