kundor

Well, I tried, but didn't make it. I added =dev-lang/python-3.9.13 to /etc/portage/package.unmask, so that it could be installed, and I added PYTHON_TARGETS="python2_7 python3_9" to /etc/portage/make.conf. (I also tried adding a line PYTHON_SINGLE_TARGET="python3_9" to make.conf, but that seemed to cause more problems, so I got rid of that.) I also had several packages in /etc/portage/package.use with flags like "PYTHON_TARGETS: -* python3_7", so I changed all of those to python3_9. After that, trying to do an "emerge -auDN @world" gave me pages of errors, so I gave up. python_merge_err

I noticed that ebuilds for Python 3.8, 3.9, and 3.10 showed up in portage. This seems exciting, because I've been chafing with missing some of the more recent features of Python for a while now! They don't get installed by default, though, I assume because they are masked or something like that. Can someone explain what I need to do to get Python 3.10 installed? Adding something to package.unmask, or setting a PYTHON_TARGET or PYTHON_SINGLE_TARGET variable in make.conf, or anything like that? I understand if I'm doing this at my own risk.

The version brave-bin-1.32.94.ebuild is no longer in the tree, only brave-bin-1.31.91.ebuild. 1.31.91 was released later, backporting fixes to the 1.31 branch. My guess is that the autogen script is not determining the latest version correctly.

# emerge -auDN @world ... [ebuild UD ] www-client/brave-bin-1.31.91::browser-kit [1.32.94::browser-kit] USE="-gnome-keyring" L10N="-am -ar -bg -bn -ca -cs -da -de -el -en-GB -en-US -es -es-419 -et -fa -fi -fil -fr -gu -he -hi -hr - hu -id -it -ja -kn -ko -lt -lv -ml -mr -ms -nb -nl -pl -pt-BR -pt-PT -ro -ru -sk -sl -sr -sv -sw -ta -te -th -tr -uk -vi -zh-CN -zh-TW" 126,429 KiB After an `ego sync`, emerge wants to downgrade brave-bin. Seems odd!

After a sync today, I could emerge it, so this was fixed. Thanks!

When I try to `emerge gvim`, I get emerge: there are no ebuilds to satisfy "~app-editors/vim-core-8.2.0430". (dependency required by "app-editors/gvim-8.2.0430::editors-kit" [ebuild]) Indeed, there only seems to be vim-core 8.2.0378. Is there a workaround to get gvim to emerge?

I used https://build.funtoo.org/1.4-release-std/x86-64bit/intel64-skylake/stage3-latest.tar.xz. Of course that's changed since. I used the version current around September 25 or 26, which is no longer available to download. The current version—stage3-intel64-skylake-1.4-release-std-2019-10-11.tar.xz—still has separate /usr/lib and /usr/lib64, so it seems that would still cause this bug. The stage3 tarball /lib is a symlink to /lib64, though (which is not the case on my system). So should I move everything from /lib to /lib64, and everything from /usr/lib to /usr/lib64?

Trying to emerge dev-java/ant-core (in the course of emerging libreoffice), I got the error: ERROR: prepare No binary for rewriting found. Do you have dev-java/javatoolkit installed? ERROR: dev-java/ant-core-1.10.5-r2::java-kit failed (prepare phase): xml-rewrite not found Call stack: ebuild.sh, line 93: Called src_prepare environment, line 4125: Called java-ant_xml-rewrite '-f' 'build.xml' '-c' '-e' 'javadoc' '-a' 'failonerror' '-v' 'false' environment, line 1896: Called die I do have dev-java/javatoolkit installed. I tried looking at the function java-ant_xml-rewrite() in core-kit/eclass/java-ant-2.eclass to fix it, but I don't even know what an eclass is. I did manage to figure out that it was looking for a file /usr/lib64/javatoolkit/bin/xml-rewrite-2.py, but all the files installed by dev-java/javatoolkit are in /usr/lib/javatoolkit/ instead. The "lib64" comes from a function get_libdir, and I don't know where that's defined. I created a symlink /usr/lib64/javatoolkit pointing to /usr/lib/javatoolkit and then the emerge worked. Are /usr/lib and /usr/lib64 even supposed to be separate directories? This is a newly installed Funtoo 1.4 system, and they were separate directories after the installation (so are /lib and /lib64).

When following the directions for a new 1.4 install at https://www.funtoo.org/Install/Kernel, I tried # echo "sys-kernel/debian-sources binary" > /etc/portage/package.use # emerge -av debian-sources But this failed with ERROR: LUKS support cannot be included: no file /sbin/cryptsetup. I noticed the output included Running with options: --no-save-config --no-oldconfig ... --disklabel --lvm --luks --mdadm --no-btrfs --no-zfs ... and the --lvm --luks part seemed wrong, since my system doesn't have either of those things. After comparing debian-sources-5.2.9_p2-r2.ebuild to debian-sources-lts-4.19.67_p2-r1.ebuild, which had built successfully in the previous step, I changed lines 224 and 225 of the ebuild from --lvm \ --luks \ to $(usex lvm --lvm --no-lvm ) \ $(usex luks --luks --no-luks ) \ and after that it emerged successfully. It looks like the ebuild has updated to 5.2.17_p1 since I synced, but those lines are still the same, so perhaps the same fix would be beneficial for others?