[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: File with $Id$ not available from loginfo

From: Mark D. Baushke
Subject: Re: File with $Id$ not available from loginfo
Date: Tue, 13 Feb 2007 22:39:33 -0800

Hash: SHA1

<kevin.mcnamee@bredband.net> writes:

> # cvs --version
> Concurrent Versions System (CVS) 1.11.20 (client/server)
> Copyright (C) 2005 Free Software Foundation, Inc.

You may wish to consider moving to cvs 1.11.22 to get some bug fixes.

> # uname -a
> SunOS anna 5.10 Generic_118833-24 sun4u sparc SUNW,Sun-Fire-880
> I am running a script from the "loginfo" admin script which parses the
> checked in files for metadata. Normally, "loginfo" runs my script from a
> temporary location containing a checked out copy of the file (e.g.
> /tmp/serv1234) together with the accompanying "CVS" directory.
> The problem I am having is that if the checked in file contains the "$Id$"
> string, then the file does not appear in the directory where my script is
> running, (i.e. the usual temporary location with its "CVS" directory). This
> happens even if the file only contains "$Id$".
> Why does this occur? Is it a bug?

As near as I can tell, it has always been this way in cvs 1.11.x. It
happend right before the CVS/Entries file gets updated.

> Or is there another admin file I should be using to parse the committed
> file?

Most folks run a command like 'cvs -Qn status' on the file if they want
to know the new working revision and parse that information. I suppose a
more dangerous way to do it would be to read the CVS/Entries file, but I
really can not recommend that method.

Fwiw: I believe that the changes to allow digital signatures for cvs
1.12.14 will probably allow the updated file to exist in the
/tmp/serv1234/ directory like you expect. However, I have no good idea
when that release will be finished (the windows port is still broken).

        -- Mark
Version: GnuPG v1.4.6 (FreeBSD)


reply via email to

[Prev in Thread] Current Thread [Next in Thread]