Package: git-buildpackage
Version: 0.9.15
Severity: normal
Dear Maintainer,
When having a gbp repo, with Debian packaging in debian/master, when being in
the master branch, where I have upstream development, if I by mistake want to
do something like gbp pq switch (Which of course should be done from
debian/master) - I get a traceback.
It would be nice if it didn't give a traceback, but simply a errormessage that
it expects you to be on another branch for that to work.
gusnan@debian-buildsystem:~/kod/packaging/allegro5/allegro5 [master]> gbp pq
switch --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', 'show-ref', '--verify', 'refs/heads/patch-queue/master']
gbp:info: No pq branch found, importing patches
gbp:debug: ['git', 'show-ref', '--verify', 'refs/heads/patch-queue/master']
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/pq.py", line 498, in main
switch_pq(repo, current, options)
File "/usr/lib/python3/dist-packages/gbp/scripts/pq.py", line 395, in
switch_pq
maybe_import_pq(repo, branch, options)
File "/usr/lib/python3/dist-packages/gbp/scripts/pq.py", line 383, in
maybe_import_pq
import_pq(repo, branch, options)
File "/usr/lib/python3/dist-packages/gbp/scripts/pq.py", line 374, in
import_pq
options.upstream_tag)
File "/usr/lib/python3/dist-packages/gbp/scripts/pq.py", line 306, in
import_quilt_patches
maintainer = get_maintainer_from_control(repo)
File "/usr/lib/python3/dist-packages/gbp/scripts/common/pq.py", line 280, in
get_maintainer_from_control
with open(control, encoding='utf-8') as f:
FileNotFoundError: [Errno 2] No such file or directory:
'/home/gusnan/kod/packaging/allegro5/allegro5/debian/control'
Thanks for all your work on gbp, it's a brilliant tool.
-- Andreas Rönnquist
[email protected]
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.0-5-amd64 (SMP w/1 CPU core)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=sv_SE.utf8, LC_CTYPE=sv_SE.utf8 (charmap=UTF-8),
LANGUAGE=sv_SE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages git-buildpackage depends on:
ii devscripts 2.19.6
ii git 1:2.23.0-1
ii man-db 2.8.7-3
ii python3 3.7.3-1
ii python3-dateutil 2.7.3-3
ii python3-pkg-resources 41.2.0-1
ii sensible-utils 0.0.12
Versions of packages git-buildpackage recommends:
ii cowbuilder 0.88
ii pbuilder 0.230.4
ii pristine-tar 1.46
ii python3-requests 2.21.0-1
Versions of packages git-buildpackage suggests:
ii python3-notify2 0.3-3
ii sudo 1.8.27-1+b1
ii unzip 6.0-25
-- no debconf information
