Bug#676463: me too and more info
Am Freitag, den 08.06.2012, 19:18 -0600 schrieb Gordon Haverland:
On June 8, 2012, Paul Menzel wrote:
Am Freitag, den 08.06.2012, 16:34 -0600 schrieb Gordon Haverland:
On June 8, 2012, Paul Menzel wrote:
thank for the follow up. In the future please add the
addresses of all people who responded in that bug thread
to CC.
Even better, import the messages from the mbox you get with
bts show --mbox 676463
What mbox? I don't get any mboxen.
Did you run the command? `bts` is in package `devscripts`.
Normally mutt opens automatically, but you can exit with `q`
right away. The downloaded mbox (mail box) files is stored
under
`~/.devscripts_cache/bts/`.
I just sent an email with kmail to the bugs address for this
bug.
I know. And I did not receive your message. I had to check the
Web page manually to see if there was an answer.
Sorry, I am not a developer or a Debian maintainer. I've lived
with UNIX since 1984 and computers since 1978. At heart, I am a
FORTRAN programmer, but I've dabbled in lots of stuff. I have
more than enough other stuff to keep me busy, I was just trying to
help. Downloading other mbox to add to my kmail isn't on my list
of things I want to do.
It takes one minute and saves everyone else time. I cannot tell you what
to do with your time. But frankly every one of us even following up on
reports has »more than enough other stuff to keep her/him busy«. And
most of the time it is just a matter if you take the time, which
unfortunately I had to do now.
By the way, if it is quicker you can also download the mbox file of one
message from the »mbox« link on the HTML bug report page. To keep
threading you just need the last one.
and reply to the appropriate message to keep the threading
and ease the life of everyone.
I'm sure if I do that all the time, someone will come along
with something else I am doing wrong.
Nobody has said such things to me yet. I am pretty sure that is
the preferred way.
Over the years, I seldom reply to all. As a general principle,
it seemed to cause more problems than it solved. I will try to do
this with bugreports, but I suspect even there, I will find more
people wondering why I wrote them, than people thanking me for
writing them.
Am Freitag, den 08.06.2012, 21:40 +0100 schrieb Roger Leigh:
On Fri, Jun 08, 2012 at 02:16:58PM -0600, Gordon Haverland wrote:
I have the same packages triggering init script
warnings.
In addition, I get a warning from insserv files about
K20scsi-idle and scsi-idle missing LSB tags and
overrides.
Could you possibly attach a copy of each failing script?
Please find the scripts attached. There seem to be also
three scripts from the `initscripts` package which cause
some problems.
/etc/init.d
/etc/init.d/rmnologin
/etc/init.d/umountnfs.sh
/etc/init.d/umountroot
/etc/init.d/sendsigs
/etc/init.d/single
/etc/init.d/killprocs
/etc/init.d/hostname.sh
/etc/init.d/mountall.sh
/etc/init.d/halt
/etc/init.d/umountfs
/etc/init.d/checkfs.sh
/etc/init.d/mountall-bootclean.sh
/etc/init.d/mountnfs.sh
/etc/init.d/bootlogs
/etc/init.d/mountdevsubfs.sh
/etc/init.d/bootmisc.sh
/etc/init.d/checkroot.sh
/etc/init.d/mountnfs-bootclean.sh
/etc/init.d/skeleton
/etc/init.d/reboot
/etc/init.d/mountoverflowtmp
/etc/init.d/rc.local
/etc/init.d/mtab.sh
/etc/init.d/mountkernfs.sh
/etc/init.d/urandom
Okay, I forced dpkg to install the new initscripts package
with -- force-depends. I now get 3 mystery files from
initscripts causing problems.
I also get these errors with `initscripts` 2.88dsf-22.1
installed. Only `sysv-rc` is currently not configured on this
system.
I looked at all the files from initscripts that install in
init.d/
[…]
Ok, reading the `postinst` script
is_unsafe_to_activate() {
retval=1
# Refuse to convert when there are obsolete init.d scripts left
# behind, as these tend to confuse the boot sequence.
echo info: Checking if it is safe to convert to dependency based
boot. 12
for package in $(dpkg -S $(find /etc/init.d -type f -perm /+x) \
2/dev/null | cut -d: -f1 | sort -u); do
obsolete_initscripts=$(dpkg-query -W -f='${Conffiles}\n'
$package | \
grep 'obsolete$' | grep -o '/etc/init.d/[^ ]\+') || :
if [ $obsolete_initscripts ]; then
for initscript in $obsolete_initscripts; do
if [ -e $initscript ]; then
Bug#676463: me too and more info
I have the same packages triggering init script warnings. In addition, I get a warning from insserv files about K20scsi-idle and scsi-idle missing LSB tags and overrides. Gord -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#676463: me too and more info
On Fri, Jun 08, 2012 at 02:16:58PM -0600, Gordon Haverland wrote: I have the same packages triggering init script warnings. In addition, I get a warning from insserv files about K20scsi-idle and scsi-idle missing LSB tags and overrides. Could you possibly attach a copy of each failing script? Thanks, Roger -- .''`. Roger Leigh : :' : Debian GNU/Linuxhttp://people.debian.org/~rleigh/ `. `' schroot and sbuild http://alioth.debian.org/projects/buildd-tools `-GPG Public Key F33D 281D 470A B443 6756 147C 07B3 C8BC 4083 E800 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#676463: me too and more info
Gordon, thank for the follow up. In the future please add the addresses of all people who responded in that bug thread to CC. Even better, import the messages from the mbox you get with bts show --mbox 676463 and reply to the appropriate message to keep the threading and ease the life of everyone. Am Freitag, den 08.06.2012, 21:40 +0100 schrieb Roger Leigh: On Fri, Jun 08, 2012 at 02:16:58PM -0600, Gordon Haverland wrote: I have the same packages triggering init script warnings. In addition, I get a warning from insserv files about K20scsi-idle and scsi-idle missing LSB tags and overrides. Could you possibly attach a copy of each failing script? Please find the scripts attached. There seem to be also three scripts from the `initscripts` package which cause some problems. /etc/init.d /etc/init.d/rmnologin /etc/init.d/umountnfs.sh /etc/init.d/umountroot /etc/init.d/sendsigs /etc/init.d/single /etc/init.d/killprocs /etc/init.d/hostname.sh /etc/init.d/mountall.sh /etc/init.d/halt /etc/init.d/umountfs /etc/init.d/checkfs.sh /etc/init.d/mountall-bootclean.sh /etc/init.d/mountnfs.sh /etc/init.d/bootlogs /etc/init.d/mountdevsubfs.sh /etc/init.d/bootmisc.sh /etc/init.d/checkroot.sh /etc/init.d/mountnfs-bootclean.sh /etc/init.d/skeleton /etc/init.d/reboot /etc/init.d/mountoverflowtmp /etc/init.d/rc.local /etc/init.d/mtab.sh /etc/init.d/mountkernfs.sh /etc/init.d/urandom But I do not know which. Thanks, Paul fuse Description: application/shellscript libchipcard-tools Description: application/shellscript smartmontools Description: application/shellscript signature.asc Description: This is a digitally signed message part
Bug#676463: me too and more info
On June 8, 2012, Paul Menzel wrote: Gordon, thank for the follow up. In the future please add the addresses of all people who responded in that bug thread to CC. Even better, import the messages from the mbox you get with bts show --mbox 676463 What mbox? I don't get any mboxen. I just sent an email with kmail to the bugs address for this bug. and reply to the appropriate message to keep the threading and ease the life of everyone. I'm sure if I do that all the time, someone will come along with something else I am doing wrong. Am Freitag, den 08.06.2012, 21:40 +0100 schrieb Roger Leigh: On Fri, Jun 08, 2012 at 02:16:58PM -0600, Gordon Haverland wrote: I have the same packages triggering init script warnings. In addition, I get a warning from insserv files about K20scsi-idle and scsi-idle missing LSB tags and overrides. Could you possibly attach a copy of each failing script? Please find the scripts attached. There seem to be also three scripts from the `initscripts` package which cause some problems. /etc/init.d /etc/init.d/rmnologin /etc/init.d/umountnfs.sh /etc/init.d/umountroot /etc/init.d/sendsigs /etc/init.d/single /etc/init.d/killprocs /etc/init.d/hostname.sh /etc/init.d/mountall.sh /etc/init.d/halt /etc/init.d/umountfs /etc/init.d/checkfs.sh /etc/init.d/mountall-bootclean.sh /etc/init.d/mountnfs.sh /etc/init.d/bootlogs /etc/init.d/mountdevsubfs.sh /etc/init.d/bootmisc.sh /etc/init.d/checkroot.sh /etc/init.d/mountnfs-bootclean.sh /etc/init.d/skeleton /etc/init.d/reboot /etc/init.d/mountoverflowtmp /etc/init.d/rc.local /etc/init.d/mtab.sh /etc/init.d/mountkernfs.sh /etc/init.d/urandom Okay, I forced dpkg to install the new initscripts package with -- force-depends. I now get 3 mystery files from initscripts causing problems. I looked at all the files from initscripts that install in init.d/ There are 6 files which do not have a last line which starts with a full colon. One that does has : exit 0 There are 6 files where the first executable line is not PATH= There are 6 files where the first non-empty line after ### END INIT INFO line is a comment line. There are 5 or 6 lines in the INIT INFO area, where there is no argument to the field, but there is whitespace after the full colon. I believe two of the files have a tab as the trailing whitespace, the remainder having a single space as the trailing whitespace. I think one file has both (one of each). Without knowing what your program is looking for, that is all I can guess at. Time to get back to writing a presentation on NORM. Gord -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#676463: me too and more info
Am Freitag, den 08.06.2012, 16:34 -0600 schrieb Gordon Haverland: On June 8, 2012, Paul Menzel wrote: thank for the follow up. In the future please add the addresses of all people who responded in that bug thread to CC. Even better, import the messages from the mbox you get with bts show --mbox 676463 What mbox? I don't get any mboxen. Did you run the command? `bts` is in package `devscripts`. Normally mutt opens automatically, but you can exit with `q` right away. The downloaded mbox (mail box) files is stored under `~/.devscripts_cache/bts/`. I just sent an email with kmail to the bugs address for this bug. I know. And I did not receive your message. I had to check the Web page manually to see if there was an answer. and reply to the appropriate message to keep the threading and ease the life of everyone. I'm sure if I do that all the time, someone will come along with something else I am doing wrong. Nobody has said such things to me yet. I am pretty sure that is the preferred way. Am Freitag, den 08.06.2012, 21:40 +0100 schrieb Roger Leigh: On Fri, Jun 08, 2012 at 02:16:58PM -0600, Gordon Haverland wrote: I have the same packages triggering init script warnings. In addition, I get a warning from insserv files about K20scsi-idle and scsi-idle missing LSB tags and overrides. Could you possibly attach a copy of each failing script? Please find the scripts attached. There seem to be also three scripts from the `initscripts` package which cause some problems. /etc/init.d /etc/init.d/rmnologin /etc/init.d/umountnfs.sh /etc/init.d/umountroot /etc/init.d/sendsigs /etc/init.d/single /etc/init.d/killprocs /etc/init.d/hostname.sh /etc/init.d/mountall.sh /etc/init.d/halt /etc/init.d/umountfs /etc/init.d/checkfs.sh /etc/init.d/mountall-bootclean.sh /etc/init.d/mountnfs.sh /etc/init.d/bootlogs /etc/init.d/mountdevsubfs.sh /etc/init.d/bootmisc.sh /etc/init.d/checkroot.sh /etc/init.d/mountnfs-bootclean.sh /etc/init.d/skeleton /etc/init.d/reboot /etc/init.d/mountoverflowtmp /etc/init.d/rc.local /etc/init.d/mtab.sh /etc/init.d/mountkernfs.sh /etc/init.d/urandom Okay, I forced dpkg to install the new initscripts package with -- force-depends. I now get 3 mystery files from initscripts causing problems. I also get these errors with `initscripts` 2.88dsf-22.1 installed. Only `sysv-rc` is currently not configured on this system. I looked at all the files from initscripts that install in init.d/ There are 6 files which do not have a last line which starts with a full colon. One that does has : exit 0 There are 6 files where the first executable line is not PATH= There are 6 files where the first non-empty line after ### END INIT INFO line is a comment line. There are 5 or 6 lines in the INIT INFO area, where there is no argument to the field, but there is whitespace after the full colon. I believe two of the files have a tab as the trailing whitespace, the remainder having a single space as the trailing whitespace. I think one file has both (one of each). Interesting. Did you fix these right away (and send patches)? :P Without knowing what your program is looking for, that is all I can guess at. Guess we have to check what the package scripts actually check. Time to get back to writing a presentation on NORM. Whatever NORM is, good luck with your presentation. Thanks, Paul signature.asc Description: This is a digitally signed message part
Bug#676463: me too and more info
On June 8, 2012, Paul Menzel wrote: Am Freitag, den 08.06.2012, 16:34 -0600 schrieb Gordon Haverland: On June 8, 2012, Paul Menzel wrote: thank for the follow up. In the future please add the addresses of all people who responded in that bug thread to CC. Even better, import the messages from the mbox you get with bts show --mbox 676463 What mbox? I don't get any mboxen. Did you run the command? `bts` is in package `devscripts`. Normally mutt opens automatically, but you can exit with `q` right away. The downloaded mbox (mail box) files is stored under `~/.devscripts_cache/bts/`. I just sent an email with kmail to the bugs address for this bug. I know. And I did not receive your message. I had to check the Web page manually to see if there was an answer. Sorry, I am not a developer or a Debian maintainer. I've lived with UNIX since 1984 and computers since 1978. At heart, I am a FORTRAN programmer, but I've dabbled in lots of stuff. I have more than enough other stuff to keep me busy, I was just trying to help. Downloading other mbox to add to my kmail isn't on my list of things I want to do. and reply to the appropriate message to keep the threading and ease the life of everyone. I'm sure if I do that all the time, someone will come along with something else I am doing wrong. Nobody has said such things to me yet. I am pretty sure that is the preferred way. Over the years, I seldom reply to all. As a general principle, it seemed to cause more problems than it solved. I will try to do this with bugreports, but I suspect even there, I will find more people wondering why I wrote them, than people thanking me for writing them. Am Freitag, den 08.06.2012, 21:40 +0100 schrieb Roger Leigh: On Fri, Jun 08, 2012 at 02:16:58PM -0600, Gordon Haverland wrote: I have the same packages triggering init script warnings. In addition, I get a warning from insserv files about K20scsi-idle and scsi-idle missing LSB tags and overrides. Could you possibly attach a copy of each failing script? Please find the scripts attached. There seem to be also three scripts from the `initscripts` package which cause some problems. /etc/init.d /etc/init.d/rmnologin /etc/init.d/umountnfs.sh /etc/init.d/umountroot /etc/init.d/sendsigs /etc/init.d/single /etc/init.d/killprocs /etc/init.d/hostname.sh /etc/init.d/mountall.sh /etc/init.d/halt /etc/init.d/umountfs /etc/init.d/checkfs.sh /etc/init.d/mountall-bootclean.sh /etc/init.d/mountnfs.sh /etc/init.d/bootlogs /etc/init.d/mountdevsubfs.sh /etc/init.d/bootmisc.sh /etc/init.d/checkroot.sh /etc/init.d/mountnfs-bootclean.sh /etc/init.d/skeleton /etc/init.d/reboot /etc/init.d/mountoverflowtmp /etc/init.d/rc.local /etc/init.d/mtab.sh /etc/init.d/mountkernfs.sh /etc/init.d/urandom Okay, I forced dpkg to install the new initscripts package with -- force-depends. I now get 3 mystery files from initscripts causing problems. I also get these errors with `initscripts` 2.88dsf-22.1 installed. Only `sysv-rc` is currently not configured on this system. I looked at all the files from initscripts that install in init.d/ There are 6 files which do not have a last line which starts with a full colon. One that does has : exit 0 There are 6 files where the first executable line is not PATH= There are 6 files where the first non-empty line after ### END INIT INFO line is a comment line. This doesn't seem to matter. There are 5 or 6 lines in the INIT INFO area, where there is no argument to the field, but there is whitespace after the full colon. I believe two of the files have a tab as the trailing whitespace, the remainder having a single space as the trailing whitespace. I think one file has both (one of each). This doesn't seem to matter. Interesting. Did you fix these right away (and send patches)? :P No, I didn't send patches. There seemed to be lots of times where trailiing whitespace caused problems for people in Perl, so that is one thing I look at. But, it is easy enough in Perl (and other languages) to strip trailing whitespace. Without knowing what your program is looking for, that is all I can guess at. Guess we have to check what the package scripts actually check. I also looked at INFO areas where a Short-Description had content and a Description didn't, where X-interactive was present and a couple of other things. So far nothing I change alters the fact 3 scripts from initscripts are causing problems. Looking at the logfile that sysv-rc.postinst produces also doesn't show 3 errors
