diff options
| author | Eli Schwartz <eschwartz93@gmail.com> | 2024-03-28 02:08:42 -0400 |
|---|---|---|
| committer | Sam James <sam@gentoo.org> | 2024-03-29 02:28:24 +0000 |
| commit | 39eca52d93521a58c4205411d4ab11eca1cb1756 (patch) | |
| tree | 421239a417edddb50a69d2b38e3e67535ffc1bb4 /dev-python/google-api-python-client/google-api-python-client-2.121.0.ebuild | |
| parent | 3db28eb5c6b781f5f24b2d15fcd40174bba4f7da (diff) | |
| download | gentoo-39eca52d93521a58c4205411d4ab11eca1cb1756.tar.gz gentoo-39eca52d93521a58c4205411d4ab11eca1cb1756.tar.bz2 gentoo-39eca52d93521a58c4205411d4ab11eca1cb1756.zip | |
sys-cluster/legion: remove conceptually invalid repository clone url
This clearly wasn't tested (or else it was a cunning form of troll) to
list the primary clone url as git://directoryname/reponame.git given
that the directory name "StanfordLegion" is not a valid hostname or IP
address.
If I had to hazard the wildest of wild guesses as to what this was
intended to do, it was intended to allow cloning from github.com over
your choice of git:// or https:// protocols. Which leaves open the
alternative question "why in G-ds name...".
In any case, it doesn't matter since github hasn't offered git://
support for quite some time, so even if it worked, it wouldn't work.
This change was made by github for the same reason that portage scolds
you for using it:
* git-r3: git protocol is completely insecure and may render the ebuild
* easily susceptible to MITM attacks (even if used only as fallback). Please
* use https instead.
Signed-off-by: Eli Schwartz <eschwartz93@gmail.com>
Signed-off-by: Sam James <sam@gentoo.org>
Diffstat (limited to 'dev-python/google-api-python-client/google-api-python-client-2.121.0.ebuild')
0 files changed, 0 insertions, 0 deletions