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:   05-Oct-2003 15:37:50
  Branch: HEAD                             Handle: 2003100514375000

  Modified files:
    openpkg-re              upgrade.txt

  Log:
    start assembling the OpenPKG 2.0 upgrade hints

  Summary:
    Revision    Changes     Path
    1.15        +8  -1      openpkg-re/upgrade.txt
  ____________________________________________________________________________

  patch -p0 <<'@@ .'
  Index: openpkg-re/upgrade.txt
  ============================================================================
  $ cvs diff -u -r1.14 -r1.15 upgrade.txt
  --- openpkg-re/upgrade.txt    6 Aug 2003 11:08:54 -0000       1.14
  +++ openpkg-re/upgrade.txt    5 Oct 2003 13:37:50 -0000       1.15
  @@ -2,7 +2,7 @@
     General Notes
     =============
   
  -  o $Revision: 1.14 $. The most recent update of this file can be
  +  o $Revision: 1.15 $. 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
  @@ -33,6 +33,13 @@
       security compatiblity as we only support the latest release and it's
       immediate predecessor. So don't fall behind by running outdated
       releases for prolonged times.
  +
  +  Upgrade from OpenPKG 1.3 to OpenPKG 2.0
  +  =======================================
  +
  +  o RPM 4.0.2 to 4.2.1:
  +
  +    you can't go back and require a --db-rebuild afterwards!
   
     Upgrade from OpenPKG 1.2 to OpenPKG 1.3
     =======================================
  @@ .
______________________________________________________________________
The OpenPKG Project                                    www.openpkg.org
CVS Repository Commit List                     [EMAIL PROTECTED]

Reply via email to