[linux] RPM3/4

[Peter Ivanyi]

> > > Pouzivam RH6.2, teda RPM3. Mnoho novych balikov RPM je vytvorenych v RPM4.
> > > Ako upgradovat RPM3->RPM4?
> > V oficialnych updejtoch je patricny balik, konkretne rpm-3.0.5-9.6x.i386.rpm
> > alebo este novsi rpm-4.0.2-6x.i386.rpm
> > Ja neviem je to naozaj take zlozite na to dost ze s tym furt maju ludia
> > problemy?
> 
> 	Myslim, ze je, pretoze RPM4 potrebuje na svoju vlastnu instalaciu
> RPM4, co moze byt tomu, kto ma tradicne RPM3 asi tak na dve veci.

To bola pravda trochu davnejsie, ked jedinym oficialnym miestom 4kovej
verzie bola distribucia rawhide (slo to vyriesit stiahnutim binarky rpm
alebo rpm2cpio, pomocou nej instalaciou srpm, a zostavenim balika
starsou verziou rpm)

 
> 	Ja viem, ze riesenim je nainstalovanie si RPM >= 3.0.5, ale zvlast
> po tom, co na stranke rpm.org nie je ziadny oficialny navod, to moze byt pre
> normalneho cloveka dost _tazko_ pochopitelne. A potom, ze ideme robit Linux
> pre normalnych ludi... :-/
> 
> 	Navyse databazy RPM3 a RPM4 su navzajom nekompatibilne, ale to uz je
> o inom. Ospravedlnujem sa za mozno zbytocny e-mail.

Povedal by som, ze je takmer nutnostou kazdeho admina niektorej
distribucie sledovanie min. bezpecnostnych konferencii
konkretnych autorov distribucii. A prihlasit sa do nich skutocne
nie je ziadny problem - v drvivej vacsine pripadov sa da k nim
napr. doklikat priamo z domovskych stranok.

Nakolko som offline a nemozem uviest odkaz, tak aspon cast oznamenia
z listu linux-security na redhat.com, ktora moze byt uzitocna (na
prekvapenie) uzivatelom distribucie Red Hat:

> ---------------------------------------------------------------------
>                    Red Hat, Inc. Red Hat Security Advisory
> 
> Synopsis:          rpm-4.0.2 for all Red Hat platforms and releases.
> Advisory ID:       RHSA-2001:016-03
> Issue date:        2001-02-19
> Updated on:        2001-03-19
> Product:           Red Hat Linux
> Keywords:          rpm
> Cross references:
> Obsoletes:
> ---------------------------------------------------------------------
> 
> 1. Topic:
> 
> A common version of rpm for all Red Hat distributions is being released.
> This version of rpm understands legacy version 3 packaging used in Red
> Hat 6.x/5.x distributions as well as version 4 packaging used in Red Hat
> 7.x.
> In addition, rpm-4.0.2 has support for both the legacy db1 format used in
> Red Hat 6.x/5.x databases as well as support for the db3 format database
> used in Red Hat 7.x
> 
> 2. Relevant releases/architectures:
> 

[ vystrihnute ]

> Several potential problems
> 
> 1) Red Hat 6.x/5.x users will need to install the db3 packages from
>     RHEA-2001:015-09.
> 
> 2) Red Hat 5.x users should note that the default compiler flags in rpm
>     have changed, and are not compatible with the gcc originally shipped
>     with Red Hat 5.2. Use egcs as a compiler instead.
> 
> 3) Red Hat 6.x/5.x users should convert from db1 to db3 format dtabases at
>     your earliest convience. This can be done by running, as root, the
>     command
>         rpm --rebuilddb
>     Support for legacy db1 format rpm databases will be removed in the next
>     release of rpm.
> 
> 4) All platforms: If you chose to install rpm-4.0.2, and then go back to a
>     previous version of rpm, then you will experience segfaults due to an
>     incompatible change in headers in the database. The problem is in
>     legacy versions of rpm going back to rpm-3.0, and is both caused and
>     fixed by rpm-4.0.2. This incompatibility also applies to any/all
>     applications that are statically linked against rpm libraries which
>     should either be upgraded or recompiled to use rpm-4.0.2 libraries.
>     Applications that use shared libraries should not be affected by this
>     problem.
> 
> 5) All platforms: rpm-4.0.2 will fail to install if you have both db1 and
>     db3 rpm databases in /var/lib/rpm. If the packages do not install,
>     please check the directory /var/lib/rpm for the files "packages.rpm"
>     (the db1 format headers) and "Packages" (the db3 format headers)
>     and rename/remove the older or smaller of the two files in order to
>     upgrade.
> 
> 4. Solution:
> 
> To update all RPMs for your particular architecture, run:
> 
> rpm -Fvh <filenames>
> 
> where <filenames> is a list of the RPMs you wish to upgrade.  Only those
> RPMs which are currently installed will be updated.  Those RPMs which are
> not installed but included in the list will not be updated.  Note that you
> can also use wildcards (*.rpm) if your current directly *only* contains the
> desired RPMs.


Po stiahnuti spravnej verzie z nejakeho mirroru ftp://updates.redhat.com/
alebo pouziti up2date je postup jasny. Volbu, ci trebars na 5.2 instalovat
verziu rpm 3.0.5-9* alebo 4.0.2 si musi zvazit kazdy sam.
Pred aktualizaciou rpm je este ziaduce zozalohovat adresar /var/lib/rpm.



Peter