Changelog parser doesn't raise a failure if the last entry is malformatted

Bug #516798 reported by John A Meinel
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
python-debian (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: python-debian

I was trying to create a test case with a badly formatted changelog, only to find out that it didn't actually care when there was only a single entry.

Specifically I tried to do:

invalid_changelog = """\
psuedo-prog (1.1.1-2) unstable; urgency=low

  * New upstream release.
  * Awesome bug fixes.

 -- Joe Foo <email address hidden>

""" # Missing the date

And
cl = changelog.Changelog(invalid_changelog)

Happily parses the content, but cl._blocks is empty.
I'm guessing it needs a "there was trailing garbage" check.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.