A transient make error was observed when compiling lvm2 with lvm flag set: ``` cannot create regular file '/build/birman/tmp/portage/sys-fs/lvm2-2.03.20/image/lib/udev/rules.d/10-dm.rules' cannot create regular file '/build/birman/tmp/portage/sys-fs/lvm2-2.03.20/image/sbin/dmsetup' .... : File exists ``` It looks like we try to install `dmsetup` twice. The Makefile do have .PHONY rules, but it does not prevent a second invocation of install. ``` make -C dm-tools install make[2]: Entering directory '/build/brya/tmp/portage/sys-fs/lvm2-2.03.20/work/LVM2.2.03.20/libdm/dm-tools /usr/lib/portage/python3.8/ebuild-helpers/xattr/install -c -m 555 -D dmsetup /build/birman/tmp/portage/sys-fs/lvm2-2.03.20/image/sbin/dmsetup ``` `dmsetup` is installed twice by `install` and `install_device-mapper` targets. However, since`install` implies `install_device-mapper`, we don't have to install `install_device-mapper` unconditionally.
Created attachment 864898 [details, diff] Patch to not make install_device-mapper when make install is invoked Running a diff of portage/logs/sys-fs\:lvm2-2.03.20, confirm that no files are added when `install_device-mapper` is invoked.
Created attachment 864899 [details] emerge log with install_device-mapper Compile with MAKEOPTS="-j1" to improve readability. Diffing with the next file show the section that compile `install_device-mapper` is a noop, all files were already install by `install` rule.
Created attachment 864900 [details] emerge log without install_device-mapper Compare with previous emerge.
I think this might have been handled in bug 913231?
