Package: git-buildpackage Version: 0.9.17 Severity: normal A common workflow using gbp is to import-orig into an experimental branch when upgrading a package to a new version. The upgrade can be pushed to experimental before releasing to sid.
By default gbp imports into the master branch. Importing elsewhere needs to be specified explicitly with the --debian-branch option. However, if you're working in an experimental branch and run gbp import-orig, it silently imports into the master branch. This breaks expectations, you might not realise the import went wrong until you try to build and wonder why it complains and fails. import-orig should either import into the current branch (experimental, master or otherwise), or else it should refuse to import if the current branch is not master and provide a warning message (if --debian-branch is not given) -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.3.0-2-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_AU:en (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.7 ii git 1:2.24.0-1 ii man-db 2.9.0-1 ii python3 3.7.5-3 ii python3-dateutil 2.7.3-3 ii python3-pkg-resources 41.4.0-1 ii sensible-utils 0.0.12+nmu1 Versions of packages git-buildpackage recommends: ii pbuilder 0.230.4 ii pristine-tar 1.47 ii python3-requests 2.21.0-1 ii sbuild 0.78.1-2 Versions of packages git-buildpackage suggests: ii python3-notify2 0.3-3 ii sudo 1.8.29-1 ii unzip 6.0-25 -- no debconf information
