From: tastytea <gentoo@tastytea.de>
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 17:10:44 +0100 [thread overview]
Message-ID: <20230218171044.138f5e35@ventiloplattform.tastytea.de> (raw)
In-Reply-To: <20230218104504.6a1d9d23.lembark@wrkhors.com>
On 2023-02-18 10:45-0500 Steven Lembark <lembark@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
next prev parent reply other threads:[~2023-02-18 16:10 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 [this message]
2023-02-18 18:58 ` Steven Lembark
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=20230218171044.138f5e35@ventiloplattform.tastytea.de \
--to=gentoo@tastytea.de \
--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