Updating CVS repo to UseNewInfoFmtStrings=yes

[Barry Hawkins]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Barry Hawkins wrote:
> Debian Java Maintainers Team,
>     I am sure (well, I hope ;-)) you have noticed a warning something
> like the following when committing your changes to your CVS modules:
[...]
> $ cvs commit
> [...]
> cvs commit: Using deprecated info format strings.  Convert your scripts
> to use
> the new argument format and remove '1's from your info file format strings.
> 
>     The provisional '1' was then removed from the loginfo script and
> committed.  After that, the next test commit from a module completed
> without any warnings, and no messages beyond those we were used to for
> the first 10 years ;-).
[...]
    Like most things, I managed to find that "one other thing" after
sending this.  My first couple of test commits went through without any
messages, but then a subsequent commit that involved adding and removing
files issued the warning again :-(.
    Our repository's CVSROOT/loginfo utilizes the cvs-mailcommit script,
and the syntax for invoking it has changed.  For good measure, I updated
to the current version of the script, then updated the invocation of it,
as directed by the cvs-commitmail man page:

Previous invocation in CVSROOT/loginfo (line may wrap):
ALL $CVSROOT/CVSROOT/cvs-mailcommit -m
pkg-java-commits at lists.alioth.debian.org --cvs %{sVv} --diff

Modified invocation in CVSROOT/loginfo (line may wrap):
CVSROOT/CVSROOT/cvs-mailcommit --mailto
pkg-java-commits at lists.alioth.debian.org --diff --root %r --dir %p %{sVv}

    I had added a --replyto argument to have replies sent to this list,
but then got rid of that and figured it best to keep the same headers.
Of course, now I haven't gotten any mail for my test commits, and after
three silent test commits, the original warning reappeared on the fourth
one.  So, if anyone has some insight on what might be wrong, I'd love to
know.  We are still able to use CVS, we just seem to still get the
annoying warnings and not receive commit mails.  I'll keep looking into
the issue.

Regards,
- --
Barry Hawkins
site: www.bytemason.org
weblog: www.yepthatsme.com

Registered Linux User #368650
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFDF+aAHuKcDICy0QoRAqRsAJ9rh1BUEMCcOI4XRjVB6cewt8zeRwCgjRKg
m7Rz8DRpMXLIZKSrnQssNG8=
=QgVd
-----END PGP SIGNATURE-----