[Monotone-devel] Issue 139 - .mtn-ignore only read at start of automate stdio session (monotone)
Hello, A new issue has been created and assigned to you: 139 - .mtn-ignore only read at start of automate stdio session Project: monotone Status: New Reported by: Stephen Leake Labels: Type:Incorrect Behavior Priority:Medium Description: Steps to reproduce the problem: --- 1. start an automate stdio session 2. use it to run inventory 3. add unknown files to .mtn-ignore 4. run inventory again Expected result: ignored files show in inventory as ignored Actual results: --- ignored files show in inventory as unknown Output of `mtn version --full`: --- -- Issue: https://code.monotone.ca/p/monotone/issues/139/ ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] Updated Issue 139 - .mtn-ignore only read at start of automate stdio session (monotone)
Hello, The following issue has been updated: 139 - .mtn-ignore only read at start of automate stdio session Project: monotone Status: Duplicate Reported by: Stephen Leake URL: https://code.monotone.ca/p/monotone/issues/139/ Labels: Type:Incorrect Behavior Priority:Medium Comments (last first): # By Thomas Keller, Feb 2, 2011: This is a dupe of issue 75. Status: Duplicate # By Stephen Leake, Feb 2, 2011: Steps to reproduce the problem: --- 1. start an automate stdio session 2. use it to run inventory 3. add unknown files to .mtn-ignore 4. run inventory again Expected result: ignored files show in inventory as ignored Actual results: --- ignored files show in inventory as unknown Output of `mtn version --full`: --- -- Issue: https://code.monotone.ca/p/monotone/issues/139/ ___ 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 rich...@levitte.org writes: 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 real problem is that 'make dist' does not build the info files, so they are not in the tar file, so 'make distcheck' trys to build them in the read-only directory. TEXINFOS is empty in build/Makefile, and it doesn't recurse into build/doc/Makefile I don't know how to fix that properly. -- -- 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
ignore my other email about .info not being built. Sigh.
Richard Levitte rich...@levitte.org writes:
In message 82hbcoukgw@stephe-leake.org on Tue, 01 Feb 2011 05:18:07
-0500, Stephen Leake stephen_le...@stephe-leake.org said:
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.
The .info files are in the tarball; they are built in the orig source
directory before the tarball is built.
However, monotonevars.texi is changed, because the build dir is changed,
so the infos are rebuilt, with a read-only source tree, which fails.
So it's the introduction of monotonevars that is causing this problem.
That is used in '@verbatiminclude @value{top_srcdir}/src/std_hooks.lua'
Apparently there is no search path for this; it would be _much_ cleaner
to specify 'makeinfo -I ${top_srcdir}'!
Maybe we could make a symlink, so '@verbatiminclude std_hooks.lua' would
work?
I'm really not sure we should double-bend our backs to accomodate
people checking out monotone into a r/o source.
I agree in general, except that's what 'make distcheck' does, and it's
on the list of required Makefile targets (which I'm adding to
notes/release_checklist.txt).
We could remove 'distcheck' from the list of required targets.
--
-- 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
In message 82sjw6ubw5@stephe-leake.org on Wed, 02 Feb 2011 02:35:38 -0500, Stephen Leake stephen_le...@stephe-leake.org said: stephen_leake ignore my other email about .info not being built. Sigh. stephen_leake stephen_leake Richard Levitte rich...@levitte.org writes: stephen_leake stephen_leake I'm really not sure we should double-bend our backs stephen_leake to accomodate people checking out monotone into a r/o stephen_leake source. stephen_leake stephen_leake I agree in general, except that's what 'make distcheck' stephen_leake does, and it's on the list of required Makefile targets stephen_leake (which I'm adding to notes/release_checklist.txt). stephen_leake stephen_leake We could remove 'distcheck' from the list of required targets. For who is 'make distcheck' a required target? -- 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
[Monotone-devel] Updated Issue 139 - .mtn-ignore only read at start of automate stdio session (monotone)
Hello, The following issue has been updated: 139 - .mtn-ignore only read at start of automate stdio session Project: monotone Status: Duplicate Reported by: Stephen Leake URL: https://code.monotone.ca/p/monotone/issues/139/ Labels: Type:Incorrect Behavior Priority:Medium Comments (last first): # By Stephen Leake, Feb 3, 2011: Sorry about that; I did not search the old issues first. # By Thomas Keller, Feb 2, 2011: This is a dupe of issue 75. Status: Duplicate # By Stephen Leake, Feb 2, 2011: Steps to reproduce the problem: --- 1. start an automate stdio session 2. use it to run inventory 3. add unknown files to .mtn-ignore 4. run inventory again Expected result: ignored files show in inventory as ignored Actual results: --- ignored files show in inventory as unknown Output of `mtn version --full`: --- -- Issue: https://code.monotone.ca/p/monotone/issues/139/ ___ 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 stephen_le...@stephe-leake.org writes:
The .info files are in the tarball; they are built in the orig source
directory before the tarball is built.
However, monotonevars.texi is changed, because the build dir is changed,
so the infos are rebuilt, with a read-only source tree, which fails.
So it's the introduction of monotonevars that is causing this problem.
That is used in '@verbatiminclude @value{top_srcdir}/src/std_hooks.lua'
Apparently there is no search path for this; it would be _much_ cleaner
to specify 'makeinfo -I ${top_srcdir}'!
Sigh. makeinfo does support -I. the user manual on texinfo does not
mention this, because all the TeX tool user manuals are written in
complete ignorance of command line options, for some historical reason
(TeX is a really old language).
On the other hand, texi2dvi does not support -I, but it does support the
environment variable TEXINPUTS.
So this problem is now fixed; tested on Debian and MinGW.
'make distcheck' is now failing on something later.
--
-- 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 rich...@levitte.org writes: In message 82sjw6ubw5@stephe-leake.org on Wed, 02 Feb 2011 02:35:38 -0500, Stephen Leake stephen_le...@stephe-leake.org said: stephen_leake We could remove 'distcheck' from the list of required targets. For who is 'make distcheck' a required target? Tim mentioned it, and it seems like a reasonable test of the distribution process on Unix, where it used to work. It's a standard autotools target, so making it work means we are more compatible with the Gnu autotools process. It's now listed in nvm.source-tree-cleanup/notes/release-checlist.txt. Perhaps we need to add some rationale there. -- -- 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 stephen_le...@stephe-leake.org writes: Richard Levitte rich...@levitte.org writes: In message 82sjw6ubw5@stephe-leake.org on Wed, 02 Feb 2011 02:35:38 -0500, Stephen Leake stephen_le...@stephe-leake.org said: stephen_leake We could remove 'distcheck' from the list of required targets. For who is 'make distcheck' a required target? Tim mentioned it, and it seems like a reasonable test of the distribution process on Unix, where it used to work. It's a standard autotools target, so making it work means we are more compatible with the Gnu autotools process. Most importantly, it verifies that the .tar.gz we post on our website (which is built with 'make dist') can run 'make all monotone.dvi check install installcheck uninstall', all of which some user will want to do. step 9 in release-checklist requires running 'make distcheck', as part of building the .tar.gz source package. 'make distcheck' just found that 'tester-plaf.hh' was left out of the .tar.gz; I fixed Makefile.am test_bin_tester_SOURCES 'make distcheck' now passes. All the 'required targets' now pass on Debian and MinGW. So I think this is ready to promote to main. -- -- Stephe ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
Re: [Monotone-devel] nvm.source-tree-cleanup
Thomas Keller m...@thomaskeller.biz writes: There are a couple of minor issues left which kind of block the merge back to nvm, one of them is the move of some innosetup-specific resources out of src/win32 I'm not clear what the issue is here. In any case, 'make win32-installer' now works, does that resolve it? and another one deals with HTML documentation. I'm not clear what the issue is here. In any case, 'make html' now works, and builds both doc/monotone.html and doc/html/*, does that resolve it? -- -- Stephe ___ 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 Wed, Feb 02, 2011 at 12:09:23AM +0100, Richard Levitte wrote:
In message 20110201200533.ga8...@topoi.pooq.com on Tue, 1 Feb 2011 15:05:33
-0500, Hendrik Boom hend...@topoi.pooq.com said:
In your configuration file, you have a logdir setting. You might want
to look at the log file there (write.log, I believe).
Yes.. There is oe now. I stopped looking because for a while there
wasn't one, but one has now showed up. It seems to be asking me for a
passphrase for key ID hend...@topoi.pooq.com {599fffe...}
Presumably, monotone wants a passphrase wo start up in server mode.
What's the recommended way to provide one nowadays? The method
involving the get_passphrase hook that the tutorial says is deprecated
because of insecurity? It does have to be available when there's no
user logged in on the server machine.
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}.
Well, as long as the monotone process gets started, even if it
immediately complains and exits, the fork itself has succeeded, so at
the very least it's a misleading error message. But at this point
that's just a quibble.
Thanks.
-- hendrik
___
Monotone-devel mailing list
Monotone-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/monotone-devel
