Jump to content
funtoo forums

adcdam

Members
  • Content count

    107
  • Joined

  • Last visited

  • Days Won

    6

adcdam last won the day on August 13 2017

adcdam had the most liked content!

About adcdam

  • Rank
    Advanced Member

Personal

  • Location
    La Plata, Buenos Aires, Argentina
  1. Ravenports by Marino, Opinions?

    Before Ravenports Marino created a port building tool called synth programed in Ada Languaje for FreeBSD and DragonFly BSD, i tried it and it was much better than portmaster , it would be nice if Daniel, Oleg, Palica talk with Marino, perhaps new ideas will come, or something to improve portage (which is great) even more...
  2. http://ravenports.ironwolf.systems/
  3. i installed Runit i posted a video in the general discussion section. its really nice!!
  4. This is how it went, everything ok!! a very kind Russian guy with tons of knowledge and patience explain me how to install and use it. https://vimeo.com/254601362
  5. openrc-0.35.0_beta1 failed to compile

    Hi, thanks that was the problem portage owns distfile directory but not git3-src i changed that and i was able to install openrc 0.35 but when booting it say rc is deprecated, please use openrc instead and etc/init.d/udev use runscript, please convert to openrc udev
  6. openrc-0.35.0_beta1 failed to compile

    Hi, yes portage is able to write there, i updated today and there are lots of new version packages is in /var/cache /portage/distfiles so portage is able to write there, openrc was the only package that wasnt able to update. if i manually create OpenRC_openrc.git dir inside /var/cache/portage/distfiles/git3-src i get this >>> Emerging (1 of 1) sys-apps/openrc-0.35.0_beta1::core-kit >>> Unpacking source... * Fetching https://github.com/OpenRC/openrc.git ... git fetch https://github.com/OpenRC/openrc.git +HEAD:refs/git-r3/HEAD fatal: Not a git repository: '/var/cache/portage/distfiles/git3-src/OpenRC_openrc.git' * ERROR: sys-apps/openrc-0.35.0_beta1::core-kit failed (unpack phase): * Unable to fetch from any of EGIT_REPO_URI * * Call stack: * ebuild.sh, line 121: Called src_unpack * environment, line 3219: Called git-r3_src_unpack * environment, line 2165: Called git-r3_src_fetch * environment, line 2159: Called git-r3_fetch * environment, line 2081: Called die * The specific snippet of code: * [[ -n ${success} ]] || die "Unable to fetch from any of EGIT_REPO_URI"; * * If you need support, post the output of `emerge --info '=sys-apps/openrc-0.35.0_beta1::core-kit'`, * the complete build log and the output of `emerge -pqv '=sys-apps/openrc-0.35.0_beta1::core-kit'`. * The complete build log is located at '/var/tmp/portage/sys-apps/openrc-0.35.0_beta1/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/sys-apps/openrc-0.35.0_beta1/temp/environment'. * Working directory: '/var/tmp/portage/sys-apps/openrc-0.35.0_beta1/work' * S: '/var/tmp/portage/sys-apps/openrc-0.35.0_beta1/work/openrc-0.35.0_beta1' >>> Failed to emerge sys-apps/openrc-0.35.0_beta1, Log file: >>> '/var/tmp/portage/sys-apps/openrc-0.35.0_beta1/temp/build.log' * Messages for package sys-apps/openrc-0.35.0_beta1: * ERROR: sys-apps/openrc-0.35.0_beta1::core-kit failed (unpack phase): * Unable to fetch from any of EGIT_REPO_URI * * Call stack: * ebuild.sh, line 121: Called src_unpack * environment, line 3219: Called git-r3_src_unpack * environment, line 2165: Called git-r3_src_fetch * environment, line 2159: Called git-r3_fetch * environment, line 2081: Called die * The specific snippet of code: * [[ -n ${success} ]] || die "Unable to fetch from any of EGIT_REPO_URI"; * * If you need support, post the output of `emerge --info '=sys-apps/openrc-0.35.0_beta1::core-kit'`, * the complete build log and the output of `emerge -pqv '=sys-apps/openrc-0.35.0_beta1::core-kit'`. * The complete build log is located at '/var/tmp/portage/sys-apps/openrc-0.35.0_beta1/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/sys-apps/openrc-0.35.0_beta1/temp/environment'. * Working directory: '/var/tmp/portage/sys-apps/openrc-0.35.0_beta1/work' * S: '/var/tmp/portage/sys-apps/openrc-0.35.0_beta1/work/openrc-0.35.0_beta1'
  7. Hi, i get this: how can i solve that? >>> Unpacking source... mkdir: cannot create directory ‘/var/cache/portage/distfiles/git3-src/OpenRC_openrc.git’: Permission denied * ERROR: sys-apps/openrc-0.35.0_beta1::core-kit failed (unpack phase): * (no error message) * * Call stack: * ebuild.sh, line 121: Called src_unpack * environment, line 3219: Called git-r3_src_unpack * environment, line 2165: Called git-r3_src_fetch * environment, line 2159: Called git-r3_fetch * environment, line 1956: Called _git-r3_set_gitdir 'https://github.com/OpenRC/openrc.git' * environment, line 476: Called die * The specific snippet of code: * mkdir "${GIT_DIR}" || die; * * If you need support, post the output of `emerge --info '=sys-apps/openrc-0.35.0_beta1::core-kit'`, * the complete build log and the output of `emerge -pqv '=sys-apps/openrc-0.35.0_beta1::core-kit'`. * The complete build log is located at '/var/tmp/portage/sys-apps/openrc-0.35.0_beta1/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/sys-apps/openrc-0.35.0_beta1/temp/environment'. * Working directory: '/var/tmp/portage/sys-apps/openrc-0.35.0_beta1/work' * S: '/var/tmp/portage/sys-apps/openrc-0.35.0_beta1/work/openrc-0.35.0_beta1' >>> Failed to emerge sys-apps/openrc-0.35.0_beta1, Log file: >>> '/var/tmp/portage/sys-apps/openrc-0.35.0_beta1/temp/build.log' * Messages for package sys-apps/openrc-0.35.0_beta1: * ERROR: sys-apps/openrc-0.35.0_beta1::core-kit failed (unpack phase): * (no error message) * * Call stack: * ebuild.sh, line 121: Called src_unpack * environment, line 3219: Called git-r3_src_unpack * environment, line 2165: Called git-r3_src_fetch * environment, line 2159: Called git-r3_fetch * environment, line 1956: Called _git-r3_set_gitdir 'https://github.com/OpenRC/openrc.git' * environment, line 476: Called die * The specific snippet of code: * mkdir "${GIT_DIR}" || die; * * If you need support, post the output of `emerge --info '=sys-apps/openrc-0.35.0_beta1::core-kit'`, * the complete build log and the output of `emerge -pqv '=sys-apps/openrc-0.35.0_beta1::core-kit'`. * The complete build log is located at '/var/tmp/portage/sys-apps/openrc-0.35.0_beta1/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/sys-apps/openrc-0.35.0_beta1/temp/environment'. * Working directory: '/var/tmp/portage/sys-apps/openrc-0.35.0_beta1/work' * S: '/var/tmp/portage/sys-apps/openrc-0.35.0_beta1/work/openrc-0.35.0_beta1'
  8. i really like to try Runit as init and supervisor, anyone using Runit with Funtoo? i know that i can use Runit with Openrc but i would like to use just Runit. a tutorial on how to migrate init would be nice!
  9. qbittorrent failed to compile

    i rebuild libtorrent-rastebar and then i was able to compile qbittorrent witout problems, thanks!!
  10. qbittorrent failed to compile

    Hi it say emake failed, im using gcc 5.4.0 perhaps something related to that?
  11. firefox 55 failed to build (libpng-16.29 needed)

    its fixed now, libpng-1.6.29 is available now as Cardinal told me, thanks to both!
  12. problem when updating

    Thanks Cardinal!!!! i was able to update when renaming that file!!! thank you too Oleg!
  13. problem when updating

    Hi, thanks i did that i got the same * Messages for package x11-base/xorg-server-1.17.4-r1: * This package will overwrite one or more files that may belong to other * packages (see list below). You can use a command such as `portageq * owners / <filename>` to identify the installed package that owns a * file. If portageq reports that only one package owns a file then do * NOT file a bug report. A bug report is only useful if it identifies at * least two or more packages that are known to install the same file(s). * If a collision occurs and you can not explain where the file came from * then you should simply ignore the collision since there is not enough * information to determine if a real problem exists. Please do NOT file * a bug report at https://bugs.gentoo.org/ unless you report exactly * which two packages install the same file(s). See * https://wiki.gentoo.org/wiki/Knowledge_Base:Blockers for tips on how * to solve the problem. And once again, please do NOT file a bug report * unless you have completely understood the above message. * * Detected file collision(s): * * /usr/share/X11/xorg.conf.d/10-evdev.conf * * Searching all installed packages for file collisions... * * Press Ctrl-C to Stop * * x11-drivers/xf86-input-evdev-2.10.5:0::gentoo * /usr/share/X11/xorg.conf.d/10-evdev.conf * * Package 'x11-base/xorg-server-1.17.4-r1' NOT merged due to file * collisions. If necessary, refer to your elog messages for the whole * content of the above message. * GNU info directory index is up-to-date. before i was stupid and did emerge -C xorg-server and deleted the newer version, i dont now what im doing i need a coffee why there are packages that need rebuild here? sudo equery list -po x11-base/xorg-server Contrase?a: Unavailable repository 'gentoo' referenced by masters entry in '/var/lib/layman/sunrise/metadata/layout.conf' !!! Unable to parse profile: '/etc/portage/make.profile' !!! ParseError: Parent 'gentoo:funtoo/1.0/linux-gnu/arch/x86-64bit' not found: '/etc/portage/make.profile/parent' * Searching for xorg-server in x11-base ... [--O] [ ] x11-base/xorg-server-1.17.4:0/1.17.4 [--O] [ ] x11-base/xorg-server-1.17.4-r1:0/1.17.4
  14. problem when updating

    These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild N ] x11-base/xorg-server-1.17.4-r1 USE="ipv6 nptl suid udev xorg -dmx -doc -glamor -kdrive -libressl -minimal (-selinux) -static-libs -systemd -tslib -unwind -wayland -xephyr -xnest -xvfb" [ebuild rR ] x11-drivers/xf86-input-mouse-1.9.2 [ebuild rR ] x11-drivers/xf86-input-keyboard-1.9.0 [ebuild UD ] x11-drivers/xf86-input-evdev-2.9.2 [2.10.5] [ebuild UD ] sys-fs/udisks-2.1.8 [2.6.5] [ebuild U ] app-crypt/gnupg-2.1.20 [2.1.18] [ebuild UD ] media-gfx/icoutils-0.31.1 [0.31.3] [ebuild U ] app-editors/vim-core-8.0.0911 [8.0.0606] [ebuild U ] app-editors/vim-8.0.0911 [8.0.0606] [ebuild UD ] x11-base/xorg-drivers-1.17 [1.19] [ebuild rR ] x11-drivers/nvidia-drivers-381.22 [381.22] [ebuild U ] www-client/google-chrome-60.0.3112.90 [60.0.3112.78] [ebuild U ] dev-qt/qtgui-5.7.1-r1 [5.7.1] [ebuild U ] www-client/firefox-55.0 [54.0.1] The following packages are causing rebuilds: (x11-base/xorg-server-1.17.4-r1:0/1.17.4::xorg-kit, ebuild scheduled for merge) causes rebuilds for: (x11-drivers/nvidia-drivers-381.22:0/381::xorg-kit, ebuild scheduled for merge) (x11-drivers/xf86-input-keyboard-1.9.0:0/0::xorg-kit, ebuild scheduled for merge) (x11-drivers/xf86-input-mouse-1.9.2:0/0::xorg-kit, ebuild scheduled for merge) Would you like to merge these packages? [Yes/No]
  15. problem when updating

    i did that, portage try to install the old version of xorg-server and there are some rebuilds >>> Failed to install x11-base/xorg-server-1.17.4-r1, Log file: >>> '/var/tmp/portage/x11-base/xorg-server-1.17.4-r1/temp/build.log' * Messages for package x11-base/xorg-server-1.17.4-r1: * This package will overwrite one or more files that may belong to other * packages (see list below). You can use a command such as `portageq * owners / <filename>` to identify the installed package that owns a * file. If portageq reports that only one package owns a file then do * NOT file a bug report. A bug report is only useful if it identifies at * least two or more packages that are known to install the same file(s). * If a collision occurs and you can not explain where the file came from * then you should simply ignore the collision since there is not enough * information to determine if a real problem exists. Please do NOT file * a bug report at https://bugs.gentoo.org/unless you report exactly * which two packages install the same file(s). See * https://wiki.gentoo.org/wiki/Knowledge_Base:Blockersfor tips on how * to solve the problem. And once again, please do NOT file a bug report * unless you have completely understood the above message. * * Detected file collision(s): * * /usr/share/X11/xorg.conf.d/10-evdev.conf * * Searching all installed packages for file collisions... * * Press Ctrl-C to Stop * * x11-drivers/xf86-input-evdev-2.10.5:0::gentoo * /usr/share/X11/xorg.conf.d/10-evdev.conf * * Package 'x11-base/xorg-server-1.17.4-r1' NOT merged due to file * collisions. If necessary, refer to your elog messages for the whole * content of the above message. * GNU info directory index is up-to-date.
×