After the latest updates FEATURES="multilib-strict" breaks installation =sys-fs/lvm2-2.02.99. Reproducible: Always Steps to Reproduce: 1. emerge --sync 2. emerge --info | grep multilib-strict &> /dev/null && echo "Happy" # <-- seen the word "Happy" 3. emerge =sys-fs/lvm2-2.02.99 Actual Results: Files matching a file type that is not allowed: usr/lib/systemd/system-generators/lvm2-activation-generator * ERROR: sys-fs/lvm2-2.02.99::gentoo failed: * multilib-strict check failed! * * Call stack: * misc-functions.sh, line 1275: Called install_qa_check * misc-functions.sh, line 843: Called die * The specific snippet of code: * [[ ${abort} == yes ]] && die "multilib-strict check failed!" * * If you need support, post the output of `emerge --info '=sys-fs/lvm2-2.02.99::gentoo'`, * the complete build log and the output of `emerge -pqv '=sys-fs/lvm2-2.02.99::gentoo'`. * The complete build log is located at '/var/log/portage/sys-fs:lvm2-2.02.99:20130802-083138.log'. * For convenience, a symlink to the build log is located at '/var/tmp/portage/sys-fs/lvm2-2.02.99/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/sys-fs/lvm2-2.02.99/temp/environment'. * Working directory: '/var/tmp/portage/sys-fs/lvm2-2.02.99/image' * S: '/var/tmp/portage/sys-fs/lvm2-2.02.99/work/LVM2.2.02.99' Expected Results: Expected normal build and installation. At this point, the temporary solution is FEATURES="-multilib-strict" emerge =sys-fs/lvm2-2.02.99
Created attachment 354920 [details] sys-fs:lvm2-2.02.99:20130802-083138.log
AFAICT it's systemd.eclass doing this.
Without systemd.eclass, pkg-config would give you the same result. Anyway, systemd's dir is in MULTILIB_STRICT_EXEMPT now so you shouldn't see it anymore. *** This bug has been marked as a duplicate of bug 424423 ***
/lib/systemd or /usr/lib/systemd or /usr/lib/<package name> is valid directory to install, which is why QA_MULTILIB_PATHS was quickly invented and is still the only way to supress the bogus multilib-strict check QA_MULTILIB_PATHS="usr/lib/systemd/system-generators/.*" #479520 I've applied it to the portage
(In reply to Michał Górny from comment #3) > Without systemd.eclass, pkg-config would give you the same result. Anyway, > systemd's dir is in MULTILIB_STRICT_EXEMPT now so you shouldn't see it > anymore. > > *** This bug has been marked as a duplicate of bug 424423 *** I didn't see your reply in time... I was too slow. Sorry Should I punt the QA_MULTILIB_PATHS from lvm2's ebuild? It should be harmless
(In reply to Samuli Suominen from comment #5) > (In reply to Michał Górny from comment #3) > > Without systemd.eclass, pkg-config would give you the same result. Anyway, > > systemd's dir is in MULTILIB_STRICT_EXEMPT now so you shouldn't see it > > anymore. > > > > *** This bug has been marked as a duplicate of bug 424423 *** > > I didn't see your reply in time... I was too slow. Sorry > > Should I punt the QA_MULTILIB_PATHS from lvm2's ebuild? It should be harmless I'd prefer if you punted it. Otherwise, people may start copying it over and that never ends well...
(In reply to Michał Górny from comment #6) > (In reply to Samuli Suominen from comment #5) > > (In reply to Michał Górny from comment #3) > > > Without systemd.eclass, pkg-config would give you the same result. Anyway, > > > systemd's dir is in MULTILIB_STRICT_EXEMPT now so you shouldn't see it > > > anymore. > > > > > > *** This bug has been marked as a duplicate of bug 424423 *** > > > > I didn't see your reply in time... I was too slow. Sorry > > > > Should I punt the QA_MULTILIB_PATHS from lvm2's ebuild? It should be harmless > > I'd prefer if you punted it. Otherwise, people may start copying it over and > that never ends well... ok done
