From: Steven Lembark <lembark@wrkhors.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Completed installing ... into /tmp/portage/app-emulation/virt-manager-4.0.0
Date: Sat, 18 Feb 2023 13:58:11 -0500 [thread overview]
Message-ID: <20230218135811.308a5838.lembark@wrkhors.com> (raw)
In-Reply-To: <20230218171044.138f5e35@ventiloplattform.tastytea.de>
On Sat, 18 Feb 2023 17:10:44 +0100
tastytea <gentoo@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"
--
Steven Lembark
Workhorse Computing
lembark@wrkhors.com
+1 888 359 3508
next prev parent reply other threads:[~2023-02-18 18:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-18 15:45 [gentoo-user] Completed installing ... into /tmp/portage/app-emulation/virt-manager-4.0.0 Steven Lembark
2023-02-18 16:10 ` tastytea
2023-02-18 18:58 ` Steven Lembark [this message]
2023-02-18 19:16 ` tastytea
2023-02-18 19:11 ` Steven Lembark
2023-02-18 19:19 ` tastytea
2023-02-19 20:35 ` [solved] " Steven Lembark
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230218135811.308a5838.lembark@wrkhors.com \
--to=lembark@wrkhors.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox