Re: Why apt suddenly lists packages from "stable-backports" as upgrade candidates for packages from "stable"?

["Alexander V. Makartsev" <avbetev@gmail.com>]

On 03.12.2025 07:29, Max Nikulin wrote:

> On
>       03/12/2025 01:39, Alexander V. Makartsev wrote:
>       
> > It lists packages from "stable-backports"
> >         as upgrade candidates for packages from "stable".
> >         
> >       
>       [...]
>       
> > $ cat
> >         /etc/apt/sources.list.d/debian.sources
> >         
> >       
>       
>       "apt policy" (*without* package name) might help to reveal other
>       files or preferences like improper Default-Release.
>       
>       
>     
    Thanks for the tip.
    
    $ apt policy
    Package files:
    ...
     500 https://security.debian.org/debian-security
    trixie-security/main amd64 Packages
         release
v=13,o=Debian,a=stable-security,n=trixie-security,l=Debian-Security,c=main,b=amd64
         origin security.debian.org
    ... 
     100 https://deb.debian.org/debian trixie-backports/main amd64
    Packages
         release o=Debian
    Backports,a=stable-backports,n=trixie-backports,l=Debian
    Backports,c=main,b=amd64
         origin deb.debian.org
    ...
     500 https://deb.debian.org/debian trixie-proposed-updates/main
    amd64 Packages
         release
v=13-updates,o=Debian,a=proposed-updates,n=trixie-proposed-updates,l=Debian,c=main,b=amd64
         origin deb.debian.org
    ...
     500 https://deb.debian.org/debian trixie-updates/main amd64
    Packages
         release
v=13-updates,o=Debian,a=stable-updates,n=trixie-updates,l=Debian,c=main,b=amd64
         origin deb.debian.org
    ...
     500 https://deb.debian.org/debian trixie/main amd64 Packages
         release
    v=13.2,o=Debian,a=stable,n=trixie,l=Debian,c=main,b=amd64
         origin deb.debian.org
    ...
     
    Somehow "trixie-proposed-updates" gets priority 500 which is wrong
    and it should be treated like "trixie-backports" with lower
    priority.
    I don't see the difference between them, if there is no guarantee
    that packages will not vanish from there.
    
>       
>       Perhaps apt can not distinguish cases when some package version is
>       removed from backports and from proposed updates, so it just picks
>       100 (locally installed and missed in repositories) to 100
>       (backports) upgrade.
>       
>       
>     
    I will pin everything from "trixie-proposed-updates" to lower
    priority, so packages from this source won't be considered as
    candidates. 
    And wait long enough to get candidate versions from
    "stable-updates".
    Probably it is good idea to report somewhere about this issue, so it
    gets a proper fix.

--

 With kindest regards, Alexander.

 Debian - The universal operating system
 https://www.debian.org