Closing as invalid, now.Status: Invalid
What language was that?Labels: Priority:Low
I don't think monotone ever supported time zone designators, so I suspect that 'Z' got added by another tool. In any case, I added support for those in rev 57a4fd816143b0eb82b154f256ebba2af0bc67a7.Labels: Type:Feature Request
See extra/bash_completion to reproduce the issue. Run from a directory containing spaces. Exclamation marks are nice as well... (for those, even the test fails).
I saw that very test fail on Gentoo Hardened as well, but it looks like a slightly different cause. Peter, can you please try a current snapshot on Gentoo (non-hardened)?Status: Accepted
As pointed out by Thomas, already, this has been fixed in net.venge.monotone and will appear in the next release, which is due real soon now (tm).Status: Fixed
Fixed in branch net.venge.monotone-freebsd-10Status: Fixed
(test #2 update to see if mail is correctly sent to the mailing list)
(test update to see if mail is correctly sent to the mailing list)
Probably related. I have two mtn branches: one trunk and one feature branch now suspended that doesn't show up anymore on "mtn ls branches". When I git_export both are exported (and can be seen with "git branch"); I'd like the merged-and-suspended one to be exported no more.
Compiling with clang leads to many errors, and thus it's impossible to build on FreeBSD 10. In file included from src/monotone.cc:22: In file included from src/database.hh:19: In file included from src/rev_types.hh:22: In file included from src/hybrid_map.hh:14: src/hash_map.hh:101:25: error: no member named '__stl_hash_string' in namespace '__gnu_cxx' return __gnu_cxx::__stl_hash_string(s.c_str());
I tried a couple of combinations (dir rather than path, directory deleted prior to mv) but was unable to trigger that bug (with mtn 1.1, though). Can you please provide /home/hendrik/write/nahaly/_MTN/debug, as requested in the error message?
Steps to reproduce the problem: ------------------------------- Here's what I did: hendrik@notlookedfor:~/write/nahaly/nahaly$ mtn add main.mtxt mtn: adding 'nahaly/main.mtxt' to workspace manifest hendrik@notlookedfor:~/write/nahaly/nahaly$ mtn mv main.mtxt src/main.mtxt mtn: skipping 'nahaly/src', already accounted for in workspace mtn: fatal: error: src/roster.hh:133: I(static_cast<bool>(d)) mtn: This is almost certainly a bug in monotone. mtn: Please report this error message, the output of 'mtn version --full', mtn: and a description of what you were doing to ' https://code.monotone.ca/p/monotone/issues/'. mtn: wrote debugging log to /home/hendrik/write/nahaly/_MTN/debug mtn: if reporting a bug, please include this file hendrik@notlookedfor:~/write/nahaly/nahaly$ 1. 2. 3. Expected result: I expected it to move nahaly/main.mtxt to nahaly/src/main.mtxt. (I was in the nahaly directory. ---------------- Actual results: --------------- You've seen them. Nothing was moved. Output of `mtn version --full`: ------------------------------- monotone 1.0 (base revision: a7c3a1d9de1ba7a62c9dd9efee17252234bb502c) Running on : Linux 3.10-3-686-pae #1 SMP Debian 3.10.11-1 (2013-09-10) i686 C++ compiler : GNU C++ version 4.8.1 C++ standard library: GNU libstdc++ version 20130717 Boost version : 1_49 SQLite version : 3.8.0.2 (compiled against 3.7.17) Lua version : Lua 5.1 PCRE version : 8.31 2012-07-06 (compiled against 8.31) Botan version : 1.10.5 (compiled against 1.10.5) Changes since base revision: format_version "1" new_manifest [b252820fde344fd3f5d023fd91de86522baa671d] old_revision [a7c3a1d9de1ba7a62c9dd9efee17252234bb502c] Generated from data cached in the distribution; further changes may have been made. hendrik@notlookedfor:~/write/nahaly/nahaly$
Thanks! It looks like the patches are for now the way to go in pkgsrc.
This is a known issue. Code on the main net.venge.monotone branch already works with Lua 5.2. You now have several options: - use nvm head version - wait for Monotone 1.1, to be released within short time - use a patch If you are looking for patches, see e.g. http://pkgs.fedoraproject.org/cgit/monotone.git/tree/ .
Steps to reproduce the problem: ------------------------------- 1. I tried to build the pkgsrc-packaged version of monotone-1.0, with lua-5.2.2 installed. 2. The build failed. Expected result: ---------------- A clean build. Actual results: --------------- There are several issues: Monotone uses several #defines which don't exist any more: LUA_GLOBALSINDEX, LUAI_MAXCSTACK, lua_strlen. luaext_platform.cc uses another #define which does not exist any more: LUA_ENVIRONINDEX. Looking for a quick fix it turned out that the function where it is used is trying something intimate with internal lua functions from liolib.c. However that stuff has been completely changed between lua 5.1 and 5.2. So a quick fix for somebody not intimate friends with lua *and* monotone is out of the question. This is a serious portability problem! Output of `mtn version --full`: -------------------------------
It is possible to use relative database paths in the _MTN/options file, but they are resolved using the current working directory. It could be nice to always resolve them to the root of the project so that they can actually be used. (this bug to remember about it, but I might probably take a look at this myself)
Another problem - bad dates also break exporting-to-git.
... and no documentation on how to fix it. The docs at http://www.monotone.ca/docs/Trust-Evaluation-Hooks.html recommend a key name based get_revision_cert_trust hook but that is insecure since monotone now allows duplicate key names. A secure implementation must use the key ID, but there's no documentation on how to do that. The secure hook may be implemented by using quoted hex key ids in 'trusted_signers", and implementing a new function (e.g. 'idintersection') that uses v.id instead of v.name. This ticket is for a fix to the website and any other places where the example is given, to provide a secure example. Steps to reproduce the problem: ------------------------------- 1. Add second key with same name 2. Sample trust hook will trust it too Expected result: ---------------- Better example Output of `mtn version --full`: ------------------------------- 1.0.0