Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

[gentoo-user] Completed installing ... into /tmp/portage/app-emulation/virt-manager-4.0.0

2 views
Skip to first unread message

Steven Lembark

unread,
Feb 18, 2023, 10:50:04 AM2/18/23
to

First time I've ever seen a package install into PORTAGE_TMPDIR...

Q: What am I missing?

The rest of last nights "emerge --update" went into places like
/usr/bin... where you'd expect. After the upgrade I noticed that
virt-manager wasn't there. Tried emerging it alone to see what
had happened.

# emerge ... app-emulation/virt-manager;
<time passes>

# which virt-manager;
which: no virt-manager in
(/opt/bin:/opt/sbin:/bin:/usr/bin:/sbin:/usr/sbin)
<seems odd>

$ less /var/log/portage/app-emulation\:virt-manager-4.0.0\:20230218-151519.log

<snip>

changing mode of /tmp/portage/app-emulation/virt-manager-4.0.0/image/usr/bin/virt-xml to 755
changing mode of /tmp/portage/app-emulation/virt-manager-4.0.0/image/usr/bin/virt-install to 755
changing mode of /tmp/portage/app-emulation/virt-manager-4.0.0/image/usr/bin/virt-clone to 755
changing mode of /tmp/portage/app-emulation/virt-manager-4.0.0/image/usr/bin/virt-manager to 755
>>> Completed installing app-emulation/virt-manager-4.0.0 into /tmp/portage/app-emulation/virt-manager-4.0.0/image

* Final size of build directory: 22080 KiB (21.5 MiB)
* Final size of installed tree: 7420 KiB ( 7.2 MiB)


Full emerge:

/usr/bin/emerge --deep --backtrack=128 --with-bdeps y --complete-graph y --autounmask-write --verbose-conflicts --jobs --load-average 60 --verbose-conflicts

See also:

https://pastebin.com/76x7AdB9 Full emerge log
https://pastebin.com/EmyLJsyM emerge --info

--
Steven Lembark
Workhorse Computing
lem...@wrkhors.com
+1 888 359 3508
app-emulation:virt-manager-4.0.0:20230218-151519.log

tastytea

unread,
Feb 18, 2023, 11:20:04 AM2/18/23
to
On 2023-02-18 10:45-0500 Steven Lembark <lem...@wrkhors.com> wrote:

> First time I've ever seen a package install into PORTAGE_TMPDIR...
>
> Q: What am I missing?
>
> The rest of last nights "emerge --update" went into places like
> /usr/bin... where you'd expect. After the upgrade I noticed that
> virt-manager wasn't there. Tried emerging it alone to see what
> had happened.
>
> # emerge ... app-emulation/virt-manager;
> <time passes>
>
> # which virt-manager;
> which: no virt-manager in
> (/opt/bin:/opt/sbin:/bin:/usr/bin:/sbin:/usr/sbin)
> <seems odd>

Do you have the gtk USE-flag on app-emulation/virt-manager? Does
`qlist app-emulation/virt-manager` show installed files?

[…]
> >>> Completed installing app-emulation/virt-manager-4.0.0 into
> >>> /tmp/portage/app-emulation/virt-manager-4.0.0/image
>
> * Final size of build directory: 22080 KiB (21.5 MiB)
> * Final size of installed tree: 7420 KiB ( 7.2 MiB)

That is normal. it is installed into ${PORTAGE_TMPDIR} and then merged
into ${EROOT}/ to make it less likely that the filesystem is getting
messed up.

Kind regards, tastytea

Steven Lembark

unread,
Feb 18, 2023, 2:00:03 PM2/18/23
to
On Sat, 18 Feb 2023 17:10:44 +0100
tastytea <gen...@tastytea.de> wrote:

> Do you have the gtk USE-flag on app-emulation/virt-manager? Does
> `qlist app-emulation/virt-manager` show installed files?

No, but the previous version was working without it.

> […]
> > >>> Completed installing app-emulation/virt-manager-4.0.0 into
> > >>> /tmp/portage/app-emulation/virt-manager-4.0.0/image
> >
> > * Final size of build directory: 22080 KiB (21.5 MiB)
> > * Final size of installed tree: 7420 KiB ( 7.2 MiB)
>
> That is normal. it is installed into ${PORTAGE_TMPDIR} and then merged
> into ${EROOT}/ to make it less likely that the filesystem is getting
> messed up.

The other packages on the system get installed in the root after
being collected in the temp dir. I cannot find this package
getting installed anywhere further:

>>> Completed installing app-emulation/virt-manager-4.0.0
into /tmp/portage/app-emulation/virt-manager-4.0.0/image

qlist shows some files in /usr/share, look left over from the
previous install. The only remaining executables are:

/usr/bin/virt-xml
/usr/bin/virt-install
/usr/bin/virt-clone

notice the lack of virt-manager.

Full qlist output:

https://pastebin.com/LNqczQnc


Build info:

app-emulation/virt-manager-4.0.0::gentoo was built with the following:

USE="-gtk -policykit -sasl -test"
PYTHON_SINGLE_TARGET="python3_10 -python3_9"
FEATURES="distlocks assume-digests userfetch binpkg-docompress qa-unresolved-soname-deps usersandbox network-sandbox ipc-sandbox preserve-libs merge-sync config-protect-if-modified multilib-strict binpkg-logs sfperms binpkg-dostrip protect-owned usersync parallel-install fixlafiles xattr pid-sandbox buildpkg-live userpriv unmerge-logs unmerge-orphans parallel-fetch binpkg-multi-instance sandbox unknown-features-warn strict clean-logs news ebuild-locks"

tastytea

unread,
Feb 18, 2023, 2:20:04 PM2/18/23
to
On 2023-02-18 14:11-0500 Steven Lembark <lem...@wrkhors.com> wrote:

> On Sat, 18 Feb 2023 17:10:44 +0100
> tastytea <gen...@tastytea.de> wrote:
>
> > Do you have the gtk USE-flag on app-emulation/virt-manager?
>
> Double-checking the module, I don't see it using gtk:

stable (on amd64) uses “gtk”[1], testing uses “gui”[2].

[1] <https://gitweb.gentoo.org/repo/gentoo.git/tree/app-emulation/virt-manager/virt-manager-4.0.0.ebuild>
[2] <https://gitweb.gentoo.org/repo/gentoo.git/tree/app-emulation/virt-manager/virt-manager-4.1.0.ebuild>

>
> https://packages.gentoo.org/packages/app-emulation/virt-manager
>
> USE flags
> Local Use Flags
>
> policykit
> sasl
>
> Global Use Flags
>
> gui
> test
>
> python_single_target (Use Expand)
>
> python3_9
> python3_10
> python3_11
>
>
>
>
>

Steven Lembark

unread,
Feb 18, 2023, 2:20:04 PM2/18/23
to
On Sat, 18 Feb 2023 17:10:44 +0100
tastytea <gen...@tastytea.de> wrote:

> Do you have the gtk USE-flag on app-emulation/virt-manager?

Double-checking the module, I don't see it using gtk:

https://packages.gentoo.org/packages/app-emulation/virt-manager

USE flags
Local Use Flags

policykit
sasl

Global Use Flags

gui
test

python_single_target (Use Expand)

python3_9
python3_10
python3_11





tastytea

unread,
Feb 18, 2023, 2:20:04 PM2/18/23
to
On 2023-02-18 13:58-0500 Steven Lembark <lem...@wrkhors.com> wrote:

> On Sat, 18 Feb 2023 17:10:44 +0100
> tastytea <gen...@tastytea.de> wrote:
>
> > Do you have the gtk USE-flag on app-emulation/virt-manager? Does
> > `qlist app-emulation/virt-manager` show installed files?
>
> No, but the previous version was working without it.

I don't know if it changed recently, but the current ebuild removes
"${ED}/usr/bin/virt-manager" (in pkg_preinst()) if the gtk USE-flag is
not enabled.

> > […]
> > > >>> Completed installing app-emulation/virt-manager-4.0.0 into
> > > >>> /tmp/portage/app-emulation/virt-manager-4.0.0/image
> > >
> > > * Final size of build directory: 22080 KiB (21.5 MiB)
> > > * Final size of installed tree: 7420 KiB ( 7.2 MiB)
> >
> > That is normal. it is installed into ${PORTAGE_TMPDIR} and then
> > merged into ${EROOT}/ to make it less likely that the filesystem is
> > getting messed up.
>
> The other packages on the system get installed in the root after
> being collected in the temp dir. I cannot find this package
> getting installed anywhere further:
>
> >>> Completed installing app-emulation/virt-manager-4.0.0
> into /tmp/portage/app-emulation/virt-manager-4.0.0/image
>
> qlist shows some files in /usr/share, look left over from the
> previous install. The only remaining executables are:
>
> /usr/bin/virt-xml
> /usr/bin/virt-install
> /usr/bin/virt-clone
>
> notice the lack of virt-manager.
>
> Full qlist output:
>
> https://pastebin.com/LNqczQnc

Looks like it is installed?

Steven Lembark

unread,
Feb 19, 2023, 3:40:07 PM2/19/23
to

> stable (on amd64) uses “gtk”[1], testing uses “gui”[2].

Upgraded to 4.1 & added "gui", got it installed.

Thank you
0 new messages