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

Bug#537243: marked as done ([checks/init.d] allow Python init scripts without warning)

Your message dated Sat, 20 Aug 2011 15:05:10 +0200
with message-id <4E4FB106.1040505@thykier.net>
and subject line Re: Bug#537243: lintian: init.d-script-uses-usr-interpreter should not error when  using Python
has caused the Debian Bug report #537243,
regarding [checks/init.d] allow Python init scripts without warning
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.)


-- 
537243: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=537243
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: lintian
Version: 2.2.13
Severity: normal

I have an application which has an init.d script written in Python,
intended for use in desktop environments.  The script will not
start before /usr is mounted (due to the runlevel that it starts on),
and as Python is virtually an Essential package, it is very unlikely to
be removed from a system.

Please either add an exception for Python, for scripts starting in the
multiuser runlevels, or both.

--
Luke Faraone
http://luke.faraone.cc

--- End Message ---
--- Begin Message --- 
Hi,

This has been marked "wontfix" for over 2 years and since (to my
knowledge) the situation has not changed I am closing it.  Should the
policy allow python in init.d scripts (or if python becomes essential),
feel free to reopen this bug.

~Niels

--- End Message ---
Reply to: