Re: 'staging' freeze

[Jascha Geerds]

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.

Re: 'staging' freeze

[Efraim Flashner]

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 authenticated:
> >
> >   https://ci.guix.gnu.org/jobset/staging
> >
> > Can someone remind me how to enable a disable jobset?  :-)
> 
> No easy way for now:
> 
> --8<---cut here---start->8---
> psql -d cuirass -c "update specifications set is_active = 1 where name = 
> 'staging';"
> --8<---cut here---end--->8---
> 
> does the trick.
> 
> Thanks,
> 
> Mathieu

I manually restarted some of the failed builds and they then built
without any problems (I'm looking at you ghc@8.10). Currently I believe
we could use a retry on aarch64 for staging as a whole; there was a
while where we had key issues and many packages failed to build so they
should be sent back for another try.

Currently the big series of packages I see left are the KDE packages, it
seems that 5.70 from ~2 years ago is too old for our version of Qt and
should really be updated.

I haven't yet tried reconfiguring my desktop with staging, it seemed a
bit early for that.


-- 
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' freeze

[Mathieu Othacehe]

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 enable a disable jobset?  :-)

No easy way for now:

--8<---cut here---start->8---
psql -d cuirass -c "update specifications set is_active = 1 where name = 
'staging';"
--8<---cut here---end--->8---

does the trick.

Thanks,

Mathieu

'staging' freeze

[Marius Bakke]

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 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 enable a disable jobset?  :-)

Full shortlog below:

Marius Bakke (100):
  [a49c829a05] gnu: libva: Update to 2.14.0.
  [87793b349f] gnu: libva: Use G-expressions.
  [a5436115a0] gnu: python-babel: Update to 2.10.3.
  [e850e361b6] gnu: python-sphinx: Update to 5.0.2.
  [9acd1a150f] gnu: python-certifi: Update to 2022.6.15.
  [647ec2ae78] gnu: python-requests: Update to 2.28.0.
  [a4283bf55f] gnu: python-urllib3: Update to 1.26.9.
  [3787f0d215] gnu: python-charset-normalizer: Update to 2.1.0.
  [32c676bbcd] gnu: libepoxy: Update to 1.5.10.
  [2692624ecf] gnu: libepoxy: Use new style.
  [c209146212] gnu: libwebp: Update to 1.2.2.
  [1535d8c5d8] gnu: libwebp: Simplify inputs.
  [7f209d8425] gnu: bluez: Update to 5.64.
  [6cb7e67dc5] gnu: bluez: Simplify inputs.
  [60f17c197d] gnu: bluez: Use new style.
  [a6bc7baa54] gnu: freeglut: Update to 3.2.2.
  [ddc538ac32] gnu: libical: Update to 3.0.14.
  [b40151ff4f] gnu: glu: Update to 9.0.2.
  [421a3c8172] gnu: libinput: Update to 1.19.4.
  [fce910af55] gnu: Remove postgresql@13 replacement.
  [6c7fcc71d1] gnu: qtbase: Build with PostgreSQL@14.
  [66e3adcad8] gnu: Remove unused patch.
  [de9d389c54] gnu: nspr: Update to 4.34.
  [fd004ddafa] gnu: nss, nss-certs: Update to 3.80.
  [b316d8b751] gnu: nspr: Use G-expressions.
  [01d1b285b8] gnu: nss: Use G-expressions.
  [dce7ed146d] gnu: libunwind: Enable tests.
  [d33f051740] gnu: libmng: Remove input labels.
  [5b48591176] gnu: python-pillow: Update to 9.2.0.
  [32b7e12e77] gnu: python-cffi: Update to 1.15.1.
  [97e2983310] gnu: python-cffi: Remove input labels.
  [f49eef43fd] gnu: iso-codes: Remove input labels.
  [03a4908ea5] gnu: mozjs: Build with the default LLVM.
  [13040cd309] gnu: mozjs: Remove obsolete workaround.
  [1f22184b22] gnu: python-attrs: Disable test deadline on all 
architectures.
  [572ed223ab] gnu: python-requests: Update to 2.28.1.
  [8d241c685a] gnu: python-chardet: Update to 5.0.0.
  [3b20467807] gnu: libva: Update to 2.15.0.
  [c0c6944f1a] gnu: perl-pod-parser: Update to 1.65.
  [9b4b5e33c4] gnu: perl-file-basedir: Update to 0.09.
  [c3da692293] gnu: perl-file-mimeinfo: Update to 0.33.
  [4625519f2c] gnu: libmbim: Update to 1.26.4.
  [718f75a55a] gnu: libqmi: Update to 1.30.8.
  [40992a1e02] gnu: modem-manager: Remove input labels.
  [9ee4069eb0] gnu: modem-manager: Use G-expression.
  [fdd40f391c] gnu: modem-manager: Remove obsolete input.
  [68aab436af] gnu: modem-manager: Update to 1.18.10.
  [f098d93352] gnu: nss, nss-certs: Update to 3.81.
  [f3673447cc] gnu: rust-smallvec: Update to 1.9.0.
  [ca5f1dd01e] gnu: rust-target-lexicon: Update to 0.12.4.
  [7b38d7731a] gnu: rust-cfg-expr: Add 0.10.3.
  [8d05800f67] gnu: rust-system-deps: Add 6.0.2.
  [e31cc7f0c9] gnu: rust-glib-sys: Add 0.15.
  [21e5e408bf] gnu: rust-cairo-sys: Add 0.15.1.
  [633c4ca407] gnu: rust-gobject-sys: Add 0.15.10.
  [ac393134e5] gnu: rust-glib-macros: Add 0.15.
  [bc9ea4f6e8] gnu: rust-glib: Add 0.15.12.
  [01c410a440] gnu: rust-cairo-rs: Add 0.15.12.
  [def0acd5e5] gnu: rust-pango-sys: Add 0.15.
  [713b289ff0] gnu: rust-pango: Add 0.15.10.
  [c5d4f2e8f0] gnu: rust-pangocairo-sys: Add 0.15.
  [2f9aa892c6] gnu: rust-pangocairo: Add 0.15.1.
  [b4678e4488] gnu: rust-gio-sys: Add 0.15.10.
  [bdd55817ed] gnu: rust-gdk-pixbuf-sys: Add 0.15.
  [79ee7d783a] gnu: rust-gio: Add 0.15.12.
  [c7bbf937ff] gnu: rust-gdk-pixbuf: Add 0.15.11.
  [de212cb74e] gnu: rust-itertools@0.10: Update to 0.10.3.
  [26afc27f29] gnu: rust-tinyvec@1: Update to 1.2.0.
  [e62dd8e762] gnu: rust-crc32fast: Update to 1.3.2.
  [822edbf08b] gnu: rust-gzip-header: Add 1.0.0.
  [fe76e27789] gnu: rust-mint: Update to 0.5.9.
  [1160932ea0] gnu: rust-deflate: Add 1.0.0.
  [4059158e6a] gnu: rust-png: Add 0.17.
  [1338e25610] gnu: rust-yeslogic-fontconfig-sys: Add 2.11.2.
  [0b770c2da4] gnu: librsvg: Update to 2.54.4.
  [7b69cd0740] Revert "gnu: librsvg: Update to 2.54.4."
  [b9a3083db3] gnu: qtscxml: Fix build failure.
  [f561830a5b] gnu: python-pympler: Update to 1.0.1.
  [431df1214e] gnu: python-dateutil: Adjust tests for Pytest 7.
  [30ac875bd8] gnu: python-sphinx: Update to 5.1.1.
  [a20a934081] gnu: python-freezegun: Update to 1.2.2.
  [c5860b97e9] gnu: 

Re: staging freeze

[zimoun]

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 emulation for AArch64 and armhf.

If it is possible –– not too late and not used with “guix refresh” ––,
could the attached patch go to “staging” and so all the Haskell packages
of v1.2 should be reproducible?  Otherwise, it should go to core-updates
and then wait the next round. :-)

Well, I could send the patch via guix-patches too. :-)
Let me know.


All the best,
simon

-- >8 --
>From 06eff8c02e22f583c252976f44db41554805293b Mon Sep 17 00:00:00 2001
From: zimoun 
Date: Thu, 15 Oct 2020 14:02:09 +0200
Subject: [PATCH] build-system/haskell: Disable parallel builds.

Parallel builds introduced by commit 67cb9fa2357026ee42ec5bb0923ec4dc4a43abe2
leads to unreproducibility.  Instead of reverting, default is set to #false
which allows user to locally build with parallelism.

* guix/build-system/haskell.scm (haskell-build): Turn off PARALLEL-BUILD? by
default.
---
 guix/build-system/haskell.scm | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/guix/build-system/haskell.scm b/guix/build-system/haskell.scm
index 8304e3b222..328d1139b0 100644
--- a/guix/build-system/haskell.scm
+++ b/guix/build-system/haskell.scm
@@ -1,6 +1,7 @@
 ;;; GNU Guix --- Functional package management for GNU
 ;;; Copyright © 2015 Federico Beffa 
 ;;; Copyright © 2020 Timothy Sample 
+;;; Copyright © 2020 Simon Tournier 
 ;;;
 ;;; This file is part of GNU Guix.
 ;;;
@@ -121,7 +122,7 @@ version REVISION."
 (haddock-flags ''())
 (tests? #t)
 (test-target "test")
-(parallel-build? #t)
+(parallel-build? #f)
 (configure-flags ''())
 (extra-directories ''())
 (phases '(@ (guix build haskell-build-system)

base-commit: 7269a591361138ac6fc122d465e45e2b8c4944be
-- 
2.28.0

Re: staging freeze

[Marius Bakke]

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 that we no longer use
>>transparent QEMU emulation for AArch64 and armhf.
>
> I have my groovy update ready to push to staging. Can I push it, or should I 
> wait for next time staging is open?

Sure, go ahead!  I suppose we can give people a day or two to brush up
any almost-ready patches.


signature.asc
Description: PGP signature

Re: staging freeze

[Julien Lepiller]

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
>transparent QEMU emulation for AArch64 and armhf.

I have my groovy update ready to push to staging. Can I push it, or should I 
wait for next time staging is open?

staging freeze

[Marius Bakke]

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: PGP signature

Staging freeze!

[Marius Bakke]

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 wanted!


signature.asc
Description: PGP signature

Re: Staging freeze

[Ludovic Courtès]

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 current branch on December 25 and try to
>> merge it on January 1.
>> 
>> These dates are inconvenient for many people. I propose we freeze the
>> branch and start building on December 27, and try to merge on January 3.
>
> Update:
>
> We are having some issues with the armhf and mips64el build machines
> that are keeping us from building all the packages.

That should be more or less solved.

I’ve just merged ‘master’ into ‘staging’ and started a new evaluation.

Ludo’.

Re: Staging freeze

[Leo Famulari]

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 January 1.
> 
> These dates are inconvenient for many people. I propose we freeze the
> branch and start building on December 27, and try to merge on January 3.

Update:

We are having some issues with the armhf and mips64el build machines
that are keeping us from building all the packages.


signature.asc
Description: PGP signature

Re: Staging freeze

[Ludovic Courtès]

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 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?  :-)
>> 
>> This ‘qemu-image’ job has been failing since Dec. 11, apparently because
>> the closure of the OS in build-aux/hydra/demo-os.scm has become more
>> than 1.4G (the size specified in build-aux/hydra/gnu-system.scm):
>> 
>>   https://hydra.gnu.org/job/gnu/master/qemu-image.x86_64-linux
>> 
>> I’m tempted to simply remove this job because it doesn’t buy us anything
>> compared to the system tests.
>
> Okay!
>
>> Objections?
>
> None here :)

Done in a3a27745013f3e5a287de3bf0187b2f72beb6965.

Ludo’.

Re: Staging freeze

[Leo Famulari]

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 
> > fundamental, yet to be diagnosed problem.
> 
> Yet to be diagnosed… and yet to be reported?  :-)
> 
> This ‘qemu-image’ job has been failing since Dec. 11, apparently because
> the closure of the OS in build-aux/hydra/demo-os.scm has become more
> than 1.4G (the size specified in build-aux/hydra/gnu-system.scm):
> 
>   https://hydra.gnu.org/job/gnu/master/qemu-image.x86_64-linux
> 
> I’m tempted to simply remove this job because it doesn’t buy us anything
> compared to the system tests.

Okay!

> Objections?

None here :)

Re: Staging freeze

[Ludovic Courtès]

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?  :-)

This ‘qemu-image’ job has been failing since Dec. 11, apparently because
the closure of the OS in build-aux/hydra/demo-os.scm has become more
than 1.4G (the size specified in build-aux/hydra/gnu-system.scm):

  https://hydra.gnu.org/job/gnu/master/qemu-image.x86_64-linux

I’m tempted to simply remove this job because it doesn’t buy us anything
compared to the system tests.

Objections?

Ludo’.

Re: Staging freeze

[Leo Famulari]

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 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 freeze the
>  > > branch and start building on December 27, and try to merge on 
> January 3.
>  > 
>  > And the build failures are rolling in :)
>  > 
>  > https://hydra.gnu.org/eval/109410?full=1=master#tabs-now-fail
>  
>  The 'qemu-image' build failed due to a lack of disk space, presumably on
>  the VM image file:
>  
>  --
>  registering closures...
>  error: setting journal mode: database or disk is full
>  ERROR: In procedure scm-error:
>  ERROR: failed to register store items "/xchg/system"
>  --
>  https://hydra.gnu.org/build/1741220
>  
>  Any advice? I'm not sure where to start looking in the code.
> 
> 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.

I've seen this error before when I fail to create a large enough blank
QEMU image. I think that's the problem here, but I'm not sure where this
qemu-image derivation comes from in the Guix code base, so I'm not sure
what to try adjusting or even how to replicate the failure.


signature.asc
Description: PGP signature

Re: Staging freeze

[John Darrington]

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.
 > > 
 > > 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 freeze the
 > > branch and start building on December 27, and try to merge on January 
3.
 > 
 > And the build failures are rolling in :)
 > 
 > https://hydra.gnu.org/eval/109410?full=1=master#tabs-now-fail
 
 The 'qemu-image' build failed due to a lack of disk space, presumably on
 the VM image file:
 
 --
 registering closures...
 error: setting journal mode: database or disk is full
 ERROR: In procedure scm-error:
 ERROR: failed to register store items "/xchg/system"
 --
 https://hydra.gnu.org/build/1741220
 
 Any advice? I'm not sure where to start looking in the code.

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.

Would it be worth restarting the build and crossing fingers?

J'



-- 
Avoid eavesdropping.  Send strong encrypted email.
PGP Public key ID: 1024D/2DE827B3 
fingerprint = 8797 A26D 0854 2EAB 0285  A290 8A67 719C 2DE8 27B3
See http://sks-keyservers.net or any PGP keyserver for public key.



signature.asc
Description: Digital signature

Re: Staging freeze

[Leo Famulari]

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 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 freeze the
> > branch and start building on December 27, and try to merge on January 3.
> 
> And the build failures are rolling in :)
> 
> https://hydra.gnu.org/eval/109410?full=1=master#tabs-now-fail

The 'qemu-image' build failed due to a lack of disk space, presumably on
the VM image file:

--
registering closures...
error: setting journal mode: database or disk is full
ERROR: In procedure scm-error:
ERROR: failed to register store items "/xchg/system"
--
https://hydra.gnu.org/build/1741220

Any advice? I'm not sure where to start looking in the code.


signature.asc
Description: PGP signature

Re: Staging freeze

[Leo Famulari]

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 January 1.
> 
> These dates are inconvenient for many people. I propose we freeze the
> branch and start building on December 27, and try to merge on January 3.

And the build failures are rolling in :)

https://hydra.gnu.org/eval/109410?full=1=master#tabs-now-fail


signature.asc
Description: PGP signature

Re: Staging freeze

[Leo Famulari]

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 [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 freeze the
>  branch and start building on December 27, and try to merge on January 3.
>  
>  [0]
>  http://lists.gnu.org/archive/html/guix-devel/2016-10/msg00933.html
> 
> 
> Sounds good to me.

I'll start the evaluation of the staging branch in ~12 hours.


signature.asc
Description: PGP signature

Re: Staging freeze

[John Darrington]

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 January 1.
 
 These dates are inconvenient for many people. I propose we freeze the
 branch and start building on December 27, and try to merge on January 3.
 
 [0]
 http://lists.gnu.org/archive/html/guix-devel/2016-10/msg00933.html


Sounds good to me.

J'



-- 
Avoid eavesdropping.  Send strong encrypted email.
PGP Public key ID: 1024D/2DE827B3 
fingerprint = 8797 A26D 0854 2EAB 0285  A290 8A67 719C 2DE8 27B3
See http://sks-keyservers.net or any PGP keyserver for public key.



signature.asc
Description: Digital signature

Staging freeze

[Leo Famulari]

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 freeze the
branch and start building on December 27, and try to merge on January 3.

[0]
http://lists.gnu.org/archive/html/guix-devel/2016-10/msg00933.html


signature.asc
Description: PGP signature