This also applies to the REST information for HTML_Safe. Apparently, REST isn't getting updated when a release is deleted. This should be fixed ASAP, as without it, 1.4.0 is severely hobbled.

# pear list-upgrades
File http://pear.php.net:80/rest/r/html_common/1.2.2.xml not valid (received: HTTP/1.1 404 Not Found
)

This bug has been fixed in CVS.

If this was a documentation problem, the fix will appear on pear.php.net by the end of next Sunday (CET).

If this was a problem with the pear.php.net website, the change should be live shortly.

Otherwise, the fix will appear in the package's next release.

Thank you for the report and for helping us make PEAR better.

running the script to update REST at pear.php.net right now, should be good to go in about 20 minutes.

If no releases are pulled in the next hour, it will continue to work.

As a side note, fixing bugs like this one is not difficult.  Let me walk through steps that could have made this one get fixed very quickly:

1) you knew there was a problem with REST and it had to do with package deletion
2) find the place on the PEAR website that you click to delete packages (in this case, public_html/package-edit.php), and note the params passed in
3) Scan the code, find the section that handles deleting releases,
4) note that release::remove() is the only external code
5) look in release::remove() which is in include/pear-database.php for any calls to "REST" stuff
6) look in the two REST-based methods for any problems.

This is a good way to debug pearweb, and will save troubles if someone like me is too busy to do something immediately