On Sat, 16 Nov 2024, Patrice Duroux wrote:
That's why I ended up with the suffix and letting the sysadmin
(often me, with a different hat on ;-) making that preference
explicit in the APT machinery.
But could it be the a nice feature for apt to have a list apart on the upgrading
(I would say then 'replacing') of such cases?
User can be alerted more easily during apt upgrade that some packages with a
same version could be replaced by the Debian archive ones.
apt list --replaceable
apt upgrade --no-replaceable
:-)
Note that it could be replacement from configured alternative source archives.
But pinning does this for you.
Pin your local packages at >500 and they will not be replaced (assuming
defaults).
Although having the same version number is, IMO, a bug and apt may
behave 'oddly' - I haven't tried.
If I patch a bookworm package then it gets a +~tjw12r1 added to the
version. This is higher than the one in official debian but (hopefully)
lower than any new version in debian.
And my local repo is pinned at 995, so a new, higher version in debian
doesn't replace my version unless I force it.
