I think I needed sleep. 302 isn’t an “error”, really, it’s a redirect.
greg@x1c:~$ curl -I <https://github.com/samth/find-parent-dir/tarball/e78d0277447d81934847166e8024edc5adea4b1c>
HTTP/1.1 302 Found
date: Sat, 28 Mar 2020 05:06:38 GMT
content-type: text/html; charset=utf-8
server: <http://GitHub.com\|GitHub.com>
status: 302 Found
vary: X-PJAX, Accept-Encoding, Accept, X-Requested-With
location: <https://codeload.github.com/samth/find-parent-dir/legacy.tar.gz/e78d0277447d81934847166e8024edc5adea4b1c>
...
IIUC GitHub is now redirecting these, and probably raco pkg install doesn’t follow redirects prior to 6.3.
One idea is I could stop testing/supporting all packages prior to 6.3. But that’s kind of drastic.
Another idea is that the package catalog could provide the new URL in the first place. Maybe?
@robin.ge has joined the channel
Unfortunately, as @mflatt points out, that PR won’t fix the problem. Furthermore, I think the problem is unfixable — that URL is generated by the client (the one my patch changes) not by the server, so we can’t make things work on 6.3.
Ah OK. I wonder, does this only apply to packages that specify — on the package server — the github: protocol instead of git:? If so, could it be fixed on the package server by updating those instead to use git:?
I was wondering that. Can you test installing the github and git urls directly on 6.2?
In which case, we can at least fix the important ones
Darn. I think I found a counter-example. Although one of the problem examples is the find-parent-dir pkg which does use github, another problem example is threading-lib which uses git:. So it seems it’s not that simple.
Even if it were possible to fix this, I don’t think this is worth going to heroic — or even moderately complicated — efforts to do so. The packages in question were only supporting versions as old as 6.2 and 6.2.1, already. To bump that one version higher to 6.3 does not seem such a big deal. I think even things like debian stable are way past that version now. And I’m not proposing to make things like aws, rackjure, and frog actively not-support 6.2.x anymore. I’m “only” proposing to not actively CI test them. Probably they’ll continue to work just fine with 6.2.x.
I just wanted to check if it might be a simple thing to change, to keep supporting/testing 6.2.x.
inconveniently, it’s hard to test since 6.2 fails to do any package installs on my machine because of SSL issues
Well there we go. I can just say, 6.2.x is no longer supported Because Security. :smile:
@masande.mti has joined the channel