-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello list,
I have just had a new package sponsored (Thanks Sam!) that declares a build-dep on svgalibg1-dev. This causes the buildd to fail on many archs (eg. sparc, s390, mips, etc...) because apt cannot satisfy the dependancy. I did some research on other packages that use svgalib, and have seen two possible solutions: 1) Change the build-dep to 'svgalibg1-dev [i386]', and make the svga binary package 'Architecture: i386'. (eg. gnuboy) 2) Change the build-dep to 'svgalibg1-dev | svgalib-dummyg1'. (eg. acidwarp) What are the pros/cons of each of these methods? Is there another generally accepted solution to this problem that I haven't found? Thanks for your input! Joe Nahmias, DD wannabe [EMAIL PROTECTED] PS - Here is the relevant snippet from one of the buildd logs that failed: ** Using build dependencies supplied by package: Build-Depends: debhelper (>> 3.0.0), libz-dev, svgalibg1-dev, libsdl-dev Checking for already installed source dependencies... debhelper: missing libz-dev: missing svgalibg1-dev: missing libsdl-dev: missing Checking for source dependency conflicts... /usr/bin/sudo /usr/bin/apt-get --purge $CHROOT_OPTIONS -q -y install debhelper libz-dev svgalibg1-dev libsdl-dev Reading Package Lists... Building Dependency Tree... Note, selecting zlib1g-dev instead of libz-dev Package svgalibg1-dev has no available version, but exists in the database. This typically means that the package was mentioned in a dependency and never uploaded, has been obsoleted or is not available with the contents of sources.list However the following packages replace it: svgalib-dummyg1 E: Package svgalibg1-dev has no installation candidate apt-get failed. Package installation failed -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.0 (GNU/Linux) iD8DBQE+EPbXKl23+OYWEqURAgS2AJ9xZ0Q21nQB0BJEMwmGSdZaMOGiRgCcCOcV /9gCMC36gDA7MdmtWAqiKPY= =HY/g -----END PGP SIGNATURE----- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
