Hi, Björn Stenberg wrote: > 1) Debcheck often reports "Package declares a build time dependency on [pkg] > which cannot be statisfied on [port]." Must all such build time dependencies > be resolved before a package is accepted into testing?
No. testing doesn't care about Builddeps. and you can safely ignore that messages for sh and hurd-i386... > 2) If (1) is true, how come some packages have unresolved builddeps for > testing and stable? New ports? > > 3) If (1) is false, where do I look to see why libpcap is not in testing yet? > It is a 260 days old valid candidate with no unresolved dependencies. Maybe some other packagees would break when the new went intop testing ans needs to be recompiled against the new? > 4) What is the best way to find out why cfitsio depends on gcc-3.3? I can find > it by searching through all buildd logs and knowing that libgcc1 is part of > gcc-3.3. Is there an easier/quicker way? looking in the Packages files? (do in on auric directly or d/l them and do it at home) > 5) Both gcc-3.2 and gcc-3.3 appear to contain libgcc1. Why does cfitsio depend > on gcc-3.3 and not gcc-3.2? Because gcc-3.2 depends on gcc-3.3? lobstdc++5 noe comes from gcc-3.3 libgcc1 IIRC from gcc-3.2 So when your package depends on both packages then it depends on both ;) > (As it currently looks, both gcc-3.2 and gcc-3.3 are actually valid candidates both are now in: [EMAIL PROTECTED]:~$ madison gcc-3.3 -s testing gcc-3.3 | 1:3.3-0pre5 | testing | alpha, arm, hppa, i386, ia64, m68k, mips, mipsel, powerpc, s390, sparc gcc-3.3 | 1:3.3ds5-0pre5 | testing | source [EMAIL PROTECTED]:~$ madison gcc-3.2 -s testing gcc-3.2 | 1:3.2.3-0pre9 | testing | alpha, arm, hppa, i386, ia64, m68k, mips, mipsel, powerpc, s390, sparc gcc-3.2 | 1:3.2.3ds8-0pre9 | testing | source [EMAIL PROTECTED]:~$ When they are supposed to go in, they only go in after evening's dinstall run. Regards, Rene -- .''`. Rene Engelhard -- Debian GNU/Linux Developer : :' : http://www.debian.org | http://people.debian.org/~rene/ `. `' [EMAIL PROTECTED] | GnuPG-Key ID: 248AEB73 `- Fingerprint: 41FA F208 28D4 7CA5 19BB 7AD9 F859 90B0 248A EB73
pgp449eHnlGVq.pgp
Description: PGP signature
