Invalid version string {debupstream:packaging} with nest-part
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
git-build-recipe |
New
|
Undecided
|
Unassigned |
Bug Description
Using git recipe format 0.4 with {debupstream:
HEAD is now at 991bf4ef7 2023.08.27 13:30
From https:/
* [new branch] master -> source-
Traceback (most recent call last):
File "/usr/lib/
changelog.
File "/usr/lib/
super(
File "/usr/lib/
self.
File "/usr/lib/
self.
File "/usr/lib/
raise ValueError("Invalid version string %r" % version)
ValueError: Invalid version string '{debupstream:
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/bin/git-
load_
File "/usr/lib/
add_
File "/usr/lib/
raise Exception("Invalid deb-version: %s: %s" % (version, e))
Exception: Invalid deb-version: {debupstream:
RUN: /usr/share/
Scanning for processes to kill in build RECIPEBRANCHBUI
Launchpad recipe used:
# git-build-recipe format 0.4 deb-version {debupstream:
lp:~reviczky/+git/context-texlive
nest texmf-dist lp:~reviczky/context/+git/master texmf-dist main
nest-part packaging lp:~reviczky/+git/context-debian debian debian master
Full log: https:/
I believe https:/ /paste. ubuntu. com/p/R9p8SFQsy K/ will fix this, but we need to work out why we missed this before and how to unit-test it properly.