On Thu, Jan 24, 2019 at 2:04 PM Dale <rdalek1...@gmail.com> wrote: > Neil Bothwick wrote: > > On Thu, 24 Jan 2019 13:42:04 -0600, Dale wrote: > > > >> I'm trying to recall but am not sure, is this the same Alan that used to > >> come on here and post this sort of thing when the problem was in the > >> chair not Gentoo? I recall the person I'm speaking of having a script > >> that just created a mess and then he blamed it on Gentoo. I might still > >> have some of those emails but someone else may recall if this is the > >> same person or not. > > It is. > > > > > > > Yep. I went and found this little gem. For those interested, this is > the script he used back then. I'm not sure if he still does today or > not. Some of you may find it funny. Some may just cry, for various > reasons. ;-) > > Alan Grimes wrote: > > I use two scripts for all emerge use, the goal is to run one command and > > then walk away: > > > > Standard general update script: > > ####################### > > tortoise ~ # cat sysupdate > > > > #they must have moved or removed the logs, might have to track them down > > again... > > #rm /var/log/emerge* > > > > # cache /usr/portage > > echo "caching /usr/portage. This will take a long time." > > time ls -R /usr/portage > /dev/null > > > > emerge --sync > > layman --sync ALL > > > > emerge --update --verbose portage > > emerge --update --newuse --deep --with-bdeps=y system --keep-going > > emerge --update --newuse --deep --with-bdeps=y world --keep-going > > > > rm -f /var/cache/revdep-rebuild/*.rr > > revdep-rebuild > > emerge --skipfirst --resume > > emerge --skipfirst --resume > > etc-update > > eclean-dist > > ######################## > > > > The eclean line was added just a few days ago from this thread... > > > > This one is intended to be a nice gentle update script. > > It caches the portage tree, then syncs everything, then updates > > everything starting with critical system packages, then all world > > packages... > > > > Then it cleans stuff up, it jcakhammers the revdep-rebuild but not too > > hard.... > > > > > > This next script is what I use when emerge starts giving me shit: > > > > ################## > > tortoise ~ # cat keepgoing > > emerge --update --newuse --deep --with-bdeps=y system > > emerge --skipfirst --resume --nodeps > > emerge --skipfirst --resume --nodeps > > emerge --skipfirst --resume --nodeps > > > > emerge --update --newuse --deep --with-bdeps=y world > > emerge --skipfirst --resume --nodeps > > emerge --skipfirst --resume --nodeps > > emerge --skipfirst --resume --nodeps > > emerge --skipfirst --resume --nodeps > > emerge --skipfirst --resume --nodeps > > emerge --skipfirst --resume --nodeps > > emerge --skipfirst --resume --nodeps > > emerge --skipfirst --resume --nodeps > > emerge --skipfirst --resume --nodeps > > emerge --skipfirst --resume --nodeps > > > > rm /var/cache/revdep-rebuild/*.rr > > revdep-rebuild > > emerge --skipfirst --resume --nodeps > > emerge --skipfirst --resume --nodeps > > emerge --skipfirst --resume --nodeps > > emerge --skipfirst --resume --nodeps > > > > etc-update > > ################### > > > > It's basically the same as the working section of the above but instead > > of letting emerge do it's thing, it jackhammers that bitch as hard as > > possible to get as much updated as possible, but it requires emerge to > > do something and not error out for no good reason... I expect prune and > > depclean to be useless but I kinda need update to basically work every > > time. =\ > > Whatever fails on this script, I just live with until next week/month. > > > > ################### > > tortoise ~ # ./pretendupdate > > > > These are the packages that would be merged, in order: > > > > Calculating dependencies / > > > > !!! Problem resolving dependencies for sys-apps/util-linux from @system > > ... done! > > > > !!! The ebuild selected to satisfy "sys-apps/util-linux" has unmet > > requirements. > > - sys-apps/util-linux-2.27.1::gentoo USE="caps cramfs ncurses nls pam > > python readline suid udev unicode -build -fdformat -kill (-selinux) > > -slang -static-libs -systemd -test -tty-helpers" ABI_X86="32 64 -x32" > > PYTHON_SINGLE_TARGET="-python2_7 -python3_3 -python3_4" > > PYTHON_TARGETS="python2_7 python3_4 -python3_3" > > > > The following REQUIRED_USE flag constraints are unsatisfied: > > python? ( exactly-one-of ( python_single_target_python2_7 > > python_single_target_python3_3 python_single_target_python3_4 ) ) > > > > The above constraints are a subset of the following complete > expression: > > python? ( exactly-one-of ( python_single_target_python2_7 > > python_single_target_python3_3 python_single_target_python3_4 ) > > python_single_target_python2_7? ( python_targets_python2_7 ) > > python_single_target_python3_3? ( python_targets_python3_3 ) > > python_single_target_python3_4? ( python_targets_python3_4 ) ) > > > > (dependency required by "@system" [set]) > > (dependency required by "@world" [argument]) > > > > tortoise ~ # cat ./pretendupdate > > emerge --update --newuse --deep --with-bdeps=y world --verbose --pretend > > tortoise ~ # > > > > ########### > > > > Google is not being helpful with this... =( > > > > > I have to say, the first sentence says a LOT. Who here runs emerge > without checking to make sure it is going to do what you want it to > first? Heck, I always run with -a and look at USE flags and such before > even thinking about hitting y to continue. Sometimes, it may take me > adjusting settings two or three times to get what I need. It goes > downhill from there with his script. Heck, if I were emerge, I'd break > too. lol > > Dale > > :-) :-) >
A lot of people run emerge without checking the preliminary console output. I don't think it's fair to imply that doing that is somehow wrong. The vast majority of Linux distributions support unattended upgrades without a second thought.
