Re: Release team now using gnome-build-meta repository, not JHBuild

2018-01-21 Thread mcatanzaro
On Sun, Jan 21, 2018 at 6:02 AM, Tristan Van Berkom wrote: gexiv2 is listed as a system dependency, which strikes me as a bit odd seeing as it's a requirement for some GNOME modules and it's hosted in GNOME - I'm new to the release team and will have to

Re: Release team now using gnome-build-meta repository, not JHBuild

2018-01-21 Thread mcatanzaro
Hi, On Sun, Jan 21, 2018 at 3:16 AM, Jens Georg wrote: So, following up on that and also on the libgepub thread: Which places do I have to modify if I were to switch the ABI and API version of gexiv2 (to either keep depending entities on the old stable branch or to the new

Re: Release team now using gnome-build-meta repository, not JHBuild

2018-01-21 Thread Tristan Van Berkom
Hi Jens, Hurried reply whilst getting ready to go to airport... On Sun, 2018-01-21 at 10:16 +0100, Jens Georg wrote: > > On Sat, 2018-01-20 at 11:06 -0600, mcatanz...@gnome.org wrote: > > > Hi all, > > > > This bears repeating: the release team will no longer maintain > > JHBuild  > > or the

Re: Release team now using gnome-build-meta repository, not JHBuild

2018-01-21 Thread Jens Georg
On Sat, 2018-01-20 at 11:06 -0600, mcatanz...@gnome.org wrote: > Hi all, > > This bears repeating: the release team will no longer maintain > JHBuild > or the JHBuild modulesets. When adding or removing a dependency from > your module, please now update gnome-build-meta instead. So, following