[pacman-dev] Fix for overwritten NoUpgrade files
Here is a small shell script to fix issues some people have been having with the removal of the NoUpgrade lines. A quick summary of what this does- it will scan the default list of NoUpgrade files in addition to any you have added on your own, and reset the stored md5sum in the database so the next upgrade will force a pacnew file to be written. This will be a one time deal, and will allow immediate removal of any NoUpgrade lines from pacman.conf. Questions or comments on this thread if you have them. -Dan
On 4/23/07, Dan McGee <dpmcgee@gmail.com> wrote:
Here is a small shell script to fix issues some people have been having with the removal of the NoUpgrade lines. A quick summary of what this does- it will scan the default list of NoUpgrade files in addition to any you have added on your own, and reset the stored md5sum in the database so the next upgrade will force a pacnew file to be written. This will be a one time deal, and will allow immediate removal of any NoUpgrade lines from pacman.conf.
Questions or comments on this thread if you have them.
-Dan
Replying to myself to test the mailman archives.
On 4/23/07, Dan McGee <dpmcgee@gmail.com> wrote:
On 4/23/07, Dan McGee <dpmcgee@gmail.com> wrote:
Here is a small shell script to fix issues some people have been having with the removal of the NoUpgrade lines. A quick summary of what this does- it will scan the default list of NoUpgrade files in addition to any you have added on your own, and reset the stored md5sum in the database so the next upgrade will force a pacnew file to be written. This will be a one time deal, and will allow immediate removal of any NoUpgrade lines from pacman.conf.
Questions or comments on this thread if you have them.
-Dan
Replying to myself to test the mailman archives.
FYI this will be making it's way into the pacman.install file on post_upgrade, to autocorrect the md5 issue.
Looks good to me. I ran the script, then removed the NoUpgrade from pacman.conf , then reinstalled the packages owning the default files in NoUpgrade : pacman -S filesystem grub initscripts lilo module-init-tools sudo so it extracted a bunch of unneeded pacnew files that I removed : rm /etc/*.pacnew /boot/grub/menu.lst.pacnew but it also fixed the database in the same time :) With pacman 3, I wouldn't even have needed to remove the files from NoUpgrade before reinstalling the packages. It would still have fixed the database. So well, looks like it at least works correctly in the common case :d
On 4/23/07, Xavier <shiningxc@gmail.com> wrote:
Looks good to me. I ran the script, then removed the NoUpgrade from pacman.conf , then reinstalled the packages owning the default files in NoUpgrade : pacman -S filesystem grub initscripts lilo module-init-tools sudo
so it extracted a bunch of unneeded pacnew files that I removed : rm /etc/*.pacnew /boot/grub/menu.lst.pacnew but it also fixed the database in the same time :)
With pacman 3, I wouldn't even have needed to remove the files from NoUpgrade before reinstalling the packages. It would still have fixed the database.
So well, looks like it at least works correctly in the common case :d
Yeah, I got to be the lucky one to test this first last night. I hope it works fine since I had to put my system out there. :) -Dan
participants (3)
-
Aaron Griffin
-
Dan McGee
-
Xavier