Difference between revisions of "Gentoo: System update"

From Luky-Wiki
Jump to: navigation, search
(1. Update local repository)
Line 1: Line 1:
__NOTOC__
 
 
 
'''Warning! Warning! Warning!''' ... This article is my cookbook. It is designed for binary type update (two stages deployment) and only as reference. You can use it but it may not be suitable for all configurations. Use common sense and add / modify / repeat commands if necessary. I am doing same during update. Some of commands have <code>--pretend</code> just to see actions before they are applied. I normally review them and rerun command without <code>--pretend</code> option.
 
'''Warning! Warning! Warning!''' ... This article is my cookbook. It is designed for binary type update (two stages deployment) and only as reference. You can use it but it may not be suitable for all configurations. Use common sense and add / modify / repeat commands if necessary. I am doing same during update. Some of commands have <code>--pretend</code> just to see actions before they are applied. I normally review them and rerun command without <code>--pretend</code> option.
  

Revision as of 15:26, 9 May 2017

Warning! Warning! Warning! ... This article is my cookbook. It is designed for binary type update (two stages deployment) and only as reference. You can use it but it may not be suitable for all configurations. Use common sense and add / modify / repeat commands if necessary. I am doing same during update. Some of commands have --pretend just to see actions before they are applied. I normally review them and rerun command without --pretend option.

System Update

1. Update local repository
eix-sync

or

emerge --sync

or (if repository is synced)

eix-update
2. Clean logs from previous update
find /var/log/portage -maxdepth 1 -type f -ls -delete
3. Clean distfiles and package directory
eclean-dist -d ; eclean-pkg -d
4. Update system including build dependencies
4a. on "build" system
emerge --ask --update --deep --newuse --with-bdeps=y @world
4b. on "prod" system
emerge --ask --update --deep --newuse --with-bdeps=y --binpkg-changed-deps=n @world
5. Commit or reject configuration changes in "/etc"
etc-update
6. Review messages from packages
elogv
7. Clean packages with no dependency on "world" package set
emerge --ask --depclean
8. Scan for broken dependencies
  • python:
python-updater --pretend
  • perl:
perl-cleaner --all --pretend
  • libraries detected by system:
emerge -ask @preserved-rebuild
  • libraries not detected by portage:
revdep-rebuild    --ignore --pretend
revdep-rebuild.sh --ignore --pretend
9. If previous commands result in package rebuild then review again logs and possible configuration changes
elogv
etc-update
10. Verify / validate dependency starting from "world" fileset
emerge --pretend --verbose --update --deep --newuse --with-bdeps=y @world
11. Check for possible updates by each package separately (watch versions in slots)
eix --upgrade
12. Search for possible obsolete portage configuration and installed packages
eix-test-obsolete
13. Check installed packages agains GLSA (Gentoo Linux Security Advisories)
glsa-check --test --nocolor --verbose all
14. Rebuild X11 drivers and linked packages
emerge --ask @x11-module-rebuild
emerge --ask app-crypt/hashcat app-crypt/johntheripper

Note: binary packages needs to be disabled on prod system:

export FEATURES="-buildpkg -getbinpkg"
export CFLAGS="-O2 -march=native -mfpmath=sse -fomit-frame-pointer -pipe"

Binhost checks

.
.
.
.
.
.
.
.
.
.
.