Notification!!
You are a certified winner of£250,000.00Pounds by
the microsoft award 2009 fill in below your names,
address,sex, age, telephone, occupation.
Regards
Mr P. Griffin
pg.pg...@btinternet.com
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "
Your message dated Sat, 25 Apr 2009 14:55:17 +0200
with message-id <200904251455.17909.f...@debian.org>
and subject line log_end_msg in /lib/lsb/init-functions always returns 1 =>
breaks acpid update
has caused the Debian Bug report #524823,
regarding invoke-rc.d: initscript, action "start" faile
Your message dated Sat, 18 Apr 2009 21:02:35 +
with message-id
and subject line Bug#524433: fixed in splashy 0.3.13-5
has caused the Debian Bug report #524433,
regarding invoke-rc.d: initscript, action "start" failed on install
to be marked as done.
This means that you claim that the problem
Your message dated Sat, 18 Apr 2009 21:02:34 +
with message-id
and subject line Bug#523187: fixed in splashy 0.3.13-5
has caused the Debian Bug report #523187,
regarding invoke-rc.d: initscript, action "start" failed on install
to be marked as done.
This means that you clai
Your message dated Sat, 18 Apr 2009 21:02:34 +
with message-id
and subject line Bug#523823: fixed in splashy 0.3.13-5
has caused the Debian Bug report #523823,
regarding invoke-rc.d: initscript, action "start" failed on install
to be marked as done.
This means that you claim that the problem
Your message dated Sat, 18 Apr 2009 21:02:35 +
with message-id
and subject line Bug#524317: fixed in splashy 0.3.13-5
has caused the Debian Bug report #524317,
regarding invoke-rc.d: initscript, action "start" failed on install
to be marked as done.
This means that you claim that the problem
Your message dated Sat, 18 Apr 2009 21:02:35 +
with message-id
and subject line Bug#524316: fixed in splashy 0.3.13-5
has caused the Debian Bug report #524316,
regarding invoke-rc.d: initscript, action "start" failed on install
to be marked as done.
This means that you claim that the problem
I can confirm this bug.
It seems that *all* scripts in /etc/init.d/ exit with a status of 1,
regardless of whether an error has actually happened or not.
Moving /etc/lsb-base-logging.sh out of the way (ie. renaming or removing
it) solves the problem.
I am not sure, but is it sane to have any retu
Ouch. Time to revert our last update I guess.
--
A bug magnet
On Apr 16, 2009, at 17:09, luca boncompagni wrote:
Hi,
I'm not able to upgrade acpid because I installed splashy, but I do
not enable it, I do not pass the splashy options in the boot
parameters. The upgrade scripts try to st
Hi,
I'm not able to upgrade acpid because I installed splashy, but I do not
enable it, I do not pass the splashy options in the boot parameters. The
upgrade scripts try to stop acpid but it fails because in the log_end_msg
functions it fails in the line 341 of "/etc/lsb-base-logging.sh"
338
On Fri, 2009-04-10 at 14:10 -0400, Luis Mondesi wrote:
> We updated Splashy's /etc/lsb-base-logging.sh to avoid some of these
> issues (especially when the package is removed.)
>
> What's the version being used?
splashy:
Installed: 0.3.13-4
Candidate: 0.3.13-4
Version table:
*** 0.3.13-4 0
We updated Splashy's /etc/lsb-base-logging.sh to avoid some of these
issues (especially when the package is removed.)
What's the version being used?
On Thu, Apr 9, 2009 at 2:26 AM, Thomas Renard wrote:
>>
>> Looks like a splashy related problem
>> Thomas, do you also have splashy installed, ie.
>
> Looks like a splashy related problem
> Thomas, do you also have splashy installed, ie. do you have a file
> /etc/lsb-base-logging.sh ?
>
I have :-(
So, then I tried your trick with renaming lsb-base-loging.sh and then the
update works with no problem.
Looks like uninstalling splashy for no
13 matches
Mail list logo
