Hi Charles,
Charles Curley <charlescurley@charlescurley.com> writes:
> On Thu, 14 Aug 2025 17:44:55 -0700
> Xiyue Deng <manphiz@gmail.com> wrote:
>
>> So I have a laptop that recently upgraded from Bookworm to Trixie
>> without issues. Only that, unlike my other box (which also upgraded
>> from Bookworm to Trixie and has a working unattended-upgrade), I found
>> that all recent security updates are not upgraded automatically here.
>> It turns out that unattended-upgrade seems to still be tracking
>> Bookworm.
>
> You've said nothing about /etc/apt. That is where the current version
> of Debian is set for the purpose of updates. I suspect an incomplete
> dist-upgrade.
>
> Try the following. If it turns up anything that isn't a backup file,
> that is your problem file(s).
>
> find /etc/apt -type f | xargs grep -i bookworm
>
> Fix that, and retrace your upgrade steps.
>
Thanks for your reply and pointers!
An incomplete dist-upgrade is possible but quite unlikely, as I followed
the Trixie release notes and performed the recommended stages of
upgrading:
,----
| # apt update
| # apt upgrade --without-new-pkgs
| # apt dist-upgrade
`----
And for files under /etc/apt:
,----
| $ find /etc/apt -type f | xargs grep -i bookworm
| /etc/apt/sources.list:#deb cdrom:[Official Debian GNU/Linux Live 12.11.0 lxqt 2025-05-17T09:13:04Z]/ bookworm main non-free-firmware
`----
For completeness, below is the output of `apt policy' which I cannot see
any mentions of bookworm:
,----
| $ apt policy
| Package files:
| 100 /var/lib/dpkg/status
| release a=now
| 500 https://dl.google.com/linux/chrome/deb stable/main amd64 Packages
| release v=1.0,o=Google LLC,a=stable,n=stable,l=Google,c=main,b=amd64
| origin dl.google.com
| 500 http://dl.google.com/linux/chrome-remote-desktop/deb stable/main amd64 Packages
| release v=1.0,o=Google LLC,a=stable,n=stable,l=Google,c=main,b=amd64
| origin dl.google.com
| 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 http://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
| 500 https://deb.debian.org/debian trixie/non-free-firmware amd64 Packages
| release v=13.0,o=Debian,a=stable,n=trixie,l=Debian,c=non-free-firmware,b=amd64
| origin deb.debian.org
| 500 https://deb.debian.org/debian trixie/non-free amd64 Packages
| release v=13.0,o=Debian,a=stable,n=trixie,l=Debian,c=non-free,b=amd64
| origin deb.debian.org
| 500 https://deb.debian.org/debian trixie/contrib amd64 Packages
| release v=13.0,o=Debian,a=stable,n=trixie,l=Debian,c=contrib,b=amd64
| origin deb.debian.org
| 500 https://deb.debian.org/debian trixie/main amd64 Packages
| release v=13.0,o=Debian,a=stable,n=trixie,l=Debian,c=main,b=amd64
| origin deb.debian.org
| Pinned packages:
`----
According to `/etc/apt/apt.conf.d/50unattended-upgrades', it checks
the `/etc/debian_version' file for ${distro_id} and ${distro_codename},
but both of my Trixie systems only have "13.0" in that file, so that's
not the cause either. It must got bookworm as ${distro_codename}
somehow, but I still cannot figure it out.
> --
> Does anybody read signatures any more?
>
> https://charlescurley.com
> https://charlescurley.com/blog/
>
--
Regards,
Xiyue Deng
Attachment:
signature.asc
Description: PGP signature