Re: Cuirass upgrade on ci.guix

Hey, > 1. Better throughput. I fixed a bug that would lead “workers” to > eventually get ignored by ‘cuirass remote-server’, meaning they > would become idle until either the server or the worker is > restarted¹. Wow, that's a nice catch! > 2. Evaluation can be triggered

Re: Implementing the guix-dameon in Guile

Hey Chris, Congrats on getting the grant! I'm sure it will lead to a lot of positive things. I tried it myself a couple years ago, for the exact same subject, without success. > I imagine the daemon could be structured as a set of actors (it’s really > my thing these days ;-)), with an eye on

Cross compilation status

Hello, In order for Guix to become an alternative to tools such as Yocto and Buildroot, having most or all our packages cross-compiling is a prerequisite. Here is a status of cross-compilation in Guix. For cross-compilation to work, the build-system needs to support cross-compilation. The

Re: 01/09: services: base: Add extra-env support to guix-configuration.

Hey, > Nitpick: To stick to existing naming conventions, could we rename it to > ‘environment-variables’ or ‘environment’? I changed to environment and pushed. Thanks, Mathieu

Re: 04/08: gnu: QEMU: Unbundle iPXE.

Hello Marius, > glib > gtk+ > + ipxe-qemu > libaio > libcacard;smartcard support > attr libcap-ng ;VirtFS support I just noticed that: --8<---cut

Re: Has ci.guix.gnu.org stopped building?

> This was fixed with commit 658c09333da095edf6e1b3c5e351a7bfa3c87354 Builds have restarted! Good catch, thanks! Mathieu

Re: Has ci.guix.gnu.org stopped building?

Hello Leo, > According to the web interface, ci.guix.gnu.org stopped building things > on December 31, with evaluation 79343. > > Is this true? What's wrong? Yes the master specification has not been evaluated since December 30. It looks like all subsequent evaluations are never finishing

Re: Release progress, week 8

Hey Ludo, > fe563a87ad gnu: texinfo, info-reader: Do not run tests when cross-compiling. Wow, that's a lot of fixes! > Yesterday on IRC we discussed an installer crash received at > dump.guix.gnu.org. Did you or will you have time to look into it? Yes and I think that for some reason we

Re: Release progress, week 8

Hey, Thanks for your hard work to publish the RC1! > Now we need reports from users to act upon. I’d say we can decide next > week whether we need an RC2 or not. I can handle the next release > candidate or the release itself, but I’ll be unavailable on Dec. 12–15. I noticed that we have

Re: Release progress, week 6

Hello, >It would seem that a lot of aarch64 builds are queued but not >getting processed. Any idea how to investigate that, Mathieu? That would be because we only had a single ARM machine available till this week (kreuzberg). It seems that overdrive1 and grunewald are back

Re: i586-gnu builds on ci.guix

Hello, > Alas Cuirass depends on Fibers, which is currently Linux-only¹, so we > cannot {cross-,}build it for GNU/Hurd. The good news is that > ‘remote-worker.scm’ itself doesn’t seem to use Fibers. So I wonder if > we could arrange to build a stripped-down package that contains nothing > but

Re: Release progress, week 5

Hey, >Probably we’ll postpone that post-release and drop i586-gnu from >‘etc/release-manifest.scm’ in the meantime. Objections? No. > - armhf-linux: No progress; can we arrange so that ci.guix at least >builds these core subset of packages? We already have the

Installer for 1.4.0

Hello, The installer has been hardened during the past months when it comes to error reporting: - Guile exceptions are caught, displayed and possibly uploaded to dump.guix.gnu.org if the user agrees to do so. - Failing system commands can be run again. I think that it would be nice to go a

Re: Status of armhf-linux and powerpc64le-linux

Hey, > How frequently does that machine become unreachable? > > Its uptime right now is “only” 51 days, but it seems to have been > reliably building things so far (surprisingly so!). Oh so it must be available from the Cuirass point of view but not from the guix offload point of view. I'll

Re: Release progress, week 2

Hey, Thanks for the update! > - armhf-linux is disabled on ci.guix due to improper offloading >setup (probably along the lines of >). Should we try and reenable >it, or should we drop it? > > - powerpc64le-linux is disabled

Maintainers meeting notes.

Hello, For the last six months or so, the maintainers have been conducting monthly meetings on Jami. They are scheduled every first Tuesday of the month. It is often the occasion to plan some actions and discuss the administration of the build farm. The meeting notes are available here:

Re: branch master updated: services: Add file system utilities to profile.

Hey, > So it would seem like e2fsprogs is not being added to the profile of the > installation image. I think that's because there is no ext4 file-system needed for boot, as root is an iso9660 file-system. I added e2fsprogs to the operating-system packages for this specific test with:

Pick your team!

Hello, We recently introduced a teams.scm[1] file defining different teams such as "Julia team", "Lisp team" or "Mentors". If you are a newcomer seeking for some guidance to contribute to a Lisp package, you can run the following command: --8<---cut

Re: 02/04: services: Add samba service.

Hello, Thanks for this new service :) I noticed that while the "samba" test works fine on my machine, it fails on the CI: https://ci.guix.gnu.org/build/1495525/log/raw any idea why? Mathieu

Re: 04/07: guix: Add compression module.

Hey Ludo, > While I agree this should be factorize, I wonder if this should be > promoted to (guix compression). The module name intuitively is a better > fit for the compression-related things currently in (guix utils). > > Not sure, maybe (gnu compression) would make more sense? Thanks for

Re: 02/02: gnu: shepherd: Update to 0.9.2.

Hey Ludo, The installation system tests have fail this night and I suspect this is related with the shepherd update. The problem seems to occur when we restart the guix-daemon service before running the installation command, in the install-system procedure. Any idea what could cause it? The

Re: branch master updated: gnu: gitolite: Wrap programs instead of using propagated inputs.

Hello David, I noticed that the gitolite test is now failing. Any chance it is related to the recent work on the package? https://ci.guix.gnu.org/build/1333185/details Thanks Mathieu

Re: 'staging' freeze

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

Re: branch master updated: gnu: python-lxml: Update to 4.6.5.

Hey > * gnu/packages/xml.scm (python-lxml): Update to 4.6.5. I had to revert it as it caused >15k rebuilds. I also cancelled all the triggered builds in the CI. Thanks, Mathieu

Re: Teams

Hello Ricardo, I would suggest to extend a bit the scope of this idea. What about creating an etc/tutors.scm file as the one attached. This way people would run something like: --8<---cut here---start->8--- git send-email $(get-tutors.scm HEAD^^) *.patches

Re: Donation of used Softiron Overdrive 1000

Hello Julien and Reza, Thanks for the donation! We already have two Overdrive 1000 connected to the build farm behind ci.guix.gnu.org (overdrive1 and dover machines). Adding an extra one, and have it hosted at your place Julien would be great :). You can then follow the procedure described

Re: Dropping gzip-compressed substitutes

Hey Ludo, > As discussed on IRC, I’m skeptical about this because: > > 1. It requires the development and testing of a custom tool that’s > easy to get wrong—e.g., it removes a gzipped nar for something that > had nothing but gzip available, etc. > > 2. That code would have to run

Re: Dropping gzip-compressed substitutes

ata. I hope the script will be able to complete within a reasonable amount of time, but we cannot know before trying it out :). Thanks, Mathieu >From bd306a8b20f2033d67755dd332a5d33b2f6b822d Mon Sep 17 00:00:00 2001 From: Mathieu Othacehe Date: Tue, 8 Feb 2022 14:28:56 +0100 Subject: [PATCH 1/1

Re: License of your contributions to the blog at guix.gnu.org

Hey Ludo, > Do you agree with the proposed licensing terms for your contributions to > the blog? I agree. Thanks, Mathieu

Re: File search

Hello Ludo! > Lately I found myself going several times to > to look for packages providing a given > file and I thought it’s time to do something about it. Yeah, I'm also thinking regularly about it but giving up because setting up this mechanism properly turns

Preparing the 1.4.0 release.

Hello, As you may know we have started working actively on the next Guix release. * The release branch is available here: https://git.savannah.gnu.org/cgit/guix.git/log/?h=version-1.4.0 * It is built by Cuirass here: https://ci.guix.gnu.org/jobset/version-1.4.0 It would be great if we

Re: "make dist" fails ... en@boldquote: warning: PO file headder missing or invalid

Hello, >> > I've also in the past implored to set up a ci job for "make dist" to >> > make it at least easier to figure out which commits trigger these >> > issues... how can I help move that forward? :) > > Mathieu, what does Cuirass need to make that happens? That would require to have a

Re: Branch with only available substitutes ?

Hello, > Short answer: yes, but someone has to not just ask whether it's > possible or tell it ‘should be easy’, and actually implement all this. > Also, have a look at channel-with-substitutes-available. > It's not sufficiently general for your use case though. There's also a pending patch

Re: Solstice infrastructure hackathon

Hello, > That's not to say there's not something to be gained by upgrading the > bayfront hardware, some SSD storage would be ideal to speed up the > coordinator and builds. While we are talking infrastructure, a short digression on the current situation. The Berlin build farm is providing

Re: CI status

> * The cuirass-remote-server Avahi service is no longer visible when > running "avahi-browse -a". I strongly suspect that this is related to > the static-networking update, even if I don't have a proof for > now. This means that the remote-workers using Avahi for discovering >

CI status

Hello, You must have noticed that the CI is currently struggling a bit. Here is a small recap of the situation. * The IO operations on Berlin are mysteriously slow. Removing files from /gnu/store/trash is taking ages. This is reported here: https://issues.guix.gnu.org/51787. We have to

Re: core-updates-frozen branch merged

Hey, > That's it! Enjoy the latest additions and improvements, and report any > issues you encounter! That's great news! Thanks to all the people that have been involved and special thanks to you Maxim for your commitment. Mathieu

Re: branch master updated: remote-server: Fix fetch worker crash.

Hey Ludo, > I think it’s be safer (less prone to TOCTTOU races) to write it as: > > (catch 'system-error > (lambda () > (register-gc-roots drv)) > (lambda args > (unless (= ENOENT (system-error-errno args)) ;collected in the meantime > (apply throw args Oh,

Re: 04/05: gnu: petsc: Update to 3.16.1.

Hey, > * gnu/packages/maths.scm (petsc): Update to 3.16.1. > [native-inputs]: Use PYTHON instead of PYTHON-2. Add WHICH. > [arguments]: Rewrite using gexps. Pass '--with-openblas-dir'. In > 'configure' phase, modify "config/example_template.py". I noticed that petsc-*

Re: 01/03: gnu: freecad: Switch to vtk-9.

Hey Thiago! > This duplicates the line for ‘freedink-engine-fix-sdl-hints.patch’. Thanks for the heads up, fixed with: 854120d01ffe8b209fa8d897ba0fcf39ce2cdf32. Mathieu

Re: Disarchive update

Hey, > That’d be nice! How do we do that again? The build-outputs field of the record must be used as explained here: https://guix.gnu.org/cuirass/manual/html_node/Specifications.html#Specifications. This field cannot be manipulated via the web interface yet. I think the easier way to

Re: Disarchive update

Hey Ludo, > https://ci.guix.gnu.org/eval/29213?status=succeeded Nice! It looks like an expensive operation, maybe we should increase its period to 24 hours or so? > 2. On berlin, add an mcron job that periodically copies the output of > the latest “disarchive-collection” build to a

Re: core-updates-frozen: Planning for the last world rebuild

Hey Ricardo, > It should be fine now. I didn’t run the test myself, but I ran most of the > commands and found a few more hardcoded tool file names that referenced /sbin > or /usr/bin. Yes, I confirm it passes! I also fixed the childhurd test. Only 9 tests to go :). Thanks, Mathieu

Re: guix weather -m etc/sources-manifest.scm and CI?

Hey Ludo, > -package system)) > - packages))) > + (let ((manifests (arguments->manifests rest channels))) > +(manifests->jobs store manifests))) This sounds great to me :) Thanks, Mathieu

Re: guix weather -m etc/sources-manifest.scm and CI?

Hey! > Mathieu, could it have to do with the fact that the manifest is within > the ‘guix’ channel? Using the attached little reproducer, I get a more interesting backtrace: --8<---cut here---start->8--- Backtrace: In ice-9/boot-9.scm: 1752:10 11

Re: core-updates-frozen: Planning for the last world rebuild

Hello Ricardo, > I fixed the build. Also had to upgrade 389-ds-base to get around a linker > error. Thanks for your support here! The ldap test is now run, but sadly there are some failures: https://ci.guix.gnu.org/build/928047/log/raw. Mathieu

Re: core-updates-frozen: Planning for the last world rebuild

Hey, > For example, this evaluation from Sep 17 has thousands of scheduled > evaluations: > > https://ci.guix.gnu.org/eval/19271?status=pending Mmmh, not nice. Any chance you could share the cuirass-remote-worker logs on the guixp9 machine? Thanks, Mathieu

Re: core-updates-frozen: Planning for the last world rebuild

Hey Thiago, > I was waiting for this world rebuild to happen to see the results in > Cuirass now that powerpc64le-linux builds are only done on guixp9, but in > hindsight it would have been better if I requested that those builds were > restarted instead. Restarting this build should remove

Re: core-updates-frozen: Planning for the last world rebuild

Hey! > have more system tests passing. Currently 16 out of 87 are > broken. Except for the nfs-root-fs that has always been broken, the > other tests probably cover user configurations out there. Made some progress here but there are still a bit more work needed: * childhurd

Re: core-updates-frozen: Planning for the last world rebuild

Hey! > Wouldn’t it be nice to get ‘core-updates-frozen’ merged? :-) That would be great :) Before merging to master, it would be nice to have more system tests passing. Currently 16 out of 87 are broken. Except for the nfs-root-fs that has always been broken, the other tests probably cover

Re: branch core-updates-frozen updated: services: database: Change postgresql default socket.

Hello, > The manual should also be updated to reflect this change. Fixed, thanks for the reminder. > Also, is there any reason for making this change on > ‘core-updates-frozen’ rather than ‘master’? Yes, that's a follow-up of 86cf4c039631cdf15c4c428bf4ffe52d6cbd7d4c that was pushed on

Re: OBS substitutes

Hello Chris, > On Guix Systems, if the substitute keys are left as the default, for > recent revisions of Guix, the bordeaux.guix.gnu.org signing key will be > included in the ACL by default. With Guix on foreign distributions, it > needs adding manually. > > I think there's some room for

Re: OBS substitutes

Hello zimoun, > well, I do not understand why it is not on Berlin. But why not. Then, Looks like Cuirass built it the 15th of September: https://ci.guix.gnu.org/build/785837/details. When did you experienced this issue? What was your guix revision? > Why? How is it possible that “guix

Re: core-updates weather reports!

> Oh, nice! Did increasing the nginx timeouts help? Yes, it definitely helped, but there are still some request timeouts. I hope that the publish patches we are discussing here[1] can fix this situation. Thanks, Mathieu [1]: https://issues.guix.gnu.org/50040

Re: Distributing Guix System Pinebook Pro images

Hello Vagrant, > I wonder how much diskspace savings you might get by leaving out the > display manager... I typically just login from the console and run "exec > sway". I *think* the last image I generated for that was more like 2GB, > though my memory is fallable, and maybe misses various

Distributing Guix System Pinebook Pro images

Hello, The Guix website now offers Pinebook Pro Guix System images[1]. Those images can be directly copied on a micro-SD card and booted from. More details here[2]. Thanks, Mathieu [1]: https://guix.gnu.org/en/download/latest/ [2]:

Re: core-updates weather reports!

Hello, The situation is getting better here: --8<---cut here---start->8--- https://ci.guix.gnu.org 81.1% substitutes available (16,148 out of 19,921) at least 112,494.5 MiB of nars (compressed) 17,592,186,161,392.5 MiB on disk (uncompressed) 0.006

Re: core-updates weather reports!

Hey, > Okay, are you confident in the #50040 patch? It looks like there are a > lot of spurious failures from #48468. I just discovered that many spurious failures were also caused by short Nginx timeout values. Added a comment about that on #50040. I'm also currently experimenting directly on

Re: core-updates weather reports!

Hello Leo, > As far as I can tell, the build farms are not actually trying to build > for core-updates-frozen, at least not in a systematic way. Am I > mistaken? Or are we only building the core subset of packages for this > branch? Thanks for the reports! Cuirass is actually trying to build

Re: Hundreds of failed build on master following git package update

Hello Brice & Sarah, > That sounds awfully familiar. I wonder if this is related to the > following issue? Yes, this is indeed completely related to the pointed issue. I'd like to proceed with the patch soon so that Cuirass can recover a working state. However, as this is a rather delicate

Re: branch master updated: services: cuirass: Add a no-publish argument.

Hey, > So I’d suggest turning that into ‘publish?’, defaulting to #t. Yeah, you're completely right, I reversed the logic with: cfd2442488971420289a12d5ca8f07816e1149bf. Thanks, Mathieu

Re: Substitute timeouts

Hey Ludo, Thanks for taking the time to read my wall of text :D. > Yeah, it’s a double-edged sword. If this is a problem on the main ‘guix > publish’ server, we can lower the bypass threshold, which is currently > 50 MiB: > > >

Re: Project direction with testing changes (branches and patches)

Hello Chris, > I think trying to change up how branches (staging/core-updates) are > tested is a good place to start. The concrete change I'm proposing is to > use an instance of the Guix Data Service plus an instance of the Guix > Build Coordinator to do the testing and builds, rather than

Substitute timeouts

Hello, I have been investigating a problem that is visible both on the main guix publish server at https://ci.guix.gnu.org[1] and on the Cuirass build farm[2]. This error comes from the fact that the publish server does not accept the "guix substitute" connection requests within the

Core updates frozen.

Hello, A new core-updates-frozen branch is available here: https://git.savannah.gnu.org/cgit/guix.git/log/?h=core-updates-frozen. This means that the core-updates branch remains open, while the core-updates-frozen branch will only accept bug fixes. This branch contains exciting new features,

Re: branch master updated: ci: Add bootstrap packages to the core subset.

Hey Ludo! > Should we arrange so that jobs for the commencement.scm packages get a > custom name, for example prefixed by “commencement.”? The primary key for the Builds table is on the derivation field, so duplicated job-name shouldn't be an issue. If you search for

Re: Zile and minimal systems

Hey, > I suppose this line could be removed now. Pushed, thanks for having a look. Mathieu

Re: Zile and minimal systems

Hey, > ‘zile-on-guile’ is tempting but currently unmaintained. ‘mg’ could work too. mg seems to work fine. I'm currently testing the attached patch. Any objections? Thanks, Mathieu >From 0cff5b30711a8987bc0457c23a73982888ec802e Mon Sep 17 00:00:00 2001 From: Mathieu Othacehe Date:

Re: Wrap %default-guix-channel inside channel-with-substitutes-available by default?

Hello, > I think we do have the obligation to clearly document channels-with- > substitutes-available and make it so that this particular piece of > documentation can easily be found by everyone who is potentially > affected by slow-downs. Perhaps we might even want to include an > option in

Cuirass 1.1 released

We are pleased to announce the release of Cuirass 1.1. This is the second official release of Cuirass, the GNU Guix continuous integration software. For the last six months, this project has been funded through the NGI0 PET Fund, a fund established by NLNet[1]. Thanks to this support, Cuirass

Re: Cuirass badges

Hey Ludo, > This is not yet deployed in the current ‘cuirass’ package, right? Yes it is :) For instance, to get the badge of the guix-hpc specification at https://guix.bordeaux.inria.fr, you can use the following URL: https://guix.bordeaux.inria.fr/jobset/guix-hpc/badge.svg. There are some

Re: Ungrafting CI jobs

Hey Leo, > Okay. Can you let me know when you do? I'll delay the ungrafting builds > until then. I deployed the upgrade yesterday. I've been monitoring it for 12 hours without any sign of substitutes timeout. I think you can proceed whenever you want. Thanks, Mathieu

Re: Ungrafting CI jobs

Hello Leo, I monitored a previous evaluation of the ungrafting Cuirass specification that was more successful, with more than 17000 builds performed in less than 24 hours, a new record! The recent evaluation is sadly less victorious. > The latest iteration failed en masse due to network

Re: Adding Substitute Mirrors page to installer

Hello, Sorry again for the long delay. > Of course, it feels somewhat dirty, as there is a need to read the > configuration file. > It would be cleaner if a page could affect the field created by a previous > page. Yes I agree. In the meantime, I think that the configuration file read is an

Re: linux-libre source tarballs

Hello, >> Not knowing exactly how ci.guix.gnu.org works, would it make sense to >> create a tarball package instead of the ... computed origin(?) tarball, >> so it could be better represented in the package dependency graph, and >> the various linux-libre-* packages can wait till it is

Re: Cuirass badges

Hey Luis, > And the source file: > > https://luis-felipe.gitlab.io/media/2021/05/cuirass-badges-proposal-2021-05-28.svg > > I think I like d and d*. Wooh, that's great! I updated Cuirass to use the d badge proposal. Many thanks for your help, Mathieu

Cuirass badges

Hello, Cuirass is now able to generate badges like any respectable CI system. For instance: * https://ci.guix.gnu.org/jobset/master/badge generates a badge showing the percentage of successful jobs for the master specification. * https://ci.guix.gnu.org/jobset/guix/badge generates a badge

Re: Bringing substitutes from the Guix Build Coordinator to users

Hey Chris, > That sounds sensible. On the specific name, given this is just about > substitutes, and at least in my opinion has nothing to do with > continuous integration, maybe picking just another word would avoid > thinking too much, it could be bordeaux, or hippo, or anything > really. As

Re: branch master updated: gnu: Add emacs-wucuo.

Hello Chris, > The n on this line means that this package can't be built, and also > breaks the linter. > > I've removed the n in fd2abc2a51e2cc39ac67dcef1d21a8037147e798. It also broke Cuirass master evaluation. Thanks for fixing it, Mathieu

Cuirass accessibility

Hello, As part of the Cuirass NLNet grant[1], the website at https://ci.guix.gnu.org has been audited by the Accessibility Foundation[2]. I have made the report public here[3]. Although I have already applied a bunch of accessibility related fixes, there's still some work left. The report if

Re: GNU Guix 1.3.0 released

Hey, >> This release corresponds to 8,300 commits over almost 6 months by 212 >> people. Support for the POWER9 platform is now offered as technological >> preview. This release adds new features, refines the user experience >> and improves performance. It also includes many new packages and

Re: New blog post on the Guix Build Coordinator: Building derivations, how complicated can it be?

Hello, > On Sat, Apr 24, 2021 at 11:10 AM Christopher Baines wrote: >> I did think about trying to include something about Cuirass, but I don't >> have a clear picture of it's scope or purpose, so I'm not really the >> right person to attempt to write authoritatively about it. > > OK, fair

Re: wip-ungrafting builds stuck

Hello, > Any idea what could be wrong, Mathieu? What would you suggest to do > when investigating such issues? Yes I noticed it. The main problem here is that almost all workers are stuck building Rust. I see two actions here: 1. Understand why Rust is taking so long to build. 2. Implement

Re: wip-ungrafting builds stuck

Hello, > Any idea what could be wrong, Mathieu? What would you suggest to do > when investigating such issues? Yes I noticed it. The main problem here is that almost all workers are stuck building Rust. I see two possible actions here. 1. Understand why Rust is taking so long to build. 2.

Re: Following Guix weather.

Hello Vincent, Thanks for your feedback! > The column sorting icon is overlapped with the columns title Oh, didn't notice it on my large screen! > The jobs column: > * is there really a need for decimals for the %age, an integer would > be good enough ? (no more ".00%" nor "100.00%")

Following Guix weather.

Hello, I have deployed a bunch of changes at https://ci.guix.gnu.org/. I'd like to introduce some of them here. First, there are some new specifications: "images", "tarball" and "tests". Those specifications are configured to build respectively, the %guix-system-images declared in (gnu ci),

Re: branch master updated: hydra: berlin: Accept new languages.

Hello Julien, > * hydra/nginx/berlin.scm (%extra-content): Autoredirect 'eo', 'ko' and > 'ru' > to the translated website. I had to revert this one that causes the following nginx error: 2021/04/07 17:05:08 [emerg] 94058#0: variable already defined: "lang" in

Re: Finding the channel in which a package is defined

Hello Konrad, > Is there a simple way to find out in which channel a given package was > defined? I tried "guix edit" to see the source code, but it shows a file > from a "module-union" directory in the store. You can run something like: --8<---cut

Re: Adding Substitute Mirrors page to installer

Hello, Thanks for this patch, it seems to work fine! > + ;; Extract the substitute URLs of the user configuration. > + (os (read-operating-system > (%installer-configuration-file))) > + (substitute-urls (and=> (find > +

Cuirass 1.0 released

Mathieu Lirzin 296 Mathieu Othacehe 36 Ricardo Wurmus 1 Robert Vollmert 1 Roel Janssen 6 TSholokhova 1 Tobias Geerinckx-Rice 1 Vincent Legoll Mathieu [1]: https://nlnet.nl/ [2]: https://ci.guix.gnu.org smime.p7s Description: S/MIME cryptographic signature

Re: armhf-linux substitutes

Hello, > Mathieu, what’s preventing us from doing armhf-linux builds again? We > could use the OverDrives for that (with an upper bound though), along > with the SBCs in machines-for-berlin.scm. > > That won’t be enough to keep up, so perhaps we’ll have to restrict > armhf-linux builds to the

Re: Adding Substitute Mirrors page to installer

Hello, I plan to have a look to your patch in the next coming days. Sorry for the long delay. Thanks, Mathieu

Re: Cuirass not processing core-updates (or weirdly)

Hello Leo, > If you look at https://ci.guix.gnu.org/eval/13652 you can see that the > evaluation of the derivation seems completed but there's no pending > builds. If you have a look to https://ci.guix.gnu.org/specification/edit/core-updates you will see that this specification is configured

Re: cuirass

Hello, > * The "Home" & "Guix logo" buttons bothlink back to the home page (duplicate). Yes, but I'm not sure what to do about that. Maybe remove the logo link. > > * The search combobox help popup window > is not on top level, probably on all pages. > So other page elements are displayed

Re: [opinion] CVE-patching is not sufficient for package security patching

Hello, > Concretely, this would mean a Honeycomb LX2 or Ampere ALTRA workstation, > since I don't believe there are any other aarch64 workstations available > for sale. > > https://www.solid-run.com/arm-servers-networking-platforms/honeycomb-workstation/ >

Re: 01/09: gnu: Add python-sphobjinv.

Hello, > + (patches (search-patches "python-sphobjinv-system-ca.patch" Looks like this patch is missing, causing an evaluation failure. Thanks, Mathieu

Re: 01/09: gnu: Add python-sphobjinv.

Hello, > + (patches (search-patches "python-sphobjinv-system-ca.patch" Looks like this patch is missing, causing an evaluation failure. Thanks, Mathieu

Re: 04/07: inferior: Break cached-channel-instance into two procedures.

Hey, > We need to keep ‘cached-channel-instance’ because it’s part of the > public API and used outside Guix (in Guix-Jupyter at least). We can use > ‘define-deprecated’. > > Also, I think ‘cached-profile’ doesn’t quite capture what this is > about. :-) The docstring should mention what

Re: 05/07: inferior: Fix concurrent cached-profile calls.

Hey Ludo, > However, there’s already a (file-exists? cached) call a few lines > above. So what you need instead is a TOCTTOU-free ‘symlink’, along > these lines: > > (define (symlink/safe old new) > (catch 'system-error > (lambda () > (symlink old new)) > (lambda args

Re: [Cuirass] Hanging(?) restarted build with negative Duration

Hello Tobias, > I restarted almost exactly 24h > ago, and it's still in the ‘Started’ state. Is it stuck? Maybe I'm just > overestimating our newly coordinated build farm. The build timestamps were not reset on build restart. This is fixed with:

  1   2   3   4   5   >