From a recent gentoo-user post: > however at the end a message told me it was highly recommended to update > portage. No syntax example was suggested, and none found in the > installation handbook. So I used: > #emerge portage <it ran for a while and then produced this error> Now the Handbook states clearly to ignore this error, yet it seems that this question pops up regularly in the mailing list. I would like to suggest that section be highlighted in big bold blinking red letters :) I'm joking about the big bold blinking letters, but since this issue does seem to cause consternation due to the fairly specific warning coming from the emerge sync command, I do think that that text should be highlighted some way to draw the user's attention to it. Reproducible: Always Steps to Reproduce: 1. During installation of Gentoo, run emerge sync 2. Fail to note sentence stating to ignore error. 3. See error from portage about newer version, freak out and run emerge portage 4. emerge portage fails, freak out more and post to Forum, IRC, Mailing list about the install not working 5. Get told that's normal and feel silly. Actual Results: See Above Expected Results: 1. During install of Genoo, run emerge sync 2. See error message from portage stating to update portage. 3. Think "no problem" I saw this big warning in the handbook saying this could happen. 4. Continue with the install
Created attachment 36194 [details, diff] dcron.rc6.patch
Comment on attachment 36194 [details, diff] dcron.rc6.patch wrong bug, sorry.
I'm hesitant... In the Gentoo Handbook I'm trying to reduce the amount of warnings (the red boxes with smaller font) as they tend to give the users the idea that the instructions are flawed. I want to use <warn>...</warn> only when there is a temporary issue which will get fixed by the appropriate developers. Using a <note>...</note> however makes some users skip the remark (as it's a note, not part of the sequence of instructions). I'm more thinking along the lines of keeping it as-is. It is perfectly normal that users don't read everything in the documentation. It's not fun, but it's normal. Being told that it is in the document is just a learning proces :)
Marking this as WONTFIX.
