Bug 925541 – sys-apps/util-linux: Aborting due to QA concerns: there are files installed outside the prefix (/lib/systemd/system)

• Status: UNCONFIRMED
• Product: Gentoo/Alt

[Description Julián 2024-02-26 11:09:26 UTC]

Created attachment 886023 [details]
output of `emerge --info '=sys-apps/util-linux-2.39.3-r2::gentoo'`

Trying to do a Gentoo Prefix Bootstrapping I got the following error (my machine is a HiFive Unmatched RISC-V running Ubuntu):


>>> Completed installing sys-apps/util-linux-2.39.3-r2 into /home/jmorillo/gentoo/var/tmp/portage/sys-apps/util-linux-2.39.3-r2/image

 ^[[32m*^[[0m Final size of build directory: 112744 KiB (110.1 MiB)
 ^[[32m*^[[0m Final size of installed tree:   22588 KiB ( 22.0 MiB)

 ^[[33m*^[[0m QA Notice: the following files are outside of the prefix:
 ^[[33m*^[[0m /lib
 ^[[33m*^[[0m /lib/systemd
 ^[[33m*^[[0m /lib/systemd/system
 ^[[31;01m*^[[0m ERROR: sys-apps/util-linux-2.39.3-r2::gentoo failed:
 ^[[31;01m*^[[0m   Aborting due to QA concerns: there are files installed outside the prefix
 ^[[31;01m*^[[0m
 ^[[31;01m*^[[0m Call stack:
 ^[[31;01m*^[[0m   misc-functions.sh, line 671:  Called install_qa_check
 ^[[31;01m*^[[0m   misc-functions.sh, line 134:  Called source 'install_symlink_html_docs'
 ^[[31;01m*^[[0m            05prefix, line 114:  Called install_qa_check_prefix
 ^[[31;01m*^[[0m            05prefix, line  27:  Called die
 ^[[31;01m*^[[0m The specific snippet of code:
 ^[[31;01m*^[[0m                        die "Aborting due to QA concerns: there are files installed outside the prefix"
 ^[[31;01m*^[[0m
 ^[[31;01m*^[[0m If you need support, post the output of `emerge --info '=sys-apps/util-linux-2.39.3-r2::gentoo'`,
 ^[[31;01m*^[[0m the complete build log and the output of `emerge -pqv '=sys-apps/util-linux-2.39.3-r2::gentoo'`.
 ^[[31;01m*^[[0m The complete build log is located at '/home/jmorillo/gentoo/var/tmp/portage/sys-apps/util-linux-2.39.3-r2/temp/build.log'.
 ^[[31;01m*^[[0m The ebuild environment file is located at '/home/jmorillo/gentoo/var/tmp/portage/sys-apps/util-linux-2.39.3-r2/temp/environment'.
 ^[[31;01m*^[[0m Working directory: '/home/jmorillo/gentoo/var/tmp/portage/sys-apps/util-linux-2.39.3-r2/image'
 ^[[31;01m*^[[0m S: '/home/jmorillo/gentoo/var/tmp/portage/sys-apps/util-linux-2.39.3-r2/work/util-linux-2.39.3'
!!! post install failed; exiting.

>>> Failed to emerge sys-apps/util-linux-2.39.3-r2, Log file:

>>>  '/home/jmorillo/gentoo/var/tmp/portage/sys-apps/util-linux-2.39.3-r2/temp/build.log'

[Comment 1 Julián 2024-02-26 11:13:15 UTC]

Created attachment 886024 [details]
output of `emerge -pqv '=sys-apps/util-linux-2.39.3-r2::gentoo'

[Comment 2 Julián 2024-02-26 11:18:42 UTC]

Created attachment 886025 [details]
gentoo/var/tmp/portage/sys-apps/util-linux-2.39.3-r2/temp/build.log

gentoo/var/tmp/portage/sys-apps/util-linux-2.39.3-r2/temp/build.log

[Comment 3 Sam James 2024-02-27 02:18:48 UTC]

> --with-systemdsystemunitdir=/lib/systemd/system 

The ebuild does:
> --with-systemdsystemunitdir="$(systemd_get_systemunitdir)"

so systemd.eclass' systemd_get_systemunitdir is giving an unprefixed result.

Is it finding a systemd pkgconfig file from the host?

[Comment 4 Julián 2024-02-27 15:43:47 UTC]

(In reply to Sam James from comment #3)
> > --with-systemdsystemunitdir=/lib/systemd/system 
> 
> The ebuild does:
> > --with-systemdsystemunitdir="$(systemd_get_systemunitdir)"
> 
> so systemd.eclass' systemd_get_systemunitdir is giving an unprefixed result.
> 
> Is it finding a systemd pkgconfig file from the host?

How could I check that?

[Comment 5 Mike Gilbert 2024-02-27 16:35:14 UTC]

(In reply to Julián from comment #4)
> How could I check that?

Rename /usr/share/pkgconfig/systemd.pc to something like systemd.pc.backup on the host and try bootstrapping again.

If it works, that would confirm Sam's theory.

Rename the file back after testing.

[Comment 6 Julián 2024-02-27 16:58:48 UTC]

(In reply to Sam James from comment #3)
> > --with-systemdsystemunitdir=/lib/systemd/system 
> 
> The ebuild does:
> > --with-systemdsystemunitdir="$(systemd_get_systemunitdir)"
> 
> so systemd.eclass' systemd_get_systemunitdir is giving an unprefixed result.
> 
> Is it finding a systemd pkgconfig file from the host?

OK, it looks like I have such a pkgconfig file on my host:

jmorillo@arriesgado-1:~/arriesgado-hirsute/MultiXscale/GentooPrefix$ pkg-config --exists systemd; echo $?                                                                       0
jmorillo@arriesgado-1:~/arriesgado-hirsute/MultiXscale/GentooPrefix$ pkg-config --variable=systemdsystemunitdir systemd; echo $?
/lib/systemd/system
0

But why is the Gentoo Prefix bootstrapping considering this file?

[Comment 7 Julián 2024-02-27 16:59:23 UTC]

(In reply to Mike Gilbert from comment #5)
> (In reply to Julián from comment #4)
> > How could I check that?
> 
> Rename /usr/share/pkgconfig/systemd.pc to something like systemd.pc.backup
> on the host and try bootstrapping again.
> 
> If it works, that would confirm Sam's theory.
> 
> Rename the file back after testing.

Good point, I'll try and let you know.