severity 571337 normal retitle 571337 FTBFS: /bin/sed: can't read /usr/lib/liblzma.la: No such file or directory thanks
On Thu, Feb 25, 2010 at 3:11 PM, Lucas Nussbaum <lu...@lucas-nussbaum.net> wrote: > severity 571337 serious WTF do you insist on marking serious a FTBFS when the package is successfully built on all archs in the current archive? Care to elaborate which section of the policy my package is violating? > On 25/02/10 at 13:26 +0100, Thibaut VARENE wrote: >> worksforme(tm) on ia64 (see attached build log). Seems like there's >> something wrong with amd64: > > The bug report says amd64, not ia64. I know, I can read. I've successfully built it on ia64 therefore something is wrong with *specifically* amd64. I don't see the flaw in the logic here. >> >> /bin/sed: can't read /usr/lib/liblzma.la: No such file or directory >> >> libtool: link: `/usr/lib/liblzma.la' is not a valid libtool archive >> >> make[3]: *** [mod_musicindex.la] Error 1 >> >> I can't make sense of this. I'm not linking against liblzma so this >> must be a side effect of something else. > > possibly, but only two packages are affected by that, so it's not that > widespread. Well I can't reproduce this bug and I don't know what's causing it. If only two other packages are affected, maybe you could tell me which they are, since you seem unwilling to figure out the common string here. Furthermore, why are you blaming my package when the fault lies apparently elsewhere? Again, the title of this bug seems to suggest you didn't see the kicker: >> >> /bin/sed: can't read /usr/lib/liblzma.la: No such file or directory Unless my package has somehow *removed* that file from the build system, the fault lies elsewhere. One more hint: on ia64 I'm not linking against liblzma, it's not even installed. Check the log. kthxbye -- Thibaut VARENE http://www.parisc-linux.org/~varenet/ -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
