FS#7137 - Update/pacman3 kills rc.conf
Attached to Project:
Pacman
Opened by Johannes Jordan (FoPref) - Saturday, 12 May 2007, 10:52 GMT
Last edited by Aaron Griffin (phrakture) - Tuesday, 30 October 2007, 16:06 GMT
Opened by Johannes Jordan (FoPref) - Saturday, 12 May 2007, 10:52 GMT
Last edited by Aaron Griffin (phrakture) - Tuesday, 30 October 2007, 16:06 GMT
|
Details
After updating yesterday, including pacman3, I couldn't
restart my network properly. I found out the config was
wrong. The file rc.conf was completely new. There was also
rc.conf.pacnew, which was exactly the same file.
|
This task depends upon
Closed by Aaron Griffin (phrakture)
Tuesday, 30 October 2007, 16:06 GMT
Reason for closing: Not a bug
Additional comments about closing: See final comments
Tuesday, 30 October 2007, 16:06 GMT
Reason for closing: Not a bug
Additional comments about closing: See final comments
bug 7133.On postinstall of pacman3, a script in pacman.install is executed for fixing the md5sums in pacman database, and it relies on pacman -Qo
An invalid entry in pacman database could mess up pacman -Qo output and break this script.
Note, that's just one possibility of what could have went wrong during pacman 3 upgrade, and this happened to other users.
It could be something totally different in this case, it's hard to tell without having the output of pacman.install , which appears to be missing from your pacman.log (maybe this is logged only with pacman 3).
To see if it's the case here, try running for example :
pacman -Qo /etc/rc.conf
If this works fine, supposing for example that you've pacman-3.0.4-2 installed, you could try running the script again like this :
sh /var/lib/pacman/local/pacman-3.0.4-2/install _resetbackups
I reran the install script as described. It indeed didn't work correctly the first time. Thank you!