http://blog.gmane.org/gmane.comp.version-control.monotone.devel hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://comments.gmane.org/gmane.comp.version-control.monotone.devel/19391 <pre>Is there a reason for usher to keep a database locked after the netsync is finished? I just sync'd from my laptop to my server using usher; a subsequent attempt to checkout on the server (witout usher, of course) failed because the database was locked. </pre> Hendrik Boom 2012-05-25T15:59:51 http://comments.gmane.org/gmane.comp.version-control.monotone.devel/19389 <pre>Docs for `mtn db load` are unclear to me. http://www.monotone.ca/docs/Database.html says: OK, fine, but how do you create a database without `mtn db init`? Many thanks for your help! ./ddd Background / context: I'm trying to fix a database for which `mtn db check` reports: -- "Why, oh why, didn't I take the *blue* pill?" </pre> Douglas Dickinson 2012-05-22T02:44:52 http://comments.gmane.org/gmane.comp.version-control.monotone.devel/19386 <pre>Hello, A new issue has been created: 209 - support drop/modified conflict Project: monotone Status: New Reported by: Stephen Leake Labels: Type:Incorrect Behavior Priority:Medium Description: Steps to reproduce the problem: ------------------------------- 1. create two heads, one with file_a modified, one with file_a dropped 2. merge Expected result: ---------------- merge reports a drop/modified conflict Actual results: --------------- warning about modifications being lost due to drop Output of `mtn version --full`: ------------------------------- 1.0 -- Issue: https://code.monotone.ca/p/monotone/issues/209/ </pre> code< at >monotone.ca 2012-05-14T00:37:52 http://comments.gmane.org/gmane.comp.version-control.monotone.devel/19381 <pre>I've fixed issue 202, but I can't edit the issue via code.monotone.ca. As soon as I start to edit in the 'comment' box, the page disappears, and leaves me with a "No issues were found" list. As if it had searched for something, and not found anything. Help! </pre> Stephen Leake 2012-05-13T00:52:47 http://comments.gmane.org/gmane.comp.version-control.monotone.devel/19380 <pre>I have lua-5.2 installed in Mingw, and it's actually somewhat difficult to install a different version (not like Debian :(). So are there any objections to merging nvm.lua-5.2? Do we have a release manager? </pre> Stephen Leake 2012-05-12T23:39:28 http://comments.gmane.org/gmane.comp.version-control.monotone.devel/19378 <pre> Hi all! I've deployed a new version of Indefero (1.3.2) and merged it with our custom layout. Let me know if you find any hiccups (note though that you should clear your browser cache before... :) A list of notable changes since v1.2 (which is what we were previously running) can be found here: &lt;http://projects.ceondo.com/p/indefero/page/News/&gt; (The activity calculation is not enabled for our setup, btw...) Thomas. </pre> Thomas Keller 2012-05-09T20:47:47 http://comments.gmane.org/gmane.comp.version-control.monotone.devel/19369 <pre> Just a short email to announce the 1.00 release of mtn-browse. Main improvements include a history graphing tool and new and improved combo-box entries fields. For more details please go to: http://www.coosoft.plus.com/software.html Please download from: http://sourceforge.net/projects/mtn-browse/ This application is supported for Linux, Mac OSX, and most Unixes. Regards, Tony Cooper. </pre> Anthony Edward Cooper 2012-05-06T11:07:55 http://comments.gmane.org/gmane.comp.version-control.monotone.devel/19360 <pre>I've hit a bug in compiling nvm.lua-2.0 in Cygwin, while running 'make check'; /usr/include/boost/math/special_functions/detail/lgamma_small.hpp:483:38: error: expected primary-expression before 'do' It's the L macro, due to Boost 1.48 (which Cygwin has). It's also mtn issue 191. That gives a patch; has that been committed yet? I don't see it in the commit log. It's a very small change; for now, I'll apply it on the nvm.lua-5.2 workspace, but not commit it. </pre> Stephen Leake 2012-05-02T08:00:31 http://comments.gmane.org/gmane.comp.version-control.monotone.devel/19358 <pre>LinkedIn ------------ I'd like to add you to my professional network on LinkedIn. - Venkata Hanuman Venkata Hanuman Choudari.S Project Engineer at AU-KBC Research Centre Chennai Area, India Confirm that you know Venkata Hanuman Choudari.S: https://www.linkedin.com/e/d2bh2r-h1pabcq4-1x/isd/6915973884/ntIiayv8/?hs=false&amp;tok=0dS-VtKyJKL5c1 -- You are receiving Invitation to Connect emails. Click to unsubscribe: http://www.linkedin.com/e/d2bh2r-h1pabcq4-1x/XCAxs3dcTSJze83nXF7bHoUQSZKXGHFngbD2Plz/goo/monotone-devel%40nongnu%2Eorg/20061/I2375492060_1/?hs=false&amp;tok=1Xs6iiCC9KL5c1 (c) 2012 LinkedIn Corporation. 2029 Stierlin Ct, Mountain View, CA 94043, USA. _______________________________________________ Monotone-devel mailing list Monotone-devel&lt; at &gt;nongnu.org https://lists.nongnu.org/mailman/listinfo/monotone-devel </pre> Venkata Hanuman Choudari.S 2012-05-01T18:22:32 http://comments.gmane.org/gmane.comp.version-control.monotone.devel/19357 <pre>I've pushed nvm.nfs_mount_in_workspace. In src/unix/fs.cc, I've patched rename_clobberingly to handle my use case of a subdirectory of a workspace nfs mounted to a Lynx 5.0 disk. Any comments? I'm wondering if I should make the file protection mode wider than user r/w. I tried leaving that param out, as the docs suggest it will use a reasonable default depending on the environment, but that did _not_ work; I got random modes, including nobody read or write! In any case, this works for my use case, and I'd be somewhat surprised if anyone else ever needs it :). </pre> Stephen Leake 2012-05-01T12:47:12 http://comments.gmane.org/gmane.comp.version-control.monotone.devel/19353 <pre>We're now running v1.0 (we were running some pre-1.0 before, I've no idea why we hadn't upgraded it before). All databases I know about have been migrated accordingly. Also, I've upgraded buildbot to v1.8.6p1. It already has support for monotone build in (thanks to yours truly ;-)). I suggest buildslaves get upgraded to 1.8.3 or higher. Cheers, Richard </pre> Richard Levitte 2012-04-25T13:31:52 http://comments.gmane.org/gmane.comp.version-control.monotone.devel/19349 <pre>Hi, quite a few fixes went in since monotone 1.0, including the recent fix for compatibility with Botan 1.10 (which got released in June 2011). So I'm thinking it's about time for a release. How much time do we need to be able to release? Any pending items somebody absolutely wants to get in? Regards Markus Wanner </pre> Markus Wanner 2012-04-24T20:18:14 http://comments.gmane.org/gmane.comp.version-control.monotone.devel/19344 <pre>Monotone packages are currently failing to build under Debian's auto-build system, but the reason has me confused so I thought I'd ask the main dev list. It looks like monotone itself is building fine, but a number of the tests are failing. A full log of a recent build can be found here: https://buildd.debian.org/status/fetch.php?pkg=monotone&amp;arch=i386&amp;ver=1.0-4%2Bb1&amp;stamp=1335032594 To me, it looks like monotone is copying test databases to a specific location for a test, then apparently finding the files missing. I can't replicate this in a Debian unstable chroot, nor can I imagine in the automated build environment could cause the tests to fail in this way. Any ideas? Francis </pre> Francis Russell 2012-04-24T11:30:17 http://comments.gmane.org/gmane.comp.version-control.monotone.devel/19343 <pre>Hello, A new issue has been created and assigned to you: 208 - ml_gobject.c: conflicting types for 'g_value_get_variant' Project: monotone Status: New Reported by: J Doe Labels: Type:Defect Priority:Medium Description: Steps to reproduce the problem: ------------------------------- 1. ./configure &amp;&amp; make #version monotone-viz-1.0.2 2. make fails with error attached Expected result: ---------------- Make should run fine on my Slackware64 Actual results: --------------- (outputs attached error) ml_gobject.c:292:14: error: conflicting types for 'g_value_get_variant' Output of `mtn version --full`: ------------------------------- mtn not found because make failed Attachments: - ml_gobject_make_error.txt - 636 bytes https://code.monotone.ca/p/monotone/issues/view/attachment/46/ml_gobject_make_error.txt -- Issue: https://code.monotone.ca/p/monotone/issues/208/ </pre> code< at >monotone.ca 2012-04-24T02:25:16 http://comments.gmane.org/gmane.comp.version-control.monotone.devel/19340 <pre>Hello, A new issue has been created and assigned to you: 207 - mtn revert inconsistent with/without inodeprints Project: monotone Status: New Reported by: Stephen Leake Labels: Type:Incorrect Behavior Priority:Medium Description: Steps to reproduce the problem: ------------------------------- 1. enable inodeprints via 'mtn refresh_inodeprints' 2. delete several files from disk via rm 3. 'mtn revert' one of the files Expected result: ---------------- file reverted Actual results: --------------- fatal warning about missing files. Without inodeprints, the revert succeeds. In the source, the problem is that 'work.cc maybe_update_inodeprints' calls update_current_roster_from_filesystem, which prints the warning. We need to disable warnings on some calls to update_current_roster_from_filesystem, or not call update-inodeprints for revert, or something. Output of `mtn version --full`: ------------------------------- -- Issue: https://code.monotone.ca/p/monotone/issues/207/ </pre> code< at >monotone.ca 2012-04-10T18:08:09 http://comments.gmane.org/gmane.comp.version-control.monotone.devel/19330 <pre>Hello, A new issue has been created and assigned to you: 206 - mtn build breaks with Lua 5.2.0 Project: monotone Status: New Reported by: Stephen Leake Labels: Type:Incorrect Behavior Priority:Medium Description: Steps to reproduce the problem: ------------------------------- 1. Install Lua 5.2.0 2. make check Expected result: ---------------- successful build Actual results: --------------- error about LUA_GLOBALSINDEX not defined Apparently the Lua API has changed in this area. Workaround is to use Lua 5.1.4 (highest version I tested; 5.1.5 is also available). I did not investigate further. Output of `mtn version --full`: ------------------------------- -- Issue: https://code.monotone.ca/p/monotone/issues/206/ </pre> code< at >monotone.ca 2012-03-20T21:33:07 http://comments.gmane.org/gmane.comp.version-control.monotone.devel/19329 <pre>Hello, A new issue has been created and assigned to you: 205 - Exporting to Git documentation error Project: monotone Status: New Reported by: Jake Petroules Labels: Type:Defect Priority:Medium Description: The code sample at the url (http://www.monotone.ca/docs/Exporting-to-GIT.html) states to use 'git fast import'. This should be 'git fast-import' (the docs are missing the dash). -- Issue: https://code.monotone.ca/p/monotone/issues/205/ </pre> code< at >monotone.ca 2012-03-18T03:40:45 http://comments.gmane.org/gmane.comp.version-control.monotone.devel/19328 <pre>I found this web page useful as a summary of common monotone usage: http://developer.pidgin.im/wiki/UsingPidginMonotone It's specific for the developer of pidgin, but informative all the same. </pre> Hendrik Boom 2012-03-17T14:42:45 http://comments.gmane.org/gmane.comp.version-control.monotone.devel/19325 <pre>I hate pestering you guys with trivia, but here goes again. Every time I set up a new mtn database I end up with trouble. Always it's different trouble. I don't seem to remember all the details from previous times, and I seem to misread the manual again and again. THis time what's stymied me is anonymity. I.m trying to populate a database by pulling form an usher server: hendrik&lt; at &gt;notlookedfor:~/monotone$ mtn --key hendrik&lt; at &gt;notlookedfor.topoi.pooq.com pull mtn://topoi.pooq.com/slides?com.pooq.hendrik.slides --db ~/monotone/slides.db mtn: connecting to 'mtn://topoi.pooq.com/slides' mtn: include pattern 'com.pooq.hendrik.slides' mtn: exclude pattern '' mtn: finding items to synchronize: mtn: warning: protocol error while processing peer mtn://topoi.pooq.com/slides: 'received network error: anonymous access to branch 'com.pooq.hendrik.slides' denied by server' mtn: bytes in | bytes out | certs in mtn: 97 | 350 | 0 mtn: error: processing failure while talking to peer 'mtn://topoi.pooq.com/slides', disconnecting hendrik&lt; at &gt;notlookedfor:~/monotone$ now, I have the proper permissions to read that remote data base. But what do I have to do to be recognised as not being anonymous? Is specifying the key with --key hendrik&lt; at &gt;notlookedfor.topoi.pooq.com not enough? </pre> Hendrik Boom 2012-03-17T03:10:20 http://comments.gmane.org/gmane.comp.version-control.monotone.devel/19323 <pre>Hello, A new issue has been created and assigned to you: 204 - Monotone does not work with non-ANSI symbols on Windows with Russian locale Project: monotone Status: New Reported by: Anton Zimin Labels: Type:Defect Priority:Medium Description: Steps to reproduce the problem: ------------------------------- 1. Create empty database. Setup a branch. 2. Create new folder with name in Russian ('Папка' in my case). 3. mtn add . -R Expected result: ---------------- Folder must be included into repository. Actual results: --------------- C:\temp\mtntest&gt;mtn add . -R mtn: warning: skipping directory 'Папка' with unsupported name Output of `mtn version --full`: ------------------------------- monotone 1.0 (base revision: unknown) Running on : Windows NT/2000/XP/2003 (6.1, build 7601, Service Pack 1) on ia32 (level 6, rev 3853) C++ compiler : GNU C++ version 4.5.2 C++ standard library: GNU libstdc++ version 20101216 Boost version : 1_46_1 SQLite version : 3.7.5 (compiled against 3.7.5) Lua version : Lua 5.1 PCRE version : 8.12 2011-01-15 (compiled against 8.12) Botan version : 1.8.11 (compiled against 1.8.11) Changes since base revision: unknown -- Issue: https://code.monotone.ca/p/monotone/issues/204/ _______________________________________________ Monotone-devel mailing list Monotone-devel&lt; at &gt;nongnu.org https://lists.nongnu.org/mailman/listinfo/monotone-devel </pre> code< at >monotone.ca 2012-03-14T03:25:52 http://comments.gmane.org/gmane.comp.version-control.monotone.devel/19319 <pre>Hello, A new issue has been created and assigned to you: 203 - Monotone fails to build against eglibc version 2.15 Project: monotone Status: New Reported by: Francis Russell Labels: Type:Defect Priority:Medium Description: eglibc is now the glibc of choice in both Debian and Ubuntu. Ubuntu precise contains eglibc 2.15 and have encountered build issues due to it defining a struct file_handle. This conflicts with the definition of file_handle in fnctl.h. Here's the Ubuntu build log: g++ -I. -I/usr/include/lua5.1 -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Wformat-security -Wall -W -Wno-unused -c -o src/rcs_file.o src/rcs_file.cc src/rcs_file.cc:45:1: error: redefinition of 'struct file_handle' /usr/include/i386-linux-gnu/bits/fcntl.h:239:8: error: previous definition of 'struct file_handle' src/rcs_file.cc: In function 'void parse_rcs_file(const string&amp;, rcs_file&amp;)': src/rcs_file.cc:492:34: error: no matching function for call to 'file_handle::file_handle(const string&amp;)' src/rcs_file.cc:492:34: note: candidates are: /usr/include/i386-linux-gnu/bits/fcntl.h:239:8: note: file_handle::file_handle() /usr/include/i386-linux-gnu/bits/fcntl.h:239:8: note: candidate expects 0 arguments, 1 provided /usr/include/i386-linux-gnu/bits/fcntl.h:239:8: note: file_handle::file_handle(const file_handle&amp;) /usr/include/i386-linux-gnu/bits/fcntl.h:239:8: note: no known conversion for argument 1 from 'const string {aka const std::basic_string&lt;char&gt;}' to 'const file_handle&amp;' src/rcs_file.cc:493:40: error: 'struct file_handle' has no member named 'fd' src/rcs_file.cc:493:51: error: 'struct file_handle' has no member named 'length' make[4]: *** [src/rcs_file.o] Error 1 make[4]: Leaving directory `/build/buildd/monotone-1.0' make[3]: *** [all-recursive] Error 1 make[3]: Leaving directory `/build/buildd/monotone-1.0' make[2]: *** [all] Error 2 make[2]: Leaving directory `/build/buildd/monotone-1.0' dh_auto_build: make -j1 INFO_DEPS= returned exit code 2 make[1]: *** [override_dh_auto_build] Error 2 make[1]: Leaving directory `/build/buildd/monotone-1.0' make: *** [binary] Error 2 dpkg-buildpackage: error: /usr/bin/fakeroot debian/rules binary gave error exit status 2 ****************************************************************************** Build finished at 20120208-1656 FAILED [dpkg-buildpackage died] -- Issue: https://code.monotone.ca/p/monotone/issues/203/ </pre> code< at >monotone.ca 2012-02-20T14:35:35 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.comp.version-control.monotone.devel