Hi, IMHO, unstable is a good place for it. Upload Conglomerate in unstable and fill an RC bug "not usable at the moment" to be sure it will not go to testing, even if it's buggy. Everyone knows that unstable is not stable ;-) Sven Luther <sven.luther@wanadoo.fr> wrote: > On Wed, Jun 11, 2003 at 10:14:54PM +0200, Marcelo E. Magallon wrote: > > On Wed, Jun 11, 2003 at 08:59:21PM +0200, Sven Luther wrote: > > > > > Anyway, conglomerate is still not ready for inclusion in > > > unstable, it is buggy and dies frequently, i was thinking about > > > doing an experimental upload only, but i suppose i cannot close > > > the ITP/RFP bugs in this case, right ? > > > > Why not? A package would be available, which is what the submitter > > requested. > > But in experimental only, and given that experimental has almost no > visibility, and is difficult and discouraged to use, i would let the > RFP/ITP bug open, be it only to inform people a package is available > in experimental, so a new RFP/ITP doesn't get filled. > > I have no experience in uploading new packages to experimental, and > don't know what the usual practice is in such cases. I guess there > were few enough such cases that no clear practice exists anyway. > > Friendly, > > Sven Luther -- Arnaud Vandyck, STE fi, ULg Formateur Cellule Programmation.
Attachment:
pgpWxiyymbsod.pgp
Description: PGP signature