Discussion for Tom Lord's `Arch' file revisioning system

Eric S. Raymond | 10 Jan 2008 01:10

[Help-gnu-arch] Help composing a sample session

I'm trying to write a sample Arch session for a survey paper I'm
working on, and failing.

Here's my sequence of commands;

  # Clear all arch state
  rm -fr {arch} {archives} ~/.arch-params/ .arch-ids foo.txt ++log.example--trunk--0.1--esr <at> thyrsus.com--2007-example

  tla my-id "Eric S. Raymond <esr <at> thyrsus.com>"
  mkdir {archives}
  tla make-archive esr <at> thyrsus.com--2007-example {archives}/2007-example
  tla my-default-archive esr <at> thyrsus.com--2007-example
  tla archives
  tla whereis-archive esr <at> thyrsus.com--2007-example
  tla archive-setup example--trunk--0.1
  tla categories
  tla branches example
  tla versions example--trunk
  tla init-tree example--trunk--0.1
  echo "This is a one-liner file." >foo.txt
  tla add foo.txt
  tla make-log

The last command echoes this:

++log.example--trunk--0.1--esr <at> thyrsus.com--2007-example

I then edit the log file, 

The problem cones when I try to commit:

(Continue reading)

headers

Ivan Shmakov | 15 Jan 2008 14:08

Re: [Help-gnu-arch] Help composing a sample session

>>>>> Eric S Raymond <esr <at> snark.thyrsus.com> writes:

 > I'm trying to write a sample Arch session for a survey paper I'm
 > working on, and failing.

 > Here's my sequence of commands;

[...]

 > tla init-tree example--trunk--0.1

	Note that this command doesn't affect the archive.

 > echo "This is a one-liner file." >foo.txt
 > tla add foo.txt
 > tla make-log

 > The last command echoes this:

 > ++log.example--trunk--0.1--esr <at> thyrsus.com--2007-example

 > I then edit the log file, 

 > The problem cones when I try to commit:

	Are you using $ tla commit here?

 > commit: tree has no patch log entries for version
 > tree: /home/esr/public_html/writings/version-control
 > version:esr <at> thyrsus.com--2007-example/example--trunk--0.1

(Continue reading)

headers

Thomas Lord | 10 Jan 2008 02:53

Re: [Help-gnu-arch] Help composing a sample session

Hi Eric,

I'm not up to speed on the very latest behavior of tla, but
I can give you general guidance about the confusion people
used to have around this.   You have to forgive where my
memory is sketchy on some details that can easily be cross-checked
with the code.

As I recall, a valid log file is vaguely RFC822-ish in the sense that
it has headers, then a line with nothing but a newline, then a body.

I *think* the body is optional, but the blank line before the
body is not -- check the code.   When I first wrote that part, I tried
to be conservative in the sense of making it a little harder to accidentally
commit with a log file other than the one you meant.

So, your "edit the log file" step *might* be messing up the syntax
of the log file in such a way that it doesn't pass muster.   Take
a peek at the code for certain picture, though.   Hopefully these
suggestions will make the code easier to read.

Thanks,
-t

Eric S. Raymond wrote:
> I'm trying to write a sample Arch session for a survey paper I'm
> working on, and failing.
>
> Here's my sequence of commands;
>

(Continue reading)

headers

Eric S. Raymond | 10 Jan 2008 03:32

Re: [Help-gnu-arch] Help composing a sample session

Thomas Lord <lord <at> emf.net>:
> As I recall, a valid log file is vaguely RFC822-ish in the sense that
> it has headers, then a line with nothing but a newline, then a body.

I don't think that's the problem, then.  Logfile attached.
--

-- 
		<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>

Summary: First commit
Keywords: 

This is a dummy commit message.

Summary: First commit
Keywords: 

This is a dummy commit message.

headers

Thomas Lord | 10 Jan 2008 05:22

Re: [Help-gnu-arch] Help composing a sample session

I dunno. If you want to track it down and find out what's really going on it should be easy to grep for the error message, run tla under gdb, set some breakpoints, and figure out how you got there (if not apparent from static inspection). I mean I know you know you can do all that -- I'm just adding the information that, at this late date, that's probably your best bet, sadly.

A guess? I dunno. Perhaps its bitrot. Andy has been quite gracefully and generously maintaining the grounds of Arch but they have, more or less, long lain fallow, afaict. Sorry you're finding troubles with it but it's (with all due respect to Andy and his caretaking) largely a long-dead project.

-t

Eric S. Raymond wrote:

Thomas Lord <lord <at> emf.net>:
As I recall, a valid log file is vaguely RFC822-ish in the sense that it has headers, then a line with nothing but a newline, then a body.
I don't think that's the problem, then. Logfile attached. Summary: First commit Keywords: This is a dummy commit message.

<div>
I dunno.&nbsp;&nbsp; If you want to track it down and find out what's really
going on it should be easy to grep for the error message, run tla under
gdb, set some breakpoints, and figure out how you got there (if not
apparent from static inspection).&nbsp;&nbsp; I mean I know you know you can do
all that -- I'm just adding the information that, at this late date,
that's probably your best bet, sadly.<br><br>
A guess?&nbsp; I dunno.&nbsp; Perhaps its bitrot.&nbsp; Andy has been quite gracefully
and generously maintaining the grounds of Arch but they have, more or
less, long lain fallow, afaict.&nbsp;&nbsp; Sorry you're finding troubles with it
but it's (with all due respect to Andy and his caretaking) largely a
long-dead project.<br><br>
-t<br><br><br><br>
Eric S. Raymond wrote:
<blockquote cite="mid20080110023256.GA28817 <at> thyrsus.com" type="cite">
  Thomas Lord <a class="moz-txt-link-rfc2396E" href="mailto:lord <at> emf.net">&lt;lord <at> emf.net&gt;</a>:

  <blockquote type="cite">
    As I recall, a valid log file is vaguely RFC822-ish in the sense that
it has headers, then a line with nothing but a newline, then a body.

  </blockquote>

I don't think that's the problem, then.  Logfile attached.

Summary: First commit
Keywords: 

This is a dummy commit message.

</blockquote>
<br>
</div>