[gentoo-user] Consistency checking

[gentoo-user] Consistency checking

[meino.cramer]

Hi,

I know of three commands to check the consistency of a Gentoo system:


    eix-sync && emerge --color=n -p -v --newuse --update --deep world
    emerge -p -v --depclean
    revdep-rebuild --ignore -p -v

of course, one has to remove the -p and -v flags after checking the
putput of the commands.

What else can be checked and should be checked from time to time or
after each update?

Thank you very much in advance for any help!

Best regards,
mcc

Re: [gentoo-user] Consistency checking

[YoYo Siska]

On Tue, Nov 01, 2011 at 04:45:25AM +0100, meino.cramer@gmx.de wrote:
> Hi,
> 
> I know of three commands to check the consistency of a Gentoo system:
> 
> 
>     eix-sync && emerge --color=n -p -v --newuse --update --deep world
>     emerge -p -v --depclean
>     revdep-rebuild --ignore -p -v
> 
> of course, one has to remove the -p and -v flags after checking the
> putput of the commands.
> 
> What else can be checked and should be checked from time to time or
> after each update?

  python-updater
  perl-cleaner 
to rebuild needed perl/python packages after an update, 
maybe
  module-rebuild
after a kernel upgrade...

personally I'd realy like if all the revdep-rebuild / python-updater /
perl-cleaner / ... were combined into a single tool  or at least named
consistently :) (perl-cleaner is the one I can never remember ;)


yoyo

Re: [gentoo-user] Consistency checking

[Mark Knecht]

On Mon, Oct 31, 2011 at 8:45 PM,  <meino.cramer@gmx.de> wrote:
> Hi,
>
> I know of three commands to check the consistency of a Gentoo system:
>
>
>    eix-sync && emerge --color=n -p -v --newuse --update --deep world
>    emerge -p -v --depclean
>    revdep-rebuild --ignore -p -v
>
> of course, one has to remove the -p and -v flags after checking the
> putput of the commands.
>
> What else can be checked and should be checked from time to time or
> after each update?
>
> Thank you very much in advance for any help!
>
> Best regards,
> mcc

eix-test-obsolete -d

to check your portage file setups. I think it's quite helpful for
'mostly stable' systems like I run. I've never seen much advantage to
the -c or -C options myself.

- Mark

Re: [gentoo-user] Consistency checking

[Urs Schutz]

On Tue, 1 Nov 2011 04:45:25 +0100
meino.cramer@gmx.de wrote:

> Hi,
> 
> I know of three commands to check the consistency of a
> Gentoo system:
> 
> 
>     eix-sync && emerge --color=n -p -v --newuse --update
> --deep world emerge -p -v --depclean
>     revdep-rebuild --ignore -p -v
> 
> of course, one has to remove the -p and -v flags after
> checking the putput of the commands.
> 
> What else can be checked and should be checked from time
> to time or after each update?
> 
> Thank you very much in advance for any help!
> 
> Best regards,
> mcc
> 

Beside the already mentioned ones:

Check and clean the portage logs, can be done with
elogv

Update the packets config files, can be done with
cfg-update -u

Clean up old source files (saves some space, but deletes
old unused sources)
eclean-dist -d -p

Check for Gentoo Linux Security Advices
glsa-check -t all

Have a look at the Gentoo management news
eselect news list
eselect news read xx

Regards
Urs

Re: [gentoo-user] Consistency checking

[meino.cramer]

Urs Schutz <u.schutz@bluewin.ch> [11-11-01 18:04]:
> On Tue, 1 Nov 2011 04:45:25 +0100
> meino.cramer@gmx.de wrote:
> 
> > Hi,
> > 
> > I know of three commands to check the consistency of a
> > Gentoo system:
> > 
> > 
> >     eix-sync && emerge --color=n -p -v --newuse --update
> > --deep world emerge -p -v --depclean
> >     revdep-rebuild --ignore -p -v
> > 
> > of course, one has to remove the -p and -v flags after
> > checking the putput of the commands.
> > 
> > What else can be checked and should be checked from time
> > to time or after each update?
> > 
> > Thank you very much in advance for any help!
> > 
> > Best regards,
> > mcc
> > 
> 
> Beside the already mentioned ones:
> 
> Check and clean the portage logs, can be done with
> elogv
> 
> Update the packets config files, can be done with
> cfg-update -u
> 
> Clean up old source files (saves some space, but deletes
> old unused sources)
> eclean-dist -d -p
> 
> Check for Gentoo Linux Security Advices
> glsa-check -t all
> 
> Have a look at the Gentoo management news
> eselect news list
> eselect news read xx
> 
> Regards
> Urs
> 
> 

Hi,

thank you all very much for the checks listed.

One question remains:
What sequence of commands is adviced to guarantee
the best effect on the one hand and on the other hand 
not to be urged to recompile things -- especially 
those like libreoffice...-- twice and more?

Thank you very much in advance for your help!
Best regards,
mcc

Re: [gentoo-user] Consistency checking

[Dale]

meino.cramer@gmx.de wrote:
> Hi, thank you all very much for the checks listed. One question 
> remains: What sequence of commands is adviced to guarantee the best 
> effect on the one hand and on the other hand not to be urged to 
> recompile things -- especially those like libreoffice...-- twice and 
> more? Thank you very much in advance for your help! Best regards, mcc 

This is what I do regularly.

eix-sync or emerge --sync

emerge -uvDNa world

emerge -a --depclean

revdep-rebuild -i -- -a

If python gets updated, add python-updater after the world update.

Usually portage will tell you if you need to run anything else.

All that said, the other advice doesn't hurt one bit.  It just depends 
on how sane you want your system.  When mine acts funny(tm), I do a 
emerge -e world.  It's amazing how that fixes those things you can't 
quite figure out.

Even tho I can compile OOo in about 45 minutes or so, I do hate to see 
it in the list.  Thing is, whenever something on here burps, OOo gets 
rebuilt.  lol  It does seem to be better here lately tho.  Shhhhhh, 
don't jinx it.

Dale

:-)  :-)

Re: [gentoo-user] Consistency checking

[Urs Schutz]

On Tue, 1 Nov 2011 19:00:04 +0100
meino.cramer@gmx.de wrote:

> Urs Schutz <u.schutz@bluewin.ch> [11-11-01 18:04]:
> > On Tue, 1 Nov 2011 04:45:25 +0100
> > meino.cramer@gmx.de wrote:
> > 
> > > Hi,
> > > 
> > > I know of three commands to check the consistency of a
> > > Gentoo system:
> > > 
> > > 
> > >     eix-sync && emerge --color=n -p -v --newuse
> > > --update --deep world emerge -p -v --depclean
> > >     revdep-rebuild --ignore -p -v
> > > 
> > > of course, one has to remove the -p and -v flags after
> > > checking the putput of the commands.
> > > 
> > > What else can be checked and should be checked from
> > > time to time or after each update?
> > > 
> > > Thank you very much in advance for any help!
> > > 
> > > Best regards,
> > > mcc
> > > 
snip...
<>
snip... 
> 
> Hi,
> 
> thank you all very much for the checks listed.
> 
> One question remains:
> What sequence of commands is adviced to guarantee
> the best effect on the one hand and on the other hand 
> not to be urged to recompile things -- especially 
> those like libreoffice...-- twice and more?
> 
> Thank you very much in advance for your help!
> Best regards,
> mcc
> 
> 


Portage is clever, and does not build libreoffice twice,
even if you change the sequence. Some binary packages are
faster to install. I'm pretty happy with the prebuilt
version of libreoffice. If you stay with stable packets
there is less rebuilding of heavy packages, as they
normally get less updates.

The sequence depends on what use you have. I would do it
differently on a server 1000 km away, but anyway here is
what I do normally on my laptop:

> eix-sync
then learn about the new packages in portage, look for what
gets updated.

Then 
> emerge -uDpvtN world
to see if there is any blockers, licenses or any other
inconsistencies which need to be resolved manually first
(running a mix of stable and unstable packages here, so
this happens from time to time).

Then portage may work in the background, while I do my
usual work on the laptop (all on one line):
> emerge -uDN world && revdep-rebuild -i && cfg-update -u &&
elogv
When the ventilator noise stops and cpu temperatures drop I
check the yellow and red elogv output lines, and if there is
something indicated by the package maintainers I do it right
away.
I simply delete the green elogv output lines.

Sometimes I do a 
> emerge --depclean -p
more because portage says that one should do it. I feel
that it is a lot of work to go through the package list
manually and do not see the immediate benefit in doing it
often. When I remove packages, I always do
> emerge -uDN world && revdep-rebuild -i && elogv
as I don't trust the state of the system after removing
packages.

> eix-test-obsolete -d
is easy if it is done often, as there is little corrective
action to do on a day to day basis.

> eclean-dist -d -p
This is really fast and painless, if you do not need old
package sources.

> glsa-check -t all
should find no problems if you have an up to date
installation.

> eselect news list
and
> eselect news read xx
is always a good thing to do and helps you to prevent the
big problems with a evolving Gentoo installation.

If there is a day without portage updates for your packages
you could do
> emerge -uDN  --complete-graph  --with-bdeps=y world
or
> rkhunter
or
> smartctl --all /dev/sda
or
> freshclam && clamscan
or build a new kernel, just to have some fun...

Sometimes I get a little jealous when I see my nephew
installing programs and updating applications in Ubuntu...

Regards
Urs

Re: [gentoo-user] Consistency checking

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 757 bytes --]

On Wed, 2 Nov 2011 10:09:13 -0200, Urs Schutz wrote:

> Sometimes I do a 
> > emerge --depclean -p  
> more because portage says that one should do it. I feel
> that it is a lot of work to go through the package list
> manually and do not see the immediate benefit in doing it
> often.

The obvious benefit is that it takes a lot less time to go through the
package list as it is generally shorter when the interval between runs is
shorter.

I have a weekly cron job that runs python-updater, revdep-rebuild,
eix-test-obsolete, emerge -c, emaint -c all, glsa-check etc, all with -p,
and mails me the output. Then I can browse the results at my leisure.


-- 
Neil Bothwick

Ultimate memory manager; Windows, it manages to use it all..

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] Consistency checking

[Leho Kraav]

On Wednesday, November 2, 2011 2:20:02 PM UTC+2, Urs Schutz wrote:
> > eix-test-obsolete -d
> is easy if it is done often, as there is little corrective
> action to do on a day to day basis.

I have been wondering if it's possible to get this particular check's output to be machine readable, so it could be used in automated scripts. Similar to what qlist -IC <atom> does.

First, I think the different checks need to be separatable with cmdline arguments, so one wouldn't have to start parsing for some header type thing to know what atom list applies to what file.

After that, the machine readable output needs to be as simple as possible, no colors, parenthesis, and whatnot.

Further thoughts welcome, and suggestions for other ways of automating this cleanup. Only thing I know of was udept, but that's been dead upstream for a while.

I should also note that I keep my /etc in git, so naturally all automated actions would be commited and therefore tracked - no need to fear losing some important configuration item, if that is at all applicable here even.

Re: [gentoo-user] Consistency checking

[Urs Schutz]

On Wed, 2 Nov 2011 06:01:28 -0700 (PDT)
Leho Kraav <leho@kraav.com> wrote:

> On Wednesday, November 2, 2011 2:20:02 PM UTC+2, Urs
> Schutz wrote:
> > > eix-test-obsolete -d
> > is easy if it is done often, as there is little
> > corrective action to do on a day to day basis.
> 
> I have been wondering if it's possible to get this
> particular check's output to be machine readable, so it
> could be used in automated scripts. Similar to what qlist
> -IC <atom> does.
> 
> First, I think the different checks need to be
> separatable with cmdline arguments, so one wouldn't have
> to start parsing for some header type thing to know what
> atom list applies to what file.
> 
> After that, the machine readable output needs to be as
> simple as possible, no colors, parenthesis, and whatnot.
> 
> Further thoughts welcome, and suggestions for other ways
> of automating this cleanup. Only thing I know of was
> udept, but that's been dead upstream for a while.
> 
> I should also note that I keep my /etc in git, so
> naturally all automated actions would be commited and
> therefore tracked - no need to fear losing some important
> configuration item, if that is at all applicable here
> even.
> 

Something like > eix -tTc --xml could be a start.