public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: William Kenworthy <billk@iinet.net.au>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] How should I clean up my broken system?
Date: Sat, 13 Feb 2010 07:46:33 +0800	[thread overview]
Message-ID: <1266018394.825.18.camel@rattus> (raw)
In-Reply-To: <20100212195529.GD1560@muc.de>

"equery check package" compares current with the as installed checksum
(or something like that!) for the packages files.

emerge -ep world > a
edit "a" to add "equery check " before each package name
run "sh a > b" and got hrough the list in b to see whats broke - lots of
debris - config files etc will show as failing a checksum, so ignore
them.  Also ".a" libraries may not be broke, but a side effect of
lafilefixer - need to check that one.  prelink apparently doesnt affect
(or maybe updates) the checksum.

I am sure someone probably has a utility able to automate the process -
anyone?

BillK

e.g.,
myth2 ~ # equery check gcc
[ Checking sys-devel/gcc-4.3.4 ]
!!! /usr/libexec/gcc/x86_64-pc-linux-gnu/4.3.4/f951 has incorrect md5sum
!!! /usr/lib/gcc/x86_64-pc-linux-gnu/4.3.4/32/libgfortran.so.3.0.0 has
incorrect md5sum
!!! /usr/lib/gcc/x86_64-pc-linux-gnu/4.3.4/libgcc.a has incorrect md5sum
!!! /usr/lib/gcc/x86_64-pc-linux-gnu/4.3.4/libmudflapth.so.0.0.0 has
incorrect md5sum
!!! /usr/share/gcc-data/x86_64-pc-linux-gnu/4.3.4/locale/tr/LC_MESSAGES/gcc.mo has incorrect md5sum
!!! /usr/lib/gcc/x86_64-pc-linux-gnu/4.3.4/32/libgfortran.a has
incorrect md5sum
!!! /etc/env.d/gcc/x86_64-pc-linux-gnu-4.3.4 has incorrect md5sum
!!! /usr/lib/gcc/x86_64-pc-linux-gnu/4.3.4/include/g
++-v4/bits/boost_concept_check.h has incorrect md5sum
!!! /usr/libexec/gcc/x86_64-pc-linux-gnu/4.3.4/tree1 has incorrect
md5sum
!!! /usr/share/gcc-data/x86_64-pc-linux-gnu/4.3.4/locale/es/LC_MESSAGES/gcc.mo has incorrect md5sum
 * 944 out of 954 files good
myth2 ~ #

Yeah my gcc is broke and wont rebuild :( 


On Fri, 2010-02-12 at 19:55 +0000, Alan Mackenzie wrote:
> Hi, Gentoo!
> 
> As reported in other threads, my new PC had a broken RAM stick in it.
> As a result, an unknown proportion of installed binaries are flaky.  One
> non-functioning binary is probably GCC.
> 
> What I'd like to do is reinstall every binary, yet without erasing any
> configuration info, whose creation was so arduous.
> 
> Where does portage keep it's list of installed packages?  What do I have
> to do to persuade portage it has _no_ installed packages before doing
> 'rm -rf *' in /bin, /sbin, /usr/bin, /usr/sbin?
> 
> Has anybody any other tips to offer me for this operation?
> 
-- 
William Kenworthy <billk@iinet.net.au>
Home in Perth!




  parent reply	other threads:[~2010-02-12 23:47 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-12 19:55 [gentoo-user] How should I clean up my broken system? Alan Mackenzie
2010-02-12 19:55 ` Volker Armin Hemmann
2010-02-12 21:21   ` Kyle Bader
2010-02-12 22:52     ` Neil Bothwick
2010-02-13  7:28       ` Alan McKinnon
2010-02-13 20:43         ` Neil Bothwick
2010-02-14  6:01           ` Alan McKinnon
2010-02-14  9:34             ` Neil Bothwick
2010-02-14 11:03               ` Volker Armin Hemmann
2010-02-14 11:32                 ` Neil Bothwick
2010-02-20 12:08                   ` Mick
2010-02-20 12:20                     ` Volker Armin Hemmann
2010-02-21  0:22                     ` Neil Bothwick
2010-02-21  3:12                     ` Iain Buchanan
2010-02-22 11:29                       ` daid kahl
2010-02-22 13:56                         ` Volker Armin Hemmann
2010-02-22 17:06                           ` [gentoo-user] " Harry Putnam
2010-02-26  7:29                             ` daid kahl
2010-02-26 18:20                   ` [gentoo-user] " Peter Humphrey
2010-02-26 18:47                     ` Alex Schuster
2010-02-27  1:02                       ` Peter Humphrey
2010-02-12 23:46 ` William Kenworthy [this message]
2010-02-13  7:27 ` Alan McKinnon
2010-02-13 17:51   ` Alan Mackenzie
2010-02-13 18:50     ` Stroller
2010-02-14  6:00     ` Alan McKinnon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1266018394.825.18.camel@rattus \
    --to=billk@iinet.net.au \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox