Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


hick518 last won the day on May 4 2016

hick518 had the most liked content!

About hick518

  • Rank
    Advanced Member

Recent Profile Visitors

1,053 profile views
  1. On one of my systems, any attempt to emerge a package hangs when it gets to "checking ## files for package collisions". There is no output to help me figure out where the problem lies. Can anybody suggest where I should start looking? What utility is used for this "checking..." operation?
  2. In my case I was getting "filter failed" in error.log, so your case seems to be a little different than mine. Anyway, I never solved my issue and instead installed a 32-bit Devuan virtual machine, running on my Funtoo host, and made that my print server. The Brother drivers worked fine there. Here are some of my notes from setting up the VM: https://forums.funtoo.org/topic/4469-starting-a-qemu-virtual-machine-at-boot/
  3. You can get more logging out of cups by making this change to cupsd.conf: replace LogLevel warn with LogLevel debug There's also a debug2, which is probably overkill.
  4. I'm still interested to know if there's a way to do it with just qemu, but here's how to do it using libvirt: 1) Install and run libvirt emerge -a libvirt virt-manager rc-update add libvirtd default /etc/init.d/libvirtd start 2) Import the qemu disk into libvirt. virt-install --name vmname --memory 1024 --disk /path/to/disk.qcow2 --import After the import, the vm will be powered on. Note that this can also be done in the gui, virt-manager. 3) Tell libvirt to automatically start the vm. virsh autostart vmname This creates a symbolic link in /etc/libvirt/qemu/autostart 4) You can test by shutting down the vm, stopping the libvirtd daemon, then starting the libvirtd daemon. Verify the status of the vm: virsh list --all This can also be verified in the virt-manager gui. 5) Make sure libvirtd is set to start on boot. rc-status | grep libvirtd rc-update add libvirtd default 6) On shutdown of the host, make sure the guests don't just get virtually powered off. rc-update add libvirt-guests default /etc/init.d/libvirt-guests start By default the guests will have their state saved, and any guest that is saved / shut down by the libvirt-guests service will be automatically started on the next boot (even if it was not set to autostart in step 3).
  5. I created a virtual machine using qemu. What's the proper way to automatically start it at boot time, and stop it at shutdown? Do I need to use libvirt for this? If so, how do I make libvirt aware of my existing qemu image?
  6. For a while now I haven't been able to print to my Brother DCP-7065dn printer. It used to work. I've got net-print/brother-dcp-7065dn-drivers installed. I've also tried re-installing it. One thing I notice is that all binaries in /usr/local/Brother/Printer/DCP7065DN are 32-bit. Should these work on my Funtoo 1.4 system? I've set cups logging to "debug", but haven't gotten anything useful out of the logs.
  7. Thanks bcowan, I had already tried that and the situation didn't improve. As it turns out, as long as I used '--backtrack=30' for every emerge operation, it worked ok. On one of my previous upgrades, that didn't help so on this one I didn't try it right away. But I will from now on!
  8. Adding '--backtrack=30' fixed this. emerge --backtrack=30 --jobs=3 -u =dev-lang/python-3.7* But now I'm getting similar conflicts when running the next step, ' emerge -auDN --backtrack=30 @world --jobs=3 --exclude dev-lang/perl'. Any suggestions on how to handle these types of conflicts in general would be appreciated.
  9. # eselect python list Available Python interpreters, in order of preference: [1] python3.6 [2] python2.7 (fallback)
  10. I've upgraded 3 systems from 1.3 to 1.4, and each one has caused me major headaches. I'm on my fourth one now, and figured it's time to ask for help. I'm following the instructions here, and I'm up to the point of upgrading python: https://www.funtoo.org/Upgrade_Instructions/1.4-release # emerge -u =dev-lang/python-3.7* Connected to xxxxxxxxx Fetching /packages/Packages to /tmp/tmprupi7h74 /packages/Packages 100% 1839KB 226.0KB/s 00:08 Calculating dependencies... done! [binary U ] app-arch/bzip2-1.0.8 [1.0.6-r9] USE="-abi_riscv_lp64% -abi_risc v_lp64d% -split-usr%" [binary U ] sys-libs/readline-8.0 [7.0_p5] USE="-abi_riscv_lp64% -abi_riscv _lp64d%" [binary NS ] dev-lang/python-3.7.3 [2.7.15, 3.6.8] !!! Multiple package instances within a single package slot have been pulled !!! into the dependency graph, resulting in a slot conflict: sys-libs/readline:0 (sys-libs/readline-8.0:0/8::core-kit, binary scheduled for merge) pulled in by >=sys-libs/readline-4.1:0/8= required by (dev-lang/python-3.7.3:3.7/3.7m::py thon-kit, binary scheduled for merge) ^^^^^ (sys-libs/readline-7.0_p5:0/7::core-kit, installed) pulled in by sys-libs/readline:0/7= required by (net-dns/bind-tools-9.12.2_p2-r1:0/0::cor e-kit, installed) ^^^^^ sys-libs/readline:0/7= required by (app-crypt/gnupg-2.2.11:0/0::core-kit, in stalled) ^^^^^ sys-libs/readline:0/7= required by (net-wireless/bluez-5.50-r1:0/3::core-kit , installed) ^^^^^ >=sys-libs/readline-4.1:0/7= required by (dev-lang/python-3.6.8:3.6/3.6m::py thon-kit, installed) ^^^^^ >=sys-libs/readline-4.1:0/7= required by (net-misc/ntp-4.2.8_p12:0/0::core-k it, installed) ^^^^^ sys-libs/readline:0/7= required by (sys-apps/util-linux-2.33:0/0::core-kit, installed) ^^^^^ sys-libs/readline:0/7= required by (net-fs/samba-4.9.2-r1:0/0::core-server-k it, installed) ^^^^^ ^^^^^ sys-libs/readline:0/7= required by (net-wireless/bluez-5.50-r1:0/3::core-kit, installed) ^^^^^ >=sys-libs/readline-4.1:0/7= required by (dev-lang/python-3.6.8:3.6/3.6m::python-kit, installed) ^^^^^ >=sys-libs/readline-4.1:0/7= required by (net-misc/ntp-4.2.8_p12:0/0::core-kit, installed) ^^^^^ sys-libs/readline:0/7= required by (sys-apps/util-linux-2.33:0/0::core-kit, installed) ^^^^^ sys-libs/readline:0/7= required by (net-fs/samba-4.9.2-r1:0/0::core-server-kit, installed) ^^^^^ (and 14 more with the same problems) app-arch/bzip2:0 (app-arch/bzip2-1.0.8:0/1::core-kit, binary scheduled for merge) pulled in by app-arch/bzip2:0/1= required by (dev-lang/python-3.7.3:3.7/3.7m::python-kit, binary scheduled for merge) ^^^^^ (app-arch/bzip2-1.0.6-r9:0/0::core-kit, installed) pulled in by app-arch/bzip2:0/0= required by (dev-lang/python-2.7.15:2.7/2.7::python-kit, installed) ^^^^^ (and 1 more with the same problem) NOTE: Use the '--verbose-conflicts' option to display parents omitted above !!! The slot conflict(s) shown above involve package(s) which may need to !!! be rebuilt in order to solve the conflict(s). However, the following !!! package(s) cannot be rebuilt for the reason(s) shown: (net-wireless/bluez-5.50-r1:0/3::core-kit, installed): ebuild is masked or unavailable (net-fs/samba-4.9.2-r1:0/0::core-server-kit, installed): ebuild is masked or unavailable (sys-apps/util-linux-2.33:0/0::core-kit, installed): ebuild is masked or unavailable (net-dns/bind-tools-9.12.2_p2-r1:0/0::core-kit, installed): ebuild is masked or unavailable (net-misc/ntp-4.2.8_p12:0/0::core-kit, installed): ebuild is masked or unavailable (app-crypt/gnupg-2.2.11:0/0::core-kit, installed): ebuild is masked or unavailable It may be possible to solve this problem by using package.mask to prevent one of those packages from being selected. However, it is also possible that conflicting dependencies exist such that they are impossible to satisfy simultaneously. If such a conflict exists in the dependencies of two different packages, then those packages can not be installed simultaneously. You may want to try a larger value of the --backtrack option, such as --backtrack=30, in order to see if that will solve this conflict automatically. For more information, see MASKED PACKAGES section in the emerge man page or refer to the Gentoo Handbook. I've tried manually upgrading readline and bzip2, but that just results in more conflicts. Any idea what my best path forward is? Each of the last three upgrades took me several days to work out, and I'm hoping the next two won't have to be as bad.
  11. Thanks Cardinal. The Follow button is white until you are actually following. I still think it's a good idea to give some other type of notification of upgrades, although it is a little less critical for me now that I'm following News and Announcements per your suggestion. For instance, Ubuntu utilizes motd to let you know when you log in at the CLI that a release upgrade is available. Following News and Announcements isn't exactly going to fill my inbox, but it does contain a wide variety of news. For instance, "Funtoo 1.4 is released" and "Funtoo is now on Discord" have significantly different levels of importance to me, especially since "Funtoo 1.4 is released" means that my 1.3 system will stop receiving updates at some point in time. Anyway, just food for thought for the powers that be. Thanks again, Cardinal.
  12. I don't frequent the forum, and this is the second or third time now that a big upgrade was made available that I didn't know about. The first time I went for months without any package updates because I didn't know I had to upgrade to a newer Funtoo version. I would like to suggest that a notification of available upgrade be presented when running 'ego sync' or 'emerge @world'. The notification should tell the sysadmin that there's a newer Funtoo version available, and the date it was made available (so the sysadmin will know how mature the upgrade is and also how out of date he is). For instance: Funtoo 1.4 was made available on August 1, 2019. See https://www.funtoo.org/Upgrade_Instructions/1.4-release
  13. When I upgrade to 1.4, I'm instructed to use a gfxcard mix-in. If I do that, should I remove the VIDEO_CARDS line from make.conf?
  14. An upgrade to sssd 1.16.3 today fixed the problem.
  • Create New...