Log of /scripts/bzlink.py

---

Revision 3566 - (view) (download) (as text) (annotate) - [select for diffs]
Modified Mon Apr 17 16:19:02 2006 UTC (7 years, 1 month ago) by madcoder
File length: 5248 byte(s)
Diff to previous 3565 , to selected 3564

a lot of work done, I am now able to create the correct mail to send to
the BTS/control@bugs.d.o



just have to send it now

---

Revision 3565 - (view) (download) (as text) (annotate) - [select for diffs]
Modified Mon Apr 17 15:03:09 2006 UTC (7 years, 1 month ago) by madcoder
File length: 3357 byte(s)
Diff to previous 3564

Use aba's bts2ldap gateway to guess the debian bug that is related to our
KDE one.


Now, I have: the changes of the kde bugs, the additional comments of the
kde bugs, and the debian bug. let the fest begin !

---

Revision 3564 - (view) (download) (as text) (annotate) - [selected]
Modified Mon Apr 17 14:36:10 2006 UTC (7 years, 1 month ago) by madcoder
File length: 2535 byte(s)
Diff to previous 3563

 * Fix blocks regexp: we don't want to catch full '------' lines.
 * Now parse the "modifications" block (which is what we really want to track
   the bugzilla current bug status !)


Now the cool hacks can begin. I'm thinking of:
 * using BTS usertags to keep track of bugs.kde.org bugs status.
 * automatically append additional comments to the debian bug report.

I also have to think of a way to map KDE #bugs to BTS ones. Since we can't
tag bugs.kde.org ones, we can only use the "forwarded" stats of our
bugs to have the mapping done. I guess this can be easily done by greping
into the debbugs DB, or by querying aba's ldap.

---

Revision 3563 - (view) (download) (as text) (annotate) - [select for diffs]
Added Mon Apr 17 14:12:07 2006 UTC (7 years, 1 month ago) by madcoder
File length: 1939 byte(s)
Diff to selected 3564

preliminary work on a Bugzilla <=> debbugs cheap linker