On Tue 03 Nov 2026 at 23:39:30 (+0500), Alexander V. Makartsev wrote: > On 11/3/26 21:21, Franco Martelli wrote: > > > > I running in trouble retrieving the changelog of the latest > > kernel, the previous is OK (6.12.113+1) but not the latest: > > ... > > does anybody know the reason? > > > > Thank you very much for any answer, kind regards, > For me the changelog always appears to be delayed for a few days, when > the newly released package is coming from "stable-security" > repository. > Probably the changelog becomes available when the package is > transferred to "main" repository. > I always thought it is like that to not disclose any information about > vulnerability or a security issue.
IIUC, the changelog is in the package, and not hidden at all. I usually glance at it with mc (midnight commander): press Return when the cursor is on the .deb file: linux-image-6.12.115+deb13.1-amd64_6.12.115-2_amd64.deb then navigate to: CONTENTS/usr/share/doc/linux-image-6.12.115+deb13.1-amd64/changelog.gz Of course, if you've already installed the package, it's at: /usr/share/doc/linux-image-6.12.115+deb13.1-amd64/changelog.gz I don't know how automated or timely the generation of the metadata files such as https://metadata.ftp-master.debian.org/changelogs//main/l/linux-signed-amd64/linux-signed-amd64_6.12.115+2_changelog is, because I only use them (occasionally) for packages I see mentioned here or on the web, whereas security updates will usually be downloaded to APT's cache already, by a regular cron job. Cheers, David.
