Emerge sync told me (in part) * An update to portage is available. It is _highly_ recommended * that you update portage now, before any other packages are updated. * Please run 'emerge portage' and then update ALL of your * configuration files. * To update portage, run 'emerge portage'. If I take the emphasized "ALL" literally, that could be around a thousand files. That's not going to happen, of course. But I'm not sure what's actually meant, nor what sort of update the original author had in mind. All I did was run "etc-update" and deal with all of the changes presented (one file). I submit that if that is what was wanted, it could have been more clear. Reproducible: Always Steps to Reproduce: 1. emerge sync (when a portage update is outstanding) 2. examine the output 3. Actual Results: Unclear instructions (literal copy posted above) Expected Results: Something like * and deal with all changed config files with a mention of the methods such as "etc-update". I use only etc-update and forget what the others are.
(In reply to comment #0) > If I take the emphasized "ALL" literally, that could be around a thousand > files. That's not going to happen, of course. Exactly. And if it did, you'd still need to do it. > But I'm not sure what's actually meant, nor what sort of update the original > author had in mind. Yes it is; see it's pretty clear really isn't it? ;) > All I did was run "etc-update" and deal with all of the changes presented > (one file). > > I submit that if that is what was wanted, it could have been more clear. > I submit that it was ^^. > Expected Results: > Something like > * and deal with all changed config files That could work but it's already clear as you yourself mentioned. > with a mention of the methods such as "etc-update". I use only etc-update and > forget what the others are. Er etc-proposals, cfg-update, dispatch-conf off the top of my head. http://forums.gentoo.org/viewtopic-t-546828.html might help you to maintain your system with a minimum of effort. (NB it's not official, but I am one of the authors so you can email me with problems.)
Sigh; post-install messages are not intended to replace any howto's on working with portage, and there's absolutely zero need to clutter them even more with lists of tens of official, semi-official or non-official utilities used to deal with updating config files. Is the message really so horribly unclear to you, or did you just feel like nitpicking?
We should probably just remove the part about config files, it's redundant anyway as `emerge portage` will show the usual message anyway if there is anything to update.
(In reply to comment #2) > Sigh; post-install messages are not intended to replace any howto's on working > with portage, and there's absolutely zero need to clutter them even more with > lists of tens of official, semi-official or non-official utilities used to deal > with updating config files. Is the message really so horribly unclear to you, > or did you just feel like nitpicking? > It caused me to spend some time on worrying if I was doing the right thing. As I think about it, the real culprit was the emphasis on "ALL". If that had been lowercase, or just omitted, I would have done what I usually do. And that would have worked just fine. But the presence of allcaps seemed to mean that something special was going on and I wanted to figure out what it was. Another poster has recommended dropping the comment entirely. That would have worked for me also. So maybe it's a nit. But it cost me time (quite aside from the bug submission and associated conversations) and worry that it did not need to cost me, and I presumed I might not be alone. So note: I'm not in favor of clutter. There are now 3 solutions to consider and none of them is a single character longer than what is present now. They would all have avoided my problem: 1) Lowercase the ALL 2) Remove the ALL/all 3) Remove the entire message. Thanks, and sorry to bother you. ++ kevin
(In reply to comment #4) > I think about it, the real culprit was the emphasis on "ALL". If that had been > lowercase, or just omitted, I would have done what I usually do. And that > would have worked just fine. But the presence of allcaps seemed to mean that > something special was going on and I wanted to figure out what it was. > But the "ALL" is correct; you're supposed to deal with all the config updates as soon as an emerge run has finished. A critical package might have been updated and its config might need adjustment. > Another poster has recommended dropping the comment entirely. That would have > worked for me also. > Only because portage will say "IMPORTANT x config files need updating" after every single package. I don't accept it needs to change at all; having that message has emphasized the importance of keeping config files up to date to me and countless other users. It might not be so vital to update other config files after a portage change, but really the admin shouldn't let the situation you describe happen. And I think it's better to educate users about that. So I vote to keep the message as is, FWIW.
There is now: print red(" * ")+"To update portage, run 'emerge portage' now." Running this command causes: >>> Recording sys-apps/portage in "world" favorites file... I suggest replacing this line with: print red(" * ")+"To update portage, run 'emerge -1 portage' now."
(In reply to comment #6) > There is now: > print red(" * ")+"To update portage, run 'emerge portage' now." > > Running this command causes: > >>> Recording sys-apps/portage in "world" favorites file... > > I suggest replacing this line with: > print red(" * ")+"To update portage, run 'emerge -1 portage' now." No, as a) unrelated to this bug b) it doesn't matter in 99.99% of all cases c) it would go against some plans I have wrt option handling (especially --oneshot) d) the lack of (any) options in the canonical portage update command is an important characteristic
e) (related to b) Many of us (users) think having portage in world is a good idea. Maybe it's not needed, but then I haven't even run emerge --depclean yet.. Sorry, is there any reason this bug is still open? I sincerely can't imagine this stuff troubling anyone who has maintained a Gentoo box for more than 3 months. (And even that long, only if they don't read the forums..)
(In reply to comment #8) > Sorry, is there any reason this bug is still open? I sincerely can't imagine > this stuff troubling anyone who has maintained a Gentoo box for more than 3 > months. (And even that long, only if they don't read the forums..) Because the change isn't released yet.
(In reply to comment #5) Apologies to all. A voice in my head says I've already spoke my piece, and you're either going to agree with it or not. It's beyond my control now. But I'm not wise enough to listen. Sigh. > (In reply to comment #4) > > I think about it, the real culprit was the emphasis on "ALL". If that had been > > lowercase, or just omitted, I would have done what I usually do. And that > > would have worked just fine. But the presence of allcaps seemed to mean that > > something special was going on and I wanted to figure out what it was. > > > But the "ALL" is correct; you're supposed to deal with all the config updates > as soon as an emerge run has finished. A critical package might have been > updated and its config might need adjustment. > It can be correct and misleading at the same time. It raises questions in the mind (well, mine at least): why are you SHOUTING? why is this being said _here in addition_ to other places that talk about updating? Both issues suggest something special going on when, if I now understand rightly, there is nothing more than the usual set of reasons for keeping config files up-to-date. > > Another poster has recommended dropping the comment entirely. That would have > > worked for me also. > > > Only because portage will say "IMPORTANT x config files need updating" after > every single package. Right. Exactly. It says that already and we're all used to it. An extra message raises extra issues. > > I don't accept it needs to change at all; having that message has emphasized > the importance of keeping config files up to date to me and countless other > users. It might not be so vital to update other config files after a portage > change, but really the admin shouldn't let the situation you describe happen. > And I think it's better to educate users about that. So I vote to keep the > message as is, FWIW. > Isn't this message one that comes only once or twice a year when portage is updated? I doubt you were somehow waiting months for a reminder to run your favorite config tweaker.
In reply to comment #10) > It can be correct and misleading at the same time. It raises questions in the > mind (well, mine at least): why are you SHOUTING? why is this being said _here > in addition_ to other places that talk about updating? I think you can relax because we've removed this part: * that you update portage now, before any other packages are updated. * Please run 'emerge portage' and then update ALL of your It's fixed in svn and will be released in portage-2.1.3_rc7.
The new message will look like this: * An update to portage is available. It is _highly_ recommended * that you update portage now, before any other packages are updated. * To update portage, run 'emerge portage' now.
This has been released in 2.1.3_rc7.
