On 20 Sep 2008, at 1:42 pm, Thomas Viehmann wrote:

When I noticed that it was intentional, I brought it up on #debian-qa
for that very reason, we (in particular Christoph Berg and me) came to
the conclusion that it is indeed a policy violation and thus an RC bug. Overriding the local administrator's preference (that the invoke- rc.d is
designed to cater for) counts as one of the heavier sins in the Debian
policy book.

Yes, I know. That particular sin predates my adoption of the package, so I don't know why it was there. I've uploaded a patch now - what do I need to do to ensure it gets into Lenny?


Hmm - it's a shame to have such a discussion without actually involving
the package maintainer...
I usually try to hunt down the maintainer if there is doubt and,
naturally, would prefer to leave the resolution of bugs in packages you
maintain to you. Here, there seemed to be little doubt and you
apparently had not answered the bug report yet.

It was only reported a couple of days ago... :-)

Now that you're clearly
available, we value your expertise and look forward to either you fixing
the bug or learn about your insights into the deficiencies of using
invoke-rc.d. Please do not hesitate to contact me on IRC (tomv_w e.g. on
#debian-qa) or via mail if I can be of any help.

Thanks again for attending to this bug!

No problem - I do try to be reasonably responsive with regard to my packages. am-utils is probably nearing the end of its useful life; upstream development while not quite dead is certainly comatose, and it's missing a number of features people are going to want (no support for NFSv4, for example). While I think it's a useful package for Lenny, I'm not sure it will be quite as useful for Lenny+1.

Regards,

Tim



--
The Wellcome Trust Sanger Institute is operated by Genome Research Limited, a charity registered in England with number 1021457 and a company registered in England with number 2742969, whose registered office is 215 Euston Road, London, NW1 2BE.


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

Reply via email to