| View previous topic :: View next topic |
| Author |
Message |
desultory
Bodhisattva
Joined: 04 Nov 2005
Posts: 9410
|
 Posted: Tue Aug 04, 2009 7:21 am Post subject: |
 |
|
| slack---line wrote: | | The above didn't work, it appears that portage won't downgrade glibc, and one of the other packages pulled in by 'emerge -uDNa1 glibc' broke things at some point. |
It is actually the ebuild which aborts when a downgrade is recognized. If you really want to downgrade glibc and are willing and able to handle any subsequent problems, copy the sys-libs/glibc directory and its contents from the tree into an overlay (technically not all of it is required, but it is easier to do than picking out just what is really necessary), then comment out the has_version check at the beginning of pkg_setup, along with the block of code controlled by it, generate a new manifest and install the package from that overlay. It is likely to break things, but it can be done. |
|
| Back to top |
|
 |
slackline
Veteran
Joined: 01 Apr 2005
Posts: 1471
Location: /uk/sheffield
|
| Posted: Tue Aug 04, 2009 8:38 am Post subject: |
|
|
| desultory wrote: | | slack---line wrote: | | The above didn't work, it appears that portage won't downgrade glibc, and one of the other packages pulled in by 'emerge -uDNa1 glibc' broke things at some point. |
It is actually the ebuild which aborts when a downgrade is recognized. If you really want to downgrade glibc and are willing and able to handle any subsequent problems, copy the sys-libs/glibc directory and its contents from the tree into an overlay (technically not all of it is required, but it is easier to do than picking out just what is really necessary), then comment out the has_version check at the beginning of pkg_setup, along with the block of code controlled by it, generate a new manifest and install the package from that overlay. It is likely to break things, but it can be done. |
Ahh, thats handy to know and something I was unaware of, lots to portage that I'm still ignorant of, but I'm still keeping my eyes out for tidbits like this), cheers.
I'll see how things pan out now I've removed glibc-2.9 and am emerge-ing an empty 'system' (and then 'world').
Cheers desoultory,
slack
_________________
"Science is what we understand well enough to explain to a computer. Art is everything else we do." - Donald Knuth |
|
| Back to top |
|
|
slackline
Veteran
Joined: 01 Apr 2005
Posts: 1471
Location: /uk/sheffield
|
| Posted: Wed Aug 05, 2009 6:45 am Post subject: |
|
|
Grrr, had a powercut last night which means I had to start again (its also messed up one of my external HDs but thats a separate issue).
_________________
"Science is what we understand well enough to explain to a computer. Art is everything else we do." - Donald Knuth |
|
| Back to top |
|
|
slackline
Veteran
Joined: 01 Apr 2005
Posts: 1471
Location: /uk/sheffield
|
| Posted: Thu Aug 13, 2009 10:14 am Post subject: |
|
|
Updating this for others who may suffer from this problem.
emerge -e system almost worked fine, there were three packages (bash and two others, can't remember at the moment and am at work) that hung on configuring whilst looking for the location of Emacs .elc files. I simply broke out then 'emerge --resume --skipfirst' and got through all of that.
Rebooting resulted in the following errors...
| Code: |
udevd[1597]: lookup_group: specified group 'plugdev' unknown
*Mounting devpts at /dev/pts ...
* Checking root filesystem ...
fsck.ext3: No such file or directory while trying to open /dev/ROOT
/dev/ROOT:
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it reall contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsckwith an alternatesuperblock:
e2fsck -b 8193 <device>
* Filesystem couldn't be fixed :(
Give root password for maintenance
(or type Control-D to continue):
|
So I rebooted the livecd and chrooted and 'emerge -av sys-apps/pmount' to resolve the first problem of 'pugdev' group being unknown, I also copied back my old /etc/fstab to resolve the second (Ooops  ).
System now boots fine, although wireless doesn't want to play quite yet, but its now sat there running 'emerge -e world' to get everything back up to scratch (fortunately all the packages were still residing in /urs/portage/distfiles/ so not having a network connection isn't an issue  ).
_________________
"Science is what we understand well enough to explain to a computer. Art is everything else we do." - Donald Knuth |
|
| Back to top |
|
|
slackline
Veteran
Joined: 01 Apr 2005
Posts: 1471
Location: /uk/sheffield
|
| Posted: Sat Aug 15, 2009 9:59 am Post subject: |
|
|
Finally got things back to normal. emerge -e world hung a few times whilst looking for the location of .elc files, but skipped that. Had to explicitly re-emerge gdm and use regenworld to recover /var/lib/portage/world which got wiped, but everything is working as it was before.
Next task, get a new kernel working and the bluetooth keyboard and mouse.
Lesson learnt == pay attention to upgrades and be careful with glibc!
_________________
"Science is what we understand well enough to explain to a computer. Art is everything else we do." - Donald Knuth |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Portage & Programming
