Re: Upgrade problems for sysvinit 2.86.ds1-16 -> 2.86.ds1-18

2006-09-10 Thread Bastian Venthur
Petter Reinholdtsen wrote: > [Bastian Venthur] >> Looks like there is still something left to do for the user after this >> step. Eg, on my machine KDM did not start up automatically anymore, as >> well as WLAN. Those are two things I encountered directly and are >> probably easy to fix, but I'm qu

Re: Upgrade problems for sysvinit 2.86.ds1-16 -> 2.86.ds1-18

2006-09-10 Thread Stefan Bellon
Petter Reinholdtsen wrote: > sed -n "/installed sysvinit 2.86.ds1-16/,/installed sysvinit > 2.86.ds1-18/p" /var/log/dpkg.log | awk '/ upgrade / { print $4 } / > installed / { print $5 }' | sort -u But this script only works when the user installed 2.86.ds1-16. In my case, I upgraded from 2.86

Re: Upgrade problems for sysvinit 2.86.ds1-16 -> 2.86.ds1-18

2006-09-10 Thread Petter Reinholdtsen
[Kevin Mark] > I thought that 'reinstall' seems very time consuming and thought > that there may be a diffent way to do it. Would this work for > (most|all)? cheers, Yes, I believe so. So the latest incarnation of the script to fix this problem uses this apporach. It is in sysv-rc version 2.86.

Re: Upgrade problems for sysvinit 2.86.ds1-16 -> 2.86.ds1-18

2006-09-10 Thread Petter Reinholdtsen
[Bastian Venthur] > Looks like there is still something left to do for the user after this > step. Eg, on my machine KDM did not start up automatically anymore, as > well as WLAN. Those are two things I encountered directly and are > probably easy to fix, but I'm quite uncertain if there is someth

Re: Upgrade problems for sysvinit 2.86.ds1-16 -> 2.86.ds1-18

2006-09-09 Thread Kevin Mark
Hi Petter, On Fri, Sep 08, 2006 at 07:22:53PM +0200, Petter Reinholdtsen wrote: > > In version 2.86.ds1-16 of the sysv-rc package released 2006-09-06, the > update-rc.d script was broken. When used to to update symlinks it > would remove all symlinks for a init.d script if such symlinks > existed

Re: Upgrade problems for sysvinit 2.86.ds1-16 -> 2.86.ds1-18

2006-09-09 Thread Petter Reinholdtsen
Sorry for the noise. Here is yet another script fragment, this time to extract the list of installed and upgraded packages in the dangerous period. I did not know about the /var/log/dpkg.log file before this morning. sed -n "/installed sysvinit 2.86.ds1-16/,/installed sysvinit 2.86.ds1-18/p"

Re: Upgrade problems for sysvinit 2.86.ds1-16 -> 2.86.ds1-18

2006-09-08 Thread Petter Reinholdtsen
[Petter Reinholdtsen] > A quick way out is to reinstall all the packages with scripts in > /etc/init.d/. This way proved to be too quick, trying to reinstall removed but not purged packages with init.d scripts left behind in /etc/init.d/. I recommend using something like this instead, to only rei

Re: Upgrade problems for sysvinit 2.86.ds1-16 -> 2.86.ds1-18

2006-09-08 Thread Bastian Venthur
Petter Reinholdtsen wrote: > Those with packages being broken from this bug can fix it by using > 'apt-get --reinstall install package' on the affected packages. A > quick way out is to reinstall all the packages with scripts in > /etc/init.d/. > > for p in `dpkg -S /etc/init.d/*|cut -d: -f1|so