J'ai fait ce jour une tentative de mise à jour complète du système.
Normalement, je la fais tous les jours ou presque. La dernière remonte au 7 novembre, sans problème.
Ici, après un long WE, j'ai les erreurs suivantes lors de la mise à jour.
Dans la console, j'ai les messages suivants :
Le chargement des paquets se fait normalement, mais au moment de l'installation, cela bloque(116/116) vérification des clés dans le trousseau [#######################] 100%
(116/116) vérification de l’intégrité des paquets [#######################] 100%
(116/116) chargement des fichiers des paquets [#######################] 100%
(116/116) analyse des conflits entre fichiers [#######################] 100%
(116/116) vérification de l’espace disque disponible [#######################] 100%
:: Exécution des crochets de pré-transaction…
(1/3) Removing linux initcpios...
(2/3) Remove DKMS modules
(3/3) Checking Arch News ...
There are 9 unread news items! Use informant to read them.
erreur : la commande n’a pas pu être exécutée correctement
erreur : la validation de la transaction a échoué (Impossible d’exécuter les crochets de transaction)
Des erreurs se sont produites, aucun paquet n’a été mis à jour.
Si je vais voir dans le log de pacman, je peux lire :
Jusqu'à présent, je n'ai jamais trouvé la ligne : running '60-mkinitcpio-remove.hook'...[2019-11-11T15:25:57-0300] [PACMAN] Running 'pacman -Syu'
[2019-11-11T15:25:57-0300] [PACMAN] synchronizing package lists
[2019-11-11T15:25:58-0300] [PACMAN] starting full system upgrade
[2019-11-11T15:29:39-0300] [ALPM] running '60-mkinitcpio-remove.hook'...
[2019-11-11T15:29:39-0300] [ALPM] running '70-dkms-remove.hook'...
[2019-11-11T15:29:39-0300] [ALPM-SCRIPTLET] ==> dkms remove vboxhost/6.0.14_OSE -k 4.19.81-1-lts
[2019-11-11T15:29:47-0300] [ALPM-SCRIPTLET] ==> dkms remove vboxhost/6.0.14_OSE -k 5.3.8-arch1-1
[2019-11-11T15:29:55-0300] [ALPM] running 'informant.hook'...
[2019-11-11T15:29:58-0300] [ALPM-SCRIPTLET] There are 10 unread news items! Use informant to read them.
[2019-11-11 15:29] Exited with code 1
Si je regarde la première annonce dans informant,
je peux lire :# informant read 0
New kernel packages and mkinitcpio hooks
All our official kernels: linux, linux-lts, linux-zen and linux-hardened, do not install the actual kernel to /boot anymore.
The installation is done by mkinitcpio hooks and scripts, as well as removals. There is no need for any manual intervention.
The intention is to make the kernel packages more self-contained, as well as making the boot process more flexible, while also keeping it backwards compatible.
As of now, only mkinitcpio has hooks for handling kernels installations and removals. We do not ship any for dracut yet, but it will have similar hooks in the near future.
Donc je suppose qu'il n'y a rien à faire de spécial.The installation is done by mkinitcpio hooks and scripts, as well as removals. There is no need for any manual intervention.
Pour info, la version de mkinitcpio est la suivante :
mkinitcpio-27-2 est à jour
Mon mkinitcpio.conf est le suivant :
Un avis, une solution ?# vim:set ft=sh
# MODULES
# The following modules are loaded before any boot hooks are
# run. Advanced users may wish to specify all system modules
# in this array. For instance:
# MODULES=(piix ide_disk reiserfs)
MODULES=()
# BINARIES
# This setting includes any additional binaries a given user may
# wish into the CPIO image. This is run last, so it may be used to
# override the actual binaries included by a given hook
# BINARIES are dependency parsed, so you may safely ignore libraries
BINARIES=()
# FILES
# This setting is similar to BINARIES above, however, files are added
# as-is and are not parsed in any way. This is useful for config files.
FILES=()
# HOOKS
# This is the most important setting in this file. The HOOKS control the
# modules and scripts added to the image, and what happens at boot time.
# Order is important, and it is recommended that you do not change the
# order in which HOOKS are added. Run 'mkinitcpio -H <hook name>' for
# help on a given hook.
# 'base' is _required_ unless you know precisely what you are doing.
# 'udev' is _required_ in order to automatically load modules
# 'filesystems' is _required_ unless you specify your fs modules in MODULES
# Examples:
## This setup specifies all modules in the MODULES setting above.
## No raid, lvm2, or encrypted root is needed.
# HOOKS=(base)
#
## This setup will autodetect all modules for your system and should
## work as a sane default
# HOOKS=(base udev autodetect block filesystems)
#
## This setup will generate a 'full' image which supports most systems.
## No autodetection is done.
# HOOKS=(base udev block filesystems)
#
## This setup assembles a pata mdadm array with an encrypted root FS.
## Note: See 'mkinitcpio -H mdadm' for more information on raid devices.
# HOOKS=(base udev block mdadm encrypt filesystems)
#
## This setup loads an lvm2 volume group on a usb device.
# HOOKS=(base udev block lvm2 filesystems)
#
## NOTE: If you have /usr on a separate partition, you MUST include the
# usr, fsck and shutdown hooks.
HOOKS=(base udev autodetect modconf block filesystems keyboard fsck)
# COMPRESSION
# Use this to compress the initramfs image. By default, gzip compression
# is used. Use 'cat' to create an uncompressed image.
#COMPRESSION="gzip"
#COMPRESSION="bzip2"
#COMPRESSION="lzma"
#COMPRESSION="xz"
#COMPRESSION="lzop"
#COMPRESSION="lz4"
# COMPRESSION_OPTIONS
# Additional options for the compressor
#COMPRESSION_OPTIONS=()