mauricev

If I am running a 32-bit Funtoo, do I need to do anything differently from the posted instructions to upgrade to 1.3? If I am running kdecore-meta and plasma-meta, do I need to only uninstall and reinstall X Window, or should I also uninstall and reinstall these packages too?

First, I can't report anything on bugs.funtoo.org because the login is rejecting me. Second, I got as far as emerge -av @preserved-rebuild, but it fails on compiling glib-2.58.1, but that fails with the complaint Program gdbus-codegen found: NO gio/meson.build:237:0: ERROR: Program(s) ['gdbus-codegen'] not found or not executable

How odd, I set fsid=0 as an option to the export line and now it works in the older gentoo kernel.

When I use debian-sources, I can mount the exported nfs share (nfs v3) on this system, but when I try to use a gentoo-sources I customized, I get this instead: mount.nfs: access denied by server while mounting zfs:/z/nfs In debugging, I get mount.nfs: mount(2): Permission denied So something has to be missing from my gentoo-sources, but I don't know what it can be. Everything seems to be in order according to exportfs and rpcinfo. More info, the log reveals [rpc.mountd] authenticated mount request from 127.0.0.1:836 for /z/nfs (/z/nfs) Aug 02 23:41:23 [rpc.mountd] Cannot export /z/nfs, possibly unsupported filesystem or fsid= required

The reason is explained here https://bugs.funtoo.org/browse/FL-5318?page=com.atlassian.jira.plugin.system.issuetabpanels%3Aall-tabpanel The profile overrules the make.conf

I have my use with -pam and I don't have pam installed. I have no idea why I would need so I don't have it. But suddenly portage insisting I get it. [ebuild N ] sys-libs/pam-1.3.0-r2::core-kit USE="cracklib filecaps nls pie -audit -berkdb -debug -nis (-selinux) {-test} -vim-syntax" ABI_X86="(64) -32 (-x32)" 1,754 KiB [ebuild N ] sys-auth/pambase-20150213-r3::core-kit USE="cracklib nullok sha512 -consolekit -debug -elogind -gnome-keyring -minimal -mktemp -pam_krb5 -pam_ssh -passwdqc -securetty (-selinux) -systemd" 4 KiB

I didn't get those warnings because when I built the digest I gave it the full path and when I attempted to emerge autossh, I just told it emerge -v autossh. I never referenced "cat" itself.

Ah, the word cat was not meant to be taken literally, but it refers to the category of the package, which, in this case, is net-misc. That fixed it. And, no, there were no warnings from emerge. Thanks!

/var/git/overlay └── local-overlay ├── COPYRIGHT.txt ├── LICENSE.txt ├── README.rst ├── cat │ └── autossh │ ├── Manifest │ ├── autossh-1.4f.ebuild │ └── metadata.xml ├── metadata │ └── layout.conf └── profiles └── repo_name

sudo: tree: command not found

That was a mistake, not the mistake. It still doesn't work.

Yes, I did that. But one thing that wasn't not stated in the docs is that path where the packages must reside. I would have never guessed it.

I want to use the latest version of autossh, which isn't yet in the portage tree. I followed the instructions at https://www.funtoo.org/Local_Overlay, but what are the next steps? Do I recreate the kits directory hierarchy in /var/git/overlay/local-overlay. ( I tried that and it had no effect.) My updated autossh ebuild is not being seen.

4.15.17-1 https://pastebin.com/zK629ztL

On a system I built with KDE-plasma, I notice that login to the KDE console (using SDDM) may take up to more than a minute to login. I also noticed once that parts of the GUI (the "start" menu) became nonresponsive for about 30 seconds. I am noticing this in the log [console-kit-daemon] CRITICAL: polkit_authority_check_authorization: assertion 'POLKIT_IS_AUTHORITY (authority)' failed_ This seems like a hint.

I put RUBY_TARGETS="ruby23 ruby24" in make.conf and now everything is emerging. If I comment the line, I get this emerge: there are no ebuilds built with USE flags to satisfy "virtual/rubygems[ruby_targets_ruby22]". !!! One of the following packages is required to complete your request: - virtual/rubygems-13::ruby-kit (Missing IUSE: ruby_targets_ruby22) - virtual/rubygems-12::ruby-kit (Missing IUSE: ruby_targets_ruby22) - virtual/rubygems-11::ruby-kit (Missing IUSE: ruby_targets_ruby22) (dependency required by "dev-ruby/minitest-5.10.3::ruby-kit[-test,ruby_targets_ruby22]" [ebuild]) (dependency required by "dev-lang/ruby-2.4.3::ruby-kit" [installed]) (dependency required by "dev-ruby/test-unit-3.2.6::ruby-kit[ruby_targets_ruby24]" [ebuild]) (dependency required by "dev-lang/ruby-2.3.6::ruby-kit" [installed]) (dependency required by "dev-ruby/net-telnet-0.1.1-r1::ruby-kit[ruby_targets_ruby23]" [ebuild])

https://pastebin.com/D8knQCXg

https://pastebin.com/4JGNYdbx

When trying to emerge, I get the following WARNING: One or more updates/rebuilds have been skipped due to a dependency conflict: virtual/rubygems:0 virtual/rubygems-13:0/0::ruby-kit, ebuild scheduled for merge conflicts with virtual/rubygems[ruby_targets_ruby22] required by dev-ruby/net-telnet-0.1.1-r1:1/1::ruby-kit, ebuild scheduled for merge ^^^^^^^^^^^^^^^^^^^ =virtual/rubygems-13[ruby_targets_ruby22] required by dev-ruby/json-2.1.0:2/2::ruby-kit, ebuild scheduled for merge ^^^^^^^^^^^^^^^^^^^ =virtual/rubygems-13[ruby_targets_ruby22] required by dev-ruby/rake-12.1.0:0/0::ruby-kit, ebuild scheduled for merge ^^^^^^^^^^^^^^^^^^^ =virtual/rubygems-13[ruby_targets_ruby22] required by dev-ruby/net-telnet-0.1.1-r1:1/1::ruby-kit, ebuild scheduled for merge ^^^^^^^^^^^^^^^^^^^ virtual/rubygems[ruby_targets_ruby22] required by dev-ruby/json-2.1.0:2/2::ruby-kit, ebuild scheduled for merge ^^^^^^^^^^^^^^^^^^^ virtual/rubygems[ruby_targets_ruby22] required by dev-ruby/rake-12.1.0:0/0::ruby-kit, ebuild scheduled for merge ^^^^^^^^^^^^^^^^^^^ =virtual/rubygems-13[ruby_targets_ruby22] required by dev-ruby/minitest-5.10.3:5/5::ruby-kit, ebuild scheduled for merge ^^^^^^^^^^^^^^^^^^^ =virtual/rubygems-13[ruby_targets_ruby22] required by dev-lang/ruby-2.2.9:2.2/2.2::ruby-kit, ebuild scheduled for merge ^^^^^^^^^^^^^^^^^^^ virtual/rubygems[ruby_targets_ruby22] required by dev-ruby/power_assert-1.1.0:0/0::ruby-kit, ebuild scheduled for merge ^^^^^^^^^^^^^^^^^^^ =virtual/rubygems-13[ruby_targets_ruby22] required by dev-ruby/test-unit-3.2.6:2/2::ruby-kit, ebuild scheduled for merge ^^^^^^^^^^^^^^^^^^^ virtual/rubygems[ruby_targets_ruby22] required by dev-ruby/test-unit-3.2.6:2/2::ruby-kit, ebuild scheduled for merge ^^^^^^^^^^^^^^^^^^^ virtual/rubygems[ruby_targets_ruby22] required by dev-lang/ruby-2.2.9:2.2/2.2::ruby-kit, ebuild scheduled for merge ^^^^^^^^^^^^^^^^^^^ virtual/rubygems[ruby_targets_ruby22] required by dev-ruby/minitest-5.10.3:5/5::ruby-kit, ebuild scheduled for merge ^^^^^^^^^^^^^^^^^^^ =virtual/rubygems-13[ruby_targets_ruby22] required by dev-ruby/power_assert-1.1.0:0/0::ruby-kit, ebuild scheduled for merge

I set -rdoc in USE and that seems to have worked around it.

In trying to emerge kde-plasma, I am getting this Oops! Conflicts have been encountered: >>> dev-lang/ruby-2.4.3:2.4/2.4::ruby-kit, ebuild scheduled for merge, wants >=dev-ruby/rdoc-5.1.0[ruby_targets_ruby24] >>> dev-lang/ruby-2.2.9:2.2/2.2::ruby-kit, ebuild scheduled for merge, wants >=dev-ruby/rdoc-4.0.1[ruby_targets_ruby22] My candidates are: >>> dev-ruby/rdoc-5.1.0:0/0::ruby-kit, ebuild scheduled for merge has SLOT 0/0 but not IUSE ruby_targets_ruby22 >>> dev-ruby/rdoc-4.3.0:0/0::ruby-kit, ebuild scheduled for merge has SLOT 0/0 and IUSE ruby_targets_ruby22

I'm building a machine fresh and I am at the point of running emerge for the first time and I'm seeing this error !!! Unable to parse profile: '/etc/portage/make.profile' !!! ParseError: Parent 'llvm-kit:funtoo/kits/python-kit/3.4-prime' not found: '/etc/portage/make.profile/parent' emerge info reveals Portage 2.3.8 (python 2.7.13-final-0, funtoo/1.0/linux-gnu/arch/x86-64bit, gcc-5.4.0, glibc-2.23-r4, 4.4.28-std490-amd64 x86_64) ================================================================= System uname: Linux-4.4.28-std490-amd64-x86_64-Intel-R-_Xeon-R-_CPU_E5-1650_v2_@_3.50GHz-with-gentoo-2.2.1 KiB Mem: 3080320 total, 448420 free KiB Swap: 0 total, 0 free sh bash 4.4_p12-r1 ld GNU ld (Gentoo 2.28 p1.2) 2.28 app-shells/bash: 4.4_p12-r1::core-kit dev-lang/perl: 5.24.0-r2::gentoo dev-lang/python: 2.7.13::gentoo, 3.4.6::gentoo sys-apps/baselayout: 2.2.1::gentoo sys-apps/openrc: 0.23.2-r1::core-kit sys-apps/sandbox: 2.10-r4::core-kit sys-devel/autoconf: 2.69-r2::gentoo sys-devel/automake: 1.15-r2::gentoo sys-devel/binutils: 2.28-r4::core-kit sys-devel/gcc: 5.4.0::core-kit sys-devel/gcc-config: 1.8-r1::gentoo sys-devel/libtool: 2.4.6-r4::core-kit sys-devel/make: 4.1-r1::gentoo sys-kernel/linux-headers: 4.9::gentoo (virtual/os-headers) sys-libs/glibc: 2.23-r4::gentoo Repositories: nokit location: /var/git/meta-repo/kits/nokit masters: core-kit priority: -500 core-hw-kit location: /var/git/meta-repo/kits/core-hw-kit masters: core-kit priority: 1 core-kit location: /var/git/meta-repo/kits/core-kit masters: core-kit priority: 1 aliases: gentoo desktop-kit location: /var/git/meta-repo/kits/desktop-kit masters: core-kit priority: 1 dev-kit location: /var/git/meta-repo/kits/dev-kit masters: core-kit priority: 1 editors-kit location: /var/git/meta-repo/kits/editors-kit masters: core-kit priority: 1 games-kit location: /var/git/meta-repo/kits/games-kit masters: core-kit priority: 1 haskell-kit location: /var/git/meta-repo/kits/haskell-kit masters: core-kit priority: 1 java-kit location: /var/git/meta-repo/kits/java-kit masters: core-kit priority: 1 kde-kit location: /var/git/meta-repo/kits/kde-kit masters: core-kit priority: 1 lang-kit location: /var/git/meta-repo/kits/lang-kit masters: core-kit priority: 1 lisp-scheme-kit location: /var/git/meta-repo/kits/lisp-scheme-kit masters: core-kit priority: 1 media-kit location: /var/git/meta-repo/kits/media-kit masters: core-kit priority: 1 ml-lang-kit location: /var/git/meta-repo/kits/ml-lang-kit masters: core-kit priority: 1 net-kit location: /var/git/meta-repo/kits/net-kit masters: core-kit priority: 1 perl-kit location: /var/git/meta-repo/kits/perl-kit masters: core-kit priority: 1 php-kit location: /var/git/meta-repo/kits/php-kit masters: core-kit priority: 1 python-kit location: /var/git/meta-repo/kits/python-kit masters: core-kit priority: 1 ruby-kit location: /var/git/meta-repo/kits/ruby-kit masters: core-kit priority: 1 security-kit location: /var/git/meta-repo/kits/security-kit masters: core-kit priority: 1 text-kit location: /var/git/meta-repo/kits/text-kit masters: core-kit priority: 1 xfce-kit location: /var/git/meta-repo/kits/xfce-kit masters: core-kit priority: 1 xorg-kit location: /var/git/meta-repo/kits/xorg-kit masters: core-kit priority: 1 gnome-kit location: /var/git/meta-repo/kits/gnome-kit masters: core-kit priority: 10 science-kit location: /var/git/meta-repo/kits/science-kit masters: core-kit priority: 10 ACCEPT_LICENSE="* -@EULA" CFLAGS="" CONFIG_PROTECT="/etc" CONFIG_PROTECT_MASK="/etc/env.d" CXXFLAGS="" DISTDIR="/var/cache/portage/distfiles" FEATURES="assume-digests binpkg-logs config-protect-if-modified distlocks ebuild-locks fixlafiles merge-sync multilib-strict news parallel-fetch preserve-libs protect-owned sandbox sfperms strict unknown-features-warn unmerge-logs unmerge-orphans userfetch userpriv usersandbox usersync xattr" FFLAGS="" GENTOO_MIRRORS="http://distfiles.gentoo.org" LDFLAGS="" PKGDIR="/var/cache/portage/packages" PORTAGE_CONFIGROOT="/" PORTAGE_TMPDIR="/var/tmp" USE="" Unset: ACCEPT_KEYWORDS, CBUILD, CHOST, CPPFLAGS, CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LANG, LC_ALL, LINGUAS, MAKEOPTS, PORTAGE_BUNZIP2_COMMAND, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS

I configured funtoo for kde-plasma-5. It has both use flags qt4 and qt5. When emerging with newuse , pinentry complains of the following: !!! The ebuild selected to satisfy "app-crypt/pinentry" has unmet requirements. - app-crypt/pinentry-1.0.0::core-kit USE="ncurses qt4 qt5 -caps -emacs -gnome-keyring -gtk -static" The following REQUIRED_USE flag constraints are unsatisfied: at-most-one-of ( qt4 qt5 ) The above constraints are a subset of the following complete expression: any-of ( ncurses gtk qt4 qt5 ) gtk? ( !static ) qt4? ( !static ) qt5? ( !static ) static? ( ncurses ) at-most-one-of ( qt4 qt5 ) New info: it seems that qt4 wasn't provided by the mix-in, but apparently I had to add it manually otherwise a bunch of things related to KDE wouldn't emerge. qt5 is apparently builtin to the mixin and without it, poppler won't emerge.

Wow, all those messages to come here. Thanks for everyone's efforts. Does grub require anything to be read from /dev/sda1 when it's installed? If it does and that stuff isn't present because /dev/sda1 is not mounted, then it should report an error. All this time, I was getting warnings about LVM, but there was never any error reported.

This is now in bugs, https://bugs.funtoo.org/browse/FL-4767