Re: Tip: restoring your CVS access to savannah

Stefan Monnier wrote:

>>The scripts in question are scripts used by the CVS server on
>>savannah, the page that you cited explains that.  The savannah
>>maintainers said simply to disregard these messages, as they will go
>>away when they (the maintainers) fix those scripts at some later date.
>>    
>>
>
>Yes, the real problem is that the CVS authors messed up this message
>pretty badly: it should be sent to the cvs-admin, not the cvs-user.  Or (in
>case sending it to the cvs-admin is not possible) it should at least use
>a different wording that takes into account the fact that it's talking to
>a cvs-user and not a cvs-admin.
>I can't help but be reminded of the proverbial "unsubscribe" message sent to
>thousands of helpless mailing-list members.
>  
>

That particular message was my fault, and perhaps I could have worded it 
better, but it was intentionally noisy to encourage admins to upgrade 
their scripts to be compatible with the new and more reliable trigger 
API.  Perhaps I shouldn't have been quite so draconian, but the fix is 
easy:  the admins just need to tweak their scripts to handle the new 
loginfo argument format (info about a single file is sent as three 
arguments rather than as a single comma delimited argument and filenames 
with spaces are now quoted properly), then flip a few switches in their 
config files.  If the loginfo script isn't getting revision numbers 
anyhow but only filenames (and, IIRC, this is the case with the savannah 
loginfo, or at least was several months ago when I looked) then the 
config file switches may only need to be thrown (no script changes would 
be necessary).

Derek

-- 
Derek R. Price
CVS Solutions Architect
Get CVS support at Ximbiot <http://ximbiot.com>!
v: +1 717.579.6168
f: +1 248.879.8695
<mailto:[email protected]>