From rsiemsen at rossvideo.com  Thu May  1 14:39:44 2008
From: rsiemsen at rossvideo.com (Ralph Siemsen)
Date: Thu, 01 May 2008 10:39:44 -0400
Subject: [cvsspam-devel] Heads up: oddity under Fedora 8
In-Reply-To: <4816117E.8050903@rossvideo.com>
References: <4816117E.8050903@rossvideo.com>
Message-ID: <4819D630.30306@rossvideo.com>

Ralph Siemsen wrote:

> I reverted back to cvs-1.11.22-6.fc6 while keeping everything else at 
> Fedora 8 version, and this appears to "solve" the problem.  It looks 
> like Fedora added some patches which interfere with cvsspam operation. 
> Specifically, the patch for fedora bugs #277501 and #242049 looks like 
> it might be relevant.

I have now confirmed that the cvs-1.11.22-diff-rm.patch seems to be 
responsible for the new behaviour.  Removing this patch from the F-8 
version of CVS eliminates the "cvs diff" warnings and restores the 
proper CVSspam content in the email it sends.

I will try to discuss this with the relevant Fedora folk.

-R



From rsiemsen at rossvideo.com  Tue May 20 19:25:24 2008
From: rsiemsen at rossvideo.com (Ralph Siemsen)
Date: Tue, 20 May 2008 14:25:24 -0400
Subject: [cvsspam-devel] Heads up: oddity under Fedora 8
In-Reply-To: <4819D630.30306@rossvideo.com>
References: <4816117E.8050903@rossvideo.com> <4819D630.30306@rossvideo.com>
Message-ID: <48331794.3040005@rossvideo.com>

Ralph Siemsen wrote:

> I will try to discuss this with the relevant Fedora folk.

Reported it: https://bugzilla.redhat.com/show_bug.cgi?id=447595

Surprised that nobody else has run across this problem...

-R


From ksrao at ikanos.com  Fri May 23 01:42:17 2008
From: ksrao at ikanos.com (K Srinivasa Rao)
Date: Fri, 23 May 2008 00:42:17 -0000
Subject: [cvsspam-devel] Problem in CVSSpam Documentation
Message-ID: <36CEBF441756E04FABB5A4C5E9744D2209232B@GALLUS.india.ikanos.com>

Hi CVSSpam Developers,

 

At the outset, I want to thank you for providing the simple and cool
cvsspam utility.

 

I am using 0.2.12 version (the latest as of now)

In the documentation, section Installation --> Configuring CVS (Page 4)
there is the line mentioning

 

# Always allow commits to CVSROOT

^CVSROOT /bin/cat>/dev/null

 

This is a good warning, presumably where the commit checks fail and we
should not end up unable to edit the CVSROOT files.

But if this line is added to <commitinfo> file, the following error
arose for me

 

cvs server: cannot find pre-commit filter `/bin/cat>/dev/null': No such
file or directory

cvs server: Pre-commit check failed

 

After this, I had to manually change the <commitinfo> file in the CVS
server.

I think the better option is the following (though CVS dislikes commands
that do not consume their standard input)

 

# Always allow commits to CVSROOT

^CVSROOT /bin/true

 

You may please think about this. Since had Admin privileges on the
server, I could edit it.

Otherwise, it would have created a minor problem with commits failing.

 

T h a n k Y o u,

KSR

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.badgers-in-foil.co.uk/pipermail/cvsspam-devel/attachments/20080523/113ca935/attachment.htm