On Sat, Feb 17, 2001 at 07:44:07PM +0100, Santiago Vila wrote:
> On 17 Feb 2001, James Troup wrote:
> > Santiago Vila <sanvila@unex.es> writes:
> > > > OTOH, if you do fork frozen, then you cause problems on "other"
> > > > architectures. Uploads that are sent to both places ("frozen
> > > > unstable" uploads), tend to get autobuilt twice (once for frozen,
> > > > once for unstable, which no longer works with katie),
> > > Katie should be fixed then.
> > Err, no, it shouldn't. Having two versions of a package with the same
> > filename but different md5sums & size is a) impossible with pools and
> > b) a Very Bad Thing anyway.
> I was referring to uploads which are built only once, of course.
> Many packages depend on libc6 only. Before katie it was possible to
> compile a package in a stable system and upload it for "stable unstable".
> If this is now forbidden, then it is a step backwards.
Nope, you can still do uploads for two places at once (stable, unstable is
the only possibility that's particularly meaningful: testing gets mapped
to unstable anyway, and experimental will probably just drop uploads
that are <= the version in unstable sooner or later), it's only when
autobuilders compile that upload twice (when architectures have separate
frozen and unstable autobuilders, in particular) that katie will object.
Also, it's a *lot* easier to move things around now with pools and some
of the tools James has written, so hopefully requests about the archive
won't take too long...
Cheers,
aj
--
Anthony Towns <aj@humbug.org.au> <http://azure.humbug.org.au/~aj/>
I don't speak for anyone save myself. GPG signed mail preferred.
``_Any_ increase in interface difficulty, in exchange for a benefit you
do not understand, cannot perceive, or don't care about, is too much.''
-- John S. Novak, III (The Humblest Man on the Net)
Attachment:
pgpT0zi0ES5Uo.pgp
Description: PGP signature