| Summary: | sys-fs/e2fsprogs-1.40.8/9 compile/link failure, sys-libs/com_err-1.40.8/9 error, e.g. mc/e2fsck failing, system bootup failure, TLS data error | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Werner M. Mayer <wmm> |
| Component: | [OLD] Core system | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
| Status: | RESOLVED TEST-REQUEST | ||
| Severity: | normal | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Werner M. Mayer
2008-05-27 05:30:29 UTC
Did you know that sys-fs/e2fsprogs, sys-libs/com_err and sys-libs/ss are basically different parts of one and the same package? You could try getting all three of the same version emerged. The point is to update com_err first, then ss and then e2fsprogs. And surely enough, the com_err ebuild even reminds you what you should do after you have emerged com_err: * PLEASE PLEASE take note of this * Please make *sure* to run revdep-rebuild now. * Certain things on your system may have linked against a different * version of com_err -- those things need to be recompiled. * Sorry for the inconvenience Please try that and reopen this bug only if you find the problem persists after you follow the instructions that should fix your system. Btw, looking at your emerge --info, you might also _really_ update your system by running emerge -vuaDN world. It will definitely be a tough ride, but in the end you may end up with a _current_ system. :) WOW, what a fast response. I was just about to include the error outputs
of the log files when a collision was reported.
Let me explain:
When I run updates on this slow system which can take up to two weeks of
compilation, I do this mainly at night without attending my system, so
I only see errors the next day.
Also, when updating, I do this in two steps:
First, I do an emerge -vun system and when that compiles cleanly I do an
emerge -vuanDN world in mostly convenient small parts, as I also
sometimes need this notebook inbetween to do productional tasks.
My questions:
Is there a difference between
emerge -vuanDN world
and emerge -vuaDN world
other than the extra 'n' should keep emerge from reinstalling already
installed packages?
After an unattended emerge has been done, does there exist a way of
quickly sifting through the log files to find such important notices
of the kind you mentioned about com_err telling me to run revdep-rebuild?
Or does there exist a file I don't know about that should notify me about
critical package installation messages?
If not, is there a chance of that such a file could be generated
in /var/log/portage during emerge process, i.e. like the file
emerge.log?
Do you have a script that does the job?
At what point exactly in my 'emerge --info' do you see my system
lacks updating?
It's true, I've tried to update my system many times in the past,
but errors in compiling and bugs have kept me from getting through
the update phase completely.
In the meantime, running revdep-rebuild...
I will come back as soon as revdep is through or
if I run into new problems.
WOW, fast response. While writing on an additional error log I wanted to post I got a collision notice. I will postbone the error logs until revdep-rebuild is complete and a reemerge of system update has been launched. Sorry this reply took longer to post, because compile times on P1 take longer and having multiple bug report postings open on this "bug" I noticed I had produced a lot of collision notices myself on my open and not yet sent postings. I am proceeding as requested and will report on what I find. To comment #1: When I run updates on this slow system which can take up to two weeks or longer of compilation, I do this mainly at night without attending my system, so I only see errors the next day, if at all. Also, when updating, I do this in two steps: First, I do an emerge -vun system and when that compiles cleanly I do an emerge -vuanDN world in mostly convenient small parts, as I also sometimes need this notebook inbetween to do productional tasks. My questions: Is there a difference between emerge -vuanDN world and emerge -vuaDN world other than the extra 'n',which should keep emerge from reinstalling already installed packages? After an unattended emerge has been done, does there exist a way of quickly sifting through the log files to find such important notices of the kind you mentioned about com_err telling me to run revdep-rebuild? Or does there exist a file I don't know about that should notify me about critical package installation messages? If not, is there a chance of that such a file could be generated in /var/log/portage during emerge process, i.e. like the file emerge.log? Do you have a script that does the job? To Comment #2: I would like to know where you can see my system has not successfully emerged in the last few years due to revdep-rebuild errors I could not manage to resolve (versions of installed packages?). It's true, I've tried to update my system many times in the past, but errors in compiling and bugs have kept me from getting through the update phase completely. Also I would like to know how and if unmerging one of two installed almost identical packages the older versioned number can be removed, e.g. two installed gcc's, two or more installed automake's, etc.? I am running into packages with following error I can't resolve at this time, so the question is howto emerge packages or what to do with them: =media-libs/gdk-pixbuf-0.22.0-r3 (masked by: ) media-libs/gdk-pixbuf (masked by: ) This just an example, there are many more of them... What I can't handle are packages masked by "missing keyword" and "(missing by: )". On one of my other systems (P III/500) I also have a revdep-rebuild running and emerge there fails with invalid atom... while trying to emerge packages with of this sort for all packages: =app-arch/rpm:0 =app-pda/jpilot:0 =dev-perl/DBD-mysql:0 ... Almost all versions of all packages have the same queer version number 0, some are :2, another :5. Could it be that I have a version of revdep-rebuild that has a bug, one or two are like net-analyzer/midas-nms:2.2f and kde-base/kdelibs:3.5 . How can that be? Or should I file a new bug? Meanwhile, I am trying to emerge the rest on my P III/500 and on my P I/133. I'll be back, soon. Please ignore Comment #3. It was never actually uploaded to bugzilla by me, but due to posting collision while actively editing on comment #3 on my LOCAL system it seems to have been uploaded due to collision-side merging and messing up my well structured Comment #4. Sorry for the mess in Comment #4. Viewing my postings before submitting Comment #4 as #3 showed that after Comment #2 no other comments had been posted, not even by me. After committing the well structured contents of Comment #4 as my originally planned Comment #3 and having quit links on the prior not committed Comments #3 I am somewhat astonished that even not having posted Comment #3 that the contents do show up in this bug report. Seems to be a bug in bugzilla. Is there any way of editing Comment #4? |
