| Commit message (Collapse) | Author | Age |
|\
| |
| |
| | |
[dgit --quilt=gbp --overwrite]
|
| |\ |
|
| | |
| | |
| | |
| | |
| | | |
Remove reference to installation.
Gbp-Pq: Name 0001-Debianise-README.patch
|
| | |\
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Upstream:
* Taking over as upstream maintainer.
* Remove notice about repository format potentially changing.
* Implement gcrypt.gpg-args git config setting (Closes: #771011).
* Respect git config gpg.program if configured.
Thanks Christian Amsüss. (Closes: #827943)
* Don't reset the remote ID when a gcrypt remote is not available.
Thanks Sebastian Reuße. (Closes: #827943)
* Suppress bogus warning about keyid matching multiple fingerprints.
Based on work by Raphaël Droz.
Closes https://github.com/joeyh/git-remote-gcrypt/pull/2
* Add "Note to users of GnuPG version 2" section to README.rst.
See https://github.com/joeyh/git-remote-gcrypt/pull/1
Debian packaging:
* Drop patch containing changes by Joey Hess: incorporated in release.
- Update d/copyright accordingly.
* Patch README.rst to remove references to installation.
* Add d/links to avoid duplicate changelogs Lintian warning.
* Drop Lintian override of no-upstream-changelog.
* Update URIs in old changelog entries.
* Add a comment to d/source/lintian-overrides.
* Bump standards version to 3.9.8 (no changes required).
[dgit import unpatched git-remote-gcrypt 1.0.0-1]
|
| | |
| | |
| | |
| | | |
[dgit import tarball git-remote-gcrypt 1.0.0-1 git-remote-gcrypt_1.0.0-1.debian.tar.xz]
|
| |
| |
| |
| | |
[dgit import orig git-remote-gcrypt_1.0.0.orig.tar.xz]
|
| | |
|
| |\ |
|
| | | |
|
| | |
| | |
| | |
| | | |
set. Pass --no-tty to gpg in this situation. This is needed to interoperate with the git-annex assistant, which often runs without a controlling terminal, and will in a new version always do so.
|
| | | |
|
| |\ \ |
|
| |\ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
Conflicts:
git-remote-gcrypt
|
| | | | |
| | | | |
| | | | |
| | | | | |
Closes https://github.com/blake2-ppc/git-remote-gcrypt/issues/8
|
| | | | | |
|
| | | | | |
|
| |\ \ \ \ |
|
| | | | | | |
|
| |\ \ \ \ \ |
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
git-annex. Closes https://github.com/blake2-ppc/git-remote-gcrypt/issues/3
|
| |\ \ \ \ \ \ |
|
| | | | | | | | |
|
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
Remove reference to installation.
Gbp-Pq: Name 0001-Debianise-README.patch
|
| | | | | | | | |
|
| | | | | | | | |
|
| | | | | | | | |
|
| | | | | | | | |
|
| | | | | | | | |
|
| | | | | | | | |
|
| | | | | | | | |
|
| | | | | | | | |
|
| | | | | | | | |
|
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
Based on commit a72eb5d9520a8d7fa23478aeb1c14a14e66c19a2 by Raphaël
Droz's fork -- thanks.
|
| | | | | | | | |
|
| | | | | | | | |
|
| | | | | | | | |
|
| | | | | | | | |
|
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
When a gcrypt remote is not available, for any reason
(network being down, the drive containing it not being
mounted, etc), pushing to the remote causes a new repository
ID to be created.
Instead, we now fail loudly when a remote is unavailable and
when the remote ID is already set.
https://github.com/bluss/git-remote-gcrypt/issues/20
(cherry picked from commit b46d48af15e0f8b89f2666aff2c045c9306305d6)
|
| | | | | | | | |
|
| | | | | | | | |
|
| | | | | | | | |
|
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
The filter directive filters imported upstream tarballs but fails to
filter generated tarballs. It doesn't actually matter because source
format version 3 will ignore a debian/ subdir in an orig tarball.
|
| | | | | | | | |
|
| | | | | | | | |
|
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
We do actually need separate Debian and upstream tags.
|
| | | | | | | | |
|
| | | | | | | | |
|
| | | | | | | | |
|
| | | | | | | | |
|
| | | | | | | | |
|