Gazzy
Posts: 29
Joined: Tue Aug 27, 2019 1:40 am

Re: Updated 64-bit Gentoo Image for RPi3 Released (now also for RPi3B+ and RPi4B)

Wed Aug 28, 2019 11:17 am

Ok sounds good.

Do you know at all why I can’t open pyconfig_gen, from the drop down menu

It works fine until I change locale, away from GB, then it won’t open anymore from the menu

And I have to use the terminal to issue sudo pyconfig_gen

And it opens but gives these errors.

[E] Invalid device/display ID
[E] Invalid device/display ID

I’m not sure where the files are or what it might be about, maybe the display overlay ???

Maybe you know more

Gazzy

User avatar
sakaki
Posts: 374
Joined: Sun Jul 16, 2017 1:11 pm

Re: Updated 64-bit Gentoo Image for RPi3 Released (now also for RPi3B+ and RPi4B)

Wed Aug 28, 2019 11:35 am

I'll have a look at that now also, as I'm preparing 1.5.1 atm.

What steps exactly do you do to cause the pyconfig_gen issue (when changing locale), so I can reproduce?

Thanks, sakaki

Gazzy
Posts: 29
Joined: Tue Aug 27, 2019 1:40 am

Re: Updated 64-bit Gentoo Image for RPi3 Released (now also for RPi3B+ and RPi4B)

Wed Aug 28, 2019 12:08 pm

Following the guides,

I change the keyboards, by editing

conf.d/keymaps
xorg.conf.d/00keyboard.conf
#restart to enable keys.

Then edit
local.gen
# and I just change GB to my country code
#Then
local.gen
eselect local list
eselect local set 6
# then update ~/.bashrc , and also ~/.profile
#With
export lang=“en_#countrycode#.UTF-8”
export LC_COLLATE=“c”

#Then
env-update && source /etc/profile
source ~/.bashrc

#That’s really all
I restart to make sure it sticks,
And after, eselect stages it stops working.
After restart, it will only works from the terminal, with sudo.

Gazzy

Gazzy
Posts: 29
Joined: Tue Aug 27, 2019 1:40 am

Re: Updated 64-bit Gentoo Image for RPi3 Released (now also for RPi3B+ and RPi4B)

Wed Aug 28, 2019 12:47 pm

Are you packing the new bis kernels into
1.51, I hope so,
And also a new set of startx4* and fixup4*
Files, as I hope we get all the bugs ironed
Out so it boots first time,

I reinstalled 1.5 a lot, as I haven’t used Linux or gentoo for a few years, so I have been practicing a bit, trying to get it all working straight.

I’ll reinstall again 1.51. So I can test everything I’ve already done. So I hope your updates go well.

Gazzy

User avatar
sakaki
Posts: 374
Joined: Sun Jul 16, 2017 1:11 pm

Re: Updated 64-bit Gentoo Image for RPi3 Released (now also for RPi3B+ and RPi4B)

Wed Aug 28, 2019 1:01 pm

Gazzy wrote:
Wed Aug 28, 2019 12:47 pm
Are you packing the new bis kernels into
1.51, I hope so,
And also a new set of startx4* and fixup4*
Files, as I hope we get all the bugs ironed
Out so it boots first time,

I reinstalled 1.5 a lot, as I haven’t used Linux or gentoo for a few years, so I have been practicing a bit, trying to get it all working straight.

I’ll reinstall again 1.51. So I can test everything I’ve already done. So I hope your updates go well.

Gazzy
Yes, v1.5.1 will have the latest kernels; there's an important fix (PR#3164) for WiFi + bounce buffers in the latest one. By default, the ebuild for the binary kernels drags along the boot firmware that was current at the time they were compiled, so this will get bumped also on v1.5.1.

Just added your suggested OpenRC fix for swclock, and the pulseaudio fix.

Working on the WiFi regdom and pyconfig_gen issues now.

Best, sakaki

PS I gave a false steer earlier when I said "iw reg set WIFI_REGDOM=“<country_code>”"; should just have said "iw reg set <country_code>" of course ($WIFI_REGDOM is a variable, set in /etc/conf.d/rpi3-wifi-regdom, and used by the /etc/init.d/rpi3-wifi-regdom script). Apologies for any confusion ><

Gazzy
Posts: 29
Joined: Tue Aug 27, 2019 1:40 am

Re: Updated 64-bit Gentoo Image for RPi3 Released (now also for RPi3B+ and RPi4B)

Wed Aug 28, 2019 1:22 pm

That’s fine, I think it sets that rpi3 file anyway, as it didn’t fail on the terminal. ( all other combos failed with an error. )

If you can think of a way, you should paste your changes, or a small guide on how to install the fanshim software, rpi4s get quite hot and I think the fanshim is a good solution, that is a reasonable price.

I sort of winged it to change the install.sh so it installed a rc-update service. But most people may have more trouble than me.

I really think the fan shim is essential to make the p4 run cooler, especially if you plan to do an emerge.

It could help people if you could post a paste of your rc-update service install script.

Thanks for all your help

Gazzy

Gazzy
Posts: 29
Joined: Tue Aug 27, 2019 1:40 am

Re: Updated 64-bit Gentoo Image for RPi3 Released (now also for RPi3B+ and RPi4B)

Wed Aug 28, 2019 1:48 pm

This is a exerpt of my install script, i dont know if I made any mistakes

#!/sbin/openrc-run

depend() {
need net
}

name=fanshim
command="$(pwd)/automatic.py"
command_args="--on-threshold $ON_THRESHOLD --off-threshold $OFF_THRESHOLD --delay $DELAY --brightness $BRIGHTNESS $EXTRA_ARGS"
command_user="root"
pidfile="/run/${RC_SVNAME}/PID"
command_background="yes"


printf "\nInstalling service to$(pwd)/automatic.py: $SERVICE_PATH\n"
echo "$UNIT_FILE" > $SERVICE_PATH
chmod +x /etc/init.d/fanshim

rc-update add fanshim default
rc-service fanshim restart
rc-service fanshim status


If you see anything wrong, you could give me a tip???

I seem to have it all working but any tips would help its quite new to me.

Thanks Gazzy

User avatar
sakaki
Posts: 374
Joined: Sun Jul 16, 2017 1:11 pm

Re: Updated 64-bit Gentoo Image for RPi3 Released (now also for RPi3B+ and RPi4B)

Wed Aug 28, 2019 9:05 pm

Gazzy,

after testing, I reverted for the meantime the Alpine Linux swclock fix you linked earlier. It worked most times, but not every time, so I think there's maybe a race condition in there somewhere.

I tried changing locales etc and couldn't reproduce the problem with not being able to launch pyconfig_gen from the menu anymore. I wonder if perhaps your environment variables got clobbered somehow when you edited ~/.bashrc and ~/.profile? Could you check what "env" prints out for your regular user after the locale changes have been made? Also have you by any chance set up a new user, or are you using demouser? If a new user, are they part of all necessary groups (sudo, wheel etc.)? Are you able to launch the app OK if you revert LANG to en_GB.utf8 (e.g. in ~/.bashrc) and reboot?

As to the Pimoroni fan shim (I am using these too on my Pi4s, while waiting for my Flirc cases to arrive!), I assume the automatic.py script you are trying to install is from https://github.com/pimoroni/fanshim-pyt ... tomatic.py?

If so, then ideally you'd want to write a simple ebuild to install this and its deps (rather than using e.g. pip). Your initscript looks like it should work (although adding a "need net" will prevent it starting if the network is offline - the loopback interfaces being up is not sufficient to satisfy net, as noted here, near the end), and also, I assume your variables are coming from a matching /etc/conf.d file?.

Anyway, I'll have look at publishing an ebuild / service for the fan shim, once the bugfix release is out: even without a temperature-monitoring driver, the fan shim defaults to running when plugged in, which is at least a safe default (even if not ideal).

Best, sakaki

Gazzy
Posts: 29
Joined: Tue Aug 27, 2019 1:40 am

Re: gentoo env

Thu Aug 29, 2019 12:03 am

hey, sakaki

here is my env

demouser@pi64 ~ $ env
SHELL=/bin/bash
SESSION_MANAGER=local/pi64:@/tmp/.ICE-unix/2412,unix/pi64:/tmp/.ICE-unix/2412
WINDOWID=56623107
COLORTERM=truecolor
XDG_CONFIG_DIRS=/etc/xdg:/etc/xdg
LESS=-R -M --shift 5
XDG_SESSION_PATH=/org/freedesktop/DisplayManager/Session0
XDG_MENU_PREFIX=xfce-
JDK_HOME=/home/demouser/.gentoo/java-config-2/current-user-vm
CONFIG_PROTECT_MASK=/etc/sandbox.d /etc/fonts/fonts.conf /etc/gentoo-release /etc/terminfo /etc/dconf /etc/ca-certificates.conf /etc/revdep-rebuild
DISTCC_VERBOSE=0
JAVA_HOME=/home/demouser/.gentoo/java-config-2/current-user-vm
SSH_AUTH_SOCK=/var/run/user/1000/keyring/ssh
ANT_HOME=/usr/share/ant
DESKTOP_SESSION=xfce
EDITOR=/bin/nano
GTK_MODULES=canberra-gtk-module
XDG_SEAT=seat0
PWD=/home/demouser
CONFIG_PROTECT=/usr/share/gnupg/qualified.txt /usr/lib64/libreoffice/program/sofficerc /boot/config.txt /boot/cmdline.txt
XDG_SESSION_DESKTOP=xfce
LOGNAME=demouser
XDG_SESSION_TYPE=x11
DISTCC_TCP_CORK=
MANPATH=/home/demouser/.gentoo/java-config-2/current-user-vm/man:/usr/share/gcc-data/aarch64-unknown-linux-gnu/9.1.0/man:/usr/share/binutils-data/aarch64-unknown-linux-gnu/2.32/man:/usr/lib/llvm/8/share/man:/etc/java-config-2/current-system-vm/man/:/usr/local/share/man:/usr/share/man:/usr/share/rust-1.36.0/man
XAUTHORITY=/home/demouser/.Xauthority
UNCACHED_ERR_FD=
XDG_GREETER_DATA_DIR=/var/lib/lightdm-data/demouser
HOME=/home/demouser
LANG=en_AU.UTF-8
LS_COLORS=rs=0:di=01;34:ln=01;36:mh=00:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=01;05;37;41:mi=01;05;37;41:su=37;41:sg=30;43:ca=30;41:tw=30;42:ow=34;42:st=37;44:ex=01;32:*.tar=01;31:*.tgz=01;31:*.arc=01;31:*.arj=01;31:*.taz=01;31:*.lha=01;31:*.lz4=01;31:*.lzh=01;31:*.lzma=01;31:*.tlz=01;31:*.txz=01;31:*.tzo=01;31:*.t7z=01;31:*.zip=01;31:*.z=01;31:*.dz=01;31:*.gz=01;31:*.lrz=01;31:*.lz=01;31:*.lzo=01;31:*.xz=01;31:*.zst=01;31:*.tzst=01;31:*.bz2=01;31:*.bz=01;31:*.tbz=01;31:*.tbz2=01;31:*.tz=01;31:*.deb=01;31:*.rpm=01;31:*.jar=01;31:*.war=01;31:*.ear=01;31:*.sar=01;31:*.rar=01;31:*.alz=01;31:*.ace=01;31:*.zoo=01;31:*.cpio=01;31:*.7z=01;31:*.rz=01;31:*.cab=01;31:*.wim=01;31:*.swm=01;31:*.dwm=01;31:*.esd=01;31:*.jpg=01;35:*.jpeg=01;35:*.mjpg=01;35:*.mjpeg=01;35:*.gif=01;35:*.bmp=01;35:*.pbm=01;35:*.pgm=01;35:*.ppm=01;35:*.tga=01;35:*.xbm=01;35:*.xpm=01;35:*.tif=01;35:*.tiff=01;35:*.png=01;35:*.svg=01;35:*.svgz=01;35:*.mng=01;35:*.pcx=01;35:*.mov=01;35:*.mpg=01;35:*.mpeg=01;35:*.m2v=01;35:*.mkv=01;35:*.webm=01;35:*.ogm=01;35:*.mp4=01;35:*.m4v=01;35:*.mp4v=01;35:*.vob=01;35:*.qt=01;35:*.nuv=01;35:*.wmv=01;35:*.asf=01;35:*.rm=01;35:*.rmvb=01;35:*.flc=01;35:*.avi=01;35:*.fli=01;35:*.flv=01;35:*.gl=01;35:*.dl=01;35:*.xcf=01;35:*.xwd=01;35:*.yuv=01;35:*.cgm=01;35:*.emf=01;35:*.ogv=01;35:*.ogx=01;35:*.cfg=00;32:*.conf=00;32:*.diff=00;32:*.doc=00;32:*.ini=00;32:*.log=00;32:*.patch=00;32:*.pdf=00;32:*.ps=00;32:*.tex=00;32:*.txt=00;32:*.aac=00;36:*.au=00;36:*.flac=00;36:*.m4a=00;36:*.mid=00;36:*.midi=00;36:*.mka=00;36:*.mp3=00;36:*.mpc=00;36:*.ogg=00;36:*.ra=00;36:*.wav=00;36:*.oga=00;36:*.opus=00;36:*.spx=00;36:*.xspf=00;36:
XDG_CURRENT_DESKTOP=XFCE
FLTK_DOCDIR=/usr/share/doc/fltk-1.3.5-r2/html
VTE_VERSION=5404
OPENGL_PROFILE=xorg-x11
XDG_SEAT_PATH=/org/freedesktop/DisplayManager/Seat0
DISTCC_FALLBACK=1
DCC_EMAILLOG_WHOM_TO_BLAME=
QT_GRAPHICSSYSTEM=raster
GLADE_CATALOG_PATH=:
INFOPATH=/usr/share/gcc-data/aarch64-unknown-linux-gnu/9.1.0/info:/usr/share/binutils-data/aarch64-unknown-linux-gnu/2.32/info:/usr/share/info:/usr/share/info/emacs-26
JAVAC=/home/demouser/.gentoo/java-config-2/current-user-vm/bin/javac
XDG_SESSION_COOKIE=pi64-1567002590.287885-1609203187
TERM=xterm-256color
LESSOPEN=|lesspipe %s
USER=demouser
MANPAGER=manpager
DISPLAY=:0.0
SHLVL=2
DISTCC_SAVE_TEMPS=0
PAGER=/usr/bin/less
DISTCC_SSH=
XDG_VTNR=7
GLADE_MODULE_PATH=:
XDG_RUNTIME_DIR=/var/run/user/1000
XSESSION=Xfce4
GCC_SPECS=
GLADE_PIXMAP_PATH=:
GSETTINGS_BACKEND=dconf
DISTCC_ENABLE_DISCREPANCY_EMAIL=
LC_COLLATE=C
XDG_DATA_DIRS=/usr/local/share:/usr/share:/usr/share
PATH=/usr/lib/llvm/8/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/opt/bin
GDMSESSION=xfce
DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-z2y6UapBip,guid=2c8aa2c6b1e1bf448afeec025d668fde
MAIL=/var/mail/demouser
_=/usr/bin/env

not sure what might be wrong, maybe the tv im using, or a display driver thing.

Gazzy

Gazzy
Posts: 29
Joined: Tue Aug 27, 2019 1:40 am

Re: Updated 64-bit Gentoo Image for RPi3 Released (now also for RPi3B+ and RPi4B)

Thu Aug 29, 2019 12:14 am

sakaki

yes, when i revert back to GB, the pyconfig_gen starts to work again from the drop down menu.

here is my reverted env if it helps.

demouser@pi64 ~ $ env
SHELL=/bin/bash
SESSION_MANAGER=local/pi64:@/tmp/.ICE-unix/2411,unix/pi64:/tmp/.ICE-unix/2411
WINDOWID=56623107
COLORTERM=truecolor
XDG_CONFIG_DIRS=/etc/xdg
LESS=-R -M --shift 5
XDG_SESSION_PATH=/org/freedesktop/DisplayManager/Session0
XDG_MENU_PREFIX=xfce-
JDK_HOME=/home/demouser/.gentoo/java-config-2/current-user-vm
CONFIG_PROTECT_MASK=/etc/sandbox.d /etc/fonts/fonts.conf /etc/gentoo-release /etc/terminfo /etc/dconf /etc/ca-certificates.conf /etc/revdep-rebuild
DISTCC_VERBOSE=0
JAVA_HOME=/home/demouser/.gentoo/java-config-2/current-user-vm
SSH_AUTH_SOCK=/var/run/user/1000/keyring/ssh
ANT_HOME=/usr/share/ant
DESKTOP_SESSION=xfce
EDITOR=/bin/nano
GTK_MODULES=canberra-gtk-module
XDG_SEAT=seat0
PWD=/home/demouser
CONFIG_PROTECT=/usr/share/gnupg/qualified.txt /usr/lib64/libreoffice/program/sofficerc /boot/config.txt /boot/cmdline.txt
XDG_SESSION_DESKTOP=xfce
LOGNAME=demouser
XDG_SESSION_TYPE=x11
DISTCC_TCP_CORK=
MANPATH=/home/demouser/.gentoo/java-config-2/current-user-vm/man:/usr/share/gcc-data/aarch64-unknown-linux-gnu/9.1.0/man:/usr/share/binutils-data/aarch64-unknown-linux-gnu/2.32/man:/usr/lib/llvm/8/share/man:/etc/java-config-2/current-system-vm/man/:/usr/local/share/man:/usr/share/man:/usr/share/rust-1.36.0/man
XAUTHORITY=/home/demouser/.Xauthority
UNCACHED_ERR_FD=
XDG_GREETER_DATA_DIR=/var/lib/lightdm-data/demouser
HOME=/home/demouser
LANG=en_GB.UTF-8
LS_COLORS=rs=0:di=01;34:ln=01;36:mh=00:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=01;05;37;41:mi=01;05;37;41:su=37;41:sg=30;43:ca=30;41:tw=30;42:ow=34;42:st=37;44:ex=01;32:*.tar=01;31:*.tgz=01;31:*.arc=01;31:*.arj=01;31:*.taz=01;31:*.lha=01;31:*.lz4=01;31:*.lzh=01;31:*.lzma=01;31:*.tlz=01;31:*.txz=01;31:*.tzo=01;31:*.t7z=01;31:*.zip=01;31:*.z=01;31:*.dz=01;31:*.gz=01;31:*.lrz=01;31:*.lz=01;31:*.lzo=01;31:*.xz=01;31:*.zst=01;31:*.tzst=01;31:*.bz2=01;31:*.bz=01;31:*.tbz=01;31:*.tbz2=01;31:*.tz=01;31:*.deb=01;31:*.rpm=01;31:*.jar=01;31:*.war=01;31:*.ear=01;31:*.sar=01;31:*.rar=01;31:*.alz=01;31:*.ace=01;31:*.zoo=01;31:*.cpio=01;31:*.7z=01;31:*.rz=01;31:*.cab=01;31:*.wim=01;31:*.swm=01;31:*.dwm=01;31:*.esd=01;31:*.jpg=01;35:*.jpeg=01;35:*.mjpg=01;35:*.mjpeg=01;35:*.gif=01;35:*.bmp=01;35:*.pbm=01;35:*.pgm=01;35:*.ppm=01;35:*.tga=01;35:*.xbm=01;35:*.xpm=01;35:*.tif=01;35:*.tiff=01;35:*.png=01;35:*.svg=01;35:*.svgz=01;35:*.mng=01;35:*.pcx=01;35:*.mov=01;35:*.mpg=01;35:*.mpeg=01;35:*.m2v=01;35:*.mkv=01;35:*.webm=01;35:*.ogm=01;35:*.mp4=01;35:*.m4v=01;35:*.mp4v=01;35:*.vob=01;35:*.qt=01;35:*.nuv=01;35:*.wmv=01;35:*.asf=01;35:*.rm=01;35:*.rmvb=01;35:*.flc=01;35:*.avi=01;35:*.fli=01;35:*.flv=01;35:*.gl=01;35:*.dl=01;35:*.xcf=01;35:*.xwd=01;35:*.yuv=01;35:*.cgm=01;35:*.emf=01;35:*.ogv=01;35:*.ogx=01;35:*.cfg=00;32:*.conf=00;32:*.diff=00;32:*.doc=00;32:*.ini=00;32:*.log=00;32:*.patch=00;32:*.pdf=00;32:*.ps=00;32:*.tex=00;32:*.txt=00;32:*.aac=00;36:*.au=00;36:*.flac=00;36:*.m4a=00;36:*.mid=00;36:*.midi=00;36:*.mka=00;36:*.mp3=00;36:*.mpc=00;36:*.ogg=00;36:*.ra=00;36:*.wav=00;36:*.oga=00;36:*.opus=00;36:*.spx=00;36:*.xspf=00;36:
XDG_CURRENT_DESKTOP=XFCE
FLTK_DOCDIR=/usr/share/doc/fltk-1.3.5-r2/html
VTE_VERSION=5404
OPENGL_PROFILE=xorg-x11
XDG_SEAT_PATH=/org/freedesktop/DisplayManager/Seat0
DISTCC_FALLBACK=1
DCC_EMAILLOG_WHOM_TO_BLAME=
QT_GRAPHICSSYSTEM=raster
GLADE_CATALOG_PATH=:
INFOPATH=/usr/share/gcc-data/aarch64-unknown-linux-gnu/9.1.0/info:/usr/share/binutils-data/aarch64-unknown-linux-gnu/2.32/info:/usr/share/info:/usr/share/info/emacs-26
JAVAC=/home/demouser/.gentoo/java-config-2/current-user-vm/bin/javac
XDG_SESSION_COOKIE=pi64-1567037112.334177-702106194
TERM=xterm-256color
LESSOPEN=|lesspipe %s
USER=demouser
MANPAGER=manpager
DISPLAY=:0.0
SHLVL=2
DISTCC_SAVE_TEMPS=0
PAGER=/usr/bin/less
DISTCC_SSH=
XDG_VTNR=7
GLADE_MODULE_PATH=:
XDG_RUNTIME_DIR=/var/run/user/1000
XSESSION=Xfce4
GCC_SPECS=
GLADE_PIXMAP_PATH=:
GSETTINGS_BACKEND=dconf
DISTCC_ENABLE_DISCREPANCY_EMAIL=
LC_COLLATE=C
XDG_DATA_DIRS=/usr/local/share:/usr/share
PATH=/usr/lib/llvm/8/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/opt/bin
GDMSESSION=xfce
DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-fl0UAIGNk1,guid=7a6e92f1e4e6cfb361949b855d6716b8
MAIL=/var/mail/demouser
_=/usr/bin/env

thanks, im not sure if im maybe doing it wrong or something.
Gazzy

Gazzy
Posts: 29
Joined: Tue Aug 27, 2019 1:40 am

Re: Updated 64-bit Gentoo Image for RPi3 Released (now also for RPi3B+ and RPi4B)

Thu Aug 29, 2019 12:21 am

I can notice that these Directories are different
version 1
XDG_CONFIG_DIRS=/etc/xdg:/etc/xdg


version2
XDG_CONFIG_DIRS=/etc/xdg


but i dont know what it means
Thanks
Gazzy

User avatar
sakaki
Posts: 374
Joined: Sun Jul 16, 2017 1:11 pm

Re: Updated 64-bit Gentoo Image for RPi3 Released (now also for RPi3B+ and RPi4B)

Thu Aug 29, 2019 12:25 am

Thanks, what do you get if you run:

Code: Select all

demouser@pi64 ~ $ eselect locale show
and:

Code: Select all

demouser@pi64 ~ $ locale
Also, almost certainly will make no difference but what if you use:

Code: Select all

LANG=en_AU.utf-8
(i.e. lower case utf) in your environment setup?

Best, sakaki

Gazzy
Posts: 29
Joined: Tue Aug 27, 2019 1:40 am

Re: Updated 64-bit Gentoo Image for RPi3 Released (now also for RPi3B+ and RPi4B)

Thu Aug 29, 2019 12:40 am

no lower case did not seem to help

it stops working as soon as i do the
eselect locale set 6 line

demouser@pi64 ~ $ eselect locale show
LANG variable in profile:
en_AU.utf8

demouser@pi64 ~ $ locale
LANG=en_AU.utf8
LC_CTYPE="en_AU.utf8"
LC_NUMERIC="en_AU.utf8"
LC_TIME="en_AU.utf8"
LC_COLLATE=C
LC_MONETARY="en_AU.utf8"
LC_MESSAGES="en_AU.utf8"
LC_PAPER="en_AU.utf8"
LC_NAME="en_AU.utf8"
LC_ADDRESS="en_AU.utf8"
LC_TELEPHONE="en_AU.utf8"
LC_MEASUREMENT="en_AU.utf8"
LC_IDENTIFICATION="en_AU.utf8"
LC_ALL=

there are those 2 outputs

Gazzy
Posts: 29
Joined: Tue Aug 27, 2019 1:40 am

Re: Updated 64-bit Gentoo Image for RPi3 Released (now also for RPi3B+ and RPi4B)

Thu Aug 29, 2019 12:44 am

It changes back to working after I do

sudo locale-gen

with GB in the local.gen file

if I put AU it stops working


Its a real mystery to me everything looks the same, for both locales.

Gazzy
Last edited by Gazzy on Thu Aug 29, 2019 12:46 am, edited 1 time in total.

User avatar
sakaki
Posts: 374
Joined: Sun Jul 16, 2017 1:11 pm

Re: Updated 64-bit Gentoo Image for RPi3 Released (now also for RPi3B+ and RPi4B)

Thu Aug 29, 2019 12:46 am

OK thanks, will try using these same settings tomorrow and see if I can reproduce the issue.

One other question: when you launch pyconfig_gen from the command line when in your AU locale (which you have reported works even when the menu-based version doesn't), do you do so as root, or using sudo?

If as root, can you try starting it from demouser with sudo instead (as there may be some useful diagnostic output printed).

Thanks, sakaki

Gazzy
Posts: 29
Joined: Tue Aug 27, 2019 1:40 am

Re: gentoo fix

Thu Aug 29, 2019 12:51 am

This opens the window in AU locale, this is the output

demouser@pi64 ~ $ sudo pyconfig_gen
[E] Invalid device/display ID
[E] Invalid device/display ID


then the window opens.

This is as root

pi64 /home/demouser # pyconfig_gen
[E] Invalid device/display ID
[E] Invalid device/display ID
Traceback (most recent call last):
File "/usr/lib/python-exec/python3.6/pyconfig_gen", line 10, in <module>
main_dialog.main()
File "/usr/lib64/python3.6/site-packages/pyconfig_gen/main_dialog.py", line 1105, in main
is_autostart = parser.isSet(a_opt))
File "/usr/lib64/python3.6/site-packages/pyconfig_gen/main_dialog.py", line 1073, in __init__
(self.original_uid, self.original_gid) = (int(os.environ["SUDO_UID"]),
File "/usr/lib64/python3.6/os.py", line 669, in __getitem__
raise KeyError(key) from None
KeyError: 'SUDO_UID'
pi64 /home/demouser # sudo pyconfig_gen
[E] Invalid device/display ID
[E] Invalid device/display ID

Thanks

Gazzy

User avatar
bomblord
Posts: 157
Joined: Sun Jul 14, 2019 2:54 am

Re: Updated 64-bit Gentoo Image for RPi3 Released (now also for RPi3B+ and RPi4B)

Fri Aug 30, 2019 3:55 pm

In 1.5.0 on a pi 4 and I'm noticing that porthole says there are a very large number of software packages with upgrades available but everytime I select one and select upgrade it starts to run and just says finished 0 out of 0 jobs and finishes (even when running with elevated privileges). Anyone else experienced this? Am I doing something wrong?

User avatar
sakaki
Posts: 374
Joined: Sun Jul 16, 2017 1:11 pm

Re: Updated 64-bit Gentoo Image for RPi3 Released (now also for RPi3B+ and RPi4B)

Fri Aug 30, 2019 6:14 pm

bomblord wrote:
Fri Aug 30, 2019 3:55 pm
In 1.5.0 on a pi 4 and I'm noticing that porthole says there are a very large number of software packages with upgrades available but everytime I select one and select upgrade it starts to run and just says finished 0 out of 0 jobs and finishes (even when running with elevated privileges). Anyone else experienced this? Am I doing something wrong?

Hi bomblord,

you aren't doing anything wrong, but the whole system needs updating, including the overlays etc. so that all your packages, masks, USE flags etc. are consistent, as I have changed quite a bit for v1.5.1 (once there, you can then install or upgrade individual packages using e.g. porthole, although the process below will also upgrade everything for you, so that shouldn't be necessary). The tool you need is called genup.

I'm just testing the forthcoming v1.5.1 bugfix release now, but everything's pretty much in freeze, so if you'd like to upgrade early, ensure your Pi has network connectivity then:

Code: Select all

demouser@pi64 ~ $ sudo emaint sync --repo sakaki-tools
demouser@pi64 ~ $ sudo emerge -v --update --oneshot app-portage/genup
demouser@pi64 ~ $ sudo genup
This will update your kernels, boot firmware and all affected userland packages (approximately 200 or so). Let it run to completion - although it will use binary packages from the binhost for almost all upgrades, it will still require three or so hours for everything.

Once finished (you see the message "All done - your system is now up to date!"), reboot, to start using the new kernel. Once back up, open a console and then issue:

Code: Select all

demouser@pi64 ~ $ sudo dispatch-conf
to review changes to any configuration files (only those you have edited and have upgraded base versions will be shown). If in doubt about a proposed change, press 'u' to use the new version. (You can learn more about using the dispatch-conf tool here.)

Once you have completed the config file updates, reboot once more, and you should be at v1.5.1! You can check by issuing:

Code: Select all

demouser@pi64 ~ $ eix rpi-64bit-meta
More details with the formal v1.5.1 announce to follow shortly.

hth,

sakaki

User avatar
bomblord
Posts: 157
Joined: Sun Jul 14, 2019 2:54 am

Re: Updated 64-bit Gentoo Image for RPi3 Released (now also for RPi3B+ and RPi4B)

Fri Aug 30, 2019 7:51 pm

sakaki wrote:
Fri Aug 30, 2019 6:14 pm
bomblord wrote:
Fri Aug 30, 2019 3:55 pm
In 1.5.0 on a pi 4 and I'm noticing that porthole says there are a very large number of software packages with upgrades available but everytime I select one and select upgrade it starts to run and just says finished 0 out of 0 jobs and finishes (even when running with elevated privileges). Anyone else experienced this? Am I doing something wrong?

Hi bomblord,

you aren't doing anything wrong, but the whole system needs updating, including the overlays etc. so that all your packages, masks, USE flags etc. are consistent, as I have changed quite a bit for v1.5.1 (once there, you can then install or upgrade individual packages using e.g. porthole, although the process below will also upgrade everything for you, so that shouldn't be necessary). The tool you need is called genup.

I'm just testing the forthcoming v1.5.1 bugfix release now, but everything's pretty much in freeze, so if you'd like to upgrade early, ensure your Pi has network connectivity then:

Code: Select all

demouser@pi64 ~ $ sudo emaint sync --repo sakaki-tools
demouser@pi64 ~ $ sudo emerge -v --update --oneshot app-portage/genup
demouser@pi64 ~ $ sudo genup
This will update your kernels, boot firmware and all affected userland packages (approximately 200 or so). Let it run to completion - although it will use binary packages from the binhost for almost all upgrades, it will still require three or so hours for everything.

Once finished (you see the message "All done - your system is now up to date!"), reboot, to start using the new kernel. Once back up, open a console and then issue:

Code: Select all

demouser@pi64 ~ $ sudo dispatch-conf
to review changes to any configuration files (only those you have edited and have upgraded base versions will be shown). If in doubt about a proposed change, press 'u' to use the new version. (You can learn more about using the dispatch-conf tool here.)

Once you have completed the config file updates, reboot once more, and you should be at v1.5.1! You can check by issuing:

Code: Select all

demouser@pi64 ~ $ eix rpi-64bit-meta
More details with the formal v1.5.1 announce to follow shortly.

hth,

sakaki
I'm appreciative of the detailed instructions but they error out after running genup (runs through seemingly everything but just does the installed 0 of 0 and ends in an error at the end). I'll just wait for the official 1.5.1 tar file release so I can make a new image.

User avatar
sakaki
Posts: 374
Joined: Sun Jul 16, 2017 1:11 pm

Re: Updated 64-bit Gentoo Image for RPi3 Released (now also for RPi3B+ and RPi4B)

Fri Aug 30, 2019 9:10 pm

bomblord,

so, v1.5.1 should be released this weekend. Will post here when it is.

Would you mind you pasting the console output from genup please, so I can just check what is going on? I want to make sure others can upgrade successfully from v1.5.0, and that'd be a useful diagnostic.

Thanks!

sakaki

Gazzy
Posts: 29
Joined: Tue Aug 27, 2019 1:40 am

Re: Updated 64-bit Gentoo Image for RPi3 Released (now also for RPi3B+ and RPi4B)

Sat Aug 31, 2019 4:11 am

Code: Select all

  [binary     U  ] dev-python/setuptools-41.2.0 [41.0.1] PYTHON_TARGETS="python3_7*" 
[binary   R    ] app-portage/gemato-14.1  PYTHON_TARGETS="python3_7*" 
[binary     U  ] sys-apps/portage-2.3.72 [2.3.71] PYTHON_TARGETS="python3_7*" 
[blocks B      ] <app-portage/gentoolkit-0.4.6 ("<app-portage/gentoolkit-0.4.6" is blocking sys-apps/portage-2.3.72)

 * Error: The above package list contains packages which cannot be
 * installed at the same time on the same system.

  (app-portage/gentoolkit-0.4.5:0/0::gentoo, installed) pulled in by
    >=app-portage/gentoolkit-0.3.0.8-r2 required by (app-portage/genup-1.0.24:0/0::sakaki-tools, installed)
    >=app-portage/gentoolkit-0.4.5 required by (dev-embedded/rpi-64bit-meta-1.5.0-r9:0/0::genpi64, installed)

  (sys-apps/portage-2.3.72:0/0::gentoo, binary scheduled for merge) pulled in by
    sys-apps/portage
    >=sys-apps/portage-2.3.71 required by (dev-embedded/rpi-64bit-meta-1.5.0-r9:0/0::genpi64, installed)
    sys-apps/portage[python_targets_python2_7(-)?,python_targets_python3_5(-)?,python_targets_python3_6(-)?,python_targets_python3_7(-)?,-python_single_target_python2_7(-),-python_single_target_python3_5(-),-python_single_target_python3_6(-),-python_single_target_python3_7(-)] (sys-apps/portage[python_targets_python2_7(-),python_targets_python3_5(-),python_targets_python3_6(-),-python_single_target_python2_7(-),-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)
    sys-apps/portage required by (app-admin/perl-cleaner-2.27:0/0::gentoo, installed)
    >=sys-apps/portage-2.1[python_targets_python2_7(-)?,-python_single_target_python2_7(-)] (>=sys-apps/portage-2.1[python_targets_python2_7(-),-python_single_target_python2_7(-)]) required by (app-portage/porthole-0.6.1-r6:0/0::sakaki-tools, installed)
    sys-apps/portage required by (virtual/package-manager-1:0/0::gentoo, installed)
    sys-apps/portage[python_targets_pypy(-)?,python_targets_python2_7(-)?,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_5(-),-python_single_target_python3_6(-),-python_single_target_python3_7(-)] (sys-apps/portage[python_targets_python2_7(-),python_targets_python3_5(-),python_targets_python3_6(-),-python_single_target_pypy(-),-python_single_target_python2_7(-),-python_single_target_python3_5(-),-python_single_target_python3_6(-),-python_single_target_python3_7(-)]) required by (app-portage/gentoolkit-0.4.5:0/0::gentoo, installed)


For more information about Blocked Packages, please refer to the following
section of the Gentoo Linux x86 Handbook (architecture is irrelevant):

https://wiki.gentoo.org/wiki/Handbook:X86/Working/Portage#Blocked_packages

* genup: Warning: Could not update Portage: proceeding anyway
* Bringing genup itself up to date...

Local copy of remote index is up-to-date and will be used.
Calculating dependencies... done!
>>> Auto-cleaning packages...

>>> No outdated packages were found on your system.
* Updating @world set (for new versions, or changed use flags)...
I though this looked a bit weird when updating,
says cant update portage.

Gazzy

But it seems fine-ish

Emerging 184 packages.

Could you tell us if it’s meant to be more ???

It seemed to finish fine, and I’m on the new kernel, it said I have to update 2 config files in/etc.

But in porthole there are 7 dependency packages that won’t emerge,
So I’m not quite sure what is causing that.

But it all seemed to work quite neat.

Gazzy
Last edited by Gazzy on Sat Aug 31, 2019 6:59 am, edited 1 time in total.

User avatar
Gavinmc42
Posts: 3894
Joined: Wed Aug 28, 2013 3:31 am

Re: Updated 64-bit Gentoo Image for RPi3 Released (now also for RPi3B+ and RPi4B)

Sat Aug 31, 2019 6:17 am

Code: Select all

demouser@pi64 ~ $ eix rpi-64bit-meta
[I] dev-embedded/rpi-64bit-meta [1]
     Available versions:  (~)1.5.0-r9 (~)1.5.1-r6{tbz2} {apps +boot-fw +core +innercore +kernel-bin pitop -porthash +weekly-genup +xfce}
     Installed versions:  1.5.1-r6{tbz2}(03:51:39 31/08/19)(boot-fw core innercore kernel-bin weekly-genup xfce -apps -pitop -porthash)
     Homepage:            https://github.com/sakaki-/gentoo-on-rpi-64bit
     Description:         Baseline packages for the gentoo-on-rpi-64bit image

[1] "genpi64" /usr/local/portage/genpi64
emerge 184? I had 208, but that's because I have been adding a bunch of stuff ;)

Not sure how to take a screenshot of the Openscenegraph Cessna on fire as it is fullscreen.
Vulkanscenegraph will be interesting once we have a VC6 Vulkan driver, next year maybe?

Rats, still reports Python 3.6.9, how to update that? emerge 3.7.4?
I'm dancing on Rainbows.
Raspberries are not Apples or Oranges

User avatar
sakaki
Posts: 374
Joined: Sun Jul 16, 2017 1:11 pm

Re: Updated 64-bit Gentoo Image for RPi3 Released (now also for RPi3B+ and RPi4B)

Sat Aug 31, 2019 11:48 am

Gazzy wrote:
Sat Aug 31, 2019 4:11 am

Code: Select all

  [binary     U  ] dev-python/setuptools-41.2.0 [41.0.1] PYTHON_TARGETS="python3_7*" 
[binary   R    ] app-portage/gemato-14.1  PYTHON_TARGETS="python3_7*" 
[binary     U  ] sys-apps/portage-2.3.72 [2.3.71] PYTHON_TARGETS="python3_7*" 
[blocks B      ] <app-portage/gentoolkit-0.4.6 ("<app-portage/gentoolkit-0.4.6" is blocking sys-apps/portage-2.3.72)

 * Error: The above package list contains packages which cannot be
 * installed at the same time on the same system.

  (app-portage/gentoolkit-0.4.5:0/0::gentoo, installed) pulled in by
    >=app-portage/gentoolkit-0.3.0.8-r2 required by (app-portage/genup-1.0.24:0/0::sakaki-tools, installed)
    >=app-portage/gentoolkit-0.4.5 required by (dev-embedded/rpi-64bit-meta-1.5.0-r9:0/0::genpi64, installed)

  (sys-apps/portage-2.3.72:0/0::gentoo, binary scheduled for merge) pulled in by
    sys-apps/portage
    >=sys-apps/portage-2.3.71 required by (dev-embedded/rpi-64bit-meta-1.5.0-r9:0/0::genpi64, installed)
    sys-apps/portage[python_targets_python2_7(-)?,python_targets_python3_5(-)?,python_targets_python3_6(-)?,python_targets_python3_7(-)?,-python_single_target_python2_7(-),-python_single_target_python3_5(-),-python_single_target_python3_6(-),-python_single_target_python3_7(-)] (sys-apps/portage[python_targets_python2_7(-),python_targets_python3_5(-),python_targets_python3_6(-),-python_single_target_python2_7(-),-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)
    sys-apps/portage required by (app-admin/perl-cleaner-2.27:0/0::gentoo, installed)
    >=sys-apps/portage-2.1[python_targets_python2_7(-)?,-python_single_target_python2_7(-)] (>=sys-apps/portage-2.1[python_targets_python2_7(-),-python_single_target_python2_7(-)]) required by (app-portage/porthole-0.6.1-r6:0/0::sakaki-tools, installed)
    sys-apps/portage required by (virtual/package-manager-1:0/0::gentoo, installed)
    sys-apps/portage[python_targets_pypy(-)?,python_targets_python2_7(-)?,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_5(-),-python_single_target_python3_6(-),-python_single_target_python3_7(-)] (sys-apps/portage[python_targets_python2_7(-),python_targets_python3_5(-),python_targets_python3_6(-),-python_single_target_pypy(-),-python_single_target_python2_7(-),-python_single_target_python3_5(-),-python_single_target_python3_6(-),-python_single_target_python3_7(-)]) required by (app-portage/gentoolkit-0.4.5:0/0::gentoo, installed)


For more information about Blocked Packages, please refer to the following
section of the Gentoo Linux x86 Handbook (architecture is irrelevant):

https://wiki.gentoo.org/wiki/Handbook:X86/Working/Portage#Blocked_packages

* genup: Warning: Could not update Portage: proceeding anyway
* Bringing genup itself up to date...

Local copy of remote index is up-to-date and will be used.
Calculating dependencies... done!
>>> Auto-cleaning packages...

>>> No outdated packages were found on your system.
* Updating @world set (for new versions, or changed use flags)...
I though this looked a bit weird when updating,
says cant update portage.

Gazzy

But it seems fine-ish

Gazzy
So, the initial error is, in this case, expected. What genup tries to do first is upgrade portage - the package manager used by Gentoo - on its own, before updating the rest of the system cross-sectionally. This is standard practice.

However, in this case, another installed package, gentoolkit, is blocking that single-point upgrade, as it is of too low a version to satisfy the new version of portage's deps. This will actually sort itself out later in the flow, when genup does an @world (cross-sectional) update - as both packages will then be upgraded together, obviating the issue (in Gentoo parlance, it will no longer be a hard block). The slightly lower portage version used initially is no cause for concern.
Gazzy wrote:
Sat Aug 31, 2019 4:11 am
But it seems fine-ish

Emerging 184 packages.

Could you tell us if it’s meant to be more ???

It seemed to finish fine, and I’m on the new kernel, it said I have to update 2 config files in/etc.

But in porthole there are 7 dependency packages that won’t emerge,
So I’m not quite sure what is causing that.

But it all seemed to work quite neat.

Gazzy
The exact number of packages to be updated will depend upon what other work you have done on your system etc. it will be of the order of 200 for most v1.5.0 users. If genup gave you the "All done - your system is now up to date!" message at the end, you are good to go.

Don't forget to run dispatch-conf to deal with those 2 config file updates, if you haven't already done so.

As to the remaining 7 "upgradeable but not" packages in porthole, again this is quite common, if a little confusing. What it means (for a given package foo) that foo has a newer version available in the ebuild tree, which - in the absence of any other dep-based constraints - it could be upgraded to. However, the reason it wasn't upgraded is because of another installed package having a dep on a lower version (and foo not being slotted - see my note to Gavinmc42 below).

So it looks like you've upgraded just fine ^-^
Gavinmc42 wrote:
Sat Aug 31, 2019 6:17 am

Code: Select all

demouser@pi64 ~ $ eix rpi-64bit-meta
[I] dev-embedded/rpi-64bit-meta [1]
     Available versions:  (~)1.5.0-r9 (~)1.5.1-r6{tbz2} {apps +boot-fw +core +innercore +kernel-bin pitop -porthash +weekly-genup +xfce}
     Installed versions:  1.5.1-r6{tbz2}(03:51:39 31/08/19)(boot-fw core innercore kernel-bin weekly-genup xfce -apps -pitop -porthash)
     Homepage:            https://github.com/sakaki-/gentoo-on-rpi-64bit
     Description:         Baseline packages for the gentoo-on-rpi-64bit image

[1] "genpi64" /usr/local/portage/genpi64
emerge 184? I had 208, but that's because I have been adding a bunch of stuff ;)

Not sure how to take a screenshot of the Openscenegraph Cessna on fire as it is fullscreen.
Vulkanscenegraph will be interesting once we have a VC6 Vulkan driver, next year maybe?

Rats, still reports Python 3.6.9, how to update that? emerge 3.7.4?
Looks like your upgrade went though fine also ^-^

Can't you just set a delay on the screenshooter accessory to take a full screen capture?

As to python-3.7.4, you should have it already (did you remember to check installed versions with "eix dev-lang/python"?) since the upgrade has been done.

However, python in Gentoo is slotted - that is, can have multiple versions installed at the same time. Although I've provided python-3.7.4-r2 as part of v1.5.1, following upstream I haven't made it the default yet. To do so, use the "eselect python" tool. Run "sudo eselect python list" to get a list of python interpreters. Then (if you wish) "sudo eselect python set python3.7" will make the current inhabitant of the :3.7 slot (at the moment, that's 3.7.4-r2) the default. Once done, when you run "python" or "python3" you should find you are running the 3.7.4 version (with -O3/pgo ^-^)

We talked about slotting in Gentoo before if you recall, here.

hth, sakaki

Gazzy
Posts: 29
Joined: Tue Aug 27, 2019 1:40 am

Re: Updated 64-bit Gentoo Image for RPi3 Released (now also for RPi3B+ and RPi4B)

Sat Aug 31, 2019 2:09 pm

Hey Sakaki,

So I got all the upgrading done, and everything works well. The new kernel files may be a tad faster. I still needed to reach in and set the regdom, as the update wanted to reset it to GB.

I did the genup, about three times as porthole kept finding new files, and some won’t be done by porthole so they seem to get done by genup.

I found the clock-skew fix stopped working, when I was doing some updates like those two config files. But after I played a bit (removed the checking file) then did another genup, I put the checking file back (after the gen up) and the clock skew turned off again. So I’m quite happy.

( not sure the exact mechanic but the rc-services are very full now, and I have the fanshim turn on during boot, and the swclock fix is stopping the clock skew message,
So I don’t think the issue is a boot race that stops it working, I just think the files get mixed up build dates and times, that set off the clock skew, and maybe some files are out of the scope of the script updating them. )

But I have it all updated and working well so your build and programming are very good.
Your update system genup tests very well and you don’t have to worry about it bugging or not working.

(Following the guide I also installed layman and eix, as the emerge code said it was trying to use layman. )

I still think the clock-skew fix could work ( maybe just after a full genup! ) don’t fully give up on it, when working it makes the boot a bit faster and smoother, as it no longer is generating errors.

Thanks for all your hard work on getting the prep and fixes up to 1.51, and thanks to all your friends too helping with building the great
Arm64 and rpi* repos.

The project is great and the OS is really starting to get good.

Gazzy

User avatar
bomblord
Posts: 157
Joined: Sun Jul 14, 2019 2:54 am

Re: Updated 64-bit Gentoo Image for RPi3 Released (now also for RPi3B+ and RPi4B)

Sat Aug 31, 2019 2:47 pm

Here's the genup output

Code: Select all

demouser@pi64 ~ $ sudo genup
* Checking Portage configuration, please wait...
* Gentoo System Updater v1.0.24
* Updating Portage tree and syncing the eix cache
* (this may take some time)...
 * Syncing all portage overlays
/usr/bin/eix-sync: line 396: layman: command not found
 * layman -S failed
 * Running emerge --sync
>>> Syncing repository 'gentoo' into '/usr/portage'...
 * Using keys from /usr/share/openpgp-keys/gentoo-release.asc
 * Refreshing keys via WKD ...                                           [ ok ]
>>> Starting rsync with rsync://82.221.139.201/gentoo-portage-pi64-gem...
>>> Checking server timestamp ...
receiving incremental file list
timestamp.chk

Number of files: 1 (reg: 1)
Number of created files: 0
Number of deleted files: 0
Number of regular files transferred: 1
Total file size: 32 bytes
Total transferred file size: 32 bytes
Literal data: 32 bytes
Matched data: 0 bytes
File list size: 41
File list generation time: 0.001 seconds
File list transfer time: 0.000 seconds
Total bytes sent: 104
Total bytes received: 127

sent 104 bytes  received 127 bytes  92.40 bytes/sec
total size is 32  speedup is 0.14

>>>
>>> Timestamps on the server and in the local repository are the same.
>>> Cancelling all further sync action. You are already up to date.
>>>
>>> In order to force sync, remove '/usr/portage/metadata/timestamp.chk'.
>>>

 * Manifest timestamp: 2019-08-24 00:38:58 UTC
 * Valid OpenPGP signature found:
 * - primary key: DCD05B71EAB94199527F44ACDB6B8C1F96D8BF6D
 * - subkey: E1D6ABB63BFCFB4BA02FDF1CEC590EEAC9189250
 * - timestamp: 2019-08-24 00:38:58 UTC
=== Sync completed for gentoo
q: Updating ebuild cache for /usr/portage ... 
q: Finished 36388 entries in 7.930123 seconds
>>> Syncing repository 'genpi64' into '/usr/local/portage/genpi64'...
>>> Syncing repository 'sakaki-tools' into '/usr/local/portage/sakaki-tools'...
/usr/bin/git fetch origin
/usr/bin/git fetch origin
Already up to date.
Already up to date.
=== Sync completed for sakaki-tools
=== Sync completed for genpi64
q: Updating ebuild cache for /usr/local/portage/sakaki-tools ... 
q: Updating ebuild cache for /usr/local/portage/genpi64 ... 
q: Finished 20 entries in 0.017327 seconds
q: Finished 413 entries in 0.061804 seconds

Action: sync for repo: gentoo, returned code = 0
Action: sync for repo: sakaki-tools, returned code = 0
Action: sync for repo: genpi64, returned code = 0

 * An update to portage is available. It is _highly_ recommended
 * that you update portage now, before any other packages are updated.

 * To update portage, run 'emerge --oneshot portage' now.



 * Main gentoo tree does not appear to have changed: exiting
 * Use -a or set have_changed=: in a ! hook to override this check
 * Time statistics:
    18 seconds for syncing
    19 seconds total
* Removing any prior emerge history...
Emaint: fix cleanresume    100% [============================================>]
* Bringing Portage itself up to date...

Local copy of remote index is up-to-date and will be used.
Calculating dependencies... done!
[binary     U  ] dev-python/certifi-2019.6.16 [2018.11.29] PYTHON_TARGETS="python3_7*" 
[binary     U  ] dev-python/setuptools-41.2.0 [41.0.1] PYTHON_TARGETS="python3_7*" 
[binary   R    ] app-portage/gemato-14.1  PYTHON_TARGETS="python3_7*" 
[binary     U  ] sys-apps/portage-2.3.72 [2.3.71] PYTHON_TARGETS="python3_7*" 
[blocks B      ] <app-portage/gentoolkit-0.4.6 ("<app-portage/gentoolkit-0.4.6" is blocking sys-apps/portage-2.3.72)

 * Error: The above package list contains packages which cannot be
 * installed at the same time on the same system.

  (app-portage/gentoolkit-0.4.5:0/0::gentoo, installed) pulled in by
    >=app-portage/gentoolkit-0.4.5 required by (dev-embedded/rpi-64bit-meta-1.5.0-r9:0/0::genpi64, installed)
    >=app-portage/gentoolkit-0.3.0.8-r2 required by (app-portage/genup-1.0.24:0/0::sakaki-tools, installed)

  (sys-apps/portage-2.3.72:0/0::gentoo, binary scheduled for merge) pulled in by
    sys-apps/portage required by (app-admin/perl-cleaner-2.27:0/0::gentoo, installed)
    sys-apps/portage required by (virtual/package-manager-1:0/0::gentoo, installed)
    >=sys-apps/portage-2.3.71 required by (dev-embedded/rpi-64bit-meta-1.5.0-r9:0/0::genpi64, installed)
    sys-apps/portage[python_targets_python2_7(-)?,python_targets_python3_5(-)?,python_targets_python3_6(-)?,python_targets_python3_7(-)?,-python_single_target_python2_7(-),-python_single_target_python3_5(-),-python_single_target_python3_6(-),-python_single_target_python3_7(-)] (sys-apps/portage[python_targets_python2_7(-),python_targets_python3_5(-),python_targets_python3_6(-),-python_single_target_python2_7(-),-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)
    >=sys-apps/portage-2.1[python_targets_python2_7(-)?,-python_single_target_python2_7(-)] (>=sys-apps/portage-2.1[python_targets_python2_7(-),-python_single_target_python2_7(-)]) required by (app-portage/porthole-0.6.1-r6:0/0::sakaki-tools, installed)
    sys-apps/portage
    sys-apps/portage[python_targets_pypy(-)?,python_targets_python2_7(-)?,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_5(-),-python_single_target_python3_6(-),-python_single_target_python3_7(-)] (sys-apps/portage[python_targets_python2_7(-),python_targets_python3_5(-),python_targets_python3_6(-),-python_single_target_pypy(-),-python_single_target_python2_7(-),-python_single_target_python3_5(-),-python_single_target_python3_6(-),-python_single_target_python3_7(-)]) required by (app-portage/gentoolkit-0.4.5:0/0::gentoo, installed)


For more information about Blocked Packages, please refer to the following
section of the Gentoo Linux x86 Handbook (architecture is irrelevant):

https://wiki.gentoo.org/wiki/Handbook:X86/Working/Portage#Blocked_packages

* genup: Warning: Could not update Portage: proceeding anyway
* Bringing genup itself up to date...

Local copy of remote index is up-to-date and will be used.
Calculating dependencies... done!
>>> Jobs: 0 of 0 complete                           Load avg: 0.88, 0.33, 0.12
>>> Auto-cleaning packages...

>>> No outdated packages were found on your system.
* Updating @world set (for new versions, or changed use flags)...

Local copy of remote index is up-to-date and will be used.
Calculating dependencies \

!!! Problem resolving dependencies for media-libs/mesa from @selected
... done!

!!! The following binary packages have been ignored due to non matching USE:

    =media-libs/mesa-19.2.0_rc1-r2 video_cards_vc4
    =media-libs/mesa-19.2.0_rc1 -rpi-v3d video_cards_vc4

NOTE: The --binpkg-respect-use=n option will prevent emerge
      from ignoring these binary packages if possible.
      Using --binpkg-respect-use=y will silence this warning.

!!! The ebuild selected to satisfy "media-libs/mesa" has unmet requirements.
- media-libs/mesa-19.2.0_rc1-r2::genpi64 USE="X dri3 egl gallium gbm gles1 gles2 llvm rpi-v3d xa xvmc -classic (-d3d9) -debug (-libglvnd) (-lm_sensors) (-opencl) -osmesa -pax_kernel (-selinux) -test -unwind -vaapi (-valgrind) (-vdpau) (-vulkan) (-vulkan-overlay) -wayland" VIDEO_CARDS="-freedreno (-i915) (-i965) (-intel) -iris (-lima) -nouveau -panfrost (-r100) (-r200) (-r300) (-r600) (-radeon) (-radeonsi) -vc4 -virgl -vivante (-vmware)"

  The following REQUIRED_USE flag constraints are unsatisfied:
    rpi-v3d? ( video_cards_vc4 )

  The above constraints are a subset of the following complete expression:
    d3d9? ( dri3 any-of ( video_cards_iris video_cards_r300 video_cards_r600 video_cards_radeonsi video_cards_nouveau video_cards_vmware ) ) gles1? ( egl ) gles2? ( egl ) vulkan? ( dri3 any-of ( video_cards_i965 video_cards_iris video_cards_radeonsi ) video_cards_radeonsi? ( llvm ) ) vulkan-overlay? ( vulkan ) wayland? ( egl gbm ) video_cards_freedreno? ( gallium ) video_cards_intel? ( classic ) video_cards_i915? ( any-of ( classic gallium ) ) video_cards_i965? ( classic ) video_cards_iris? ( gallium ) video_cards_lima? ( gallium ) video_cards_nouveau? ( any-of ( classic gallium ) ) video_cards_panfrost? ( gallium ) video_cards_radeon? ( any-of ( classic gallium ) gallium? ( x86? ( llvm ) amd64? ( llvm ) ) ) video_cards_r100? ( classic ) video_cards_r200? ( classic ) video_cards_r300? ( gallium x86? ( llvm ) amd64? ( llvm ) ) video_cards_r600? ( gallium ) video_cards_radeonsi? ( gallium llvm ) video_cards_vc4? ( gallium ) video_cards_virgl? ( gallium ) video_cards_vivante? ( gallium gbm ) video_cards_vmware? ( gallium ) xa? ( X ) xvmc? ( X ) rpi-v3d? ( arm64 video_cards_vc4 )

(dependency required by "@selected" [set])
(dependency required by "@world" [argument])

Local copy of remote index is up-to-date and will be used.
emerge: It seems we have nothing to resume...
* genup: Warning: emerge completed successfully, but only by restricting
* genup: Warning: build parallelism and distcc
* Removing packages not required by @world set...

 * Always study the list of packages to be cleaned for any obvious
 * mistakes. Packages that are part of the world set will always
 * be kept.  They can be manually added to this set with
 * `emerge --noreplace <atom>`.  Packages that are listed in
 * package.provided (see portage(5)) will be removed by
 * depclean, even if they are part of the world set.
 * 
 * As a safety measure, depclean will not remove any packages
 * unless *all* required dependencies have been resolved.  As a
 * consequence of this, it often becomes necessary to run 
 * `emerge --update --newuse --deep @world` prior to depclean.

Calculating dependencies... done!
 * Dependencies could not be completely resolved due to
 * the following required packages not being installed:
 * 
 *   acct-user/messagebus pulled in by:
 *     sys-apps/dbus-1.12.16
 * 
 * Have you forgotten to do a complete update prior to depclean? The
 * most comprehensive command for this purpose is as follows:
 * 
 *   emerge --update --newuse --deep --with-bdeps=y @world
 * 
 * Note that the --with-bdeps=y option is not required in many
 * situations. Refer to the emerge manual page (run `man emerge`)
 * for more information about --with-bdeps.
 * 
 * Also, note that it may be necessary to manually uninstall
 * packages that no longer exist in the repository, since it may not
 * be possible to satisfy their dependencies.

* genup: Error: Caught signal - exiting
edit: fixed it it was a stupid mistake I made editing the make.conf file a while ago I changed vc4 to vc6 to try to fix something and never changed it back.

Return to “Gentoo”