[Bug 1195568] [NEW] glib2.0 2.37.3-1ubuntu1: invalid changelog entry format

[Iain Lane]

status invalid

On Fri, Jun 28, 2013 at 05:20:07AM -0000, Daniel Hartwig wrote:
> Public bug reported:
> 
> The changelog entry for 2.37.3-1ubuntu1 is unterminated [1], flowing in
> to the next entry for the unreleased debian changes.  The following does
> not conform to changelog format as defined by debian-policy [2]:

It's not.

> 
> glib2.0 (2.37.3-1ubuntu1) saucy; urgency=low
> 
>   * Resynchronise on unrelease Debian SVN (glib is in NEW there). Remaining
>     change:
>     - Build-Depend on python:any for cross building.
> 
> glib2.0 (2.37.3-1) UNRELEASED; urgency=low
> […]
>  -- Iain Lane <iain.lane at canonical.com>   Tue, 25 Jun 2013 12:43:56 +0100

I'm guessing you got that from the changes file (or Launchpad's view of
it)? Those aren't quite the same as Debian changelogs, although
obviously they are parsed from them.

  http://www.debian.org/doc/debian-policy/ch-
controlfields.html#s-f-Changes

Download the source package and check it out. You'll see it's fine. Any
problems with packages.ubuntu.com are separate issues. Tools like
dpkg-parsechangelog can handle it fine:

,----
| laney at iota> dpkg-parsechangelog -s2.37.2-1
| Source: glib2.0
| Version: 2.37.3-1ubuntu1
| Distribution: saucy
| Urgency: low
| Maintainer: Iain Lane <iain.lane at canonical.com>
| Date: Tue, 25 Jun 2013 12:43:56 +0100
| Changes:
|  glib2.0 (2.37.3-1ubuntu1) saucy; urgency=low
|  . 
|    * Resynchronise on unrelease Debian SVN (glib is in NEW there). Remaining
|      change:
|      - Build-Depend on python:any for cross building.
|  .
|  glib2.0 (2.37.3-1) UNRELEASED; urgency=low
|  . 
|    * libglib2.0-tests: Depend on shared-mime-info required by contenttype test.
|    * New upstream release
|    * 0001-Revert-g_file_set_contents-don-t-fsync-on-ext3-4.patch: Drop, now
|      upstream.
|    * debian/tests/installed-tests: Add a new DEP-8 test to run the
|      installed-tests. Doesn't use the test runner yet as this isn't packaged.
|    * Refresh patches.
|    * Update symbols file.
`----

Cheers,

-- 
Iain Lane                                  [ iain at orangesquash.org.uk ]
Debian Developer                                   [ laney at debian.org ]
Ubuntu Developer                                   [ laney at ubuntu.com ]


** Changed in: glib2.0 (Ubuntu)
       Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1195568

Title:
  glib2.0 2.37.3-1ubuntu1: invalid changelog entry format

Status in “glib2.0” package in Ubuntu:
  Invalid

Bug description:
  The changelog entry for 2.37.3-1ubuntu1 is unterminated [1], flowing
  in to the next entry for the unreleased debian changes.  The following
  does not conform to changelog format as defined by debian-policy [2]:

  glib2.0 (2.37.3-1ubuntu1) saucy; urgency=low

    * Resynchronise on unrelease Debian SVN (glib is in NEW there). Remaining
      change:
      - Build-Depend on python:any for cross building.

  glib2.0 (2.37.3-1) UNRELEASED; urgency=low

    * libglib2.0-tests: Depend on shared-mime-info required by contenttype test.
    * New upstream release
    * 0001-Revert-g_file_set_contents-don-t-fsync-on-ext3-4.patch: Drop, now
      upstream.
    * debian/tests/installed-tests: Add a new DEP-8 test to run the
      installed-tests. Doesn't use the test runner yet as this isn't packaged.
    * Refresh patches.
    * Update symbols file.
   -- Iain Lane <iain.lane at canonical.com>   Tue, 25 Jun 2013 12:43:56 +0100

  [1] Resulting in perhaps parser errors, for example (perhaps unrelated) <http://packages.ubuntu.com/source/saucy/glib2.0> fails to list the binary packages built by this source.
  [2] <http://www.debian.org/doc/debian-policy/ch-source.html#s-dpkgchangelog>

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1195568/+subscriptions