OpenPKG CVS Repository
  http://cvs.openpkg.org/
  ____________________________________________________________________________

  Server: cvs.openpkg.org                  Name:   Ralf S. Engelschall
  Root:   /e/openpkg/cvs                   Email:  [EMAIL PROTECTED]
  Module: openpkg-re                       Date:   25-Feb-2004 21:47:11
  Branch: HEAD                             Handle: 2004022520471000

  Modified files:
    openpkg-re              news.txt upgrade.txt

  Log:
    bugfixes

  Summary:
    Revision    Changes     Path
    1.38        +6  -7      openpkg-re/news.txt
    1.33        +24 -24     openpkg-re/upgrade.txt
  ____________________________________________________________________________

  patch -p0 <<'@@ .'
  Index: openpkg-re/news.txt
  ============================================================================
  $ cvs diff -u -r1.37 -r1.38 news.txt
  --- openpkg-re/news.txt       25 Feb 2004 10:13:39 -0000      1.37
  +++ openpkg-re/news.txt       25 Feb 2004 20:47:10 -0000      1.38
  @@ -2,7 +2,7 @@
     General Note
     ============
   
  -  o $Revision: 1.37 $. The most recent update of this file can be
  +  o $Revision: 1.38 $. The most recent update of this file can be
       downloaded from http://cvs.openpkg.org/openpkg-re/news.txt
   
     o This file news.txt file talks about new features and major
  @@ -57,11 +57,9 @@
   
       OpenPKG release numbering is driven by technical enhancements and
       release engineering requirements, not by marketing. The technical
  -    change is that we now have RPM 4.2.1 under the hood. The engineering
  -    changes are (for the time being) the discontinuation of a STABLE
  -    branch and SNAPSHOTs. The typical administrator knowing OpenPKG 1.3
  -    will experience a flat learning curve when he starts working with
  -    the new 2.0 release.
  +    change is that we now have RPM 4.2.1 under the hood. The typical
  +    administrator knowing OpenPKG 1.3 will experience a flat learning
  +    curve when he starts working with the new 2.0 release.
   
     o Supported Platforms
   
  @@ -507,6 +505,7 @@
       package:
   
         # value=`cat /proc/sys/kernel/exec-shield`
  +      # echo 0 >/proc/sys/kernel/exec-shield
         # rpm --rebuild emacs-....
         # echo $value >/proc/sys/kernel/exec-shield
   
  @@ -540,7 +539,7 @@
       syslog(3) facility. OpenPKG 2.0 comes with PLUS packages having that
       enhancement.
   
  -  o [TODO] Upgrade to Perl 5.8.2 and fully worked off extensional
  +  o Upgrade to Perl 5.8.3 and fully worked off extensional
       Perl module packaging (module search order, vendor_perl, new
       perl-openpkg.sh)
   
  @@ .
  patch -p0 <<'@@ .'
  Index: openpkg-re/upgrade.txt
  ============================================================================
  $ cvs diff -u -r1.32 -r1.33 upgrade.txt
  --- openpkg-re/upgrade.txt    25 Feb 2004 10:13:39 -0000      1.32
  +++ openpkg-re/upgrade.txt    25 Feb 2004 20:47:10 -0000      1.33
  @@ -2,7 +2,7 @@
     General Notes
     =============
   
  -  o $Revision: 1.32 $. The most recent update of this file can be
  +  o $Revision: 1.33 $. 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
  @@ -116,20 +116,20 @@
       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 packages 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
  -    additional steps.
  -
  -    - 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.
  -
  -    - install 2.0.0 source RPM, filter the offending "Class:" header out from the
  -      spec and build binary.
  -       
  -    - get ingredients from 2.0.0 source RPM using rpm2cpio, filter the
  +    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.
   
     o error "Unknown tag: Class"
  @@ -181,8 +181,8 @@
       using the new %{l_prefix}/bin/openpkg command multiplexer and use
       the appropriate subcommand, i.e.
   
  -        $ /13/bin/rpm -qi openpkg
  -        $ /20/bin/openpkg rpm -qi openpkg
  +        $ /13/bin/rpm -qi openpkg          # <= OpenPKG 1.3
  +        $ /20/bin/openpkg rpm -qi openpkg  # >= OpenPKG 2.0
   
       OpenPKG 2.0 provides a wrapper for "rpm" and "rpm2cpio" to be found
       at the well known locations. They provide a compatible interface and
  @@ -230,8 +230,8 @@
       installed which was revamped to provide "index" and "build" plug
       ins. This effectively hides the change for normal use, i.e.
   
  -        $ /13/bin/openpkg build -Ua
  -        $ /20/bin/openpkg build -Ua
  +        $ /13/bin/openpkg build -Ua  # <= OpenPKG 1.3
  +        $ /20/bin/openpkg build -Ua  # >= OpenPKG 2.0
   
       However, access to the manual page(s) changed
   
  @@ -310,8 +310,8 @@
         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. Also be
  -      sure the installed packages match the bootstrap release/age.
  +      attention. Older boostraps need to be upgraded first. It is safest
  +      if the installed packages match the bootstrap release/age.
   
       - packages:
         examine installed packages names and manually check if they still
  @@ -351,10 +351,10 @@
         # %{l_prefix}/bin/rpm -e openpkg-tool
   
       - intermediate:
  -      upgrade the bootstrap to an intermediate version. This is acutally
  +      upgrade the bootstrap to an intermediate version. This is actually
         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!
  +      you have outdated pre-OpenPKG 1.3 packages installed! FIXME: WHY?
   
         $ %{l_prefix}/bin/rpm --rebuild \
           ftp://ftp.openpkg.org/release/2.0/SRC/openpkg-1.9.0-2.0.0.src.rpm
  @@ -1026,8 +1026,8 @@
       chown the <prefix>/var/squid/cache directory to rusr:rgrp.
   
     o More bullets
  +    FIXME
     - sharutils requirement (SuSE)
  -  - check anything listed here must be moved to NEWS or vice versa
     - removal of /var files including logs on erase
     - restart of application on startup
     - behaviour of rc output when executing a %section and the -o option
  @@ .
______________________________________________________________________
The OpenPKG Project                                    www.openpkg.org
CVS Repository Commit List                     [EMAIL PROTECTED]

Reply via email to