Weblog entry #1 for rob
See all weblog entries made by rob.
#1
Update Manager woe.
Posted by rob on Wed 16 May 2007 at 17:21
Decided to try the new Update Manager in Etch which, I see, is just a front-end for synaptic. It brought up the most recent security updates [samba (16May07)], I accepted, and the manager proceeded to completely hose samba and all its related packages; samba, samba-common, samba-doc, smbclient and swat. Aptitude says samba is the broken package but cannot repair it and goes into dependency hell saying it can't repair it because of swat, then samba-common and on and on nor will it remove, purge or reinstall samba or any of the related packages.
Anyone else run into this and find a fix?
Anyone else run into this and find a fix?
Comments on this Entry
I checked the old samba script in /etc/rc2.d which aptitude returned as part of the errors. The script was properly disabled to K09samba for an update. On a whim, I tried enabling it to S91samba, nothing. I next tried just commenting out the script with old.K09samba (you cannot use a # sign here) and, lo and behold, that did the trick. The new samba package was installed and all the related packages I use, that were already updated, were deemed fit for service and swat was finally configured.
Somewhere between aptitude, synaptic and dpkg I believe, based on what aptitude was saying, there was a glitch reading the samba run-level script in the new package and the old script in /etc/rc2.d but I don't possess the knowledge/skill to run it down.
robin
Somewhere between aptitude, synaptic and dpkg I believe, based on what aptitude was saying, there was a glitch reading the samba run-level script in the new package and the old script in /etc/rc2.d but I don't possess the knowledge/skill to run it down.
robin
[ Parent | Reply to this comment ]
Posted by Anonymous (72.192.xx.xx) on Fri 18 May 2007 at 00:03
I'm fiddling with this in between remodeling the house (been hanging a french-door the last several hours), so, sorry for being choppy here. My wife thinks the house is more important then playing with Debian; silly thing!
It appears that the symbolic link /etc/rc2.d/S20samba (yeah 'S20', not 'S91') somehow became corrupted or ??? as it appeared as an executable there rather than a soft link and that is what may have caused the update problem for samba. I deleted it and made a new link:
ln -s /etc/init.d/samba S20samba
So, all is well and debthree, my laptop's name and net-mate to deb's one and two and the wife's XP machine, is no longer pining for the fiords.
It appears that the symbolic link /etc/rc2.d/S20samba (yeah 'S20', not 'S91') somehow became corrupted or ??? as it appeared as an executable there rather than a soft link and that is what may have caused the update problem for samba. I deleted it and made a new link:
ln -s /etc/init.d/samba S20samba
So, all is well and debthree, my laptop's name and net-mate to deb's one and two and the wife's XP machine, is no longer pining for the fiords.
[ Parent | Reply to this comment ]
Make that:
ln -s ../init.d/samba S20samba
Ooo, if this were /. I'd be hammered to a pulp for responding so many times to my own post.
ln -s ../init.d/samba S20samba
Ooo, if this were /. I'd be hammered to a pulp for responding so many times to my own post.
[ Parent | Reply to this comment ]