On Wed, Mar 23, 2016 at 09:21:19AM +1100, Brian May wrote: > Steve Langasek <vorlon@debian.org> writes: > > No. I first noticed this bug because the package failed to build in > > Ubuntu[1], which uses sbuild, not pbuilder. I reproduced the failure in a > > clean sid schroot. I think either your sbuild environment is not clean, or > > it is not up-to-date. > Definitely a clean chroot. I just recently deleted and rebuilt it from > scratch. With sbuild-createchroot. > In a bizarre twist, I have found I can reproduce the problem on a dirty > testing Debian installation. So I will attempt to fix the problem here, > and see if this offers any clues as to what on earth is going on with my > clean chroot. Ok, that was certainly another possibility. "Clean" chroots certainly vary, and some ways of building them may include more stuff than others, and some of that "more" stuff may be triggering this problem. -- 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/ slangasek@ubuntu.com vorlon@debian.org
Attachment:
signature.asc
Description: Digital signature