linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: "Romain Cherchi" <romain.cherchi@gmail.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] lvcreate and lvremove issues
Date: Fri, 23 Jun 2006 18:15:43 +0200	[thread overview]
Message-ID: <2908808b0606230915i2153ab2ewfd6687c3e948b310@mail.gmail.com> (raw)
In-Reply-To: <20060623153122.GY19222@agk.surrey.redhat.com>

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

Thank you very much for your help and responding so quickly.

I indeed updated my system using the up2date redhat utility right after the
product activation.

Everything when right except for 2 packages:
- kernel
- kernel-smp

There was a package dependency problem.  The message was:

    To solve all dependencies for the RPMs you have selected, The following
    packages you have marked to exclude would have to be added to the set:

    Package Name                      Reason For Skipping
    ======================================================================
    kernel-2.6.9-34.0.1.EL            Pkg name/pattern
    kernel-devel-2.6.9-34.0.1.EL      Pkg name/pattern
    kernel-doc-2.6.9-34.0.1.EL        Pkg name/pattern
    kernel-hugemem-2.6.9-34.0.1.EL    Pkg name/pattern
    kernel-hugemem-devel-2.6.9-34.    Pkg name/pattern
    kernel-smp-2.6.9-34.0.1.EL        Pkg name/pattern
    kernel-smp-devel-2.6.9-34.0.1.    Pkg name/pattern
    kernel-utils-2.4-13.1.80          Pkg name/pattern

Unresolvable chain of dependencies:
kernel-2.6.9-34.0.1.EL                   conflicts with ipw2200-firmware <
2.2
kernel-smp-2.6.9-34.0.1.EL               conflicts with ipw2200-firmware <
2.2

The following packages were added to your selection to satisfy dependencies:
Package                                Required by
----------------------------------------------------------------------------

Please modify your package selections and try again.

I don't really know how to deal with this message in up2date so I just
unchecked the 2 packages and went ahead.

Right now, my kernel is still 2.6.9-34.

Do you know how to fix the problem with up2date? ... or should I download
the rpms and do the update myself ?

Regards



On 6/23/06, Alasdair G Kergon <agk@redhat.com> wrote:
>
> On Fri, Jun 23, 2006 at 05:13:34PM +0200, Romain Cherchi wrote:
> >  _deps: task run failed for (253:9)
>
> > I someone familiar with this problem?
>
> Looks like you've updated something and hit an incompatible package
> combination?
>
> Make sure your userspace device-mapper package is at least
> version 1.02.04 (with corresponding lvm2 update), or alternatively
> update your kernel to something more recent - 2.6.12 or later IIRC.
>
> Alasdair
> --
> agk@redhat.com
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@redhat.com
> https://www.redhat.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
>



-- 
Romain CHERCHI

[-- Attachment #2: Type: text/html, Size: 4731 bytes --]

      reply	other threads:[~2006-06-23 16:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-23 15:13 [linux-lvm] lvcreate and lvremove issues Romain Cherchi
2006-06-23 15:31 ` Alasdair G Kergon
2006-06-23 16:15   ` Romain Cherchi [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=2908808b0606230915i2153ab2ewfd6687c3e948b310@mail.gmail.com \
    --to=romain.cherchi@gmail.com \
    --cc=linux-lvm@redhat.com \
    /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;
as well as URLs for NNTP newsgroup(s).