Post History
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 versi...
Question
debian
#3: Post edited
by
Quasímodo
·
2022-09-29T18:19:54Z (over 1 year ago)
Add reference for bug closure syntax
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](https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=528167).
- 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.
- If a Debian bug number is referenced in the changelog of an uploaded package, it is [automatically closed](https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#upload-bugfix) 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](https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=528167).
- 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: Post edited
by
Quasímodo
·
2022-09-28T17:40:00Z (over 1 year ago)
Provide example
- 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.
- 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](https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=528167).
- 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.
#1: Initial revision
by
Quasímodo
·
2022-09-28T17:35:30Z (over 1 year ago)
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.