conflicts on pre-1.5.61 openafs-client packages since the interface
between afsd and the module has changed. openafs-client now conflicts
with openafs-modules2 and recommends openafs-modules3.
- * Change the permissions of /var/lib/openafs/local to 0700 to match
- upstream defaults. This directory contains the fssync.sock file used
- for coordination between the fileserver and the volserver, and
- commands sent to that socket are not authenticated. Linux protects
- the socket from unprivileged writes by default, but other operating
- systems do not. Upstream therefore wants this directory to be 0700
- and bosserver will complain by default if it's not. Changing the
- permissions let us drop a patch to bosserver.
* Change the default permissions of /etc/openafs/server to 0755 to match
upstream defaults, but do not change permissions on upgrade. The only
file in that directory that needs to be protected is KeyFile, which
should be mode 0600 anyway. Drop the patch to bosserver to allow more
restrictive permissions. bosserver will complain about directory
permissions after upgrade until the directory is manually changed.
- * Fix the second module control file for the standards version, section,
- and maintainer update.
- * Change the source package name of the stripped package generated by
- openafs-modules-source so that, should someone build a Debian source
- package from it, it won't have the same name as the main openafs
- source package.
* Add README.source explaining maintenance procedures and a
debian/import-upstream script to do a Git-aware merge of a new
upstream release that will allow us to cherry-pick upstream patches