Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Retrieve changes that closed a Debian bug

+4
−0

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:

Random example.

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.

History
Why does this post require moderator attention?
You might want to add some details to your flag.
Why should this post be closed?

0 comment threads

2 answers

+3
−0

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.

History
Why does this post require moderator attention?
You might want to add some details to your flag.

1 comment thread

Yes, I am familiar with Git, and though unfortunately not all of the packages are maintained in versi... (1 comment)
+0
−0

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.)

History
Why does this post require moderator attention?
You might want to add some details to your flag.

1 comment thread

I'd like to see the full changes (1 comment)

Sign up to answer this question »