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

  Server: cvs.openpkg.org                  Name:   Thomas Lotterer
  Root:   /e/openpkg/cvs                   Email:  [EMAIL PROTECTED]
  Module: openpkg-web                      Date:   22-Jan-2003 14:02:51
  Branch: HEAD                             Handle: 2003012213025000

  Modified files:
    openpkg-web/security    OpenPKG-SA-0000.000-template.txt

  Log:
    migrate template from 1.1/1.0 to 1.2/1.1; drop 1.0

  Summary:
    Revision    Changes     Path
    1.9         +13 -13     openpkg-web/security/OpenPKG-SA-0000.000-template.txt
  ____________________________________________________________________________

  patch -p0 <<'@@ .'
  Index: openpkg-web/security/OpenPKG-SA-0000.000-template.txt
  ============================================================================
  $ cvs diff -u -r1.8 -r1.9 OpenPKG-SA-0000.000-template.txt
  --- openpkg-web/security/OpenPKG-SA-0000.000-template.txt     16 Jan 2003 13:53:34 
-0000      1.8
  +++ openpkg-web/security/OpenPKG-SA-0000.000-template.txt     22 Jan 2003 13:02:50 
-0000      1.9
  @@ -12,13 +12,13 @@
   
   Affected Releases:   Affected Packages:          Corrected Packages:
   OpenPKG CURRENT      <= foo-1.2.5-20021003       >= foo-1.2.5-20030115
  +OpenPKG 1.2          <= foo-1.2.4-1.2.0          >= foo-1.2.4-1.2.1
   OpenPKG 1.1          <= foo-1.2.4-1.1.0          >= foo-1.2.4-1.1.1
  -OpenPKG 1.0          <= foo-1.2.0-1.0.0          >= foo-1.2.0-1.0.1
   
   Affected Releases:   Dependent Packages:
   OpenPKG CURRENT      bar quux
  -OpenPKG 1.1          bar quux
  -OpenPKG 1.0          bar
  +OpenPKG 1.2          bar quux
  +OpenPKG 1.1          bar 
   
   Description:
     According to a ... security advisory based on hints from ...
  @@ -38,19 +38,19 @@
     [5][6], fetch it from the OpenPKG FTP service [7][8] or a mirror
     location, verify its integrity [9], build a corresponding binary RPM
     from it [3] and update your OpenPKG installation by applying the binary
  -  RPM [4]. For the current release OpenPKG 1.1, perform the following
  +  RPM [4]. For the current release OpenPKG 1.2, perform the following
     operations to permanently fix the security problem (for other releases
     adjust accordingly).
   
     $ ftp ftp.openpkg.org
     ftp> bin
  -  ftp> cd release/1.1/UPD
  -  ftp> get foo-1.2.4-1.1.1.src.rpm
  +  ftp> cd release/1.2/UPD
  +  ftp> get foo-1.2.4-1.2.1.src.rpm
     ftp> bye
  -  $ <prefix>/bin/rpm -v --checksig foo-1.2.4-1.1.1.src.rpm
  -  $ <prefix>/bin/rpm --rebuild foo-1.2.4-1.1.1.src.rpm
  +  $ <prefix>/bin/rpm -v --checksig foo-1.2.4-1.2.1.src.rpm
  +  $ <prefix>/bin/rpm --rebuild foo-1.2.4-1.2.1.src.rpm
     $ su -
  -  # <prefix>/bin/rpm -Fvh <prefix>/RPM/PKG/foo-1.2.4-1.1.1.*.rpm
  +  # <prefix>/bin/rpm -Fvh <prefix>/RPM/PKG/foo-1.2.4-1.2.1.*.rpm
   
     Additionally, we recommend that you rebuild and reinstall
     all dependent packages (see above), if any, too. [3][4]
  @@ -62,10 +62,10 @@
     [2] http://cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-...
     [3] http://www.openpkg.org/tutorial.html#regular-source
     [4] http://www.openpkg.org/tutorial.html#regular-binary
  -  [5] ftp://ftp.openpkg.org/release/1.0/UPD/foo-1.2.0-1.0.1.src.rpm
  -  [6] ftp://ftp.openpkg.org/release/1.1/UPD/foo-1.2.4-1.1.1.src.rpm
  -  [7] ftp://ftp.openpkg.org/release/1.0/UPD/
  -  [8] ftp://ftp.openpkg.org/release/1.1/UPD/
  +  [5] ftp://ftp.openpkg.org/release/1.1/UPD/foo-1.2.0-1.1.1.src.rpm
  +  [6] ftp://ftp.openpkg.org/release/1.2/UPD/foo-1.2.4-1.2.1.src.rpm
  +  [7] ftp://ftp.openpkg.org/release/1.1/UPD/
  +  [8] ftp://ftp.openpkg.org/release/1.2/UPD/
     [9] http://www.openpkg.org/security.html#signature
   ________________________________________________________________________
   
  @@ .
______________________________________________________________________
The OpenPKG Project                                    www.openpkg.org
CVS Repository Commit List                     [EMAIL PROTECTED]

Reply via email to