Re: Testing-watch emails
On Sat, Nov 05, 2005 at 12:17:29AM +0100, Henning Makholm wrote: Scripsit Steve Langasek [EMAIL PROTECTED] If you're interested in making this happen I'll be happy to give you any info I can; 2) Any advice on how to test patches to ftp-master code before submitting them? My own scripts I can dry-run by substituting a dummy command for sendmail and run them in the very place where they will eventually function. In contrast, construcing a test mock-up of the ftp-master environment to do test runs of a patched britney appears to be highly nontrivial. Does some automation for this purpose exist? Or what do ftpmaster/release gurus do when you change code? Heh, so I guess the only info I can offer you is to say that no, there's no particularly useful automation for this... creating a copy of the ftp-master env is non-trivial, yes, but it's also the only real option, AFAIK. :) -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ signature.asc Description: Digital signature
Re: Testing-watch emails
On Sat, 2005-11-05 at 00:17 +0100, Henning Makholm wrote:
Scripsit Steve Langasek [EMAIL PROTECTED]
If you're interested in making this happen I'll be happy to give
you any info I can;
OK, here are some questions.
1) The copy of britney in merkel:/org/ftp.debian.org/ does not seem
to be synced regularly. Is there a place where one can see the
current code? It's not in the dak cvs (which appears to be
out-of-date wrt the merkel mirror anyway), and I tried poking
around on {cvs,svn,arch}.debian.org to no avail.
http://ftp-master.debian.org/testing/update_out_code/ is the official
current code, afaik. From time to time, there may be other versions
floating around - there's a least one in ~ajt on ftp-master currently.
3) Do you (or somebody in QA who reads this) happen to know how the
'keyword' under which the PTS forwards emails is transmitted? I
cannot find any code in katie that sets this. Does the PTS analyse
subject lines for fixed patterns?
[EMAIL PROTECTED] is subscribed to -devel-changes and processes
the mails in real-time.
http://cvs.debian.org/pts/?cvsroot=qa is useful here.
http://wiki.debian.org/qa.debian.org/pts is linked from the front page
of p.qa.d.o, and contains a link to a presentation Raphael Hertzog
(buxy) made about the PTS.
(Currently I'm extrapolating from the documented
[EMAIL PROTECTED] syntax, but I'm not sure
that is the Right Thing to do).
I'm not sure this is the right list to ask on, what with this being
technical matters rather than a flamewar. :-) Feel free to move to
somewhere appropriate, cc'ing me.
In terms of the PTS, either asking buxy directly or [EMAIL PROTECTED] usually
works. britney and other ftp-master related topics are probably most
appropriate on [EMAIL PROTECTED], imho.
Adam
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Testing-watch emails
Scripsit Adam D. Barratt [EMAIL PROTECTED] On Sat, 2005-11-05 at 00:17 +0100, Henning Makholm wrote: [Context for debian-dak readers who are not following the thread in -devel: I am trying to get up to speed on how to contribute some code to ftp-master that mails out testing migration notices.] 1) The copy of britney in merkel:/org/ftp.debian.org/ does not seem to be synced regularly. Is there a place where one can see the current code? http://ftp-master.debian.org/testing/update_out_code/ is the official current code, afaik. I didn't know that URL; thanks. Unfortunately it not exactly what I looked for; it corresponds to merkel:/org/ftp.debian.org/testing/update_out/*, whereas I think that the place I need to hook in is the shell script merkel:/org/ftp.debian.org/testing/britney in the parent directory. The sarge-is-frozen announcement [1] seemed to imply that these things were all under version control, but I may read that wrongly. Upon further investigation it looks like the freezing would actually be effeceted by adding a hint rather than commiting a change to the code. [1] http://lists.debian.org/debian-devel-announce/2005/05/msg1.html 2) Any advice on how to test patches to ftp-master code before submitting them? My own scripts I can dry-run by substituting a dummy command for sendmail and run them in the very place where they will eventually function. In contrast, construcing a test mock-up of the ftp-master environment to do test runs of a patched britney appears to be highly nontrivial. Does some automation for this purpose exist? Or what do ftpmaster/release gurus do when you change code? 3) Do you (or somebody in QA who reads this) happen to know how the 'keyword' under which the PTS forwards emails is transmitted? I cannot find any code in katie that sets this. Does the PTS analyse subject lines for fixed patterns? http://cvs.debian.org/pts/?cvsroot=qa is useful here. Thanks. Now I can se what happens. It does indeed use ad-hoc analysis of subject lines. [EMAIL PROTECTED] is subscribed to -devel-changes and processes the mails in real-time. Not quite, afaict; katie sends email directly to packagename@p.qa.d.o (config setting Dinstall::TrackingServer). Then the PTS's dispatch.pl script recognizes the X-Katie header and then pattern-matches the subject to decide on a keyword. britney and other ftp-master related topics are probably most appropriate on [EMAIL PROTECTED], imho. I assume you mean [EMAIL PROTECTED] - yes, that looks relevant. Cc:ing and setting M-F-T. -- Henning MakholmThere is a danger that curious users may occasionally unplug their fiber connector and look directly into it to watch the bits go by at 100 Mbps. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Testing-watch emails
Scripsit Steve Langasek [EMAIL PROTECTED] On Thu, Nov 03, 2005 at 12:05:07AM +0100, Henning Makholm wrote: I have now a frst draft of a status-change mail system running. it works from the archive mirror on merkel, [...] Thanks for running with this. Ideally, we would get this integrated on ftp-master, so that the mails could be triggered by britney rather than being done post-hoc; this would also let us associate package removals with comments from britney hints files, so that they could be incorporated into the mails. If you're interested in making this happen I am. Also, I have gotten a couple of complaints that people want the mails to be more easily procmailable. If they had katie instead of me as sender, they would have a better chance of matching people's existing recipies for routine Debian notices. It seems that integrating it *properly* would involve learning Python, (which won't happen this week or next), but less might work, too. I'll be happy to give you any info I can; though tbh, if I understood this part of the system very well, I probably would have written a patch myself already. ;) I think that doing post-hoc analysis (perhaps on Sources files, perhaps on cached HeidiResult files) is still a more robust architecture than trying to hook into britney's actual decision-making. Britney itself doesn't remember the hint comments anyway, we'll need to do some heuristic parsing of the hints files separately to extract removal reasons. -- Henning MakholmManden med det store pindsvin er kommet vel ombord i den grønne dobbeltdækker.
Testing-watch emails
Scripsit Steve Langasek [EMAIL PROTECTED]
If you're interested in making this happen I'll be happy to give
you any info I can;
OK, here are some questions.
1) The copy of britney in merkel:/org/ftp.debian.org/ does not seem
to be synced regularly. Is there a place where one can see the
current code? It's not in the dak cvs (which appears to be
out-of-date wrt the merkel mirror anyway), and I tried poking
around on {cvs,svn,arch}.debian.org to no avail.
2) Any advice on how to test patches to ftp-master code before
submitting them? My own scripts I can dry-run by substituting a
dummy command for sendmail and run them in the very place where
they will eventually function. In contrast, construcing a test
mock-up of the ftp-master environment to do test runs of a patched
britney appears to be highly nontrivial. Does some automation for
this purpose exist? Or what do ftpmaster/release gurus do when you
change code?
3) Do you (or somebody in QA who reads this) happen to know how the
'keyword' under which the PTS forwards emails is transmitted? I
cannot find any code in katie that sets this. Does the PTS analyse
subject lines for fixed patterns?
(Currently I'm extrapolating from the documented
[EMAIL PROTECTED] syntax, but I'm not sure
that is the Right Thing to do).
I'm not sure this is the right list to ask on, what with this being
technical matters rather than a flamewar. :-) Feel free to move to
somewhere appropriate, cc'ing me.
--
Henning Makholm This imposes the restriction on any
procedure statement that the kind and type
of each actual parameter be compatible with the
kind and type of the corresponding formal parameter.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
