Re: Automatic trimming of changelogs in binary packages
* Hakan Bayındır <email@example.com> [220914 03:41]:
> > On 14 Sep 2022, at 10:37, Wouter Verhelst <firstname.lastname@example.org> wrote:
> > On Sun, Sep 11, 2022 at 03:09:07PM +0300, Hakan Bayındır wrote:
> >> Yes, you’re right. However, my reservation is whether dpkg is more prone to
> >> breaking in disaster recovery scenarios. Reading a gzipped file is always
> >> simpler than querying a DB via more abstraction.
> > Honestly though, the way to track down a regression is to read
> > /var/log/dpkg.log, not changelogs.
> Does /var/log/dpkg.log contain why my VPNs suddenly don’t connect or
> my daemon behaves differently after the last update? I thought they’re
> delivered through news and changelogs.
> Actually, OpenVPN’s changing defaults are nicely delivered through
> NEWS and changelogs, so I know why things broke at the first place.
And the trimmed changelogs are unlikely to alter that at all. The
probability that the change that caused your VPN to break will have been
trimmed are close to zero. If it has been trimmed, it means you haven't
upgraded in more than two releases, and yes, you will have to get the
untrimmed changelog using apt changelog.