Jump to content

rspartz

Members
  • Content Count

    16
  • Joined

  • Last visited

  • Days Won

    1

rspartz last won the day on February 8 2017

rspartz had the most liked content!

About rspartz

  • Rank
    Member

Recent Profile Visitors

861 profile views
  1. Thank you; for pointing me in the right direction -and- for a quick reply! After I learn a bit more about this, I'll post my results back to this post. Appreciate the help! update: I was able to add the gentoo overlay and install the acct-group. That did allow me to install flatpak. But now, with every emerge command I get aragon ~ # emerge -avl --pretend gnome-software !!! Repository name or alias 'gentoo', defined for repository 'core-kit', overrides existing alias or repository. and I wonder if I messed anything up ..
  2. I'm trying to install flatpak and I've never used an overlay before. From all that I've searched, I think I'm 'almost there' and it seems the only thing stopping the emerge is Calculating dependencies | !!! 'acct-group/flatpak' has a category that is not listed in /etc/portage/categories ... done! I don't have a file or a directory in /etc/portage called categories aragon ~ # emerge -avl dev-util/flatpak-builder sys-apps/flatpak These are the packages that would be merged, in order: Calculating dependencies | !!! 'acct-group/flatpak' has a category that i
  3. I have a host that is running Ubuntu and LXD. I've installed a container from public image that is funtoo 1.3. I then did and upgrade to 1.4 for the new container I created. In /var/lib/portage/world there was one entry from the public image /sys-kernel/debian-sources-lts My question is, does a container need to have kernel sources installed? Since it's using the hosts kernel? I do understand that some packages may require kernel sources as dependency, but when the kernel is compiled it can not be installed. Is there a good 'best practices' on what do do with kernel sources within a container
  4. Well, the correct answer as of a few days ago to your question can be found in this bug report: https://bugs.funtoo.org/browse/FL-4772 From the comments by @drobbins: Not going to support ZFS booting officially as it is not needed. Just use another filesystem to get the system booted, then connect to all your ZFS. I can add a message to the wiki page to indicate this is not supported. If you do a refresh on your browser and look at the update to a ZFS install on funtoo, you'll see the new disclaimer at the top about booting using a different file system on root. I k
  5. Yes, a bug has been filed: https://bugs.funtoo.org/browse/FL-6279
  6. I happened to download the 6.0.0 version and it certainly looked 'weird' when it was booted. Like, where did this systemd stuff come from ?? No more Gentoo ??? This page shows the most important changes provided in each SystemRescueCd version. It only shows changes in the versions of the Linux kernel and relevant utilities. The full list of packages provides more details about the exact versions of all other packages. 6.0.0) 2019-02-02: System is now based on ArchLinux and built using archiso and its dependencies Kernel and user space programs are
  7. Ok, after looking at funtoo bugs (should've started there, sorry!) I see this is already in process: https://bugs.funtoo.org/browse/FL-5591 Great! I'll keep an eye on it and look to install later. [SOLVED] ** Update ** Since FL-5591 is now closed, samba now builds. Just 'ego sync' to the latest version and emerge. -working. Thank you Oleg.
  8. I am trying to emerge samba on a fresh, funtoo install. I did change my flavor from 'core' to 'workstation' and set about updating world because of new USE flags. Once that was done, I've tried this and I am stuck: northstar ~ # emerge -a net-fs/samba These are the packages that would be merged, in order: Calculating dependencies... done! emerge: there are no ebuilds to satisfy ">=sys-libs/talloc-2.1.14[python?,python_targets_python2_7(-)?,-python_single_target_jython2_7(-),-python_single_target_pypy(-),-python_single_target_pypy3(-),-python_single_target_python3_7(-),-p
  9. To all who've contributed to this thread; so far no luck with any options suggested. I think I am in agreement with Oleg that initramfs must be the 'closest' to the root cause, or possibly something to do with GRUB since it consistently fails to find the 'root device'. I will submit a bug report on this right away. If anyone has more to add, after their own testing, please comment here and I will add to the bug report. -thank you.
  10. Hello, Chris - To answer about the 'pool' and the 'bootfs' info: sysresccd ~ # zpool list NAME SIZE ALLOC FREE EXPANDSZ FRAG CAP DEDUP HEALTH ALTROOT rpool 191G 12.8G 178G - 3% 6% 1.00x ONLINE /mnt/funtoo sysresccd ~ # zpool get bootfs rpool NAME PROPERTY VALUE SOURCE rpool bootfs rpool/ROOT/funtoo local sysresccd ~ # Here's the zpool.cache info, both from /tmp and inside the chroot: sysresccd ~ # ls -lsda /tmp/zpool.cache 4 -rw-r--r-- 1 root root 1416 Feb 8 08:30 /tmp/zpool.cache sysresccd ~ # ls -lsda /mnt/
  11. Hello! I have tried many times to get this to work based on the fine ZFS_Install_Guide but I consistently fail at this point (see screenshot). Both the kernel and initramfs are completely rebuilt using genkernel, but it can never find 'rpool' as the root device. Any guidance is appreciated!
  12. FIXED. Thanks cardinal , that did it. I appreciate your response to this!
  13. Each time I run revdep-rebuild it wants to rebuild samba-4.7.1 as a 'one shot'. I've allowed it to do the rebuild a few times and let it go over serveral days to see if any furture syncs make it just go away. Not sure where to start to understand what is triggering this rebuild. Thank you! root@opti390:~# revdep-rebuild --ignore --pretend -i * This is the new python coded version * Please report any bugs found using it. * The original revdep-rebuild script is installed as revdep-rebuild.sh * Please file bugs at: https://bugs.gentoo.org/ * Collecting system binaries
×
×
  • Create New...