OpenPKG CVS Repository
http://www.openpkg.org/cvsweb/cvsweb.cgi
____________________________________________________________________________
Server: cvs.openpkg.org Name: Michael Schloh
Root: /e/openpkg/cvs Email: [EMAIL PROTECTED]
Module: openpkg-adm Date: 29-Aug-2002 13:54:53
Branch: HEAD Handle: 2002082912545300
Modified files:
openpkg-adm upgrade.txt
Log:
Corrections, cleanups, and specify s/me/Ralf/ (assumption).
Summary:
Revision Changes Path
1.8 +28 -28 openpkg-adm/upgrade.txt
____________________________________________________________________________
Index: openpkg-adm/upgrade.txt
============================================================
$ cvs diff -u -r1.7 -r1.8 upgrade.txt
--- openpkg-adm/upgrade.txt 29 Aug 2002 10:08:06 -0000 1.7
+++ openpkg-adm/upgrade.txt 29 Aug 2002 11:54:53 -0000 1.8
@@ -9,13 +9,13 @@
=======================================
o Additional user accounts
-
- OpenPKG 1.1 adds additional user accounts to the system. The new UIDs
+
+ OpenPKG 1.1 adds additional user accounts to the system. The new UIDs
are not used by the bootstrap itself and can be changed by manually
configuring the system files immediately after the upgrade. Do not
modify them after any dependent packages were installed (i.e. postfix
and sendmail) as these packages might compile UIDs into the binary.
-
+
o Removed Packages
OpenPKG 1.1 does not include autogen, guile, imapd and sfio. They
@@ -24,7 +24,7 @@
ftp://ftp.openpkg.org/CURRENT/SRC/.
o Inconsistent rc.conf variables in rsync
-
+
Previously the rsync package inconsistently used rc.conf variables
with prefix "rsyncd_". This was now corrected to be "rsync_". The
entries in rc.conf have to be corrected manually.
@@ -47,7 +47,7 @@
by default. Instead PAM support can be consistently enabled there
through a --define "with_pam yes" during build-time. This now
requires the "pam" glue package to be installed first. This "pam"
- package now takes over the task of re-configuring the /etc/pam.d/ or
+ package now takes over the task of reconfiguring the /etc/pam.d/ or
/etc/pam.conf in a consistent way. The following table compares
PAM support between this and the previous OpenPKG release.
@@ -87,12 +87,12 @@
===========================================
o RPM downgrade view:
-
+
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
+ unconditionally makes RPM think that 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
@@ -105,25 +105,25 @@
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
+ receive static ELF binaries with the 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
+ 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
-
+
Upgrade from OpenPKG 0.9 to OpenPKG 1.0
=======================================
@@ -143,42 +143,42 @@
_NOW_ upgraded to the new bootstrap package.
For the experts: it has to be done before we rename/add/delete files
- in forthcoming openpkg-0.9-X versions, because else a complete
- re-install would be required later or the database would be no longer
+ in forthcoming openpkg-0.9-X versions, because otherwise a complete
+ reinstall would be required later or the database would no longer be
in sync with the installed files if you upgrade too late.
To determine whether an OpenPKG hierarchy has to be upgraded, run the
following command:
-
+
# 0. determine current state
$ rpm -qa | egrep '(rpm|openpkg)'
-
+
If the output is "rpm-4.0-X" upgrading is required. If the output is
"openpkg-0.9-X" upgrading was already done (perhaps by someone else)
and so you do _NOT_ have to upgrade immediately.
-
+
If upgrading is required, enter as soon as possible the following
commands as "root" exactly as they are written down here and in
exactly this order for every OpenPKG filesystem hierarchy (replace /cw
with the path to your particular OpenPKG hierarchy):
-
+
# 1. enter the OpenPKG filesystem hierarchy (for relative paths below)
$ cd /cw
-
- # 2. rebuild the OpenPKG bootstrap package for this hierarchy
+
+ # 2. rebuild the OpenPKG bootstrap package for this hierarchy
$ bin/rpm --rebuild http://www.openpkg.org/pkg/openpkg-0.9-8.src.rpm
-
+
# 3. remove the old bootstrap name from RPM database
$ bin/rpm -e --justdb --nodeps rpm
-
+
# 4. install the new bootstrap [expect 2 warnings]
$ bin/rpm -i --noscripts --nodeps --force RPM/PKG/openpkg-0.9-8.*.rpm
-
+
# 5. rebuild the RPM database
$ bin/rpm --rebuilddb
-
+
# 6. cleanup after upgrade
$ rm -f etc/rpm/*.rpmorig
-
- For more details or help in case of problems, feel free to contact me.
-
+
+ For more details or help in case of problems, feel free to contact Ralf.
+
______________________________________________________________________
The OpenPKG Project www.openpkg.org
CVS Repository Commit List [EMAIL PROTECTED]
