[Savannah-hackers] [support #102705] no commit email

[Elfyn McBratney]

This mail is an automated notification from the support tracker
 of the project: Savannah Administration.

/**************************************************************************/
[support #102705] Latest Modifications:

Changes by: 
                Elfyn McBratney <address@hidden>
'Date: 
                Thu 07/01/2004 at 11:10 (Europe/London)

------------------ Additional Follow-up Comments ----------------------------
Karl, and everyone else that's watching this tracker, you can now have the 
bells and whistles.  Until we have a front-end up we'll be installing it for 
anyone that asks.

So if you want those nice 'n' shiny commit logs, send the following info to 
address@hidden:

  - project (system) name
  - regular expression to match against
  - possible module name
  - email address to send commit logs to
  - possible email address to send diffs to

and we'll get it installed and set-up for your project.






/**************************************************************************/
[support #102705] Full Item Snapshot:

URL: <http://savannah.gnu.org/support/?func=detailitem&item_id=102705>
Project: Savannah Administration
Submitted by: Mark Wielaard
On: Mon 01/05/2004 at 15:00

Category:  None
Priority:  7 - High
Severity:  5 - Average
Resolution:  None
Assigned to:  beu
Originator Email:  
Status:  Open


Summary:  no commit email

Original Submission:  Hi,

I and several other Classpath hackers have gotten strange cvs server messages 
on cvs commit like:

Cannot open file </var/run/log_accum/#classpath.lastdir.8481 No such file or 
directory.

Cannot open file </var/run/log_accum/#classpath.lastdir.25663 No such file or 
directory.

The commit itself seems to succeed, but no email is send about the commit 
message to the mailinglist. So it probably is related.

Thanks,

Mark

Follow-up Comments
------------------


-------------------------------------------------------
Date: Thu 07/01/2004 at 11:10       By: beu
Karl, and everyone else that's watching this tracker, you can now have the 
bells and whistles.  Until we have a front-end up we'll be installing it for 
anyone that asks.

So if you want those nice 'n' shiny commit logs, send the following info to 
address@hidden:

  - project (system) name
  - regular expression to match against
  - possible module name
  - email address to send commit logs to
  - possible email address to send diffs to

and we'll get it installed and set-up for your project.

-------------------------------------------------------
Date: Sun 06/27/2004 at 13:50       By: karl
Hi Elfyn -- thanks for the response.

i'll be glad when and if savannah can offer email updates again, but it's no 
longer critical for me.  i couldn't wait any longer, so i implemented it a 
while ago for my projects by creating a checked-out tree exactly for this 
purpose, and running a cron job that does (basically) cvs diff and cvs update 
every few minutes.

This doesn't have all the bells and whistles possible with logreport, 
cvsreport, etc., but it works well enough.

I wrote Mark and some of the others on this thread about this when I did it.  
If you have any interest in documenting this for other savannah users, the 
script is trivial:
#!/bin/sh
cvs -z1 -q diff -rBASE -rHEAD -c 2>&1 | egrep -v "tag BASE is not in|chroot 
failed|end of file from server|ssh_exchange_identification"
cvs -z1 -q up -P 2>&1 | egrep -v "chroot failed|end of file from 
server|ssh_exchange_identification"

and the cron entry looks like this:
22,44 * * * * cd $HOME/src/texinfo-cvs && $HOME/bin/cvsdiff 2>/dev/null | 
$HOME/bin/mail-if-nonempty -s "texinfo update (`date`)" address@hidden

Cheers,
karl


-------------------------------------------------------
Date: Sun 06/27/2004 at 11:27       By: mark
Thanks for looking into this.
We have lots of active developers and manually posting commit messages is a bit 
of a pain (we do that now since we want to keep on top of who is working on 
what and not get a surprize when doing a cvs update about a patch that was or 
wasn't committed yet). Any way to automatically get CVS commit messages to the 
address@hidden mailinglist again would be really appreciated.

-------------------------------------------------------
Date: Fri 06/25/2004 at 18:28       By: beu
Apologies for the lack of response.  As I don't get notifications for when 
trackers are updated it's hard to keep track of things.

I'll download logreport and cvsreport but getting them to work on Savannah is 
not going to be easy as the current strategy is to compile perl scripts into 
binary using perlcc (something I disagree with but never the less is what's 
being used).

For the moment commit_prep and log_accum are installed and have been working 
well for the `emacs' project for a couple of weeks.

I will discuss with other Savannah hackers about installing log_accum et al. on 
a case by case basis until we have front-end set-up where users can do this 
themselves.

-------------------------------------------------------
Date: Sat 05/01/2004 at 12:26       By: None
"- log_accum
- commit_prep"

These programs have a long history of brokeness, I strongly suggest to use 
cvsreport, maintained by Vincent Caron, instead. 

Mathieu Roy
Regards,


-------------------------------------------------------
Date: Tue 04/27/2004 at 00:31       By: karl
Thank you very much for the update!  It's nice to know it's being worked on.  
By the way, when I was investigating this in other contexts, logreport seemed 
like the nicest reporting script ...

I'd just like to mention for anyone who might be tracking this that in the 
meantime, I've set up simple cron jobs on fencepost that do a cvs diff on my 
projects once an hour or so.  Not great, but better than nothing ...


-------------------------------------------------------
Date: Mon 04/26/2004 at 20:38       By: beu
Sysadmins and savannah-hackers are still working on getting these features back 
up-and-running.

As far as I know, what remains to be done is:

 - log_accum
 - commit_prep

Once the first two are finished, we should be able to start enabling on-commit 
emails.

Note also, that, `CVSROOT/' is no longer writable by users (we will be starting 
work on frontend's to manage CVS administravia soon). 

I have opened a task in the Administration project (task #3284) to track our 
progress on this issue.

-------------------------------------------------------
Date: Fri 04/09/2004 at 13:47       By: karl
commit email is not working for me, either, ever since the crack.  (ticket 
102736)  i seem from the comments in this ticket that progress is being made, 
so i thought i'd ask yet again.

my problem is different than mark's, but the result is the same, no commit 
email.  when i try to commit loginfo in the texinfo or gnulib projects, i get:
/cvsroot/gnulib/CVSROOT/loginfo,v  <--  loginfo
new revision: 1.2; previous revision: 1.1
cvs [server aborted]: could not open lock file 
`/cvsroot/gnulib/CVSROOT/,loginfo,': Permission denied

if you want me to open another ticket, of course that's fine. there are already 
tons of other unresolved tickets on the subject, like 102376.  (which is 
closed, but not fixed.)

thanks.

-------------------------------------------------------
Date: Thu 04/08/2004 at 22:31       By: Beuc
Sysadmins are currently working on putting back scripts for CVS in the chroot 
environnement.

-------------------------------------------------------
Date: Thu 04/08/2004 at 21:57       By: beu
Hi Mark,

Is this still an issue?

-------------------------------------------------------
Date: Thu 04/01/2004 at 23:14       By: mark
The error messages that I get from the CVS server are a bit different now BTW:

Checking in ChangeLog;
/cvsroot/classpath/classpath/ChangeLog,v  <--  ChangeLog
new revision: 1.1971; previous revision: 1.1970
done
Cannot open file >>/var/run/log_accum/#classpath.files.changed.0.2084.
Checking in javax/swing/JViewport.java;
/cvsroot/classpath/classpath/javax/swing/JViewport.java,v  <--  JViewport.java
new revision: 1.6; previous revision: 1.5
done
Cannot open file >>/var/run/log_accum/#classpath.files.changed.0.2084.

I see that the following was added to out CVSROOT/loginfo file last month:

revision 1.2
date: 2004/03/03 21:31:56;  author: root;  state: Exp;  lines: +1 -0
Added log_accum line.

Which added the following line:

+DEFAULT /bin/log_accum -T classpath -C -m address@hidden -s %{sVv}

This seems to not work properly.

Where can I find this log_accum script?

-------------------------------------------------------
Date: Mon 03/29/2004 at 11:52       By: mark
Commit messages are still not going to the address@hidden mailinglist as they 
should.

Is there any progress on this issue?
Can I do or check something to help fix this faster?

Since we have a rather large developer base it is pretty essential that we can 
easily see when who commits what.

-------------------------------------------------------
Date: Tue 01/13/2004 at 23:47       By: mark
The error message are not shown since the new savannah setup.

But we are still missing CVS commit email messages to the mailinglist, which we 
are really missing since it is a way to check and coordinate each others work.

-------------------------------------------------------
Date: Sat 01/10/2004 at 18:21       By: rudy
Are you still having this problem?

-------------------------------------------------------
Date: Mon 01/05/2004 at 15:00       By: yeupou
This item has been reassigned from the project Savannah support tracker to your 
tracker.

The original report is still available at support #102638

Following are the information included in the original report:

[field #0] <font class="preinput"><font class="help" title="Unique item 
identifier">Item ID: </font></font> 102638<br>[field #1] <font 
class="preinput"><font class="help" title="Unique project identifier">Group ID: 
</font></font> 11<br>[field #2] <font class="preinput"><font class="help" 
title="Current Status">Status: </font></font> Open<br>[field #3] <font 
class="preinput"><font class="help" title="Impact of the item on the system 
(Critical, Major,...)">Severity: </font></font> 5 - Average<br>[field #4] <font 
class="preinput"><font class="help" title="Generally high level modules or 
functionalities of the software (e.g. User interface, Configuration Manager, 
etc)">Category: </font></font> CVS Server<br>[field #5] <font 
class="preinput"><font class="help" title="User who originally submitted the 
item">Submitted by: </font></font> mark<br>[field #6] <font 
class="preinput"><font class="help" title="Who is in charge of handling the 
item">Assigned to: </font></font>
zerodeux<br>[field #7] <font class="preinput"><font class="help" title="Date 
and time of the initial submission">Submitted on: </font></font> Fri 11/28/03 
at 22:13<br>[field #8] <font class="preinput"><font class="help" title="One 
line description of the item">Summary: </font></font> Strange cvs server 
message and no commit email<br>[field #9] <font class="preinput"><font 
class="help" title="Full description of the item">Original Submission: 
</font></font> Hi,
<br />

<br />
I and several other Classpath hackers have gotten strange cvs server messages 
on cvs commit like:
<br />

<br />
Cannot open file </var/run/log_accum/#classpath.lastdir.8481 No such file or 
directory.
<br />

<br />
Cannot open file </var/run/log_accum/#classpath.lastdir.25663 No such file or 
directory.
<br />

<br />
The commit itself seems to succeed, but no email is send about the commit 
message to the mailinglist. So it probably is related.
<br />

<br />
Thanks,
<br />

<br />
Mark<br>[field #11] <font class="preinput"><font class="help" 
title="Characterizes the nature of the item (e.g. Crash Error, Documentation 
Typo, Installation Problem, etc">Item Group: </font></font> None<br>[field #12] 
<font class="preinput"><font class="help" title="Current resolution of the 
item">Resolution: </font></font> None<br>[field #13] <font 
class="preinput"><font class="help" title="Version of the System Component 
impacted by the item">Component Version: </font></font> None<br>[field #14] 
<font class="preinput"><font class="help" title="Name and version of the 
platform impacted by the item">Platform Version: </font></font> None<br>[field 
#15] <font class="preinput"><font class="help" title="How easy it is to 
reproduce the item">Reproducibility: </font></font> None<br>[field #16] <font 
class="preinput"><font class="help" title="Estimated size of the code to be 
developed or reworked to handle the item">Size (loc): </font></font> 
None<br>[field #17] <font
class="preinput"><font class="help" title="Release in which the item was 
actually implemented">Fixed Release: </font></font> None<br>[field #18] <font 
class="preinput"><font class="help" title="Release in which it is planned to 
have the item implemented">Planned Release: </font></font> None<br>[field #19] 
<font class="preinput"><font class="help" title="Number of hours of work needed 
to handle the item">Effort: </font></font> 0.00<br>[field #23] <font 
class="preinput"><font class="help" title="How quickly the item should be 
implemented (Immediate, Normal, Low, Later,...)">Priority: </font></font> 3 - 
Low<br>[field #26] <font class="preinput"><font class="help" title="">Percent 
Complete: </font></font> 0%<br>[field #28] <font class="preinput"><font 
class="help" title="Release (global version number) impacted by the 
item">Release: </font></font> None<br>[field #53] <font class="preinput"><font 
class="help" title="Customizable Select Box (pull down menu with
predefined values)">Custom Select Box #1: </font></font> None<br>[field #54] 
<font class="preinput"><font class="help" title="Customizable Select Box (pull 
down menu with predefined values)">Custom Select Box #2: </font></font> 
None<br>[field #55] <font class="preinput"><font class="help" 
title="Customizable Select Box (pull down menu with predefined values)">Custom 
Select Box #3: </font></font> None<br>[field #56] <font class="preinput"><font 
class="help" title="Customizable Select Box (pull down menu with predefined 
values)">Custom Select Box #4: </font></font> None<br>[field #57] <font 
class="preinput"><font class="help" title="Customizable Select Box (pull down 
menu with predefined values)">Custom Select Box #5: </font></font> 
None<br>[field #58] <font class="preinput"><font class="help" 
title="Customizable Select Box (pull down menu with predefined values)">Custom 
Select Box #6: </font></font> None<br>[field #59] <font class="preinput"><font 
class="help"
title="Customizable Select Box (pull down menu with predefined values)">Custom 
Select Box #7: </font></font> None<br>[field #60] <font class="preinput"><font 
class="help" title="Customizable Select Box (pull down menu with predefined 
values)">Custom Select Box #8: </font></font> None<br>[field #61] <font 
class="preinput"><font class="help" title="Customizable Select Box (pull down 
menu with predefined values)">Custom Select Box #9: </font></font> 
None<br>[field #62] <font class="preinput"><font class="help" 
title="Customizable Select Box (pull down menu with predefined values)">Custom 
Select Box #10: </font></font> None<br>




CC List
-------

CC Address                          | Comment
------------------------------------+-----------------------------
beu                                 | Elfyn McBratney









For detailed info, follow this link:
<http://savannah.gnu.org/support/?func=detailitem&item_id=102705>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/