OpenPKG CVS Repository
http://cvs.openpkg.org/
____________________________________________________________________________
Server: cvs.openpkg.org Name: Thomas Lotterer
Root: /e/openpkg/cvs Email: [EMAIL PROTECTED]
Module: openpkg-re Date: 30-Jul-2003 14:17:54
Branch: HEAD Handle: 2003073013175400
Modified files:
openpkg-re news.txt
Log:
import filtered information from our internal weekly summaries
Summary:
Revision Changes Path
1.19 +98 -0 openpkg-re/news.txt
____________________________________________________________________________
patch -p0 <<'@@ .'
Index: openpkg-re/news.txt
============================================================================
$ cvs diff -u -r1.18 -r1.19 news.txt
--- openpkg-re/news.txt 29 Jul 2003 12:47:29 -0000 1.18
+++ openpkg-re/news.txt 30 Jul 2003 12:17:54 -0000 1.19
@@ -2,6 +2,104 @@
Major changes between OpenPKG 1.2 and OpenPKG 1.3
=================================================
+ o hook to support forthcoming OSSP rc which should eventually
+ replace the OpenPKG "rc" script. The hook checks if the OSSP rc
+ is installed and automatically executes it instead of the old
+ <prefix>/etc/rc. OSSP rc is provided by installing the
+ "openpkg-rc" package. This is an early adopters replacement
+ package only.
+
+ o mangled and partly rewritten OpenPKG "rc" script. It now provides
+ correct error handing, verbose messages, supports Bourne- and
+ C-Shell style shells for %env, uses secure temporary file
+ handling, to name some few majors. Now it comes with a man page.
+
+ o additionally we were also very busy in cleaning up and enhancing
+ the run-command scripts of all CORE and BASE. We especially
+ added the long-awaited %status section which soon will allow us
+ to add smarter starting and stopping of our daemons.
+
+ o log file rotation was hardened for all CORE and BASE packages.
+ We took care of permissions and daemons will be reloaded,
+ restarted or use the new fsl jitter option to make sure they
+ recreate a new log after the previous one was moved. This has
+ been run-time tested.
+
+ o we added OSSP fsl support for every released package we found to
+ use syslog(3).
+
+ o OpenPKG Development: in order to make the daily maintainance
+ less error-prone and time-consuming and to check errors already
+ in advance for reducing the release engineering efforts, we
+ recently wrote the so-called "speclint" -- a program which
+ checks a large amount of syntactical and semantical aspects of
+ our RPM .spec files. The same we've now done for the
+ run-command (rc) and OSSP fsl configuration files with two
+ additional "linters" named "rclint" and "fsllint". This now
+ allows us to check mostly all aspects of our packaging input.
+ Work is now also in progress for an "rpmlint", which checks the
+ packaging output, the binary .rpm files.
+
+ o OpenPKG Development: to reduce the "line noise" in our CVS
+ repository, we've added real "mass committing" support to our
+ developer shell "openpkg-dev". This allowed us to already commit
+ many mass changes in one clean step this week. Our
+ development/packager shell was enhanced again to now provide
+ even more convinience commands for the PMOD/PSOD. OpenPKG:
+ openpkg-dev: we finished the working-off of our internal
+ "packager shell". It is now fully CVS branch aware and provides
+ lots simplified and equalized commands. This way the daily
+ PMOD/PSOD tasks and the security engineering tasks should be
+ greatly simplified and from now on cost less effort.
+
+ o OpenPKG, MySQL: after a long enough evaluation phase, we've now
+ officially moved in OpenPKG-CURRENT from MySQL 3.x to MySQL 4.x.
+ Following our general rules for dealing with versioned packages
+ (and the fact that we only want _one_ single version in each
+ release, of course), the old (MySQL-3 based) "mysql" package was
+ first merged up to 1-STABLE (for possible inclusion into OpenPKG
+ 1.3), then "mysql" was renamed to "mysql3" (in case you still
+ have to drive MySQL 3 within OpenPKG-CURRENT), "mysql4" become
+ "mysql" and "mysql4" has gone. Be aware of these changes for
+ OpenPKG-CURRENT instances
+
+ o OpenPKG: after intensive testing and fixing, we've finally
+ upgraded in OpenPKG-CURRENT to the current stable GNU C/C++
+ Compiler Suite (GCC) version 3.3. In case of any occurring
+ incompatibilities or broken packages, please respond to
+ [EMAIL PROTECTED] with details.
+
+ o OpenPKG: Request Tracker (RT): we finished the migration from
+ the Jitterbug based OpenPKG Bug Database to Request Tracker
+ (RT). For this we've added mandatory HTTPS access and the
+ bi-directional gatewaying between RT and the mailing-lists
+ openpkg-dev/openpkg-bugdb. This way, all OpenPKG related
+ requests now can be found exclusively in the OpenPKG RT and
+ you're strongly advised to give your OpenPKG feedback to us by
+ just mailing your request to [EMAIL PROTECTED]
+
+ https://rt.openpkg.org/
+ mailto:[EMAIL PROTECTED]
+
+ o OpenPKG Service: because the public PGP key servers come and go
+ (like keyserver.pgp.com) and this way do not allow us to give
+ out reasonable stable references, we finally solved the problem
+ by establishing an own OpenPGP and HKP speaking key server for
+ the OpenPKG community. Additionally, on the key server's website
+ there is a short step-by-step guideline on how to use GnuPG for
+ verifying the digital signatures on our RPM packages and
+ security advisories.
+
+ http://pgp.openpkg.org/
+ hkp://pgp.openpkg.org/
+
+ o *************************************************************************
+ ** NOTICE: Now that OpenPKG 1.3 is available, we fully drop support **
+ ** for OpenPKG 1.1. Outdated Releases are considered deprecated and no **
+ ** longer maintained in any way. We especially do no longer provide **
+ ** security updates. **
+ *************************************************************************
+
o now all issues are tracked in RT
o release extended to 400 packages
@@ .
______________________________________________________________________
The OpenPKG Project www.openpkg.org
CVS Repository Commit List [EMAIL PROTECTED]
