Description: ------------ While this could be by design.... Right now, one's only able to submit bugs for packages which have a stable release. It would be handy of users could submit bugs for non-stable packages too. Otherwise users might resort to posting bugs for an unstable package not at all, or in the wrong place where it won't get fixed at all. Changing the XML_RPC call in bugtypes.inc from package::listAll(); to package::listAll(true); should fix the problem I think. Reproduce code: --------------- http://pear.php.net/bugs/bug.php?id=307 http://pear.php.net/bugs/bug.php?id=266

1) package::listAll() is no XML_RPC method. It's defined in pear-database.php. 2) The optional parameter only determines if all packages or just packages with >= 1 release(s) should be listed. Thus this will not fix the problem. We'll try to find another solution.

Yer, correct, bad wording on my side. The ::listAll() function is the same function as that was called via XML_RPC, and that's how I debugged this :) However, browsing the CVS archive I did find this line of code in the SQL query done by the package::listAll() function: ($released_only is the first argument provided to the function.) ($released_only ? "AND r.state = 'stable' " : ""). This would seem to suggest that only stable state packages are searched, not just those with any releases. F.I. http://pear.php.net/package/Spreadsheet_Excel_Writer shows this package has released several versions, none of those stable however, and the package doesn't show up on the buglist :)

This bug has been fixed in CVS. In case this was a documentation problem, the fix will show up at the end of next Sunday (CET) on pear.php.net. In case this was a pear.php.net website problem, the change will show up on the website in short time. Thank you for the report, and for helping us make PEAR better.