Re: Serializing transitions
On Tue, 30 Mar 2010, Raphael Hertzog wrote:
> X-Debbugs-Cc and a script should be more than enough, you can
> certainly parse the pseudo-headers to find out the packages and the
> version. And when you report the bug, you can add a custom
> pseudo-header "Arch" that the BTS would ignore but that your script
> would use.
Another method is that you can use usertags to set a tag that
corresponds to a wannabuild db index (with a specific user) and then
query the bts for that at some later point in time.
You can handle architectures in a similiar fashion if you want.
For example:
Source: foo
Severity: serious
User: wannabuild@buildd.debian.org
UserTags: wannabuildid-12345, wannabuildarch-i386
then after a suitable wait (or perhaps in a cron job which looked for
filed bugs which didn't have a bug # associated):
bts select users:wanabuild@buildd.debian.org tag:wannabuildid-12345
would return the bug using the soap interface. [There is a planned
feature called uservalues which would make this slightly more elegant,
but i haven't completed it yet.]
Don Armstrong
--
Identical parts aren't.
-- Beach's Law
http://www.donarmstrong.com http://rzlab.ucr.edu
Reply to: