To reduce the amount of manual intervention that's needed to create the GWN each week several existing scripts could be run from a cronjob which would mail their output to gwn-feedback@g.o. Ideally this cronjob would run on Gentoo hardware (raptor has been suggested) and it would run once a week. The scripts that need to be run are: gwn_bugzilla_report_en.py, get_glsas.py and the script that generates GuideXML for the package additions/removals that masterdriverz is working on. These scripts are (or will shortly be) available in the gentoo/src/gwn module. The box that these cronjobs will run on will need CVS (so that it can check out the latest versions of the scripts with anoncvs), dev-python/pyxml and some sort of MTA that's available from a cronjob. Here's the relevant (I hope) parts of last night's conversation in #g-infra: ... 00:03 <@robbat2laptop> tomk, why does that require too much interaction 00:03 <@robbat2laptop> mkdir foo && cd foo && cvs -d:pserver:anoncvs.g.o.... xyz 00:03 <@robbat2laptop> and then cvs up in your cronjob 00:03 <@robbat2laptop> that gets you the scripts fine 00:10 <@kingtaco|work> tomk, pong 00:11 <@kingtaco|work> which script is this? 00:13 < wolf31o2|mobile> it's the GWN scripts... and yeah, don't use 'pecker... 00:18 <@kingtaco|work> wolf31o2|mobile, what sort of "data" do they need access to? 00:18 < wolf31o2|mobile> for this script, glsa's 00:18 <@kingtaco|work> the glsa repo? 00:18 <@kingtaco|work> glsa.gentoo.org? 00:20 < wolf31o2|mobile> tomk can answer better, since I don't know... I know the glsa2gwn.py script requires the .xml files from the tree 00:22 < tomk> kingtaco|work: basically I need to run some of the scripts from gentoo/src/gwn and email the output to gwn-feedback from a cronjob 00:23 <@kingtaco|work> tomk, how often do these cron jobs happen? weekly? 00:23 < tomk> it'll fetch the glsa's from the net and I can make it do the same for the last glsa file too 00:23 < tomk> kingtaco|work: yeah weekly 00:24 < tomk> s/last glsa/last gwn/ 00:24 <@kingtaco|work> well, sounds like we could probably do it on raptor 00:24 < tomk> ok 00:25 <@kingtaco|work> can you put together a (meta) bug on what sort of things you need and how often they will happen? I'm assuming you have or will have more than one script and I'd like to keep them all together 00:25 < tomk> sure 00:25 <@kingtaco|work> cool 00:30 < tomk> kingtaco|work: does raptor have the gwn scripts from cvs regurlarly checked out on it? otherwise I'll go with robbat2laptop's suggestion of updating the scripts from cvs each time the cronjob runs 00:32 < tomk> and I'll most likely add it all to the same cronjob so that there's only one script to run each week 00:32 <@kingtaco|work> tomk, I wouldn't assume that raptor checks out everything 00:32 <@kingtaco|work> though I can't answer with certainty 00:35 < tomk> ok, in that case it'd probably make sense to check them out each time just in case there were any changes 00:35 <@kingtaco|work> would be sane 00:35 <@kingtaco|work> we can always remove the checkout if it's not necessarry 00:35 < tomk> yeah 00:37 < tomk> I haven't got a login on raptor, should I add that to the bug or would you want it to be run as a diffent user? 00:39 <@kingtaco|work> it'd be a different user 00:40 <@kingtaco|work> different ssh keys different blah 00:40 < tomk> ok 00:40 <@robbat2laptop> no boxes have global checkouts on them 00:41 <@robbat2laptop> if you want a portion of code, check out that part of the tree yourself 00:41 <@robbat2laptop> use anoncvs so it can run unattended 00:41 <@kingtaco|work> robbat2laptop, however raptor being the master sync probably checks out the files he's looking for 00:41 <@kingtaco|work> but yes, anoncvs is a good idea 00:50 <@kingtaco|work> tomk, anyway, would seem best to fetch your needed files from anoncvs, but we can remove that if it turns out they sync anyway 00:51 < tomk> kingtaco|work: agreed
I've got everything sorted for this, before the script will work Chris will need to check in the changes to various scripts in gentoo/src/gwn/ that I've mailed to him.
Created attachment 110765 [details] Mailer script
Created attachment 110766 [details] crontab
(In reply to comment #1) > I've got everything sorted for this, before the script will work Chris will > need to check in the changes to various scripts in gentoo/src/gwn/ that I've > mailed to him. > These patches have now been added, so everything's ready to go. What needs to happen: 1) find a suitable box for this to live on 2) create a new user and add them to the cron group 3) add the mailer script to their home dir and make it executable 4) add the attached crontab (after changing the path so it points to the new location of mail_gwn_script_output.sh) 5) profit!
Created attachment 128232 [details] mklastrites how to make last rites (req by tomk): - take one (1) package.mask - run `cvs diff -u -kk -w -D <dateoflastgwn> package.mask > ~/lastrites-$(date +Y%m%d).cvs` - manually fish out packages masked for removal (liberally add shots of b.g.o and gentoo-dev ml archive as needed), dice, cut, and paste into ~/lastrites-$(date +Y%m%d) three fields - cat/pkgname, dev name <email@gentoo.org>, and removal date (DD Mmm YYYY) - separated by tabs or colons. - run mklastrites - serve
Since GWN is dead, I'll close this bug.
