Hi,
I'm really interested in Rust 1.60. Is there any progress on merging the
staging branch? I see a lot of commits but I'm not sure whether we come closer
to the merge or drifting away from it.
On Sun, Aug 28, 2022 at 05:56:08PM +0200, Mathieu Othacehe wrote:
>
> Hey Marius,
>
> > The 'staging' branch is in a pretty good shape, let's get it merged!
>
> Nice work!
>
> > I'm fairly rusty when it comes to Cuirass, and don't see a button to
> > start the jobset here even when
Hey Marius,
> The 'staging' branch is in a pretty good shape, let's get it merged!
Nice work!
> I'm fairly rusty when it comes to Cuirass, and don't see a button to
> start the jobset here even when authenticated:
>
> https://ci.guix.gnu.org/jobset/staging
>
> Can someone remind me how to
Hi Guix,
The 'staging' branch is in a pretty good shape, let's get it merged!
Highlights from this branch:
* Rust 1.60
* Gstreamer 1.20.3
* Sphinx 5.1.1
* ruby-nokogiri and its dependencies is no longer in the bootstrap path
of TeX Live, so they can be more freely updated on 'master'
I'm
Hi Marius,
On Tue, 13 Oct 2020 at 23:54, Marius Bakke wrote:
> I've pushed a set of updates to the long-overdue "staging" branch.
>
> Let's get it merged once Cuirass is done building for the various
> architectures. Not sure how long that takes now that we no longer use
> transparent QEMU
Julien Lepiller writes:
> Le 13 octobre 2020 17:54:16 GMT-04:00, Marius Bakke a écrit :
>>Hello Guix,
>>
>>I've pushed a set of updates to the long-overdue "staging" branch.
>>
>>Let's get it merged once Cuirass is done building for the various
>>architectures. Not sure how long that takes now
Le 13 octobre 2020 17:54:16 GMT-04:00, Marius Bakke a écrit :
>Hello Guix,
>
>I've pushed a set of updates to the long-overdue "staging" branch.
>
>Let's get it merged once Cuirass is done building for the various
>architectures. Not sure how long that takes now that we no longer use
Hello Guix,
I've pushed a set of updates to the long-overdue "staging" branch.
Let's get it merged once Cuirass is done building for the various
architectures. Not sure how long that takes now that we no longer use
transparent QEMU emulation for AArch64 and armhf.
signature.asc
Description:
Guix,
The 'staging' branch has seen plenty of changes recently and is now
"frozen".
Changes in the current iteration include Mesa 20.0.7, Rust 1.39 as the
default Rust compiler, Qt 5.14.2, KDE Frameworks 5.70, updates and
overhaul of all Vulkan packages, and lots of other minor changes.
Testers
Leo Famulari skribis:
> On Fri, Dec 23, 2016 at 12:23:39AM -0500, Leo Famulari wrote:
>> The last staging branch was merged into the master branch on December
>> 11.
>>
>> According to the 3 week staging cycle we are trying to adhere to [0],
>> this would mean we freeze the
On Fri, Dec 23, 2016 at 12:23:39AM -0500, Leo Famulari wrote:
> The last staging branch was merged into the master branch on December
> 11.
>
> According to the 3 week staging cycle we are trying to adhere to [0],
> this would mean we freeze the current branch on December 25 and try to
> merge it
Leo Famulari skribis:
> On Thu, Dec 29, 2016 at 06:51:46PM +0100, Ludovic Courtès wrote:
>> Hi!
>>
>> John Darrington skribis:
>>
>> > For what it's worth, I find that building *anything* related to qemu fails
>> > for different reasons in
On Thu, Dec 29, 2016 at 06:51:46PM +0100, Ludovic Courtès wrote:
> Hi!
>
> John Darrington skribis:
>
> > For what it's worth, I find that building *anything* related to qemu fails
> > for different reasons in about 2/3 attempts. So I think there is a
> >
Hi!
John Darrington skribis:
> For what it's worth, I find that building *anything* related to qemu fails
> for different reasons in about 2/3 attempts. So I think there is a
> fundamental, yet to be diagnosed problem.
Yet to be diagnosed… and yet to be reported?
On Wed, Dec 28, 2016 at 10:17:31AM +0100, John Darrington wrote:
> On Tue, Dec 27, 2016 at 11:13:05PM -0500, Leo Famulari wrote:
> On Tue, Dec 27, 2016 at 06:56:44PM -0500, Leo Famulari wrote:
> > On Fri, Dec 23, 2016 at 12:23:39AM -0500, Leo Famulari wrote:
> > > The last staging
On Tue, Dec 27, 2016 at 11:13:05PM -0500, Leo Famulari wrote:
On Tue, Dec 27, 2016 at 06:56:44PM -0500, Leo Famulari wrote:
> On Fri, Dec 23, 2016 at 12:23:39AM -0500, Leo Famulari wrote:
> > The last staging branch was merged into the master branch on December
> > 11.
> >
On Tue, Dec 27, 2016 at 06:56:44PM -0500, Leo Famulari wrote:
> On Fri, Dec 23, 2016 at 12:23:39AM -0500, Leo Famulari wrote:
> > The last staging branch was merged into the master branch on December
> > 11.
> >
> > According to the 3 week staging cycle we are trying to adhere to [0],
> > this
On Fri, Dec 23, 2016 at 12:23:39AM -0500, Leo Famulari wrote:
> The last staging branch was merged into the master branch on December
> 11.
>
> According to the 3 week staging cycle we are trying to adhere to [0],
> this would mean we freeze the current branch on December 25 and try to
> merge it
On Fri, Dec 23, 2016 at 07:00:38AM +0100, John Darrington wrote:
> On Fri, Dec 23, 2016 at 12:23:39AM -0500, Leo Famulari wrote:
> The last staging branch was merged into the master branch on December
> 11.
>
> According to the 3 week staging cycle we are trying to adhere to
On Fri, Dec 23, 2016 at 12:23:39AM -0500, Leo Famulari wrote:
The last staging branch was merged into the master branch on December
11.
According to the 3 week staging cycle we are trying to adhere to [0],
this would mean we freeze the current branch on December 25 and
The last staging branch was merged into the master branch on December
11.
According to the 3 week staging cycle we are trying to adhere to [0],
this would mean we freeze the current branch on December 25 and try to
merge it on January 1.
These dates are inconvenient for many people. I propose we
21 matches
Mail list logo