George Brancovici wrote:
>
> On Fri, 2 Feb 2001 18:33:17 +0200
> Viorel Anghel <[EMAIL PROTECTED]> wrote:
> > WARNING: NU INCERCA ACEEASI MANEVRA CU RPM 4!
> Ok, si totusi cum fac cu Rpm4. Am incercat mai demult tot felul de
> variatii la ceea ce ai descris tu, dar nu a mers, insa nici urmari
> neplacute nu am avut. Dar ma dispera Rpm3, pentru care nimeni aproape nu
> mai face pachete. Nu am gasit nici un HowTo. Chiar nu se poate trece la
> Rpm4?
>
> Thanks,
RH are o lista de discutii dedicata rpm-ului; sapind in ea dupa aceeasi
pb. uite ce am gasit:
(raspunsurile le-am separat prin ---------------------)
> I have a RH6.0 machine with RPM3 installed. I want to upgrade some
> packages from the RH7.0 disk, but they are in RPM4 format. The machine
> is a DNS server and is much modified so I don't want to do a
> total RH7.0 upgrade, I just want some packages. So I need to upgrade
> my RPM from 3 to 4. But the RPM rpm's for version 4 are in RPM4 format
> so I need to upgrade before I can upgrade ... catch 22.
>
> I tried an RPM Build from the source, but it won't finish
> building and installing without db3 which I only have in RPM4 format which
> my RPM3 won't install.
>
> Is there a simple upgrade path?
>
> Cheers,
> Geoff Russell
>
The latest version of rpm in the 6.2 updates will read rpm 4 format.
But you do NOT want to upgrade to rpm 4 - it uses a different database
format then rpm 3.x. Also, you will have problems installing RPMs from
7.0 on a 6.x system. 7.0 uses a later version of libc, as well as other
libraties. Your best bet is to get the source RPM, and try and compile
it on your 6.0 system. You are still going to have to upgrade a lot of
packages. Basicly, you will want to upgrade the system to the latest
6.2 RPMs.
If you want to run the latest RedHat 7.0 packages, you are better off
upgrading to 7.0. Some of the libraries needed by 7.0 packages will
break 6.x packages. This is part of the reasion it is 7.0, and not 6.3.
---------------------------------------------------------------------------
I've installed a lot of 7.0 SRPM's to my 6.1 system (using the latest
RPM version in the 3.x series, and NOT RPM 4), and haven't had a lot of
dependency issues. The only notable one was initscripts. I haven't had
to upgrade my libc, though.
I always upgrade from source packages, so I can get the latest fixes
and features and so that the resulting binary is optimized to my
particular system.
Before an actual upgrade of any important package, I run a --test pass
to see what will be affected, and I tar up any config just in case I
have to back out the upgrade.
-----------------------------------------------------------------------
rpm >= 3.0.5 will read the 4.x format. These are for 6.x.
But you probably don't want to install redhat-7.x rpms on redhat-6.x.
6.x and 7.x are different animals. If you need something from 7.x
and you can't find a current version of it for 6.x on rpmfind.net
or other mirrors then look for a .src pkg and compile it yourself
on your system.
More than likely the 7.x wouldn't install anyway without force
because dependency checks would fail and forcing it could lead
to serious trouble.
-----------------------------------------------------------------
The mechanistic answer, which perhaps should be in the FAQ (if it
isn't), is to upgrade to rpm 3.0.5 or 3.0.6. These can read rpm4
packages. However, many RH7 packages also require the RH7 version
of glibc, and judging from recent traffic on this list that upgrade
can get tricky.
On a production machine, the best answer may be "don't go there."
At least, be sure of your backups before starting.
----------------------------------------------------------------
din acest motiv eu am intrebat cum se face de la 3.0.4 la 3.0.6 si nu la
4.
--
Once a Linux user always a Linux user
