dkg
-
Posts
74 -
Joined
-
Last visited
-
Days Won
3
Content Type
Profiles
Forums
Blogs
Posts posted by dkg
-
-
2 hours ago, palica said:
so I would recommend you to do it this way:
/etc/portage/repos.conf/ will contain:
-
copy all the kits and prepend them with ego-
- so you will have ego-core-kit linking to /var/git/meta-repo/repos.conf/core-kit and so on for other kits
- don't copy default
- put stuff from default into core-kit
- put your chopin.conf in here too
This is going to be the new layout coming with ego-2.3.2
Paste your chopin.conf
eix-sync works without problems no need to write custom scripts
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 /var/git/meta-repo/repos.conf/chopin.conf [chopin] location = /var/git/overlay/chopin masters = core-kit auto-sync = no priority = 10
-
copy all the kits and prepend them with ego-
-
Another point. Earlier I said this...
On 11/22/2017 at 5:19 PM, dkg said:On another system, eix simply returns old results, but I may have done something to nuke it's cache. I'm not sure.
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.
-
1 hour ago, palica said:
you want probably
L10N="${LINGUAS}" in your make.conf
for the useflags I would suggest to remove them from make.conf and use profiles instead
for example
gif jpeg png tiff flac ogg vorbis mp3
are all in audio and media mix-ins which are part of workstation flavor which is part of desktop flavor
so selecting desktop flavor has you covered with most of them
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.
-
1 hour ago, cardinal said:
@dkg
Post output:
eix --print PORTDIReix --print PORTDIR_OVERLAYSorry. 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 warning: ignoring parent core-kit:funtoo/1.0/linux-gnu/arch/x86-64bit/subarch/corei7 of file /etc/portage/make.profile/parent warning: ignoring parent core-kit:funtoo/1.0/linux-gnu/flavor/desktop of file /etc/portage/make.profile/parent warning: ignoring parent core-kit:funtoo/1.0/linux-gnu/mix-ins/lxqt of file /etc/portage/make.profile/parent warning: ignoring parent core-kit:funtoo/1.0/linux-gnu/mix-ins/no-systemd of file /etc/portage/make.profile/parent warning: ignoring parent core-kit:funtoo/1.0/linux-gnu/mix-ins/kde-plasma-5 of file /etc/portage/make.profile/parent warning: ignoring parent editors-kit:funtoo/kits/python-kit/3.4-prime of file /etc/portage/make.profile/parent warning: ignoring parent text-kit:funtoo/kits/python-kit/3.4-prime of file /etc/portage/make.profile/parent warning: ignoring parent dev-kit:funtoo/kits/python-kit/3.4-prime of file /etc/portage/make.profile/parent warning: ignoring parent perl-kit:funtoo/kits/python-kit/3.4-prime of file /etc/portage/make.profile/parent warning: ignoring parent games-kit:funtoo/kits/python-kit/3.4-prime of file /etc/portage/make.profile/parent warning: ignoring parent lisp-scheme-kit:funtoo/kits/python-kit/3.4-prime of file /etc/portage/make.profile/parent warning: ignoring parent desktop-kit:funtoo/kits/python-kit/3.4-prime of file /etc/portage/make.profile/parent warning: ignoring parent net-kit:funtoo/kits/python-kit/3.4-prime of file /etc/portage/make.profile/parent warning: ignoring parent xorg-kit:funtoo/kits/python-kit/3.4-prime of file /etc/portage/make.profile/parent warning: ignoring parent media-kit:funtoo/kits/python-kit/3.4-prime of file /etc/portage/make.profile/parent warning: ignoring parent ml-lang-kit:funtoo/kits/python-kit/3.4-prime of file /etc/portage/make.profile/parent warning: ignoring parent security-kit:funtoo/kits/python-kit/3.4-prime of file /etc/portage/make.profile/parent warning: ignoring parent haskell-kit:funtoo/kits/python-kit/3.4-prime of file /etc/portage/make.profile/parent warning: ignoring parent nokit:funtoo/kits/python-kit/3.4-prime of file /etc/portage/make.profile/parent warning: ignoring parent java-kit:funtoo/kits/python-kit/3.4-prime of file /etc/portage/make.profile/parent warning: ignoring parent core-hw-kit:funtoo/kits/python-kit/3.4-prime of file /etc/portage/make.profile/parent warning: ignoring parent core-kit:funtoo/kits/python-kit/3.4-prime of file /etc/portage/make.profile/parent warning: ignoring parent php-kit:funtoo/kits/python-kit/3.4-prime of file /etc/portage/make.profile/parent warning: ignoring parent gnome-kit:funtoo/kits/python-kit/3.4-prime of file /etc/portage/make.profile/parent warning: ignoring parent ruby-kit:funtoo/kits/python-kit/3.4-prime of file /etc/portage/make.profile/parent warning: ignoring parent kde-kit:funtoo/kits/python-kit/3.4-prime of file /etc/portage/make.profile/parent warning: ignoring parent python-kit:funtoo/kits/python-kit/3.4-prime of file /etc/portage/make.profile/parent warning: ignoring parent xfce-kit:funtoo/kits/python-kit/3.4-prime of file /etc/portage/make.profile/parent warning: ignoring parent science-kit:funtoo/kits/python-kit/3.4-prime of file /etc/portage/make.profile/parent warning: ignoring parent lang-kit:funtoo/kits/python-kit/3.4-prime of file /etc/portage/make.profile/parent /usr/portage/
[root@chopin repos.conf]# eix --print PORTDIROVERLAY 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 warning: ignoring parent core-kit:funtoo/1.0/linux-gnu/arch/x86-64bit/subarch/corei7 of file /etc/portage/make.profile/parent warning: ignoring parent core-kit:funtoo/1.0/linux-gnu/flavor/desktop of file /etc/portage/make.profile/parent warning: ignoring parent core-kit:funtoo/1.0/linux-gnu/mix-ins/lxqt of file /etc/portage/make.profile/parent warning: ignoring parent core-kit:funtoo/1.0/linux-gnu/mix-ins/no-systemd of file /etc/portage/make.profile/parent warning: ignoring parent core-kit:funtoo/1.0/linux-gnu/mix-ins/kde-plasma-5 of file /etc/portage/make.profile/parent warning: ignoring parent editors-kit:funtoo/kits/python-kit/3.4-prime of file /etc/portage/make.profile/parent warning: ignoring parent text-kit:funtoo/kits/python-kit/3.4-prime of file /etc/portage/make.profile/parent warning: ignoring parent dev-kit:funtoo/kits/python-kit/3.4-prime of file /etc/portage/make.profile/parent warning: ignoring parent perl-kit:funtoo/kits/python-kit/3.4-prime of file /etc/portage/make.profile/parent warning: ignoring parent games-kit:funtoo/kits/python-kit/3.4-prime of file /etc/portage/make.profile/parent warning: ignoring parent lisp-scheme-kit:funtoo/kits/python-kit/3.4-prime of file /etc/portage/make.profile/parent warning: ignoring parent desktop-kit:funtoo/kits/python-kit/3.4-prime of file /etc/portage/make.profile/parent warning: ignoring parent net-kit:funtoo/kits/python-kit/3.4-prime of file /etc/portage/make.profile/parent warning: ignoring parent xorg-kit:funtoo/kits/python-kit/3.4-prime of file /etc/portage/make.profile/parent warning: ignoring parent media-kit:funtoo/kits/python-kit/3.4-prime of file /etc/portage/make.profile/parent warning: ignoring parent ml-lang-kit:funtoo/kits/python-kit/3.4-prime of file /etc/portage/make.profile/parent warning: ignoring parent security-kit:funtoo/kits/python-kit/3.4-prime of file /etc/portage/make.profile/parent warning: ignoring parent haskell-kit:funtoo/kits/python-kit/3.4-prime of file /etc/portage/make.profile/parent warning: ignoring parent nokit:funtoo/kits/python-kit/3.4-prime of file /etc/portage/make.profile/parent warning: ignoring parent java-kit:funtoo/kits/python-kit/3.4-prime of file /etc/portage/make.profile/parent warning: ignoring parent core-hw-kit:funtoo/kits/python-kit/3.4-prime of file /etc/portage/make.profile/parent warning: ignoring parent core-kit:funtoo/kits/python-kit/3.4-prime of file /etc/portage/make.profile/parent warning: ignoring parent php-kit:funtoo/kits/python-kit/3.4-prime of file /etc/portage/make.profile/parent warning: ignoring parent gnome-kit:funtoo/kits/python-kit/3.4-prime of file /etc/portage/make.profile/parent warning: ignoring parent ruby-kit:funtoo/kits/python-kit/3.4-prime of file /etc/portage/make.profile/parent warning: ignoring parent kde-kit:funtoo/kits/python-kit/3.4-prime of file /etc/portage/make.profile/parent warning: ignoring parent python-kit:funtoo/kits/python-kit/3.4-prime of file /etc/portage/make.profile/parent warning: ignoring parent xfce-kit:funtoo/kits/python-kit/3.4-prime of file /etc/portage/make.profile/parent warning: ignoring parent science-kit:funtoo/kits/python-kit/3.4-prime of file /etc/portage/make.profile/parent warning: ignoring parent lang-kit:funtoo/kits/python-kit/3.4-prime of file /etc/portage/make.profile/parent
-
13 minutes ago, cardinal said:
Your funtoo symlink ends with //
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".
15 minutes ago, cardinal said:Check your eix PORTDIR and PORTDIR_OVERLAY variables after you fix the symlink. If they don't match mine with the exception of my "/usr/local/portage" personal overlay you may have a PORTDIR = "/usr/portage" defined in /etc/portage/make.conf that has to be removed.
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_DEFAULT_OPTS="--with-bdeps=y --ask --quiet-build=y --autounmask=n" FETCHCOMMAND="/usr/bin/wget --limit-rate=200k --timeout=60 --tries=3 --passive-ftp -O \"\${DISTDIR}/\${FILE}\" \"\${URI}\"" RESUMECOMMAND="/usr/bin/wget -c --limit-rate=200k --timeout=60 --tries=3 --passive-ftp -O \"\${DISTDIR}/\${FILE}\" \"\${URI}\"" PORTAGE_ELOG_SYSTEM="save_summary:log,warn,error mail_summary:log,warn,error echo" PORTAGE_ELOG_MAILURI="dave@gasaway.org /usr/bin/sendmail" PORTAGE_ELOG_MAILFROM="portage@nymph.dakega.info" FEATURES="clean-logs" USE="consolekit gif jpeg png tiff flac ogg vorbis mp3 opus -iptables -networkmanager -upower -ldap -nls -pulseaudio -handbook -ppp" VIDEO_CARDS="radeon radeonsi" #VIDEO_CARDS="fglrx" LINGUAS="en en_US en_DK de_AT" ABI_X86="64 32" INPUT_DEVICES="evdev roccat_konepure" -
1 minute ago, palica said:
sorry. my bad about new-repo. But should help you with packages being displayed as not installed in eix output.
can you list
/var/git/meta-repo/repos.conf
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------- 1 portage portage 83 Sep 17 11:38 core-kit -rw------- 1 portage portage 31 Sep 17 11:38 default -rw------- 1 portage portage 89 Sep 17 11:38 desktop-kit -rw------- 1 portage portage 81 Sep 17 11:38 dev-kit -rw------- 1 portage portage 89 Sep 17 11:38 editors-kit -rw------- 1 portage portage 85 Sep 17 11:38 games-kit -rw------- 1 portage portage 86 Sep 17 11:38 gnome-kit -rw------- 1 portage portage 89 Oct 28 14:14 haskell-kit -rw------- 1 portage portage 83 Sep 17 11:38 java-kit -rw------- 1 portage portage 81 Sep 17 11:38 kde-kit -rw------- 1 portage portage 83 Oct 28 14:14 lang-kit -rw------- 1 portage portage 97 Oct 28 14:14 lisp-scheme-kit -rw------- 1 portage portage 85 Sep 17 11:38 media-kit -rw------- 1 portage portage 89 Oct 28 14:14 ml-lang-kit -rw------- 1 portage portage 81 Sep 17 11:38 net-kit -rw------- 1 portage portage 81 Sep 17 11:38 nokit -rw------- 1 portage portage 83 Sep 17 11:38 perl-kit -rw------- 1 portage portage 81 Sep 17 11:38 php-kit -rw------- 1 portage portage 87 Sep 17 11:38 python-kit -rw------- 1 portage portage 83 Oct 28 14:14 ruby-kit -rw------- 1 portage portage 90 Sep 17 11:38 science-kit -rw------- 1 portage portage 91 Sep 17 11:38 security-kit -rw------- 1 portage portage 83 Sep 17 11:38 text-kit -rw------- 1 portage portage 83 Oct 28 14:14 xfce-kit -rw------- 1 portage portage 83 Sep 17 11:38 xorg-kit
The chopin.conf file is for a local overlay on this system. The other system where I have eix issues does not have a local overlay. If eix is working for you, please describe any steps taken beyond those in the meta-repo migration guide.
-
3 minutes ago, Oleg Vinichenko said:
sorry, --newrepo, it was typo with --new-repo
WOW! That is going to rebuild the whole system (922 packages). That's what I need to do to fix eix?
-
2 hours ago, palica said:
What your ego version?
You probably have to run emerge -avuDN @world --new-repo
[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-primeWhat is '--new-repo' supposed to do? As far as I can see, that is not a valid argument to emerge.
-
2 hours ago, palica said:
Paste your
/etc/portage/make.profile/parent
Paste what is in your /etc/portage/repos.conf direcotry
[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-prime lisp-scheme-kit:funtoo/kits/python-kit/3.4-prime desktop-kit:funtoo/kits/python-kit/3.4-prime net-kit:funtoo/kits/python-kit/3.4-prime xorg-kit:funtoo/kits/python-kit/3.4-prime media-kit:funtoo/kits/python-kit/3.4-prime ml-lang-kit:funtoo/kits/python-kit/3.4-prime security-kit:funtoo/kits/python-kit/3.4-prime haskell-kit:funtoo/kits/python-kit/3.4-prime nokit:funtoo/kits/python-kit/3.4-prime java-kit:funtoo/kits/python-kit/3.4-prime core-hw-kit:funtoo/kits/python-kit/3.4-prime core-kit:funtoo/kits/python-kit/3.4-prime php-kit:funtoo/kits/python-kit/3.4-prime gnome-kit:funtoo/kits/python-kit/3.4-prime ruby-kit:funtoo/kits/python-kit/3.4-prime kde-kit:funtoo/kits/python-kit/3.4-prime python-kit:funtoo/kits/python-kit/3.4-prime xfce-kit:funtoo/kits/python-kit/3.4-prime science-kit:funtoo/kits/python-kit/3.4-prime lang-kit:funtoo/kits/python-kit/3.4-prime
[root@chopin ~]# ls -l /etc/portage/repos.conf total 8 drwx------ 2 root root 4096 Oct 19 21:13 ./ drwxr-xr-x 9 root root 4096 Oct 19 21:12 ../ lrwxrwxrwx 1 root root 30 Oct 19 21:13 funtoo -> /var/git/meta-repo/repos.conf// [root@chopin ~]#
-
On 11/22/2017 at 10:57 PM, jhan said:
There seems to be something wrong on your system, as eix still reports old versions of eix as available. When I look at my portage tree on my system, there is only an ebuild for version 0.32.9-r1.
Also the warning messages about your parent file suggest that the content of your parent file is not correct. Could you post the parent file?
Because eix's database is out-of-date. Those are not actually the ebuilds available.
-
Never mind. I think logitechmediaserver-bin was the source of all my problems.
-
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 =dev-lang/perl-5.24* >>> virtual/perl-Getopt-Long-2.480.0-r1:0/0::perl-kit, ebuild scheduled for merge, wants =dev-lang/perl-5.24* >>> virtual/perl-Test-Harness-3.360.0-r1:0/0::perl-kit, ebuild scheduled for merge, wants =dev-lang/perl-5.24* >>> virtual/perl-JSON-PP-2.273.0-r4:0/0::gentoo, installed, wants =dev-lang/perl-5.24.0* >>> virtual/perl-CPAN-Meta-2.150.5-r1:0/0::perl-kit, ebuild scheduled for merge, wants =dev-lang/perl-5.24* >>> virtual/perl-ExtUtils-MakeMaker-7.100.100_rc-r2:0/0::perl-kit, ebuild scheduled for merge, wants =dev-lang/perl-5.24.0* >>> virtual/perl-Digest-MD5-2.540.0-r2:0/0::gentoo, installed, wants =dev-lang/perl-5.24* >>> virtual/perl-Data-Dumper-2.160.0-r1:0/0::perl-kit, ebuild scheduled for merge, wants =dev-lang/perl-5.24* >>> virtual/perl-ExtUtils-ParseXS-3.310.0-r1:0/0::perl-kit, ebuild scheduled for merge, wants =dev-lang/perl-5.24* >>> virtual/perl-version-0.991.600-r1:0/0::perl-kit, ebuild scheduled for merge, wants =dev-lang/perl-5.24* >>> virtual/perl-Text-ParseWords-3.300.0-r2:0/0::gentoo, installed, wants =dev-lang/perl-5.24* >>> virtual/perl-Carp-1.400.0-r1:0/0::perl-kit, ebuild scheduled for merge, wants =dev-lang/perl-5.24* >>> virtual/perl-podlators-4.70.0-r1:0/0::perl-kit, ebuild scheduled for merge, wants =dev-lang/perl-5.24* >>> virtual/perl-ExtUtils-Install-2.40.0-r2:0/0::gentoo, installed, wants =dev-lang/perl-5.24* >>> virtual/perl-ExtUtils-Manifest-1.700.0-r3:0/0::gentoo, installed, wants =dev-lang/perl-5.24* >>> virtual/perl-Compress-Raw-Zlib-2.69.0-r1:0/0::perl-kit, ebuild scheduled for merge, wants =dev-lang/perl-5.24* >>> virtual/perl-ExtUtils-CBuilder-0.280.225-r1:0/0::perl-kit, ebuild scheduled for merge, wants =dev-lang/perl-5.24* >>> virtual/perl-IO-Compress-2.69.0-r2:0/0::perl-kit, ebuild scheduled for merge, wants =dev-lang/perl-5.24.0* >>> virtual/perl-File-Spec-3.630.0-r2:0/0::perl-kit, ebuild scheduled for merge, wants =dev-lang/perl-5.24.0* >>> virtual/perl-IO-1.360.0-r2:0/0::perl-kit, ebuild scheduled for merge, wants =dev-lang/perl-5.24.0* >>> virtual/perl-Perl-OSType-1.9.0-r1:0/0::perl-kit, ebuild scheduled for merge, wants =dev-lang/perl-5.24* >>> virtual/perl-Compress-Raw-Bzip2-2.69.0-r1:0/0::perl-kit, ebuild scheduled for merge, wants =dev-lang/perl-5.24* >>> virtual/perl-Module-Metadata-1.0.31-r1:0/0::perl-kit, ebuild scheduled for merge, wants =dev-lang/perl-5.24* >>> virtual/perl-Digest-SHA-5.950.0-r4:0/0::gentoo, installed, wants =dev-lang/perl-5.24.0* >>> virtual/perl-Text-Balanced-2.30.0-r2:0/0::gentoo, installed, wants =dev-lang/perl-5.24* >>> virtual/perl-MIME-Base64-3.150.0-r2:0/0::gentoo, installed, wants =dev-lang/perl-5.24* >>> virtual/perl-libnet-3.80.0-r1:0/0::perl-kit, ebuild scheduled for merge, wants =dev-lang/perl-5.24* >>> dev-perl/Data-UUID-1.221.0:0/0::gentoo, installed, wants dev-lang/perl:0/5.22= >>> dev-python/subunit-1.2.0-r1:0/0::gentoo, installed, wants dev-lang/perl:0/5.22= >>> virtual/perl-MIME-Base64-3.150.0-r2:0/0::gentoo, installed, wants dev-lang/perl:0/5.22= >>> virtual/perl-ExtUtils-Install-2.40.0-r2:0/0::gentoo, installed, wants dev-lang/perl:0/5.22= >>> virtual/perl-ExtUtils-Manifest-1.700.0-r3:0/0::gentoo, installed, wants dev-lang/perl:0/5.22= >>> virtual/perl-Digest-SHA-5.950.0-r4:0/0::gentoo, installed, wants dev-lang/perl:0/5.22= >>> app-text/po4a-0.47-r2:0/0::core-kit, installed, wants dev-lang/perl:0/5.22= >>> perl-core/File-Temp-0.230.400-r1:0/0::gentoo, installed, wants dev-lang/perl:0/5.22= >>> dev-perl/Text-WrapI18N-0.60.0-r1:0/0::gentoo, installed, wants dev-lang/perl:0/5.22= >>> dev-perl/File-Copy-Recursive-0.380.0-r1:0/0::gentoo, installed, wants dev-lang/perl:0/5.22= >>> dev-perl/Text-CharWidth-0.40.0-r1:0/0::gentoo, installed, wants dev-lang/perl:0/5.22= >>> dev-perl/Parse-RecDescent-1.967.13:0/0::gentoo, installed, wants dev-lang/perl:0/5.22= >>> dev-perl/Net-SMTP-SSL-1.30.0:0/0::gentoo, installed, wants dev-lang/perl:0/5.22= >>> dev-perl/Unicode-String-2.90.0-r1:0/0::gentoo, installed, wants dev-lang/perl:0/5.22= >>> virtual/perl-Text-Balanced-2.30.0-r2:0/0::gentoo, installed, wants dev-lang/perl:0/5.22= >>> dev-perl/Socket6-0.270.0:0/0::perl-kit, installed, wants dev-lang/perl:0/5.22= >>> virtual/perl-File-Temp-0.230.400-r5:0/0::gentoo, installed, wants dev-lang/perl:0/5.22= >>> virtual/perl-Text-ParseWords-3.300.0-r2:0/0::gentoo, installed, wants dev-lang/perl:0/5.22= >>> dev-vcs/git-2.11.1-r1:0/0::core-kit, installed, wants dev-lang/perl:0/5.22= >>> media-sound/logitechmediaserver-bin-9999:0/0::gentoo, installed, wants <dev-lang/perl-5.23[ithreads] >>> dev-perl/Error-0.170.240:0/0::gentoo, installed, wants dev-lang/perl:0/5.22= >>> virtual/perl-Digest-MD5-2.540.0-r2:0/0::gentoo, installed, wants dev-lang/perl:0/5.22= >>> dev-perl/Authen-SASL-2.160.0-r1:0/0::gentoo, installed, wants dev-lang/perl:0/5.22= >>> dev-perl/XML-Parser-2.440.0:0/0::gentoo, installed, wants dev-lang/perl:0/5.22= >>> dev-perl/TermReadKey-2.330.0:0/0::gentoo, installed, wants dev-lang/perl:0/5.22= >>> dev-perl/IO-Socket-INET6-2.720.0:0/0::perl-kit, installed, wants dev-lang/perl:0/5.22= >>> dev-perl/Sys-MemInfo-0.980.0:0/0::perl-kit, installed, wants dev-lang/perl:0/5.22= >>> dev-perl/Unicode-EastAsianWidth-1.330.0-r1:0/0::gentoo, installed, wants dev-lang/perl:0/5.22= >>> dev-perl/Digest-HMAC-1.30.0-r1:0/0::gentoo, installed, wants dev-lang/perl:0/5.22= >>> virtual/perl-JSON-PP-2.273.0-r4:0/0::gentoo, installed, wants dev-lang/perl:0/5.22= >>> dev-perl/IO-Tee-0.640.0-r1:0/0::gentoo, installed, wants dev-lang/perl:0/5.22= My candidates are: >>> dev-lang/perl-5.24.0-r2:0/5.24::perl-kit, ebuild scheduled for merge has SLOT 0/5.24 >>> dev-lang/perl-5.22.2:0/5.22::perl-kit, ebuild scheduled for merge has SLOT 0/5.22
-
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:funtoo/1.0/linux-gnu/build/current of file /etc/portage/make.profile/parent warning: ignoring parent core-kit:funtoo/1.0/linux-gnu/arch/x86-64bit/subarch/corei7 of file /etc/portage/make.profile/parent warning: ignoring parent core-kit:funtoo/1.0/linux-gnu/flavor/desktop of file /etc/portage/make.profile/parent warning: ignoring parent core-kit:funtoo/1.0/linux-gnu/mix-ins/lxqt of file /etc/portage/make.profile/parent warning: ignoring parent core-kit:funtoo/1.0/linux-gnu/mix-ins/no-systemd of file /etc/portage/make.profile/parent warning: ignoring parent core-kit:funtoo/1.0/linux-gnu/mix-ins/kde-plasma-5 of file /etc/portage/make.profile/parent
Then notice the results on this system...
[?] app-portage/eix Available versions: 0.32.4 ~0.32.5 ~0.32.5-r1 ~0.32.9 {debug doc linguas_de linguas_ru nls sqlite} Installed versions: 0.32.9-r1[?](02:00:06 PM 10/19/2017)(-debug -doc -linguas_de -linguas_ru -nls -sqlite) Homepage: https://github.com/vaeth/eix/ Description: Search and query ebuildsThe Available versions are outdated. I believe what it is updating based on the old /usr/portage tree. On another system where I removed /usr/portage, eix just always returns no results. Running 'eix-update' or 'eix-sync -u' do not correct the situation. In fact, if I remove /usr/portage, then it will complain about missing /usr/portage files...
[root@chopin portage]# eix-update Reading Portage settings... [... Warnings removed ...] Building database (/var/cache/eix/portage.eix)... cannot open /usr/portage/profiles/categories: No such file or directory [0] "" /usr/portage/ (cache: metadata-md5-or-flat) Reading category 0|0 (100) EMPTY! Applying masks... Calculating hash tables... Writing database file /var/cache/eix/portage.eix... Database contains 0 packages in 0 categoriesOn another system, eix simply returns old results, but I may have done something to nuke it's cache. I'm not sure. I'm using default branches for all kits on these systems. One system does have a local overlay, but I don't think that's the problem. What else do I need to do to get eix working?
-
13 hours ago, drobbins said:
Try creating an /etc/local.d/dropbox.start script that will start dropbox as the user of your choice when the system boots:
#!/bin/bash su username -c "/usr/bin/dropbox start"
Then...
# chmod +x /etc/local.d/dropbox.start
Seems to work just fine, thanks!
-
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?
-
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' did work fine, though. Thanks guys.
-
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?
-
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.
-
not necessarily, default branch could also contain ebuilds with stable and unstable ebuilds. by deviating into master (or other) branch unstable ebuilds will prevail, i believe.
Ah, so there could be more than one branch available for a given kit. I wasn't sure about that.
-
yes, in master branches, the ebuilds will be with keywords as they are, stable and unstable as gentoo puts them
Thanks. Is this also what I would get by "deviating from a default kit branch"?
-
Funtoo Linux with the default kits will be very similar to the old 'stable', with fewer updates. Users who want more bleeding-edge will need to deviate from our default kit branches and will need an upcoming version of ego to do this.
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?
-
No. You can actually test what will be the result by testing meta-repo (a successor of portage tree).
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.
-
that's the goal of kits, the package list defined by kit will be less frequent updated and it will more controlled and predictable is what makes stable rebundant at some point.
That's the goal of kits? What I read was the following:
The mantra and vision of kits is as follows: "If my system becomes unstable, I want it to become unstable because I choose to use a more experimental or new set of packages, not just because I applied regular updates via emerge -auDN @world" This is the strategic vision of the effort and what we are striving to deliver. At the same time, we don't want to take away the ability of users to run newer versions of packages if they choose.
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?
-
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.
Getting eix to work with kits
in Portage Help
Posted
I'm sorry. I fail to see how this will get eix to stop looking for /usr/portage. Will it fix the warnings? Is this what you have done to get eix to work?
(I have no /usr/share/portage/config/repos.conf file, by the way.)