I obvious haven’t been paying close attention... thanks for that, and I’ll
review the other thread too.
Cheers,
-Tristan
> On Aug 25, 2020, at 10:24 PM, Michael Catanzaro wrote:
>
> On Tue, Aug 25, 2020 at 9:27 pm, Tristan Van Berkom
> wrote:
>> My wild guess: fre
When decommissioning, please let us know what we have to do to adapt.
My wild guess: freeze break requests arrive in the form of... issues ?
Submitted against gnome-build-meta ?
If so, it’s important that we get an email, instructing is to set our
notifications to global for that project (as
News
o Support `buildstream1.conf` as well as `buildstream.conf` for
parallel installations.
o Lazy resolution of variables, this allows junctions to use variables
without requiring the project to have fully resolved variables, while
still reporting the right error messages
News
o Process options in included files in the context of the project they
were included from.
This is technically a breaking change, however it is highly unlikely
that this will break projects. In some cases projects were working around
the broken behavior by ensuring
News
o Fix support for conditional list append/prepend in project.conf,
Merge request !1857
o Fix internal imports to import from "collections" instead
of "collections.abc", this improves support for Python 3.8,
see issue #831
o Fix some downloads from gitlab.com by
News
o Source plugins may now request access access to previous during track and
fetch by setting `BST_REQUIRES_PREVIOUS_SOURCES_TRACK` and/or
`BST_REQUIRES_PREVIOUS_SOURCES_FETCH` attributes.
o Add new `pip` source plugin for downloading python packages using pip,
based on
News
o Fixed issues with workspaced junctions which need fetches (#1030)
o Bail out with informative error if stdout/stderr are O_NONBLOCK (#929)
Download
https://download.gnome.org/sources/BuildStream/1.2/BuildStream-1.2.8.tar.xz
(342K)
sha256sum:
News
o Improved messaging around unknown artifact cache keys (#981)
o Fixed crash which occurs when deleting artifact cache with
open workspaces (#1017)
o Fixed `bst --no-strict build --track-all ...` which sometimes
exited successfully without building anything (#1014)
o
News
o Fix 'quit' option when interrupting a build (#525)
o Only queue one cache size calculation job at a time
o Fix stack traces on forceful termination
o Fix scheduler processing order regression (#712)
o Fix race condition in bzr source plugin
o Better error messages for
Hi,
Thanks for bringing this up.
On Thu, 2019-04-25 at 17:08 +0200, Debarshi Ray via release-team wrote:
> Hey Egmont,
>
> Thanks for the heads up!
>
> > On Thu, Apr 25, 2019 at 11:59 AM Egmont Koblinger wrote:
> > - VTE 0.56.2 was released ahead of schedule in order to fix a crash
> > (RH
News
o Fixed failure to process some elements when workspaces are open (#919)
o Better error reporting when files are missing, or when encountering
errors in sub projects (#947)
o Do not require exact versions of dependencies for running tests (#916)
o Fail on overlap policy
On Thu, 2019-03-07 at 06:16 +0100, Andre Klapper wrote:
> On Wed, 2019-03-06 at 21:48 -0600, mcatanz...@gnome.org wrote:
> > Hi,
> >
> > I'd like to request a freeze break to fix a crash in Epiphany when
> > opening the preferences dialog with certain languages configured:
> >
> >
On Wed, 2019-02-20 at 16:57 +0100, Robert Ancell via release-team
wrote:
> I'd like to request a change [1] in GNOME Control Center to disable
> the adaptive panel feature. This is due to it introducing some bugs
> [2] and not all panels being updated in time for 3.32. The feature
> will return in
News
o Migration of scripts to use tox
o Force updating tags when fetching from git repos (#812)
o Avoid downloading unused submodules (#804)
o Fixed cleanup of cache server with disk is full (#609)
o Fixed possible artifact cache corruption (#749)
o Fixed `bst checkout
News
o Fixed an unhandled exception when cleaning up a build sandbox (#153)
o Fixed race condition when calculating cache size and commiting artifacts
o Fixed regression where terminating with `^C` results in a double user
interrogation (#693)
o Fixed regression in summary when
News
o Fixed corruption of artifact cache at cache cleanup time (#623)
o Fixed accidental deletion of artifacts when tracking is enabled
o Error out when protected variables are set by project authors (#287)
o Fixed option resolution in project wide element & source configurations
News
o Various last minute bug fixes
o Final update to the SourceFetcher related mirroring APIs
Download
https://download.gnome.org/sources/BuildStream/1.2/BuildStream-1.2.0.tar.xz
(443K)
sha256sum: 35c317c9c08e7961f07ff93650bbe0672bec2b932a552beeede7660171da90d4
On Fri, 2018-08-31 at 23:06 +0200, Egmont Koblinger via release-team
wrote:
> Hi,
>
> There's a recently discovered flaw in VTE's current development
> series 0.53 that occasionally leads to a segfault when the widget is
> unrealized.
>
> This can lead to all the gnome-terminal windows and tabs
News
o Fix CAS resource_name format
Artifact servers need to be updated.
o Improved startup performance and performance of
calculating artifact cache size
o Various other bug fixes
Download
News
o A lot of bug fixes
Download
https://download.gnome.org/sources/BuildStream/1.1/BuildStream-1.1.6.tar.xz
(438K)
sha256sum: f872c53e2b8d9a852364a58408f0df3667a83e38258cba89f8bfe5d14464e88b
___
release-team@gnome.org
News
o Add a `--tar` option to `bst checkout` which allows a tarball to be
created from the artifact contents.
o Fetching and tracking will consult mirrors defined in project config,
and the preferred mirror to fetch from can be defined in the command
line or user config.
News
o `bst workspace` commands and `bst track` will substitute their
source elements when performing those operations, e.g. performing
`bst track` on a filter element will track the sources on the
element that it depends on (if it has sources).
o Added new simple `make`
News
o Added new `bst init` command to initialize a new project.
o Cross junction tracking is now disabled by default for projects
which can support this by using project.refs ref-storage
New options have been added to explicitly enable cross-junction
tracking.
o Failed
On Sun, 2018-04-15 at 08:53 -0500, Michael Catanzaro wrote:
>
> Javier created a branch the other day:
>
> https://gitlab.gnome.org/GNOME/gnome-build-meta/tree/gnome-3-28
>
Ahhh, I missed that in `git branch -r`
> What it is missing is that stable limits were not created:
>
>
On Fri, 2018-03-23 at 15:07 +0900, Tristan Van Berkom wrote:
> This is more or less related to BuildStream format, I think less
> related than more.
>
> I think we have consensus anyway at this point that we're not going to
> repeat this accumulative thing that we did with JHBuild
News
o New ref-storage option allows one to store source refs, such
as git shas, in one central project.refs file instead of inline
with the source declarations.
o Deprecated `--track-save` optionality in `bst build`, this
does not make sense to support now that we have
This is more or less related to BuildStream format, I think less
related than more.
I think we have consensus anyway at this point that we're not going to
repeat this accumulative thing that we did with JHBuild in the
gnome-build-meta repository, so lets create a branch.
I propose that:
o We
News
o New project configuration controlling how the sandbox behaves
when `bst shell` is used; allowing projects to provide a more
functional shell environment.
o The `bst shell` command now has a `--mount` option allowing
users to mount files and directories into the
On Mon, 2018-03-05 at 12:51 -0600, mcatanz...@gnome.org wrote:
> Hi,
>
> The following commit fixes a buffer overflow in epiphany's tests:
>
> https://git.gnome.org/browse/epiphany/commit/?id=0ad97baa47cd13c955e0
> 873e52cf03b84ad4a620
>
> May I backport it to the gnome-3-28 branch?
+1
On Thu, 2018-03-01 at 23:39 -0800, Christian Hergert wrote:
> On 03/01/2018 11:24 PM, Tristan Van Berkom wrote:
> > There is no automated publishing system either for the above mentioned
> > builders, instead from what I recall; Alex has to manually go and run a
> > script w
On Thu, 2018-03-01 at 21:15 -0800, Christian Hergert wrote:
> The arm/aarch64 SDK builders on gnome-nightly seem to be about a year
> out of date. Are there plans to get these updated, or is that blocking
> on BuildStream? Maybe we just forgot about them?
What are the "builders on gnome-nightly"
Download
https://download.gnome.org/sources/BuildStream/1.1/BuildStream-1.1.0.tar.xz
(261K)
sha256sum: 5cc7193758a92f288e8faa16a1f0f89c46363450b98267d0c321a3fb1941726e
___
release-team@gnome.org
On Fri, 2018-01-26 at 16:16 +, Allan Day wrote:
> Hi all,
>
> Today was my first experience using Buildstream, which I did by following the
> guide on the GNOME wiki. I got blocked by an issue, but I wanted to provide
> some notes on my experience using the documentation (see below).
>
>
Hi Release Team,
I've put up the converted and slightly touched up project last night
at:
https://gitlab.gnome.org/GNOME/gnome-build-meta
Release team members should add themselves as maintainers to the doap
file in this repo.
Also I've updated the URL and made some other changes to the
News
o Fixed instability of cache keys generated for elements
using the `local` source
o Removed some undocumented secret and unused APIs, technically
a break but nothing yet depends on these.
Download
On Sun, 2018-01-07 at 20:52 -0600, Michael Catanzaro wrote:
> Are we ready to stop the automatic conversion from JHBuild modulesets
> to BuildStream? I don't think we need to wait until February for that,
> right?
We need to keep the conversions going until the cutoff for JHBuild
modulesets,
Hi,
So it's 2018, and all of the changes to the release scripts seem to be
holding up since the last release.
As we did not advertise an exact date for the cutoff, I suggest that we
target the next devel release (3.27.90) for discontinuation of JHBuild
moduleset XML - if there are no objections
News
First stable release of BuildStream
BuildStream 1.0.0 is all about API stability - for the past months we
have been reviewing our various API surfaces, implementing strategies
for revisioning of our interfaces and cleaning up. Long term stability
is very important for build
On Thu, 2017-11-30 at 11:44 -0600, Michael Catanzaro wrote:
> On 11/30/2017 11:15 AM, Tristan Van Berkom wrote:
> > $ cd ../gnome-modulesets
> > $ bst track core-deps/m4-common.bst base/crates.bst
> >
> > The result of this is we'll have specific commit references for t
On Thu, 2017-11-30 at 17:15 +, Tristan Van Berkom wrote:
> So this week I ploughed through this convert-to-tarballs.py script
> and I believe it's the last piece we are depending specifically on
> jhbuild for.
>
> So I did end up documenting how I did the 3.27.2
So this week I ploughed through this convert-to-tarballs.py script
and I believe it's the last piece we are depending specifically on
jhbuild for.
So I did end up documenting how I did the 3.27.2 release here[0], but
as things have changed in this particular regard I'll lay out an
outline for
On Tue, 2017-11-21 at 10:37 -0600, Michael Catanzaro wrote:
> On Tue, Nov 21, 2017 at 2:20 AM, Tristan Van Berkom
> > <tristan.vanber...@codethink.co.uk> wrote:
> > o nobody as far as I can tell *cares* about these static release
> > modulesets anyway, nobody
TL;DR:
In general, we build and test against master and specific branches in
git, and then last minute we convert to tarballs and "hope for the
best", this is fragile and makes it difficult to ever have any hope
of running CI against what we're actually going to release in advance
of
:
https://www.gnome.org/start/unstable
Cheers,
Tristan Van Berkom
GNOME Release Team
___
release-team@gnome.org
https://mail.gnome.org/mailman/listinfo/release-team
Release-team lurker? Do NOT participate in discussions.
On Tue, 2017-10-31 at 20:24 +, Javier Jardón wrote:
> On 31 October 2017 at 10:36, Tristan Van Berkom
> > <tristan.vanber...@codethink.co.uk> wrote:
>
>
> > I'm hoping that we can take a different strategy with a converted
> > BuildStream project than we
On Sun, 2017-10-29 at 11:41 -0500, Michael Catanzaro wrote:
> On Sun, Oct 29, 2017 at 5:38 AM, Tristan Van Berkom
> > <tristan.vanber...@codethink.co.uk> wrote:
> > Does this sound like a sensible plan ?
>
> Yes. Excellent. :)
>
> Do you want to take resp
On Sun, 2017-10-29 at 19:38 +0900, Tristan Van Berkom wrote:
> On Wed, 2017-10-11 at 22:30 +0900, Tristan Van Berkom wrote:
> > Hi !
> >
>
> Here is a follow up and status report.
[...]
> Status of builds
>
> I believe we've reached build p
On Wed, 2017-10-11 at 22:30 +0900, Tristan Van Berkom wrote:
> Hi !
>
Here is a follow up and status report.
Was hoping to get this out a whole week ago, but with significant
BuildStream maintenance overhead, and dealing with librsvg now using
rust, this was a bit delayed.
Summary
On Wed, 2017-10-11 at 17:15 +0100, Javier Jardón wrote:
[...]
> >
> > If we want people to start using Buildstream instead jhbuild, I think
> > we would need a step to step guide to build stuff. Basically a
> > equivalent of this: [1]
> >
> > Does BuildStream have something similar already?
Hi !
It's been a couple months since meeting at GUADEC, and forgive me if
I'm still not up to speed with things, but looking at this wiki page:
https://wiki.gnome.org/Schedule
...suggests that the dust is settling for the current 3.26 release and
we have not really started with 3.28 - so I
On Fri, Mar 8, 2013 at 12:48 AM, Martin Pitt martin.p...@ubuntu.com wrote:
Hello fellow GNOMErs,
after the first round of discussions a month ago[1] about the jhbuild
CI building/testing [2] I'd like to give some status update.
Along the same topic, I wanted to bring to light something that
On Thu, Feb 14, 2013 at 3:12 PM, Martin Pitt martin.p...@ubuntu.com wrote:
Hello Tristan,
Tristan Van Berkom [2013-02-14 6:42 +0900]:
Upon reading this particular part (and I noticed before you are
using mostly jhbuild mechanics), it leads me to wonder, how
granular exactly
First, this sounds like really interesting stuff, great news.
On Tue, Feb 12, 2013 at 3:43 PM, Martin Pitt martin.p...@ubuntu.com wrote:
Hello fellow GNOME developers,
this already came up as a side issue recently[1], but now we are at a
point where have reasonably stabilized our GNOME
News
- Correctly detect the required devhelp version (Javier Jardón)
- Sort objects in output by property reference, ensures a
GtkTreeModelFilter gets serialized after its 'child-model' (fixes bug
657164)
- Fixed crashers when performing Remove Parent (bug
54 matches
Mail list logo
