[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#688084: marked as done (Please consider tagging #612918 wheezy-ignore)

Your message dated Sat, 13 Oct 2012 19:22:20 +0100
with message-id <e0852aa8abe713422a8585e23d07e0c5@mail.adsl.funky-badger.org>
and subject line Re: Bug#688084: Please consider tagging #612918 wheezy-ignore
has caused the Debian Bug report #688084,
regarding Please consider tagging #612918 wheezy-ignore
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
688084: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=688084
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
package: release.debian.org
severity: normal

Bug #612918 involves a violation of the FHS (using a file in /etc as a
state file), thus violating debian policy.  Apparently there was going
to be some involved upstream work to correct the problem, but after
over a year, that appears not to have happened.  Given that and the
fact that practically speaking, its only really problematic in a
read-only /etc environment, and users in that situation can choose a
different network manager anyway, I think it would be appropriate to
ignore it for wheezy until that upstream work actually gets done.

Best wishes,
Mike

--- End Message ---
--- Begin Message --- 
On 19.09.2012 07:52, Michael Gilbert wrote:
Bug #612918 involves a violation of the FHS (using a file in /etc as a state file), thus violating debian policy. Apparently there was going 
to be some involved upstream work to correct the problem, but after
over a year, that appears not to have happened.
Further activity in #612918 suggests this isn't actually an issue any more, and that bug is now closed; therefore doing the same with this one. 

Regards,

Adam

--- End Message ---
Reply to: