| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
| |
Add option `--upstream-signatures=[on|auto|off]` to export-orig.
Add option `--git-upstream-signatures=[on|auto|off]` to buildpackage.
Closes: 872864
|
| |
|
|
|
|
| |
The python2 version won't do
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
This will help on upstream tarball signatures as well as
improving additional tarball handling.
|
|
|
|
|
| |
This is a valid use case in overlay mode
Thanks: Thomas Koch for the report
|
|
|
|
| |
Closes: #941894
|
|
|
|
| |
Closes: #940043
|
| |
|
|
|
|
|
|
| |
(rightfully tripping up newer flake8)
Gbp-Dch: Ignore
|
|
|
|
|
|
| |
The debian_merge_by_replace function ends up calling force_head, but up
to this point the current branch could be anything, and thus when called from a
feature branch the latest commits get lost.
|
|
|
|
| |
Closes: #782886
|
|
|
|
| |
This way it can be shared.
|
|
|
|
|
| |
The working directory of the hook is the top temporary directory the
tarballs are being unpacked into.
|
|
|
|
|
|
|
|
|
|
|
| |
Otherwise, if we import a patch containing non-ASCII characters exported
by `gbp pq export` or `git format-patch` using DEP-3 syntax, we'd
misinterpret these fields as semantically significant and copy them into
pseudo-headers, causing them to be duplicated in the commit's long
description.
Closes: #924478
Signed-off-by: Simon McVittie <smcv@debian.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
gbp dch errors out with the following output if the "log.showSignature"
git config is enabled:
$ gbp dch --verbose
gbp:debug: ['git', 'rev-parse', '--show-cdup']
gbp:debug: ['git', 'rev-parse', '--is-bare-repository']
gbp:debug: ['git', 'rev-parse', '--git-dir']
gbp:debug: ['git', 'symbolic-ref', 'HEAD']
gbp:debug: ['git', 'show-ref', 'refs/heads/master']
gbp:debug: ['git', 'tag', '-l', 'debian/2.7.3-2']
gbp:debug: ['git', 'tag', '-l', 'debian/2.7.3-2']
gbp:debug: ['git', 'log', '--pretty=format:%H', '-1', '--', 'debian/changelog']
gbp:info: Changelog last touched at 'gpg: Signature made Fri 01 Feb 2019 03:56:19 PM EST'
gbp:debug: ['git', 'log', '--pretty=format:%H', 'gpg: Signature made Fri 01 Feb 2019 03:56:19 PM EST..HEAD', '--no-merges', '--']
fatal: bad revision 'gpg: Signature made Fri 01 Feb 2019 03:56:19 PM EST..HEAD'
gbp:error: Error getting commits gpg: Signature made Fri 01 Feb 2019 03:56:19 PM EST..HEAD
This is caused by gbp dch receiving unexpected output for the PGP
signatures and trying to use this unexpected output.
To avoid any surprises, let's disable signatures being output when we
list commits.
Also, when collecting a shortlog-like output from commit objects, the
same unexpected PGP signature output is sprayed all over the changelog.
We'll avoid this by also disable showing signatures when showing each
commit's first line.
Closes: #923087
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Replace the \S in the substitution. Otherwise we fail on Python3.7 like
======================================================================
ERROR: Test determining the author name/email
----------------------------------------------------------------------
Traceback (most recent call last):
File "/usr/lib/python3.7/sre_parse.py", line 1021, in parse_template
this = chr(ESCAPES[this][1])
KeyError: '\\S'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/var/scratch/src/git-buildpackage/git-buildpackage/tests/component/rpm/test_rpm_ch.py", line 182, in test_author
eq_(mock_ch([]), 0)
File "/var/scratch/src/git-buildpackage/git-buildpackage/tests/component/rpm/test_rpm_ch.py", line 37, in mock_ch
'--spawn-editor=never'] + args)
File "/var/scratch/src/git-buildpackage/git-buildpackage/gbp/scripts/rpm_ch.py", line 422, in main
since = get_start_commit(ch_file.changelog, repo, options)
File "/var/scratch/src/git-buildpackage/git-buildpackage/gbp/scripts/rpm_ch.py", line 230, in get_start_commit
since = guess_commit(changelog.sections[0], repo, options)
File "/var/scratch/src/git-buildpackage/git-buildpackage/gbp/scripts/rpm_ch.py", line 180, in guess_commit
options.changelog_revision)
File "/usr/lib/python3.7/re.py", line 192, in sub
return _compile(pattern, flags).sub(repl, string, count)
File "/usr/lib/python3.7/re.py", line 309, in _subx
template = _compile_repl(template, pattern)
File "/usr/lib/python3.7/re.py", line 300, in _compile_repl
return sre_parse.parse_template(repl, pattern)
File "/usr/lib/python3.7/sre_parse.py", line 1024, in parse_template
raise s.error('bad escape %s' % this, len(this))
re.error: bad escape \S at position 7
|
|
|
|
|
|
|
|
| |
`gbp pull --redo-pq` assumed that `gbp-pq` exists in PATH, which isn't
normally true since 0.6.24 (2015).
Signed-off-by: Simon McVittie <smcv@debian.org>
Closes: #917637
|
|
|
|
| |
Closes: #914280
|
|
|
|
|
|
| |
This makes sure in new repos this is the correct default branch.
Closes: #916651
|
|
|
|
|
|
|
|
| |
If the patch only has '---' we pass empty data to git-mail-info
otherwise.
Thanks: James Cowgill for the detailed report
Closes: #916545
|
| |
|
|
|
|
|
|
|
| |
This is still experimental but let's ship it since it's useful in
some cases already.
Gbp-Dch: Ignore
|
| |
|
|
|
|
| |
Closes: #916044
|
|
|
|
| |
since it's the source package's name
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
Add support for passing %(version), %(hversion) and %(version%A%B) in
buildpackage --git-tarball-dir and export-orig --tarball-dir.
Closes: #909266
Signed-off-by: Luca Boccassi <bluca@debian.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
There are patches around that use
Content-Transfer-Encoding: base64
but the actual patch after '---' is unencoded ascii resulting in garbage
after the patch description when imported into a patch queue.
Since we're discarding the patch part of git-mailinfo anyway don't pass
this on in the first place.
Closes: #912426
|
| |
|
|
|
|
|
|
| |
This is consistent with --git-post-export and unbreaks
tests/component/rpm/test_buildpackage_rpm.py:TestGbpRpm.test_hook_options
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Sometimes it is necessary to perform operations before preparing the
tarballs and exporting to the build directory.
One such case is when having to handle extremely large binary assets in
the orig tarball and at the same time complex packaging code, which
makes it desirable to separate the two into different repositories for
easier handling.
A pre-export hook allows to ensure that the tarball repository is
present and checked out at the correct branch.
Closes: #909266
Signed-off-by: Luca Boccassi <bluca@debian.org>
|
|
|
|
|
|
| |
See also
https://docs.python.org/3/whatsnew/3.6.html#deprecated-python-behavior
|
|
|
|
|
|
| |
to make flake8 happy
Gbp-Dch: Ignore
|
| |
|
|
|
|
| |
Gbp-Dch: Ignore
|
| |
|
|
|
|
| |
Gbp-Dch: Ignore
|