| Commit message (Collapse) | Author | Age |
... | |
| |
|
|
|
|
|
|
|
| |
When importing not form the upstream branch the changelog is fetched
via `git show`. Decode the bytes in that case.
Closes: #1004354
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When dh-sequence-foo is listed in build-depends, debhelper
automatically inserts dh_foo in the commands.
override_dh_auto_test is not invoked anymore if DEB_BUILD_OPTIONS
contains nocheck.
execute_after_dh_* is available and more readable than override_dh_*.
Move chmod to execute_after_dh_fixperms for clarity.
Examples are not compressed anymore.
|
|
|
|
|
| |
There seems to be no reason to change their names and permissions
between the source tree and the eventual installation path.
|
|
|
|
| |
This slightly improves readability.
|
|
|
|
| |
Closes: #1011344
|
|
|
|
|
|
|
|
| |
Otherwise get the signature back as well.
Thanks: наб for the patch
Closes: #1010370
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We can't assume the user is pushing to the defaulte remote as
gbp push foo
is also supported hence we can't just check pristine-tar status on the
default merge branch.
Helps 2405e158 ("push: skip pristine-tar push if already present remotely")
Gbp-Dch: Ignore
|
| |
|
|
|
|
| |
Closes: #1010750
|
|
|
|
|
|
|
|
| |
When one is working on an older branch (stable update or backport), the
pristine-tar branch may already contain new commits after the one
corresponding to the upstream version in question.
Closes: #1001163
|
|
|
|
| |
Closes: #1010061
|
| |
|
|
|
|
|
|
|
| |
The test suite contains several assumptions about the global git
configuration, including but not limited to the default branch name
being `master`. By running the tests against a unexisting HOME, git will
not load the user configuration and instead use all the git defaults.
|
|
|
|
|
|
|
| |
According to https://pydoctor.readthedocs.io/en/latest/help.html, the
command line and configuration parsing has changed in an incompatible
way. These changes fix the documentation build for me, but are probably
backwards-incompatible with older versions of pydoctor.
|
|
|
|
|
|
| |
This trips up pydoctor.
Thanks to Carsten Schönert for debugging help
|
|
|
|
|
|
| |
This trips up pydoctor.
Thanks to Carsten Schönert for debugging help
|
|
|
|
|
|
|
| |
"Can not" may in some cases mean something different than "cannot",
use "cannot" to make sure there are no misunderstandings.
Signed-off-by: Andrej Shadura <andrew.shadura@collabora.co.uk>
|
|
|
|
| |
Closes: #1005321
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
An empty Debian tag indicates "don't care" about the packaging branch.
Don't fail in that case but rather push out up to the branch tip:
Currently we'd fail like
$ gbp push --debian-tag='' guido
Traceback (most recent call last):
File "/usr/bin/gbp", line 149, in <module>
sys.exit(supercommand())
File "/usr/bin/gbp", line 145, in supercommand
return module.main(args)
File "/usr/lib/python3/dist-packages/gbp/scripts/push.py", line 153, in main
to_push['refs'].append((ref, get_push_src(repo, ref, dtag)))
UnboundLocalError: local variable 'dtag' referenced before assignment
this make it simple to push the current development work via
gbp push --debian-tag='' <remote>
|
|
|
|
|
|
| |
The test created a broken tag on the remote side to avoid that being
pushed in the test however git 2.34 and newer fail every push to that
repo so rather create a non-ff branch instead to make the push fail.
|
| |
|
| |
|
|
|
|
|
|
| |
We can rely on the <target> element being present in dehs output.
The output it looks for from uscan no longer matches anyway.
|
|
|
|
| |
Signed-off-by: Andrej Shadura <andrew.shadura@collabora.co.uk>
|
|
|
|
|
|
|
|
| |
Since we’re checking pristine_tar_branch, not pristine_tar.branch,
use the same expression in the log even though it’s not supposed
to be different.
Signed-off-by: Andrej Shadura <andrew.shadura@collabora.co.uk>
|
|
|
|
| |
Signed-off-by: Andrej Shadura <andrew.shadura@collabora.co.uk>
|
|
|
|
| |
The package is currently not available everywhere.
|
| |
|
|
|
|
|
|
| |
Otherwise dch based tests fail
Closes: #998573
|
|
|
|
|
| |
This avoids having to specify a suite with more modern common branch
names.
|
| |
|
|
|
|
| |
since Python 3.10 dropped the alias.
|
|
|
|
|
| |
This makes the requirement more obvious since dh-python does
multiple things
|
| |
|
|
|
|
| |
Even oldoldstable is recent enough
|
|
|
|
| |
Gbp-Dch: Ignore
|
|
|
|
| |
Gbp-Dch: Ignore
|
|
|
|
|
| |
Make it simple to create/update the pot file and provide an initial
po file for de.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When importing a dsc on a empty repository when `ìnit.defaultBranch` is
set to something like `main` in `~/.gitconfig` we failed with:
gbp:debug: ['git', 'update-ref', '-m', 'gbp: Import Upstream version 0.5.10.2', 'refs/heads/master', '95172aee8d1a4e6c69494e4f158f904111710168']
gbp:debug: ['git', 'symbolic-ref', 'HEAD']
gbp:debug: ['git', 'show-ref', 'refs/heads/main']
gbp:debug: ['git', 'symbolic-ref', 'HEAD']
gbp:debug: ['git', 'show-ref', 'refs/heads/main']
gbp:debug: ['git', 'branch', '-m', 'None', 'debian/buster']
gbp:error: Git command failed: Error running git branch: error: refname refs/heads/None not found
fatal: Branch rename failed
Traceback (most recent call last):
File "/usr/local/lib/python3.9/dist-packages/gbp-0.9.22-py3.9.egg/gbp/scripts/import_dsc.py", line 519, in main
commit = import_upstream(repo, sources[0], dsc, options)
File "/usr/local/lib/python3.9/dist-packages/gbp-0.9.22-py3.9.egg/gbp/scripts/import_dsc.py", line 269, in import_upstream
repo.rename_branch(repo.branch, options.debian_branch)
File "/usr/local/lib/python3.9/dist-packages/gbp-0.9.22-py3.9.egg/gbp/git/repository.py", line 333, in rename_branch
self._git_command("branch", args.args)
File "/usr/local/lib/python3.9/dist-packages/gbp-0.9.22-py3.9.egg/gbp/git/repository.py", line 245, in _git_command
raise GitRepositoryError("Error running git %s: %s" % (command, detail.decode().strip()))
gbp.git.repository.GitRepositoryError: Error running git branch: error: refname refs/heads/None not found
fatal: Branch rename failed
That's because we created the commit on `refs/heads/master` and then
tried to rename it from `refs/heads/main`.
To avoid that, if the repository is empty look at the name of the
current branch as reported by the symbolic ref pointed by `HEAD`.
Closes: #906600
Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>
|
|
|
|
| |
Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>
|
|
|
|
|
|
|
|
| |
The alternative would be to set a dummy address in case of
--git-author but that again can use $EMAIL so just fail if
both are unset.
Closes: #987611
|
| |
|
| |
|
| |
|
| |
|