Fix case where OWN_DIRS_PERMS obviously was intended instead of OWN_DIRS.
Also use ${REAL_ROOT_USER}:${REAL_ROOT_GROUP} instead of hardcoding
root:wheel.
Bump PKGREVISION for fixes that changed binary package.
Problems found with existing digests:
Package memconf distfile memconf-2.16/memconf.gz
b6f4b736cac388dddc5070670351cf7262aba048 [recorded]
95748686a5ad8144232f4d4abc9bf052721a196f [calculated]
Problems found locating distfiles:
Package dc-tools: missing distfile dc-tools/abs0-dc-burn-netbsd-1.5-0-gae55ec9
Package ipw-firmware: missing distfile ipw2100-fw-1.2.tgz
Package iwi-firmware: missing distfile ipw2200-fw-2.3.tgz
Package nvnet: missing distfile nvnet-netbsd-src-20050620.tgz
Package syslog-ng: missing distfile syslog-ng-3.7.2.tar.gz
Otherwise, existing SHA1 digests verified and found to be the same on
the machine holding the existing distfiles (morden). All existing
SHA1 digests retained for now as an audit trail.
Released on 2013-07-28.
* Sources migrated to a GitHub project from the previous copy in
the pkgsrc repository. sysupgrade is now a first-class package and
includes a traditional build system based on automake and autoconf.
* Moved the sysupgrade script from bin to sbin.
- ftp(1) in NetBSD 1.5.2 does not support using -R on files that do not
exist yet. Avoid using this option unless necessary.
- httpd(8) in NetBSD 1.5.2 does not support the -P option. Skip the http
test unless this option is present, as otherwise we cannot easily kill
the spawned httpd instance on a test failure.
- Use netbsd-*.gz files to install the kernel rather than kern-*.tgz sets.
This lets sysupgrade work in conjunction with the "releasekernel" target
of build.sh, as this generates the former instead of the latter.
- Preserve timestamps of the kernel when backing it up as onetbsd.
- Fix some tests to not rely on the current state of the system (the cache
directory and the autodetection of KERNEL).
sysupgrade is a script to automate NetBSD system upgrades. sysupgrade
works by first fetching distribution sets from a specified site or local
directory, then by upgrading the system using such distribution sets and
later by ensuring that the system configuration is up to date. All the
process is controlled by a configuration file, and the defaults should
suit the most common NetBSD upgrades.
sysupgrade can be used to perform upgrades across different system major
and/or minor versions, and it can also be used to track a stable or
development branch from the CVS repository.
sysbuild is the perfect companion to sysupgrade in those cases where you
want to roll your own binaries: both utilities share a very similar
command-line and configuration interface, and the default configuration
files provide examples on how to integrate one with the other.
A few notes about the import:
Right after I submitted sysbuild, I was pointed at etcmanage and its
scripts to build and upgrade NetBSD. I am sending this anyway because
1) it matches sysbuild's behavior closely, 2) it has a detailed manual
page, 3) it has tests... and, well, 4) I had already written most of it
at that time and didn't want to throw it away!
The config and utils modules in this import are a duplicate of the code
in sysbuild, with a few tweaks. This is really bad and the code should
be deduplicated somehow. I'm not sure what the best way of doing so is
and can only think about introducing a common base package with the
shared code (which brings its own problems).
I have tested this to upgrade both -current and 6.0_BETA2 to newer
snapshots, both from local and remote release files.
