Your message dated Thu, 12 Oct 2017 23:39:04 +0200
with message-id <[email protected]>
and subject line Re: Bug#866197: add most recent changelog entry to dsc file
has caused the Debian Bug report #866197,
regarding add most recent changelog entry to dsc file
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
866197: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866197
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: dpkg
Version: 1.18.24
Severity: wishlist
Would it be possible to automatically add the most recent
changelog entry to the package.dsc file at build time?
This would make it possible to easily browse the most
recent changes without downloading a giant changelog file.
Regards
Harri
--- End Message ---
--- Begin Message ---
Hi!
On Wed, 2017-06-28 at 09:16:07 +0200, Harald Dunkel wrote:
> Package: dpkg
> Version: 1.18.24
> Severity: wishlist
> Would it be possible to automatically add the most recent
> changelog entry to the package.dsc file at build time?
Not always. Consider that binNMUs contain a changelog entry that only
appears in the binary packages, but never in any source package.
> This would make it possible to easily browse the most
> recent changes without downloading a giant changelog file.
Not really. Also, this would require for users to have archive
Sources available, which I don't think it's common. It would also
assume the upload only contained one release, which is not always
true. And as stated above would not work for binNMUs.
The relevant changlog entries are already included .changes files,
when preparing the upload. Of course those are not usually exposed
from archives. I guess the archive (or something like tracker.d.o)
could provide some kind of API to query changelog ranges for example.
But in any case I don't think the proposal in this report goes in
the right direction, so I'm just going to close the report.
Thanks,
Guillem
--- End Message ---
