I am about to give Gentoo up

[JustAnother]

[NeddySeagoon]

helecho,

[NeddySeagoon]

JustAnother,

[JustAnother]

I think most of the use cases can be drawn up from common sense.

Here is a simple idea -- just start building a list of the terms that would go into a glossary. That may sound dumb, but it is surprising how much such a simple act might reveal. Then somebody starts back referencing the terms to see what is already in the docs, and where to get it. Then somebody starts writing the term definitions that become the nucleus of more robust entries. Each of these steps is a value adder, and simplifies the next step.

[NeddySeagoon]

JustAnother,

[Tony0945]

JustAnother, and keep reading the forum and not just your problems. In time you will start to see it all come together. And also, who to trust and who to not trust.

[JustAnother]

[NeddySeagoon]

JustAnother,

Gentoo has Larry the Cow as a mascot.

There is lots of Gentoo terminology that users don't need to be aware of until they are beginning to stray from the beaten path.
Then there is no point in spoon feeding ase every path is different.
That's a lot of effort for a small fraction of Gentoo users.

I would be pleased to see a pilot page appear on the Wiki though.

Gentoo is not really a Linux distro. Its a toolkit you use to implement your own distro.
Don't think of Gentoo as a distro.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.

[1clue]

[Fitzcarraldo]

[Spargeltarzan]

I also believe we have got so many documented mechanisms (already) in the forums which could become migrated into a knowledge-database.

Reading the forums help a lot, but the forum itself should be more a place to ask for help and discuss topics.
Also in a forum a user usually reads (if he or she is motivated) 3-4 pages back and the search function is not the best unfortunately. (maybe is also time for a new forum? - with support for tablets/smartphones? if the forum should contain recent documentation, sticky items must be updated urgently)

Just recently I turned my system to be non-bootable following the Wiki for Intel Microcode Update - in the forum there was already the right mechanism documented.

Agree with Gentoo we can create our very own Distro, but it follows some rules. (by the way, in my point of view quite strict rules, to achieve a good system)

If we want to turn the "downwards spiral", this currently for sure means much effort for a few users. The userbase will grow afterwards!

We also need some positive review results in Google.

Larry the cow is awesome.
_________________
___________________
Regards

Spargeltarzan

Notebook: Lenovo YOGA 900-13ISK: Gentoo stable amd64, GNOME systemd, KVM/QEMU
Desktop-PC: Intel Core i7-4770K, 8GB Ram, AMD Radeon R9 280X, ZFS Storage, GNOME openrc, Dantrell, Xen

[Cyker]

Woo! Larry the Cow!

[mimosinnet]

[Spargeltarzan]

The Grub2 section of it is obsolete (such deep Grub changes actually are never a good idea), I have copied microcode.cpio to /boot and I have just added initrd /microcode.cpio to grub.cfg (I didn't use an initramfs before)
_________________
___________________
Regards

Spargeltarzan

Notebook: Lenovo YOGA 900-13ISK: Gentoo stable amd64, GNOME systemd, KVM/QEMU
Desktop-PC: Intel Core i7-4770K, 8GB Ram, AMD Radeon R9 280X, ZFS Storage, GNOME openrc, Dantrell, Xen

[P.Kosunen]

[Waterdevil]

Hello World,

for your information:

I tried to help to improve the documentation for troubleshooting gentoo portage issues.

I edited https://wiki.gentoo.org/wiki/Troubleshooting and added an additional example:

[Mr. T.]

It's a matter of perspective: it may be easier to remove a wrongly exposed example rather than improve it!

[asturm]

This is not an example of a block. Portage would in this circumstance happily emerge other packages, but it is telling you why a certain upgrade is not possible. The example would definitely need improvement explaining the reason for the necessary lower than available version.

[Waterdevil]

Ok, I want to list possible emerge problems and their solution. But I don't know how to improve this.
I know I had this issue, I wrestled with it for many days and I wish I had such a example for a possible solution. I didn't understand '<' so that neither 4.7 nor 4.9 would solve.

All this emerge output is way too complicated for me.

Is there a wrapper for emerge errors to translate to clear english?
_________________
_____________________
Aut semper aut numquam

Main-Sys: LianLi modded Big Cube 8000,X11DPG-QT,MEM:64G,LSI 9305,HDD:102TB(16x3T,8x6T,4x1T,1x0,5Tm.2,4x0,5TSSD),nVidia GTX1060,NIC:2x10GbSFP+,Fans:20,PSU:1200W+500W,UPS:APC1500VA,FibreChannel,Tandberg LTO-6

[LIsLinuxIsSogood]

Do you really need a way of shortening the output or would just a clear description of the problem also be helpful. If so the difference here as was already described is that in this case the slotted versions oc packages are what is presenting conflict. Therefore if you removed your dependency of mate-applet then you would find no error. That is what is known as a slot conflict, and i guess if you have any doubt about it then go on try it out. You can even afterwards reinstall the mate-applet to see if there is nothing special here you are looking at a decision to either use package mask or else if for some very odd reason you want to be on just the newest releases then i guess removing the previous dependency as i mentioned. What primarily makes this not something besides a block, is the versions are all for the same software rather that conflict is usually referred as a slot conlict.

[Fitzcarraldo]

Waterdevil,

as asturm pointed out, the particular example you gave is not a block. It is just warning you that Portage would skip updating cpupower to Version 4.9.0-r1 because your installation has Version 1.12.1-r4 of mate-applets installed, and that version of mate-applets requires a version of cpupower that is lower than Version 4.7.

So I recommend you modify the Wiki text to something similar to the following:

[LIsLinuxIsSogood]

In a sense the OP's situation is almost identical to a Blocked Package except the source of the problem is an already installed package that requires updating and another package that is already installed. No update to the wiki should be made except if it offers the suggestion for a route of how to get around the problem. The description of a Blocked Package is and isn't important, unless it helps to work through the issue. In other words, yes it is not a Blocked Pakage, but why it's not is because of a nuance about how the package manager handles errors in dependency resolution. The Blocked Package actually is a conflict of different packages that are each being pulled in from different dependencies, or something like that (in my own words). Basically ebuilds with dependencies built in for if a package needs another one that is somehow not satisfactory for another package that is a Blocked Package.

Or like the Handbook has it...
When one of these dependencies explicitly marks a package or virtual as being not compatible, it triggers a blockage.

So what should OP be doing?
My feeling is the best way around that situation, based on my own experimenting over time is to basically remove a package and hopefully you remove the right one, in order to proceed with an update and let portage work out the dependencies again once that conflict present in versions is removed via a removal of the package itself. There's no real harm in installing and reinstalling packages a bizillion times and if you are certain that the packages are being maintained as they are then it is likely to work.

[fca]

I feel like I'm in a bit of a similar situation here as the OP. Long time Gentoo user (see join date), recently reconnected my linux computer after a move, and now seeing at least 3 major upgrade blockers (perl, new profiles, python targets?). It's a bit disheartening, especially since some packages seem to fail build, and then "emerge -e world" just gives up after the first build failure, even with a --keep-going, or emerge --resume. Given that I have around 1700 packages to install (including libreoffice, chromium and so on, which will take a ton of time even if everything goes smoothly), I start wondering if Gentoo is still for me.

And the last time a simple "emerge -u world" worked I cannot remember...

I see some conflicting advice also: update often, but only update when you have the time to fix things. How is this supposed to work?

The point is, encountering and resolving a block takes time (sometimes a lot of time), and I find myself getting less and less patient for these kind of issues. I want to use Gentoo, not troubleshoot its problems.

Anyway, I have no real point here, except don't disparage the OP: for every such complaint there are tons of people just quietly leaving, which cannot be good, right?

[NeddySeagoon]

fca,

That you have all these update in one go indicates your system is out of date.

Do perl on its own.

[asturm]