Bug#350088: Forcibly orphaning mhash?

2006-05-09 Thread Nathanael Nerode
As discussed in this bug, mhash's maintainer appears to be MIA or out to lunch.

Is it OK if we forcibly orphan the package now?

-- 
Nathanael Nerode  [EMAIL PROTECTED]

It's just a goddamned piece of paper.
-- President Bush, referring to the US Constitution
http://www.capitolhillblue.com/artman/publish/article_7779.shtml


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#350088: Forcibly orphaning mhash?

2006-05-09 Thread Chris Hanson
Nathanael Nerode wrote:
 As discussed in this bug, mhash's maintainer appears to be MIA or out to 
 lunch.
 
 Is it OK if we forcibly orphan the package now?

What exactly do you want me to do?  I released a new version recently,
and as far as I can tell there's no consensus on whether the suggested
fixes actually work.  Plus, the upstream sources don't seem to be
generally accessible now, so it's hard to tell what's going on there.

So I continue to wait for something useful to happen.

Plus, I've been teaching a new class this term and consequently have
very little time.  But the term's almost over.

Do you have any specific suggestion as to what should happen?


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#350088: Forcibly orphaning mhash?

2006-05-09 Thread Thomas Bushnell BSG
Nathanael Nerode [EMAIL PROTECTED] writes:

 As discussed in this bug, mhash's maintainer appears to be MIA or
 out to lunch.

 Is it OK if we forcibly orphan the package now?

There is no procedure for forcible orphaning the package.

If you have a fix for the bug (the bug log seems to suggest that
nobody has a patch at the moment), then please add it to the log;
since the bug is severity grave, you can certainly then do a proper
NMU.

We do not forcibly orphan anything; that's a silly procedure, because
all it can do is change a package with a less-than-ideal maintainer
into a package with none at all.  There is a procedure for hijacking,
but this is hardly a case.  It's not like a clearly winning patch is
being ignored.

Thomas


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]