hi everyone,
(if there's a better place to ask this, my apologies and feel free to
redirect me!)
does anyone know here if there is any machine-friendly interface to
the php bug tracking system?
in debian we have a service called "bts-link"[1] which we can use to track
"forwarded" bugs in remote systems's (i.e. a bug reported in debian which
has been linked with another bug such as one on bugs.php.net). for
debian package maintainers this is a major boon since we can keep
better track of bugs that have been fixed or otherwise addressed
"upstream".
so what i'm wondering is: is there an easily parseable or structured
interface (xmlrpc, soap, read-only JSON export, whatever) to the php.net bts
that could be used to get a bug's information? or would such a bts-link
service need to resort to scraping the page for a particular bug's status?
thanks!
sean
[1] http://bts-link.alioth.debian.org/
ps - I'm cc'ing Sandro Tosi, who i believe could answer any questions
you might have about the bts-link service in case you would only
provide such access under certain conditions (he is not subscribed
to this list).
so what i'm wondering is: is there an easily parseable or structured
interface (xmlrpc, soap, read-only JSON export, whatever) to the php.net bts
that could be used to get a bug's information? or would such a bts-link
service need to resort to scraping the page for a particular bug's status?
There is no such thing at the moment, but I wouldn't mind seeing a patch
for this.
regards,
Derick
--
http://derickrethans.nl | http://ezcomponents.org | http://xdebug.org
twitter: @derickr
so what i'm wondering is: is there an easily parseable or structured
interface (xmlrpc, soap, read-only JSON export, whatever) to the
php.net bts
that could be used to get a bug's information? or would such a bts-
link
service need to resort to scraping the page for a particular bug's
status?
Not sure if this really helps you (and I agree that the bug system
really needs some sort of better programmatic interface), but you can
translate most bugs.php.net pages into rss (which is easier to parse
than HTML... usually (-: ) by prepending rss/ to the URL. This useful
for reading.
For example:
http://bugs.php.net/bug.php?id=46944
becomes:
http://bugs.php.net/rss/bug.php?id=46944
and:
http://bugs.php.net/search.php?boolean=0&limit=All&order_by=status&direction=ASC&cmd=display&status=Open&bug_type
[]=Documentation+problem&bug_age=0
becomes:
http://bugs.php.net/rss/search.php?boolean=0&limit=All&order_by=status&direction=ASC&cmd=display&status=Open&bug_type
[]=Documentation+problem&bug_age=0
S
Hi all,
so what i'm wondering is: is there an easily parseable or structured
interface (xmlrpc, soap, read-only JSON export, whatever) to the php.net
bts
that could be used to get a bug's information? or would such a bts-link
service need to resort to scraping the page for a particular bug's status?Not sure if this really helps you (and I agree that the bug system really
needs some sort of better programmatic interface), but you can translate
most bugs.php.net pages into rss (which is easier to parse than HTML...
usually (-: ) by prepending rss/ to the URL. This useful for reading.For example:
http://bugs.php.net/bug.php?id=46944
becomes:
http://bugs.php.net/rss/bug.php?id=46944
yeah, I'll probably follow this way, but using the format=xml parameter:
http://bugs.php.net/rss/bug.php?format=xml&id=46944
that seems better for programmatical parsing.
Just another question: may you please list me all the possible
'Status' field values? In particular we are interested in those
'Status'es that identify the bug as closed and "wontfix".
Cheers,
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi
Just another question: may you please list me all the possible
'Status' field values? In particular we are interested in those
'Status'es that identify the bug as closed and "wontfix".
I believe all current statuses are declared here:
http://cvs.php.net/viewvc.cgi/php-bugs-web/include/functions.inc?view=markup#l82
S
Just another question: may you please list me all the possible
'Status' field values? In particular we are interested in those
'Status'es that identify the bug as closed and "wontfix".I believe all current statuses are declared here:
http://cvs.php.net/viewvc.cgi/php-bugs-web/include/functions.inc?view=markup#l82
That's perfect!
Thanks a lot for your help! I'll let you know when I'll come up with
the final solution.
Cheers,
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi
Just another question: may you please list me all the possible
'Status' field values? In particular we are interested in those
'Status'es that identify the bug as closed and "wontfix".I believe all current statuses are declared here:
http://cvs.php.net/viewvc.cgi/php-bugs-web/include/functions.inc?view=markup#l82That's perfect!
Thanks a lot for your help! I'll let you know when I'll come up with
the final solution.
If you can tell us what exactly you need we can "hook you up" quite easily...
You want json result set of status/assigned/last updated/summary/...
just let php-webmaster@lists.php.net know and it'll get fixed as soon
as someone sees your mail (we can't keep up with the "irrelevant
traffic" on internals@...)
-Hannes
Hannes Magnusson wrote:
Just another question: may you please list me all the possible
'Status' field values? In particular we are interested in those
'Status'es that identify the bug as closed and "wontfix".
I believe all current statuses are declared here:
http://cvs.php.net/viewvc.cgi/php-bugs-web/include/functions.inc?view=markup#l82
That's perfect!Thanks a lot for your help! I'll let you know when I'll come up with
the final solution.If you can tell us what exactly you need we can "hook you up" quite easily...
You want json result set of status/assigned/last updated/summary/...
just let php-webmaster@lists.php.net know and it'll get fixed as soon
as someone sees your mail (we can't keep up with the "irrelevant
traffic" on internals@...)
I wouldn't add anything in the current tracker. Just wait a bit and we
should have something easier to maintain. (that GSoC thing..)
--Jani
Hannes Magnusson wrote:
You want json result set of status/assigned/last updated/summary/...
just let php-webmaster@lists.php.net know and it'll get fixed as soon
as someone sees your mail (we can't keep up with the "irrelevant
traffic" on internals@...)I wouldn't add anything in the current tracker. Just wait a bit and we
should have something easier to maintain. (that GSoC thing..)
Could you please expand it a bit? is this a newer issue trackers? just
an update?
Cheers,
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi
Sandro Tosi wrote:
Hannes Magnusson wrote:
You want json result set of status/assigned/last updated/summary/...
just let php-webmaster@lists.php.net know and it'll get fixed as soon
as someone sees your mail (we can't keep up with the "irrelevant
traffic" on internals@...)
I wouldn't add anything in the current tracker. Just wait a bit and we
should have something easier to maintain. (that GSoC thing..)Could you please expand it a bit? is this a newer issue trackers? just
an update?
It's this: http://cvs.php.net/viewvc.cgi/pear/Bugtracker/
And it's not new per se. It's a kind of fork by Pear folks at one time,
which I then took and "forked" into it's own package and modified to be
usable by all PHP, PECL and PEAR. (as standalone installations first)
And Philip just sent an email about it on this list:
http://news.php.net/php.internals/44782
I suggest you reply to that. :)
--Jani
Hello Hannes,
On Sun, Jul 5, 2009 at 03:17, Hannes
Magnussonhannes.magnusson@gmail.com wrote:
Just another question: may you please list me all the possible
'Status' field values? In particular we are interested in those
'Status'es that identify the bug as closed and "wontfix".I believe all current statuses are declared here:
http://cvs.php.net/viewvc.cgi/php-bugs-web/include/functions.inc?view=markup#l82That's perfect!
Thanks a lot for your help! I'll let you know when I'll come up with
the final solution.If you can tell us what exactly you need we can "hook you up" quite easily...
What I need is a way to programmatically query a given php bugs to
know its status, so we can updated the "connected" bugs in the Debian
issue tracker.
You want json result set of status/assigned/last updated/summary/...
I think the rss xml format is fine enough.
just let php-webmaster@lists.php.net know and it'll get fixed as soon
as someone sees your mail (we can't keep up with the "irrelevant
traffic" on internals@...)
Sure, feel free to forward the discussion there, if you see fit.
Cheers
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi
Hi all,
so what i'm wondering is: is there an easily parseable or structured
interface (xmlrpc, soap, read-only JSON export, whatever) to the php.net
bts
that could be used to get a bug's information? or would such a bts-link
service need to resort to scraping the page for a particular bug's status?Not sure if this really helps you (and I agree that the bug system really
needs some sort of better programmatic interface), but you can translate
most bugs.php.net pages into rss (which is easier to parse than HTML...
usually (-: ) by prepending rss/ to the URL. This useful for reading.For example:
http://bugs.php.net/bug.php?id=46944
becomes:
http://bugs.php.net/rss/bug.php?id=46944yeah, I'll probably follow this way, but using the format=xml parameter:
http://bugs.php.net/rss/bug.php?format=xml&id=46944
that seems better for programmatical parsing.
FYI: I've implemented the parsing using the rss xml ouput. In case
some development is done on this side, please keep me in the loop :)
Cheers,
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi