Re: Building GNOME in restrictive network environments
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: Too many broken modules
Just to follow up... > Do you hav eany details on this one? It built during distcheck, I just > tried building the tarball into an rpm and that worked, and it's not > broken in continuous. This ended up being the moduleset's GDM requiring plymouth to build, and Javier's distro not having plymouth available. He's going to change the moduleset to make plymouth optional and it should resolve the problem. --Ray ___ 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
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
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
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
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
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
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
Building GNOME in restrictive network environments
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
Re: Too many broken modules
Hey, On Mon, Jul 31, 2017 at 7:12 AM wrote: > 'gdm' Do you hav eany details on this one? It built during distcheck, I just tried building the tarball into an rpm and that worked, and it's not broken in continuous. I can try doing a jhbuild run with the moduleset I guess... but i'm wondering if maybe this was just angry pixies that have since mellowed out ? --Ray ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Too many broken modules
On Mon, Jul 31, 2017 at 12:36 PM, Arun Raghavan wrote: Is there some place we can look at logs of the current build? I don't have a jhbuild-y setup here, but I'd be happy to look at the gst-* failures. Nope, got to ask Javier if he remembers why it failed. Sorry. We know we need way better release infrastructure. Alternatively you could download the 3.25.4 modulesets from the release announcement and try building that. In the past, I had to change GStreamer to build from Autotools instead of meson because the tarballs did not contain meson.build. That's the first thing I would check. Michael ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Too many broken modules
On 31 July 2017 at 12:36, Arun Raghavan wrote: > Is there some place we can look at logs of the current build? Same here, fwupd builds fine here, and also in Travis... Richard ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Too many broken modules
On 31 July 2017 at 12:11, wrote: > Hi devs, > > There are too many broken modules right now! Here is the list of modules > that Javier had to skip when releasing 3.25.4: > > 'pango', 'at-spi2-atk', 'vte', 'gdm', 'clutter-gtk', 'graphene', 'nautilus', > 'glade', 'libgxps', 'libgepub', 'gnome-font-viewer', 'fwupd', > 'gnome-terminal', 'totem', 'simple-scan', 'usbredir', 'spice-gtk', > 'gst-plugins-base', 'gst-plugins-bad', 'gnome-dictionary', > 'nautilus-sendto', 'gnome-builder', 'gnome-chess', 'gnome-sudoku' > > That's wy too many broken modules. We normally have just one or two > broken modules per release. Please, if your module is in the list above, > make sure your module builds in JHBuild using your latest *tarball* release. > In particular, if JHBuild is configured to build your module using meson, > and you still have an Autotools build, you *must* ensure every meson.build > is distributed, otherwise the build cannot work. > > I'll be contacting individual maintainers regarding build breakage next > week. It'd be easier if everything is fixed by Monday next week. :) I'm > hoping to release 3.25.90 on time next week, but will delay as long as > required if modules are not building. Is there some place we can look at logs of the current build? I don't have a jhbuild-y setup here, but I'd be happy to look at the gst-* failures. Thanks, Arun ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Too many broken modules
Hi devs, There are too many broken modules right now! Here is the list of modules that Javier had to skip when releasing 3.25.4: 'pango', 'at-spi2-atk', 'vte', 'gdm', 'clutter-gtk', 'graphene', 'nautilus', 'glade', 'libgxps', 'libgepub', 'gnome-font-viewer', 'fwupd', 'gnome-terminal', 'totem', 'simple-scan', 'usbredir', 'spice-gtk', 'gst-plugins-base', 'gst-plugins-bad', 'gnome-dictionary', 'nautilus-sendto', 'gnome-builder', 'gnome-chess', 'gnome-sudoku' That's wy too many broken modules. We normally have just one or two broken modules per release. Please, if your module is in the list above, make sure your module builds in JHBuild using your latest *tarball* release. In particular, if JHBuild is configured to build your module using meson, and you still have an Autotools build, you *must* ensure every meson.build is distributed, otherwise the build cannot work. I'll be contacting individual maintainers regarding build breakage next week. It'd be easier if everything is fixed by Monday next week. :) I'm hoping to release 3.25.90 on time next week, but will delay as long as required if modules are not building. Thanks, Michael ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list