Reopening this bug for Natty. This bug was re-introduced by the last
merge which dropped part of the fix.
** Also affects: lintian (Ubuntu Natty)
Importance: Medium
Assignee: Jos Boumans (jib)
Status: Fix Released
** Changed in: lintian (Ubuntu Natty)
Status: Fix Released
This bug was fixed in the package lintian - 2.4.3ubuntu3
---
lintian (2.4.3ubuntu3) natty; urgency=low
* checks/init.d: fix LP: #496798 again; upstream only took part of our
patch and the rest of the fix was dropped in the last merge; per
maintainer's comments in Debian bug
** Changed in: lintian (Debian)
Status: Unknown = Fix Released
--
lintian should not complain about upstart jobs not looking like init scripts
https://bugs.launchpad.net/bugs/496798
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Bug watch added: Debian Bug tracker #569492
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=569492
** Also affects: lintian (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=569492
Importance: Unknown
Status: Unknown
--
lintian should not complain about upstart
As for a test, grab the source to the Ubuntu eucalyptus package (and its
build-deps), and build it.
Without the patched lintian, you will see this output:
Now running lintian...
W: eucalyptus source: patch-system-but-direct-changes-in-diff aclocal.m4 and 29
more
W: eucalyptus source:
This bug was fixed in the package lintian - 2.3.3ubuntu2
---
lintian (2.3.3ubuntu2) lucid; urgency=low
[ Jos Boumans ]
* Avoid checking upstart jobs linked from /etc/init.d (LP: #496798),
patch submitted to Debian bug #569492
-- Dustin Kirkland kirkl...@ubuntu.com Thu, 11
Hi Steve,
Thanks for the explanation. Since the 'lsb-header' argument support
also needs to be implemented on Ubuntu's upstart-job, do you think it
would be possible to help Michael implement it? I assume some of the
implementation details were already discussed with Scott.
It would help both
Cool, thanks, Jos.
I have a similar patch that I've been using on my local system
(attached).
So I'm looking for affirmation from the Lintian developers here... We'd
like to patch Lucid's lintian package, but would like to do so in a
manner that will be also be carried upstream in Debian. Can
Jos, would be great if you could provide a test too (take a look at
t/tests/).
But taking a look at the implementation:
Once upstart-job is included in Debian and made the default it will
return the LSB headers when called with a special argument (I don't
remeber the details right now). As such,
On Tue, Dec 29, 2009 at 04:47:08AM -, Raphael Geissert wrote:
I'm not sure if the update-rc.d call needs to be dropped either.
In Ubuntu, where upstart is the only supported init implementation,
update-rc.d is not called because the extra symlinks have been shown to
cause boot-time overhead.
[Raphael Geissert]
Jos, would be great if you could provide a test too (take a look at t/tests/).
But taking a look at the implementation:
Once upstart-job is included in Debian and made the default it will
return the LSB headers when called with a special argument (I don't
remeber the
Attached is a patch for the issue described. Tests confirm both warnings
are now no longer present.
Output for sample .deb is now:
W: eucalyptus-cc: executable-not-elf-or-script
./usr/lib/axis2/services/EucalyptusCC/services.xml
W: eucalyptus-cc: executable-not-elf-or-script
** Changed in: lintian (Ubuntu)
Assignee: (unassigned) = Jos Boumans (jib)
--
lintian should not complain about upstart jobs not looking like init scripts
https://bugs.launchpad.net/bugs/496798
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Assigning the bug to Jos, and leaving a few pointers behind...
1) Grab the source to Lintian in Lucid (apt-get source lintian, or dget the
source .dsc file)
2) Look at checks/init.d*; Basically, these are getting applied to all
scripts installed in /etc/init.d. We're dropping a symlink to
Dustin Kirkland dustin.kirkl...@gmail.com writes:
Assigning the bug to Jos, and leaving a few pointers behind...
1) Grab the source to Lintian in Lucid (apt-get source lintian, or dget
the source .dsc file)
2) Look at checks/init.d*; Basically, these are getting applied to all
Thus Russ, will do, as soon as Jos gets it fixed ;-) This bug will be
good education, end-to-end ;-)
--
lintian should not complain about upstart jobs not looking like init scripts
https://bugs.launchpad.net/bugs/496798
You received this bug notification because you are a member of Ubuntu
Bugs,
** Changed in: lintian (Ubuntu)
Status: New = Confirmed
** Changed in: lintian (Ubuntu)
Importance: Undecided = Medium
--
lintian should not complain about upstart jobs not looking like init scripts
https://bugs.launchpad.net/bugs/496798
You received this bug notification because you
17 matches
Mail list logo
