Accepted git-buildpackage 0.9.26 (source) into unstable

Debian FTP Masters Mon, 16 May 2022 02:51:17 -0700
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Mon, 16 May 2022 10:56:56 +0200
Source: git-buildpackage
Architecture: source
Version: 0.9.26
Distribution: unstable
Urgency: medium
Maintainer: Guido Günther <a...@sigxcpu.org>
Changed-By: Guido Günther <a...@sigxcpu.org>
Closes: 1005321 1010061 1010750
Changes:
 git-buildpackage (0.9.26) unstable; urgency=medium
 .
   [ Quanah Gibson-Mount ]
   * [677500d] rpm: Avoid devscript dependency.
     The package is currently not available everywhere.
 .
   [ Andrej Shadura ]
   * [231ecef] import-orig: Don’t hardcode the pristine-tar branch
   * [de3c7c8] export-orig: Consistently refer to the pristine-tar branch.
     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.
   * [1065bca] config: Add missing comma
   * [6acd556] deb.git, scripts: Use cannot rather than can not for clarity
     "Can not" may in some cases mean something different than "cannot",
     use "cannot" to make sure there are no misunderstandings.
 .
   [ Unit 193 ]
   * [f268448] uscan: Remove pre-devscripts 2.10.70 compat code.
     We can rely on the <target> element being present in dehs output.
     The output it looks for from uscan no longer matches anyway.
 .
   [ Guido Günther ]
   * [c8782f2] HACKING: mention how to rerun a single test
   * [bb783b5] HACKING: Document how to keep test repos around
   * [63ce4ed] tests: Fix "test_push_failure" with newer git.
     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.
   * [caf64cb] push: Make --debian-tag='' match the documentation.
     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.
     this makes it simpler to push the current development work via
       gbp  push --debian-tag='' <remote>
     But we'll need to add less obscure ways in follow up commits too.
   * [8db5af7] pq: Check if repo is clean before importing patches
     (Closes: #1005321)
   * [dbadeed] rpm.changelog: Drop non breaking space.
     This trips up pydoctor.
     Thanks to Carsten Schönert for debugging help
   * [40b9693] rpm.policy: Drop non breaking space.
     This trips up pydoctor.
     Thanks to Carsten Schönert for debugging help
 .
   [ Antonio Terceiro ]
   * [5dcd753] docs: port build system to newer pydoctor.
     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.
   * [0dfc259] tests: set HOME to an unexisting directory.
     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.
   * [1a5fd69] debian/rules: fix build with python3.10 as default
   * [6733ab9] tests: fix input data to create-remote-repo tests
     (Closes: #1010061)
   * [2405e15] push: skip pristine-tar push if already present remotely.
     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. (Helps: #1001163)
 .
   [ Nicolas Boulenguez ]
   * [e17d814] scripts: add -v shortcut for --verbose where it has been
     forgotten
     (Closes: #1010750)
 .
   [ Roland Mas ]
   * [3627fa0] docs: Fix argument for "gbp pq export --commit"
Checksums-Sha1:
 7b821e26b4b5c971ee6860caa8b4ae31628de969 2311 git-buildpackage_0.9.26.dsc
 a2f484a9414e391c9db904f8a6732550befd31de 3135680 git-buildpackage_0.9.26.tar.xz
 42bee78aa51790f1913d745e058eb938d836fa33 12981 
git-buildpackage_0.9.26_amd64.buildinfo
Checksums-Sha256:
 b3f41b9ac23734b7a0aeb2aedb5a531f5f4ad6f0e9e501f96997497fa2cbd771 2311 
git-buildpackage_0.9.26.dsc
 dbb4acfb36cf713de4eacd8fe3be71c55d7e4bfb3dcdad379f2e5c2e0486f0c5 3135680 
git-buildpackage_0.9.26.tar.xz
 41b8f73e0b63a309b33c36ebe3259447a11aa1d9204966b7e8836814509fc33a 12981 
git-buildpackage_0.9.26_amd64.buildinfo
Files:
 44d4608f5d2157199d9200fad53f7fc5 2311 vcs optional git-buildpackage_0.9.26.dsc
 cab5a05e0bffcb140b64e3413bf3bd5b 3135680 vcs optional 
git-buildpackage_0.9.26.tar.xz
 ba4f40bb7320bdd6e20d0ca990c6f5d0 12981 vcs optional 
git-buildpackage_0.9.26_amd64.buildinfo
Accepted git-buildpackage 0.9.26 (source) into unstable

Reply via email to
