From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: (no subject)
Date: Fri, 23 May 2003 22:19:34 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-105372903623063@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-105363331927786@msgid-missing>
On Thu, May 22, 2003 at 09:03:10PM -0400, Johannes Erdfelt wrote:
> On Thu, May 22, 2003, Greg KH <greg@kroah.com> wrote:
> > On Thu, May 22, 2003 at 01:49:31PM -0600, Curtis Lehman wrote:
> > > 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.
> >
> > Try loading both of them at the same time:
> > rpm -Uhv hotplug-2003_05_01-1.noarch.rpm hotplug-base-2003_05_01-1.noarch.rpm
> >
> > It does seem that -2003_05_01-1 is detected as an "older" package. I
> > thought I would not have this problem with the way I named the versions,
> > but I guess not. Anyone have any ideas about that?
>
> It doesn't look like that to me. It just looks like a dependancy problem
> where you need to specify both packages on the same command line like
> you suggested.
>
> None of the error messages suggest that rpm thinks the 2003_05_01
> package is older.
No, that's not shown in these messages, I saw it when I installed the
packages on one of my boxes. Hm, the rpm version of apt keeps wanting
to install the old version of hotplug too, I'll look into this...
thanks,
greg k-h
-------------------------------------------------------
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
next prev parent reply other threads:[~2003-05-23 22:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-22 19:49 (no subject) Curtis Lehman
2003-05-22 21:10 ` Greg KH
2003-05-22 22:41 ` Curtis Lehman
2003-05-23 1:03 ` Johannes Erdfelt
2003-05-23 22:19 ` Greg KH [this message]
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-105372903623063@msgid-missing \
--to=greg@kroah.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).