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

[tastytea]

On 2023-02-18 14:11-0500 Steven Lembark  wrote:

> On Sat, 18 Feb 2023 17:10:44 +0100
> tastytea  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] 

[2] 


> 
> 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
> 
> 
> 
> 
> 

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

[tastytea]

On 2023-02-18 13:58-0500 Steven Lembark  wrote:

> On Sat, 18 Feb 2023 17:10:44 +0100
> tastytea  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?

> 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"
> 

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

[Steven Lembark]

On Sat, 18 Feb 2023 17:10:44 +0100
tastytea  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





-- 
Steven Lembark
Workhorse Computing
lemb...@wrkhors.com
+1 888 359 3508

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

[Steven Lembark]

On Sat, 18 Feb 2023 17:10:44 +0100
tastytea  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
lemb...@wrkhors.com
+1 888 359 3508

Re: [gentoo-user] Re: emerge times blown out

[Stefan Schmiedl]

Samstag, 18. Februar 2023 19:05:

 
>
>On 2023-02-18, Stefan Schmiedl  wrote:
>>
>>Samstag, 18. Februar 2023 01:49:
>>>
>>>I have three systems (all ~arch) and the emerge times have blown out on all 
>>>of them across all packages. 
>>
>>When I had something like this about two years ago, the culprit was me
>>setting the cpufreq thingie in the kernel config to powersave or whatever
>>it's called ... running emerge with 800 MHz instead of 3.2 GHz produced
>>effects similar to yours.

>
>The same thing happened to me recently. Somehow, I broke the load/temp
>based CPU clock scaling on one of my machines, and it suddenly took 4X
>as long to build things as my other machines. It was running at the
>lowest clock speed possible all the time. Unfortunately, I don't
>remember exactly what I did to fix it...


CONFIG_CPU_FREQ_GOV_PERFORMANCE
CONFIG_CPU_FREQ_GOV_POWERSAVE
CONFIG_CPU_FREQ_GOV_USERSPACE
CONFIG_CPU_FREQ_GOV_ONDEMAND
CONFIG_CPU_FREQ_GOV_CONSERVATIVE
CONFIG_CPU_FREQ_GOV_SCHEDUTIL

Back when I finally found it, all of these were set to "n" but for POWERSAVE 
which was set to "y".
I rebuilt the kernel to use ONDEMAND and things were back to normal.

s.

[gentoo-user] Re: emerge times blown out

[Grant Edwards]

On 2023-02-18, Stefan Schmiedl  wrote:
> Samstag, 18. Februar 2023 01:49:
>  
>> I have three systems (all ~arch) and the emerge times have blown out on all 
>> of them across all packages. Worst example appears to be;
>
>>     Fri Dec 23 13:11:44 2022 >>> net-libs/webkit-gtk-2.38.3-r410
>>        merge time: 37 minutes and 8 seconds.
>
>>      Fri Dec 23 13:43:08 2022 >>> net-libs/webkit-gtk-2.38.3
>>        merge time: 31 minutes and 24 seconds.
>
>>      Sat Feb  4 21:16:40 2023 >>> net-libs/webkit-gtk-2.38.4-r410
>>        merge time: 6 hours, 53 minutes and 28 seconds.
>
>>      Sun Feb  5 04:17:12 2023 >>> net-libs/webkit-gtk-2.38.4
>>        merge time: 7 hours and 32 seconds.
>
>> Is anyone else seeing this?
>
> When I had something like this about two years ago, the culprit was me
> setting the cpufreq thingie in the kernel config to powersave or whatever
> it's called ... running emerge with 800 MHz instead of 3.2 GHz produced
> effects similar to yours.

The same thing happened to me recently. Somehow, I broke the load/temp
based CPU clock scaling on one of my machines, and it suddenly took 4X
as long to build things as my other machines. It was running at the
lowest clock speed possible all the time. Unfortunately, I don't
remember exactly what I did to fix it...

--
Grant

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

[tastytea]

On 2023-02-18 10:45-0500 Steven Lembark  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;
> 
> 
> # which virt-manager;
> which: no virt-manager in
> (/opt/bin:/opt/sbin:/bin:/usr/bin:/sbin:/usr/sbin)
> 

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

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

[Steven Lembark]

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;


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


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



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
lemb...@wrkhors.com
+1 888 359 3508
 * Package:app-emulation/virt-manager-4.0.0:0
 * Repository: gentoo
 * Maintainer: virtualizat...@gentoo.org
 * USE:abi_x86_64 amd64 elibc_glibc kernel_linux python_single_target_python3_10 userland_GNU
 * FEATURES:   network-sandbox preserve-libs sandbox userpriv usersandbox
 * Using python3.10 to build
>>> Unpacking source...
>>> Unpacking virt-manager-4.0.0.tar.gz to /tmp/portage/app-emulation/virt-manager-4.0.0/work
>>> Source unpacked in /tmp/portage/app-emulation/virt-manager-4.0.0/work
>>> Preparing source in /tmp/portage/app-emulation/virt-manager-4.0.0/work/virt-manager-4.0.0 ...
 * Applying virt-manager-4.0.0-setuptools-61-fix.patch ...
 [ ok ]
 * Non-PEP517 builds are deprecated for ebuilds using plain distutils.
 * Please migrate to DISTUTILS_USE_PEP517=setuptools.
 * Please see Python Guide for more details:
 *   https://projects.gentoo.org/python/guide/distutils.html
>>> Source prepared.
>>> Configuring source in /tmp/portage/app-emulation/virt-manager-4.0.0/work/virt-manager-4.0.0 ...
python3.10 setup.py configure --default-graphics=spice
running configure
Generated /tmp/portage/app-emulation/virt-manager-4.0.0/work/virt-manager-4.0.0/virtinst/build.cfg
>>> Source configured.
>>> Compiling source in /tmp/portage/app-emulation/virt-manager-4.0.0/work/virt-manager-4.0.0 ...
python3.10 setup.py build -j 64
running build
Generating /tmp/portage/app-emulation/virt-manager-4.0.0/work/virt-manager-4.0.0/build/virt-install
Generating /tmp/portage/app-emulation/virt-manager-4.0.0/work/virt-manager-4.0.0/build/virt-clone
Generating /tmp/portage/app-emulation/virt-manager-4.0.0/work/virt-manager-4.0.0/build/virt-xml
Generating /tmp/portage/app-emulation/virt-manager-4.0.0/work/virt-manager-4.0.0/build/virt-manager
Generating man/virt-xml.1
Generating man/virt-manager.1
Generating man/virt-install.1
Generating man/virt-clone.1
Generating build/bash-completion/virt-install
Generating build/bash-completion/virt-clone
Generating build/bash-completion/virt-xml
running build_i18n
msgfmt po/zh_TW.po -o build/mo/zh_TW/LC_MESSAGES/virt-manager.mo
msgfmt po/zh_CN.po -o build/mo/zh_CN/LC_MESSAGES/virt-manager.mo
msgfmt po/uk.po -o build/mo/uk/LC_MESSAGES/virt-manager.mo
msgfmt po/tr.po -o build/mo/tr/LC_MESSAGES/virt-manager.mo
msgfmt po/te.po -o build/mo/te/LC_MESSAGES/virt-manager.mo
msgfmt po/ta.po -o build/mo/ta/LC_MESSAGES/virt-manager.mo
msgfmt po/sv.po -o build/mo/sv/LC_MESSAGES/virt-manager.mo
msgfmt po/s...@latin.po -o build/mo/sr@latin/LC_MESSAGES/virt-manager.mo
msgfmt po/sr.po -o build/mo/sr/LC_MESSAGES/virt-manager.mo
msgfmt po/sk.po -o build/mo/sk/LC_MESSAGES/virt-manager.mo
msgfmt po/si.po -o build/mo/si/LC_MESSAGES/virt-manager.mo
msgfmt po/ru.po -o build/mo/ru/LC_MESSAGES/virt-manager.mo
msgfmt po/ro.po -o build/mo/ro/LC_MESSAGES/virt-manager.mo
msgfmt po/pt_BR.po -o build/mo/pt_BR/LC_MESSAGES/virt-manager.mo
msgfmt po/pt.po -o build/mo/pt/LC_MESSAGES/virt-manager.mo
msgfmt po/pl.po -o build/mo/pl/LC_MESSAGES/virt-manager.mo
msgfmt po/pa.po -o build/mo/pa/LC_MESSAGES/virt-manager.mo
msgfmt po/or.po -o build/mo/or/LC_MESSAGES/virt-manager.mo
msgfmt po/nl.po -o build/mo/nl/LC_MESSAGES/virt-manager.mo
msgfmt po/nb.po -o build/mo/nb/LC_MESSAGES/virt-manager.mo
msgfmt po/ms.po -o build/mo/ms/LC_MESSAGES/virt-manager.mo
msgfmt po/mr.po -o build/mo/mr/LC_MESSAGES/virt-manager.mo
msgfmt po/ml.po -o build/mo/ml/LC_MESSAGES

Re: [gentoo-user] emerge times blown out

[Stefan Schmiedl]

Samstag, 18. Februar 2023 01:49:
 
> I have three systems (all ~arch) and the emerge times have blown out on all 
> of them across all packages. Worst example appears to be;

>     Fri Dec 23 13:11:44 2022 >>> net-libs/webkit-gtk-2.38.3-r410
>        merge time: 37 minutes and 8 seconds.

>      Fri Dec 23 13:43:08 2022 >>> net-libs/webkit-gtk-2.38.3
>        merge time: 31 minutes and 24 seconds.

>      Sat Feb  4 21:16:40 2023 >>> net-libs/webkit-gtk-2.38.4-r410
>        merge time: 6 hours, 53 minutes and 28 seconds.

>      Sun Feb  5 04:17:12 2023 >>> net-libs/webkit-gtk-2.38.4
>        merge time: 7 hours and 32 seconds.

> Is anyone else seeing this?

When I had something like this about two years ago, the culprit was me
setting the cpufreq thingie in the kernel config to powersave or whatever
it's called ... running emerge with 800 MHz instead of 3.2 GHz produced
effects similar to yours.

s. 
 

Re: [gentoo-user] emerge times blown out

[Alan J. Wylie]

Adam Carter  writes:

> My reason for asking is that i'm seeing this across multiple systems, 2
> AMD, 1 Intel, who's configuration hasn't really changed and while there is
> some variance there has been a step change late December / early January.
> Another example
>
> Sat Nov 26 14:34:50 2022 >>> sys-apps/systemd-252.2
>merge time: 2 minutes and 19 seconds.
>
>  Sat Dec 10 20:59:29 2022 >>> sys-apps/systemd-252.3
>merge time: 1 minute and 54 seconds.
>
>  Wed Dec 14 13:56:52 2022 >>> sys-apps/systemd-252.3
>merge time: 2 minutes and 56 seconds.
>
>  Wed Dec 21 20:08:36 2022 >>> sys-apps/systemd-252.4
>merge time: 3 minutes and 7 seconds.
>
>  Tue Jan  3 22:29:43 2023 >>> sys-apps/systemd-252.4
>merge time: 12 minutes and 42 seconds.
>
>  Thu Jan 12 14:56:32 2023 >>> sys-apps/systemd-252.4-r1
>merge time: 22 minutes and 12 seconds.
>
>  Sat Jan 21 12:00:06 2023 >>> sys-apps/systemd-252.4-r1
>merge time: 12 minutes and 3 seconds.
>
>  Mon Jan 30 15:41:44 2023 >>> sys-apps/systemd-252.5
>merge time: 21 minutes and 45 seconds.
>
>  Fri Feb 17 21:18:21 2023 >>> sys-apps/systemd-252.6
>merge time: 22 minutes and 18 seconds.

All my three systems are fine

AMD FX(tm)-8350 Eight-Core Processor, 16GiB

 Sun Oct  2 13:07:33 2022 >>> sys-apps/systemd-251.4
merge time: 3 minutes and 35 seconds.

 Fri Nov 25 08:06:10 2022 >>> sys-apps/systemd-251.7
merge time: 3 minutes and 24 seconds.

 Sat Dec 10 10:11:16 2022 >>> sys-apps/systemd-251.8
merge time: 3 minutes and 19 seconds.

 Tue Jan  3 08:43:49 2023 >>> sys-apps/systemd-252.4
merge time: 3 minutes and 22 seconds.

 Sat Jan 28 06:28:16 2023 >>> sys-apps/systemd-252.4-r1
merge time: 5 minutes and 24 seconds.

AMD FX(tm)-4300 Quad-Core Processor, 16GiB

 Sun Oct  2 13:42:48 2022 >>> sys-apps/systemd-251.4
merge time: 5 minutes and 32 seconds.

 Fri Nov 25 08:11:27 2022 >>> sys-apps/systemd-251.7
merge time: 5 minutes and 40 seconds.

 Sat Dec 10 12:31:38 2022 >>> sys-apps/systemd-251.8
merge time: 5 minutes and 36 seconds.

 Tue Jan  3 08:47:13 2023 >>> sys-apps/systemd-252.4
merge time: 5 minutes and 36 seconds.

 Sat Jan 28 06:28:27 2023 >>> sys-apps/systemd-252.4-r1
merge time: 6 minutes and 17 seconds.

Intel(R) Atom(TM) CPU N2800   @ 1.86GHz, 4GiB, not systemd

 Wed Sep 28 08:32:50 2022 >>> net-dns/bind-9.16.33
merge time: 15 minutes and 28 seconds.

 Fri Jan 20 07:50:41 2023 >>> net-dns/bind-9.16.36
merge time: 16 minutes and 23 seconds.

 Thu Feb 16 07:33:46 2023 >>> net-dns/bind-9.16.37
merge time: 17 minutes and 9 seconds.

-- 
Alan J. Wylie  https://www.wylie.me.uk/

Dance like no-one's watching. / Encrypt like everyone is.
Security is inversely proportional to convenience