genpi64 / genpi64-overlay Goto Github PK

When I try to emerge dev-python/rpi-gpio, I get
`202 /var/db/repos/genpi64 # emerge -pv dev-python/rpi-gpio

These are the packages that would be merged, in order:

Calculating dependencies \

!!! Problem resolving dependencies for dev-python/rpi-gpio ... done!

!!! The ebuild selected to satisfy "dev-python/rpi-gpio" has unmet requirements.

• dev-python/rpi-gpio-0.7.0::genpi64 USE="" PYTHON_TARGETS="-python3_8 -python3_9"

  The following REQUIRED_USE flag constraints are unsatisfied:
  any-of ( python_targets_python3_8 python_targets_python3_9 )

`

Thankz
Jeff

Hi,
Unfortunately latest commit breaks download of some distfiles, such as here.
Seems to be due to fact that not all releases are ready for forked repos under GenPi64 whereas they were under sakaki-, e.g. this gives 404.
Thanks,
G

We set en_US.UTF-8 UTF-8 in other places.

I'm largely ignorant of how LC_MESSAGES works, so it might be that C is the correct setting.

Creating Manifest for /home/jonesmz/genpi64-overlay/net-misc/xorgxrdp

• ERROR: net-misc/xrdp-0.9.8::genpi64 failed (depend phase):
• pam: EAPI 5 not supported
• Call stack:

•       ebuild.sh, line 657:  Called source '/home/jonesmz/genpi64-overlay/net-misc/xrdp/xrdp-0.9.8.ebuild'
  

• xrdp-0.9.8.ebuild, line 6: Called inherit 'autotools' 'eutils' 'pam' 'systemd'

•       ebuild.sh, line 337:  Called __qa_source '/var/db/repos/gentoo/eclass/pam.eclass'
  

•       ebuild.sh, line 114:  Called source '/var/db/repos/gentoo/eclass/pam.eclass'
  

•      pam.eclass, line  17:  Called die
  

• The specific snippet of code:

•  *) die "${ECLASS}: EAPI ${EAPI:-0} not supported" ;;
  

• If you need support, post the output of emerge --info '=net-misc/xrdp-0.9.8::genpi64',
• the complete build log and the output of emerge -pqv '=net-misc/xrdp-0.9.8::genpi64'.
• Working directory: '/usr/lib/python3.9/site-packages'
• S: '/var/tmp/portage/net-misc/xrdp-0.9.8/work/xrdp-0.9.8'
  !!! getFetchMap(): aux_get() error reading net-misc/xrdp-0.9.8; aborting.
  !!! Unable to generate manifest for '/home/jonesmz/genpi64-overlay/net-misc/xrdp'.

Describe the bug
<-- A clear and concise description of what the bug is. -->

To Reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior
<-- A clear and concise description of what you expected to happen. -->

Screenshots
<-- If applicable, add screenshots to help explain your problem. -->

Image details (please complete the following information):

• Version used: <-- e.g. alpha6 -->

Additional context
<-- Add any other context about the problem here. -->

Upstream has newer version, which pulls in spidermonkey.

In-overlay version of xfce4-cpugraph-plugin is out of date compared to gentoo, but we carry a patch to force a periodic full screen refresh.

It's unknown whether this patch exists because of a raspberry pi issue, or if it was with the original package copied from gentoo.

Describe the bug
Below is an outline of the steps required to enable the GenPi64 image to boot on a Raspberry Pi 5.

To Reproduce
Steps to reproduce the behavior:
Mount a current GenPi64 image as chroot, also mount the /boot partition. Enter the chroot.

• edit /etc/portage/repos.conf/genpi64.conf and change the line:

sync-git-clone-extra-opts = -single-branch branch master 

to read:

sync-git-clone-extra-opts = -single-branch -branch rpi5-kernel

• If you are starting with a fresh image the repositories are empty to save space. So sync the genpi64 repository with the command:
  emaint -r genpi64 sync

after making the edit above.

If you have already synced the repositories I think it is necessary to delete everything under /var/db/repos/genpi64 and use the command above to resync the repository based on the rpi5-kernel branch.

• create dist-kernel-6.1.63.ebuild by copying and renaming the latest version
• Create the manifest for the 6.1.63 kernel:
  ebuild raspberrypi-kernel-6.1.63.ebuild manifest
• Create /etc/portage/package.unmask directory
• Create a file in the above directory containing the line below to unmask the virtual file
  =virtual/dist-kernel-6.1.63
• Create a file in /etc/portage/package.keywords containing the lines below to unmask the updated kernel
  sys-kernel/raspberrypi-kernel ~arm64
  virtual/dist-kernel-6.1.63 ~arm64
• These steps should now allow you to emerge the 6.1.63 kernel
  emerge -avu —-ignore-default-opts sys-kernel/raspberrypi-kernel
  A few hours later you should have the 6.1.63 kernel installed
• The edit the /boot/config.txt file and add the following lines
  [pi5]
  kernel=kernel8-p4.img
  dtoverlay=vc4-kms-v3d-pi5
  max_framebuffers=2

Expected behavior
Updated image should boot on a RPi 5

Describe the bug
I have installed =sys-kernel/raspberrypi-kernel-5.10.2 using binaries but uname -r returns me 5.10.0-rc5-v8 and modules are installed in /lib/modules/5.10.0-rc5-v8 folder.

To Reproduce
Steps to reproduce the behavior:

1. Run sudo emerge -va sys-kernel/raspberrypi-kernel with the following use flag bcm2711 bcmrpi3 -bcm2709 -bcmrpi -debug -initramfs -savedconfig -test

Expected behavior
Kernel 5.10.2 installed, uname -r showing 5.10.2 and modules installed inside /lib/modules/5.10.2 folder.

Image details (please complete the following information):

• Version used: migrated from sakaki installation

Thanks ENx

Current version is 0.25.
Latest release is https://github.com/ponylang/ponyc/releases/tag/0.47.0

However, this doesn't appear to have anything to do with raspberry pi, so I lean more toward deleting it entirely.

A precursory glance at the rpi-imager github page https://github.com/raspberrypi/rpi-imager shows that we need to list deps for qt related packages, and we currently do not.

Looks like that tool needs an overhaul for latest firmware

Describe the bug
emerge of sys-kernel/raspberrypi-kernel failed at install phase

To Reproduce
Steps to reproduce the behavior:

1. emerge sys-kernel/raspberrypi-kernel

Expected behavior
emerge should be OK

Additional context
emerge failed with:

Release file /var/tmp/portage/sys-kernel/raspberrypi-kernel-5.10.11/image/usr/src/linux-5.10.11/include/config/kernel.release not installed!

Describe the bug

Since a few days I am getting a package conflict when trying to run emerge -uDN world:

[blocks B ] media-libs/raspberrypi-userland ("media-libs/raspberrypi-userland" is soft blocking dev-embedded/raspberrypi-utils-0_p20240203)

(media-libs/raspberrypi-userland-0_pre20201022:0/0::gentoo, ebuild scheduled for merge) pulled in by
media-libs/raspberrypi-userland required by @Profile

(dev-embedded/raspberrypi-utils-0_p20240203:0/0::gentoo, installed) pulled in by
dev-embedded/raspberrypi-utils required by (dev-embedded/rpi-eeprom-21.0_p1:0/0::gentoo, installed) USE="pi4 -pi5" PYTHON_TARGETS="python3_11 -python3_10 -python3_12"
dev-embedded/raspberrypi-utils required by @selected

media-libs/raspberrypi-userland is pulled in directly by the genpi64:default/linux/arm64/17.0/genpi64 profile. The profile also pulls in dev-embedded/rpi-eeprom, which needs dev-embedded/raspberrypi-utils, which depends on !media-libs/raspberrypi-userland.

To Reproduce

Sync genpi and the gentoo repository to current state.

Run emerge -uDNva world

Image details (please complete the following information):

genpi64-overlay commit: eadbc9b
main gentoo repo commit: bc9bfd98746afe73d7df5190574b402b5220025f

Additional context

Did I miss some instructions to switch to a different profile?

My workaround is to remove media-libs/raspberrypi-userland from profiles/targets/genpi64/packages. No idea what exactly it provides, but my RPI mostly serves as a nextcloud and samba server.

Describe the bug
emerge of sys-firmware/bcm4340a1-firmware is failed

To Reproduce
Steps to reproduce the behavior:

1. emerge sys-firmware/bcm4340a1-firmware

Expected behavior
emerge should be OK

Additional context
emerge failed with

FileNotFoundError: [Errno 2] No such file or directory: b'BCM43430A1.hcd'

Upstream Raspberry Pi OS 64bit lite ships with Linux kernel 5.10.92

See release notes https://downloads.raspberrypi.org/raspios_arm64/release_notes.txt

rpi3-init-scripts-1.1.5-r3 causes X.org fail to start

rpi3-init-scripts-1.1.5-r3 seems to have a change that causes 50-hostname-mode-none.conf to get installed into /usr/share/X11/xorg.conf.d/, which then causes X.org to fail because this file does not belong in X.org's configuration folder.

The earlier versions of this package installed 50-hostname-mode-none.conf into /etc/NetworkManager/conf.d/, where it was supposed to go.

See upstream request for new release here: Plippo/twofing#14

As a result, we can drop our patch from the overlay.

Missing packages:

dev-embedded/rpi4-eeprom-updater
sys-apps/rpi3-expand-swap
sys-firmware/brcm43430-firmware
sys-boot/rpi3-64bit-firmware
dev-embedded/rpi4-eeprom-images

Installed only through binhost.
There is also a dependency problem, media-libs/raspberrypi-userland is not put, the problem is in the version name. The version is also installed only from binhost.
This is not very good.

The HomeAssistantRepository ( https://github.com/onkelbeh/HomeAssistantRepository ) has more actively maintained ebuilds for the colorzero, gpiozero, and rpi-gpio packages.

Arguably, since these originally were from the raspberry pi ecosystem, we should keep these packages. But we're doing our users a disservice by not keeping them updated.

We should either drop these ebuilds (my preference), or we should sync them with HomeAssistantRepository.

Alternatively, if git were to support some kind of sub-tree sub-module, that would work as well.

1. For some time (at least on version 5.10.x) default root filesystem for your kernels was btrfs. I flashed my boards around that time. Unfortunately for new releases (confirmed with raspberrypi-kernel-5.15.61) default filesystem is ext and btrfs as module which causes images built with sys-kernel/raspberrypi-kernel not boot at all on my boards. After I ctrl+z emerge and manually changed the config to include btrfs support compiled in instead of module those images boot fine on my boards
2. Second issue is that the port has a savedconfig use flag but unfortunately it's completely ignored :( The config is copied /etc/portage/savedconfig but it's overwritten in work directory during compilation with fresh one from fedora's repo
3. Couldn't you add something like "menuconfig" use flag so people could adjust kernel components during emerge process? I understand that something similar could be achieved with "savedconfig" use flag (once it's fixed of course :)) however adjusting config is often more complicated than changing m->y ;) Having full menuconfig with all it docs, dependencies etc. at hand could be useful :) Of course I understand that's possible to have custom build directory when you can do menuconfig and then just copy it to /etc/portage/savedconfig/sys-kernel/ . Nevertheless having it as part of ebuild makes it more user friendly IMHO.
   Hope this helps :)

• ERROR: media-video/smtube-19.6.0-r1::genpi64 failed (depend phase):
• l10n.eclass could not be found by inherit()
• Call stack:

•             ebuild.sh, line 657:  Called source '/home/jonesmz/genpi64-overlay/media-video/smtube/smtube-19.6.0-r1.ebuild'
  

• smtube-19.6.0-r1.ebuild, line 8: Called inherit 'desktop' 'l10n' 'qmake-utils'

•             ebuild.sh, line 303:  Called die
  

• The specific snippet of code:

•          [[ -z ${location} ]] && die "${1}.eclass could not be found by inherit()"
  

• If you need support, post the output of emerge --info '=media-video/smtube-19.6.0-r1::genpi64',
• the complete build log and the output of emerge -pqv '=media-video/smtube-19.6.0-r1::genpi64'.
• Working directory: '/usr/lib/python3.9/site-packages'
• S: '/var/tmp/portage/media-video/smtube-19.6.0-r1/work/smtube-19.6.0'
• ERROR: media-video/smtube-20.1.0::genpi64 failed (depend phase):
• l10n.eclass could not be found by inherit()
• Call stack:

•          ebuild.sh, line 657:  Called source '/home/jonesmz/genpi64-overlay/media-video/smtube/smtube-20.1.0.ebuild'
  

• smtube-20.1.0.ebuild, line 8: Called inherit 'desktop' 'l10n' 'qmake-utils'

•          ebuild.sh, line 303:  Called die
  

• The specific snippet of code:

•          [[ -z ${location} ]] && die "${1}.eclass could not be found by inherit()"
  

• If you need support, post the output of emerge --info '=media-video/smtube-20.1.0::genpi64',
• the complete build log and the output of emerge -pqv '=media-video/smtube-20.1.0::genpi64'.
• Working directory: '/usr/lib/python3.9/site-packages'
• S: '/var/tmp/portage/media-video/smtube-20.1.0/work/smtube-20.1.0'

See https://github.com/RPi-Distro/bluez-firmware/tree/master/broadcom for the associated firmware file(s)

Copyright from 2019.
Out of date?

In-overlay version of xfce4-battery-plugin is out of date compared to gentoo, but we carry a patch for the pitop. So a revbump is needed.

Otherwise every time we install the raspberrypi-kernel package, it pulls in the gentoo-kernel package, and compiles and installs it.

Current ebuild is v1.6.
Latest is https://github.com/raspberrypi/rpi-imager/releases/tag/v1.7.1

At the moment, when updating, an error pops up:

Calculating dependencies | * ERROR: sys-kernel/raspberrypi-kernel-5.10.11::genpi64 failed (depend phase):
 *   Invalid implementation in PYTHON_COMPAT: python3_10
...
...

Maybe you should remove python-utils-r1.eclass from the overlay and use it from Gentoo?

• ERROR: app-accessibility/onboard-1.4.1-r1::genpi64 failed (depend phase):
• No supported implementation in PYTHON_COMPAT.
• Call stack:

•             ebuild.sh, line 657:  Called source '/home/jonesmz/genpi64-overlay/app-accessibility/onboard/onboard-1.4.1-r1.ebuild'
  

• onboard-1.4.1-r1.ebuild, line 9: Called inherit 'distutils-r1' 'gnome2-utils' 'versionator'

•             ebuild.sh, line 337:  Called __qa_source '/var/db/repos/gentoo/eclass/distutils-r1.eclass'
  

•             ebuild.sh, line 114:  Called source '/var/db/repos/gentoo/eclass/distutils-r1.eclass'
  

•   distutils-r1.eclass, line 105:  Called inherit 'python-r1'
  

•             ebuild.sh, line 337:  Called __qa_source '/var/db/repos/gentoo/eclass/python-r1.eclass'
  

•             ebuild.sh, line 114:  Called source '/var/db/repos/gentoo/eclass/python-r1.eclass'
  

•      python-r1.eclass, line 250:  Called _python_set_globals
  

•      python-r1.eclass, line 198:  Called _python_set_impls
  

• python-utils-r1.eclass, line 159: Called die
• The specific snippet of code:

•  	                die "No supported implementation in PYTHON_COMPAT."
  

• If you need support, post the output of emerge --info '=app-accessibility/onboard-1.4.1-r1::genpi64',
• the complete build log and the output of emerge -pqv '=app-accessibility/onboard-1.4.1-r1::genpi64'.
• Working directory: '/usr/lib/python3.9/site-packages'
• S: '/var/tmp/portage/app-accessibility/onboard-1.4.1-r1/work/onboard-1.4.1'
  !!! getFetchMap(): aux_get() error reading app-accessibility/onboard-1.4.1-r1; aborting.
  !!! Unable to generate manifest for '/home/jonesmz/genpi64-overlay/app-accessibility/onboard'.

/var/db/repos/genpi64/profiles/targets/genpi64desktop/make.defaults
add "gtk xft" to USE=.

/etc/portage/package.accept_keyword
add
sys-apps/pyconfig_gen
x11-misc/rpi3-safecompositor
x11-misc/rpi3-safecursor
x11-apps/xdm
x11-apps/xconsole
x11-misc/arandr
dev-python/PyQt-builder

rpi3-bluetooth apparently just has a modified udev rule.

Is this still needed? Surely upstream udev has this in their database by now?

We currently have sys-apps/repoman in the default package set (

As per https://bugs.gentoo.org/835013 and current Gentoo mask file https://github.com/gentoo/gentoo/blob/b8ce8a793839b5a2c13c785da5c6d727625db3e0/profiles/package.mask#L46 , the package has been masked with the recommendation to replace it with dev-util/pkgcheck and dev-util/pkgdev instead.

Since the go-live of the package.mask file and sys-apps/portage being updated to >=3.0.31 (current stable 3.0.36), GenPi64 packages file creates a blockage for genpi upgrades.

Bug title is "remove" but maybe it could be replaced with pkccheck and pkgdev. I leave the decision to a discussion and could make the easy corresponding pull request.

TIA

I'm fairly certain that this is the repository that contains the image builder for raspberry pi os, including the 64bit image that was recently released with support for the rpi 0 w 2.

https://github.com/RPi-Distro/pi-gen

We should use their kernel configuration, instead of fedora's, as the baseline for our kernel builds.

PYTHON_TARGETS="-python3_10"isn't working no more.
Thankz
Jeff

Question

I am running a custom build of Kinvolks Flatcar Container Linux with some adjustments to https://github.com/kinvolk/coreos-overlay and containing the following:

• Enabled CONFIG_GPIO_SYSFS kernel option, so that /sys/class/gpio/... is present, and /dev/gpiomem is present
• Add pigpio (with some fixes to make it work on Flatcar)

When starting pigpiod, I am getting errors similar to joan2937/pigpio#461 saying that I can not open a messagebox (mbox). The command sudo modprobe vcio fails, as the module is not present on the machine. I assume, that I have to add an ebuild or two, but can not figure out which ones to add.

At this stage I am just guessing and could use some guidance. This repository somehow got pigpio working on gentoo and I was wondering, what it took to do so? My next guess would be to add raspberrypi-userland but this seems not be part of this repository anymore, so any ideas or any help is welcome.

Describe the bug

www-client/chromium/chromium-70.0.3538.110-r2.ebuild is giving me an error about "EAPI=6" is not supported when I run emerge to update my system:

• ERROR: www-client/chromium-70.0.3538.110-r2::genpi64 failed (depend phase):
• EAPI=6 is not supported
• Call stack:

•                      ebuild.sh, line 645:  Called source '/var/db/repos/genpi64/www-client/chromium/chromium-70.0.3538.110-r2.ebuild'
  

This is a really old package, maybe it should just be removed from the repo.

I don't know if the rest of the ebuilds using EAPI=6 need work, they don't seem to be causing me an error message in emerge at the moment.

To Reproduce
Steps to reproduce the behavior:

1. sync repos:
   sudo emerge --sync --nospinner --ask
2. update system:
   sudo emerge --update @System --newuse --deep --with-bdeps=y --verbose --verbose-conflicts --nospinner --ask
3. See error

Expected behavior

emerge should work without throwing the error message.

Image details (please complete the following information):

• Version used: sakaki's last image, upgraded through time...

• ERROR: net-misc/wsdd-0.3::genpi64 failed (depend phase):
• No supported implementation in PYTHON_COMPAT.
• Call stack:

•            ebuild.sh, line 657:  Called source '/home/jonesmz/genpi64-overlay/net-misc/wsdd/wsdd-0.3.ebuild'
  

•      wsdd-0.3.ebuild, line   8:  Called inherit 'python-r1' 'systemd'
  

•            ebuild.sh, line 337:  Called __qa_source '/var/db/repos/gentoo/eclass/python-r1.eclass'
  

•            ebuild.sh, line 114:  Called source '/var/db/repos/gentoo/eclass/python-r1.eclass'
  

•     python-r1.eclass, line 250:  Called _python_set_globals
  

•     python-r1.eclass, line 198:  Called _python_set_impls
  

• python-utils-r1.eclass, line 159: Called die
• The specific snippet of code:

•  	                die "No supported implementation in PYTHON_COMPAT."
  

• If you need support, post the output of emerge --info '=net-misc/wsdd-0.3::genpi64',
• the complete build log and the output of emerge -pqv '=net-misc/wsdd-0.3::genpi64'.
• Working directory: '/usr/lib/python3.9/site-packages'
• S: '/var/tmp/portage/net-misc/wsdd-0.3/work/wsdd-0.3'

Also, this package is extremely out of date. Either we should version bump it to 0.7.0, or we should drop it entirely.

I'm sure that the package author at this overlay (https://github.com/christgau/wsdd-gentoo) would be willing to adopt any necessary rpi compatibility patches

E.g. the below are in need of fixing.

GenPi64 ~ # equery u raspberrypi-kernel
[ Legend : U - final flag setting for installation]
[        : I - package is installed with flag     ]
[ Colors : set, unset                             ]
 * Found these USE flags for sys-kernel/raspberrypi-kernel-5.10.90:
 U I
 - - bcm2709     : <unknown>
 + - bcm2711     : <unknown>
 - - bcmrpi      : <unknown>
 + - bcmrpi3     : <unknown>
 - - debug       : Enable extra debug codepaths, like asserts and extra output. If you want to get meaningful backtraces see https://wiki.gentoo.org/wiki/Project:Quality_Assurance/Backtraces
 - - initramfs   : <unknown>
 - - savedconfig : Use this to restore your config from /etc/portage/savedconfig ${CATEGORY}/${PN}. Make sure your USE flags allow for appropriate dependencies
 - - test        : Enable dependencies and/or preparations necessary to run tests (usually controlled by FEATURES=test but can be toggled independently)

see upstream changelog https://sourceforge.net/p/raspberry-gpio-python/code/ci/default/tree/CHANGELOG.txt

see forum discussion about official kernel being updated

https://forums.raspberrypi.com/viewtopic.php?t=322879

Describe the bug
Enabling VC4 support causes both versions 2.0.12-r2 and 2.0.14-r1 to fail with a compiler error

To Reproduce
Steps to reproduce the behavior:

1. Burn alpha6 image to SD card. Fix config.txt to point to correct kernel image.
2. Sync portage and add VIDEO_CARDS="vc4" to make.conf
3. emerge --deep --newuse --update libsdl2

Expected behavior
successful install of libsdl2

Additional context

Confirmed by two others in the Discord. One was able to get 2.0.14-r1 working using a patch from https://bugs.gentoo.org/741490
Recommended to add this patch to the ebuilds until upstream fixes the issue

This package appears to exist only to work around a bug with xfce.

Do newer versions of xfce4 no longer have this bug?