jhan

That seems to be a warning about the different python versions for those two packages. Currently numpy-1.17.0_rc1 accepts python 3.5, 2.6 and 3.7 while inkscape-0.92.4 just python 2.7 Looks like bug report FL-6568 to me.

It seems to be a similar case as bug FL-6628 That would mean that you need to emerge dev-libs/gobject-introspection and then the problem should be solved. If you could verify that it would be good if you could also open a bug report at bugs.funtoo.org so that the problem can be fixed.

What are the permissions of the directories above? Do you have enough free space available (in all partitions)? Any error messages, e.g. in dmesg? Can you read the contents of the file? An OSError can be a lot of things. Unless you can find more information, there isn't much to say.

For running kde with wayland without xorg there still seem to be a few showstoppers but I think kwin does help with getting started. Gnome should be also on the way, at least according to their roadmap but you can also find more information there, including information for using android drivers. Generally my information is that the usability of wayland without xorg still depends on the applications you want to use and their support for wayland. Looking at the packages on gentoo that support wayland, the list is not that big yet. There are also some cases where wayland still causes problems, see Link1 and link2 I was looking at trying out wayland as well but it seems to be now quite where I would be willing to do that. At least not for my main computer.

Look at the output of 'epro' arch should be set there. See https://www.funtoo.org/Install/Profiles and https://www.funtoo.org/Funtoo_Profiles for more details.

That is the important part. Making the suggested changes could solve the problem. You can either do this manually, by adding the USE flags to /etc/portage/package.use or by choosing the appropiate mix-in for your graphics card. Available mix-ins can be shown with 'epro list'.

I would either remove the old version or rename it, so that it fits into the new versioning scheme. If I see that correctly, it seems to me that the new scheme is something like <main version>.<year>.<yearly release number> With 8046 the 12th release for 2016 that would be 1.2016.12 or 0.2016.12 in the new scheme, depending on the real meaning of the first digit. Packages that may depend on plantuml may need to be looked at but that has to be done anyhow, to make sure that the new scheme doesn't lead to problems.

Well, you know how it is with software that has dependencies, sometimes some of the dependencies can be forgotten. It is called making an error. And that is also the reason why there is the pull request for some time, to deliver the missing dependency. The reason why the pull request is not accepted yet, is that all newer versions of lua >dev-lang/lua-5.1.5-r4 are slotted on gentoo, as can be seen at https://packages.gentoo.org/packages/dev-lang/lua That might not be a problem for you or me but @drobbins doesn't like it and would prefer it "unslotted". That is his right, as it is his project. If you don't like this situation you can either convince him otherwise, so that the PR will be accepted. Or, better, "unslot" the new lua version and submit your on pull request. The open bug report for the update of conky can be found at https://bugs.funtoo.org/browse/FL-6457

https://bugs.funtoo.org/browse/FL-6463

Because you probably had a reason to choose one profile over another. And looking at the difference between those two mix-ins, I would say that the amdgpu mix-in seems to be more fitting to your make.conf settings (VIDEO_CARDS="gallium-r600 swrast r600 radeon"): farout ~ # more /var/git/meta-repo/kits/core-kit/profiles/funtoo/1.0/linux-gnu/mix-ins/gfxcard-older-ati/* /var/git/meta-repo/kits/core-kit/profiles/funtoo/1.0/linux-gnu/mix-ins/gfxcard-amdgpu/* :::::::::::::: /var/git/meta-repo/kits/core-kit/profiles/funtoo/1.0/linux-gnu/mix-ins/gfxcard-older-ati/make.defaults :::::::::::::: VIDEO_CARDS="radeon r100 r200" USE="vdpau" (Next file: /var/git/meta-repo/kits/core-kit/profiles/funtoo/1.0/linux-gnu/mix-ins/gfxcard-amdgpu :::::::::::::: /var/git/meta-repo/kits/core-kit/profiles/funtoo/1.0/linux-gnu/mix-ins/gfxcard-amdgpu/make.defaults :::::::::::::: VIDEO_CARDS="amdgpu radeon gallium-r300 gallium-r600 gallium-radeonsi" USE="xa xvmc vaapi vdpau" farout ~ #

Are you sure that the mix-in gfxcard-older-ati applies for your card and not gfxcard-amdgpu? I'm not familar with the AMD/ATI cards but I think that the HD6450 is a bit younger than a R100 or R200 mentioned at https://www.funtoo.org/Make.conf/VIDEO_CARDS/Mix-ins

That probably depends on the terminal you are using. For xterm the colors and other visual settings used are stored in ~/.Xdefaults

Maybe you should add not only pt but the correct name of the keymap as well. Looking at the available pt keymaps: sicota@farout /data/incoming $ find /usr/share/keymaps/ -name "*pt*" /usr/share/keymaps/i386/olpc/pt-olpc.map.gz /usr/share/keymaps/i386/qwerty/pt-latin9.map.gz /usr/share/keymaps/i386/qwerty/pt-latin1.map.gz /usr/share/keymaps/mac/all/mac-pt-latin1.map.gz sicota@farout /data/incoming $ I would suggest to use something like pt-latin1 instead of pt.

Do you mean the testing or the upgrade process? As far as I know some parts are tested automatically but you can't test everything as one would need all possible hard- and software configurations to do that.

You can follow the instructions at https://www.funtoo.org/Upgrade_Instructions/1.4-release and report any problems in IRC or bugs.funtoo.org (if they are not already there).