Retrieve changes that closed a Debian bug
If a Debian bug number is referenced in the changelog of an uploaded package, it is automatically closed with a generic message:
We believe that the bug you reported is fixed in the latest version of [package], which is due to be installed in the Debian FTP archive:
This message also contains the new changelog entries, which helps having an idea of what was fixed, but is not as insightful as seeing the whole changes under debian/, especially if a patch was created or updated.
Is there a convenient way to get the full changes that caused a given bug to be closed?
The only solution I could think of is going to https://snapshot.debian.org/package/poppler (using poppler as a package example), picking the corresponding two versions' debian.tar.xz files, unpacking them and comparing the directories, which looks quite cumbersome.
2 answers
That depends on your definition of convenient. Are you familiar with git? Is the source of the relevant package stored on salsa.debian.org? If yes, then you can just run:
git clone https://salsa.debian.org/debian/poppler-data
cd poppler-data
git diff debian/0.4.9-1 debian/0.4.9-2
Where these are the versions to compare for this example package.
1 comment thread
https://metadata.ftp-master.debian.org/changelogs/main/p/poppler/poppler_22.12.0-2_changelog contains the changelog for this particular package. It should be obvious how to change to a different version or a different package. For example, https://metadata.ftp-master.debian.org/changelogs/main/e/emacs contains all the changelogs for the emacs package.
There is also https://tracker.debian.org/pkg/poppler which contains a lot of developer information for this particular package.
https://serverfault.com/questions/174737/how-do-i-see-the-changelog-for-a-debian-ubuntu-deb-package contains several command-line solutions. The most straightforward is the apt changelog command;
apt changelog emacs
(This particular command does not work for the poppler package at the moment; dunno what's with that.)
0 comment threads