[Monotone-devel] A cornucopia of issues

[Ryan Hinton]

Sorry, this is going to be a long email.  I've numbered the issues for 
convenience.  Thanks for the help thus far. 


(1)  I added a package for GCC 3.3.2, downloaded monotone 0.21, and hit 
another snag.  I had to add "#include <cstdarg>" to database.hh.  It 
uses a va_list type.  I'm suggesting this as a patch.


(2)  Next issue.  In order to get my feet wet and suggest this patch, I 
tried to pull the monotone source.  I pull about 9MB of data and then 
begin spewing.  Incidentally, there is a noticeable stall at the 5.4MB.  
Here is what I see.

myhost% monotone --db=mt.db --key="" pull venge.net net.venge.monotone
monotone: warning: doing anonymous pull
monotone: connecting to venge.net
monotone: first time connecting to server venge.net
monotone: I'll assume it's really them, but you might want to double-check
monotone: their key's fingerprint: 70a0f283898a18815a83df37c902e5f1492e9aa2
monotone: warning: No branches found.
monotone: rebuilding merkle trees ...
monotone: bytes in | bytes out | certs in | revs in | revs written
monotone:   204.0k |      5957 |       21 |       0 |            0
monotone:     2.0M |    161.1k |     1302 |      21 |            0
monotone:     5.0M |    383.6k |     5808 |     716 |            0
monotone:     5.4M |    396.8k |     7678 |    2721 |            0
monotone:     7.7M |    449.9k |     7678 |    2721 |            0
monotone:     8.4M |    456.9k |     7678 |    2721 |            0
monotone:     8.7M |    461.9k |     7678 |    2721 |            0
monotone:     8.7M |    464.1k |     7678 |    2721 |            0
monotone:     8.9M |    466.6k |     7678 |    2721 |            0
monotone:     8.9M |    467.4k |     7678 |    2721 |            0

I get the multiple lines hitting <ENTER> to keep my SSH session from 
dropping (anyone know how to STOP THAT?!).  I think the resulting 
download log is a nifty feature.  After that it spews many warnings 
ending with the following.

monotone: warning: discarding revision data packet 
6b72e940a0c1f3e9d79a60164964786aaea74798 with unmet dependencies
monotone: warning: discarding revision data packet 
e6c1c7e7c34dd4c62bc7cdc45ace535776707b32 with unmet dependencies
monotone: warning: discarding revision data packet 
1dcf5b3cb746ea6c1848280d7ad6ca9f42a29eb3 with unmet dependencies
monotone: fatal: std::bad_alloc: St9bad_alloc

I can send a core dump if that would be useful.  Any suggestions on 
getting the monotone source?  Is there any way to do a partial pull?


(3)  Next I tried to get a client to test my OpenBSD server.  So I tried 
to compile 0.21 on my FreeBSD box.  It fails.  Here is the error.

if g++ -DLOCALEDIR=\"/usr/local/share/locale\" -DHAVE_CONFIG_H -I. -I. 
-I.  -I./lua -I./sqlite -I/usr/local/include  -DNDEBUG 
-DBOOST_DISABLE_THREADS -Wall  -O2 -fno-strict-aliasing 
-DBOOST_REGEX_V4_CHAR_REGEX_TRAITS_HPP -DBOOST_REGEX_COMPILE_HPP -MT 
monotone-merkle_tree.o -MD -MP -MF ".deps/monotone-merkle_tree.Tpo" \
 -c -o monotone-merkle_tree.o `test -f 'merkle_tree.cc' || echo 
'./'`merkle_tree.cc; \
then mv -f ".deps/monotone-merkle_tree.Tpo" 
".deps/monotone-merkle_tree.Po"; \
else rm -f ".deps/monotone-merkle_tree.Tpo"; exit 1; \
fi
/usr/local/include/boost/dynamic_bitset/dynamic_bitset.hpp: In 
constructor `boost::dynamic_bitset<Block, 
Allocator>::dynamic_bitset(size_t, long unsigned int, const Allocator&) 
[with Block = unsigned char, Allocator = std::allocator<unsigned char>]':
merkle_tree.cc:77:   instantiated from here
/usr/local/include/boost/dynamic_bitset/dynamic_bitset.hpp:541: warning: 
comparison between `enum boost::dynamic_bitset<unsigned char, 
std::allocator<unsigned char> >::<anonymous>' and `enum 
boost::dynamic_bitset<unsigned char, std::allocator<unsigned char> 
>::<anonymous>'
merkle_tree.cc:77:   instantiated from here
/usr/local/include/boost/dynamic_bitset/dynamic_bitset.hpp:548: error: 
no matching function for call to 
`make_non_const(boost::dynamic_bitset<unsigned char, 
std::allocator<unsigned char> >::<anonymous enum>)'
gmake[2]: *** [monotone-merkle_tree.o] Error 1
gmake[2]: Leaving directory `/usr/ports/devel/monotone/src'
gmake[1]: *** [all-recursive] Error 1
gmake[1]: Leaving directory `/usr/ports/devel/monotone/src'
gmake: *** [all] Error 2

I am running FreeBSD 5.3-STABLE, GCC version "3.4.2 [FreeBSD] 
20040728".  I used the pre-packged Boost 1.32 port, which compiled 
without complaint.  My current FreeBSD ports tree has a monotone 0.11 
port, but it's marked as broken.  Any clues?


(4)  I am having trouble running monotone chroot'ed.  This is probably 
user error, but any help is appreciated.

myhost# chroot /var/www/ monotone --db=/var/monotone/myhost.mtdb serve 
myhostname "myhostname-reversed.*"
monotone: fatal: std::exception: OS_Rng: open /dev/urandom operation 
failed with error 6

Notice I'm still running as root.  (Same results for the _monotone user 
I created.)  I have a /var/www/dev/urandom file with permissions 755.  
Here is the output from monotone --full-version just for fun.

monotone 0.21 (base revision: e65bc11b6670a0b2ed8e72214cb81d94e6a9a2d1)
Running on: OpenBSD 3.5 GENERIC#34 i386
Changes since base revision:

new_manifest [4dc584ff115bc0e54e51697ec048e2806499ae12]

old_revision [e65bc11b6670a0b2ed8e72214cb81d94e6a9a2d1]
old_manifest [4dc584ff115bc0e54e51697ec048e2806499ae12]


 Generated from data cached in the distribution;
 further changes may have been made.

 ...

I can do directory listings and such just fine chroot'ed, but monotone 
seems unhappy.


(5)  Finally, an easy one.  I am trying to find the best way to run 
monotone as a server.  Should I add it to rc.local?  Should I use 
nohup?  Run it in the background using my user account?  I saw someone 
suggested using runit, but OpenBSD 3.5 doesn't have a packaged version.  
I can try to download and install it if it's the best solution.  The 
same thread mentioned some post-install information/scripts I haven't 
found yet.  Where can I find that information?  Any other suggestions on 
how to securely run and use the monotone server?

Thanks for your patience and help!

--
Ryan Hinton
address@hidden