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

On Mon, 2018-01-22 at 14:31 -0600, mcatanz...@gnome.org wrote: > > > I'll use one specific anecdote. On October 30, the Autotools build > files were removed from at-spi2-core. The accompanying JHBuild > moduleset update switching it to use meson was pushed by Philip > Withnall (thanks!) on

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

>But I'm only speaking for the release team here, not the entire community - I know that answer doesn't actually solve the problem, but hopefully that explains our thinking. Definitely, I imagined this is just a side effect of the release team not using JHbuild anymore, which I understand. Just

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

On Mon, Jan 22, 2018 at 12:56 PM, Carlos Soriano wrote: What's the workflow for those before a proper solution is done? Or are the developers of those modules expected to maintain JHbuild on the meantime? Thanks Carlos; this is an important question. Let me provide a

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

Adding on top of Florian, some apps like gnome-boxes and Nautilus are not yet ready for Flatpak, or Flatpak is not ready for them yet. While I agree we should pursue that as a end goal, pulling out maintenance of JHbuild as tool for people to contribute to our modules before a viable alternative

Re: [GitLab] Projects moved and 'tips of the week'

Done , cheers. Carlos Soriano GNOME Board of Directors On 22 January 2018 at 18:08, 藍挺瑋 wrote: > Tobias Mueller 於 西元2018年01月23日 00:46 寫道: > > Hi. > > > > On Tue, 2018-01-23 at 00:09 +0800, 藍挺瑋 wrote: > >> Is it possible to

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

On Sat, Jan 20, 2018 at 9:47 AM, Tristan Van Berkom wrote: > Instructions for using the gnome-build-meta BuildStream project can be > found at: > > https://wiki.gnome.org/Newcomers/BuildSystemComponent We found a bug in BuildStream which is triggered by

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

On Mon, Jan 22, 2018 at 9:13 AM, Florian Müllner wrote: Very much, I actually use a jhbuild GNOME session as my everyday system. I don't have a good answer. :/ Michael ___ desktop-devel-list mailing list

Re: [GitLab] Projects moved and 'tips of the week'

Tobias Mueller 於 西元2018年01月23日 00:46 寫道: > Hi. > > On Tue, 2018-01-23 at 00:09 +0800, 藍挺瑋 wrote: >> Is it possible to get a private bug migrated to GitLab? I have a bug >> report which was marked as private by a libgtop developer, but there >> is >> no confidential information in the bug and I

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

mcatanz...@gnome.org 於 西元2018年01月22日 21:34 寫道: > > > On Mon, Jan 22, 2018 at 7:25 AM, mcatanz...@gnome.org wrote: >> Were you actually using JHBuild to run integrated system components >> (gnome-shell, gnome-session)? If so, how? I was not aware that that >> was even possible nowadays. >> >>

Re: [GitLab] Projects moved and 'tips of the week'

Hi. On Tue, 2018-01-23 at 00:09 +0800, 藍挺瑋 wrote: > Is it possible to get a private bug migrated to GitLab? I have a bug > report which was marked as private by a libgtop developer, but there > is > no confidential information in the bug and I don't know why it became > private. > >

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

On Mon, Jan 22, 2018 at 2:34 PM, wrote: > > > On Mon, Jan 22, 2018 at 7:25 AM, mcatanz...@gnome.org wrote: >> >> Were you actually using JHBuild to run integrated system components >> (gnome-shell, gnome-session)? If so, how? I was not aware that that was even >> possible

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

On Mon, 2018-01-22 at 07:34 -0600, mcatanz...@gnome.org wrote: > > On Mon, Jan 22, 2018 at 7:25 AM, mcatanz...@gnome.org wrote: > > Were you actually using JHBuild to run integrated system > > components > > (gnome-shell, gnome-session)? If so, how? I was not aware that > > that > > was even

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

On Mon, Jan 22, 2018 at 7:25 AM, mcatanz...@gnome.org wrote: Were you actually using JHBuild to run integrated system components (gnome-shell, gnome-session)? If so, how? I was not aware that that was even possible nowadays. When developing these components, Sorry, trying again When

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

On Mon, Jan 22, 2018 at 6:33 AM, Florian Müllner wrote: Is this information outdated? At least I see all those components in the gnome-build-meta repo, so I dare to hope ... You can build them, and there is CI to ensure the build does not fail. But I imagine it would

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

On Sat, Jan 20, 2018 at 6:06 PM, wrote: > When adding or removing a dependency from your > module, please now update gnome-build-meta instead. The BuildSteam page still mentions this: > In case you are trying to develop integrated components such as GNOME Shell, > GDM,