up2us release notes $Id: README,v 1.2 2003/02/25 20:44:45 tomj Exp $ up2us-1.0-5 ----------- The first release that can be obtained automatically via zero.wps.com's Current server using up2us. Please download release 4 manually and install, and run it; it should update to release 5 for you. up2us-1.0-4 ----------- With this release up2us works as advertised. Few visible changes from rel 3, but I've solved the bootstrap problem: up2us and/or up2date can now be used to update up2us. (The mechanism is simple but has some subtleties; the modules are stored in a version-release named subdir in /usr/share, and the next version knows how to delete the previous version.) That, plus the included distribution of ZERO's SSL certificate, means that once you install release 4 manually, you can obtain subsequent versions via up2us itself. (I created release 5 for this purpose. Release 5 is otherwise identical to release 4.) up2us-1.0-3 ----------- It behaves more like a real program; input error-checking on ADD repository. --version and --help supported. Minor problems with the RPM fixed. Don't forget to use rpm -U to upgrade. up2us-1.0-2 ----------- The security installation shoudl now be correct; rpm -i should correctly install the package, placing the modules and executable in the right spot, install the PAM stuff and the symlink to consolehelper. Same crappy program as 1.0-1 however. That's next. up2us-1.0-1 ----------- Almost working. It can actually be used to do updates, and you can add a repository, but it does no error checking on input (in the works) and is reasonably ugly. It does however do some things nciely, and silently. It does crash recovery quite well (eg. it has to mess about with up2date config; up2us will restore original files upon later re-run). It handles files cleanly. Modules and config are in correct, final places. BIG OOPS: I don't have consolehelper working yet, so (1) the executable isn't in the path and (2) you have to have root priv to start it. The RPM installs in the normal manner. Execute by: /usr/share/up2us/up2us Version 0.0 ----------- Barely works. Is cosmetically unpleasant. Most of the work went into Gtk stuff (enabling buttons only when correct conditions exist, etc). THIS IS A TEST HACK and not even pre-release. It MODIFIES the up2date config file, /etc/sysconfig/rhn/up2date; it is very easy to befuddle this version into leaving a non-RedHat-stock version of that config file. (The scheme to prevent this is not coded yet.) The temporary fix for this is that up2us keeps a virgin copy of the original up2date config, in a configurable place. This is a test hack and will go away with subsequent versions. See the up2us.conf file, below. Ignore error: Argument "(FOO)" isn't numeric in subroutine entry at /usr/lib/perl5/5.6.1/i386-linux/POSIX.pm line 38. BEFORE YOU START UP2US test version: sudo -s (Eventually it will use consolehelper to make sure you start as root (and to work with PAM) but right now it simply fails in silly ways if you're not root priv.) run up2date manually. Cancel at first window is OK. (up2us doesn't deal with migrating changes from rhn_register yet; up2daet will rebuild the /etc/sysconfig/rhn/up2date config file). Version 0.0 misfeatures, warts, bugs HELP will put up a help window that will scroll to the appropriate place in the help file for that main screen. Not implemented (and the window is UG-LY). SETUP: ADD doesn't work yet; it's kind of a big deal to be done right, and the next project. REMOVE works. Can't remove RedHat, as it's part of the base config. Umm, if you delete all the repositories, untar again to get a fresh copy of the repository.config file. CONFIGURATION: up2us.conf General up2us configuration. One temporary crock: orig-up2date-config= ./up2date.orig When first run up2us copies the up2date config file here to make a copy for error recovery. If you munge things feel free to copy this back to /etc/sysconfig/rhn/up2date. repository.conf This is the repository data. It does not include package info; that will be put in /var when the time comes.