Log message:
Update to 1.0: depend on monotone-1.0.

Log message:
Update monotone{,-el,-server} to 0.99.1:

Bugs fixed

- monotone crashed on x86_64 when a netsync action required
  the parsing of an URL. This has been fixed.
  (closes monotone issue 100)

- monotone's automation interface version was reported wrongly
  as 12.1, where it should have been 13.0.

Log message:
Update to 0.99: depend on monotone 0.99.

Log message:
sync some more occurences of the mtn version

Log message:
update pkgname to sync with mtn base pkg, no changes

Log message:
Remove distinfo.  It is unused and, at this point outdated, which is causing
the build of this package to fail.

Log message:
I actually forgot to bump the dependency... do it now.

Log message:
Update to 0.48: depend on monotone-0.48.

Log message:
Update to 0.47: use the 0.47 distfile and depend on monotone 0.47.

Log message:
Full rewrite of the monotone-server package:

- Delete the monotone-server-init script.

- Modify the monotone rc.d(8) script to provide extra commands such as
  'init', 'genkey' and 'read' to manipulate the server.  These are not
  interactive, but allow the same level of customization as the previous
  script.  Inspired by how the monotone init.d script from Fedora works.

- Delete the need of an rc.conf script in the pkg_sysconfdir of this
  package.  The settings previously stored there are now automatically
  discovered.

- Fully automated creation of a server key: no more need to create a
  passphrase by hand, memorize it, and stick it on a configuration file
  to never look at it again.

- The log file is now placed where it belongs: in varbase/log.

- Addition of a monotone-server(7) manpage explaining the whole setup
  process and pointers to the server files.

Note: upgrading from a previous version of the package will require manual
intervention if the rc.d script in /etc/rc.d is replaced.  However, I
really doubt anyone is using this package so I didn't want to go through
the trouble of implementing a migration procedure.  I've added a note to
the MESSAGE, though, asking users to contact me if required.