OpenPKG CVS Repository
http://www.openpkg.org/cvsweb/cvsweb.cgi
____________________________________________________________________________
Server: cvs.openpkg.org Name: Thomas Lotterer
Root: /e/openpkg/cvs Email: [EMAIL PROTECTED]
Module: openpkg-adm Date: 29-Aug-2002 10:25:37
Branch: HEAD Handle: 2002082909253700
Modified files:
openpkg-adm upgrade.txt
Log:
from CURRENT to openpkg-1.1
Summary:
Revision Changes Path
1.4 +35 -5 openpkg-adm/upgrade.txt
____________________________________________________________________________
Index: openpkg-adm/upgrade.txt
============================================================
$ cvs diff -u -r1.3 -r1.4 upgrade.txt
--- openpkg-adm/upgrade.txt 6 Jun 2002 16:36:50 -0000 1.3
+++ openpkg-adm/upgrade.txt 29 Aug 2002 08:25:37 -0000 1.4
@@ -5,12 +5,42 @@
You cannot skip a version. That means, upgrading from 0.9 to 1.1
requires an upgrade to 1.0 as an intermediate step.
- OpenPKG Bootstrap "downgrade" from openpkg-20021234 (aka CURRENT) to openpkg-1.1
- ================================================================================
+ OpenPKG Bootstrap "downgrade" from CURRENT to openpkg-1.1
+ =========================================================
- Use --oldpackage for bootstrap first, then do the same for additional
- packages. Some might require --nodeps or require all dependent
- packages given on one command line.
+ If binutils and gcc-3.2 were installed previously, binutils, gcc and
+ openpkg must be upgraded in exacly that order.
+
+ Due to a problem with binutils before 200208261229 FreeBSD users will
+ receive static ELF binaries with wrong brand. The loader will reject
+ them with error 'ELF binary type "0" not known'. Unfortunately, the
+ /cw/lib/openpkg/rpm executable called by the /cw/bin/rpm wrapper is
+ such a binary. If you receive this error the last chance to recover is
+ to brand the binary manually, i.e. using
+
+ $ brandelf -t "FreeBSD" /cw/lib/openpkg/rpm
+
+ The following table shows the three critical packages and tells which
+ are identical besides the number. If CURRENT packages are older than
+ those listed, switching to v1.1.0 is a real upgrade. If the numbers
+ match exactly switching to v1.1.0 will not change anything but the
+ number. If CURRENT packages are newer than those listed, switching to
+ v1.1.0 is a real downgrade.
+
+ openpkg-20020826-20020826 = openpkg-1.1.0-1.1.0
+ binutils-2.13-20020826 = binutils-2.13-1.1.0
+ gcc-3.2-20020815 = gcc-3.2-1.1.0
+
+ Please understand the difference between a real up-/downgrade compared
+ to what RPM thinks is a up-/downgrade.
+
+ The nature of the OpenPKG release engineering version number scheme
+ unconditionally makes RPM thinking the step from CURRENT to any
+ release is a downgrade. Use --oldpackage along with -Uvh to cheat and
+ force RPM to accept that "downgrade". Some packages might require an
+ additional --nodeps to unchain version dependencies for the same
+ reason. An alternative to ignoring depencencies is to specify all
+ dependent packages on a single command line.
OpenPKG Bootstrap Upgrade from openpkg-1.0 to openpkg-1.1
=========================================================
______________________________________________________________________
The OpenPKG Project www.openpkg.org
CVS Repository Commit List [EMAIL PROTECTED]
