[Sync on system not updated in a while... Not good!]

did you already switch to release = 1.2 ?

[Sync on system not updated in a while... Not good!]

please provide the error messages with PYTHON_TARGET stuff.

[Sync on system not updated in a while... Not good!]

and you could try putting this into your /etc/portage/make.profile/parent file

core-kit:funtoo/1.0/linux-gnu/arch/x86-64bit
core-kit:funtoo/1.0/linux-gnu/arch/x86-64bit/subarch/generic_64
core-kit:funtoo/1.0/linux-gnu/build/current
core-kit:funtoo/1.0/linux-gnu/flavor/core

 

[Sync on system not updated in a while... Not good!]

if that works you can then use the steps that are on wiki:

Quote

 

If you still cannot merge using emerge, the following should work:

#  cd /var/git/meta-repo/kits/core-kit/app-admin/ego
#  ebuild ego-2.4.2.ebuild merge

 

or any higher ego version

[Sync on system not updated in a while... Not good!]

13 hours ago, dkg said:

[root@wolfie 61% tmp]# git clone https://github.com/funtoo/ego.git

[root@wolfie 61% tmp]# cd ego

[root@wolfie 61% ego]# ego sync

if you mean this ^

then to actually use the cloned ego you have to write

./ego sync

:) so yes I've seen it but you missed it

[Sync on system not updated in a while... Not good!]

upgrade ego first then ego sync

[Sync on system not updated in a while... Not good!]

did you follow?

https://www.funtoo.org/Upgrade_Instructions

 

[Solved: ruby installating hangs in configure step: checking for broken backtrace]

Still no luck reproducing your issue even with libressl and jemalloc it compiles fine. Recompiling world with libressl and will try again, but looks like hw related failure. Give more info as what image did you use to install funtoo. I would probably try with generic_64bit image and expand from there, as some of intel cpu don't have all the cpu capabilities they should have according to their family specs. My NUC also doesn't support aes and rdrnd although ivybridge :) (Intel(R) Core(TM) i3-3217U CPU @ 1.80GHz)

[Broken files on fastpull-us.funtoo.org]

 

without actual logs it is just reading from a crystal ball.

https://bugs.funtoo.org for bug reports, but again with actual logs and errors.

[Solved: ruby installating hangs in configure step: checking for broken backtrace]

hi saskia!

unfortunately I am unable to reproduce this on my setup. both packages emerge fine (ruby and neovim).

 

[Why can not switch to systemd]

gnome3 works well with funtoo and without systemd.

[Solved: ruby installating hangs in configure step: checking for broken backtrace]

what exact package(s) (with version number and maybe emerge -av <package> output) are you trying to emerge and fail? what is the output that you are getting? what other blockers did you encounter?

please read also

 

[Why can not switch to systemd]

Funtoo doesn't support systemd and probably never will.

[[UEFI+BTRFS] Need support getting it to boot.]

try changing

linux /kernel-genkernel-x86_64-4.18.8-gentoo real_root=/dev/sda3 rootfstype=btrfs root=/dev/sda3 rootflags=ssd,compress=zstd rootfstype=btrfs

to

linux /kernel-genkernel-x86_64-4.18.8-gentoo real_root=/dev/sda3 rootfstype=btrfs real_rootflags=ssd,compress=zstd,subvol=/

 

[Metro documentation]

The best and easiest way to donate to the project is getting a Funtoo Container.

https://www.funtoo.org/Funtoo_Containers

In this way you get something back immediately. For metro docs please open a bug on bugs.funtoo.org. Funtoo development is doing weekly scrum sprints and I am sure that can be done to make the documentation of core techs better.

[Budgie Desktop?]

if you know how, you could test budgie out of sabayon overlay and report back. the problem with gnome3 is the heavy dependence on systemd and I don't know how systemd hungry budgie is. the supported gnome3 is stripped from all these systemd deps and still works. so probably possible to add budgie, but would appreciate your help with it.

[Greetings from Spain.]

desktop with gnome is supported well. just for your info.

[ego crashes when meta-repo is read only]

5 minutes ago, romikb said:

readonly: "true"

remove this and it will work as a workaround.

[Greetings from Spain.]

What do you want to do? Desktop, server ...?

[ego crashes when meta-repo is read only]

which release are you using in containers?

[ego crashes when meta-repo is read only]

what ego version in container and on the host?

[env -i HOME=/root TERM=$TERM chroot . bash -l zsh: illegal hardware instruction...]

couple of things here:

• you are booting the 32bit version of sysresccd and downloading and installing a 64bit version of funtoo - this will not work.
• you are downloading stage3 that ismore than 3 years old - this might not be such a good idea

• On 29.5.2015 at 4:12 PM, linuxbigot said:

  stage3-intel64-sandybridge-funtoo-current-2015-05-29.tar.xz

   

• are you extracting to the newly created filesystem? as it looks like you are trying to extract it to root of the sysresccd

If you want more help I would recommend reading this article:

 

[eix-update broken]

emerge --info

please

[Outdated Desktop Environments]

upper/lower case? if that makes no difference write to support@funtoo.org with details.

[Funtoo improves Dropbox]

Maybe take a look at syncthing: https://syncthing.net/