Message following "Updating binary package" doesn't make sense
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 258
- Forks
- 68
- PR merge metrics
- No merged PRs in 30d
Description
Before af24915ba36c57ef7133023eb55148712a6023f1 the message was:
```
* Updating binary package linux-x86_64/gdal/2.4.1.tar.gz...
curl: no URL specified!
curl: try 'curl --help' or 'curl --manual' for more information
* Binary package is still up to date
```
the script was broken, and the message could not be trusted, because it didn't actually check the package URL.
After af24915ba36c57ef7133023eb55148712a6023f1 it is:
```
* Updating binary package linux-x86_64/gdal/2.4.1.tar.gz...
* Binary not available yet for linux-x86_64/gdal/2.4.1.tar.gz
```
Now it actually checks the URL, but then says it's not available. I'd assume curl should succeed with HTTP status 304 Not Modified, but it appears to work differently.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the linux-x86_64/gdal/2.4.1.tar.gz update and inspect the package-checking change in commit af24915ba36c57ef7133023eb55148712a6023f1. Trace how the curl response is interpreted and verify that the final message accurately reflects whether the binary package is available.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux
- Domain
- release
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100