[gentoo-user] fix for e2fsprogs BLOCK?

[gentoo-user] fix for e2fsprogs BLOCK?

[Denis]

This probably was already discussed at length...  But I keep waiting
for an automatic portage tree fix to this...  Any idea if there will
be a fix, or will I need to take care of this manually?  (Intel Core
Duo 32-bit system, FYI).

RE: [gentoo-user] fix for e2fsprogs BLOCK?

[James Homuth]

 

-----Original Message-----
From: Denis [mailto:denis.che@gmail.com] 
Sent: November 5, 2008 1:08 PM
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] fix for e2fsprogs BLOCK?

This probably was already discussed at length...  But I keep waiting for an
automatic portage tree fix to this...  Any idea if there will be a fix, or
will I need to take care of this manually?  (Intel Core Duo 32-bit system,
FYI).

Apparently a later version of Portage will correct it, but if you're running
2.1.4.5 you're probably fixing it manually. That's been my experience
anyway.

Re: [gentoo-user] fix for e2fsprogs BLOCK?

[Dirk Heinrichs]

Am Mittwoch, 5. November 2008 19:08:23 schrieb Denis:
> This probably was already discussed at length...  But I keep waiting
> for an automatic portage tree fix to this...  Any idea if there will
> be a fix, or will I need to take care of this manually?  (Intel Core
> Duo 32-bit system, FYI).

emerge -f e2fsprogs e2fsprogs-libs # wget won't work w/o com_err , so you need 
to fetch first.
emerge -C com_err ss
emerge e2fsprogs

or, simpler with paludis:

paludis -i --dl-blocks discard e2fsprogs

If the block still exists after you unmerged com_err and ss, use emerge with -
t to find out which package still wants them end re-emerge this first.

HTH...

	Dirk

Re: [gentoo-user] fix for e2fsprogs BLOCK?

[Volker Armin Hemmann]

On Mittwoch 05 November 2008, Dirk Heinrichs wrote:
> Am Mittwoch, 5. November 2008 19:08:23 schrieb Denis:
> > This probably was already discussed at length...  But I keep waiting
> > for an automatic portage tree fix to this...  Any idea if there will
> > be a fix, or will I need to take care of this manually?  (Intel Core
> > Duo 32-bit system, FYI).
>
> emerge -f e2fsprogs e2fsprogs-libs # wget won't work w/o com_err , so you
> need to fetch first.
> emerge -C com_err ss
> emerge e2fsprogs
>
> or, simpler with paludis:
>
> paludis -i --dl-blocks discard e2fsprogs
>
> If the block still exists after you unmerged com_err and ss, use emerge
> with - t to find out which package still wants them end re-emerge this
> first.
>
> HTH...
>
> 	Dirk

and mask com_err and ss afterwards - to make sure that nothing pulls them in.

Re: [gentoo-user] fix for e2fsprogs BLOCK?

[Jorge Peixoto de Morais Neto]

On Wed, Nov 5, 2008 at 6:52 PM, Volker Armin Hemmann
<volker.armin.hemmann@tu-clausthal.de> wrote:
> On Mittwoch 05 November 2008, Dirk Heinrichs wrote:
>> Am Mittwoch, 5. November 2008 19:08:23 schrieb Denis:
>> > This probably was already discussed at length...  But I keep waiting
>> > for an automatic portage tree fix to this...  Any idea if there will
>> > be a fix, or will I need to take care of this manually?  (Intel Core
>> > Duo 32-bit system, FYI).
>>
>> emerge -f e2fsprogs e2fsprogs-libs # wget won't work w/o com_err , so you
>> need to fetch first.
>> emerge -C com_err ss
>> emerge e2fsprogs
>>
>> or, simpler with paludis:
>>
>> paludis -i --dl-blocks discard e2fsprogs
>>
>> If the block still exists after you unmerged com_err and ss, use emerge
>> with - t to find out which package still wants them end re-emerge this
>> first.
>>
>> HTH...
>>
>>       Dirk
>
> and mask com_err and ss afterwards - to make sure that nothing pulls them in.
Seems completely unnecessary.

Re: [gentoo-user] fix for e2fsprogs BLOCK?

[Volker Armin Hemmann]

On Mittwoch 05 November 2008, Jorge Peixoto de Morais Neto wrote:
> On Wed, Nov 5, 2008 at 6:52 PM, Volker Armin Hemmann
>
> <volker.armin.hemmann@tu-clausthal.de> wrote:
> > On Mittwoch 05 November 2008, Dirk Heinrichs wrote:
> >> Am Mittwoch, 5. November 2008 19:08:23 schrieb Denis:
> >> > This probably was already discussed at length...  But I keep waiting
> >> > for an automatic portage tree fix to this...  Any idea if there will
> >> > be a fix, or will I need to take care of this manually?  (Intel Core
> >> > Duo 32-bit system, FYI).
> >>
> >> emerge -f e2fsprogs e2fsprogs-libs # wget won't work w/o com_err , so
> >> you need to fetch first.
> >> emerge -C com_err ss
> >> emerge e2fsprogs
> >>
> >> or, simpler with paludis:
> >>
> >> paludis -i --dl-blocks discard e2fsprogs
> >>
> >> If the block still exists after you unmerged com_err and ss, use emerge
> >> with - t to find out which package still wants them end re-emerge this
> >> first.
> >>
> >> HTH...
> >>
> >>       Dirk
> >
> > and mask com_err and ss afterwards - to make sure that nothing pulls them
> > in.
>
> Seems completely unnecessary.

seems - but was part of the bug back in the days I did the switch. unmerge and 
mask them, was the instruction.

Re: [gentoo-user] fix for e2fsprogs BLOCK?

[Alex Schuster]

James Homuth writes:

> Apparently a later version of Portage will correct it, but if you're
> running 2.1.4.5 you're probably fixing it manually. That's been my
> experience anyway.

On the PC I am writing this, portage 2.2 had no trouble with this update. 
But on another, which was upgraded to portage 2.2 just before the world 
update, I got the blockers and had to solve this manually. No idea why.

	Wonko

Re: [gentoo-user] fix for e2fsprogs BLOCK?

[Erik Hahn]

On Wed, Nov 05, 2008 at 07:16:02PM +0100, Dirk Heinrichs wrote:
> or, simpler with paludis:
> 
> paludis -i --dl-blocks discard e2fsprogs
> 
> If the block still exists after you unmerged com_err and ss, use emerge with -
> t to find out which package still wants them end re-emerge this first.

It might be a good idea to remove the entries in the package database
afterwards.

	-Erik

-- 
v4sw5RUYhw2ln3pr5ck0ma2u7Lw3+2Xm0l6/7Gi2e2t3b6AKMen5+7a16s0Sr1p-5.62/-6.56g6OR

Re: [gentoo-user] fix for e2fsprogs BLOCK?

[Denis]

I did this

emerge -f e2fsprogs e2fsprogs-libs
emerge -C com_err ss

but it still complained about blocks when I tried "emerge e2fsprogs"

So I had to do

emerge -C e2fsprogs
emerge e2fsprogs

This seems to work fine - no more blocks.

Thank you,
Denis

Re: [gentoo-user] fix for e2fsprogs BLOCK?

[Markos Chandras]

On Wednesday 05 November 2008 22:39:52 Denis wrote:
> I did this
>
> emerge -f e2fsprogs e2fsprogs-libs
> emerge -C com_err ss
>
> but it still complained about blocks when I tried "emerge e2fsprogs"
>
> So I had to do
>
> emerge -C e2fsprogs
> emerge e2fsprogs
>
> This seems to work fine - no more blocks.
>
> Thank you,
> Denis

Yep. Thats the solution ;)

-- 
Markos Chandras

Re: [gentoo-user] fix for e2fsprogs BLOCK?

[KH]

Markos Chandras schrieb:
> On Wednesday 05 November 2008 22:39:52 Denis wrote:
>   
>> I did this
>>
>> emerge -f e2fsprogs e2fsprogs-libs
>> emerge -C com_err ss
>>
>> but it still complained about blocks when I tried "emerge e2fsprogs"
>>
>> So I had to do
>>
>> emerge -C e2fsprogs
>> emerge e2fsprogs
>>
>> This seems to work fine - no more blocks.
>>
>> Thank you,
>> Denis
>>     
>
> Yep. Thats the solution ;)
>
>   
To be on the save side of gentoo :-)

quickpkg ss com_err e2fsprogs e2fsprogs-libs

imho quickpkg is a good idea whenever changing something which ist part
of system.

kh

Re: [gentoo-user] fix for e2fsprogs BLOCK?

[Alex Schuster]

KH writes:

> To be on the save side of gentoo :-)
>
> quickpkg ss com_err e2fsprogs e2fsprogs-libs

Yeah, that saved me some trouble.

> imho quickpkg is a good idea whenever changing something which ist part
> of system.

Or you can put buildyspkg into your FEATURES list in make.conf. Then, 
whenever a system package is merged, a binary package will be created.

	Wonko

Re: [gentoo-user] fix for e2fsprogs BLOCK?

[Dirk Heinrichs]

[-- Attachment #1: Type: text/plain, Size: 506 bytes --]

Am Mittwoch 05 November 2008 23:26:57 schrieb ext KH:

> quickpkg ss com_err

That doesn't make sense at all. They're the ones you need to get rid of.

Bye...

	Dirk
-- 
Dirk Heinrichs          | Tel:  +49 (0)162 234 3408
Configuration Manager   | Fax:  +49 (0)211 47068 111
Capgemini Deutschland   | Mail: dirk.heinrichs@capgemini.com
Wanheimerstraße 68      | Web:  http://www.capgemini.com
D-40468 Düsseldorf      | ICQ#: 110037733
GPG Public Key C2E467BB | Keyserver: wwwkeys.pgp.net


[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] fix for e2fsprogs BLOCK?

[KH]

Alex Schuster schrieb:
> KH writes:
>
>   
>> To be on the save side of gentoo :-)
>>
>> quickpkg ss com_err e2fsprogs e2fsprogs-libs
>>     
>
> Yeah, that saved me some trouble.
>
>   
>> imho quickpkg is a good idea whenever changing something which ist part
>> of system.
>>     
>
> Or you can put buildyspkg into your FEATURES list in make.conf. Then, 
> whenever a system package is merged, a binary package will be created.
>
> 	Wonko
>
>   
Wow did not know that. Great option! Does this only do packages for
system or also for the hole world?

kh

Re: [gentoo-user] fix for e2fsprogs BLOCK?

[KH]

Dirk Heinrichs schrieb:
> Am Mittwoch 05 November 2008 23:26:57 schrieb ext KH:
>
>   
>> quickpkg ss com_err
>>     
>
> That doesn't make sense at all. They're the ones you need to get rid of.
>
> Bye...
>
> 	Dirk
>   
Well that's the point. You want to get rid of them. So you are unmerging
them. The moment something fails after unmerging and before emerging the
new packages, you will be very happy to have your old packages. You just
put them pack in place and you have a running system again. It's a
seatbelt.

kh

Re: [gentoo-user] fix for e2fsprogs BLOCK?

[Volker Armin Hemmann]

On Donnerstag 06 November 2008, Dirk Heinrichs wrote:
> Am Mittwoch 05 November 2008 23:26:57 schrieb ext KH:
> > quickpkg ss com_err
>
> That doesn't make sense at all. They're the ones you need to get rid of.
>
> Bye...
>
> 	Dirk

it is good to have backups - just in case.

Re: [gentoo-user] fix for e2fsprogs BLOCK?

[Dirk Heinrichs]

[-- Attachment #1: Type: text/plain, Size: 1099 bytes --]

Am Donnerstag 06 November 2008 08:21:26 schrieb ext KH:

> Well that's the point. You want to get rid of them. So you are unmerging
> them. The moment something fails after unmerging and before emerging the
> new packages, you will be very happy to have your old packages. You just
> put them pack in place and you have a running system again. It's a
> seatbelt.

That's why

1) I use paludis, no seatbelts required. One can safely de-install com_err and 
ss _after_ upgrading e2fsprogs and e2fsprogs-libs.

2) I outlined to first emerge -f e2fsprogs e2fsprogs. It's known that wget 
will fail after unmerging com_err, so the new packages need to be fetched 
first. That's all. No need to make the thing more complicated than it is.

Bye...

	Dirk
-- 
Dirk Heinrichs          | Tel:  +49 (0)162 234 3408
Configuration Manager   | Fax:  +49 (0)211 47068 111
Capgemini Deutschland   | Mail: dirk.heinrichs@capgemini.com
Wanheimerstraße 68      | Web:  http://www.capgemini.com
D-40468 Düsseldorf      | ICQ#: 110037733
GPG Public Key C2E467BB | Keyserver: wwwkeys.pgp.net


[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] fix for e2fsprogs BLOCK?

[Volker Armin Hemmann]

On Donnerstag 06 November 2008, KH wrote:
> Alex Schuster schrieb:
> > KH writes:
> >> To be on the save side of gentoo :-)
> >>
> >> quickpkg ss com_err e2fsprogs e2fsprogs-libs
> >
> > Yeah, that saved me some trouble.
> >
> >> imho quickpkg is a good idea whenever changing something which ist part
> >> of system.
> >
> > Or you can put buildyspkg into your FEATURES list in make.conf. Then,
> > whenever a system package is merged, a binary package will be created.
> >
> > 	Wonko
>
> Wow did not know that. Great option! Does this only do packages for
> system or also for the hole world?
>
> kh

to get packages built for whole world, add 'buildpkg' to make.conf FEATURES.

Re: [gentoo-user] fix for e2fsprogs BLOCK?

[Volker Armin Hemmann]

On Donnerstag 06 November 2008, Dirk Heinrichs wrote:
> Am Donnerstag 06 November 2008 08:21:26 schrieb ext KH:
> > Well that's the point. You want to get rid of them. So you are unmerging
> > them. The moment something fails after unmerging and before emerging the
> > new packages, you will be very happy to have your old packages. You just
> > put them pack in place and you have a running system again. It's a
> > seatbelt.
>
> That's why
>
> 1) I use paludis, no seatbelts required. One can safely de-install com_err
> and ss _after_ upgrading e2fsprogs and e2fsprogs-libs.
>
> 2) I outlined to first emerge -f e2fsprogs e2fsprogs. It's known that wget
> will fail after unmerging com_err, so the new packages need to be fetched
> first. That's all. No need to make the thing more complicated than it is.

and both have nothing to do with the fact, that it is wise to have a backup of 
essintial files in case something goes horribly wrong.

oh, and latest portage can 'break' blocks too....

Re: [gentoo-user] fix for e2fsprogs BLOCK?

[KH]

Volker Armin Hemmann schrieb:
> On Donnerstag 06 November 2008, KH wrote:
>   
>> Alex Schuster schrieb:
>>     
>>>       
>>> Or you can put buildyspkg into your FEATURES list in make.conf. Then,
>>> whenever a system package is merged, a binary package will be created.
>>>
>>> 	Wonko
>>>       
>> Wow did not know that. Great option! Does this only do packages for
>> system or also for the hole world?
>>
>> kh
>>     
>
> to get packages built for whole world, add 'buildpkg' to make.conf FEATURES.
>
>   
Hi,
just tried it. There was a misspelling:

from http://linuxreviews.org/man/make.conf/
cool page, just found it (never searched it before)

*buildpkg*
    Binary packages will be created for all packages that are merged.
    Also see *quickpkg <http://linuxreviews.org/man/quickpkg>*(1) and
    *emerge <http://linuxreviews.org/man/emerge>*(1) *--buildpkg* and
    *--buildpkgonly* options. 
*buildsyspkg*
    Build binary packages for just packages in the system set. 

kh

Re: [gentoo-user] fix for e2fsprogs BLOCK?

[Volker Armin Hemmann]

On Donnerstag 06 November 2008, KH wrote:
> Volker Armin Hemmann schrieb:
> > On Donnerstag 06 November 2008, KH wrote:
> >> Alex Schuster schrieb:
> >>> Or you can put buildyspkg into your FEATURES list in make.conf. Then,
> >>> whenever a system package is merged, a binary package will be created.
> >>>
> >>> 	Wonko
> >>
> >> Wow did not know that. Great option! Does this only do packages for
> >> system or also for the hole world?
> >>
> >> kh
> >
> > to get packages built for whole world, add 'buildpkg' to make.conf
> > FEATURES.
>
> Hi,
> just tried it. There was a misspelling:
>
> from http://linuxreviews.org/man/make.conf/
> cool page, just found it (never searched it before)
>
> *buildpkg*
>     Binary packages will be created for all packages that are merged.
>     Also see *quickpkg <http://linuxreviews.org/man/quickpkg>*(1) and
>     *emerge <http://linuxreviews.org/man/emerge>*(1) *--buildpkg* and
>     *--buildpkgonly* options.
> *buildsyspkg*
>     Build binary packages for just packages in the system set.
>
> kh

man make.conf in a shell of your choice would have told you the same.

Re: [gentoo-user] fix for e2fsprogs BLOCK?

[Dale]

Volker Armin Hemmann wrote:
> On Donnerstag 06 November 2008, KH wrote:
>   
>> Volker Armin Hemmann schrieb:
>>     
>>> On Donnerstag 06 November 2008, KH wrote:
>>>       
>>>> Alex Schuster schrieb:
>>>>         
>>>>> Or you can put buildyspkg into your FEATURES list in make.conf. Then,
>>>>> whenever a system package is merged, a binary package will be created.
>>>>>
>>>>> 	Wonko
>>>>>           
>>>> Wow did not know that. Great option! Does this only do packages for
>>>> system or also for the hole world?
>>>>
>>>> kh
>>>>         
>>> to get packages built for whole world, add 'buildpkg' to make.conf
>>> FEATURES.
>>>       
>> Hi,
>> just tried it. There was a misspelling:
>>
>> from http://linuxreviews.org/man/make.conf/
>> cool page, just found it (never searched it before)
>>
>> *buildpkg*
>>     Binary packages will be created for all packages that are merged.
>>     Also see *quickpkg <http://linuxreviews.org/man/quickpkg>*(1) and
>>     *emerge <http://linuxreviews.org/man/emerge>*(1) *--buildpkg* and
>>     *--buildpkgonly* options.
>> *buildsyspkg*
>>     Build binary packages for just packages in the system set.
>>
>> kh
>>     
>
> man make.conf in a shell of your choice would have told you the same.
>
>
>
>   

And if you use Konqueror in KDE, man:make.conf would work as well.  Just
one more option to have.

Yes, it was misspelled in the original post.  It should be buildsyspkg. 
There is a "s" missing.

Dale

:-)  :-) 

Re: [gentoo-user] fix for e2fsprogs BLOCK?

[Dale]

Dirk Heinrichs wrote:
> Am Donnerstag 06 November 2008 08:21:26 schrieb ext KH:
>
>   
>> Well that's the point. You want to get rid of them. So you are unmerging
>> them. The moment something fails after unmerging and before emerging the
>> new packages, you will be very happy to have your old packages. You just
>> put them pack in place and you have a running system again. It's a
>> seatbelt.
>>     
>
> That's why
>
> 1) I use paludis, no seatbelts required. One can safely de-install com_err and 
> ss _after_ upgrading e2fsprogs and e2fsprogs-libs.
>
> 2) I outlined to first emerge -f e2fsprogs e2fsprogs. It's known that wget 
> will fail after unmerging com_err, so the new packages need to be fetched 
> first. That's all. No need to make the thing more complicated than it is.
>
> Bye...
>
> 	Dirk
>   

But not everyone uses paludis.  So those that don't do it this way.  I
agree it is the safest way.

Dale

:-)  :-)