We also experienced this issue at the newcomers workshop as many
flatpak manifests also download dependencies using the git:// protocol.
It'd be great to have these fixed or maybe have a fallback behavior
(having several URLs to try in the manifests?).
-Bastian
On Mon, Jul 31, 2017 at 1:29 , mcatanz...@gnome.org wrote:
Hi all,
I've gotten multiple complaints at GUADEC that it's not possible to
clone GNOME modules because the university network is blocking the
git protocol. This is particularly common at universities in
third-world countries, where it's common for newcomers to complain
about this, but seems it happens in Europe too. So I have changed
JHBuild to clone stuff using https:// rather than git://. I'm testing
this now and will push as soon as I'm sure I haven't broken anything.
Caveats:
* I have not updated all of gnome-world, so contributions are
welcome there as usual. But all the supported 3.26 modulesets should
now be completely fixed.
* Some modules clone git:// submodules. Please be on the lookout for
these. For example, this is .gitmodules in gnome-online-accounts:
# Bad
[submodule "telepathy-account-widgets"]
path = telepathy-account-widgets
url = git://git.gnome.org/telepathy-account-widgets.git
It's better to clone using the same protocol as the parent project:
# Good
[submodule "telepathy-account-widgets"]
path = telepathy-account-widgets
url = ../telepathy-account-widgets.git
I'll leave it to module maintainers to fix these.
Thanks,
Michael
_______________________________________________
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list