Jump to content

cardinal

Members
  • Content Count

    398
  • Joined

  • Last visited

  • Days Won

    52

cardinal last won the day on September 3

cardinal had the most liked content!

6 Followers

About cardinal

  • Rank
    Advanced Member

Recent Profile Visitors

3,160 profile views
  1. emerge --info Read the output to verify python3_6 is not included in the USE flag variables PYTHON_SINGLE_TARGET or PYTHON_TARGETS This is what I have on my system with no python3_6 installed. PYTHON_SINGLE_TARGET="python3_7" PYTHON_TARGETS="python3_7 python2_7" If you see python3_6 then you have set an override for it in /etc/portage/repos.conf or some other location that needs to be removed. After you remove without rebooting ego sync followed by emerge -avuDN @world will trigger a rebuild of any modules that were built against python3_6 to be rebuilt against python3_7 if it's supported. If you have modules only supported by python3_6 you will either remove the modules and python3_6 or leave both installed.
  2. Bug Report: https://bugs.funtoo.org/browse/FL-7460 This is assigned to a contributor to be fixed, but it hasn't been updated for 10 days. Click the bug report link, login to bugs.funtoo.org, upper right under People click Vote for this issue and Start watching this issue.
  3. drobbins removed rust-kit but didn't move all the packages it contained to lang-kit. I created a bug report referencing this forum thread: https://bugs.funtoo.org/browse/FL-7479
  4. Not a bug, portage on my system can see /var/git/meta-repo/kits/rust-kit/virtual/cargo rj@funtoo ~ $ ego query v virtual/cargo virtual/cargo| slot| repo --------------+-----+-------------------- * 1.37.0| 0| rust-kit/1.37-prime rj@funtoo ~ $ ego query v librsvg gnome-base/librsvg| slot| repo -------------------+-----+--------------------- * 2.46.4-r1| 2| gnome-kit/3.36-prime 2.48.4| | gnome-kit/3.36-prime rj@funtoo ~ $ equery g librsvg-2.46.4-r1 | grep cargo [ 1] virtual/cargo-1.37.0 rj@funtoo ~ $ equery g librsvg-2.48.4 | grep cargo [ 1] virtual/cargo-1.37.0
  5. There are at least three possible reasons xauth can't create ~/.Xauthority and xorg-server can't create /tmp/.X0-lock 1. The partition{s} containing /tmp and /home are mounted read-only. 2. The partition{s} containing /tmp and /home have no free space. 3. The permissions are wrong and too restrictive for /tmp and ~/ Footnote: ~/ is an abbreviation for /home/<your regular users name here> you are currently logged into.
  6. Search /var/log/messages and /var/log/sddm.log for error messages related to your problem. Reference: https://bugs.gentoo.org/728550 - sys-libs/pam-1.4.0-r1 breaks kde-plasma/kwallet-pam-5.19.1 auto unlock of wallet during login problem starts with the newer version of pam that is not in funtoo's portage yet.
  7. The partition{s} for the root filesystem / and /home must be mounted read/write, yours appear to be mounted read only. Check /etc/fstab and remove a ro option if it exists. The /etc/fstab for mounting the partition for / on my funtoo install: UUID=8c41a40b-5166-4c6c-9819-0713ffca423d / ext4 noatime 0 1 Funtoo is installed on my system on one partition /dev/sda9 and it is rw rj@funtoo ~ $ mount /dev/sda9 on / type ext4 (rw,noatime)
  8. The problem your having is not a bug but an issue with your install. I am attaching my build log in case it may provide a clue to the origin of the problem on your system. sys-kernel:debian-sources-lts-4.19.132_p1:20200916-235334.log.xz
  9. There is no bug report about the failure to mv/rename all the files in /boot by appending their existing names with -debian-sources or -debian-sources-lts You could either go to the root of the file system and extract the ./boot directory which contains the kernel,initramfs,and SystemMap files from the stage3 tarball or copy them from /var/tmp/portage/sys-kernel/debian-sources-lts-4.19.132_p1/image.
  10. drobbins announced End Of Life on March 1, 2020 for 1.3-release. drobbins removed the libvpx mask from funtoo-cautionary. Now that media-kit/1.4-release/media-libs/libvpx-1.9.0 is unmasked you should be able to install mate after you remove/revert any configurations you made that may cause a block or conflict and set the mate mix-ins. These outputs are from my system: emerge -pv mate emerge --info epro list ego kit
  11. https://bugs.funtoo.org/browse/FL-6561 >=libvpx-1.8.0 globally masked you could disable vpx use flag globally in /etc/portage/make.conf to eliminate any need for libvpx. I need vpx for ffmpeg and it was preventing the x265 update. I comment out the mask which is temporary which allowed the update to proceed. rj@funtoo /var/git/meta-repo/kits/core-kit/profiles/package.mask $ sudo nano funtoo-cautionary # Allow firefox to merge cleanly #>=media-libs/libvpx-1.8 You could also add the libvpx-1.7.0.ebuild from the 1.3-release branch to a local overlay.
  12. Remove MAKEOPTS="-j13" from /etc/portage/make.conf, try building with MAKEOPTS="-j2" I was able to build dev-lang/spidermonkey-60.5.2_p0-r3 on my core2duo system, build log is attached.dev-lang:spidermonkey-60.5.2_p0-r3:20200827-140855.log.xz
  13. Fixed: https://bugs.funtoo.org/browse/FL-7392 Sync and update.
  14. An issue report at bugs.funtoo.org is needed. libffado-2.4.1 pulled in by jack2 with ieee1394 use flag requires libxmlpp-2.40.1 that is designated to slot 2.6 (dev-cpp/libxmlpp:2.6) libxmlpp-3.0.1-r1 the only version available in funtoo is designated to slot 3.0 (SLOT="3.0") A temporary workaround is to disable ieee1394 for jack2
  15. From the most recent entry in the change log which is for 5.0 We replaced the default Window Manager from LxQT to LXDE + openbox
×
×
  • Create New...