On Tue, Apr 05, 2005 at 02:39:47PM +0200, Joost Yervante Damad wrote: > On Tuesday 05 April 2005 10:55, Steve Langasek wrote: > > On Tue, Apr 05, 2005 at 08:23:58AM +0200, Joost Yervante Damad wrote: > > > On Tuesday 05 April 2005 04:57, Henrique de Moraes Holschuh wrote: > > > > Package: openmsx > > > > Severity: grave > > > > Justification: renders package unusable > > > > > > > > openmsx depends on libgcc1 (>= 1:4.0) which is NOT in sid. > > > > > > > > Please build it using gcc 3.4 in a sid chroot. > > > > > > This is really strange, as I build it in a "testing" chroot. I'll look > > > into it tonight.
> > Er, why do you do that? Packages uploaded to unstable are expected to be > > built against unstable, not testing... > Well, it relaxes the depends slightly. This allowed friends of me running > testing to test the packages also, yet it still runs fine in unstable. > Is this not allowed? All of the autobuilders will build against unstable, not against testing. If you do this to an arch: any package during a library transition, you will get skewed dependencies. You may also upload a package that fails to build on all architectures in unstable, without noticing because you built against testing. In fact, this package is failing to build on the powerpc autobuilder, which suggests wrong build-dependencies besides. http://buildd.debian.org/fetch.php?&pkg=openmsx&ver=0.5.0-10&arch=powerpc&stamp=1112640541&file=log&as=raw -- Steve Langasek postmodern programmer
signature.asc
Description: Digital signature
