On 10/20/20 1:55 PM, Jakob Bohm wrote: > On 2020-10-20 06:05, Sebastiaan Couwenberg wrote: >> Control: tags -1 unreproducible >> Control: severity -1 important >> >> Hi Jakob, >> >> Thanks for reporting this issue, but unfortunately I cannot reproduce it. >> >> Building 2.2-6 in a buster chroot works as expected: >> >> gbp clone \ >> https://salsa.debian.org/nagios-team/pkg-monitoring-plugins.git >> git checkout -b buster debian/2.2-6 >> gbp buildpackage --git-pbuilder \ >> --git-dist=buster \ >> --git-debian-branch=buster >> >> Kind Regards, >> >> Bas >> > > Did your test include the use of backported packages, as stated?
No, just plain buster. Note that 2.2-6 still uses a deprecated debhelper compat level, this has been changed in git. If you need a backport for buster, you may need to cherry-pick some unreleased commits from the master branch. > When checking out from git, I didn't select any specific branch, as the > "please use the git source" message just said to clone the tree, thus HEAD. > > Also, I notice that your build commands differ from mine, what is "gbp"? git-buildpackage, it's the tools we use to build packages from the git repo. See: https://wiki.debian.org/PackagingWithGit Or a more specific guide that includes setting up the cowbuilder chroots: https://debian-gis-team.pages.debian.net/policy/packaging.html#git-pbuilder > As a local sysadmin, I don't have my own installs of automated build > daemons such as pbuilder. pbuilder & cowbuilder are not automated build daemons, they are chroot environments to ensure that the package is built in a clear environment just like on the official build daemons (which use sbuild instead of pbuilder). Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
