php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #56524 Wrong REST information for package HTML_Common
Submitted: 2005-09-03 07:31 UTC Modified: 2005-09-04 18:58 UTC
From: toby@php.net Assigned: cellog (profile)
Status: Closed Package: PECL website (PECL)
PHP Version: Irrelevant OS: Irrelevant
Private report: No CVE-ID: None
 [2005-09-03 07:31 UTC] toby@php.net
Description:
------------
http://pear.php.net/rest/r/html_common/lastest.txt and http://pear.php.net/rest/r/html_common/stable.txt show version 1.2.2 to be latest, which does not exist.

Actual result:
--------------
toby@a15186171:~$ sudo pear clear-cache
reading directory /tmp/pear/cache
140 cache entries cleared
toby@a15186171:~$ sudo 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
)


Patches

Add a Patch

Pull Requests

Add a Pull Request

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2005-09-04 08:10 UTC] klaus at capitalfocus dot org
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.
 [2005-09-04 08:25 UTC] toggg at toggg dot toggg
# 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
)
 [2005-09-04 18:58 UTC] cellog@php.net
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
 
PHP Copyright © 2001-2021 The PHP Group
All rights reserved.
Last updated: Sun Jan 17 03:01:23 2021 UTC