Jump to content

dkg

Members
  • Content Count

    73
  • Joined

  • Last visited

  • Days Won

    3

Everything posted by dkg

  1. I'm having trouble understanding your instructions. You say to "copy all the kits". Copy them from where? Are you saying to copy the files in /var/git/meta-repo/repos.conf/? Then you say that I will have 'ego-core-kit linking to...'. Um. If I copy files, then they will be files, not links. Unless you are talking about the locations in those files. If so, then I would have to change all the locations in the files, no? [root@chopin ~]# cat /var/git/meta-repo/repos.conf/core-kit [core-kit] location = /var/git/meta-repo/kits/core-kit auto-sync = no priority = 1 [root@chopin ~]# cat /
  2. Another point. Earlier I said this... I figured out that difference. On the other system I had deleted /usr/portage, as it did not have space for both trees. If I do 'mv /usr/portage /usr/portage.old && eix-update' on this system, then I get the same empty results as the other system.
  3. It's likely those USE flags predate funtoo profiles. This system has been in operation since early 2014. Surely, that is not the cause of my eix troubles.
  4. Sorry. Here they are. [root@chopin repos.conf]# eix --print PORTDIR warning: ignoring parent core-kit:funtoo/1.0/linux-gnu/arch/x86-64bit of file /etc/portage/make.profile/parent warning: ignoring parent core-kit:funtoo/1.0/linux-gnu/build/current of file /etc/portage/make.profile/parent
  5. I have never seen that cause an issue with a directory symlink, but I have changed it. In addition, the symlink on the other system with eix issues did not have this "issue". I have neither PORTDIR nor PORTDIR_OVERLAY defined in make.conf. [root@chopin portage]# cat /etc/portage/make.conf # These settings were set by the metro build script that automatically built this stage. # Please consult /etc/portage/make.conf.example for a more detailed example. MAKEOPTS="-j9" # For darktable #CPU_FLAGS_X86="sse3" #CPU_FLAGS_X86="mmx mmxext popcnt sse sse2 sse3 sse4_1 sse4_2 ssse3" EMERGE_D
  6. I do not have an issue with eix displaying incorrect information about what is installed. It is reporting incorrect information about what is available to install. Really, it doesn't seem logical that rebuilding the system will fix that issue, or the other issue described above (warning: ignoring parent). [root@chopin ~]# ls -l /var/git/meta-repo/repos.conf total 116 drwx------ 2 portage portage 4096 Oct 28 14:14 ./ drwx------ 6 portage portage 4096 Nov 22 16:36 ../ -rw------- 1 portage portage 92 Oct 19 08:41 chopin.conf -rw------- 1 portage portage 89 Sep 17 11:38 core-hw-kit -rw--
  7. WOW! That is going to rebuild the whole system (922 packages). That's what I need to do to fix eix?
  8. [root@chopin ~]# ego query versions ego app-admin/ego| slot| repo --------------+-----+------------------- 2.0.9| 0| core-kit/1.0-prime 2.0.10| | core-kit/1.0-prime 2.0.14| | core-kit/1.0-prime 2.1.1| | core-kit/1.0-prime 2.2.0| | core-kit/1.0-prime 2.2.1| | core-kit/1.0-prime * 2.3.1| | core-kit/1.0-prime 2.3.2| | core-kit/1.0-prime 9999| | core-kit/1.0-prime What is '--new-repo' supposed to do? As far as I can see, that is not a valid argument to emerge.
  9. [root@chopin ~]# cat /etc/portage/make.profile/parent core-kit:funtoo/1.0/linux-gnu/arch/x86-64bit core-kit:funtoo/1.0/linux-gnu/build/current core-kit:funtoo/1.0/linux-gnu/arch/x86-64bit/subarch/corei7 core-kit:funtoo/1.0/linux-gnu/flavor/desktop core-kit:funtoo/1.0/linux-gnu/mix-ins/lxqt core-kit:funtoo/1.0/linux-gnu/mix-ins/no-systemd core-kit:funtoo/1.0/linux-gnu/mix-ins/kde-plasma-5 editors-kit:funtoo/kits/python-kit/3.4-prime text-kit:funtoo/kits/python-kit/3.4-prime dev-kit:funtoo/kits/python-kit/3.4-prime perl-kit:funtoo/kits/python-kit/3.4-prime games-kit:funtoo/kits/python-kit/3.4-pr
  10. Because eix's database is out-of-date. Those are not actually the ebuilds available.
  11. dkg

    perl woes

    Never mind. I think logitechmediaserver-bin was the source of all my problems.
  12. dkg

    perl woes

    Another ex-stable user here. I don't have the option to reinstall. The system is a VM, and the host doesn't have the space to accommodate another guest VDI built from scratch. What can I try to get around this perl slot funk? I'm not averse to temporary 'emerge -C' and system breakage, as I can always roll back. Thanks. Oops! Conflicts have been encountered: >>> virtual/perl-Parse-CPAN-Meta-1.441.700-r2:0/0::perl-kit, ebuild scheduled for merge, wants =dev-lang/perl-5.24.0* >>> virtual/perl-CPAN-Meta-YAML-0.18.0-r1:0/0::perl-kit, ebuild scheduled for merge, wants =d
  13. I'm confused what I need to do to get eix to work on a current funtoo system. People say it should work. There's an old forum thread that talks about it, but nothing in the thread has helped with my issues. Worse, I am getting different results on different systems (but never the right results). Problem one, I get warnings like this... [root@chopin portage]# eix eix warning: ignoring parent core-kit:funtoo/1.0/linux-gnu/arch/x86-64bit of file /etc/portage/make.profile/parent warning: ignoring parent core-kit:fu
  14. Seems to work just fine, thanks!
  15. Hi, Included in drobbins' recent Dropbox announcement was, "No longer has an initscript." I use the initscript on one system so that Dropbox contents would always sync immediately, even if I was not logged in. This is a server that runs 24x7 and is the primary backup source (as in pushed to backup locations, which means I need the source to be current) for my Dropbox contents. What is an alternate way to achieve this?
  16. dkg

    Using a local overlay

    I already had the local overlay setup okay (after some help via FL-4342). I think there is still something missing from the local overlay guide, though, as it didn't mention changing the owner of the overlay dirs to portage:portage. I had a permission error using 'ebuild <...> manifest' until I did this. Second, there is *something* different from gentoo. As I said, I was attempting to follow the documented gentoo procedure, which is here: https://wiki.gentoo.org/wiki/Custom_repository It calls for using repoman, which did not work for me. 'ebuild <...> mantifest
  17. I've created a local overlay per the funtoo guide, but now I'm not sure how to use it. I created a folder within, media-gfx/darktable, and placed an ebuild file in it. The gentoo guide says to use 'repoman manifest', but that isn't working for me... [root@chopin darktable]# repoman manifest [CRITICAL] Couldn't read KEYWORDS from arch.list Or, for a 'simple version bump'... [root@chopin darktable]# repoman --digest=y -d full [CRITICAL] Couldn't read KEYWORDS from arch.list What is the correct procedure for funtoo w/ kits?
  18. Understood. As I tried to explain before, I've had very few software stability issues on funtoo, whether -stable or -current. I'm not concerned about that part. :) I'm just anxious about diving in without a better understanding how kits work. Thanks.
  19. Ah, so there could be more than one branch available for a given kit. I wasn't sure about that.
  20. Thanks. Is this also what I would get by "deviating from a default kit branch"?
  21. Thanks, but I'm still struggling with the bigger picture somehow. Say I wanted to install emacs. It seems as though I would have to have editors-kit selected. Which is a 'master' branch. So, there will be no stable (amd64) ebuild available? Or will there still be amd64/~amd64 ebuilds in that overlay? Or, say I wanted a stable KDE but need the latest Digikam to work with raws from my camera. I would need to "deviate from our default kit branches" in order to do that?
  22. Again, I'm not understanding how kits are used, and this link doesn't help much. Would one be choosing to use or not use a kit? Is choosing to use a kit the equivalent of choosing -stable today? Are there different stable/unstable branches of kits? If one chooses to use a kit but want to use the latest version of package in that kit, will that be possible? That is, what is the equivalent of keywording a package with kits? It is implied that this is possible, but doesn't explain how.
  23. That's the goal of kits? What I read was the following: This is talking about system stability. Anyway, I think my problem is the lack of available information. The wiki page explains what "-prime" and "-snap" kit branches are, but not much else. Will a user be able to choose different branches of a kit? How is that done? How would one choose to use an "unstable" package that belongs to a "stable" kit?
  24. As a user of both -stable and -current, I wouldn't say that I've more issues with stable than with current. Of course, my stable installs are servers, which removes a lot of the complexity. Still, I didn't choose stable for system stability (which has rarely been an issue for me for any kind of funtoo install), I chose it to deal with fewer updates on the servers. It's more "stable" in the sense that there are fewer system changes. I'm not sure if kits will provide the same advantages.
  25. Sorry, I thought you had vers=4.2 as a mount option in your fstab file. I tried this on my my system: # mount.nfs -v wolfie:/share /share mount.nfs: timeout set for Fri Feb 5 21:00:46 2016 mount.nfs: trying text-based options 'vers=4.2,addr=192.168.0.3,clientaddr=192.168.0.50' mount.nfs: mount(2): Protocol not supported mount.nfs: trying text-based options 'vers=4.1,addr=192.168.0.3,clientaddr=192.168.0.50' Do you have NFSv4.2 support enabled in your kernel? I do.
×
×
  • Create New...