Bug 25256 – emerge -u/U system/world warning.

• Product: Portage Development
• Status: RESOLVED DUPLICATE

[Description Ian Leitch (RETIRED) 2003-07-25 07:11:22 UTC]

Many, many people on the forums seem to be unaware of the dangers of a blind
emerge -u/U system/world. They run it, something breaks and they have no idea
what it was because they didn't see any important information along the way. I
think a little warning is needed to make people aware of emerging blindly. 


Reproducible: Always
Steps to Reproduce:
1.
2.
3.

[Comment 1 Ian Leitch (RETIRED) 2003-07-25 07:11:59 UTC]

Created attachment 14998 [details, diff]
emerge.patch

[Comment 2 SpanKY 2003-07-25 15:18:12 UTC]

*** This bug has been marked as a duplicate of 11359 ***

[Comment 3 Ian Leitch (RETIRED) 2003-07-25 15:53:18 UTC]

Doesn't look like a dup to me...? The enhancements in 11359 are extra logging. My patch makes portage produce a warning when running emerge -u world/system. 

"- /usr/bin/emerge uses dump() to dump the ELOGFILE to stdout." - This wont stop people running blind world updates in the first place as by the time ELOGFILE gets dumped the damage will have been done.

[Comment 4 SpanKY 2003-07-25 16:00:56 UTC]

yes, the extra logging logs all that information you would miss if you did a blind 
update ... thus people could do a blind update, come back later, read the logged 
output, and then figure out what they need to do to not have a bj0rked system 

[Comment 5 Ian Leitch (RETIRED) 2003-07-25 16:17:47 UTC]

Well thats a kind of odd way of handling the problem IMO, but your the boss.

[Comment 6 Ian Leitch (RETIRED) 2003-07-25 16:20:21 UTC]

postemptive ;)