Summary: | ASTERISK-26795: pjproject MD5SUM link incorrect | ||
Reporter: | Seán C. McCord (ulexus@gmail.com) | Labels: | |
Date Opened: | 2017-02-15 21:07:47.000-0600 | Date Closed: | 2017-02-15 21:20:27.000-0600 |
Priority: | Minor | Regression? | Yes |
Status: | Closed/Complete | Components: | pjproject/pjsip |
Versions: | 14.3.0 | Frequency of Occurrence | Constant |
Related Issues: | |||
Environment: | OS doesn't matter, but for reference, use Debian jessie | Attachments: | |
Description: | The URL for the MD5 sum of the pjproject file (pjproject-2.5.5) is apparently incorrect, resulting in a 404 error.
The URL currently is: http://www.pjsip.org/release/2.5.5/MD5SUM It should be: http://www.pjsip.org/release/2.5.5/MD5SUM.TXT --- $ curl http://www.pjsip.org/release/2.5.5/MD5SUM.TXT dde6091ae166e73ce99227e570ef39f2 *pjproject-2.5.5.zip 183f7144b9aa238884243c0fc52ece36 pjproject-2.5.5.tar.bz2 $ curl http://www.pjsip.org/release/2.5.5/MD5SUM <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>404 Not Found</title> </head><body> <h1>Not Found</h1> <p>The requested URL /release/2.5.5/MD5SUM was not found on this server.</p> </body></html> --- | ||
Comments: | By: Asterisk Team (asteriskteam) 2017-02-15 21:07:48.256-0600 Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution. A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report. Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process]. By: Seán C. McCord (ulexus@gmail.com) 2017-02-15 21:20:06.870-0600 It looks like this has already been fixed in the 14 branch, just not the 14.3.0 release. By: Seán C. McCord (ulexus@gmail.com) 2017-02-15 21:20:27.177-0600 Fix is already in 14 branch |