fem-overlay - News Dashboard

femxen-kernel problem with partuuid in grub config

Posted: 2025-05-07 by Timo Kettenbach
Starting with grub-2.04, a new option GRUB_DISABLE_LINUX_PARTUUID was added and defaulted to 'true'. The maintainers of sys-boot/grub::gentoo have decided to set this option to 'false' with recent config updates.

Beginning with femxen-kernel-6.6.74 this configuration can lead to the system being unbootable. To prevent this please comment the following line in /etc/default/grub:


 GRUB_DISABLE_LINUX_PARTUUID=false

And instead uncomment the following line:


 GRUB_DISABLE_LINUX_UUID=true

gst-plugins-bad splits off fdkaac plugin

Posted: 2022-04-24 by Adrian Schollmeyer
gst-plugins-bad was imported into the FeM Overlay to add support for the fdkaac plugin. In the Gentoo Bugzilla, Bug #837809 [1] has been opened, requesting addition of the fdkaac plugin. The maintainers have decided to make the fdkaac plugin available in a split package. As soon as the split package gets added to ::gentoo, the cleanup of gst-plugins-bad in the FeM Overlay shall start.

To ease with the transition, a split package media-plugins/gst-plugins-fdkaac has been created, which is equivalent to the package in the open pull request. The current revision of media-libs/gst-plugins-bad in the FeM Overlay pulls in media-plugins/gst-plugins-fdkaac conditionally if the fdk USE flag is present. However, to make sure the plugin doesn't get removed in the next deplean, users must add the package to the world set:


emerge --ask --noreplace media-plugins/gst-plugins-fdkaac

[1] https://bugs.gentoo.org/837809

fem-overlay moves to a new upstream repository

Posted: 2021-08-13 by Adrian Schollmeyer
The current FeM Bitbucket is being replaced with a GitLab instance. As such, the fem-overlay, whose upstream repository is currently located in the FeM Bitbucket [0], will also be moved to the GitLab instance.

The new repository is:
  • https://gitlab.fem-net.de/gentoo/fem-overlay.git


We will continue to mirror the fem-overlay to the old repository [0] until 2021-10-31. After that day, it is no longer guaranteed that the old repository will be up to date and it will be removed some time later. Furthermore, the SVN mirror [1] will also be disabled.

Depending on the overlay management tool being used (and if such a tool is being used at all), the repository URL in /etc/portage/repos.conf might have to be adjusted to match the new upstream URL. If in doubt, check /etc/portage/repos.conf for any occurences of the fem-overlay, e.g.:


$ grep -R fem-overlay /etc/portage/repos.conf

If a line pops up with the old upstream clone URL [2], edit the corresponding file and insert the new upstream URL instead. If a line pops up, containing the GitHub mirror URL [3], the system is not affected by this change and nothing needs to be done.

If the URL had to be changed in repos.conf, it has to be changed in the cloned repo as well. Assuming, the repository is cloned to /var/db/repos/fem-overlay, run the following:


# cd /var/db/repos/fem-overlay
# git remote set-url origin https://gitlab.fem-net.de/gentoo/fem-overlay.git

Alternatively, you can just remove the repository so that the repository is freshly cloned upon the next emerge --sync:


# rm -r /var/db/repos/fem-overlay

Afterwards syncing now fetches from the new upstream repository and further changes should not be necessary.

[0] https://bitbucket.fem.tu-ilmenau.de/projects/GENTOO/repos/fem-overlay/browse [1] http://subversion.fem.tu-ilmenau.de/repository/fem-overlay/trunk/ [2] https://bitbucket.fem.tu-ilmenau.de/scm/gentoo/fem-overlay.git [3] https://github.com/gentoo-mirror/fem-overlay.git

More... (Archive)