On Wed, 14 Nov 2001, Thomas Ribbrock wrote:

> On Wed, Nov 14, 2001 at 11:00:26PM +1000, Matthew Melvin wrote:
> > The problem isn't with upgrading the machines to use rpm4 - we acutally do
> > that.  The problem is that the version of rpm used by the redhat installer
> > (anaconda?) itself doens't properly understand packages built with rpmv4.
> [...]
>
> I knew I'd be overlooking something - thanks for the explanation! So, to
> handle this situation correctly, RH would have needed to provide an update
> for the installer as well?
>
> Cheerio,
>
> Thomas

Hello Martthew and Thomas,

        In fact, I tried upgrading the Rh6.2 "instimage" directory from
rpm3 to rpm4 with correct libraries but it didn't seem to work.. I suspect
this is because rpm-python from "instimage" was built with rpm3 and
upgrading the "rpm" command under "instimage" doesn't help... The
behaviour we got when we applied the first rpm4 package to our kickstart
installs (I believe it was ucd-snmpd*) was that the package would be
present in the rpm-db but no files (or several missing files) were to be
found on the actual filesystem.. I may not have investigated that issue
enough but it should be feasible - I think - to upgrade an rpm3-based
instimage from rh6.2 to an rpm4 tree..

,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,
Vincent S. Cojot, Computer Engineering. STEP project. _.,-*~'`^`'~*-,._.,-*~
Ecole Polytechnique de Montreal, Comite Micro-Informatique. _.,-*~'`^`'~*-,.
Linux Xview/OpenLook resources page _.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'
http://step.polymtl.ca/~coyote  _.,-*~'`^`'~*-,._ [EMAIL PROTECTED]

They cannot scare me with their empty spaces
Between stars - on stars where no human race is
I have it in me so much nearer home
To scare myself with my own desert places.       - Robert Frost





_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list

Reply via email to