Your message dated Mon, 19 Oct 2009 11:02:26 +1300
with message-id <[email protected]>
and subject line
has caused the Debian Bug report #551333,
regarding docvert-openoffice.org: init script has has no "status"
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 [email protected]
immediately.)
--
551333: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=551333
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: docvert-openoffice.org
Version: 3.4-10
Severity: wishlist
Hi,
since openoffice.org 1:3.1.1-3 (and various other extension packages)
the upgrade explicitely fails when a OOo is running with a debconf error
instead of either running into a unopkg error (which then would still
return 0!!) or running into a corrupted services.rdb.
Of course, a running docvert-converter falso falls into this category
(and ps ax | grep soffice.bin catches it).
I am going to stop it in OOos maintainer scripts before the upgrade and
start it again after it (already committed).
Unfortunately /etc/init.d/docvert-converter has no status action
to see whether it is running so I need to do it unconditional *and*
it does not print out anything on start/stop either making people unaware
of it being started/stopped in the process.
Please add "status" and output.
Grüße/Regards,
Rene
--- End Message ---
--- Begin Message ---
Version: 3.4-11
--- End Message ---
