Hi Myself and a colleague seeing a bug with FC4 (binary* and compiled from source) using 0.22:
$> monotone --db=my.db co --branch=default ... lots of lines... monotone: binding 1 parameters for SELECT id FROM files WHERE id = ? monotone: binding 1 with value '99c97df73594ad6da25efa38dbd3ecbe62236e75' monotone: binding 1 parameters for SELECT data FROM files WHERE id = ? monotone: binding 1 with value '99c97df73594ad6da25efa38dbd3ecbe62236e75' monotone: version cache expiring 2efe1d7ce337d5316d4c604068ce1feffb352fad monotone: version cache expiring 50cd2617410d3e05c20056392a2aa1f7c4193044 monotone: version cache expiring 6ee923712be02fb51081a53a327df24135f6042e monotone: work path is MT/work monotone: attribute map path is .mt-attrs monotone: unix/process.cc:61: usage constraint 'N(fd != -1)' violated terminate called after throwing an instance of 'informative_failure' monotone: fatal: signal: SIGABRT (application abort requested) monotone: this is almost certainly a bug in monotone. monotone: please send this error message, the output of 'monotone --full-version', monotone: and a description of what you were doing to [EMAIL PROTECTED]: discarding debug log (maybe you want --debug or --dump?) The error doesn't occur with 0.21. Any ideas? Thanks! Conrad * The link on the monotone web front page to the FC4 binary rpm is broken as well: http://www.venge.net/monotone/downloads/monotone-0.22-1.i386.rpm should be http://www.venge.net/monotone/downloads/monotone-0.22-1_fc4.i386.rpm On Tue, 2005-08-09 at 01:53 -0700, Nathaniel Smith wrote: > I'm please to announce that monotone 0.22 is now available at > http://venge.net/monotone/. As always, more binary packages will > appear mysteriously from the ether over the next day or two. > > The biggest change in this release is the switch of our underlying > crypto library from crypto++ to botan. This should have no > user-visible effects, but let us know if you see anything weird. > > Otherwise, this is mostly a bug fix and smoothing-things-out release. > Some error messages are a little more informative, 'merge' and > 'propagate' now take an '--lca' option as a convenience to avoid > explicit_merge until we get merging fixed properly, etc. > > The biggest change is that the get_netsync_anonymous_read_permitted > and get_netsync_read_permitted hooks have been merged; experience > showed them to be very confusing. When upgrading to 0.22, server > operators should: > -- remove get_netsync_anonymous_read_permitted > -- if necessary, adjust get_netsync_read_permitted to take into > account the possibility of receiving the Lua special value > 'nil' as a key id. > > If you allow anonymous reads, you probably have: > function get_netsync_anonymous_read_permitted(branch) > return true > end > function get_netsync_read_permitted(branch, keyid) > return true > end > Just make it: > function get_netsync_read_permitted(branch, keyid) > return true > end > > If you don't, you probably have: > function get_netsync_anonymous_read_permitted(branch) > return false > end > function get_netsync_read_permitted(branch, keyid) > <conditionals here> > return false > end > Just make this: > function get_netsync_read_permitted(keyid) > <conditionals here> > return false > end > Or, to be extra certain: > function get_netsync_read_permitted(branch, keyid) > if keyid == nil then return false end > <conditionals here> > return false > end > > (Of course, if you're upgrading from 0.20, you also need to delete the > branch argument from you get_netsync_write_permitted hook or you will > get mysterious permission denied messages.) > > Enjoy, > -- Nathaniel > > _______________________________________________ > Monotone-devel mailing list > Monotone-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/monotone-devel -- Conrad Steenberg <[EMAIL PROTECTED]> California Institute of technology
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel