From: Brian J. Murrell <Brian.Murrell@oracle.com>
To: lustre-devel@lists.lustre.org
Subject: [Lustre-devel] e2fsprogs-1.41.10.sun2-0redhat provides issues
Date: Wed, 07 Jul 2010 10:23:16 -0400 [thread overview]
Message-ID: <1278512596.6469.85.camel@pc.interlinx.bc.ca> (raw)
In-Reply-To: <4C337E74.2060306@oreilly.com>
On Tue, 2010-07-06 at 14:05 -0500, Dan Bassett wrote:
> I have e2fsprogs-1.41.10.sun2-0redhat from the lustre downloads page
> installed as part of my lustre 1.8.3 installation and it's causing some
> weird dependency issues on my OSS's. When I attempt to upgrade or
> install new packages on the system I get errors like:
This is something that most likely warrants a bug being filed in our
bugzilla.
Cheers,
b.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part
URL: <http://lists.lustre.org/pipermail/lustre-devel-lustre.org/attachments/20100707/05a0dffd/attachment.pgp>
prev parent reply other threads:[~2010-07-07 14:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-06 19:05 [Lustre-devel] e2fsprogs-1.41.10.sun2-0redhat provides issues Dan Bassett
2010-07-07 14:23 ` Brian J. Murrell [this message]
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=1278512596.6469.85.camel@pc.interlinx.bc.ca \
--to=brian.murrell@oracle.com \
--cc=lustre-devel@lists.lustre.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.