Create new changelog block from existing changelog

Murrell, Brian brian.murrell at intel.com
Mon Nov 2 19:48:41 GMT 2020


Since this looks like a mailing-list, please CC me directly on any
replies as I am not a list member.  I hope I don't have to subscribe
first as I just followed a mailto: link in the documentation to start
this e-mail.

Anyway, looking at

https://salsa.debian.org/python-debian-team/python-debian/-/blob/master/lib/debian/changelog.py#L20-26

it looks like I have to supply an amount of information (package,
version, etc.) that debian.changelog could conceivably already know
about by having opened the existing changelog with:

debian.changelog.Changelog(open("debian/changelog"))

I wonder why, if one does something like:

ch = debian.changelog.Changelog(open("debian/changelog"))
ch.new_block(version="1.2.3)

one gets an exception:

debian.changelog.ChangelogCreateError: Package not specified

Surely, the package name is known already in the Changelog object and
new_block() can just use that, yes?

Basically just an implied:

ch = debian.changelog.Changelog(open("debian/changelog"))
ch.new_block(package=ch.get_package(),
             version=1.2.3",
             distributions=ch.distributions,
             author="%s <%s>" % debian.changelog.get_maintainer(),
             date=email.utils.formatdate(None, True))

Given the above, the only field that seems like it really needs to be
mandatory and not have a reasonable default is the version field.

Thoughts?

b.




More information about the pkg-python-debian-maint mailing list