bz*.py project

[Pierre Habouzit]

this afternoon, I've been hacking around, two small scripts, that allow 
us to make the most of bts usertags to track the KDE bugzilla status 
directly on our lovely BTS. (ala malone).

The flood of mail on debian-qt-kde at lists.d.o is due to the first early 
runs of those scripts, and that should not happen ever again, I'm sorry 
for that.

anyway, I've on my people.debian.org page a form that crafts URL to 
query the BTS about the current status of forwarded bugs [1]. Just 
leave the name of a source package, and you'll see the report for that 
source package. e.g. [2] for kdebase.

That means that before an upload, this gives a good idea of the bugs 
that should be fixed with the upload (we only have to check for every 
Fixed/Resolved bug if it has been pulled or not).


What it needs to work ?
~~~~~~~~~~~~~~~~~~~~~~~

 (1) bzsync.py is able to resync tags with the KDE bugzilla.

     ./bzsync.py http://bugs.kde.org/NNNNNN
 
     is able to find out if a debian bug is already forwarded to NNNNNN
     and will sync its tags with it (that's the script that flooded).

     ./bzsync.py nnn http://bugs.kde.org/NNNNNN

     force nnn to be forwarded to http://bugs.kde.org/NNNNNN
     and sync tags

 (2) bzlink.py also uses the mail notifications to incrementaly update
     our states. It currently takes a mail on stdin, and does the
     adequate changes.

     the script is currently not hooked into our pkg-kde-bugs-fwd list,
     and won't be as is anyway (see in How it works for reasons).

How it works
~~~~~~~~~~~~

  I use the bts2ldap gateway to be able to guess (asking for a bug that
  is forwarded to http://bugs.kde.org/NNNNNN) which debian#nnn corrspond
  to a KDE#NNN. bts2ldap is synchronized with 15 to 60minutes of delay.
  So we cannot process Bugzillas mails live.

  Also, it still needs us to create new bugs entries manually, and NOT
  TO FORGOT to add pkg-kde-bugs-wfd in the Cc:

  The script is also stupid wrt "duplicates" it does not try to follow
  duplicate bugs, and forward has to be corrected (using bzsync)
  manually.

Future Work
~~~~~~~~~~~

 Near future:

  * make the script less verbose (I don't want to spam debian-qt-kde
    again ...) => thanks dato for the ideas to reduce that.

  * make bzlink.py work either on stdin, OR on a mailbox (that should be
    trivial in python IIRC)

  * setup a mailbox subscribed to pkg-kde-b-fwd, that will be rotated
    each hour, and processed when the next is rotated (to have the
    necessary 1 hour delay).

  * make bzsync.py ensure that pkg-kde-bugs-fwd is in the Cc:

 Medium term Future:

  * fix the bad behaviour on Duplicate closings.

  * find a way to submit a bug report into bugs.kde.org automatically.
    with user interaction if needed. I suppose this is doable with an
    expect script that works on top of links quite easily.
    (yes this is ugly, I know, but I've no better idea atm)

  * have the bz*.py scripts in a good-enough shape to propose that to
    other projects whose upstream has a bugzilla.
    => bzlink.py has been written in that spirit.
    => bzsync.py is more kde-dependant atm


[1] http://people.debian.org/~madcoder/
[2] http://tinyurl.com/jf6h9
-- 
·O·  Pierre Habouzit
··O                                                madcoder at debian.org
OOO                                                http://www.madism.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.alioth.debian.org/pipermail/pkg-kde-talk/attachments/20060418/b4b8804d/attachment.pgp