Re: [gentoo-user] Portage update errors
On Wed, 21 Nov 2018 13:52:50 +1100, Zoltán Kócsi wrote: > I have a machine with Gentoo, which was installed from scratch 5 months > ago, was updated 3 months ago. Time to look at it again. > > emerge --sync > > told me that I was strongly advised to update portage. > > emerge portage > > comes back with lots of errors, see below (the output is slightly > edited for brevity). > > There is nothing to mask those packages, for example the word 'certifi' > does not occur in *any* file under /etc/portage at all. > > As per the "5 config files ..." bit, well, dispatch-conf and etc-update > tell me that they have nothing to do, so I have no idea what 5 files > need updating, to what and how to update them. find /etc/portage -name ._cfg\* Config files for updating start with ._cfg > I don't really understand how portage works (but I'd be glad if someone > could point me to a single-entity document of its architecture and > internals) so I couldn't even guess what its problem is. And the system > is not *that* old, really. The Gentoo Handbook and man portage are good starting points. > tade ~ # emerge portage 2> /tmp/emsg > > * IMPORTANT: 5 config files in '/etc/portage' need updating. > * See the CONFIGURATION FILES and CONFIGURATION FILES UPDATE TOOLS > * sections of the emerge man page to learn how to update config files. > > [ebuild U ] app-crypt/openpgp-keys-gentoo-release-20180706 >[20180703] USE="{-test%}" > > [ebuild R] dev-python/setuptools-36.7.2 >PYTHON_TARGETS="python3_6* -python3_5*" > > [ebuild R] dev-python/certifi-2018.4.16 > PYTHON_TARGETS="python3_6* -python3_5* (-python3_7)" > > [ebuild U *] app-portage/gemato- [13.0-r1] > PYTHON_TARGETS="python3_6* -python3_5* -python3_7%" > > [ebuild U *] sys-apps/portage- [2.3.40-r1] > PYTHON_TARGETS="python3_6* -python3_5* -python3_7%" This would appear to be your problem, you are trying to emerge version of portage. Version usually refers to a git version, so not usually desirable, especially for a critical system tool. So the first step is to find out why portage wants version . grep -r portage /etc/portage will tell you if you have set it for installation. Otherwise repeat the emerge command with the -t option, which shows what is pulling in a particular package. > > !!! Multiple package instances within a single package slot have been > pulled > !!! into the dependency graph, resulting in a slot conflict: > > sys-apps/portage:0 > > (sys-apps/portage-:0/0::gentoo, ebuild scheduled for merge) > pulled in by sys-apps/portage (Argument) This implies you have somehow unmasked portage- -- Neil Bothwick [ Printed on recycled electrons ] pgpNtiyHYUZYI.pgp Description: OpenPGP digital signature
[gentoo-user] Portage update errors
I have a machine with Gentoo, which was installed from scratch 5 months ago, was updated 3 months ago. Time to look at it again. emerge --sync told me that I was strongly advised to update portage. emerge portage comes back with lots of errors, see below (the output is slightly edited for brevity). There is nothing to mask those packages, for example the word 'certifi' does not occur in *any* file under /etc/portage at all. The system is a stock-standard Gentoo with nothing fancy except one thing: although it is installed as a 64-bit system, it is told to also install every library in 32-bit mode, because it must be able to run closed-source 32-bit programs. As per the "5 config files ..." bit, well, dispatch-conf and etc-update tell me that they have nothing to do, so I have no idea what 5 files need updating, to what and how to update them. I don't really understand how portage works (but I'd be glad if someone could point me to a single-entity document of its architecture and internals) so I couldn't even guess what its problem is. And the system is not *that* old, really. Any help would be much appreciated, Thanks, Zoltan - tade ~ # emerge portage 2> /tmp/emsg * IMPORTANT: 5 config files in '/etc/portage' need updating. * See the CONFIGURATION FILES and CONFIGURATION FILES UPDATE TOOLS * sections of the emerge man page to learn how to update config files. [ebuild U ] app-crypt/openpgp-keys-gentoo-release-20180706 [20180703] USE="{-test%}" [ebuild R] dev-python/setuptools-36.7.2 PYTHON_TARGETS="python3_6* -python3_5*" [ebuild R] dev-python/certifi-2018.4.16 PYTHON_TARGETS="python3_6* -python3_5* (-python3_7)" [ebuild U *] app-portage/gemato- [13.0-r1] PYTHON_TARGETS="python3_6* -python3_5* -python3_7%" [ebuild U *] sys-apps/portage- [2.3.40-r1] PYTHON_TARGETS="python3_6* -python3_5* -python3_7%" !!! Multiple package instances within a single package slot have been pulled !!! into the dependency graph, resulting in a slot conflict: sys-apps/portage:0 (sys-apps/portage-:0/0::gentoo, ebuild scheduled for merge) pulled in by sys-apps/portage (Argument) (sys-apps/portage-2.3.40-r1:0/0::gentoo, installed) pulled in by sys-apps/portage[python_targets_pypy(-)?,python_targets_python2_7(-)?,python_targets_python3_4(-)?,python_targets_python3_5(-)?,python_targets_python3_6(-)?,python_targets_python3_7(-)?,-python_single_target_pypy(-),-python_single_target_python2_7(-),-python_single_target_python3_4(-),-python_single_target_python3_5(-),-python_single_target_python3_6(-),-python_single_target_python3_7(-)] required by (app-portage/gentoolkit-0.4.2-r1:0/0::gentoo, installed) sys-apps/portage[python_targets_python2_7(-)?,python_targets_python3_4(-)?,python_targets_python3_5(-)?,python_targets_python3_6(-)?,python_targets_python3_7(-)?,-python_single_target_python2_7(-),-python_single_target_python3_4(-),-python_single_target_python3_5(-),-python_single_target_python3_6(-),-python_single_target_python3_7(-)] required by (dev-java/java-config-2.2.0-r4:2/2::gentoo, installed) app-portage/gemato:0 (app-portage/gemato-:0/0::gentoo, ebuild scheduled for merge) pulled in by >=app-portage/gemato-14[python_targets_pypy(-)?,python_targets_python2_7(-)?,python_targets_python3_4(-)?,python_targets_python3_5(-)?,python_targets_python3_6(-)?,python_targets_python3_7(-)?,-python_single_target_pypy(-),-python_single_target_python2_7(-),-python_single_target_python3_4(-),-python_single_target_python3_5(-),-python_single_target_python3_6(-),-python_single_target_python3_7(-)] required by (sys-apps/portage-:0/0::gentoo, ebuild scheduled for merge) (app-portage/gemato-13.0-r1:0/0::gentoo, installed) pulled in by >=app-portage/gemato-12.1[python_targets_pypy(-)?,python_targets_python2_7(-)?,python_targets_python3_4(-)?,python_targets_python3_5(-)?,python_targets_python3_6(-)?,-python_single_target_pypy(-),-python_single_target_python2_7(-),-python_single_target_python3_4(-),-python_single_target_python3_5(-),-python_single_target_python3_6(-)] required by (sys-apps/portage-2.3.40-r1:0/0::gentoo, installed) dev-python/setuptools:0 (dev-python/setuptools-36.7.2:0/0::gentoo, ebuild scheduled for merge) pulled in by >=dev-python/setuptools-34[python_targets_pypy(-)?,python_targets_python2_7(-)?,python_targets_python3_4(-)?,python_targets_python3_5(-)?,python_ta
[gentoo-user] Re: Firefox and Thunderbird compile issue
On 2018-11-18, Daniel Frey wrote: [...] > It's really unfortunate that on massive builds distcc is not an option. > Maybe I should consider -bin instead. If you do happen to have a more powerful machine running Gentoo on a compatible architecture[1], you could also try Gentoo binary packages (that is, not -bin, but binary packages made from www-client/firefox and mail-client/thunderbird on that machine, either automatically with FEATURES=buildpkg, or manually using quickpkg or emerge --buildpkg). [1] I guess it should also be possible to cross-compile, but that will require additional steps, with which I am not acquainted. Do you know Seamonkey? If you like it and it works for everything you use Firefox and Thunderbird with, another idea to consider would be replacing Firefox and Thunderbird with Seamonkey Navigator and Seamonkey Mail&News. That way, it would be "just" one massive build instead of two. -- Nuno Silva
Re: [gentoo-user] Why falkon?
On Monday, 19 November 2018 23:40:04 GMT Neil Bothwick wrote: > On Mon, 19 Nov 2018 09:27:30 +, Peter Humphrey wrote: > > Would someone kindly enloghten me as to why the presence of qtwebengine > > now requires installation of www-client/falkon? --->8 > It doesn't, it's the kdecore-meta package that depends on it, controlled > by the webengine USE flag. qtwebengine doesn't require falkon at all, > it's the other way round. Hmm. I see what you mean. Maybe this is the straw that makes me strip out all the stuff I don't need, by removing meta-packages and just installing what I want. After all, there's a limit to the number of web browsers a body might need. -- Regards, Peter.
Re: [gentoo-user] A question regarding building Gentoo and UEFI vs Non UEFI
On Tuesday, 20 November 2018 09:29:42 GMT Andrew Lowe wrote: > On 20/11/18 17:16, Neil Bothwick wrote: > > On Tue, 20 Nov 2018 12:51:34 +0800, Andrew Lowe wrote: > >>I just have this little niggling doubt, probably baseless, in > >> > >> the back of my mind that there maybe something that may cause a problem > >> for the newly built stuff due to it not being natively booted in UEFI or > >> something like that when it was built. > > > > The only issue you're likely to face is setting up booting from the SSD. > > You need to be booted via UEFI to set up UEFI booting, but you can do > > that from your SysResCd stick. > > The SSD is up and running. I get Gentoo booting to a console and I'm > now in the process of getting stuff installed, LibreOffice, Firefox, > Thunderird etc, stuff that takes ages to build. So now that I'm > confident that things will work, I can continue to work, from the old > disk, chroot into the new and continue to install there. > > Thanks, > Andrew You can check you have booted with UEFI instead of MBR legacy (emulation) by listing the EFI variables: ls -la /sys/firmware/efi/ If it's empty you have booted in good ol' MBR. -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] sys-apps/systemd-239-r2 does not install completely
Am 20.11.18 um 11:19 schrieb Neil Bothwick: > On Tue, 20 Nov 2018 10:49:27 +0100, Stefan G. Weichinger wrote: > >>> What version does "qlist ICv systemd" show? >> >> No version, just a long list of files. > > That should have been "qlist -ICv systemd" thanks -> # qlist -ICv systemd sys-apps/gentoo-systemd-integration-7 sys-apps/systemd-236-r5
Re: [gentoo-user] sys-apps/systemd-239-r2 does not install completely
On Tue, 20 Nov 2018 10:49:27 +0100, Stefan G. Weichinger wrote: > > What version does "qlist ICv systemd" show? > > No version, just a long list of files. That should have been "qlist -ICv systemd" -- Neil Bothwick Do you realize how many holes there could be if people would just take the time to take the dirt out of them? pgp5QjnYEKOQM.pgp Description: OpenPGP digital signature
Re: [gentoo-user] sys-apps/systemd-239-r2 does not install completely
Am 20.11.18 um 10:19 schrieb Neil Bothwick: > On Mon, 19 Nov 2018 10:14:01 +0100, Stefan G. Weichinger wrote: > upgrading from sys-apps/systemd-236-r5 to 239-r2 the emerge runs through and warns me that it overwrites files ... so it merges only partially ... >>> >>> What's the exact error message? You may get a suggested >>> solution based on this vague description of the problem but it >>> may not be the right one, or even safe. >>> >>> Normally emerge will put up a warning like this before >>> installing anything. >> >> pasted error msg below >> >> --- >> >> * Package 'sys-apps/systemd-239-r2' merged despite file >> collisions. If * necessary, refer to your elog messages for the >> whole content of the * above message. > > According to this the file collisions were ignore and the updated > package installed, so either something else prevented the > installation from completing or eix is confused. > > What version does "qlist ICv systemd" show? No version, just a long list of files. > How about "ls -ld /var/db/pkg/sys-apps/systemd-*"? # ls -ld /var/db/pkg/sys-apps/systemd-* drwxr-xr-x 2 root root 4096 May 15 2018 /var/db/pkg/sys-apps/systemd-236-r5 but: # systemctl --version systemd 239 and to even make it more interesting: # dmesg -t | grep systemd # last lines ... [Sat Nov 17 10:42:14 2018] systemd[1]: systemd 238 running in system mode. (+PAM -AUDIT -SELINUX +IMA -APPARMOR +SMACK -SYSVINIT +UTMP -LIBCRYPTSETUP +GCRYPT -GNUTLS +ACL -XZ +LZ4 +SECCOMP +BLKID -ELFUTILS +KMOD -IDN2 -IDN +PCRE2 default-hierarchy=hybrid) [Sat Nov 17 10:42:14 2018] systemd[1]: Detected architecture x86-64. [Sat Nov 17 10:42:14 2018] systemd[1]: File /lib/systemd/system/systemd-journald.service:35 configures an IP firewall (IPAddressDeny=any), but the local system does not support BPF/cgroup based firewalling. [Sat Nov 17 10:42:14 2018] systemd[1]: Proceeding WITHOUT firewalling in effect! (This warning is only shown for the first loaded unit using IP firewalling.) [Sat Nov 17 10:51:01 2018] systemd[1]: Reloading. [Sat Nov 17 10:51:01 2018] systemd[1]: /lib/systemd/system/systemd-journald.service:32: Unknown system call group, ignoring: @system-service [Sat Nov 17 10:51:01 2018] systemd[1]: /lib/systemd/system/systemd-udevd.service:28: Unknown lvalue 'PrivateMounts' in section 'Service' [Sat Nov 17 10:51:01 2018] systemd[1]: /lib/systemd/system/systemd-udevd.service:32: Unknown system call group, ignoring: @system-service [Sat Nov 17 10:51:01 2018] systemd[1]: /lib/systemd/system/systemd-timesyncd.service:41: Unknown system call group, ignoring: @system-service [Sat Nov 17 10:51:01 2018] systemd[1]: /lib/systemd/system/systemd-machined.service:26: Unknown system call group, ignoring: @system-service [Sat Nov 17 10:51:01 2018] systemd[1]: /lib/systemd/system/systemd-logind.service:33: Unknown system call group, ignoring: @system-service [Sat Nov 17 10:51:01 2018] systemd[1]: /lib/systemd/system/systemd-resolved.service:41: Unknown system call group, ignoring: @system-service [Sat Nov 17 10:51:01 2018] systemd[1]: /lib/systemd/system/systemd-networkd.service:38: Unknown system call group, ignoring: @system-service [Mon Nov 19 19:26:34 2018] systemd-journald[226]: Failed to set ACL on /var/log/journal/9ce1e483f41dcc57a00e5611521d1771/user-1018.journal, ignoring: Operation not supported
Re: [gentoo-user] A question regarding building Gentoo and UEFI vs Non UEFI
On 20/11/18 17:16, Neil Bothwick wrote: > On Tue, 20 Nov 2018 12:51:34 +0800, Andrew Lowe wrote: > >> I just have this little niggling doubt, probably baseless, in >> the back of my mind that there maybe something that may cause a problem >> for the newly built stuff due to it not being natively booted in UEFI or >> something like that when it was built. > > The only issue you're likely to face is setting up booting from the SSD. > You need to be booted via UEFI to set up UEFI booting, but you can do > that from your SysResCd stick. > > The SSD is up and running. I get Gentoo booting to a console and I'm now in the process of getting stuff installed, LibreOffice, Firefox, Thunderird etc, stuff that takes ages to build. So now that I'm confident that things will work, I can continue to work, from the old disk, chroot into the new and continue to install there. Thanks, Andrew
Re: [gentoo-user] sys-apps/systemd-239-r2 does not install completely
On Mon, 19 Nov 2018 10:14:01 +0100, Stefan G. Weichinger wrote: > >> upgrading from sys-apps/systemd-236-r5 to 239-r2 > >> > >> the emerge runs through and warns me that it overwrites files ... > >> so it merges only partially ... > > > > What's the exact error message? You may get a suggested solution > > based on this vague description of the problem but it may not be > > the right one, or even safe. > > > > Normally emerge will put up a warning like this before installing > > anything. > > pasted error msg below > > --- > > * Package 'sys-apps/systemd-239-r2' merged despite file collisions. If > * necessary, refer to your elog messages for the whole content of the > * above message. According to this the file collisions were ignore and the updated package installed, so either something else prevented the installation from completing or eix is confused. What version does "qlist ICv systemd" show? How about "ls -ld /var/db/pkg/sys-apps/systemd-*"? > /var/tmp/portage/sys-apps/systemd-239-r2/temp/environment: line 190: > warning: setlocale: LC_NUMERIC: cannot change locale (de_AT.UTF-8) > /var/tmp/portage/sys-apps/systemd-239-r2/temp/environment: line 192: > warning: setlocale: LC_TIME: cannot change locale (de_AT.UTF-8) > /var/tmp/portage/sys-apps/systemd-239-r2/temp/environment: line 190: > warning: setlocale: LC_NUMERIC: cannot change locale (de_AT.UTF-8) > /var/tmp/portage/sys-apps/systemd-239-r2/temp/environment: line 192: > warning: setlocale: LC_TIME: cannot change locale (de_AT.UTF-8) > !!! Failed to copy extended attributes. In order to avoid this error, > !!! set FEATURES="-xattr" in make.conf. > !!! copy > /var/tmp/portage/sys-apps/systemd-239-r2/image/var/log/journal/remote/.keep_sys-apps_systemd-0 > -> /var/log/journal/remote/.keep_sys-apps_systemd-0 failed. > !!! Filesystem containing file > '/var/log/journal/remote/.keep_sys-apps_systemd-0#new' does not > support extended attribute 'system.posix_acl_access' > /var/tmp/portage/sys-apps/systemd-239-r2/temp/environment: line 190: > warning: setlocale: LC_NUMERIC: cannot change locale (de_AT.UTF-8) > /var/tmp/portage/sys-apps/systemd-239-r2/temp/environment: line 192: > warning: setlocale: LC_TIME: cannot change locale (de_AT.UTF-8) > > * Messages for package sys-apps/systemd-239-r2: > > * CONFIG_CGROUP_BPF:is not set when it should be. > * Please check to make sure these options are set correctly. > * Failure to do so may cause unexpected problems. > > * Messages for package sys-apps/systemd-239-r2: > > * This package will overwrite one or more files that may belong to > other > * packages (see list below). You can use a command such as `portageq > * owners / ` to identify the installed package that owns a > * file. If portageq reports that only one package owns a file then do > * NOT file a bug report. A bug report is only useful if it identifies > at > * least two or more packages that are known to install the same > file(s). > * If a collision occurs and you can not explain where the file came > from > * then you should simply ignore the collision since there is not enough > * information to determine if a real problem exists. Please do NOT file > * a bug report at https://bugs.gentoo.org/ unless you report exactly > * which two packages install the same file(s). See > * https://wiki.gentoo.org/wiki/Knowledge_Base:Blockers for tips on how > * to solve the problem. And once again, please do NOT file a bug report > * unless you have completely understood the above message. > * > * Detected file collision(s): > * > */lib64/libsystemd.so.0.23.0 > */lib64/libudev.so.1.6.11 > */lib/systemd/systemd-time-wait-sync > */lib/systemd/systemd-portabled > */lib/systemd/portablectl > */lib/systemd/systemd-user-runtime-dir > */lib/systemd/libsystemd-shared-239.so > */lib/systemd/portable/profile/trusted/service.conf > */lib/systemd/portable/profile/strict/service.conf > */lib/systemd/portable/profile/nonetwork/service.conf > */lib/systemd/portable/profile/default/service.conf > */lib/systemd/system/system-update-pre.target > */lib/systemd/system/suspend-then-hibernate.target > */lib/systemd/system/user-runtime-dir@.service > */lib/systemd/system/systemd-time-wait-sync.service > */lib/systemd/system/systemd-portabled.service > */lib/systemd/system/systemd-suspend-then-hibernate.service > */lib/systemd/system/user-.slice.d/10-defaults.conf > */usr/bin/resolvectl > */usr/lib/tmpfiles.d/portables.conf > */usr/share/locale/ja/LC_MESSAGES/systemd.mo > */usr/share/doc/systemd-239-r2/NEWS.bz2 > */usr/share/doc/systemd-239-r2/TODO.bz2 > */usr/share/doc/systemd-239-r2/nsswitch.conf.bz2 > */usr/share/doc/systemd-239-r2/UIDS-GIDS.md.bz2 > */usr/share/doc/systemd-239-r2/README.md.bz2 > */usr/share/doc/systemd-239-r2/TRANSLATORS.bz2 > */usr/share/doc/systemd-239-r2/README.bz2 >
Re: [gentoo-user] A question regarding building Gentoo and UEFI vs Non UEFI
On Tue, 20 Nov 2018 12:51:34 +0800, Andrew Lowe wrote: > I just have this little niggling doubt, probably baseless, in > the back of my mind that there maybe something that may cause a problem > for the newly built stuff due to it not being natively booted in UEFI or > something like that when it was built. The only issue you're likely to face is setting up booting from the SSD. You need to be booted via UEFI to set up UEFI booting, but you can do that from your SysResCd stick. -- Neil Bothwick Few women admit their age. Few men act theirs. pgp1cx3aPsOlH.pgp Description: OpenPGP digital signature