Re: ‘staging’ branch is open!

[Christopher Baines]

Ludovic Courtès  writes:

> Hopefully we’ll get a clearer picture in the coming days…

There is starting to be some information in the QA data service instance:

  
https://data.qa.guix.gnu.org/compare-by-datetime/package-derivations?base_branch=master_datetime=_branch=staging_datetime==x86_64-linux=none_change=broken_name=_results=_results=on

That page should show things that build on master, but fail to build on
staging.

There are some false positives though, like python-protobuf that was
recently fixed on master and should be working on staging once master is
merged in.

There's probably some false negatives as well, since the build
information is coming from bordeaux.guix.gnu.org, and it's not yet
attempted to build everything for staging yet.

Chris


signature.asc
Description: PGP signature

Re: python-cryptography and rust [was: Re: ‘staging’ branch is open!]

[Ludovic Courtès]

Hello,

Efraim Flashner  skribis:

> On Sun, May 15, 2022 at 11:22:05PM +0200, Ludovic Courtès wrote:

[...]

>> Yes, so what do you mean?  Should we keep the old 3.3.1 for use on
>> non-x86_64 platforms?  Would that even work?
>
> I'll add 3.4.8 for non-x86_64 platforms and see if I can do something
> about the rust inputs for python-cryptography, to shorten the graph a
> bit and note which crates are "locked" in their current versions.

OK.

>> Besides, since mrustc was updated on ‘staging’, does that new version
>> better support platforms other than x86_64?
>
> I hear we should be able to do aarch64 with our new version of mrustc
> but I haven't tried building it yet on my machines.

On i686 as well maybe?

> I'd leave it as a happy bonus for now and leave aarch64 with the C
> counterparts for this round, rather than relying on the rust bootstrap
> chain, considering how much RAM it can use.

Yup, makes sense.  We can try that eventually on a branch.

Ludo’.

Re: ‘staging’ branch is open!

[Ludovic Courtès]

Hi,

zimoun  skribis:

> On Sun, 15 May 2022 at 22:55, Ludovic Courtès  wrote:
>
>> I propose freezing tomorrow evening, Monday 16th ca. 8PM CEST.
>> How does that sound?
>
> LGTM.  The branch is now frozen and receive only fixes, right?

An update: ci.guix wasn’t building much lately due to a bug that was
finally fixed a few days ago:

  https://issues.guix.gnu.org/55441

However, to quote Forest Gump, “shit happens”, and indeed it happened to
us: we lost SSH access to berlin.guix.gnu.org about the time we were
going to reconfigure it so it has that bug fix.

So, while working on it, the schedule itself is frozen.  :-)

Hopefully we’ll get a clearer picture in the coming days…

Ludo’.

Re: ‘staging’ branch is open!

[zimoun]

Hi,

On Sun, 15 May 2022 at 22:55, Ludovic Courtès  wrote:

> I propose freezing tomorrow evening, Monday 16th ca. 8PM CEST.
> How does that sound?

LGTM.  The branch is now frozen and receive only fixes, right?

Note the «Aborted» status on .


Cheers,
simon

Re: python-cryptography and rust [was: Re: ‘staging’ branch is open!]

[Efraim Flashner]

On Sun, May 15, 2022 at 11:22:05PM +0200, Ludovic Courtès wrote:
> Hi Efraim,
> 
> (+Cc: Marius.)
> 
> Efraim Flashner  skribis:
> 
> > python-cryptography now depends on rust. We're going to need 3.4.8 from
> > the 3.4 series for the other architectures. Currently
> > python-cryptography@36.0.1 is gating about 3000 packages.
> 
> Yes, so what do you mean?  Should we keep the old 3.3.1 for use on
> non-x86_64 platforms?  Would that even work?

I'll add 3.4.8 for non-x86_64 platforms and see if I can do something
about the rust inputs for python-cryptography, to shorten the graph a
bit and note which crates are "locked" in their current versions.

> Besides, since mrustc was updated on ‘staging’, does that new version
> better support platforms other than x86_64?

I hear we should be able to do aarch64 with our new version of mrustc
but I haven't tried building it yet on my machines. I'd leave it as a
happy bonus for now and leave aarch64 with the C counterparts for this
round, rather than relying on the rust bootstrap chain, considering how
much RAM it can use.

> Thanks for the heads-up,
> Ludo’.
> 

-- 
Efraim Flashner  אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted


signature.asc
Description: PGP signature

Re: python-cryptography and rust [was: Re: ‘staging’ branch is open!]

[Ludovic Courtès]

Hi Efraim,

(+Cc: Marius.)

Efraim Flashner  skribis:

> python-cryptography now depends on rust. We're going to need 3.4.8 from
> the 3.4 series for the other architectures. Currently
> python-cryptography@36.0.1 is gating about 3000 packages.

Yes, so what do you mean?  Should we keep the old 3.3.1 for use on
non-x86_64 platforms?  Would that even work?

Besides, since mrustc was updated on ‘staging’, does that new version
better support platforms other than x86_64?

Thanks for the heads-up,
Ludo’.

Re: ‘staging’ branch is open!

[Ludovic Courtès]

Hi Guix!

Ludovic Courtès  skribis:

> zimoun  skribis:
>
>> The schedule could be:
>>
>>  + freeze the ’staging’ branch on the Sun May, 8th
>>  + fix until it is ready, targeting the Sun, May 22th
>>  + prepare a release for June
>
> So now I look ridiculous for being derailed myself…  But yes, something
> like this offset by one (or two?) week would be awesome.

I propose freezing tomorrow evening, Monday 16th ca. 8PM CEST.
How does that sound?

>From there we can start testing and fixing things.

The branch has updates for a few important packages and partial
ungrafting (util-linux and openssl grafts remain).

Thanks,
Ludo’.

python-cryptography and rust [was: Re: ‘staging’ branch is open!]

[Efraim Flashner]

python-cryptography now depends on rust. We're going to need 3.4.8 from
the 3.4 series for the other architectures. Currently
python-cryptography@36.0.1 is gating about 3000 packages.

-- 
Efraim Flashner  אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted


signature.asc
Description: PGP signature

Re: ‘staging’ branch is open!

[zimoun]

Hi,

On Sun, 08 May 2022 at 00:04, Ludovic Courtès  wrote:
> zimoun  skribis:
>
>> The schedule could be:
>>
>>  + freeze the ’staging’ branch on the Sun May, 8th
>>  + fix until it is ready, targeting the Sun, May 22th
>>  + prepare a release for June
>
> So now I look ridiculous for being derailed myself…  But yes, something
> like this offset by one (or two?) week would be awesome.
>
> Who’s in?  :-)

Considering the current constraints on my schedule, now it is becoming
hard nor impossible to free enough time in the next two weeks.

I am in, but after the 22th. :-)


Cheers,
simon

Re: ‘staging’ branch is open!

[Ludovic Courtès]

Hi!

zimoun  skribis:

> The schedule could be:
>
>  + freeze the ’staging’ branch on the Sun May, 8th
>  + fix until it is ready, targeting the Sun, May 22th
>  + prepare a release for June

So now I look ridiculous for being derailed myself…  But yes, something
like this offset by one (or two?) week would be awesome.

Who’s in?  :-)

Thanks,
Ludo’.

Re: ‘staging’ branch is open!

[Maxim Cournoyer]

Hi,

Ludovic Courtès  writes:

> Hi!
>
> The ‘staging’ branch is open!  Which means that changes with “between
> 300 and 1,800 rebuilds” (info "(guix) Submitting Patches") can go there;
> now’s the time to (re)send package updates in that ballpark.

Just to be clear, it was never closed :-).

> Incidentally, I was considering ungrafting things on that branch, even
> those that go beyond the 1,800 dependents limit, since this is almost
> always a safe change and ci.guix now has the capacity and stability
> needed for that.
>
> What do people think?
>
> I think we should aim for a freeze in one or two weeks, merging in three
> weeks, and resume work on the new release to be done sometime after the
> merge.
>
> Thoughts?

Seems like a fine plan.  Note that although we have the storage capacity
on paper, we still need to complete the Berlin config to make use of it
before we can afford to stress it with as many world rebuilds attempts
as we'd like.

Thanks,

Maxim

Re: ‘staging’ branch is open!

[zimoun]

Hi,

On Sat, 30 Apr 2022 at 01:08, Ludovic Courtès  wrote:

> Incidentally, I was considering ungrafting things on that branch, even
> those that go beyond the 1,800 dependents limit, since this is almost
> always a safe change and ci.guix now has the capacity and stability
> needed for that.

Cool!  I am in for ungrafting things. :-)


> I think we should aim for a freeze in one or two weeks, merging in three
> weeks, and resume work on the new release to be done sometime after the
> merge.

The schedule could be:

 + freeze the ’staging’ branch on the Sun May, 8th
 + fix until it is ready, targeting the Sun, May 22th
 + prepare a release for June

WDYT?


Cheers,
simon

‘staging’ branch is open!

[Ludovic Courtès]

Hi!

The ‘staging’ branch is open!  Which means that changes with “between
300 and 1,800 rebuilds” (info "(guix) Submitting Patches") can go there;
now’s the time to (re)send package updates in that ballpark.

Incidentally, I was considering ungrafting things on that branch, even
those that go beyond the 1,800 dependents limit, since this is almost
always a safe change and ci.guix now has the capacity and stability
needed for that.

What do people think?

I think we should aim for a freeze in one or two weeks, merging in three
weeks, and resume work on the new release to be done sometime after the
merge.

Thoughts?

Ludo’.

Re: Staging branch is OPEN

[Alex Griffin]

Never mind, I see that it was already updated.

-- 
Alex Griffin

On Thu, Dec 12, 2019, at 5:38 PM, Alex Griffin wrote:
> Is eudev 3.2.9 an appropriate update for staging? It contains an 
> important fix for Librem laptop keyboards.
> 
> $ guix refresh -l eudev
> Building the following 964 packages would ensure 1723 dependent 
> packages are rebuilt: ...
> 
> -- 
> Alex Griffin
> 
> On Wed, Dec 11, 2019, at 10:34 PM, Marius Bakke wrote:
> > Guix,
> > 
> > The 'staging' branch is awaiting your patches.  Please submit your
> > changes by the end of this week (i.e. before Monday, 2019-12-15).
> > 
> > Thanks,
> > Marius
> > 
> > Attachments:
> > * signature.asc
> 
>

Re: Staging branch is OPEN

[Alex Griffin]

Is eudev 3.2.9 an appropriate update for staging? It contains an important fix 
for Librem laptop keyboards.

$ guix refresh -l eudev
Building the following 964 packages would ensure 1723 dependent packages 
are rebuilt: ...

-- 
Alex Griffin

On Wed, Dec 11, 2019, at 10:34 PM, Marius Bakke wrote:
> Guix,
> 
> The 'staging' branch is awaiting your patches.  Please submit your
> changes by the end of this week (i.e. before Monday, 2019-12-15).
> 
> Thanks,
> Marius
> 
> Attachments:
> * signature.asc

Staging branch is OPEN

[Marius Bakke]

Guix,

The 'staging' branch is awaiting your patches.  Please submit your
changes by the end of this week (i.e. before Monday, 2019-12-15).

Thanks,
Marius


signature.asc
Description: PGP signature

Re: 'staging' branch is OPEN

[Efraim Flashner]

On Tue, Oct 08, 2019 at 09:29:05PM +0200, Marius Bakke wrote:
> Guix,
> 
> Now that 'core-updates' is merged (\o/), it's time to restart the
> regular 'staging' cycles.
> 
> Please push your patches before Monday, October 14th.  After that the
> branch will be 'frozen' and hopefully merged some days later barring
> regressions.

Now I have to decide whether to bump qt to 5.12.5 or up to 5.13.1 ...


-- 
Efraim Flashner  אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted


signature.asc
Description: PGP signature

Re: 'staging' branch is OPEN

[Björn Höfling]

On Tue, 08 Oct 2019 21:29:05 +0200
Marius Bakke  wrote:

> Guix,
> 
> Now that 'core-updates' is merged (\o/), it's time to restart the
> regular 'staging' cycles.
> 
> Please push your patches before Monday, October 14th.  After that the
> branch will be 'frozen' and hopefully merged some days later barring
> regressions.

Thanks to everyone who helped on core-updates and thanks Marius for
announcing the state of 'staging'. I wish the state of the
core-updates/staging branches would be clearer from now on.

Björn



pgpES70Er0bTY.pgp
Description: OpenPGP digital signature

'staging' branch is OPEN

[Marius Bakke]

Guix,

Now that 'core-updates' is merged (\o/), it's time to restart the
regular 'staging' cycles.

Please push your patches before Monday, October 14th.  After that the
branch will be 'frozen' and hopefully merged some days later barring
regressions.

Thanks!


signature.asc
Description: PGP signature