Jump to content
funtoo forums


Funtoo Linux Developer
  • Content count

  • Joined

  • Last visited

  • Days Won


palica last won the day on June 17

palica had the most liked content!


About palica

  • Rank
    Advanced Member
  1. eix-update broken

    emerge --info please
  2. Outdated Desktop Environments

    upper/lower case? if that makes no difference write to support@funtoo.org with details.
  3. Funtoo improves Dropbox

    Maybe take a look at syncthing: https://syncthing.net/
  4. Funtoo improves Dropbox

    Source: https://www.dropboxforum.com/t5/Syncing-and-uploads/Dropbox-client-warns-me-that-it-ll-stop-syncing-in-Nov-why/m-p/290065/highlight/true#M42255
  5. Outdated Desktop Environments

    1. using kits to deliver software => not being fully rolling release (semi-rolling or release based) more info: https://www.funtoo.org/News:New_Ports-2017_tree_and_Kits 2. lack of manpower but you can file a bug here: bugs.funtoo.org and see what happens.
  6. 1.2 Funtoo Linux Release

    More up-to-date instructions can be found here: https://www.funtoo.org/Upgrade_Instructions
  7. Funtoo Stages and Release 1.2

    Upgrade instructions can be found here: https://www.funtoo.org/Upgrade_Instructions
  8. emerge --newuse -uD world - mips-sources problem?

    "ego sync" maybe?
  9. trouble with totem-3.26.0

  10. kernel can't find / (root)

    UUID should work with the default debian-sources (kernel), what you might need to add to your boot cmd is "rootwait". Sometimes it takes a while to initialize the USB ports or SD cards if /(root) is on those cards USB stick.
  11. sh: bad number

    Where do you have this message? Before starting what openrc program? Do you mean script or before OpenRC starts? Can you just give more details. What is in your fstab, how do you start your kernel, what is the kernel command line. Do you use your own kernel or debian-sources .......? There are thousands of possible reasons why you see this message. Thanks for providing more details and thanks for reading this post:
  12. how to get a local overlay working

    well, there are at least two warnings displayed on my computer, after replicating your setup. root@sucellus /usr/local/portage/cat/autossh # ebuild autossh-1.4f.ebuild digest !!! 'cat/autossh' has a category that is not listed in /etc/portage/categories >>> Creating Manifest for /usr/local/portage/cat/autossh !!! File b'/var/cache/portage/distfiles/autossh-1.4f.tgz' doesn't exist, can't update Manifest root@sucellus /usr/local/portage/metadata # cat layout.conf repo-name = local thin-manifests = true sign-manifests = false profile-formats = portage-2 cache-formats = md5-dict masters = core-kit root@sucellus /usr/local/portage/metadata # emerge -pv cat/autossh These are the packages that would be merged, in order: Calculating dependencies / !!! 'cat/autossh' has a category that is not listed in /etc/portage/categories ... done! emerge: there are no ebuilds to satisfy "cat/autossh". emerge: searching for similar names... emerge: Maybe you meant net-misc/autossh? it is just helpful to paste any error or warning message, besides saying "it doesn't work for me ..."
  13. how to get a local overlay working

    why don't you simply copy the directory structure from the package already in portage. That means in your case: net-misc/autossh didn't emerge warn you about non-existent category "cat"?
  14. ZFS Mountpoints

    My recommendation is to use mirroring.
  15. how to get a local overlay working

    this is easy to fix (with bit of searching on your part). hint: [I] app-text/tree [1] Available versions: 1.7.0 (~)1.7.0-r1 Installed versions: 1.7.0-r1(12:16:50 AM 11/22/2017) Homepage: http://mama.indstate.edu/users/ice/tree/ Description: Lists directories recursively, and produces an indented listing of files [1] "text-kit" /var/git/meta-repo/kits/text-kit