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]:
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 <[email protected]> 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>
** Affects: glib2.0 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1195568
Title:
glib2.0 2.37.3-1ubuntu1: invalid changelog entry format
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1195568/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
