On Mon, Apr 03, 2000 at 03:48:00AM -0600, Jason Gunthorpe wrote:
> On Mon, 3 Apr 2000, Julian Gilbey wrote:
> > Like during the Perl transition period, or when a recent libstdc++
> > broke apt, or when su stopped being able to su, or when ....
> What you are describing is a problem with the package life cycle, not the
> replication of incoming. Let me reiterate:
> DO NOT USE INCOMING
> The files may be trojans, corrupt, partial, massively screwed, fail
> lintian, whatever. Massive, massive caution is advised!
Absolutely! I was just pointing out how "stable" and "reliable"
unstable can be. Using Incoming just makes things worse. I can't be
the only maintainer to have pulled packages from Incoming when I've
realised that I've made a serious mistake.
Can I also recommend the use of Roderick Schertler's dscverify program
in devscripts in conjunction with the debian-keyring package to ensure
that at the very least the package is properly signed.
Julian Gilbey, Dept of Maths, QMW, Univ. of London. J.D.Gilbey@qmw.ac.uk
Debian GNU/Linux Developer, see http://www.debian.org/~jdg
Donate free food to the world's hungry: see http://www.thehungersite.com/