valerievonck
-
Posts
9 -
Joined
-
Last visited
Content Type
Profiles
Forums
Blogs
Posts posted by valerievonck
-
-
ego is pulling in mesa-13.0.1, thanks again!
-
-
jhan,
Indeed, when doing eix -s mesa, only these two packages are shown, :s, but it is not available (anymore)...
Is anyone experiencing this as well ? (fresh installation)?
-
Yesterday, I successfully installed Funtoo on ZFS in a virtual box.
Then I added the desktop flavor and added my mix-ins.
I did an emerge -avuND world, to get all the packages, but when emerge wanted to pull in mesa, the scripts says: directory is no longer available.On my other Funtoo virtual box, this package is installed
But in my Gentoo virtual box, the package is on version 17.0.6?
Can anyone help me please?
Do I have to unmask this package in /etc/portage/package.use? (>=media-libs/mesa-13.0.1 tilde amd64)?Or do I have to create a bug?
Thank you,
Kind regards,
Valerie -
I got the same problem, but with a
ego sync
and aemerge -avuND @world
it started pulling in the updates.Edit: in my make.conf there are no longer PYTHON_TARGET nor PYTHON_SINGLE_TARGET
Edit 2: on my other vbox, I had to pull in libpcre2 & xmlsec ebuilds to start the world update... (and do an etc-update)
Kind regards,
Valerie
-
Wrong topic
Sorry
-
right, that's the idea of having automatically setting of python stuff. yes, automated process, which is also gives ability for clean update (or downgrade) of python. For example from 3.4 to 3.6 in one single step. This is step beyond known python switch everyone used to have in gentoo. By a bad fortune i accidentally enabled this feature little bit earlier than it's planned, so my apologies for that.
No problem, you are welcome.
-
Ok :)
My misunderstanding, I thought you meant, leave the make.conf empty... :huh:
My mistake,
Thank you for the swift reply!
-
Just a question, not wanting to start a discussion nor a flamewar.
I have been a long time Gentoo user, and I am used to do everything to do with : /etc/portage/make.conf,
I know that people are going to say, Funtoo != Gentoo, I could not agree more, it is fast & lean, just how an OS must be.
A staff member said:
you shouldn't put anything into make.conf. you need to sync again and there should be ego update to 1.1.3-r5
I respect his opinion, but why is Funtoo taken this approach (to move away from make.conf) or why I am not getting it,
I am trying to understand and learn...
If I do not set my makeopts, will Funtoo be able to determine my (virtual) cpu's?
Just wondering...
-
and epro update is required to run.
Removed the lines from make.conf, run epro update, and emerge -avuND @world
It is pulling in the updates, Thank you!!
-
@Oleg Vinichenko,
Thank you for your insight, I will try this when building a new VBox Machine.
emerge -s ego | more
yielded ego 1.1.3-r5
Marking this topic as [solved]
Thank you!
Kind regards,
Valerie
-
Hello everyone,
Since a couple of months I am using Funtoo in Virtual Box, up until now, I have got no problems installing Funtoo in following configurations:
- Base install
- KDE
- Base install + ZFS
Past weekend I did follow the instructions for using the new ego system, mentioned at http://www.funtoo.org/News:Kits_Are_Go_(And_Ego_Needs_a_Manual_Bump) , also I have read on the forum to do an additional
chown -R portage:portage.
I will post my make.conf
CFLAGS="-O2 -pipe" CXXFLAGS="${CFLAGS}" MAKEOPTS="-j5" ACCEPT_LICENSE="* @EULA" CHOST="x86_64-pc-linux-gnu" USE="alsa gif jpeg png tiff xpm python icu bindist mmx sse sse2" PORTDIR="/usr/portage" DISTDIR="${PORTDIR}/distfiles" PKGDIR="${PORTDIR}/packages"So far so good, this morning I did a
ego sync emerge --sync emerge -avuND @world update.
Now I am getting following blocking error:
!!! Problem resolving dependencies for sys-apps/file form @system ... done ! !!! The ebuild selected to satisfy "sys-apps/file" has unment requirements . - sys-apps/file-5.30::core-kit USE="python zlib - static-libs" ABI_X86="64 -32 -x32" PYTHON_TARGETS"-pypy -python2_7 -python3_4 -python3_5 -python3_6" The following REQUIRED_USE flag constraints are unsatisfied: python? ( any-of ( python_targets_pypy_python_targets_python2_7 python_targets_python3_4 python_targets3_5 python_targets_python3_6 ) ) (dependency required by " @system" [set]) (dependency required by " @world" [argument])
So, I modified the /etc/portage/make.conf profile, I have added:
ABI_X86="64"
Run emerge again, the same error... :(
I said, ok, erase the disk (Virtual Box) and start over again.
Included the changes for the meta-repo
I am getting on to the point to do a
emerge -av boot-update
I am getting the following errors:
!!! Problem resolving dependencies for sys-boot/boot-update ... done ! !!! The ebuild selected to satisfy "boot-update" has unment requirements . - sys-boot/boot-update-1.8.0::core-kit USE="" PYTHON_SINGLE_TARGETS"-python3_4 -python3_5 -python3_6" PYTHON_TARGETS="-python3_4 -python3_5 -python3_6" The following REQUIRED_USE flag constraints are unsatisfied: exactly-one-of ( python_single_target_python3_4 python_single_target_python3_5 python_single_target_python3_6 ) The above constraints are a subset of the following complere expression: exactly-one-of ( python_single_target_python3_4 python_single_target_python3_5 python_single_target_python3_6 ) python_single_target3_4? (python_target_python3_4) python_single_target3_5? (python_target_python3_5) python_single_target3_6? (python_target_python3_6)
So I am blocked for continuing my installation,
Can anyone render me someone assistance please?
Thank you,
Kind regards,

sys-kernel/debian-sources-4.13.10-1 Test
in General Discussion
Posted
@Oleg Vinichenko
Please find the results of my tests under a Virtual Box machine:
- First I had to add "amd64" to KEYWORD variable in the ebuild under: /var/git/meta-repo/core-kit/
- Then I had to expand the virtual harddisk, so that I had 20G free (from 32G to 60G) (ubuntu live cd)
- Then I had to do a
emerge -av ">=debian-sources-4.13.10-1"because with an ego sync && emerge -avuND world it dit not show up in the package tree, when I searched for it.
It compiled without a problem, and after (manually) adapting the /boot/grub/grub.cfg, replacing 4.8.15-1 with the correct version, the Virtual Machine booted up correctly
Also, KDE Plasma with virtual box guest additions booted up correctly.
Kind regards,
Valerie