OpenPKG CVS Repository
http://cvs.openpkg.org/
____________________________________________________________________________
Server: cvs.openpkg.org Name: Thomas Lotterer
Root: /e/openpkg/cvs Email: [EMAIL PROTECTED]
Module: openpkg-re Date: 13-Mar-2004 22:30:06
Branch: HEAD Handle: 2004031321300500
Modified files:
openpkg-re upgrade.txt
Log:
mention build host issue in "upgrade procedure with intermediate step"
(feedback from Christian Reiber)
Summary:
Revision Changes Path
1.37 +33 -19 openpkg-re/upgrade.txt
____________________________________________________________________________
patch -p0 <<'@@ .'
Index: openpkg-re/upgrade.txt
============================================================================
$ cvs diff -u -r1.36 -r1.37 upgrade.txt
--- openpkg-re/upgrade.txt 10 Mar 2004 10:31:58 -0000 1.36
+++ openpkg-re/upgrade.txt 13 Mar 2004 21:30:05 -0000 1.37
@@ -2,7 +2,7 @@
General Notes
=============
- o $Revision: 1.36 $. The most recent update of this file can be
+ o $Revision: 1.37 $. The most recent update of this file can be
downloaded from http://cvs.openpkg.org/openpkg-re/upgrade.txt
o This file upgrade.txt file talks about tweaks and quirks when
@@ -113,24 +113,38 @@
o upgrade procedure with intermediate step
- While RPM silently ignores unknown sections, the introduction of
- the new "Class:" header inhibits older RPMs from parsing the spec
- file. Thus an old RPM will refuse to accept packages leveraging
- such a feature. For all but one package it means that the OpenPKG
- bootstrap package "openpkg" has to be upgraded first. The upgrade of
- the "openpkg" package itself is an exception that requires one of
- the following two steps:
-
- - possibility 1: we provide an intermediate
- openpkg-1.9.0-2.0.0.src.rpm (intentionally no src.sh available)
- package which can be rebuild and installed using a 1.x bootstrap.
- This intermediate package is only supported to fulfill the upgrade
- operation.
-
- - possibility 2: install 2.0.0 source RPM, filter the offending
- "Class:" header out from the spec and build binary. Or get
- ingredients from 2.0.0 source RPM using rpm2cpio, filter the
- offending header out from the spec and build binary.
+ While RPM silently ignores unknown sections, the introduction of the
+ new "Class:" header inhibits older RPMs from parsing the spec file.
+ Therefore the bootstrap package "openpkg" has to be upgraded first
+ using one of the following variants:
+
+ - use openpkg-1.3.1 to rebuild and install the
+ openpkg-1.9.0-2.0.0.src.rpm provided with the 2.0 release
+ (intentionally no src.sh available). This intermediate package
+ is a modified openpkg-2.0.0-2.0.0.src.rpm that has the offending
+ "Class:" header removed. This is the recommended variant.
+
+ - use openpkg-1.3.1 to install openpkg-2.0.0-2.0.0.src.rpm, manually
+ filter out the offending "Class:" header. Then build and install
+ it using openpkg-1.3.1.
+
+ - use rpm2cpio to get ingredients from openpkg-2.0.0-2.0.0.src.rpm,
+ manually filter out the offending "Class:" header. Then build and
+ install it using openpkg-1.3.1.
+
+ The last step of upgrading the "openpkg" package is to use the 1.9
+ aka "Class:"-less 2.0 bootstrap to rebuild and install the real
+ openpkg-2.0.0-2.0.0.src.rpm. At this point the upgrade reaches a
+ point undistinguishable from a fresh install.
+
+ Note that a 1.x installation is not able to read 2.x binary RPMs.
+ When upgrading, it is a requirement using openpkg-1.3.1 to build the
+ 1.9 aka "Class:"-less 2.0 bootstrap binary RPM. If you use a build
+ host to create binaries and deploy them on target machines make sure
+ the build host runs openpkg-1.3.1 when creating the intermediate
+ package and the build host runs openpkg-2.0.0 when creating the real
+ package. Deploy the intermediate then the real bootstrap to the
+ target machines. Do not skip the intermediate step.
o error "Unknown tag: Class"
@@ .
______________________________________________________________________
The OpenPKG Project www.openpkg.org
CVS Repository Commit List [EMAIL PROTECTED]
