ainsley31415926

ls -lh /etc/portage/repos.conf total 4.0K -rw-r--r-- 1 root root 145 Jun 27 10:53 gentoo

Sorry guys, I am from the past. I have not updated to meta-repo I think I am ports-2012 Normally eix-sync or emerge --sync update something. For several days now I get eix-sync * Running emerge --sync >>> Syncing repository 'gentoo' into '/usr/portage'... /usr/bin/git pull Already up-to-date. === Sync completed for gentoo q: Updating ebuild cache in /usr/portage ... q: Finished 39471 entries in 2.241310 seconds * Copying old database to /var/cache/eix/previous.eix * Running eix-update Reading Portage settings... Building database (/var/cache/eix/portage.eix)... [0] "gentoo" /usr/portage/ (cache: metadata-md5-or-flat) Reading category 165|165 (100) Finished Applying masks... Calculating hash tables... Writing database file /var/cache/eix/portage.eix... Database contains 19883 packages in 165 categories * Calling eix-diff * Time statistics: 8 seconds for syncing 9 seconds for eix-update 1 seconds for eix-diff 18 seconds total

I notice there have been no updates for several days when I do emerge --sync Is this just me and my 10 machines?

e -p sys-kernel/gentoo-sources Calculating dependencies \ * ERROR: sys-kernel/gentoo-sources-4.10.2::gentoo failed (depend phase): * kernel-2: EAPI 6 not supported

Not sure what this is? emerge nvidia-drivers * ERROR: x11-drivers/nvidia-drivers-378.13::gentoo failed (pretend phase): * USE Flag 'amd64' not in IUSE for x11-drivers/nvidia-drivers-378.13 and emerge www-client/google-chrome-unstable * ERROR: www-client/google-chrome-unstable-58.0.3018.3::gentoo failed (pretend phase): * USE Flag 'amd64' not in IUSE for www-client/google-chrome-unstable-58.0.3018.3 Any clue?

With latest emerge update I get * Messages for package sys-fs/udisks-2.1.7: * CONFIG_SWAP: is not set when it should be. If I do e -pv --depclean udisks Calculating dependencies... done! sys-fs/udisks-2.1.7 pulled in by: kde-base/kdelibs-4.14.16 requires sys-fs/udisks:2 Why do I have to enable swap? I don't want it, I don't use it, but I guess I can enable it. But why do I have to enable it in the kernel - its not used.

x11-drivers/nvidia-drivers-355.11-r2 wont compile with kernel linux-4.3.0-gentoo /var/tmp/portage/x11-drivers/nvidia-drivers-355.11-r2/work/kernel/nvidia/nv-procfs.c: In function ?nv_procfs_read_registry?: /var/tmp/portage/x11-drivers/nvidia-drivers-355.11-r2/work/kernel/nvidia/nv-procfs.c:363:5: error: void value not ignored as it ought to be return seq_printf(s, "Binary: \"%s\"\n", registry_keys);

I have managed Linux servers for over 15 years. The only times I have had serious crashes, it was to do with systemd. I have even had systems that did not have systemd installed crash, because of code to do with systemd.

Sorry, posted in the wrong place. But there does not seem to be a way to delete apost.

Does anyone else have this occuring: emerge gcc Calculating dependencies... done! >>> Verifying ebuild manifests >>> Emerging (1 of 1) sys-devel/gcc-4.9.2-r2 >>> Failed to emerge sys-devel/gcc-4.9.2-r2, Log file: >>> '/var/tmp/portage/sys-devel/gcc-4.9.2-r2/temp/build.log' >>> Jobs: 0 of 1 complete, 1 failed Load avg: 0.21, 0.26, 0.81 * gcc-4.9.2.tar.bz2 SHA256 SHA512 WHIRLPOOL size ;-) ... [ ok ] >>> Downloading 'http://distfiles.gentoo.org/distfiles/gcc-4.9.2-patches-1.5.tar.bz2' --2015-09-02 15:41:38-- http://distfiles.gentoo.org/distfiles/gcc-4.9.2-patches-1.5.tar.bz2 Resolving distfiles.gentoo.org... 156.56.247.195, 140.211.166.134, 137.226.34.42, ... Connecting to distfiles.gentoo.org|156.56.247.195|:80... connected. HTTP request sent, awaiting response... 404 Not Found 2015-09-02 15:41:38 ERROR 404: Not Found. >>> Downloading 'http://ftp.osuosl.org/pub/funtoo/distfiles/gcc/gcc-4.9.2-patches-1.5.tar.bz2' --2015-09-02 15:41:38-- http://ftp.osuosl.org/pub/funtoo/distfiles/gcc/gcc-4.9.2-patches-1.5.tar.bz2 Resolving ftp.osuosl.org... 140.211.166.134 Connecting to ftp.osuosl.org|140.211.166.134|:80... connected. HTTP request sent, awaiting response... 404 Not Found 2015-09-02 15:41:39 ERROR 404: Not Found. >>> Downloading 'http://build.funtoo.org/distfiles/gcc/gcc-4.9.2-patches-1.5.tar.bz2' --2015-09-02 15:41:39-- http://build.funtoo.org/distfiles/gcc/gcc-4.9.2-patches-1.5.tar.bz2 Resolving build.funtoo.org... 172.97.103.39 Connecting to build.funtoo.org|172.97.103.39|:80... connected. HTTP request sent, awaiting response... 404 Not Found 2015-09-02 15:41:39 ERROR 404: Not Found. !!! Couldn't download 'gcc-4.9.2-patches-1.5.tar.bz2'. Aborting. * Fetch failed for 'sys-devel/gcc-4.9.2-r2', Log file: * '/var/tmp/portage/sys-devel/gcc-4.9.2-r2/temp/build.log' * Messages for package sys-devel/gcc-4.9.2-r2: * Fetch failed for 'sys-devel/gcc-4.9.2-r2', Log file: * '/var/tmp/portage/sys-devel/gcc-4.9.2-r2/temp/build.log'

I am not sure if this really worked or is even wise, but I did it anyhow. I changed to the x86-64bit arch Then added subarch intel64-haswell Then changed back to the pure64 arch Now eselect profile show looks like this: arch: gentoo:funtoo/1.0/linux-gnu/arch/pure64 build: gentoo:funtoo/1.0/linux-gnu/build/current flavor: gentoo:funtoo/1.0/linux-gnu/flavor/core subarch: gentoo:funtoo/1.0/linux-gnu/arch/x86-64bit/subarch/intel64-haswell mix-ins: gentoo:funtoo/1.0/linux-gnu/mix-ins/no-systemd But of course intel64-haswell does not show under eselect profile list

I see the missing subarch profiles in /usr/portage/profiles/profiles.eselect.desc

I have 10 servers all completely up to date, most installed in the last few days. They are slightly different from each other in their configuration and booting. They are all up to date, and they all give: Currently available arch profiles: [1] funtoo/1.0/linux-gnu/arch/x86-64bit [2] funtoo/1.0/linux-gnu/arch/pure64 * Currently available subarch profiles: [3] funtoo/1.0/linux-gnu/arch/pure64/subarch/amd64-bulldozer-pure64 [4] funtoo/1.0/linux-gnu/arch/pure64/subarch/amd64-jaguar-pure64 [5] funtoo/1.0/linux-gnu/arch/pure64/subarch/amd64-k10-pure64 [6] funtoo/1.0/linux-gnu/arch/pure64/subarch/amd64-k8-pure64 [7] funtoo/1.0/linux-gnu/arch/pure64/subarch/amd64-piledriver-pure64 [8] funtoo/1.0/linux-gnu/arch/pure64/subarch/amd64-steamroller-pure64 [9] funtoo/1.0/linux-gnu/arch/pure64/subarch/atom_64-pure64 [10] funtoo/1.0/linux-gnu/arch/pure64/subarch/core2_64-pure64 [11] funtoo/1.0/linux-gnu/arch/pure64/subarch/corei7-pure64 [12] funtoo/1.0/linux-gnu/arch/pure64/subarch/generic_64-pure64 Currently available build profiles: [13] funtoo/1.0/linux-gnu/build/stable [14] funtoo/1.0/linux-gnu/build/current * [15] funtoo/1.0/linux-gnu/build/experimental Currently available flavor profiles: [16] funtoo/1.0/linux-gnu/flavor/minimal [17] funtoo/1.0/linux-gnu/flavor/core * [18] funtoo/1.0/linux-gnu/flavor/desktop [19] funtoo/1.0/linux-gnu/flavor/workstation [20] funtoo/1.0/linux-gnu/flavor/hardened Currently available mix-ins profiles: [21] funtoo/1.0/linux-gnu/mix-ins/audio [22] funtoo/1.0/linux-gnu/mix-ins/cinnamon [23] funtoo/1.0/linux-gnu/mix-ins/console-extras [24] funtoo/1.0/linux-gnu/mix-ins/dvd [25] funtoo/1.0/linux-gnu/mix-ins/gnome [26] funtoo/1.0/linux-gnu/mix-ins/kde [27] funtoo/1.0/linux-gnu/mix-ins/mate [28] funtoo/1.0/linux-gnu/mix-ins/media (auto) [29] funtoo/1.0/linux-gnu/mix-ins/media-pro * [30] funtoo/1.0/linux-gnu/mix-ins/mediadevice-audio-consumer (auto) [31] funtoo/1.0/linux-gnu/mix-ins/mediadevice-audio-pro * (auto) [32] funtoo/1.0/linux-gnu/mix-ins/mediadevice-base (auto) [33] funtoo/1.0/linux-gnu/mix-ins/mediadevice-video-consumer (auto) [34] funtoo/1.0/linux-gnu/mix-ins/mediadevice-video-pro * (auto) [35] funtoo/1.0/linux-gnu/mix-ins/mediaformat-audio-common (auto) [36] funtoo/1.0/linux-gnu/mix-ins/mediaformat-audio-extra [37] funtoo/1.0/linux-gnu/mix-ins/mediaformat-gfx-common (auto) [38] funtoo/1.0/linux-gnu/mix-ins/mediaformat-gfx-extra [39] funtoo/1.0/linux-gnu/mix-ins/mediaformat-video-common (auto) [40] funtoo/1.0/linux-gnu/mix-ins/mediaformat-video-extra [41] funtoo/1.0/linux-gnu/mix-ins/lxde [42] funtoo/1.0/linux-gnu/mix-ins/lxqt [43] funtoo/1.0/linux-gnu/mix-ins/no-emul-linux-x86 [44] funtoo/1.0/linux-gnu/mix-ins/no-systemd * [45] funtoo/1.0/linux-gnu/mix-ins/print [46] funtoo/1.0/linux-gnu/mix-ins/python3-only [47] funtoo/1.0/linux-gnu/mix-ins/X [48] funtoo/1.0/linux-gnu/mix-ins/xfce [49] funtoo/1.0/linux-gnu/mix-ins/vmware-guest [50] funtoo/1.0/linux-gnu/mix-ins/hardened yet ls -la /usr/portage/profiles/funtoo/1.0/linux-gnu/arch/pure64/subarch/ gives total 92 drwxr-xr-x 22 root root 4096 Apr 6 22:00 . drwxr-xr-x 6 root root 4096 Apr 6 22:00 .. -rw-r--r-- 1 root root 121 Apr 6 22:00 README.txt drwxr-xr-x 2 root root 4096 Apr 6 22:00 amd64-bulldozer-pure64 drwxr-xr-x 2 root root 4096 Apr 6 22:00 amd64-jaguar-pure64 drwxr-xr-x 2 root root 4096 Apr 6 22:00 amd64-k10-pure64 drwxr-xr-x 2 root root 4096 Apr 6 22:00 amd64-k8+sse3-pure64 drwxr-xr-x 2 root root 4096 Apr 6 22:00 amd64-k8-pure64 drwxr-xr-x 2 root root 4096 Apr 6 22:00 amd64-piledriver-pure64 drwxr-xr-x 2 root root 4096 Apr 6 22:00 amd64-steamroller-pure64 drwxr-xr-x 2 root root 4096 Apr 6 22:00 atom_64-pure64 drwxr-xr-x 2 root root 4096 Apr 6 22:00 btver1_64-pure64 drwxr-xr-x 2 root root 4096 Apr 6 22:00 core-avx-i-pure64 drwxr-xr-x 2 root root 4096 Apr 6 22:00 core2_64-pure64 drwxr-xr-x 2 root root 4096 Apr 6 22:00 corei7-pure64 drwxr-xr-x 2 root root 4096 Apr 6 22:00 generic_64-pure64 drwxr-xr-x 2 root root 4096 Apr 6 22:00 intel64-haswell-pure64 drwxr-xr-x 2 root root 4096 Apr 6 22:00 intel64-ivybridge-pure64 drwxr-xr-x 2 root root 4096 Apr 6 22:00 intel64-sandybridge-pure64 drwxr-xr-x 2 root root 4096 Apr 6 22:00 native_64-pure64 drwxr-xr-x 2 root root 4096 Apr 6 22:00 nocona-pure64 drwxr-xr-x 2 root root 4096 Apr 6 22:00 opteron_64-pure64 drwxr-xr-x 2 root root 4096 Apr 6 22:00 xen-pentium4+sse3_64-pure64 What am I doing wrong?

Thats my point, I cant choose native-64, I ONLY see [9] funtoo/1.0/linux-gnu/arch/pure64/subarch/atom_64-pure64 [10] funtoo/1.0/linux-gnu/arch/pure64/subarch/core2_64-pure64 [11] funtoo/1.0/linux-gnu/arch/pure64/subarch/corei7-pure64 [12] funtoo/1.0/linux-gnu/arch/pure64/subarch/generic_64-pure64 If I look in /usr/portage/profile/funtoo/1.0/linux-gnu/arch/<preferred arch>/subarch/ There are a whole bunch of subarch's that I dont see when I do eselect profile list Am I missing something?

Looks good. But for Intel cpu's I only see [9] funtoo/1.0/linux-gnu/arch/pure64/subarch/atom_64-pure64 [10] funtoo/1.0/linux-gnu/arch/pure64/subarch/core2_64-pure64 [11] funtoo/1.0/linux-gnu/arch/pure64/subarch/corei7-pure64 [12] funtoo/1.0/linux-gnu/arch/pure64/subarch/generic_64-pure64 Is [12] the same as 'native'? What would I set for E3-1271 v3 ?