Your message dated Thu, 26 Jan 2017 14:00:53 +0100
with message-id <[email protected]>
and subject line Re: Bug#848189: /usr/bin/dpkg-parsechangelog: 
dpkg-parsechangelog doesn't parse from stdin by default as claimed in the 
manpage
has caused the Debian Bug report #848189,
regarding /usr/bin/dpkg-parsechangelog: dpkg-parsechangelog doesn't parse from 
stdin by default as claimed in the manpage
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.)


-- 
848189: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848189
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: dpkg-dev
Version: 1.18.15
Severity: normal
File: /usr/bin/dpkg-parsechangelog

Dear Maintainer,

The dpkg-parsechangelog manual page says:

   --file file
          Set the changelog filename to parse.  Default is ‘-’ (standard
          input).

That is, however, not the case. It actually reads the debian/changelog
file, even when stdin is a pipe:

$ git show esr45/master:debian/changelog | dpkg-parsechangelog --file - -S 
Version
45.6.0esr-1
$ git show esr45/master:debian/changelog | dpkg-parsechangelog -S Version
50.1.0-1
$ dpkg-parsechangelog --file debian/changelog -S Version
50.1.0-1
$ dpkg-parsechangelog -S Version
50.1.0-1


-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.8.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages dpkg-dev depends on:
ii  binutils      2.27.51.20161212-1
ii  bzip2         1.0.6-8
ii  libdpkg-perl  1.18.15
ii  make          4.1-9
ii  patch         2.7.5-1
pn  perl:any      <none>
ii  tar           1.29b-1.1
ii  xz-utils      5.2.2-1.2

Versions of packages dpkg-dev recommends:
ii  build-essential          12.2
ii  fakeroot                 1.21-3
ii  gcc [c-compiler]         4:6.2.1-1
ii  gcc-6 [c-compiler]       6.2.1-6
ii  gnupg                    2.1.16-3
ii  gpgv                     2.1.16-3
ii  libalgorithm-merge-perl  0.08-3

Versions of packages dpkg-dev suggests:
pn  debian-keyring  <none>

-- no debconf information

--- End Message ---
--- Begin Message ---
Version: 1.18.16

Hi!

On Thu, 2016-12-15 at 13:06:01 +0100, Guillem Jover wrote:
> On Thu, 2016-12-15 at 08:56:20 +0900, Mike Hommey wrote:
> > Package: dpkg-dev
> > Version: 1.18.15
> > Severity: normal
> > File: /usr/bin/dpkg-parsechangelog
> 
> > The dpkg-parsechangelog manual page says:
> > 
> >    --file file
> >           Set the changelog filename to parse.  Default is ‘-’ (standard
> >           input).
> > 
> > That is, however, not the case. It actually reads the debian/changelog
> > file, even when stdin is a pipe:
> 
> Right, because those were the arguments to the old parser backend
> which used to be itself a program called from dpkg-parsechangelog.
> Several other options listed are neither supported by the frontend
> and have no relevance anymore, such as --label. In this case --file
> is equivalent to -l. I'll merge and fix the "Parser Options" section
> to match reality.

This got fixed in dpkg 1.18.16, with:

  ,---
  dpkg (1.18.16) unstable; urgency=medium

  […]
    * Documentation:
  […]
      - Update dpkg-parsechangelog parser options. The options specific to
        the changelog parser program did not get updated when the parser got
        switched to be a perl module. Missed in dpkg 1.18.8.
  […]

   -- Guillem Jover <[email protected]>  Sat, 17 Dec 2016 00:25:53 +0100
  `---


but it seems I misse to add a bug closure. Retroactively added that
to the changelog and closing this report now.

Thanks,
Guillem

--- End Message ---

Reply via email to