Thomas Bushnell BSG <[EMAIL PROTECTED]> writes:
> So my question from Monday is still there. Perhaps following the
> suggestion in the bug log will solve the problem?
Here's where things stand:
- I tried building the package in merulo's unstable chroot. That
worked fine. Since the chroot doesn't have slib installed, and
neither did the buildd (according to the log), slib's not likely
to be the problem.
- The other suggestion was to make sure guile-1.6-libs isn't
installed. If the buildd starts from scratch for each package
(does it?), then that guile-1.6-libs couldn't be the problem. If
the buildd doesn't start from scratch, then it would seem a little
surprising if the problem only occurs on ia64.
(In truth, an existing installation of Guile shouldn't affect a
Guile build, but if it does, then the problem needs to be fixed
and the fix needs to be incorporated upstream.)
If we could experiment in the buildd environment, it would be a lot
easier to figure out what's going on. If nothing else, if
guile-1.6-libs is installed there, we could try purging it, and see if
that fixes the problem.
However, as mentioned above, I'm still a little suspicious of the idea
that it's a guile-1.6-libs problem, but it's hard to tell given the
available evidence.
I suppose we could just add a "Build-Conflicts: guile-1.6-libs" and
see what happens, though that's a somewhat scattershot approach, and
even if it worked, I'd still really want to find the root cause.
> The bug has now been blocking gnucash from entering testing for three
> months...
I'd certainly like to fix the problem too, and it could well be that
I'm overlooking something obvious.
--
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]
