| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
|
|
|
| |
This makes it usable when creating changelogs but it can also be useful
when we don't want to compare to changelog version.
Gbp-Dch: Ignore
|
| |
|
|
|
|
|
| |
Running `gbp dch` with a mangled upstream tag resulted in a KeyError
while trying to build a tag pattern.
Signed-off-by: Guido Günther <agx@sigxcpu.org>
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
With commit 59254996d740b8b8a0db306a7e04950a5f4e51b8 the version
guessing behavior changed. gbp dch --release suggested to bump
the package version from: 1.0-0vyatta1 to 1.0-1
Old and expected beahviour is: 1.0-0vyatta2
Signed-off-by: Guido Günther <agx@sigxcpu.org>
Closes: gh#10
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In some unfortunate cases you might have something like this:
$ git tag
v1.0
vyatta/1.0-0something1
... where later tag is closer to describe current HEAD.
With upstream-tag set to v%(version)s find_tag() is going to propose
something based on vyatta/1.0-0something1 which is not expected.
The problem is that find_tag() returns tags, which match the
upstream-tag format, but which are not on the upstream-branch at all.
To fix this find_tag()/git-describe should not be used to determine
the closest upstream-tag.
Closes: gh#7
|
| |
|
|
| |
so Python3 can cope as well
|
| | |
|
| |
|
|
|
| |
and allow to specify the content so we can reuse it for other dch
tests.
|
| |
|
|
|
|
|
| |
This puts test dirs below /tmp which often is a tmpfs.
All tests include the context module which consolidates tmpdir creation
and cleanup, undoes a chdir in teardown and silences log messages.
|
| |
|
|
|
|
| |
based on a patch by Daniel Dehennin
Needed for #672954, #646684, #669171
|
| |
|
|
| |
Git-Dch: Ignore
|
|
|
Closes: #652366
Thanks: a lot to Daniel Dehennin for the testcase
|
