View previous topic :: View next topic |
Author |
Message |
g0rg0n Tux's lil' helper

Joined: 18 Feb 2006 Posts: 98
|
Posted: Sun Nov 03, 2024 8:33 am Post subject: sys-kernel/dracut-105: Installation of a symlink is blocked |
|
|
I did a world update today and saw following error messages with dracut:
Code: |
>>> Completed (1 of 1) sys-kernel/dracut-105::gentoo
* Messages for package sys-kernel/dracut-105:
*
* Installation of a symlink is blocked by a directory:
* '/usr/lib/dracut/modules.d/80test'
* This symlink will be merged with a different name:
* '/usr/lib/dracut/modules.d/80test.backup.0000'
*
*
* Installation of a symlink is blocked by a directory:
* '/usr/lib/dracut/modules.d/80test-root'
* This symlink will be merged with a different name:
* '/usr/lib/dracut/modules.d/80test-root.backup.0000'
*
*
* Installation of a symlink is blocked by a directory:
* '/usr/lib/dracut/modules.d/80test-makeroot'
* This symlink will be merged with a different name:
* '/usr/lib/dracut/modules.d/80test-makeroot.backup.0000'
*
* Install additional packages for optional runtime features:
* sys-fs/btrfs-progs for Scan for Btrfs on block devices
* app-shells/dash for Allows use of dash instead of default bash (on your own risk)
* sys-apps/busybox for Allows use of busybox instead of default bash (on your own risk)
* sys-block/open-iscsi for Support iSCSI
* sys-fs/lvm2[lvm] for Support Logical Volume Manager
* sys-fs/mdadm for Support MD devices, also known as software RAID devices
* sys-fs/dmraid for Support MD devices, also known as software RAID devices
* sys-fs/multipath-tools for Support Device Mapper multipathing
* >=sys-boot/plymouth-0.8.5-r5 for Plymouth boot splash
* sys-block/nbd for Support network block devices
* app-admin/rsyslog for Enable logging with rsyslog
* sys-fs/squashfs-tools for Support Squashfs
* app-crypt/tpm2-tools for Support TPM 2.0 TSS
* sys-apps/biosdevname for Support BIOS-given device names
* sys-apps/nvme-cli for Support network NVMe
* app-misc/jq for Support network NVMe
* sys-apps/rng-tools for Enable rngd service to help generating entropy early during boot
* sys-apps/systemd[boot] for building Unified Kernel Images with dracut (--uefi)
* sys-apps/systemd-utils[boot] for building Unified Kernel Images with dracut (--uefi)
* sys-kernel/installkernel[dracut,uki] for automatically generating an UKI on each kernel installation
* GNU info directory index is up-to-date.
theoffice /usr/lib/dracut/modules.d #
|
not sure why but there were empty 80test* directories under /usr/lib/dracut/modules;
Code: |
theoffice /usr/lib/dracut/modules.d # ls -alF | grep test
drwxr-xr-x 2 root root 4096 Nov 2 22:01 80test/
lrwxrwxrwx 1 root root 24 Oct 13 23:10 80test.backup.0000 -> ../test/modules.d/80test/
drwxr-xr-x 2 root root 4096 Nov 2 22:01 80test-makeroot/
lrwxrwxrwx 1 root root 33 Oct 13 23:10 80test-makeroot.backup.0000 -> ../test/modules.d/80test-makeroot/
drwxr-xr-x 2 root root 4096 Nov 2 22:01 80test-root/
lrwxrwxrwx 1 root root 29 Oct 13 23:10 80test-root.backup.0000 -> ../test/modules.d/80test-root/
theoffice /usr/lib/dracut/modules.d #
|
deleted 80test* directories and symlinks, re-emerging dracut seems to have resolved the issue.
Code: |
theoffice /usr/lib/dracut/modules.d # ls -alF | grep test
lrwxrwxrwx 1 root root 24 Oct 13 23:10 80test -> ../test/modules.d/80test/
lrwxrwxrwx 1 root root 33 Oct 13 23:10 80test-makeroot -> ../test/modules.d/80test-makeroot/
lrwxrwxrwx 1 root root 29 Oct 13 23:10 80test-root -> ../test/modules.d/80test-root/
theoffice /usr/lib/dracut/modules.d #
|
has anyone encountered a similar issue? _________________ nicewarm.coffee |
|
Back to top |
|
 |
sam_ Developer


Joined: 14 Aug 2020 Posts: 2159
|
Posted: Sun Nov 03, 2024 9:10 am Post subject: |
|
|
Note that I don't think they were errors, but warnings (even though they showed up in red). It does say it will merge them with a different name. |
|
Back to top |
|
 |
Nowa Developer


Joined: 25 Jun 2014 Posts: 478 Location: Nijmegen
|
Posted: Sun Nov 03, 2024 10:18 am Post subject: |
|
|
It's harmless, you can remove the dead symlinks if you want. You don't need these modules anyway, they are only used for running the tests.
It's caused by upstream moving a directory into the spot where a symlink to that same directory used to be. _________________ OS: Gentoo 6.10.12-gentoo-dist, ~amd64, 23.0/desktop/plasma/systemd
MB: MSI Z370-A PRO
CPU: Intel Core i9-9900KS
GPU: Intel Arc A770 16GB & Intel UHD Graphics 630
SSD: Samsung 970 EVO Plus 2 TB
RAM: Crucial Ballistix 32GB DDR4-2400 |
|
Back to top |
|
 |
g0rg0n Tux's lil' helper

Joined: 18 Feb 2006 Posts: 98
|
Posted: Tue Nov 05, 2024 11:53 am Post subject: |
|
|
Nowa wrote: | It's caused by upstream moving a directory into the spot where a symlink to that same directory used to be. |
ah thank you! _________________ nicewarm.coffee |
|
Back to top |
|
 |
|