Control: severity -1 wishlist On Tue, Mar 29, 2016 at 2:31 AM, Steve Langasek <vor...@debian.org> wrote: > On Mon, Mar 28, 2016 at 07:35:22PM +0900, Roger Shimizu wrote: >> $ sudo apt build-dep pam >> $ sudo apt install git-remote-bzr >> $ git clone bzr::http://anonscm.debian.org/bzr/pkg-pam/debian/sid pam >> -- may wait a few minutes -- >> $ cd pam >> -- to start from a previous release point -- >> $ git checkout -b v1.1.8-3 c0f400 >> $ gbp buildpackage -uc -us --git-ignore-branch > >> Enclosed the build log from my armel box. > > Well, in comparison, here is the latest official build log on armel, which > you'll see shows no use of bison. > > > https://buildd.debian.org/status/fetch.php?pkg=pam&arch=armel&ver=1.1.8-3.2&stamp=1452133353 > > My guess is that because you're using git-remote-bzr + git-buildpackage, > your build system is not picking up the orig.tar that's stored in the > pristine-tar branch, and as a result you have a tree with files unpacked in > the wrong order, leading make to conclude that the yacc output needs to be > regenerated (because it's older than the input file). > > Grabbing the orig.tar from the archive and placing it in the right place in > your filesystem should be sufficient to avoid this problem, I think?
I checked my build environment, and there's "pam_1.1.8.orig.tar.gz" in parent directory, downloaded by command below: $ wget http://httpredir.debian.org/debian/pool/main/p/pam/pam_1.1.8.orig.tar.gz Sorry for not mentioning this in previous steps. Anyway, the official repo is bzr and my gbp usage is just "alternative", I agree to lower the priority. Maybe some day you meet the issue can there's a reference here. -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 17B3ACB1
