|
[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]
|
Re: [PLUG] What am I missing about RPM?
|
ok, here is what my friend says about the problem
-brad
-----Original Message-----
From: Michael Chapman [mailto:mchapman@beren.hn.org]
Sent: Tuesday, 16 April 2002 9:31 PM
To: Bradley Molnar
Subject: RE: RPM problem
[...]
> # ssh -V
> OpenSSH_2.9p2, SSH protocols 1.5/2.0, OpenSSL 0x0090602f
>
> Whoops, that's no good. Hey, I thought they said this machine was
> updated...
>
> # rpm -qa | grep openssh
> openssh-askpass-gnome-2.9p2-12
> openssh-clients-2.9p2-12
> openssh-2.9p2-12
> openssh-server-2.9p2-12
> openssh-askpass-2.9p2-12
>
> Curious. Well, how 'bout we find upgrades for those:
>
> # rpmfind --upgrade openssh
> Resource openssh : no need to upgrade
>
> Hrm. Weird. You sure?
>
> # rpmfind -v -v --upgrade openssh
> Host : foo.bar.dom, Country: 840, Zones 0 0 0, Continent 1
> Arch : i386, Os : Linux
> Default distribution : Red Hat, Inc.(Red Hat Linux)
> owning 1099 of 1105 installed packages
> findResource openssh
> Resource openssh is provided by: openssh-2.9p2-7
> lookupRemoteResource openssh
> Get http://speakeasy.rpmfind.net//resources/openssh.rdf
> Fetching : http://speakeasy.rpmfind.net//resources/openssh.rdf to
/root/.rp=
> mfinddir/fetch9383
> HTTPRequest returned : -1
> Failed !
> Get rpmfind.net/resources/openssh.rdf
> Fetching : rpmfind.net/resources/openssh.rdf to /root/.rpmfinddir/fetch886
> Failed !
> Error fetching openssh metadata
> Resource openssh : no need to upgrade
>
> Oh, I see you're just hiding error messages from me. That's just
> swell. But what does this mean? That I need to upgrade rpmfind? As
> near as I can tell from rpmfind's web interface, rpmfind-1.7-2 is
> the current version. So which version am I running? Well, there's
> some dispute about that:
>
> # rpm -q rpmfind
> rpmfind-1.7-2
> # rpmfind --version
> rpmfind: unknown option --version
> rpmfind 1.6 : RPM packages search engine
> [...]
>
> Huh?
I don't use rpmfind (I subscribe to bugtraq and find out when Red Hat
update a package that way), so I'm not too sure how to configure/use it.
However, trying to get
http://speakeasy.rpmfind.net//resources/openssh.rdf
just gives me a 404 Not Found. Perhaps it's moved location (and you'll
need to edit the appropriate Red Hat conf file for that). At any rate,
rpmfind isn't going to be much use until it can get the latest rdf file.
> In any case, I can grab the openssh packages one by one, rpm -e the
> old packages, then rpm -i the new ones, only but that doesn't
> actually work:
>
> # rpm -i
ftp://speakeasy.rpmfind.net/linux/redhat/updates/7.2/en/os/i386/op=
> enssh-server-3.1p1-2.i386.rpm
> error: unpacking of archive failed on file
> /usr/libexec/openssh/sftp-server;3cbc105e: cpio: read
There was an error in the download. FYI, the correct md5sums for those
files are:
f8c46c51f3bd74a8437a7fb1f0b15502 openssh-3.1p1-2.i386.rpm
ef80fbb8b75ed3ff627c2fe060fc5165 openssh-askpass-3.1p1-2.i386.rpm
7b2a01eff4dcf0601ff4b54becb949d6 openssh-askpass-gnome-3.1p1-2.i386.rpm
1d2528e9f4af919f730423b7bb7a815d openssh-clients-3.1p1-2.i386.rpm
7b65f56a9044dad10f02f444774a9b32 openssh-server-3.1p1-2.i386.rpm
And instead of -e then -i, you should use -U (upgrade) or -F (freshen)
instead.
> [root@mta1 root]# which sshd
> /usr/bin/which: no sshd in
(/usr/kerberos/sbin:/usr/kerberos/bin:/bin:/sbin=
>
:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin:/usr/bin/X11:/usr/X11R6/=
> bin:/root/bin)
>
> ARGH!
>
> What the hell am I supposed to do now? (Or, what the hell should I
> have done before?)
>
> I'm throwing up my hands and just installing OpenSSH in the sane way
> I know will work (from source), but I don't want to be scurrying
> around upgrading every one of our Linux machines every two weeks
> when OpenBSD realizes they've reintroduced another bug from the
> '80s...
heh :-)
> --
> gabriel rosenkoetter
> gr@eclipsed.net
>
>
> On Mon, Apr 15, 2002 at 06:57:46PM -0400, gabriel rosenkoetter wrote:
> > I was handed a machine on which I was assured that RedHat's up2date
> > had already been run (I cannot re-run up2date, as I don't have
> > access to the account with RH which is used to update it; long
> > story... in the long run, this machine will use up2date, but it's
> > not right now).
>
> Incidentally, I have no way to verify this (since rpmfind is broken
> and I can't use up2date), but as near as I can tell, RPM thinks of
> these two items as separate packages rather than as separate
> versions of the same package:
>
> openssh-2.9p2-12
> openssh-3.1p1-2
>
> If that's still true (it was the last time I was dealing with) then
> it is COMPLETELY brain-damaged. Arguably, this is the fault of the
> package maintainer rather than the fault of the RPM system, but if
> the RPM system is too dumb to comprehend 2.9p2 < 3.1p1 still, then
> it's broken at so basic a level that I just don't know how to deal.
If there's no file clashes, RPM can happily install multiple versions of
the one package. This is very useful when you need two different versions
of the one library on a system for some reason.
If there _are_ file clashes between versions, RPM will only install
multiple version of the one package if the --force option is supplied.
rpm -e openssh-2.9p2-12
should do what you want.
> --
> gabriel rosenkoetter
> gr@eclipsed.net
Michael Chapman
--
A computer without a Microsoft operating system is like a dog without
bricks tied to its head
______________________________________________________________________
Philadelphia Linux Users Group - http://www.phillylinux.org
Announcements-http://lists.phillylinux.org/mail/listinfo/plug-announce
General Discussion - http://lists.phillylinux.org/mail/listinfo/plug
|
|