# # # add_file "debian/NEWS" # content [3ce4f7b180b5ea6ef694d79490bf3a452ba539be] # # patch "ChangeLog" # from [b3c858995b5a3059cd2e54adc2cd6acf22f70994] # to [583ce8666abd871071e00cf3631b8b993ba61e40] # # patch "debian/changelog" # from [0a4e17484859889c9037f27a2e9d2771b89683c5] # to [0a516555a6eae09b4c104be84e5509847a7e0013] # # patch "debian/monotone-server.postinst" # from [03a81dce45863c6ae132d33cafb149e156bc09e9] # to [d0791ab97df17473409712e09148d3c4a4ee212f] # ============================================================ --- debian/NEWS 3ce4f7b180b5ea6ef694d79490bf3a452ba539be +++ debian/NEWS 3ce4f7b180b5ea6ef694d79490bf3a452ba539be @@ -0,0 +1,55 @@ +monotone (0.31-90.1) unstable; urgency=low + + * Another efficiency change. You need to do the following on each + of your databases (except for the server database handled by the + monotone-server package, for which this is done automatically): + + mtn db migrate + # ... possibly other commands, depending on how old your previous + # mtn version was + mtn db regenerate_caches + + This does NOT affect remote participants of your projects, the + changes are only local. + + -- Richard Levitte Mon, 13 Nov 2006 22:56:10 +0100 + +monotone (0.30-0.1) unstable; urgency=low + + * Efficiency changes have been implemented, which changes the rosters + (and internal file description structure). It means that you will + have to do the following on each of your databases (except for the + server database handled by the monotone-server package, for which + this is done automatically): + + mtn db migrate + # ... possibly other commands, depending on how old your previous + # mtn version was + mtn db regenerate_rosters + + This does NOT affect remote participants of your projects, the + changes are only local. + + -- Richard Levitte Thu, 7 Sep 2006 05:15:43 +0200 + +monotone (0.30-0.1) unstable; urgency=low + + * [this is copied from the normal monotone NEWS file] + + In this release, there is a minor change to the format of the + data stored in the bookkeeping directory "_MTN". You must run + the command "mtn migrate_workspace" in all your existing + workspaces before you can use them with this version of + monotone; once you have done this, you will not be able to use + those workspaces with older versions of monotone. Nothing + terrible will happen if you try to use an old workspace + without migrating it; you'll just get an error message. + + This change makes it possible for a workspace to have more + than one parent revision, which will enable a number of + long-wanted features. Those features are not yet complete, + but we do not expect to have to change formats again to + support them. + + -- Richard Levitte Tue, 5 Sep 2006 08:18:34 +0200 + ============================================================ --- ChangeLog b3c858995b5a3059cd2e54adc2cd6acf22f70994 +++ ChangeLog 583ce8666abd871071e00cf3631b8b993ba61e40 @@ -1,3 +1,18 @@ +2006-11-14 Richard Levitte + + NOTE: I bumped the Debian version number to 0.31-90.1 in this + change so needed upgrades of the monotone-server package would + get through easily. I'm regarding that as a very early pre- + release of 0.32. Debian maintainers should still release 0.31 + the normal way (updating to the monotone-0.31 tag) and insert + their entry in debian/changelog directly above the 0.31-0.1 entry. + * debian/NEWS: Added to provide information on important changes + to Debian users. + * debian/changelog: Added an entry for 0.31-90.1 + * debian/monotone-server.postinst: Changed to provide automatic + upgrade using 'mtn db regenerate_caches" if the previous monotone + version is less than 0.31-90.1. + 2006-11-13 Thomas Moschny * cmd_diff_log.cc (CMD(log)): Fix-ups from last propagate nvm -> ============================================================ --- debian/changelog 0a4e17484859889c9037f27a2e9d2771b89683c5 +++ debian/changelog 0a516555a6eae09b4c104be84e5509847a7e0013 @@ -1,3 +1,11 @@ +monotone (0.31-90.1) unstable; urgency=low + + * Pre-0.32 "release", serving as a marker for a new infrastructure which + has been merged into mainline and that requires database upgrades, + which is reflected in monotone-server.postinst. + + -- Richard Levitte Mon, 13 Nov 2006 23:50:45 +0100 + monotone (0.31-0.1) unstable; urgency=low * New upstream release. ============================================================ --- debian/monotone-server.postinst 03a81dce45863c6ae132d33cafb149e156bc09e9 +++ debian/monotone-server.postinst d0791ab97df17473409712e09148d3c4a4ee212f @@ -40,7 +40,7 @@ function monotone_migrate () function monotone_migrate () { - if dpkg --compare-versions "$MTN_VERSION" lt "0.30"; then + if dpkg --compare-versions "$MTN_VERSION" lt "0.31-90.1"; then # upgradable version of monotone echo "Attempting to migrate monotone database..." >&2 echo "A backup named '`basename $MTN_DB~`' will be created in $MTN_HOME." >&2 @@ -83,15 +83,15 @@ function monotone_rosterify () fi } -function monotone_regenerate_rosters () +function monotone_regenerate_caches () { - if dpkg --compare-versions "$MTN_VERSION" lt "0.30"; then - # now we need to regenerate rosters - echo "Attempting to regenerate rosters..." >&2 + if dpkg --compare-versions "$MTN_VERSION" lt "0.31-90.1"; then + # now we need to regenerate caches + echo "Attempting to regenerate caches..." >&2 - if $MTN --db=$MTN_DB db regenerate_rosters --rcfile=$MTN_CONFDIR/hooks.lua \ + if $MTN --db=$MTN_DB db regenerate_caches --rcfile=$MTN_CONFDIR/hooks.lua \ --norc --keydir=$MTN_KEYDIR --confdir=$MTN_CONFDIR >&2; then - echo "Rosters successfully regenerated." >&2 + echo "Caches successfully regenerated." >&2 /bin/true else echo "*** Error regenerating roster. ***" >&2 @@ -188,7 +188,7 @@ case "$1" in monotone_check_minimum_previous_version && \ monotone_migrate && \ monotone_rosterify && \ - monotone_regenerate_rosters + monotone_regenerate_caches set -e fi