public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "James Homuth" <james@the-jdh.com>
To: <gentoo-user@lists.gentoo.org>
Subject: RE: [gentoo-user] fix for e2fsprogs BLOCK?
Date: Wed, 5 Nov 2008 13:13:03 -0500	[thread overview]
Message-ID: <069801c93f72$280a38f0$a500a8c0@quan> (raw)
In-Reply-To: <d9a0a6da0811051008x6eb39c37hfd2c47de984b278c@mail.gmail.com>

 

-----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.




  reply	other threads:[~2008-11-05 18:13 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-05 18:08 [gentoo-user] fix for e2fsprogs BLOCK? Denis
2008-11-05 18:13 ` James Homuth [this message]
2008-11-05 20:13   ` Alex Schuster
2008-11-05 18:16 ` Dirk Heinrichs
2008-11-05 18:52   ` Volker Armin Hemmann
2008-11-05 19:12     ` Jorge Peixoto de Morais Neto
2008-11-05 19:40       ` Volker Armin Hemmann
2008-11-05 20:33   ` Erik Hahn
2008-11-05 20:39     ` Denis
2008-11-05 20:53       ` Markos Chandras
2008-11-05 22:26         ` KH
2008-11-05 22:49           ` Alex Schuster
2008-11-06  7:15             ` KH
2008-11-06  8:04               ` Volker Armin Hemmann
2008-11-06  8:48                 ` KH
2008-11-06  9:16                   ` Volker Armin Hemmann
2008-11-06 14:51                     ` Dale
2008-11-06  6:49           ` Dirk Heinrichs
2008-11-06  7:21             ` KH
2008-11-06  7:47               ` Dirk Heinrichs
2008-11-06  8:29                 ` Volker Armin Hemmann
2008-11-06 14:53                 ` Dale
2008-11-06  7:23             ` Volker Armin Hemmann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='069801c93f72$280a38f0$a500a8c0@quan' \
    --to=james@the-jdh.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox