#
#
# patch "INSTALL"
# from [1ce67691a7b2c99af3bdce649ce6b8d9388ef8b7]
# to [df6a35fc0a52cf22d8a971f021a173218c0554ee]
#
# patch "NEWS"
# from [0a38b76c36a4842e734564c1aae26fb9a46c2feb]
# to [61bb84d86cd4a4e3d0789b2c36c8d558ca9da2a4]
#
# patch "UPGRADE"
# from [2877096a746cf318568d418e444959797a9621f0]
# to [58cc349e2a00199c7fa8146d8f547727714e0ef3]
#
# patch "index.html"
# from [c33464c1853c2851cc73b0dcb5b5b8a35e65bea2]
# to [936c892c904592904f3cdac304e710af8ba49355]
#
# patch "releases.xml"
# from [78a371d4e633c37cf7bbc99c08be7392e4f292a2]
# to [7cfcc88eaab7b47811e0e0ab3467249945165cc3]
#
============================================================
--- INSTALL 1ce67691a7b2c99af3bdce649ce6b8d9388ef8b7
+++ INSTALL df6a35fc0a52cf22d8a971f021a173218c0554ee
@@ -33,10 +33,10 @@ 1. prerequisites:
install the following packages:
autoconf automake gettext g++ libboost-dev libz-dev
- libbotan1.8-dev libsqlite3-dev libpcre3-dev liblua5.1-0-dev
- libidn11-dev texinfo
+ libbotan-dev libsqlite3-dev libpcre3-dev liblua5.1-0-dev
+ libidn11-dev libgmp3-dev libbz2-dev texinfo
- (On etch, you may need to use libbotan1.8 from lenny.)
+ (On etch, you may need to use libbotan1.7 from lenny.)
on FreeBSD:
@@ -50,9 +50,6 @@ 1. prerequisites:
autoconf automake boost botan gettext libpcre libidn lua sqlite
zlib
- (you might need to add the "~x86" flag to dev-libs/botan, so you
- get at least version 1.6.3, we recommend using at 1.8.0 or newer)
-
on Fedora:
install the following packages:
@@ -209,40 +206,58 @@ 1. prerequisites:
15. build monotone
$ cd /c/.../monotone
- $ export PATH=/bin:$PATH
+ $ export PATH=/bin:/mingw/bin
$ autoreconf -i
- $ ./configure sqlite_LIBS=-lsqlite3
+ $ ./configure sqlite3_LIBS=-lsqlite3
$ make
on Windows (using Cygwin):
Monotone needs the following packages to compile:
+ (newer releases are usually ok)
Runtime requirements:
- cygwin-1.5.24 or newer
- libiconv2-1.11 or newer
- libintl8-0.15 or newer
- zlib-1.2.3-2 or newer
+ cygwin-1.7.0-60
+ libgcc1-4.3.2-2
+ libidn11-1.9-1
+ libintl8-0.17-11
+ libpcre0-7.9-1
+ libsqlite3_0-3.6.2-1
+ libstdc++6-4.3.2-2
+ lua-5.1.4-11
+ zlib0-1.2.3-10
Build requirements:
- gcc-3.4.4 or newer
- binutils-20050610 or newer
- boost-devel-1.33.1 or newer
- gettext-0.14.5 or newer
- zlib-1.2.3-2 or newer
- perl-5.8.7 or newer
- sqlite3-3.6.2-1 or newer
- libidn-devel-1.9-1 or newer
- lua-5.1.4-1 or newer (*)
- botan-1.8.0-1 or newer (*)
+ gcc4-4.3.2
+ binutils-2.19.51
+ boost-devel-1.33.1
+ libsqlite3-devel-3.6.2
+ libidn-devel-1.9
+ gettext-0.17
+ zlib-1.2.3
+ perl-5.10.0
+ botan-1.8.2
- currently every prerequisite is avaialble as packages except
- lua and botan; an official Cygwin package for monotone and
- all its dependencies will be available soon after release
+ currently every prerequisite is available as packages except
+ lua and botan which are only available in Cygwin 1.7;
+ an official Cygwin package for monotone and all its
+ dependencies is usually available soon after release.
- the following is needed to succesfulyl configure
+ The following is needed to succesfully configure:
CXXFLAGS+="-I/usr/include/boost-1_33_1/"
+ Easiest way to create a Cygwin package is using cygport
+ (which must be installed separately as a Cygwin package)
+ and upgrade the previous version cygport file; you can fetch
+ latest version from the maintainer's own repository:
+
+ % mtn pull lapo.it it.lapo.cygwin.ports
+ % mtn checkout -b it.lapo.cygwin.ports cygwin
+ % cd cygwin
+ % mtn mv monotone-$OLD-1.cygport monotone-$NEW-1.cygport
+ proceed to change or fix the port and/or the patch as needed
+ % cygport monotone-$NEW-1 all
+
on other systems:
check your system package repository, you may need to
============================================================
--- NEWS 0a38b76c36a4842e734564c1aae26fb9a46c2feb
+++ NEWS 61bb84d86cd4a4e3d0789b2c36c8d558ca9da2a4
@@ -1,3 +1,100 @@
+Sun Jan 17 21:40:35 UTC 2010
+
+ 0.46 release.
+
+ Changes
+
+ - "automate stdio" (and "automate remote_stdio", see below)
+ use separate streams to encode out-of-band information like
+ informational messages, warnings or tickers. A special
+ "header" section has been added to the standard output to
+ identify future stdio version changes. The error codes used
+ in the output of both stdio and remote_stdio, have also
+ slightly changed: errors which are the result of a wrong
+ call (unknown command, invalid options, parsing errors, ...)
+ are returned with code 1, while errors which happened while
+ the actual command executed are returned with code 2. Error
+ codes are no longer echoed with every packet, but only as
+ the payload of the final 'l' ("last") packet.
+
+ Please consult the manual section "mtn automate stdio" for a
+ detailed description of the new format.
+
+ - The 'heads' command should be significantly faster now (not
+ that it was particularly slow before). This probably isn't
+ terribly noticable unless you're in the habit of using "h:*"
+ (heads of all branches) as a selector, it's primarily meant
+ to enable future changes that will depend on fast 'heads'.
+
+ The database schema has been changed, so you will need to
+ run 'mtn db migrate' (preferably after making a backup copy
+ of your db).
+
+ - the 'status' command now includes the current (to be committed)
+ revision number and will indicate when the branch option in
+ _MTN/options has been changed and does not match one of the
+ revision's parent branches.
+
+ - Cert labels in the output of the 'log' command are now
+ localized.
+
+ New features
+
+ - There's a new command "automate remote_stdio" that makes it
+ possible to execute automate commands on a remote server
+ (for example, to permit a single database to be used both
+ for serving netsync connections and for running a viewmtn
+ instance). This requires that the server be running monotone
+ 0.46 or later. Access control on the server uses a new lua
+ hook "get_remote_automate_permitted(identity, command_line,
+ options)".
+
+ - There's also a new command "automate remote" that's very much
+ the same, but executes only a single command and does not
+ stdio-encode the output.
+
+ - A new 'bisect' command has been added to allow searching for a
+ specific revision within a range of revisions. This can be useful for
+ locating the exact revision that broke something or removed a
+ particular feature.
+
+ - Three new commands - 'push', 'pull' and 'sync' - have been added
+ to the automation interface. They work just as their non-automate
+ counterparts.
+
+ - The global option '--timestamps' has been added which prefixes
+ the current local timestamp before diagnostic messages such as
+ warnings, progress messages, errors and tickers. For example,
+ this option can be used to log the date and time when clients
+ connect to a monotone server.
+
+ Bugs fixed
+
+ - A regression from 0.45's key migration prevented the proper
+ output of the `committer` field in 'git_export'.
+
+ - 'db info --full' no longer crashes when executed on a database
+ with only one revision.
+
+ - The mtn_automate Lua function which can be used for custom
+ commands now properly handles binary data.
+
+ - `db info` now returns a correct byte count for certs again.
+
+ - If a public key was read in via the `read` or
+ `automate read_packets`, an invariant was triggered if the
+ key was already existing in the database. This has been fixed.
+
+ - `annotate` no longer crashes if the annotated file is empty.
+
+ Other
+
+ - Added the script of the Lua-based contributed Monotone
+ extension command "mtn remote_export" to contrib/command/
+ with which a remote revision can be exported locally without
+ having to fetch all of the history before.
+
+
Fri Sep 11 20:50:00 UTC 2009
0.45 release.
============================================================
--- UPGRADE 2877096a746cf318568d418e444959797a9621f0
+++ UPGRADE 58cc349e2a00199c7fa8146d8f547727714e0ef3
@@ -1,4 +1,4 @@
-upgrading monotone to 0.45
+upgrading monotone to 0.46
==========================
How to read this file:
@@ -16,6 +16,10 @@ If you are upgrading from:
will be described there, not here.
If you are upgrading from:
+ - 0.45 or earlier: The database format has changed. You must run
+ (after remembering to take a backup copy):
+ $ mtn -d mydb.mtn db migrate
+ on each of your databases.
- 0.44 or earlier: The database format has changed. You must run
(after remembering to take a backup copy):
$ mtn -d mydb.mtn db migrate
============================================================
--- index.html c33464c1853c2851cc73b0dcb5b5b8a35e65bea2
+++ index.html 936c892c904592904f3cdac304e710af8ba49355
@@ -35,7 +35,7 @@
============================================================
--- releases.xml 78a371d4e633c37cf7bbc99c08be7392e4f292a2
+++ releases.xml 7cfcc88eaab7b47811e0e0ab3467249945165cc3
@@ -5,8 +5,116 @@
http://monotone.ca/releases.xml
monotone releases with links to the sources.en
- Fri, 11 Sep 2009 20:50:00 +0000
+ Sun, 17 Jan 2010 21:40:00 +0000
+ monotone 0.46 released
+
+Changes
+
+
+
"automate stdio" (and "automate remote_stdio", see below)
+ use separate streams to encode out-of-band information like
+ informational messages, warnings or tickers. A special
+ "header" section has been added to the standard output to
+ identify future stdio version changes. The error codes used
+ in the output of both stdio and remote_stdio, have also
+ slightly changed: errors which are the result of a wrong
+ call (unknown command, invalid options, parsing errors, ...)
+ are returned with code 1, while errors which happened while
+ the actual command executed are returned with code 2. Error
+ codes are no longer echoed with every packet, but only as
+ the payload of the final 'l' ("last") packet.
+
+ Please consult the manual section "mtn automate stdio" for a
+ detailed description of the new format.
+
+
The 'heads' command should be significantly faster now (not
+ that it was particularly slow before). This probably isn't
+ terribly noticable unless you're in the habit of using "h:*"
+ (heads of all branches) as a selector, it's primarily meant
+ to enable future changes that will depend on fast 'heads'.
+
+ The database schema has been changed, so you will need to
+ run 'mtn db migrate' (preferably after making a backup copy
+ of your db).
+
+
the 'status' command now includes the current (to be committed)
+ revision number and will indicate when the branch option in
+ _MTN/options has been changed and does not match one of the
+ revision's parent branches.
+
+
Cert labels in the output of the 'log' command are now
+ localized.
+
+
+
New features
+
+
+
There's a new command "automate remote_stdio" that makes it
+ possible to execute automate commands on a remote server
+ (for example, to permit a single database to be used both
+ for serving netsync connections and for running a viewmtn
+ instance). This requires that the server be running monotone
+ 0.46 or later. Access control on the server uses a new lua
+ hook "get_remote_automate_permitted(identity, command_line,
+ options)".
+
+
There's also a new command "automate remote" that's very much
+ the same, but executes only a single command and does not
+ stdio-encode the output.
+
+
A new 'bisect' command has been added to allow searching for a
+ specific revision within a range of revisions. This can be useful for
+ locating the exact revision that broke something or removed a
+ particular feature.
+
+
Three new commands - 'push', 'pull' and 'sync' - have been added
+ to the automation interface. They work just as their non-automate
+ counterparts.
+
+
The global option '--timestamps' has been added which prefixes
+ the current local timestamp before diagnostic messages such as
+ warnings, progress messages, errors and tickers. For example,
+ this option can be used to log the date and time when clients
+ connect to a monotone server.
+
+
+
Bugs fixed
+
+
+
A regression from 0.45's key migration prevented the proper
+ output of the `committer` field in 'git_export'.
+
+
'db info --full' no longer crashes when executed on a database
+ with only one revision.
+
+
The mtn_automate Lua function which can be used for custom
+ commands now properly handles binary data.
+
+
`db info` now returns a correct byte count for certs again.
+
+
If a public key was read in via the `read` or
+ `automate read_packets`, an invariant was triggered if the
+ key was already existing in the database. This has been fixed.
+
+
`annotate` no longer crashes if the annotated file is empty.
+
+
+
Other
+
+
+
Added the script of the Lua-based contributed Monotone
+ extension command "mtn remote_export" to contrib/command/
+ with which a remote revision can be exported locally without
+ having to fetch all of the history before.
+
+]]>
+
+ Sun, 17 Jan 2010 21:40:00 +0000
+
+
+ monotone 0.45 released