On Mon, Mar 28, 2016 at 07:35:22PM +0900, Roger Shimizu wrote: > Control: tags -1 -unreproducible
> On Mon, Mar 28, 2016 at 1:55 PM, Steve Langasek <vor...@debian.org> wrote: > > On Sun, Mar 27, 2016 at 11:28:14PM +0900, Roger Shimizu wrote: > > This package has never had a problem building with the current build-depends > > set. Please show a build log that explains why you think this > > build-dependency is needed. > Maybe the one of libraries pam's depending on removed the dependency? > Just by my best guess, maybe not true. > Anyway, here's how I build pam package: > $ 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? -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer http://www.debian.org/ slanga...@ubuntu.com vor...@debian.org
signature.asc
Description: Digital signature
