linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Curtis Lehman" <clehman@aircell.com>
To: linux-hotplug@vger.kernel.org
Subject: (no subject)
Date: Thu, 22 May 2003 19:49:31 +0000	[thread overview]
Message-ID: <marc-linux-hotplug-105363331927786@msgid-missing> (raw)

Hi,

	I have been trying to load the latest RPM modules for hotplug but I have run into a problem with the rpm manager. It won't seem to install the latest hotplug rpm packages. I think it has something to do with the fact that they have been broken out to two packages. I am running on Redhat 9.0. I have tried searching through the hotplug developers mailing list, but know one seems to have had this problem before.  I am not real strong in the RPM usage department, so I would appreciate any suggestions on how to get the package installed. I was afraid to force the removal of the old package given the dependencies. Below is an output of what I have tried.

Thanks,
Curt

[root@localhost hotplug]# uname -a
Linux localhost.localdomain 2.4.20-13.9 #1 Mon May 12 10:55:37 EDT 2003 i686 i686 i386 GNU/Linux

[root@localhost hotplug]# rpm -v -i hotplug-2003_05_01-1.noarch.rpm
warning: hotplug-2003_05_01-1.noarch.rpm: V3 DSA signature: NOKEY, key ID db2dfb29
error: Failed dependencies:
        hotplug-base >= 2003_05_01 is needed by hotplug-2003_05_01-1

[root@localhost hotplug]# rpm -v -i hotplug-base-2003_05_01-1.noarch.rpm
warning: hotplug-base-2003_05_01-1.noarch.rpm: V3 DSA signature: NOKEY, key ID db2dfb29
Preparing packages for installation...
        file /sbin/hotplug from install of hotplug-base-2003_05_01-1 conflicts with file from package hotplug-2002_04_01-17

[root@localhost hotplug]# rpm -v -q hotplug
hotplug-2002_04_01-17

[root@localhost hotplug]# rpm -v -e hotplug-2002_04_01-17
error: Failed dependencies:
        hotplug >= 2001_04_24-9 is needed by (installed) kernel-pcmcia-cs-3.1.31-13
        hotplug >= 2001_04_24-13 is needed by (installed) gphoto2-2.1.0-7




-------------------------------------------------------
This SF.net email is sponsored by: ObjectStore.
If flattening out C++ or Java code to make your application fit in a
relational database is painful, don't do it! Check out ObjectStore.
Now part of Progress Software. http://www.objectstore.net/sourceforge
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

             reply	other threads:[~2003-05-22 19:49 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-22 19:49 Curtis Lehman [this message]
2003-05-22 21:10 ` (no subject) Greg KH
2003-05-22 22:41 ` Curtis Lehman
2003-05-23  1:03 ` Johannes Erdfelt
2003-05-23 22:19 ` Greg KH
2004-02-16 15:15 ` christophe.varoqui
2004-10-09 13:36 ` Emilia Greenberg
2004-12-04 11:58 ` pablarribas
2004-12-05  2:58 ` Kay Sievers
2005-04-05 18:58 ` craig
2005-04-05 20:23 ` Patrick Mansfield
2005-05-04 17:30 ` Layne Garrett Pedersen
2005-05-04 17:40 ` Kay Sievers
2005-05-06 13:27 ` Victor Riquelme Durán
2005-05-16 22:50 ` Kay Sievers
2005-06-02 11:52 ` Rajat Jain
2005-06-05  7:21 ` shubhrangam

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=marc-linux-hotplug-105363331927786@msgid-missing \
    --to=clehman@aircell.com \
    --cc=linux-hotplug@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).