Re: [Monotone-devel] usher 0.99 release (name-based virtual hosting for monotone)
In message <20110201200533.ga8...@topoi.pooq.com> on Tue, 1 Feb 2011 15:05:33
-0500, Hendrik Boom said:
hendrik> On Mon, Nov 08, 2010 at 02:04:46PM -0500, Hendrik Boom wrote:
hendrik> >
hendrik> > I guess now comes the inevitable flood of stupid questions as i try
to
hendrik> > make sense of the documentation.
hendrik> >
hendrik>
hendrik> Well, I have usher running, and depending on how I write the
hendrik> configuration file it reports I have one or two servers, called
"write",
hendrik> the one I want to start with, and "local", the one inherited form the
hendrik> example in the documentation.
hendrik>
hendrik> But when I try to sync with "write" from another computer, I geet
hendrik> problems:
hendrik>
hendrik> hendrik@notlookedfor:~/write/Melinda$ mtn sync
4691://topoi.pooq.com/write
hendrik> enter passphrase for key ID [hend...@notlookedfor.topoi.pooq.com]
(ad968be7...):
hendrik> mtn: connecting to 4691://topoi.pooq.com/write
hendrik> mtn: Received warning from usher: Cannot fork server.
hendrik> mtn: peer 4691://topoi.pooq.com/write IO terminated connection in
working state (error)
hendrik> mtn: error: I/O failure while talking to peer
4691://topoi.pooq.com/write, disconnecting
hendrik> hendrik@notlookedfor:~/write/Melinda$
In your configuration file, you have a logdir setting. You might want
to look at the log file there (write.log, I believe).
hendrik> Can I get usher to tell me what the command it uses really
hendrik> is, so I can try it in isolation?
Basically, if we say that {monotone} and {local} are the values of the
settings with corresponding names, it does this:
{monotone} server --bind=127.0.0.1:{randomport} {local}
hendrik> Or does it misreport a successful fork with an invalid
hendrik> monotone command as a failed fork? Or ... (fill in the real
hendrik> explanation here, please?)
Well, an invalid command of some sort WOULD result in a failed fork,
so that's definitely a plausible explanation. Check the log in
{logdir}.
--
Richard Levitte rich...@levitte.org
http://richard.levitte.org/
"Life is a tremendous celebration - and I'm invited!"
-- from a friend's blog, translated from Swedish
___
Monotone-devel mailing list
Monotone-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/monotone-devel
Re: [Monotone-devel] usher 0.99 release (name-based virtual hosting for monotone)
On Mon, Nov 08, 2010 at 02:04:46PM -0500, Hendrik Boom wrote:
>
> I guess now comes the inevitable flood of stupid questions as i try to
> make sense of the documentation.
>
Well, I have usher running, and depending on how I write the
configuration file it reports I have one or two servers, called "write",
the one I want to start with, and "local", the one inherited form the
example in the documentation.
But when I try to sync with "write" from another computer, I geet
problems:
hendrik@notlookedfor:~/write/Melinda$ mtn sync 4691://topoi.pooq.com/write
enter passphrase for key ID [hend...@notlookedfor.topoi.pooq.com]
(ad968be7...):
mtn: connecting to 4691://topoi.pooq.com/write
mtn: Received warning from usher: Cannot fork server.
mtn: peer 4691://topoi.pooq.com/write IO terminated connection in working state
(error)
mtn: error: I/O failure while talking to peer 4691://topoi.pooq.com/write,
disconnecting
hendrik@notlookedfor:~/write/Melinda$
Presumably something is still wrong with my configuration.
It looks as if usher does recieve the connection, identifies the
correct server ("write") in the script below, and fails to fork to start the
server.
Hers's the configuration file (password replaced):
userpass"hendrik" "notthepasswordd"
monotone"/usr/local/bin/mtn" "-k" "hend...@topoi.pooq.com"
listenaddr "0.0.0.0:4691"
adminaddr "127.0.0.1:12345"
logdir "/farhome/hendrik/monotone/usher-log/"
server "write"
host"0.0.0.0"
pattern "com.pooq.hendrik.write*"
local "-d" "/farhome/hendrik/monotone/write.db"
server "local"
host"127.0.0.1"
pattern "*"
local "-d" "/usr/local/src/managed/my.db"
Now when I try to execute the command suggested by the monotone line,
/usr/local/bin/mtn -k hend...@topoi.pooq.com
the shell starts monotone OK, although of course monotone immediately
complains at length that it's an invalid commant. But from the shell, the
"fork" succeeds.
Can I get usher to tell me what the command it uses really is,
so I can try it in isolation? Or does it misreport a successful fork
with an invalid monotone command as a failed fork? Or ... (fill in
the real explanation here, please?)
By the way, looking at the computer where usher is running, for each
attempt to sync it gives me three requests to enter the passphrase
for hend...@topoi.pooq.com. But entering the passphrase there doesn't
seem to have any effect.
By the way, the monotone running on the usher machine is 0.99.1;
the version on the client machine is 0.48 -- the one distributed
recently in testing as 0.48.3
-- hendrik
___
Monotone-devel mailing list
Monotone-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/monotone-devel
Re: [Monotone-devel] Re: [Monotone-commits-diffs] net.venge.monotone.source-tree-cleanup: d54c8c17eeebbe7dd6bb30d4d10996db79de24f2
In message <82hbcoukgw@stephe-leake.org> on Tue, 01 Feb 2011 05:18:07
-0500, Stephen Leake said:
stephen_leake> I'm getting an error from autoconf on Debian and MinGW:
stephen_leake>
stephen_leake> stephe@Shevek$ autoreconf -i
stephen_leake> doc/Makefile.am:44: installing `doc/mdate-sh'
stephen_leake> doc/Makefile.am:44: installing `doc/texinfo.tex'
stephen_leake> Makefile.am:600: variable `CLEAN_SOURCES' is defined but no
program or
stephen_leake> Makefile.am:600: library has `CLEAN' as canonical name (possible
typo)
Fixed. Apparently, it takes CLEAN_SOURCES as {foo}_SOURCES and can't
see it referred in anything that's called {foo}_PROGRAM, {foo}_LIB and
so on, so it seems to think that we've forgotten something.
Why this doesn't happen in main, I do not know.
stephen_leake> After that, 'make distcheck' fails on Debian:
stephen_leake>
stephen_leake> make[3]: Entering directory
`/home/Projects/monotone/monotone.source-tree-cleanup-build/monotone-1.0dev/_build/doc'
stephen_leake>
stephen_leake> ...
stephen_leake>
stephen_leake> cd ../../doc
stephen_leake>
stephen_leake> ...
stephen_leake>
stephen_leake> mkdir: cannot create directory `.am17349': Permission denied
stephen_leake>
stephen_leake> At this point, the working directory is
stephen_leake> monotone.source-tree-cleanup-build/monotone-1.0dev/doc, which has
stephen_leake> permissions dr-xr-xr-x, which is why the mkdir fails.
stephen_leake>
stephen_leake> Apparently distcheck doesn't expect the makefile commands to
write to
stephen_leake> the source directory (which makes sense); it changes the source
stephen_leake> directory permissions to a-w. But this is a standard autotool
hack to
stephen_leake> backup some tex files.
stephen_leake>
stephen_leake> And it works in main.
Yup, the backup happens when it builds .info files. Makefile.am in
main has a hack that probably cirumvents this. I'll check that out...
The GNU standard seems to say that .info files should be distributed
with the tarball, so the user doesn't have to build them (in other
words, the user isn't required to have the tool chain that is
required). That's why they build .info files in the source tree by
default. Consequently, they don't expect maintainers (such as
yourself ;-)) to have r/o source directories... which does make
sense, come to think of it.
I'm really not sure we should double-bend our backs to accomodate
people checking out monotone into a r/o source. I can fully
understand if the dist tarball ends up being extracted into a r/o
directory, but that's really a different story.
stephen_leake> Then immediately:
stephen_leake>
stephen_leake> ../../doc/monotone.texi: No such file or directory
stephen_leake>
stephen_leake> This is from trying to run makeinfo. But that file
stephen_leake> exists!
Hmm...
stephen_leake> Building monotone.info not inside the distcheck directory works:
stephen_leake>
stephen_leake> cd monotone.source-tree-cleanup-build/doc
stephen_leake> make ../../monotone.source-tree-cleanup/doc/monotone.info
Well, yeah...
stephen_leake> On MinGW, I'm getting link errors in mtn.exe. Clearly
stephen_leake> time to go to bed and try again tomorrow ...
I would have liked to see the errors... oh well.
Cheers,
Richard
--
Richard Levitte rich...@levitte.org
http://richard.levitte.org/
"Life is a tremendous celebration - and I'm invited!"
-- from a friend's blog, translated from Swedish
___
Monotone-devel mailing list
Monotone-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/monotone-devel
Re: [Monotone-devel] Re: [Monotone-commits-diffs] net.venge.monotone.source-tree-cleanup: d54c8c17eeebbe7dd6bb30d4d10996db79de24f2
Stephen Leake writes: > On MinGW, I'm getting link errors in mtn.exe. This is now resolved; apparently something in my PATH was set wrong. win32-installer works. -- -- Stephe ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
Re: [Monotone-devel] Re: [Monotone-commits-diffs] net.venge.monotone.source-tree-cleanup: d54c8c17eeebbe7dd6bb30d4d10996db79de24f2
Stephen Leake writes: > Stephen Leake writes: > >> After that, 'make distcheck' fails on Debian: >> >> make[3]: Entering directory >> `/home/Projects/monotone/monotone.source-tree-cleanup-build/monotone-1.0dev/_build/doc' >> >> ... >> >> cd ../../doc >> >> ... >> >> mkdir: cannot create directory `.am17349': Permission denied >> >> At this point, the working directory is >> monotone.source-tree-cleanup-build/monotone-1.0dev/doc, which has >> permissions dr-xr-xr-x, which is why the mkdir fails. >> >> Apparently distcheck doesn't expect the makefile commands to write to >> the source directory (which makes sense); it changes the source >> directory permissions to a-w. But this is a standard autotool hack to >> backup some tex files. >> >> And it works in main. > > Apparently it doesn't do the backup thing on main, I'm not clear why. Perhaps we don't really need to run distcheck? as long as we are careful when running dist? -- -- Stephe ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
Re: [Monotone-devel] Re: [Monotone-commits-diffs] net.venge.monotone.source-tree-cleanup: d54c8c17eeebbe7dd6bb30d4d10996db79de24f2
Stephen Leake writes: > After that, 'make distcheck' fails on Debian: > > make[3]: Entering directory > `/home/Projects/monotone/monotone.source-tree-cleanup-build/monotone-1.0dev/_build/doc' > > ... > > cd ../../doc > > ... > > mkdir: cannot create directory `.am17349': Permission denied > > At this point, the working directory is > monotone.source-tree-cleanup-build/monotone-1.0dev/doc, which has > permissions dr-xr-xr-x, which is why the mkdir fails. > > Apparently distcheck doesn't expect the makefile commands to write to > the source directory (which makes sense); it changes the source > directory permissions to a-w. But this is a standard autotool hack to > backup some tex files. > > And it works in main. Apparently it doesn't do the backup thing on main, I'm not clear why. -- -- Stephe ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
Re: [Monotone-devel] Re: [Monotone-commits-diffs] net.venge.monotone.source-tree-cleanup: d54c8c17eeebbe7dd6bb30d4d10996db79de24f2
Richard Levitte writes: > In message <821v3swn69@stephe-leake.org> on Mon, 31 Jan 2011 20:36:46 > -0500, Stephen Leake said: > > stephen_leake> Ok, that's a problem. > stephen_leake> > stephen_leake> Maybe we can make EPS_FIGURES be empty on Win32 MinGW? > stephen_leake> > stephen_leake> Is there a reason to build monotone.ps, when .pdf is available? > stephen_leake> > stephen_leake> If it comes down to a choice between monotone.ps and > win32-installer, I > stephen_leake> think we can live without monotone.ps. > stephen_leake> > stephen_leake> this gets back to the question I asked: > stephen_leake> > stephen_leake> What Makefile targets are supposed to work? > stephen_leake> > stephen_leake> I tested monotone.pdf, but not monotone.ps. Is there some > other target > stephen_leake> that builds monotone.ps? 'dist' apparently doesn't. > stephen_leake> > stephen_leake> What other targets do I need to test when messing with > Makefiles? > > Have a look at revision adea9595011591375f0fc9c48bf741ae59cf328f, the > dependencies are a lot saner now. > > Really, not having monotone.texi in a subdirectory compared to > Makefile.am is so much simpler. The way automake differs in behavior > is huge (and I can understand why, considering all variants of make > it's trying to be compatible with!). Ok, that does look better. I'm getting an error from autoconf on Debian and MinGW: stephe@Shevek$ autoreconf -i doc/Makefile.am:44: installing `doc/mdate-sh' doc/Makefile.am:44: installing `doc/texinfo.tex' Makefile.am:600: variable `CLEAN_SOURCES' is defined but no program or Makefile.am:600: library has `CLEAN' as canonical name (possible typo) On Debian: stephe@Shevek$ autoconf --version autoconf (GNU Autoconf) 2.67 On MinGW: SABUL$ autoconf --version autoconf (GNU Autoconf) 2.63 After that, 'make distcheck' fails on Debian: make[3]: Entering directory `/home/Projects/monotone/monotone.source-tree-cleanup-build/monotone-1.0dev/_build/doc' ... cd ../../doc ... mkdir: cannot create directory `.am17349': Permission denied At this point, the working directory is monotone.source-tree-cleanup-build/monotone-1.0dev/doc, which has permissions dr-xr-xr-x, which is why the mkdir fails. Apparently distcheck doesn't expect the makefile commands to write to the source directory (which makes sense); it changes the source directory permissions to a-w. But this is a standard autotool hack to backup some tex files. And it works in main. Then immediately: ../../doc/monotone.texi: No such file or directory This is from trying to run makeinfo. But that file exists! Building monotone.info not inside the distcheck directory works: cd monotone.source-tree-cleanup-build/doc make ../../monotone.source-tree-cleanup/doc/monotone.info On MinGW, I'm getting link errors in mtn.exe. Clearly time to go to bed and try again tomorrow ... -- -- Stephe ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
