You are not logged in.
I have one machine that isn't updated so often. Long story short, I missed deadline by a day.
[2016-04-24 14:50] [ALPM] upgraded pacman (4.2.1-4 -> 5.0.1-2)
Everything seems to work fine. What are the repercussions of this to my system, what should I fix?
Offline
Some caches might be out of date. e.g. update-desktop-database, update-mime-database, gtk-update-icon-cache..
Basically, for packages that install a hook to /usr/share/libalpm/hooks/, you may need to run the hook manually.
$ pkgfile -d /usr/share/libalpm/hooks/
core/glib2
core/pacman
core/texinfo
extra/desktop-file-utils
extra/dkms
extra/gconf
extra/gdk-pixbuf2
extra/gtk-update-icon-cache
extra/gtk2
extra/gtk3
extra/shared-mime-info
community/appstream
community/etckeeper
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Offline
Wouldn't be enough just to reinstall packages from this list?
# pkgfile -d /usr/share/libalpm/hooks/
core/glib2
core/pacman
core/texinfo
extra/desktop-file-utils
extra/dkms
extra/gconf
extra/gdk-pixbuf2
extra/gtk-update-icon-cache
extra/gtk2
extra/gtk3
extra/shared-mime-info
community/appstream
community/etckeeper
Offline
Not necessarily. Those packages may or may not activate the hooks, and some of the hooks need to know specifically what was installed when they activated.
Offline
I would've suggested doing a
pacman -Sy && pacman -S pacman && pacman -Su
Hooks installed during a pacman transaction are still considered in order to be run at the end of that transaction, so as long as you have a version of pacman that supports hooks you should be okay.
...
Hooks don't trigger themselves on being installed (though it is possible some will come in the same package as a file that does trigger them), and some of them actually need to be run with input: the list of installed files that triggered them. For example, the texinfo hooks.
You will need to see about running the commands in the hooks by hand to make sure they are properly run. (e.g. You could delete the info directory file, then run install-info on each file in /usr/share/info/ to make sure it indexes only/all the files that actually exist.)
Last edited by eschwartz (2016-05-08 15:29:31)
Managing AUR repos The Right Way -- aurpublish (now a standalone tool)
Offline
I ended up doing:
pacman -Sy && pacman -S pacman && pacman -Su
/usr/bin/update-mime-database /usr/share/mime
/usr/bin/update-mime-database /usr/share/mime
/usr/bin/update-desktop-database --quiet
/usr/share/libalpm/scripts/gtk-update-icon-cache
/usr/share/libalpm/scripts/gtk-update-icon-cache
/usr/bin/gtk-query-immodules-3.0 --update-cach
/usr/bin/gtk-query-immodules-3.0 --update-cache
/usr/bin/gtk-query-immodules-2.0 --update-cache
/usr/bin/gio-querymodules /usr/lib/gio/modules
/usr/bin/gdk-pixbuf-query-loaders --update-cache
pacman -S glib2 texinfo desktop-file-utils dkms gconf gdk-pixbuf2 gtk-update-icon-cache gtk2 gtk3 shared-mime-info appstream etckeeper
Offline
...you didn't need to install all the packages with hooks. If you don't use those packages usually, there's no reason to install them now.
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Offline
Yeah, that's obvious but unless I missed something all of those were just reinstalled.
Offline