| Commit message (Collapse) | Author | Age |
| |
|
|
|
|
|
|
|
| |
uscan as of devscripts 2.17.7 properly exits on gpg signature validation
errors.
This reverts commit 0388f9e397e591cd4de7de019e54d10548049943.
|
|
|
|
| |
so later testcases don't break
|
| |
|
|
|
|
| |
Closes: #868733
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
| |
uscan does not abort with a non-zero exit status when it fails to verify
gpg signatures or similar things so abort when we find a warning or
error.
We can't do any better since uscan stops further processing in this case
of e.g. pgp errors skipping version mangle among other things. See
#841910.
|
| |
|
|
|
|
| |
since that's the name of the module
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
since it breaks setup.py with
Traceback (most recent call last):
File "setup.py", line 79, in <module>
'console_scripts': ['gbp=gbp.scripts.supercommand:supercommand'],
File "/usr/lib/python2.7/distutils/core.py", line 111, in setup
_setup_distribution = dist = klass(attrs)
File "/usr/lib/python2.7/dist-packages/setuptools/dist.py", line 320, in __init__
_Distribution.__init__(self, attrs)
File "/usr/lib/python2.7/distutils/dist.py", line 259, in __init__
getattr(self.metadata, "set_" + key)(val)
File "/usr/lib/python2.7/distutils/dist.py", line 1220, in set_requires
distutils.versionpredicate.VersionPredicate(v)
File "/usr/lib/python2.7/distutils/versionpredicate.py", line 113, in __init__
raise ValueError("expected parenthesized list: %r" % paren)
ValueError: expected parenthesized list: '-dateutil'
This reverts commit d05dfea469e71f4fa13619f69639b83a105cea34.
|
|
|
|
|
|
|
|
|
|
| |
We import dateutil, but we only declare this dependency within the
debian packaging and RPM packaging.
Add the dependency to Python's setuptools packaging as well. This allows
git-buildpackage to install seamlessly within a Python virtualenv.
Signed-off-by: Guido Günther <agx@sigxcpu.org>
|
| |
|
|
|
|
| |
so we get a proper error message when pristine-tar is not installed.
|
|
|
|
| |
Gbp-Dch: Ignore
|
|
|
|
| |
Even oldoldstable has a more recent one.
|
|
|
|
|
|
|
|
| |
This is only necessary for non 3.0 (quilt) packages when not using
merge-mode=auto with "gbp import-orig".
Thanks: Sean Whitton
Closes: #864881
|
|
|
|
| |
Closes: #851128
|
|
|
|
|
|
|
|
|
| |
We should not raise CommandErrors from methods on a GitRepository so
convert the error and suppress the output. This will make us use the
hander for GitRepositoryErrors in import_orig and pristine_tar which
default to printing the error message.
Closes: #829252
|
|
|
|
|
| |
So far we used the defaults of command_wrapper which prints to stderr.
Add a quiet option to suppress this.
|
|
|
|
|
|
|
|
|
| |
This allows one to run the pristine-tar import at a later point. This
is useful when using component tarballs and we need to reference the
right trees for the commits.
The command can later be extended to allow for "export" as well to
recreate the tarballs without having to invoke "gbp buildpackage".
|
|
|
|
|
|
|
|
| |
mention RPM and start with a capital letter to make
gbp --list-cmds
output consistent.
|
| |
|
|
|
|
|
|
|
| |
We don't want to pass them on to pdebuild since this can trip up
the invoked build system e.g.
https://anonscm.debian.org/cgit/pkg-mozilla/icedove.git/commit/?id=56f8f4b728fa0a1075ccce1883a29bbe1daae303
|
|
|
|
| |
instead of the apt:/// scheme.
|
| |
|
| |
|
| |
|
|
|
|
| |
to produce diff compatible patches
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Closes: #863167
|
|
|
|
|
|
| |
There are some nuances in reflog handling.
Thanks: jean-christophe manciot for reporting this
|
|
|
|
|
|
| |
incorporating the changes we made since 0.8.3
Thanks: Russ Allbery
|
| |
|
| |
|
|
|
|
| |
for the gbp clone network test
|
|
|
|
|
|
| |
since this is the tested script
Gbp-Dch: Ignore
|
|
|
|
|
|
| |
to make cloning simpler
Closes: #861206
|
|
|
|
|
|
|
|
|
|
| |
When starting with Debian _and_ git people often stumble over a mismatch
between what dpkg-source expects to be in the tarball and the generated
tarball for various reasons. Give them a way to say:
"Use what I have on my current debian branch"
as upstream source.
Closes: #861004
|
|
|
|
| |
Gbp-Dch: Ignore
|
|
|
|
| |
Gbp-Dch: Ignore
|
|
|
|
| |
Gbp-Dch: Ignore
|
|
|
|
| |
Gbp-Dch: Ignore
|
| |
|
| |
|
|
|
|
| |
Gbp-Dch: Ignore
|
|
|
|
|
|
|
| |
by implying --git-ignore-new --git-ignore-branch. There's no point
in these safety checks when we export the working copy as is.
Closes: #822823
|
|
|
|
| |
Gbp-Dch: Ignore
|