unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: 27778@debbugs.gnu.org
Subject: bug#27778: Changing package source URLs from git:// to https://
Date: Thu, 20 Jul 2017 18:06:31 -0400	[thread overview]
Message-ID: <20170720220631.GB31573@jasmine.lan> (raw)

[-- Attachment #1: Type: text/plain, Size: 2021 bytes --]

There are several packages that fetch their sources over the Git
protocol. That is, 'git://'.

This protocol is unauthenticated, which is not great, although not 100%
terrible since we know the hash of what we are trying to fetch. Also, it
uses port 9418 which is blocked more often than 443 or 80.

Let's change these packages to use HTTPS or HTTP!

~/guix/gnu/packages% grep -rI 'git://'
pumpio.scm:                    (url "git://pumpa.branchable.com/")
fltk.scm:                    (url "git://git.tuxfamily.org/gitroot/non/fltk.git")
microcom.scm:                    (url "git://git.pengutronix.de/git/tools/microcom.git")
rdesktop.scm:                    (url "git://github.com/FreeRDP/FreeRDP.git")
gnunet.scm:                      (url "git://git.sv.gnu.org/guix/gnunet.git")
suckless.scm:               (url "git://git.2f30.org/human.git")
admin.scm:                      (url "git://github.com/TrilbyWhite/interrobang")
embedded.scm:                      (url "git://git.zapb.de/libjaylink.git")
embedded.scm:                      (url "git://git.code.sf.net/p/openocd/code.git")
version-control.scm:             (url "git://myrepos.branchable.com/myrepos")
audio.scm:                    (url "git://git.ardour.org/ardour/ardour.git")
emacs.scm:                    (url "git://git.hcoop.net/git/bpt/emacs.git")
messaging.scm:                    (url "git://git.psyced.org/git/psyclpc")
music.scm:                      (url "git://git.tuxfamily.org/gitroot/non/non.git")
python.scm:             (url "git://github.com/tgalal/python-axolotl-curve25519")
web.scm:                    (url "git://git.libwebsockets.org/libwebsockets")
gnome.scm:                      (url "git://git.gnome.org/byzanz")
guile.scm:                    (url "git://git.hcoop.net/git/bpt/guile.git")
guile.scm:                      (url "git://dthompson.us/guile-syntax-highlight.git")
java.scm:                      (url "git://git.savannah.gnu.org/classpath.git")
shells.scm:                    (url "git://github.com/rakitzis/rc.git")

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

             reply	other threads:[~2017-07-20 22:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-20 22:06 Leo Famulari [this message]
2017-07-22 23:33 ` bug#27778: Changing package source URLs from git:// to https:// Leo Famulari
2017-07-25  7:12   ` Mark H Weaver
2017-07-25 18:00     ` Leo Famulari
2017-08-27 22:36       ` Leo Famulari
2017-08-27 23:41   ` ng0

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170720220631.GB31573@jasmine.lan \
    --to=leo@famulari.name \
    --cc=27778@debbugs.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).