trans-coord-devel
[Top][All Lists]
Advanced

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

Re: The `sync' rule is not robust; expected to fail tonight


From: Yavor Doganov
Subject: Re: The `sync' rule is not robust; expected to fail tonight
Date: Mon, 04 Feb 2008 15:55:57 +0000

On пн, 2008-02-04 at 17:34 +0200, Kaloian Doganov wrote:
> This is true, but so far we have not decided how to implement this,
> neither we have decided what we want and what we don't want to be
> mailed.  

So?  I want warnings like this one to be mailed to this list, errors if
make-prototype fails to www-discuss + here, and errors for invalid PO
files to trans-coord-discuss (+ here).  The rules have to be amended for
the latter two, but we could do the first one right now.

Or we can do it now, and later change to do something different.  I
don't think it's that important right now, given the fact that something
has to be installed before 23:10 EET.

> I suggest to keep things to one session transcript, for now.

This is not possible, since there are three jobs running at different
time and different commands (whatsnew, sync and the gnun build).  I am
deliberately suppressing the sync one, because the output is not really
helpful.

>     I prefer an explicit mail for this, personally.
> 
> Why?

Because it is easier to spot it.  I don't think that it is useful to
receive this every day:

template_translated
= ../../server/banner.bg.html ../../server/banner-homepage.bg.html 
../../server/footer-text.bg.html ../../server/banner.fr.html 
../../server/banner-homepage.fr.html ../../server/footer-text.fr.html
home_translated
= ../../home.bg.shtml ../../home.pl.shtml ../../home.zh-cn.shtml
ALL_POTS
= ../../gnu/po/gnu.pot ../../gnu/po/rms-lisp.pot ../../philosophy/po/bdk.pot 
../../philosophy/po/eldred-amicus.pot ../../philosophy/po/java-trap.pot 
../../philosophy/po/philosophy.pot ../../philosophy/po/schools.pot 
../../philosophy/po/sun-in-night-time.pot ../../po/keepingup.pot 
../../po/provide.pot
articles_translated
= ../../philosophy/java-trap.bg.html ../../philosophy/schools.bg.html 
../../philosophy/sun-in-night-time.bg.html
make: Entering directory
`/srv/data/home/y/yavor/projects/trans-coord/gnun/prep/gnun'
for file in home.shtml server/banner.html server/banner-homepage.html
server/footer-text.html gnu/gnu.html gnu/rms-lisp.html
philosophy/bdk.html philosophy/eldred-amicus.html
philosophy/java-trap.html philosophy/philosophy.html
philosophy/schools.html philosophy/sun-in-night-time.html keepingup.html
provide.html ; do \
          cp -p --update ../../../../www/$file ../../$file ; done
cd ../.. ; \
          cvs commit -m "Automatic sync from the master www repository."
cvs commit: Examining .
cvs commit: Examining gnu
cvs commit: Examining gnu/po
cvs commit: Examining philosophy
cvs commit: Examining philosophy/po
cvs commit: Examining po
cvs commit: Examining prep
cvs commit: Examining prep/gnun
cvs commit: Examining server
cvs commit: Examining server/po
make: Leaving directory
`/srv/data/home/y/yavor/projects/trans-coord/gnun/prep/gnun'

At least it won't be useful for me...

>   There is nothing wrong if we do not react ASAP on such warning.

...and I might ignore the warning, whether urgent/important or not.

> This could happen by accident.

True, but if it happens by accident, don't fear the flood -- I'm at the
moderating dike.  No reason to worry about that.

(Alternatively, let's use $(CVSSKIP) before `mail -s ...' and let cron
run `make sync VCS=yes'?)





reply via email to

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