Jump to content
funtoo forums


  • Content Count

  • Joined

  • Last visited

About mauricev

  • Rank
    Advanced Member

Recent Profile Visitors

500 profile views
  1. What could be tripping up ego on a fresh 1.3 installation of 32-bit? ERROR: There was an error syncing xorg-kit. ERROR: There was an error syncing gnome-kit.
  2. 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?
  3. 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
  4. How odd, I set fsid=0 as an option to the export line and now it works in the older gentoo kernel.
  5. 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 for /z/nfs (/z/nfs) Aug 02 23:41:23 [rpc.mountd] Cannot export /z/nfs, possibly unsupported filesystem or fsid= required
  6. 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
  7. 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
  8. 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.
  9. 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!
  10. /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
  11. That was a mistake, not the mistake. It still doesn't work.
  12. 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.
  13. 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.
  14. 4.15.17-1 https://pastebin.com/zK629ztL
  • Create New...