Re: GitHub source URLs not working
On Fri, Nov 26, 2021 at 5:50 PM Fabio Valentini <decathorpe(a)gmail.com> wrote:
On Fri, Nov 26, 2021 at 11:30 PM Nico Kadel-Garcia <nkadel(a)gmail.com> wrote:
>
> It's also Friday right after Thanksgiving, "Black Friday". And most
> python modules .spec files, which use pypi.org as their source
> repository rathter than github, seem to be workin.
(snip)
> Directly referencing github is sometimes useful, for example for
> anyone who bothers to straighten the somewhat crazed renaming of
> "ansible" and ansible-core" as "ansible-core" and
> "ansible-collections, or who works with ansible colleciton modules.
> But how much of github references use 'codeload.github.com' rather
> than 'github.com' ?There hae been way, way too many syntaxes for
> pulling tarballs for git repos, it's sometimes quite confusing.
> Especially for python modules, since the e python repo owner can
> delete and replace arbitrary tags at whim.
If you look at the actual request URL, you'll see that it is for github.com.
The codeload.github.com URL is then a result of a server-side redirect.
To quote Willie Wonka: "Strike that: reverse it". The
codeload.github.com URL typically generates a successful redirect,
which is not working.
I'd encourage throwing most of thee varied 'get the designated
tarball' schemes to simplify the schemes and make it more reliable.
There *have* been many way to load tarballs from GitHub, but this
has
pretty much standardized in recent 2-3 years.
And the fact that the URL scheme that is documented in the Packaging
Guidelines (and probably the one used by the forge macros) is broken
does not bode well.
*Absolutely* correct! I'd hate to have to change it in the standards.
Do any of us know anyone over at github.com to let them know directly?
I'm not working for a company with such a contract right now, my repos
there are personal right now.