Thomas Bushnell BSG <[EMAIL PROTECTED]> writes: > So the suggestion in the bug log was to actually *require* slib, not > conflict with the old version.
Right, but since a by-hand build on merulo in the unstable chroot succeeded, and the buildd build failed, both without slib installed, I don't think slib is the likely culprit, at least not slib alone. > I agree that this is extremely unlikely. The only guess is that the > bug log includes a purge of guile-1.6-libs; though even that shouldn't > matter since guile-1.6-libs doesn't contain anything that would be > left behind absent a purge. The most likely problem I can think of, if the failure actually is related to having guile-1.6-libs installed, is that the Guile build (or rather make check) is somehow picking up the /usr versions of the Guile libraries or modules in preference to the build tree versions, and those versions are somehow broken, at least with respect to the build tree code. This would definitely be a bug in Guile. > Indeed. I have had major frustrations sometimes of this sort. One > strategy is to use pbuilder instead of just an ordinary unstable > chroot, since pbuilder is much closer to the sbuild reality than > anything else. I've never used pbuilder. Does it require root, or is it possible to try it via fakeroot, fakechroot, or similar? > Indeed, now that I've checked, the last time I had this kind of > frustration, the problem was that lilypond behaved differently when > stdin was a terminal and when it wasn't. This is perhaps one of the > more weird differences between the sbuild/pbuilder environment and > normal running of dpkg-buildpackage. Interesting. -- Rob Browning rlb @defaultvalue.org and @debian.org; previously @cs.utexas.edu GPG starting 2002-11-03 = 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
