[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Monotone-devel] [ANNOUNCE] monotone 1.0 released
From: |
Support |
Subject: |
Re: [Monotone-devel] [ANNOUNCE] monotone 1.0 released |
Date: |
Sun, 27 Mar 2011 18:30:08 +0100 |
User-agent: |
SquirrelMail |
Hi Richard,
No I hadn't at the time as it had the feeling of a wild goose chase
about it (I never had issues with your pre-built binaries and thought
that I might be doing something silly). Anyway having had a slightly
closer look I can't see anything obviously wrong with the build.
I have now raised a ticket (156) with all the details that I could
think of in it.
Cheers,
Tony.
> Have you issued a bug report on this?
>
> Cheers,
> Richard
>
> In message <address@hidden> on Sat, 26 Mar 2011 13:39:42
> +0000, CooSoft Support <address@hidden> said:
>
> support> I tried building from source and my binary went bang (illegal
> support> instruction). This is what has happened since about 0.48, I'm
> sure I'm
> support> doing something wrong but it's not obvious (dependencies are
> met or so
> support> it seems). I normally download the binary from the site now.
> Any idea
> support> when the mtn-1.00-linux-x86.bz2 file will be ready for
> downloading?
> support>
> support> Cheers,
> support>
> support> Tony.
> support> Richard Levitte wrote:
> support> > Monotone 1.0 is out!
> support> >
> support> > We, the monotone developers, are very proud to release version
> 1.0 of
> support> > our distributed version control system.
> support> >
> support> > This is a major milestone, and a lot of effort has been made to
> make
> support> > this release a reality. It contains quite a number of bug
> fixes,
> support> > changes and new features. The tarball can be downloaded here
> [0],
> support> > binaries are posted on the same page as they come in.
> support> >
> support> > Following is the relevant part of the NEWS [1] file:
> support> >
> support> > Sat Mar 26 10:53:47 UTC 2011
> support> >
> support> > 1.0 release.
> support> >
> support> > Changes
> support> >
> support> > - The database scheme was changed; please execute 'mtn
> db migrate'
> support> > on all your local and remote databases.
> support> >
> support> > - In 'mtn conflicts resolve_first interactive', the
> result
> support> > file name now defaults to
> _MTN/resolutions/<left_path>.
> support> > (fixes monotone issue 103)
> support> >
> support> > - The French monotone translation has been updated and
> is
> support> > now part of the main distribution again. Many thanks
> to
> support> > Steve Petruzzello <address@hidden> for the
> outstanding
> support> > work!
> support> >
> support> > - get_netsync_(read|write)_permitted have been extended
> to not
> support> > only read the files read-permissions and
> write-permissions,
> support> > but also the files in the subdirectories
> read-permissions.d
> support> > and write-permissions.d.
> support> >
> support> > - monotone now also tracks the workspaces of databases
> which
> support> > do not reside in a "managed" location.
> support> >
> support> > - automate now resets the locale to "POSIX" internally.
> This
> support> > means that all scripts can expect the same
> untranslated
> support> > messages from mtn automate, regardless of the locale
> of the
> support> > calling process.
> support> >
> support> > - The hook 'get_netsync_key' has been split up into two
> separate
> support> > hooks, one for client usage
> ('get_netsync_client_key', with
> support> > the same arguments as the original 'get_netsync_key')
> and one
> support> > for server usage ('get_netsync_server_key', with a
> single table
> support> > argument containing all the given '--bind' options).
> Please
> support> > review your custom hooks accordingly.
> support> >
> support> > - Short options ('-b', '-d', ...) are no longer
> completed. This
> support> > fixes an invariant failure originating from wrong
> option usage.
> support> > (closes monotone issue 141)
> support> >
> support> > New Features
> support> >
> support> > - 'mtn conflicts store' now outputs a count of the
> conflicts,
> support> > and the name of the conflicts file.
> support> > (fixes monotone issue 108)
> support> >
> support> > - New 'mtn list workspaces' command which outputs all
> the
> support> > known workspaces for a specific database.
> support> > (closes monotone issue 129)
> support> >
> support> > Bugs fixed
> support> >
> support> > - The internal line merger will actually preserve your
> line
> support> > endings now, instead of changing everything to "\n".
> support> >
> support> > - Improved the help and fixed the argument indexing in
> support> > 'conflicts resolve_first' (fixes monotone issue 101)
> support> >
> support> > - A regression from 0.48 prevented monotone from
> ordering the
> support> > diff output of individual files alphabetically.
> support> > (fixes monotone issue 102)
> support> >
> support> > - 'mtn privkey' did not recognize private keys solely
> available
> support> > in the key store. This has been fixed.
> support> >
> support> > - Added compatibility with Botan 1.9.9 and newer.
> support> > (fixes monotone issue 104)
> support> >
> support> > - 'mtn pull' and 'mtn sync' would always say that your
> workspace
> support> > has not been updated. Now, it only does that when
> you used
> support> > the '--update' option and there were no updates.
> support> > (fixes monotone issue 106)
> support> >
> support> > - 'mtn automate remote' and 'mtn automate remote_stdio'
> now use
> support> > a given database given by an alias to read, store and
> validate
> support> > a remote server's key fingerprint (fixes monotone
> issue 95)
> support> >
> support> > - monotone gives a proper error message now if a
> netsync URI
> support> > with the 'mtn' scheme misses the required host part
> support> > (fixes monotone issue 110)
> support> >
> support> > - Whenever a binary file was removed and one would try
> to get
> support> > a diff using mtn diff, it would report that
> "/dev/null is
> support> > binary". This has been changed to it reports the
> actual
> support> > name of the removed file instead.
> support> > (fixes monotone issue 111)
> support> >
> support> > - monotone no longer wrongly falls back on a :memory:
> database
> support> > when no database option is given. It also prints out
> an
> support> > informational message for commands like 'setup' and
> 'clone'
> support> > that fall back on the configured default database,
> again,
> support> > if no database is specified for these commands.
> support> > (fixes monotone issue 113)
> support> >
> support> > - If 'mtn serve' is called with one or more '--bind'
> options,
> support> > then the arguments to these options can now be
> specified
> support> > again as follows:
> support> >
> support> > '<ip-or-host>'
> support> > to listen to IP or host on the default port
> support> > '<ip-or-host>:<port>'
> support> > to listen to IP or host on the specified port
> - or
> support> > ':<port>'
> support> > to listen on all interfaces on the specified
> port
> support> >
> support> > (fixes monotone issue 119)
> support> >
> support> > - monotone no longer enforces ".mtn" as file extension
> for
> support> > managed databases. A new Lua hook,
> get_default_database_glob(),
> support> > is used instead to determine a pattern which matches
> support> > accepted database filenames and this pattern by
> default
> support> > accept files ending with both, ".mtn" and ".db".
> support> > (fixes monotone issue 128)
> support> >
> support> > - monotone now gives a proper error message when an
> incomplete
> support> > or partial identifier contains non-hex digits.
> support> > (fixes monotone issue 143)
> support> >
> support> > - Performance of "mtn ls changed" has been improved and
> is now
> support> > comparable to "mtn status". (fixes monotone issue
> 120)
> support> >
> support> > Internal
> support> >
> support> > - The source tree has been reorganized. Sources, tests
> and
> support> > documentation now reside in specific directories and
> many
> support> > smaller improvements in terms of source code cleanup,
> support> > developer documentation and general build
> infrastructure
> support> > accompany this big change.
> support> >
> support> > Other
> support> >
> support> > - Added a new directory extra/, which contains monotone
> hooks and
> support> > related scripts that have been shown to work. Most
> of these get
> support> > installed, usually somewhere under
> $(prefix)/share/monotone.
> support> > Please read extra/README for further information.
> support> >
> support> > - Added the mtn-cleanup Perl script that returns a
> workspace to its
> support> > pristine state with the minimum amount of change.
> This script is
> support> > in the extra/bin directory.
> support> >
> support> >
> support> > Thank you all for your ongoing support!
> support> >
> support> > On behalf of the monotone team,
> support> > Richard Levitte
> support> >
> support> > [0] http://www.monotone.ca/downloads.php
> support> > [1] http://www.monotone.ca/NEWS
> support> >
> support> > --
> support> > Richard Levitte address@hidden
> support> >
> http://richard.levitte.org/
> support> >
> support> > "Life is a tremendous celebration - and I'm invited!"
> support> > -- from a friend's blog, translated from Swedish
> support> >
> ------------------------------------------------------------------------
> support> >
> support> > _______________________________________________
> support> > Monotone-devel mailing list
> support> > address@hidden
> support> > http://lists.nongnu.org/mailman/listinfo/monotone-devel
> support> >
> support>
>
> _______________________________________________
> Monotone-devel mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/monotone-devel
>