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: 20-Feb-2004 12:50:39
Branch: HEAD Handle: 2004022011503900
Modified files:
openpkg-re upgrade.txt
Log:
recommended manual upgrade procedure
Summary:
Revision Changes Path
1.28 +103 -5 openpkg-re/upgrade.txt
____________________________________________________________________________
patch -p0 <<'@@ .'
Index: openpkg-re/upgrade.txt
============================================================================
$ cvs diff -u -r1.27 -r1.28 upgrade.txt
--- openpkg-re/upgrade.txt 20 Feb 2004 09:29:22 -0000 1.27
+++ openpkg-re/upgrade.txt 20 Feb 2004 11:50:39 -0000 1.28
@@ -2,7 +2,7 @@
General Notes
=============
- o $Revision: 1.27 $. The most recent update of this file can be
+ o $Revision: 1.28 $. 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
@@ -121,10 +121,10 @@
of the "openpkg" package itself is an exception that requires
additional steps.
- - we provide an intermediate openpkg-1.9.9-2.0.0.src.rpm (no src.sh)
- package which can be installed using a 1.x bootstrap. This
- intermediate package is only supported to fulfill one operation:
- upgrade to the real 2.0.0 bootstrap.
+ - we provide an intermediate openpkg-1.9.9-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.
- install 2.0.0 source RPM, filter the offending "Class:" header out from the
spec and build binary.
@@ -132,6 +132,14 @@
- get ingredients from 2.0.0 source RPM using rpm2cpio, filter the
offending header out from the spec and build binary.
+ o error "Unknown tag: Class"
+
+ The message appears when a bootstrap is not aware of the new
+ "Class:" header and is given a spec file which makes use of this
+ new feature. Upgrade the bootstrap. If the problem is building the
+ boostrap during upgrade you probably tried to skip the intermediate
+ step.
+
o new tag feature to replace location id
In OpenPKG v1.x, binaries were named
@@ -277,7 +285,97 @@
13> pam-20030715-1.3.0.src.rpm (accident)
13> pam-1.3.1-1.3.1.src.rpm
20> pam-0-2.0.0.src.rpm
+
+ o recommended manual upgrade procedure
+
+ - documentation:
+ review and understand the news.txt file and the other upgrade
+ information within this upgrade.txt file.
+
+ - basis:
+ ensure the existing instance runs the OpenPKG 1.3.1 bootstrap
+ or a CURRENT bootstrap dated in the range 20030925 ... 20040130
+ inclusive. Later CURRENT bootstraps do not require special
+ attention. Older boostraps need to be upgraded first. [FIXME
+ what about sooner boostraps, 1.3.0 and 1.2.x?] Also be sure the
+ installed packages match the bootstrap release/age.
+
+ - packages:
+ examine installed packages names and manually check if they still
+ exist in the OpenPKG 2.0 release.
+
+ $ %{l_prefix}/bin/rpm -qa
+
+ - applications:
+ examine installed packages for vendor application versions and
+ manually check which vendor version comes with OpenPKG 2.0. Be
+ sure you can handle the new version.
+
+ $ %{l_prefix}/bin/rpm -qa --queryformat '%{name}-%{VERSION}\n'
+
+ - options:
+ examine installed packages for options that are in use and
+ manually check if options are still available with or renamed in
+ OpenPKG v2.0
+
+ $ %{l_prefix}/bin/rpm -qa --queryformat '%{name} provides: [%{PROVIDES} ]\n'
+
+ - tag:
+ think about altering the default tag for binaries.
+
+ - backup:
+ verify the backup of your instance is up to date, complete,
+ readable, integrity checked and stored in a safe location which is
+ accessible after a possibly failed upgrade. If you do not have a
+ proper backup we strongly recommend you rescue at least the whole
+ %{l_prefix}/etc directory.
+
+ # cd %{l_prefix} && tar cvf /my/safe/place/opkg131etc.tar etc/
+
+ - conflict:
+ remove the openpkg-tool package, if currently in use.
+
+ # %{l_prefix}/bin/rpm -e openpkg-tool
+
+
+ - intermediate:
+ upgrade the bootstrap to an intermediate version. This is acutally
+ a full featured OpenPKG 2.0 but the Class: header was omitted to
+ allow older bootstraps to rebuild it. The rc system will choke if
+ you have outdated pre-OpenPKG 1.3 packages installed!
+
+ $ %{l_prefix}/bin/rpm --rebuild \
+ ftp://ftp.openpkg.org/release/2.0/SRC/openpkg-1.9.9-2.0.0.src.rpm
+
+ **** POINT OF NO RETURN ****
+
+ # %{l_prefix}/bin/rpm -Uvh openpkg-1.9.9-2.0.0-*.rpm
+
+ - conversion:
+ rebuild the database, converting it to the new format
+ # %{l_prefix}/bin/openpkg rpm --db-rebuild
+
+ - upgrade:
+ $ %{l_prefix}/bin/openpkg rpm --rebuild --tag='<user>@<host>' \
+ ftp://ftp.openpkg.org/release/2.0/SRC/openpkg-2.0.0-2.0.0.src.rpm
+ # %{l_prefix}/bin/openpkg rpm -Uvh openpkg-2.0.0-2.0.0-*.rpm
+
+ The bootstrap is now upgraded. Now upgrade the applications step
+ by step. Start with packages that do not require other packages.
+ Then continue with packages that only require the ones you already
+ upgraded. Do until every package is upgraded.
+
+ View dependencies:
+ $ %{l_prefix}/bin/openpkg rpm -qa --queryformat '%{name} requires:[
%{REQUIRENAME}]\n' \
+ | sed -e 's;[Oo]pen[Pp][Kk][Gg] *;;g' -e 's; [^ ]*([^)]*);;g'
+
+ Be sure you use the new options names when rebuilding. Note that
+ packages where version numbering changed might require a
+ --oldpackage to trick rpm.
+ Check for configuration changes after installing.
+ $ find %{l_prefix}/etc/ -type f | egrep '\.rpm(save|orig|new)'
+
Upgrade from OpenPKG 1.2 to OpenPKG 1.3
=======================================
@@ .
______________________________________________________________________
The OpenPKG Project www.openpkg.org
CVS Repository Commit List [EMAIL PROTECTED]
