Hi!

On Tue, 2012-08-07 at 19:21:48 +0200, Axel Beckert wrote:
> Package: dpkg-dev
> Version: 1.16.8
> Severity: wishlist

> it would be nice if dpkg-parsechangelog would support gzip-compressed
> changelogs as part of every binary package.
> 
>    * What led up to the situation?
> 
> I wanted to parse a changelog as installed by a package into /usr/share/doc/
> 
>    * What exactly did you do (or not do) that was effective (or
>      ineffective)?
> 
> $ dpkg-parsechangelog --from 4.6.2-5 --to 4.6.3-1 
> -l/usr/share/doc/gcc-4.6/changelog.Debian.gz
> 
> [Got binary garbage and tons of parser warnings.]
> 
>    * What outcome did you expect instead?
> 
> The same as the one which finally worked:
> 
> $ zcat /usr/share/doc/gcc-4.6/changelog.Debian.gz | dpkg-parsechangelog 
> --from 4.6.2-5 --to 4.6.3-1 -l-

The support is mostly all there, it's just an issue with the base parsing
code which destroys all possibility to leave the rest handle the
compression transparently. I've started fixing this now, will be
included in 1.17.x.

> Maybe an option -p<package> would helpful here, too, so that the
> commands above would look like this:
> 
> $ dpkg-parsechangelog --from 4.6.2-5 --to 4.6.3-1 -pgcc-4.6

I don't think this is a good idea, as long as the changelog files are
in the normal file system instead of in the dpkg database, because it
would require hardcoding a series of file paths, which might change
from distro to distro, also it would need to know if a package is
native or not, etc. Once (and if) those are there, then yes I would
be open to consider that.

> As a workaround it would already help to document in
> dpkg-parsechangelog(1) that dpkg-parsechangelog can read from STDIN if
> the option "-l-" is given (as "-l/dev/stdin" and "-l<(zcat
> changelog.Debian.gz)" both did not work).

I've fixed this locally now, which will be included in 1.17.x.

thanks,
guillem


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to