| 1 |
"equery check package" compares current with the as installed checksum |
| 2 |
(or something like that!) for the packages files. |
| 3 |
|
| 4 |
emerge -ep world > a |
| 5 |
edit "a" to add "equery check " before each package name |
| 6 |
run "sh a > b" and got hrough the list in b to see whats broke - lots of |
| 7 |
debris - config files etc will show as failing a checksum, so ignore |
| 8 |
them. Also ".a" libraries may not be broke, but a side effect of |
| 9 |
lafilefixer - need to check that one. prelink apparently doesnt affect |
| 10 |
(or maybe updates) the checksum. |
| 11 |
|
| 12 |
I am sure someone probably has a utility able to automate the process - |
| 13 |
anyone? |
| 14 |
|
| 15 |
BillK |
| 16 |
|
| 17 |
e.g., |
| 18 |
myth2 ~ # equery check gcc |
| 19 |
[ Checking sys-devel/gcc-4.3.4 ] |
| 20 |
!!! /usr/libexec/gcc/x86_64-pc-linux-gnu/4.3.4/f951 has incorrect md5sum |
| 21 |
!!! /usr/lib/gcc/x86_64-pc-linux-gnu/4.3.4/32/libgfortran.so.3.0.0 has |
| 22 |
incorrect md5sum |
| 23 |
!!! /usr/lib/gcc/x86_64-pc-linux-gnu/4.3.4/libgcc.a has incorrect md5sum |
| 24 |
!!! /usr/lib/gcc/x86_64-pc-linux-gnu/4.3.4/libmudflapth.so.0.0.0 has |
| 25 |
incorrect md5sum |
| 26 |
!!! /usr/share/gcc-data/x86_64-pc-linux-gnu/4.3.4/locale/tr/LC_MESSAGES/gcc.mo has incorrect md5sum |
| 27 |
!!! /usr/lib/gcc/x86_64-pc-linux-gnu/4.3.4/32/libgfortran.a has |
| 28 |
incorrect md5sum |
| 29 |
!!! /etc/env.d/gcc/x86_64-pc-linux-gnu-4.3.4 has incorrect md5sum |
| 30 |
!!! /usr/lib/gcc/x86_64-pc-linux-gnu/4.3.4/include/g |
| 31 |
++-v4/bits/boost_concept_check.h has incorrect md5sum |
| 32 |
!!! /usr/libexec/gcc/x86_64-pc-linux-gnu/4.3.4/tree1 has incorrect |
| 33 |
md5sum |
| 34 |
!!! /usr/share/gcc-data/x86_64-pc-linux-gnu/4.3.4/locale/es/LC_MESSAGES/gcc.mo has incorrect md5sum |
| 35 |
* 944 out of 954 files good |
| 36 |
myth2 ~ # |
| 37 |
|
| 38 |
Yeah my gcc is broke and wont rebuild :( |
| 39 |
|
| 40 |
|
| 41 |
On Fri, 2010-02-12 at 19:55 +0000, Alan Mackenzie wrote: |
| 42 |
> Hi, Gentoo! |
| 43 |
> |
| 44 |
> As reported in other threads, my new PC had a broken RAM stick in it. |
| 45 |
> As a result, an unknown proportion of installed binaries are flaky. One |
| 46 |
> non-functioning binary is probably GCC. |
| 47 |
> |
| 48 |
> What I'd like to do is reinstall every binary, yet without erasing any |
| 49 |
> configuration info, whose creation was so arduous. |
| 50 |
> |
| 51 |
> Where does portage keep it's list of installed packages? What do I have |
| 52 |
> to do to persuade portage it has _no_ installed packages before doing |
| 53 |
> 'rm -rf *' in /bin, /sbin, /usr/bin, /usr/sbin? |
| 54 |
> |
| 55 |
> Has anybody any other tips to offer me for this operation? |
| 56 |
> |
| 57 |
-- |
| 58 |
William Kenworthy <billk@×××××××××.au> |
| 59 |
Home in Perth! |
Archives