e2fsprogs update alert/warning <heads up!>

pappy_mcfae

Just a general heads-up. For ~arch users who have yet to sync your tree today ( 8-17-08 ) and update. There's a nice bomb waiting for you.

The first thing you will note is that the update comes up blocking things. In order to fix this, you need to emerge -C e2fsprogs before you install the e2fsprogs update. That will eliminate the blockage.

Unfortunately, if you are using NFS to access your distfiles, AND you're running wireless networking as well, NFS breaks, as does the wireless network...at least it did on Gen-tosh.

So, when that one comes through, it's best if you're using the wired network. If NFS becomes a problem, you may have serious problems if your portage tree is shared. If only your distfiles are shared (as in my case), you will have to temporarily remove the symlink to your nfs distfiles, and generate a /usr/portage/distfiles directory and emerge the new e2fsprogs and it's libs from fresh distfiles.

Once you reboot after the update, things will return to normal. If you do the update and it fails for the reasons above, get out your trusty install disk, chroot, and emerge e2fsprogs that way. I say this because if you reboot, things will break on a massive scale, as in no boot! It can be fixed rather easily in a chroot, but that initial shock is a real buzz kill!

As long as you take precautions, and are running wired, you should be able to get through it without too much problem. However, if it fails, you're in for some temporary hell.

Good luck.

Blessed be!
Pappy
_________________
This space left intentionally blank, except for these ASCII symbols.

yngwin · Posted: Sun Aug 17, 2008 7:21 pm Post subject:

No problems with wireless (ndiswrapper) here.
_________________
"Those who deny freedom to others deserve it not for themselves." - Abraham Lincoln
Free Culture | Defective by Design | EFF

drinian · Posted: Sun Aug 17, 2008 7:29 pm Post subject:

Am I seeing this because my Portage tree is only halfway up to date, and an rsync later today or tomorrow will fix things?

ok · Guru Joined: 11 Jul 2006 Posts: 390 Location: germany

not the only problem: https://bugs.gentoo.org/show_bug.cgi?id=234907

drinian · Posted: Mon Aug 18, 2008 12:11 am Post subject:

Good tip, and I was able to successfully move forward using this post in the bug report:

https://bugs.gentoo.org/show_bug.cgi?id=234907#c7

skellr · Posted: Mon Aug 18, 2008 12:29 am Post subject:

Edit: Things will probably break if you do this!
It's a bit safer if you don't unmerge e2fsprogs and just unmerge ss and com_err first, then update e2fsprogs. From the bug report:

pappy_mcfae · Posted: Mon Aug 18, 2008 5:57 am Post subject:

Elbar Thera · n00b Joined: 15 May 2008 Posts: 60

Well i have run into this e2fsprogs trap too, but it seems like that i did it in a much stylisher :wink:

way. I dont have any use for kerberos on my one computer system, so i thought i shall get rid of kerberos alltogether. Disabling the kerberos use flag and pruning mit-krb5 from the computer, then re-emerging all packages that rely on the flag and here we go....At least that was the plan

Unfortunatly i found a SINGLE package that relies on kerberos and that is MEDIA-VIDEO/TOTEM.... :evil:

what the hell does totem need kerberos for? (btw i might add that gnome-base/gnome-2.22.3 depends on totem )

This means that gnome cant be installed without kerberos? :?:

Funny things seems to be happening lately...
Elbar

PS: e2fsprogs-1.41.0 and comrads are from now on masked on my system....

Bloodsurfer · Posted: Mon Aug 18, 2008 9:41 am Post subject:

There was already a thread about this: https://forums.gentoo.org/viewtopic-t-704413.html

It should be pinned, many people will run into trouble with this.
_________________
SiberianSniper: my girlfriend's name ends with .c
Clete2: Uber geek! W00t! I'd rather have it end in .cpp... <insert name>.cpp
Dralnu: ...why not <name>.o? Then she's ready for linking...
SiberianSniper: or <name>.ko, so she's ready for insertion?

zsitvaij · n00b Joined: 11 Jan 2006 Posts: 74

AFAIK the recommended way to deal with blockers like this is to install the new packages before unmerging the old ones.

For portage: emerge --oneshot --nodeps sys-libs/e2fsprogs-libs sys-fs/e2fsprogs && emerge -C sys-libs/com_err sys-libs/ss

For paludis: paludis -1i sys-fs/e2fsprogs --dl-upgrade as-needed --dl-blocks discard && paludis -u --permit-unsafe-uninstalls sys-libs/com_err sys-libs/ss

This is because the system remains working throughout the upgrade, and since the new packages are now the owners of the needed files, the unmerge only gets rid of the files the old packages exclusively own.

square_ · Tux's lil' helper Joined: 20 Dec 2007 Posts: 114

im using portage-2.2-rc8

bunder · Bodhisattva Joined: 10 Apr 2004 Posts: 5934

merged one post.
_________________

kiboko · n00b Joined: 29 May 2003 Posts: 59

cst · Apprentice Joined: 24 Feb 2008 Posts: 203 Location: /proc

arnvidr · l33t Joined: 19 Aug 2004 Posts: 629 Location: Oslo, Norway

Portage should resolve the blockers automatically now, as detailed on the bug. At least it did for me, when I synced and updated about 5 hours ago.
_________________

cyrillic · Posted: Tue Aug 19, 2008 12:41 am Post subject:

Me too

I saw those 3 blockers when I did --pretend , but portage was able to resolve those blockers on its own (portage-2.2_rc8)

weisso5 · Apprentice Joined: 07 Dec 2007 Posts: 268 Location: NYC

arnvidr · l33t Joined: 19 Aug 2004 Posts: 629 Location: Oslo, Norway

Thread should have [solved] if anything, since portage now resolves this blocker automatically.
_________________

pappy_mcfae · Posted: Tue Aug 19, 2008 7:33 pm Post subject:

I am going to leave the title as is. It's meant to be a heads up...so it's a heads up. It is an issue that if improperly done can damage systems.

Blessed be!
Pappy
_________________
This space left intentionally blank, except for these ASCII symbols.

steffl · n00b Joined: 19 Aug 2008 Posts: 4

NeddySeagoon · Posted: Tue Aug 19, 2008 7:55 pm Post subject:

steffl,

Welcome to Gentoo.

touch needs /proc to be mounted. You can get into the chroot without doing that step
Outside the chroot do

steffl · n00b Joined: 19 Aug 2008 Posts: 4

OK. I totally missed that step. It seems chrooting is not my daily business... ;-)

Thanks for such a fast answer to fix my problem!

steffl · n00b Joined: 19 Aug 2008 Posts: 4

Hm. Unfortunately that was not the cause of my problem! Even after following all necessary steps for chrooting (even looking up the gentoo docs ) touch still brings that error while producing files:

NeddySeagoon · Posted: Tue Aug 19, 2008 9:00 pm Post subject:

steffl,

Cheat ... download the binpackage for your arch from tinderbox.dev.gentoo.org and put it in your gentoo root.
Untar it there just like it was a stage3, tar xpjf .... and ignore the warning about extra garbage at end ignored.

You can fix all sorts of messes this way ... missing gcc, removed glibc ....

As soon as you can, emerge the package(s) you downloaded as they are not likely to be made with your CFLAGS or your USE flags.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.

herbert12345 · n00b Joined: 04 Sep 2007 Posts: 58

Just wanted to report what happened here. Synced today but portage couldn't resolve the blockers for me. I did the emerge --oneshot --nodeps e2fsprogs-libs e2fsprogs && emerge -C ss com_err thing and emerge @preserved-rebuild failed on every package. Then I did emerge --oneshot e2fsprogs-libs e2fsprogs and currently it appears as if emerge @preserved-rebuild will finish.