cardinal
-
Posts
490 -
Joined
-
Last visited
-
Days Won
59
Content Type
Profiles
Forums
Blogs
Posts posted by cardinal
-
-
LUKS encrypted root filesystems can not be unlocked on boot.
https://bugs.funtoo.org/browse/FL-8318
https://gesis.pw/encrypted-rootfs-on-funtoo-linux-1-4/
-
https://bugs.funtoo.org/browse/FL-8443
media-tv/plex-media-server-1.23.1.4571 fails to update
-
I'm running an older version of debian-sources-lts.
No modification of the kernel configuration.
Genkernel builds the initramfs so it includes mptfc and autoloads it on boot.
rj@funtoo ~ $ modinfo mptfc filename: /lib/modules/4.19.152_p1-debian-sources-lts/kernel/drivers/message/fusion/mptfc.ko version: 3.04.20 license: GPL description: Fusion MPT FC Host driver author: LSI Corporation srcversion: 2043697964B5896B7AB7B54 alias: pci:v00001657d00000646sv*sd*bc*sc*i* alias: pci:v00001000d00000646sv*sd*bc*sc*i* alias: pci:v00001000d00000640sv*sd*bc*sc*i* alias: pci:v00001000d00000642sv*sd*bc*sc*i* alias: pci:v00001000d00000626sv*sd*bc*sc*i* alias: pci:v00001000d00000628sv*sd*bc*sc*i* alias: pci:v00001000d00000622sv*sd*bc*sc*i* alias: pci:v00001000d00000624sv*sd*bc*sc*i* alias: pci:v00001000d00000621sv*sd*bc*sc*i* depends: mptscsih,scsi_transport_fc,mptbase,scsi_mod retpoline: Y intree: Y name: mptfc vermagic: 4.19.152_p1-debian-sources-lts SMP mod_unload modversions parm: mptfc_dev_loss_tmo: Initial time the driver programs the transport to wait for an rport to return following a device loss event. Default=60. (int) parm: max_lun: max lun, default=16895 (int)rj@funtoo ~ $ lsmod | grep mptfc mptfc 20480 0 scsi_transport_fc 69632 3 lpfc,qla2xxx,mptfc mptscsih 32768 3 mptsas,mptspi,mptfc mptbase 81920 4 mptsas,mptspi,mptfc,mptscsih scsi_mod 245760 41 gdth,arcmsr,megaraid_mbox,mptsas,3w_sas,aic94xx,lpfc,aacraid,mptspi,virtio_scsi,atp870u,aic79xx,scsi_transport_sas,aic7xxx,sd_mod,raid_class,scsi_transport_spi,megaraid,scsi_transport_iscsi,qla2xxx,initio,3w_xxxx,BusLogic,scsi_transport_fc,usb_storage,mptfc,iscsi_tcp,hpsa,qla1280,mptscsih,sym53c8xx,libsas,libiscsi,megaraid_sas,libata,sg,dc395x,dmx3191d,3w_9xxx,sr_mod,mpt3sas -
Reference /var/lib/portage/preserved_libs_registry or the output from "
portageq list_preserved_libs /"Examine the list, it's possible more than one package could be linked to the same preserved lib.
Move or rename the preserved libs rather than deleting.
Use revdep-rebuild to install the updated lib package if needed and rebuild/link target packages previously linked to the now hidden preserved libs.
Repeat until all packages are linked to the updated installed libs.
-
kde-kit/kde-misc/kio-locate/kio-locate-0.5.3-r1 from kde-kit/5.19-release branch builds on my updated amd64 system.
Run these commands as root user:
funtoo /home/rj # cd /var/git/meta-repo/kits/kde-kit funtoo /var/git/meta-repo/kits/kde-kit # git checkout 5.19-release funtoo /var/git/meta-repo/kits/kde-kit # emerge -av =kde-misc/kio-locate-0.5.3-r1 funtoo /var/git/meta-repo/kits/kde-kit # git checkout 5.20-release funtoo /var/git/meta-repo/kits/kde-kit # echo ">kde-misc/kio-locate-0.5.3-r1" > /etc/portage/package.mask/kio-locate
Bug report: https://bugs.funtoo.org/browse/FL-8344
-
I was able to build
media-libs/gst-plugins-base-1.14.4-r1Your system has 2 versions of binutils .
While binutils is slotted which allows multiple versions installed at the same time, it's dependency binutils-libs is not slotted.
The installed binutils version must match binutils-libs version.
You have the old version of binutils-libs but your system is using the new version of binutils.
sys-devel/binutils: 2.32-r1::core-kit, 2.36.1-r1::core-kit
Verify install or upgrade to binutils-libs-2.36.1-r1
emerge -1av =sys-libs/binutils-libs-2.36.1-r1The end result is to only have binutils-2.36-r1 and binutils-libs-2.36-r1 on your system.
Then try using --depclean first, or if necessary -Ca to remove the old version binutils-2.32-r1
My system:
rj@funtoo ~ $ ego query v binutils
sys-devel/binutils | slot| repo
-----------------------+---------+---------------------
2.32-r1| 0/2.32| core-kit/1.4-release
-----------------------+---------+---------------------
* 2.36.1-r1| 0/2.36.1| core-kit/1.4-release
rj@funtoo ~ $ ego query v binutils-libs
sys-libs/binutils-libs| slot| repo
-----------------------+---------+---------------------
2.32-r1| 0/2.32| core-kit/1.4-release
-----------------------+---------+---------------------
* 2.36.1-r1| 0/2.36.1| core-kit/1.4-releaserj@funtoo ~ $ emerge --info | grep binutils
sys-devel/binutils: 2.36.1-r1::core-kit -
Confirm emerge failure oracle-javamail-1.5.6
Install dev-java/javatoolkit-0.6.5.ebuild and dev-java/oracle-javamail-1.5.6-r1.ebuild from gentoo in your local overlay solves the issue.
In the process of building jedit-5.4.0 and its depends jython-2.7.0-r2 emerge failed.
Emerged jython by going to Bug 758881 - dev-java/jython-2.7.0-r2 AttributeError: 'NoneType' object has no attribute 'startswith' apply jython-2.7.0-r2.ebuild.patch regenerate manifest.
dev-java:jython-2.7.0-r2:20210319-042623.log dev-java:jython-2.7.0-r2:20210319-025110.log
-
Reverse the changes gentoo made in the gpsd-3.20.ebuild and gpsd-999.ebuild for acct-user/gpsd: migrating from user.eclass
The other alternative is to add the acct-user.eclass and acct-user/gpsd/gpsd-0-r1.ebuild to the overlay.
-
Try replacing UUID with PARTUUID=71e22c3d-02 which is not changing.
-
https://bugs.funtoo.org/browse/FL-8123
FL-8123: Remove patches merged upstream in sys-devel/distcc.
The source prepare patch failure that was stopping the emerge for distcc-3.3.5 was fixed by removing the eapply patch commands for the failing patches from the ebuild.
-
The patches need to be updated for distcc-3.3.5.ebuild
My workaround for failed updates is git revert the commit to the prior version distcc-3.3.3.ebuild
After successfully emerging distcc-3.3.3 mask it until the patches are fixed and distcc-3.3.5 will build.
funtoo /var/git/meta-repo/kits/core-kit # git log --all --full-history -- "*distcc*.*" Checkout the 2nd commit in the result to restore distcc-3.3.3.ebuild funtoo /var/git/meta-repo/kits/core-kit # git checkout 8d890 funtoo /var/git/meta-repo/kits/core-kit # emerge -av distcc Mask distcc-3.3.5 from update until it's fixed. funtoo /var/git/meta-repo/kits/core-kit # echo ">sys-devel/distcc-3.3.3" >> /etc/portage/package.mask/distcc Change core-kit back to head. funtoo /var/git/meta-repo/kits/core-kit # git checkout 1.4-releaseBug report:
Autogened sys-libs/distcc-3.3.5 update patch fails prepare
-
Libreoffice{-bin} needs qt5
Openoffice-bin no qt5.
Openoffice-bin on funtoo requires configuring a local overlay,adding sys-libs/ncurses-compat-6.2 from gentoo, installing layman, enabling guru overlay for openoffice-bin-4.1.9
Bug report:
Emerge for Openoffice-bin-4.1.6 depends on removed ncurses:5
-
Use libreoffice-bin instead.
-
Exclude doesn't allow = or - in package name.
category/ is optional
emerge -avuDN @world --exclude qtcore emerge -avuDN @world --exclude dev-qt/qtcore emerge -avuDN @world --exclude qtcore:5.15.2 emerge -avuDN @world --exclude dev-qt/qtcore:5.15.2 emerge -avuDN @world --exclude qtcore:* emerge -avuDN @world --exclude dev-qt/qtcore:* -
Portage builds the packages in a sandbox to prevent the process from writing or modifying files on your running system.
Emerge tried to open_write to
/usr/lib/python3.7/lib2to3/Grammar3.7.7.final.0.picklea file owned by dev-lang/python.
A workaround is to disable the sandbox and build the package:
funtoo /home/rj # FEATURES="-sandbox -usersandbox" emerge -1av dev-python/setuptools -
If you designate a version number after the package name you have to start with =
=category/package-version
funtoo /home/rj # emerge -pv =dev-python/setuptools-53.0.0 These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild R ] dev-python/setuptools-53.0.0::python-modules-kit USE="-test" PYTHON_TARGETS="python2_7 python3_7 -pypy3 -python3_8 -python3_9" 0 KiB Total: 1 package (1 reinstall), Size of downloads: 0 KiBIf you don't designate the version number and there are multiple versions the greatest unmasked version is built.
category/package
There is only one dev-python/setuptools , there is no reason to designate the version
funtoo /home/rj # ego query v setuptools dev-python/setuptools| slot| repo ----------------------+-----+------------------------------- * 53.0.0| 0| python-modules-kit/1.4-release funtoo /home/rj # emerge -pv dev-python/setuptools These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild R ] dev-python/setuptools-53.0.0::python-modules-kit USE="-test" PYTHON_TARGETS="python2_7 python3_7 -pypy3 -python3_8 -python3_9" 0 KiB Total: 1 package (1 reinstall), Size of downloads: 0 KiB -
A workaround is to use git to checkout the previous commit in core-kit which restores cmake-3.19.5.ebuild
rj@funtoo ~ $ cd /var/git/meta-repo/kits/core-kit funtoo /var/git/meta-repo/kits/core-kit # ls dev-util/cmake/ Manifest autogen.py cmake-3.20.0-rc1.ebuild files templates funtoo /var/git/meta-repo/kits/core-kit # git checkout HEAD~1 funtoo /var/git/meta-repo/kits/core-kit # ls dev-util/cmake/ Manifest autogen.py cmake-3.19.5.ebuild files templatesRerun emerge update to build cmake-3.19.5
Follow it up with a package.mask, otherwise next sync cmake-3.20.0-rc1.ebuild reappears and you'll be nagged with same error.
funtoo /var/git/meta-repo/kits/core-kit # echo ">dev-util/cmake-3.19.5" >> /etc/portage/package.mask/cmakeI mask cmake with my currently installed version to avoid problems due to untested cmake auto-updates.
Bug Report:
-
No difference, use the same command.
Chroot requires running as superuser root.
HOME=/root is an environmental variable which sets /root as the home directory for superuser root.
Just because /home is mounted on a different partition than the rest of the file tree doesn't change this fact.
-
-
-
Funtoo's freshest kde ebuilds are in kde-kit non-default 5.20-release branch for testing.
Manual override default branch for kde-kit and emerge.
funtoo /home/rj # ego config set kits kde-kit 5.20-release funtoo /home/rj # ego kit funtoo /home/rj # ego syncIf configured correctly:
Syncing kde-kit branch 5.20-release (non-default) Already on '5.20-release' Your branch is up to date with 'origin/5.20-release'. HEAD is now at 23455e77e Automated updates by metatools for md5-cache and python profile settings. Already up to date. -
-
Kwayland-5.57.0 or kwayland-5.59.0 will build against Qt-5.15.2 with the attached kwayland-5.59-qt-5.15.2.patch installed to local patches.
funtoo /home/rj # mkdir -p /etc/portage/patches/kde-frameworks/kwayland funtoo /home/rj # cp kwayland-5.59.0-qt-5.15.2.patch /etc/portage/patches/kde-frameworks/kwaylandRemove the patch when kwayland is upgraded or patch will fail and stop emerge.
kwayland-5.59.0-qt-5.15.2.patch
Reference: kwayland-5.59.0 build fails with QHash error
-
Installing Funtoo bootloader problem
in Installation Help
Posted
You're multi-booting, booted into arch linux with grub2 already installed, installing funtoo on another partition or partition/drive on the same computer?
Boot update only works if you have funtoo installed as the first linux os on the drive and it was used to install grub2.