On 04/06/14 19:21, Duncan wrote: > Rich Freeman posted on Wed, 04 Jun 2014 07:41:23 -0400 as excerpted: > >> On Tue, Jun 3, 2014 at 4:24 PM, Alan McKinnon <alan.mckin...@gmail.com> >> wrote: >>> Yes, it *is* a simple matter of running one easy command. Portage does >>> that for you with trivial ease. But portage doesn't tell you *which* is >>> the one easy command. >>> >>> A news item does that. >> That is the real challenge here. It isn't obvious to most users that >> upower is causing the problem, and it is even less obvious to users >> without using Google that there is an alternative. >> >> Anybody who doesn't read the lists or GMN wouldn't probably wouldn't >> realize that the simple fix exists. > This. > > It's only simple for me because I saw it right here ahead of time, and > it's only simple for ssuominen because he knows about the other choice > since he created the package.
Wrong. I'm always using the -t (--tree) flag with Portage and I would have seen upower being the culprit immediately, and second command would have been `eix upower` to see available versions, at which point I would have seen upower-pm-utils, and figured it out. Just like with any other B blocker that comes up with normal upgrade process. I've never since 2006 needed to ask anyone anything regarding blockers, and it has always been trivial to find out these things. Long before anything called "news items" even existed. - Samuli
