On Fri, Nov 10, 2006 at 05:21:09PM -0800, Steve Langasek wrote: > On Sat, Nov 11, 2006 at 01:39:23AM +0100, Ana Guerrero wrote: > > > Hi again Steffen, > > > On Sat, Nov 11, 2006 at 12:42:03AM +0100, Ana Guerrero wrote: > > > This does not seem an arch problem. I have reproduced the problem > > > rebuilding > > > xoscope in a clean i386 etch chroot. > > > The problem is the package is missing a dependency on libsvga1-dev. > > Attached is the patch of my NMU. > > Ah, note that libsvga1-dev is only available on i386 and amd64, so this > package will now FTBFS on all other archs where it's currently built. For a > package named *x*oscope, I don't think SVGAlib support is the most important > feature -- indeed, I would suggest a build-conflicts with libsvga1-dev > instead of a build-depends :) >
gah, in the the README file included in the upstream source says you need libsvga1 to get oscope built. The upstream author and I did not think you could need build xoscope in more archs besides amd64 and i386 :) So, there are 2 solutions here: a) keep this dependency in amd64 and i386 and build oscope only in this archs (and maybe include README.Debian telling this problem) b) do not build oscope in any arch. After all, Xoscope is much more nice... (i would go for this). Anyway, it seems xoscope does not build in amd64 even before the NMU [1], so i guess a new NMU or MU should select one of the above solutions and fix the FTBFS in amd64. [1] http://buildd.debian.org/fetch.cgi?&pkg=xoscope&ver=1.12-2&arch=amd64&stamp=1143594333&file=log -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
