Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


Reputation Activity

  1. Great Post
    NikosAlexandris reacted to joachin in pangomm & libreoffice error   
    Hey guys, having some problems trying to install pango mm:
    and libreoffice-bin:
    !!! Multiple package instances within a single package slot have been pulled
    !!! into the dependency graph, resulting in a slot conflict:
      (dev-libs/boost-1.65.0:0/1.65.0::core-kit, ebuild scheduled for merge) pulled in by
        dev-libs/boost:0/1.65.0 required by (app-office/libreoffice-bin-, ebuild scheduled for merge)
      (dev-libs/boost-1.70.0:0/1.70.0::core-kit, installed) pulled in by
        >=dev-libs/boost-1.65.1:0/1.70.0= required by (sys-fs/cryfs-0.10.2:0/0::core-kit, installed)
        ^^               ^^^^^^^^^^^^^^^^                                                            
        (and 1 more with the same problem)
      (app-text/hunspell-1.6.2-r1:0/1.6::text-kit, ebuild scheduled for merge) pulled in by
        app-text/hunspell:0/1.6 required by (app-office/libreoffice-bin-, ebuild scheduled for merge)
      (app-text/hunspell-1.7.0:0/1.7::text-kit, installed) pulled in by
        app-text/hunspell:0/1.7= required by (kde-frameworks/sonnet-5.59.0:5/5.59::kde-kit, installed)
        (and 1 more with the same problem)
    NOTE: Use the '--verbose-conflicts' option to display parents omitted above
    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.
  2. Great Post
    NikosAlexandris reacted to drobbins in IMPORTANT: 1.3-release to BETA and removal of multilib   
    Hi All,
    Within 12 hours, I plan to move 1.3-release to BETA status.
    Along with this comes the very important change on 64-bit platforms -- I am removing multilib and making "pure64" compatibility the default. This means that 1.3-release builds with the x86-64bit arch will be 64-bit only.
    This is done for a variety of reasons, most important of which is that the world has had a 64-bit PC instruction set for approximately 15 years. It is time to drop 32-bit support. For those who still need 32-bit support, it will be available via a Funtoo 32-bit chroot setup.
    The story behind multilib is rather complex and interesting, and might be the focus of a future blog post, but for now, you will just have to trust me -- multilib support in Gentoo is a pain in the butt. It takes a lot of effort to work with and slows us down. Our efforts are best spent in other places, and chroot should work for the vast majority of users who truly are running a critical 32-bit application (other options are 32-bit containers, etc.)
    EDIT: Upgrade Instructions Here: https://www.funtoo.org/Upgrade_Instructions/1.3-release
  3. Great Post
    NikosAlexandris reacted to drobbins in We have a new FAQ!   
    Hey Everyone,
    We have a new FAQ developed that allows you to more easily browse answers. See:
    You can also submit your own FAQ questions which I will answer! ? Hope you enjoy it.
  4. Confused
    NikosAlexandris reacted to shelom in Why Funtoo is not migrating on GitLab ?   
    Hello to everybody & sorry for my poor english.
    I really wish to ask the comunity of Funtoo:
    Why you are staying on GitHub,scince it was acquired by the Sionistic/Massonic microsoft?
    Are you not affraid,that someone can manipulate your sources to realese some kind of backdoor in your images ?
    Thanks . 
  5. Great Post
    NikosAlexandris reacted to drobbins in Bentōō (An user-friendly Stage4 of Funtoo Linux.)   
    OK, done.... ?

  6. Great Post
    NikosAlexandris reacted to lazlo.vii in I like 2FA   
    Thanks for adding the 2FA to the site.  I wish more would do it.  I use it every where I can.  Even my home server has the google-auth pam modules for ssh.
  7. Haha
    NikosAlexandris reacted to drobbins in Detached HEAD state for some kit branches   
    There is nothing wrong with some branches having "detached head". You will see this when there has been a recent update to our 1.3 development branch.
    If you see this at the end:
    Sync successful and kits in alignment! :) Then it means things are OK.
  8. Great Post
    NikosAlexandris got a reaction from cardinal in Ego ImportError   
    May I ask what your system's
    eselect python show is set to? I guess python3.6.
  9. Great Post
    NikosAlexandris got a reaction from cardinal in Ego ImportError   
    OK, I 've set to python3.6 via
    root@carbon nik # eselect python list Available Python interpreters, in order of preference: [1] python3.4 [2] python2.7 [3] python3.6 (fallback) [4] python3.5 (fallback) root@carbon nik # eselect python set 3 root@carbon nik # eselect python show python3.6 and it worked.  Thank you for the hints!
  10. Great Post
    NikosAlexandris reacted to palica in ego 2.6 testing?   
    since the commands from boot-update moved to ego you need to remove boot-update first.
  11. Great Post
    NikosAlexandris reacted to drobbins in IMPORTANT: Upgrade your Funtoo Account!   
    The Funtoo authentication system has recently been upgraded to use Authy, a SMS-based verification service. We're using this to protect the funtoo community against spam bots and other nasty things, which are unfortunately an issue we need to deal with.
    You will not be able to log in to Funtoo until you upgrade your account!
    To do this, go to https://auth.funtoo.org/login, log in, and you will be prompted to provide an SMS number to verify your account.
    This will only happen once -- it normally happens upon account registration only -- but existing Funtoo users will need to go through this extra step.
    Apologies for the inconvenience, but unfortunately this kind of thing is becoming necessary.
  12. Haha
    NikosAlexandris reacted to maleita in emerge @preserved-rebuild trouble   
    is in the /var/db/pkg/app-crypt/qca-2.1.3-r2/qca-2.1.3-r2.ebuild
    before has qt4 and qt5 IUSE , now have no!
    PS: if u remove kdelibs your kde goes broke!!!!
  13. Great Post
    NikosAlexandris reacted to palica in Playonlinux doesnt start after update, can anybody test if it work?   
    yes, I know that one exactly.
    Once it will be fixed :)
  14. Great Post
    NikosAlexandris reacted to drobbins in xorg-kit 1.19-prime now default   
    Hi All,
    xorg-kit 1.19-prime will be the default after the next tree update. It includes xorg-server-1.19.3 but with backports of all security fixes through (and including) xorg-server 1.19.5.
  15. Great Post
    NikosAlexandris reacted to Oleg Vinichenko in meta-repo: Can /usr/portage be deleted now?   
    you can save the distfiles and pkgs (binary) if its a problem, otherwise /usr/portage can be zapped
  16. Sad
    NikosAlexandris reacted to Tassie_Tux in java not working with chromium   
    I just tried the Java verification site https://www.java.com/verify/ and the applet does not work for me with chromium 38.0.2125.24. It does work with firefox 31.0 and oracle-jdk-bin
  17. Haha
    NikosAlexandris reacted to cafaia in Can't emerge 'www-client/chromium-62.0.3202.18::net-kit'   
    To compile this version of chromium you have upgrade gcc-5.3.0-r1 to gcc-5.4.0. Look here: https://bugs.funtoo.org/browse/FL-4235. sys-devel/gcc-5.4.0 is sufficient to complile this version of chromium.
  18. Great Post
    NikosAlexandris reacted to drobbins in Welcome to the new forums!   
    I just fixed login-related issues. Funtoo users who had not used the forums before were unable to log in.
    I've also fixed the password reset link to go to our official password reset page, as well as the create account link. So logins should be working well.
    One note is that if you were are user of the old forums, and you changed your 'displayname' to show something other than your username, then your forums account username will be your displayname. You can alternatively try logging in with your email as your username instead.
    Everyone else should be good to go using their funtoo username (and password, of course) to log in here.
  19. Trolling
    NikosAlexandris reacted to Oleg Vinichenko in funtoo-stable is going away   
    and from my own experience, i have never used stable builds anywhere and there was no really major problems (like disastrous ones), maybe 2-3 only in last 10 years. so, a key is - when you know what to do with stable or unstable - you could expect things to work. if you don't know what to do, likely you'll trap into troubles regardless stable or unstable used. Sometimes updates can be frustrating, i agree. And for newcomers, of course, it's hard as they mostly driven by existing documentation, web, irc -which can be really wrong. The "stable" is what is controlled by matter of letter, in ebuilds, i can put "amd64" instead "~amd64" and it will be considered stable by package manager, which is of course far from real definition of stable. For example, back into not so old case (about 4 monthes), xorg-server-1.19 stabilized by gentoo, due to multiple security vulnerabilities in xorg itself and in it's core parts. xorg-1.19, in turn, found to be very unstable in certain conditions, so the security fixes diminished by the fact you have no working xorg. Those security fixes can be easily, and they are in Funtoo, backported into good known 1.17 version. of course, if 1.19 were ok for the one, he could choose using 1.19. Just trying to describe that stabilization and stable by means of packages, is a volatile term.
  20. Trolling
    NikosAlexandris reacted to mingdao in Capturing kernel customization to post on forum and wiki?   
    I don't use Docker, so can't answer concerning it.
    When you run "make menuconfig", when you save and close, it moves .config to .config.old. So just run:
    diff /usr/src/linux/.config /usr/src/linux/.config.old You can't show changes with menuconfig, and copy the text with markings (whatever markings are).
  21. Trolling
    NikosAlexandris reacted to drobbins in funtoo-stable is going away   
    Hi everyone,
    We've decided to retire funtoo-stable to keep us focused as we move towards funtoo kits and other next-generation initiatives. I recommend that all stable users migrate to funtoo-current.
  22. Trolling
    NikosAlexandris reacted to hencb in Learning to create newer versions of e-builds   
    Ok there's quite a few outdated documents and command warnings that cause problems here.
    First of, emerge <ebuildname>.ebuild from the current overlay directory tends to work. I generally don't use it since the ebuild
    tool allows you to install a package just like emerge does, but it does this by going through different stages.
    Let's start with the prerequisite: The manifest file.
    You don't have to run ebuild *.ebuild manifest, just run ebuild <ebuildname>.ebuild manifest, which will generate a manifest for all ebuilds in the current directory. There's also repoman, which Gentoo uses, and which can create manifests as well: repoman manifest will create manifest entries for all ebuilds that don't have one already.
    I highly recommend reading "man ebuild" on how to use the ebuild tool. It will make debugging ebuild problems a lot easier. A basic way to install a custom ebuild using the ebuild tool can be done like this, if the manifest is correct:
    ebuild gdal-2.0.3.ebuild fetch (downloads the package and verifies that its integrity using the manifest file) ebuild gdal-2.0.3.ebuild unpack (downloads the package and untars it into /var/tmp/portage/sci-libs/gdal-2.0.3.ebuild) ebuild gdal-2.0.3.ebuild prepare (applies any patches and prepares the ebuild) ebuild gdal-2.0.3.ebuild configure (runs the configure script of autotools) ebuild gdal-2.0.3.ebuild compile (compiles the packages) ebuild gdal-2.0.3.ebuild install (this will install the package into a sandbox, that is, into /var/tmp/portage/sci-libs/gdal-2.0.3/image folder) ebuild gda1 qmerge (install the package into the system. At this point, the whole process is completed and is equivalent to running emerge) Some phases also include others. Typically, you'll skip the fetch and configure phase, they are included in the other commands (unpack and compile). I haven't listed some of the phases due to brevity. This is still a very verbose way to install an ebuild, and a bit tedious.  A simpler way to use the ebuild tool is to run:
    ebuild <ebuildname>.ebuild merge ,which is equivalent to running: emerge <ebuildname>.ebuild.
    Consider reading both man ebuild (for the tool) and man 5 ebuild (for the ebuild syntax). They're the most accurate documents at the moment.
    It seems somebody masked the newer versions of gdal for some reason. This needs further investigation. It might be a malformed mask and you should add an entry to package.unmask for the time being:
    Drop by on IRC sometime and I'll be glad to assist you with any questions. Just ping me (bhenc) and I'll help you get started with the ebuilds. If you're unfamiliar with IRC, the www.funtoo.org/Getting_Help  page might be a good place to start.
    Happy hacking!
  23. Trolling
    NikosAlexandris got a reaction from Tassie_Tux in On the latest instructions for the "ZFS Install Guide"   
    Just closing this topic. All works fine.
  24. Trolling
    NikosAlexandris reacted to Tassie_Tux in On the latest instructions for the "ZFS Install Guide"   
    It is unfortunate that boot has been unsuccessful. Comments left on the Talk page.
  25. Trolling
    NikosAlexandris reacted to cardinal in How to "adjust" euse".   
    Open /usr/bin/euse as root in text editor.
    Comment line 723,add bold text and save.
    #eval $(portageq envvar -v PORTDIR)
    : ${PORTDIR="$(portageq get_repo_path $(portageq envvar EROOT) gentoo)"}
    get_portdir() { # Use a subshell so we don't have to protect the variables in # the current scope ( #eval $(portageq envvar -v PORTDIR) : ${PORTDIR="$(portageq get_repo_path $(portageq envvar EROOT) gentoo)"} echo "${PORTDIR}" ) } # }}} Reference: https://goo.gl/WXOGhM
  • Create New...