Jump to content
funtoo forums

All Activity

This stream auto-updates     

  1. Today
  2. Trouble with LINGUAS

    Already done. But is this normal, that LINGUAS doesn't work for portage?
  3. Hello, I just wanted to ask if there is any chance to get rid of all Gnome related packages in a KDE environment. For example Pulseaudio pulls in Gnome package even if I have -gnome in make.conf and -gnome USE flag for pulseaudio itself. Gnome Kit is still updated as well. GTK was installed automatically with some packages depending on it too. Are Gnome/GTK packages still needed for plasma/KDE stuff? Thanks for your help regards Checko
  4. Yesterday
  5. Trouble with LINGUAS

    add as a USE on package.use will work
  6. PAM: faillock integration

    pam-1.3.0-r3 ebuild introducing the faillock capability from Red Hat. This will allow locking of user account after a consequent login failure attempts. After a number of attempts (can be configured) the account will be locked for a certain time (can be configured). Testing can be performed by following. Set the keywords for sys-libs/pam ebuild and install new version. echo "=sys-libs/pam-1.3.0-r3 **" >> /etc/portage/package.accept_keywords emerge -1u pam After installation, edit /etc/pam.d/system-auth with editor and put the lines pointed auth required pam_env.so auth required pam_faillock.so preauth audit deny=3 unlock_time=60 auth required pam_unix.so try_first_pass likeauth nullok auth required pam_faillock.so authfail audit deny=3 fail_interval=60 unlock_time=60 auth optional pam_permit.so account required pam_faillock.so account required pam_unix.so account optional pam_permit.so password required pam_cracklib.so difok=2 minlen=8 dcredit=2 ocredit=2 retry=3 password required pam_unix.so try_first_pass use_authtok nullok sha512 shadow password optional pam_permit.so session required pam_limits.so session required pam_env.so session required pam_unix.so session optional pam_permit.so Notice the lines in bold red. This is very important that first line in auth part is before pam_unix module. The second line must be after pam_unix module. In account part, pam_faillock module needed before pam_unix module. In example, 3 attempts are set for the locking. After that, account will be locked and in console you will see a message that account is locked for 60 seconds, in example. After that period of time, the account will be released. To review the state , you can use faillock utility installed by pam. For more advanced options, follow faillock and pam_faillock manual pages. If some mistakes possibly made with configuration, please, have a live cd to boot from to alter the changes in /etc/pam.d/system-auth. It is wise decision to have a copy of it somewhere before the tests.
  7. Trouble with LINGUAS

    P.S. It seems that #funtoo irc channel is disappear. Is anybody use it?
  8. Trouble with LINGUAS

    Hi, everybody. Try to upgrade portage and got: [ebuild R ] sys-apps/portage-2.3.41 USE="-linguas_ru*" In emerge -p output. While in make.conf: LINGUAS="en ru" What wrong with LINGUAS and what can i do to fix this? Thanks!
  9. NGINX ebuilds available to test

    Following version of nginx available to test: =www-servers/nginx-1.14.0 the stable release =www-server/nginx-1.15.2 the mainline release To test either one or both, add following to /etc/portage/package.accept_keywords, example with 1.14.0 is shown below =www-servers/nginx-1.14.0 ** Testing feedback is very much appreciated.
  10. Outdated Desktop Environments

    Main reason is to have users who are experienced KDE users and understand about possible quirks during updates. This does no necessarily means that its needed to be good at writing ebuilds, but it' s of course much better if you can. The way it can be tested is using the generation of a tree that will contain the updated stack of what is forming the KDE. How to perform this is described in: https://www.funtoo.org/Local_Development_Setup Assuming that you have KDE of older kit branch installed, then, you can generate a new tree that track gentoo master ebuilds for KDE. Or LXQT. Then, you can try updating and hunting for update troubles that can be faced during this step. There could be quite a list of inter-connected issues, considering that KDE and QT are big projects. Eliminating and fixing such pitfalls and also documenting about upgrade steps are the basics. When it's known to be reliable, then, the kit can be locked down and released. Next releases can be then considered to work on. It very much looking as semi-rolling. It can be helped and supported by us with technical difficulties and questions.
  11. Improving on a good thing.

    Hmm...if I understand all that correctly, it sounds to me that you are complicating the matter. I would just write myself a simple script which would do the following: - Do a pre-install snapshot - emerge everything (or do other damaging stuff) - Do a post-install snapshot I see no need to involve portage in it, other than it is intended to do already. But I might not be understand what you are trying to accomplish here. In that case please elaborate.
  12. XA state tracker failure with mesa 18.2.0-rc2

    mesa here is still in 17.2.8 i need 18.1.6 i think dxvk ask for newer version of mesa.
  13. Last week
  14. Outdated Desktop Environments

    I mentioned this on the bug tracker as well: I'm willing to help out, I'm just not sure how to go about starting that. Specifically, I'm not sure what "funtoo-style" testing is and how or whether I would do that. Also, if I have updated ebuilds, would I attach them to their own issues on JIRA, a single issue (e.g. "Updated LXQt ebuilds"), or give a link to a git overlay? I've decided to start working on updating LXQt, since that looks like a more manageable task right now. I'm only going to do manual testing and any tests included with the source code, unless there's more to "funtoo-style" testing that I should do.
  15. Improving on a good thing.

    OK, I have do my tests and this is what I have found: 1.) While the script in the Gentoo wiki will generate pre-install snapshots it will not generate post-install snapshots. 2.) As I feared, the script in the Gentoo wiki is triggered per ebuild install phase. This means that you get one snapshot per package Portage installs. This is a bad thing because snapper limits the amount of snapshots it stores and in a large emerge run you might end up overwriting some of the snapshots you made just a while ago. For this to be really effective Portage would have tell snapper to make a pre snapshot during the pre-compile phase after it does all of it's sanity checks. Then after the last package is installed and about the same time Portage gives the output messages from all of the packages it would need to call on snapper again to make it's post snapshot. Snapper does do timeline snapshots correctly with cronie installed though, so that is about 75% of what I want right there. So from here I'll start backing up my server and get it reinstalled with a btrfs raid10. I am unsure of how to go about officially requesting the changes I desire or if these changes are really feasible. If anyone working with Portage cares to comment I would be grateful to hear your thoughts on the subject.
  16. Improving on a good thing.

    Thank you very much for the link. Tomorrow I'll spin up a new Funtoo VM and test this out. If it works as expected is the proper procedure to file a bug against btrfs-progs for a use flag to pull in snapper on request and another bug against snapper to add a use flag for portage auto snapshots via /etc/portage/bashrc?
  17. Improving on a good thing.

    I've looked at this myself, as I run Funtoo on all of my systems with btrfs as the root filesystem. I found this page on the Gentoo Wiki, which outlines a way to take pre- and post-snapshots when using Portage. Haven't tried it yet.
  18. Improving on a good thing.

    Hi, I hope this is the right place to post this. A bit of background that can be skipped if you are in a hurry: I am by no means a programmer and try hard just to stay out of the way and keep my head down when using open source software. I've been using Funtoo for a long time now on my home servers. These systems started as lab style "blow them away at the drop of a hat when things go bad while flying by the seat of my pants learning a thing or two along the way" machines but over the years they have evolved into a much more stable pattern. I have a desktop for gaming but I don't run Funtoo on it, choosing Mint instead because "It just works" most of the time. One of the things that bothers me about Mint is the lack of real data protection in the default install so I set up a raid like I do with my server but instead of mdadm I used brtfs, This means that the default filesystem snapshot tool in Mint (TimeShift) can't work on my system. So I dug around and found a very cool utility called "snapper" that auto snapshots my btrfs filesystem. It does this transparently in the back ground and can be configured to keep so many hourly, daily, weekly (and so on) snapshots. The cool thing is that it makes a pre and post snapshot every time I unistall or uninstall software with apt. I looked for snapper in portage and it's there. This has me thinking about starting a fresh install of Funtoo on my server and using btrfs raid10 and having snapper as a second layer of system protection. So to the point: Can snapper automatically snapshot a btrfs filesystem before and after an emerge command is executed? If not would making it do so be trivial or non-trivial? If it does so or can easily be made to do so why not add a snapper use flag to btrfs-progs so it would be pulled in if desired by the system admin? This is the kind of idea I normally keep to myself because I can't write it and I tell myself "If it was that good of an idea it would be done already." In this case it's something I really would like to have and it would benefit so many people using both Funtoo and Gentoo that I felt I should at least ask.
  19. Outdated Desktop Environments

    We need maintainers for non-GNOME desktop environments who will help us test and maintain kits. Please let me know if you are interested in doing this. The primary reason the DE's are out-of-date is because we need some people to volunteer to maintain the DE's and apply funtoo-style testing to them. We don't want to just track Gentoo's changes since we then have no process to ensure things are working as things get updated.
  20. Many things to test

    The following ebuilds are available for testing by end users and are currently keyword-masked. Add the following to your package.accept_keywords to test: =sys-apps/portage-2.3.47 ** =sys-devel/gcc-7.3.1-r3 ** =sys-apps/corenetwork-1.6.4 ** =x11-drivers/xf86-video-intel-2.99.917_p20180609 ** Here is a quick review of changes in the above packages. Portage is a new version from Gentoo, which has passed all unit tests. Gcc-7.3.1-r3 is a much-improved ebuild from @Temptorsent which now enables SSP by default for improved security. Corenetwork-1.6.4 has some bug fixes that have accumulated in git, and the new xf86-video-intel is the latest from git and needs testing, particularly on newer intel hardware like Coffee Lake and Kaby Lake refresh -- and it always seems like google chrome has rendering issues, so be sure to test Chrome with this driver. Please test these things and report back your experiences.
  21. Outdated Desktop Environments

    Gentoo has KDE Plasma 5.13 (and qt 5.11) in normal portage, no need to use testing. PS: You could also use the ebuilds in my overlay, if you don't want to sync the whole Gentoo tree (they are imported from Gentoo), though they may be behind slightly in the release version (the 'x' in 5.13.x)
  22. eix-update broken

    Right, I gave it a try but it doesn't fix anything. I also noted an empty PORTAGE_OVERLAY vs my desktop. I think something is wrong with my portage setup... on container : # eix-update --print PORTDIR_OVERLAY # on desktop: # eix-update --print PORTDIR_OVERLAY /var/git/meta-repo/kits/core-hw-kit /var/git/meta-repo/kits/desktop-kit /var/git/meta-repo/kits/dev-kit (...) /var/git/meta-repo/kits/xorg-kit # cat /etc/portage/make.conf MAKEOPTS="-j7" USE="php geoip php pdo mysql curl zip xslt xmlreader xmlwriter" USE="$USE vhosts luajit" #PORTDIR="/var/git/meta-repo/kits/core-kit" NGINX_MODULES_EXTERNAL="accept_language lua luajit headers_more" NGINX_MODULES_STREAM="geoip realip ssl_preread access geo limit_conn map return split_clients upstream_hash upstream_least_conn upstream_zone" PHP_TARGETS="php7-1 php7-2 php7-3" DISTDIR=/var/cache/portage/distfiles PORTAGE_BINHOST=https://bin.host.funtoo.org/intel64-westmere # emerge --info !!! Repository 'ruby-kit' is missing masters attribute in '/var/git/meta-repo/kits/ruby-kit/metadata/layout.conf' !!! Set 'masters = core-kit' in this file for future compatibility WARNING: One or more repositories have missing repo_name entries: /var/git/meta-repo/kits/ruby-kit/profiles/repo_name NOTE: Each repo_name entry should be a plain text file containing a unique name for the repository on the first line. Portage 2.3.41 (python 3.6.5-final-0, funtoo/1.0/linux-gnu/arch/x86-64bit, gcc-7.3.1, glibc-2.26-r7, 4.9.110-1 x86_64) ================================================================= System uname: Linux-4.9.110-1-x86_64-Intel-R-_Xeon-R-_CPU_E7-_4870_@_2.40GHz-with-gentoo-2.2.2 KiB Mem: 4194304 total, 1939780 free KiB Swap: 134217724 total, 133923280 free sh bash 4.4_p18 ld GNU ld (Gentoo 2.29.1 p3) 2.29.1 app-shells/bash: 4.4_p18::core-kit dev-java/java-config: 2.2.0-r3::java-kit dev-lang/perl: 5.24.0-r3::perl-kit dev-lang/python: 2.7.14-r2::python-kit, 3.6.5-r1::python-kit dev-util/cmake: 3.10.1::core-kit sys-apps/baselayout: 2.2.2::core-kit sys-apps/openrc: 0.35.5::core-kit sys-apps/sandbox: 2.12::core-kit sys-devel/autoconf: 2.69-r4::core-kit sys-devel/automake: 1.13.4-r1::core-kit, 1.15.1-r1::core-kit sys-devel/binutils: 2.29.1-r1::core-kit sys-devel/gcc: 7.3.1::core-kit sys-devel/gcc-config: 1.9.1::core-kit sys-devel/libtool: 2.4.6-r4::core-kit sys-devel/make: 4.2.1-r1::core-kit sys-kernel/linux-headers: 4.14::core-kit (virtual/os-headers) sys-libs/glibc: 2.26-r7::core-kit Repositories: nokit location: /var/git/meta-repo/kits/nokit masters: core-kit priority: -500 core-hw-kit location: /var/git/meta-repo/kits/core-hw-kit masters: core-kit priority: 1 core-kit location: /var/git/meta-repo/kits/core-kit priority: 1 aliases: gentoo desktop-kit location: /var/git/meta-repo/kits/desktop-kit masters: core-kit priority: 1 dev-kit location: /var/git/meta-repo/kits/dev-kit masters: core-kit priority: 1 editors-kit location: /var/git/meta-repo/kits/editors-kit masters: core-kit priority: 1 games-kit location: /var/git/meta-repo/kits/games-kit masters: core-kit priority: 1 gnome-kit location: /var/git/meta-repo/kits/gnome-kit masters: core-kit priority: 1 haskell-kit location: /var/git/meta-repo/kits/haskell-kit masters: core-kit priority: 1 java-kit location: /var/git/meta-repo/kits/java-kit masters: core-kit priority: 1 kde-kit location: /var/git/meta-repo/kits/kde-kit masters: core-kit priority: 1 lang-kit location: /var/git/meta-repo/kits/lang-kit masters: core-kit priority: 1 lisp-scheme-kit location: /var/git/meta-repo/kits/lisp-scheme-kit masters: core-kit priority: 1 llvm-kit location: /var/git/meta-repo/kits/llvm-kit masters: core-kit priority: 1 media-kit location: /var/git/meta-repo/kits/media-kit masters: core-kit priority: 1 ml-lang-kit location: /var/git/meta-repo/kits/ml-lang-kit masters: core-kit priority: 1 net-kit location: /var/git/meta-repo/kits/net-kit masters: core-kit priority: 1 perl-kit location: /var/git/meta-repo/kits/perl-kit masters: core-kit priority: 1 php-kit location: /var/git/meta-repo/kits/php-kit masters: core-kit priority: 1 python-kit location: /var/git/meta-repo/kits/python-kit masters: core-kit priority: 1 python-modules-kit location: /var/git/meta-repo/kits/python-modules-kit masters: core-kit priority: 1 ruby-kit location: /var/git/meta-repo/kits/ruby-kit masters: core-kit priority: 1 science-kit location: /var/git/meta-repo/kits/science-kit masters: core-kit priority: 1 security-kit location: /var/git/meta-repo/kits/security-kit masters: core-kit priority: 1 text-kit location: /var/git/meta-repo/kits/text-kit masters: core-kit priority: 1 xfce-kit location: /var/git/meta-repo/kits/xfce-kit masters: core-kit priority: 1 xorg-kit location: /var/git/meta-repo/kits/xorg-kit masters: core-kit priority: 1 chaoslab location: /var/lib/layman/chaoslab masters: core-kit priority: 50 ACCEPT_KEYWORDS="amd64 ~amd64" ACCEPT_LICENSE="* -@EULA Oracle-BCLA-JavaSE" CBUILD="x86_64-pc-linux-gnu" CFLAGS="-march=westmere -O2 -pipe" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/share/gnupg/qualified.txt" CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/env.d /etc/fonts/fonts.conf /etc/gconf /etc/gentoo-release /etc/php/apache2-php7.1/ext-active/ /etc/php/apache2-php7.2/ext-active/ /etc/php/apache2-php7.3/ext-active/ /etc/php/cgi-php7.1/ext-active/ /etc/php/cgi-php7.2/ext-active/ /etc/php/cgi-php7.3/ext-active/ /etc/php/cli-php7.1/ext-active/ /etc/php/cli-php7.2/ext-active/ /etc/php/cli-php7.3/ext-active/ /etc/revdep-rebuild /etc/sandbox.d /etc/terminfo" CXXFLAGS="-march=westmere -O2 -pipe" DISTDIR="/var/cache/portage/distfiles" FEATURES="assume-digests binpkg-logs config-protect-if-modified distlocks ebuild-locks fixlafiles merge-sync multilib-strict news parallel-fetch preserve-libs protect-owned sandbox sfperms strict unknown-features-warn unmerge-logs unmerge-orphans userfetch userpriv usersandbox usersync xattr" FFLAGS="-march=westmere -O2 -pipe" GENTOO_MIRRORS="https://fastpull-us.funtoo.org" LANG="en_US.utf8" LDFLAGS="-Wl,-O1 -Wl,--sort-common -Wl,--as-needed" LINGUAS="en_US fr_FR" MAKEOPTS="-j7" PKGDIR="/var/cache/portage/packages" PORTAGE_BINHOST="https://bin.host.funtoo.org/intel64-westmere" PORTAGE_CONFIGROOT="/" PORTAGE_TMPDIR="/var/tmp" USE="acl amd64 berkdb bzip2 cracklib crypt curl cxx gdbm geoip iconv icu ipv6 luajit mmx modules mudflap multilib mysql ncurses nls nptl openmp pam pcre pdo php python readline resolvconf sse sse2 ssl tcpd unicode vhosts xattr xml xmlreader xmlwriter xslt zip zlib" ABI_X86="64" APACHE2_MODULES="actions alias auth_basic authn_alias authn_anon authn_dbm authn_default authn_file authz_dbm authz_default authz_groupfile authz_host authz_owner authz_user autoindex cache cgi cgid dav dav_fs dav_lock deflate dir disk_cache env expires ext_filter file_cache filter headers include info log_config logio mem_cache mime mime_magic negotiation rewrite setenvif speling status unique_id userdir usertrack vhost_alias authn_core authz_core socache_shmcb unixd" CALLIGRA_FEATURES="kexi words flow plan sheets stage tables krita karbon braindump author" COLLECTD_PLUGINS="df interface irq load memory rrdtool swap syslog" CPU_FLAGS_X86="aes mmx mmxext popcnt sse sse2 sse3 sse4_1 sse4_2 ssse3" ELIBC="glibc" GPSD_PROTOCOLS="ashtech aivdm earthmate evermore fv18 garmin garmintxt gpsclock isync itrax mtk3301 nmea ntrip navcom oceanserver oldstyle oncore rtcm104v2 rtcm104v3 sirf skytraq superstar2 timing tsip tripmate tnt ublox ubx" GRUB_PLATFORMS="efi-64 pc" INPUT_DEVICES="evdev synaptics keyboard mouse" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" LIBREOFFICE_EXTENSIONS="presenter-console presenter-minimizer" NGINX_MODULES_EXTERNAL="accept_language lua luajit headers_more" NGINX_MODULES_STREAM="geoip realip ssl_preread access geo limit_conn map return split_clients upstream_hash upstream_least_conn upstream_zone" OFFICE_IMPLEMENTATION="libreoffice" PHP_TARGETS="php7-1 php7-2 php7-3" POSTGRES_TARGETS="postgres9_5" PYTHON_SINGLE_TARGET="python3_6" PYTHON_TARGETS="python3_6 python2_7" QEMU_SOFTMMU_TARGETS="i386 x86_64" QEMU_USER_TARGETS="i386 x86_64" RUBY_TARGETS="ruby23 ruby24" USERLAND="GNU" XTABLES_ADDONS="quota2 psd pknock lscan length2 ipv4options ipset ipp2p iface geoip fuzzy condition tee tarpit sysrq steal rawnat logmark ipmark dhcpmac delude chaos account" Unset: CPPFLAGS, CTARGET, EMERGE_DEFAULT_OPTS, ENV_UNSET, INSTALL_MASK, LC_ALL, PORTAGE_BUNZIP2_COMMAND, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS # emerge --info -vvv | grep "PORT\|portage" !!! Repository 'ruby-kit' is missing masters attribute in '/var/git/meta-repo/kits/ruby-kit/metadata/layout.conf' !!! Set 'masters = core-kit' in this file for future compatibility WARNING: One or more repositories have missing repo_name entries: /var/git/meta-repo/kits/ruby-kit/profiles/repo_name NOTE: Each repo_name entry should be a plain text file containing a unique name for the repository on the first line. DISTDIR="/var/cache/portage/distfiles" FETCHCOMMAND_SFTP="bash -c "x=\${2#sftp://} ; host=\${x%%/*} ; port=\${host##*:} ; host=\${host%:*} ; [[ \${host} = \${port} ]] && port= ; eval \"declare -a ssh_opts=(\${3})\" ; exec sftp \${port:+-P \${port}} \"\${ssh_opts[@]}\" \"\${host}:/\${x#*/}\" \"\$1\"" sftp "${DISTDIR}/${FILE}" "${URI}" "${PORTAGE_SSH_OPTS}"" FETCHCOMMAND_SSH="bash -c "x=\${2#ssh://} ; host=\${x%%/*} ; port=\${host##*:} ; host=\${host%:*} ; [[ \${host} = \${port} ]] && port= ; exec rsync --rsh=\"ssh \${port:+-p\${port}} \${3}\" -avP \"\${host}:/\${x#*/}\" \"\$1\"" rsync "${DISTDIR}/${FILE}" "${URI}" "${PORTAGE_SSH_OPTS}"" MULTILIB_STRICT_EXEMPT="(perl5|gcc|gcc-lib|binutils|eclipse-3|debug|portage)" PKGDIR="/var/cache/portage/packages" PORTAGE_ARCHLIST="" PORTAGE_BINHOST="https://bin.host.funtoo.org/intel64-westmere" PORTAGE_BIN_PATH="/usr/lib/portage/python3.6" PORTAGE_COMPRESS_EXCLUDE_SUFFIXES="css gif htm[l]? jp[e]?g js pdf png" PORTAGE_CONFIGROOT="/" PORTAGE_DEBUG="0" PORTAGE_DEPCACHEDIR="/var/cache/edb/dep" PORTAGE_ELOG_CLASSES="log warn error" PORTAGE_ELOG_MAILFROM="portage@localhost" PORTAGE_ELOG_MAILSUBJECT="[portage] ebuild log for ${PACKAGE} on ${HOST}" PORTAGE_ELOG_MAILURI="root" PORTAGE_ELOG_SYSTEM="save_summary:log,warn,error,qa echo" PORTAGE_FETCH_CHECKSUM_TRY_MIRRORS="5" PORTAGE_FETCH_RESUME_MIN_SIZE="350K" PORTAGE_GID="250" PORTAGE_GPG_SIGNING_COMMAND="gpg --sign --digest-algo SHA256 --clearsign --yes --default-key "${PORTAGE_GPG_KEY}" --homedir "${PORTAGE_GPG_DIR}" "${FILE}"" PORTAGE_INST_GID="0" PORTAGE_INST_UID="0" PORTAGE_INTERNAL_CALLER="1" PORTAGE_OVERRIDE_EPREFIX="" PORTAGE_PYM_PATH="/usr/lib64/python3.6/site-packages" PORTAGE_PYTHONPATH="/usr/lib64/python3.6/site-packages" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --omit-dir-times --compress --force --whole-file --delete --stats --human-readable --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages --exclude=/.git" PORTAGE_RSYNC_RETRIES="-1" PORTAGE_SYNC_STALE="30" PORTAGE_TMPDIR="/var/tmp" PORTAGE_VERBOSE="1" PORTAGE_WORKDIR_MODE="0700" PORTAGE_XATTR_EXCLUDE="btrfs.* security.evm security.ima security.selinux system.nfs4_acl user.apache_handler user.Beagle.* user.dublincore.* user.mime_encoding user.xdg.*" PORT_LOGDIR_CLEAN="find "${PORT_LOGDIR}" -type f ! -name "summary.log*" -mtime +7 -delete" RESUMECOMMAND_SSH="bash -c "x=\${2#ssh://} ; host=\${x%%/*} ; port=\${host##*:} ; host=\${host%:*} ; [[ \${host} = \${port} ]] && port= ; exec rsync --rsh=\"ssh \${port:+-p\${port}} \${3}\" -avP \"\${host}:/\${x#*/}\" \"\$1\"" rsync "${DISTDIR}/${FILE}" "${URI}" "${PORTAGE_SSH_OPTS}"" RPMDIR="/var/cache/portage/rpm" UNINSTALL_IGNORE="/lib/modules/* /var/run /var/lock /etc/portage/*" By the way, in meta_repo containers there is no /var/git/meta-repo/kits/ruby-kit/metadata/layout.conf ll /var/git/meta-repo/kits/ruby-kit/ total 16K drwxr-xr-x 4 nobody nobody 34 Aug 17 21:00 . drwxr-xr-x 29 nobody nobody 4.0K May 23 15:49 .. drwxr-xr-x 7 nobody nobody 197 Aug 17 21:00 .git drwxr-xr-x 4 nobody nobody 12K Aug 13 20:00 dev-ruby
  23. eix-update broken

    emerge --info please
  24. eix-update broken

    I think you are mistaken by setting PORTDIR to "/var/git/meta-repo/kits/core-kit/". As you output shows, eix-update is only updating core-kit. And eix is part of "nokit". So it is clear that eix could not be found. Besides, the problem is, that you need to set PORTDIR in the first place. As far as I know this variable could generally be used when you work with overlays but is not needed for the standard tree. So, do you work with overlays and might have changed something that could influence eix?
  25. eix-update broken

    it comes from this : # eix-update --print PORTDIR /usr/portage/ my desktop is : # eix-update --print PORTDIR /var/git/meta-repo/kits/core-kit/ forcing it in /etc/portage/make.conf is not enough : # cat /etc/portage/make.conf | grep PORTDIR PORTDIR="/var/git/meta-repo/kits/core-kit/" # eix-update Reading Portage settings... Building database (/var/cache/eix/portage.eix)... [0] "core-kit" /var/git/meta-repo/kits/core-kit/ (cache: metadata-md5-or-flat) Reading category 40|40 (100) Finished # eix eix No matches found
  26. eix-update broken

    meta_repo_path was just to have a repo in rw for ego sync, but I switched back to the default one since it is now on 1.2. I also checked /etc/eixrc/00-eixrc against my desktop where eix works well and I don't have any diff. Here it is : # /etc/eixrc/00-eixrc # # All non-hidden files in /etc/eixrc # (or a subdirectory thereof) are read in alphabetical order. # # In these files system-wide defaults for variables related to eix can # be stored, i.e. the variables set in files override the built-in defaults. # Both can be overridden by ~/.eixrc and by environment variables. # # It is strongly recommended to set here only those variables which you # want to *differ* from the built-in defaults (or for which you have a # particular reason why the default should never change with an eix update). # # *Otherwise you might miss changes in the defaults in newer eix versions* # which may result in confusing behavior of the eix binaries. # # If you want to get a file containing the setting of all related variables # in the current/defaults state, redirect the output of options --dump # or --dump-defaults, respectively. # # However once more: To avoid unexpected problems # # *IT IS NOT RECOMMENDED TO SET _ALL_ VARIABLES* in /etc/eixrc/* # # Only set those for which you have a reason to do so! # # For the available variables and their defaults, see the output of the # options --dump or --dump-defaults. # For more detailed explanations see the manpage of eix.
  27. Thank you for your help! The step that fixed my problems was to remove /etc/portage/make.profile and have ego recreate it with "ego sync --config-only" and reset everything with epro
  28. eix-update broken

    OK, a few things to check here: - Why do you have meta_repo_path in ego.conf? Any special reason? I don't have that line and eix-update works for me - What does /etc/eixrc/00-eixrc look like?
  1. Load more activity
×