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.
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
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
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
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
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.
-Original Message-
From: Denis [mailto:[EMAIL PROTECTED]
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...
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
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
On Wed, Nov 5, 2008 at 6:52 PM, Volker Armin Hemmann
[EMAIL PROTECTED] 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
On Mittwoch 05 November 2008, Jorge Peixoto de Morais Neto wrote:
On Wed, Nov 5, 2008 at 6:52 PM, Volker Armin Hemmann
[EMAIL PROTECTED] 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
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
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
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
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.
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
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
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
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
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
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.
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
22 matches
Mail list logo
