after a successful compile it fails in the install stage /usr/bin/install: cannot change permissions of '/tmp/portage/portage/sys-fs/lvm2-2.03.18-r1/image/sb in/dmsetup': No such file or directory make[2]: *** [Makefile:71: install_dmsetup_dynamic] Error 1 make[2]: Leaving directory '/tmp/portage/portage/sys-fs/lvm2-2.03.18-r1/work/LVM2.2.03.18/libdm/dm-t ools' ln -s -f dmsetup /tmp/portage/portage/sys-fs/lvm2-2.03.18-r1/image/sbin/dmstats /usr/lib/portage/python3.10/ebuild-helpers/xattr/install -c -m 755 -d /tmp/portage/portage/sys-fs/lv m2-2.03.18-r1/image/usr/lib64 make[1]: *** [../libdm/make.tmpl:337: dm-tools.install_device-mapper] Error 2 make[1]: *** Waiting for unfinished jobs.... Reproducible: Always USE="lvm readline thin udev -lvm2create-initrd -sanlock (-selinux) -static -static-libs -systemd" it left my system in a funk and I had to boot in with a rescue iso and roll back to sys-fs/lvm2-2.03.17-r2 . this bug also happens in sys-fs/lvm2-2.03.18
proper log output /usr/bin/install: cannot change permissions of '/tmp/portage/portage/sys-fs/lvm2-2.03.18-r1/image/sbin/dmsetup': No such file or directory make[2]: *** [Makefile:71: install_dmsetup_dynamic] Error 1 make[2]: Leaving directory '/tmp/portage/portage/sys-fs/lvm2-2.03.18-r1/work/LVM2.2.03.18/libdm/dm-tools' ln -s -f dmsetup /tmp/portage/portage/sys-fs/lvm2-2.03.18-r1/image/sbin/dmstats /usr/lib/portage/python3.10/ebuild-helpers/xattr/install -c -m 755 -d /tmp/portage/portage/sys-fs/lvm2-2.03.18-r1/image/usr/lib64 make[1]: *** [../libdm/make.tmpl:337: dm-tools.install_device-mapper] Error 2 make[1]: *** Waiting for unfinished jobs.... make[4]: Nothing to be done for 'install_device-mapper'. make[4]: Leaving directory '/tmp/portage/portage/sys-fs/lvm2-2.03.18-r1/work/LVM2.2.03.18/daemons/dmeventd/plugins/lvm2' make[4]: Nothing to be done for 'install_device-mapper'. make[4]: Leaving directory '/tmp/portage/portage/sys-fs/lvm2-2.03.18-r1/work/LVM2.2.03.18/daemons/dmeventd/plugins/raid' make[2]: Leaving directory '/tmp/portage/portage/sys-fs/lvm2-2.03.18-r1/work/LVM2.2.03.18/libdm/dm-tools' make[4]: Nothing to be done for 'install_device-mapper'. make[4]: Leaving directory '/tmp/portage/portage/sys-fs/lvm2-2.03.18-r1/work/LVM2.2.03.18/daemons/dmeventd/plugins/mirror' make[4]: Nothing to be done for 'install_device-mapper'. make[4]: Leaving directory '/tmp/portage/portage/sys-fs/lvm2-2.03.18-r1/work/LVM2.2.03.18/daemons/dmeventd/plugins/snapshot' make[4]: Nothing to be done for 'install_device-mapper'. make[4]: Leaving directory '/tmp/portage/portage/sys-fs/lvm2-2.03.18-r1/work/LVM2.2.03.18/daemons/dmeventd/plugins/thin' make[4]: Nothing to be done for 'install_device-mapper'. make[4]: Leaving directory '/tmp/portage/portage/sys-fs/lvm2-2.03.18-r1/work/LVM2.2.03.18/daemons/dmeventd/plugins/vdo' make[3]: Leaving directory '/tmp/portage/portage/sys-fs/lvm2-2.03.18-r1/work/LVM2.2.03.18/daemons/dmeventd/plugins' ln -s -f ../../lib64/libdevmapper.so.1.02 /tmp/portage/portage/sys-fs/lvm2-2.03.18-r1/image/usr/lib64/libdevmapper.so make[1]: Nothing to be done for 'all'. make[1]: Leaving directory '/tmp/portage/portage/sys-fs/lvm2-2.03.18-r1/work/LVM2.2.03.18/lib' make -C tools make -C scripts ln -s -f ../../lib64/libdevmapper-event.so.1.02 /tmp/portage/portage/sys-fs/lvm2-2.03.18-r1/image/usr/lib64/libdevmapper-event.so make[1]: Leaving directory '/tmp/portage/portage/sys-fs/lvm2-2.03.18-r1/work/LVM2.2.03.18/libdm' make: *** [make.tmpl:396: libdm.install_device-mapper] Error 2 make: *** Waiting for unfinished jobs....
Please include the full build.log and emerge --info.
Also, which is it? It doesn't install, or you can't boot with it? Are you mixing this with bug 892487?
Created attachment 849429 [details] error installing 2.03.18-r1
I attached the log of it failing to install lvm2-2.03.18-r1 . I just now decided to recompile it again to get a fresh log and it compiled and installed just fine . When it failed before it did screw up my boot and rolling back to lvm2-2.03.17-r2-1.xpak fixed it. So I'm at a loss as to what actually happened. Mark this one up to gremlins.
Created attachment 849431 [details] successful install 2.03.18-r1
No worries, thank you for trying again! Maybe it tried to interact with the installed broken lvm. No idea.