195 days is a lot of time to have an important package orphaned. At 6 or so months of "orphaned-ness", if a maintainer is not found, one should and IMHO must look at the very real at that point possibility of going on without it. If this necessitates further changes as in removal of an entire architecture, then I'd say that it's time to shit or get off the pot, to use the vernacular. It can't be too damned important if nobody steps up and adopts it for ~6.5 months... ATM, though, it's not a real issue, but I think that in addition to the bug horizons, there needs to be a wnpp check on a freeze: orphaned packages die during a freeze unless adoped post haste (I can't remember if this means that silo would've died during the potato freeze...).
On Wed, 27 Dec 2000, Ben Collins wrote: > On Tue, Dec 26, 2000 at 07:06:30PM -0700, John Galt wrote: > > > > If it's so important, why is it orphaned? I'm thinking that if the SPARC > > folx can't be bothered to maintain their bootloader, perhaps the port's > > utilization of resources needs to be called into question... What's the > > point in Debian proper showing more support for SPARC than the SPARC > > community shows for Debian? > > > > What the fuck are you talking about!?! For one the damn thing isn't > changed that often. Upstream isn't making frequent updates, and the > fucking thing works. You need to find your red herrings some place else. > > -- Pardon me, but you have obviously mistaken me for someone who gives a damn. email [EMAIL PROTECTED]
