Skip to content

Fix ~bpo version increment to bump local counter#60

Open
Robie Basak (basak-qcom) wants to merge 2 commits into
mainfrom
bpo-bumps
Open

Fix ~bpo version increment to bump local counter#60
Robie Basak (basak-qcom) wants to merge 2 commits into
mainfrom
bpo-bumps

Conversation

@basak-qcom

Copy link
Copy Markdown
Contributor

The ~bpo handler was treating the trailing +M as an opaque suffix and incrementing N instead. For a version like ~bpo13+1 the result was ~bpo14+1 rather than the correct ~bpo13+2.

Rewrite the regex to capture the optional +M group explicitly and increment M when present, falling back to incrementing N for the plain ~bpoN form.

Fixes: #52

If bumping 1.0.19+ds-0qli3~bpo13+1~ then the answer should be
1.0.19+ds-0qli3~bpo13+2~ and not 1.0.19+ds-0qli3~bpo14+1~. This was
filed as #52. First I'm adding a test to it to demonstrate the problem.
My next change will fix it.

Signed-off-by: Robie Basak <robie.basak@oss.qualcomm.com>
The ~bpo handler was treating the trailing +M as an opaque suffix and
incrementing N instead. For a version like ~bpo13+1 the result was
~bpo14+1 rather than the correct ~bpo13+2.

Rewrite the regex to capture the optional +M group explicitly and
increment M when present, falling back to incrementing N for the plain
~bpoN form.

Remove the xfail mark from the corresponding test.

Fixes: #52

Signed-off-by: Robie Basak <robie.basak@oss.qualcomm.com>
@basak-qcom

Copy link
Copy Markdown
Contributor Author

The test suite isn't run automatically, but I have verified it by hand.

The failing check is long term failing and unrelated to this PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

wrong backport version bump

2 participants