Jump to content

cardinal

Members
  • Content Count

    424
  • Joined

  • Last visited

  • Days Won

    53

Everything posted by cardinal

  1. 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/bro
  2. I was able to build media-libs/gst-plugins-base-1.14.4-r1 Your 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-r1 The en
  3. 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 dev-java:oracle-java
  4. Reverse the changes gentoo made in the gpsd-3.20.ebuild and gpsd-999.ebuild for acct-user/gpsd: migrating from user.eclass https://gitweb.gentoo.org/repo/gentoo.git/commit/sci-geosciences/gpsd?id=52d0dd930929ebc49804bd4a8ecfe674e8cff3cc The other alternative is to add the acct-user.eclass and acct-user/gpsd/gpsd-0-r1.ebuild to the overlay.
  5. Try replacing UUID with PARTUUID=71e22c3d-02 which is not changing.
  6. 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.
  7. 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. f
  8. 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
  9. 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:*
  10. 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.pickle a 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
  11. 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 KiB If you don't designate the version number and there are multiple versions the greatest unmasked version is built. c
  12. 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 templates Rerun emerge update to build cmake-3.19.5 Follow it up with a package.mask, otherwise next sync cmake-3.20.0-rc1.ebuild reap
  13. 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.
  14. 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 sync If 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.
  15. 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/kwayland Remove 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
  16. Bug Report: app-crypt/qca missing from portage
  17. Reverse x11-misc/sddm elogind here: /var/git/meta-repo/kits/core-kit/profiles/funtoo/1.0/linux-gnu/flavor/workstation/package.use.mask by adding x11-misc/sddm -elogind to /etc/portage/profile/package.use.mask
  18. Does emerge --info | grep 'L10N="fr"' highlight the output L10N="fr" in red?
  19. Did you build and install app-office/libreoffice-l10n with L10N="fr" variable set ? equery u libreoffice-l10n You should have a + in both columns to the left of l10n_fr
  20. Add the attached boost-1.72.build.fix.patch to /etc/portage/patches/media-video/mkvtoolnix boost-1.72.build.fix.patch
  21. Having cmake auto-update to the newest version is going to break building older packages. This is the case with cmake-3.18.4 failing to build grantlee-5.1.0. If you add grantlee-5.2.0 in your local overlay it will build with cmake-3.18.4. Bug report: Auto-updated cmake-3.18.4 breaks grantlee-5.1.0 build
×
×
  • Create New...