Re: Building GNOME in restrictive network environments

[Debarshi Ray]

On Mon, Jul 31, 2017 at 01:29:09PM +0100, mcatanz...@gnome.org wrote:
>  * 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

This was done on purpose because ostbuild used to have problems with
the relative URLs. See gnome-photos.git where the libgd submodule
started off by using a relative URL, but was then changed to use an
absolute one.

What's the current state of affairs here? Will Continuous break if
we were use relative URLs for the submodules?
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list

Re: Building GNOME in restrictive network environments

[mcatanzaro]

On Mon, Jul 31, 2017 at 1:29 PM, mcatanz...@gnome.org wrote:
I'm testing this now and will push as soon as I'm sure I haven't 
broken anything.


Done.

Michael
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list

Re: Building GNOME in restrictive network environments

[philip . chimento]

Thanks to Florian for remembering this trick. For those at GUADEC for the
time being you can add to your ~/.gitconfig:

[url "https://git.gnome.org/browse;]
  insteadOf = git://git.gnome.org
[url "https://anongit.free desktop.org/git"]
  insteadOf = git://anongit.freedesktop.org

On Mon, Jul 31, 2017, 16:38 Sam Thursfield  wrote:

> On 7/31/17, mcatanz...@gnome.org  wrote:
> > I'd also ask the GUADEC 2018 hosts to keep in mind the importance of
> > having a good network connection for the unconference days. I'm told
> > the MMU network is blocking email and IRC in addition to git. It's also
> > blocking my Private Internet Access VPN. Shame we can't use our free
> > PIA subscriptions (thanks PIA!) to avoid these problems.
>
> Ugh! Sorry...
>
> it at least makes sense to test the wifi in advance of the event and
> document what is blocked so people can set up proxy servers with SSH
> listening on port 443 in advance...
>
>
> Sam
> ___
> desktop-devel-list mailing list
> desktop-devel-list@gnome.org
> https://mail.gnome.org/mailman/listinfo/desktop-devel-list
>
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list

Re: Building GNOME in restrictive network environments

[Sam Thursfield]

On 7/31/17, mcatanz...@gnome.org  wrote:
> I'd also ask the GUADEC 2018 hosts to keep in mind the importance of
> having a good network connection for the unconference days. I'm told
> the MMU network is blocking email and IRC in addition to git. It's also
> blocking my Private Internet Access VPN. Shame we can't use our free
> PIA subscriptions (thanks PIA!) to avoid these problems.

Ugh! Sorry...

it at least makes sense to test the wifi in advance of the event and
document what is blocked so people can set up proxy servers with SSH
listening on port 443 in advance...


Sam
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list

Re: Building GNOME in restrictive network environments

[Mathieu Bridon]

I just fixed all the .json manifests and .app files in the master
branch of gnome-apps-nightly, as well as the .json manifest for the
master branch of the GNOME Sdk.


-- 
Mathieu

On Mon, 2017-07-31 at 15:40 +0200, Mathieu Bridon wrote:
> I've just gotten bitten by this as well, and have started moving all
> the ones in gnome-apps-nightly from git:// to https://
> 
> 
> -- 
> Mathieu
> 
> On Mon, 2017-07-31 at 14:15 +0100, Bastian Ilso wrote:
> > 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.
> > > 
> > > Cav eats:
> > > 
> > >  * 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

Re: Building GNOME in restrictive network environments

[mcatanzaro]

On Mon, Jul 31, 2017 at 2:15 PM, Bastian Ilso 
 wrote:
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?).


I'd also ask the GUADEC 2018 hosts to keep in mind the importance of 
having a good network connection for the unconference days. I'm told 
the MMU network is blocking email and IRC in addition to git. It's also 
blocking my Private Internet Access VPN. Shame we can't use our free 
PIA subscriptions (thanks PIA!) to avoid these problems.


Michael
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list

Re: Building GNOME in restrictive network environments

[Mathieu Bridon]

I've just gotten bitten by this as well, and have started moving all
the ones in gnome-apps-nightly from git:// to https://


-- 
Mathieu

On Mon, 2017-07-31 at 14:15 +0100, Bastian Ilso wrote:
> 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.
> > 
> > Cav eats:
> > 
> >  * 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
-- 
Mathieu
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list

Re: Building GNOME in restrictive network environments

[Bastian Ilso]

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