Re: New mumi www and mumi compose subcommands

Hi Ludo, Ludovic Courtès writes: > Won’t work with Gnus, but nice still. ;-) You should be able to customize `url-mail-command`, see "(url) mailto". Best, -- Josselin Poiret signature.asc Description: PGP signature

Re: Guix pull: avoiding "Computing Guix derivation"

ain the terrible performance of `guix pull`. [1] mid:87wmxe3vsa@jpoiret.xyz https://yhetil.org/guix/87wmxe3vsa@jpoiret.xyz/ Best, -- Josselin Poiret signature.asc Description: PGP signature

Re: Core updates status

n commencement because we have them already available at that point. The own downside of this is that the patch name will not include the fixed CVEs, so guix lint won't be aware that the CVEs have been patched. [1] https://salsa.debian.org/glibc-team/glibc/-/blob/sid/debian/patches/git-updates.diff WDYT? Best, -- Josselin Poiret signature.asc Description: PGP signature

Re: Core updates status

Hi Maxim, Maxim Cournoyer writes: > Hi Josselin, > > Josselin Poiret writes: > > [...] > >> However, as you can see, these are non-local failures: build failures >> have to be fixed in a dependency, which incurs a lot of rebuilding. >> I've fixed a c

Re: Core updates status

more. I'd vote to keep the pkgconf switch for later and focus on merging the rest of what c-u has to offer. WDYT? -- Josselin Poiret signature.asc Description: PGP signature

Re: Status of ‘core-updates’

locale errors that I fixed with ae07bc2dd0124b625acf70e594ccc90d6d128562, so I'm not expecting too much trouble. We'll probably have to add libxcrypt as an input to some other packages that I haven't tested yet, but that's quite trivial. Best, -- Josselin Poiret signature.asc Description: PGP signature

Re: Contribute or create a channel?

o channels pick different commits for a channel dependency *cannot* be made to work, at least using Guile. I think what would currently happen is that either: 1) Guix refuses to build (unlikely); 2) Guix just chooses one commit that it then uses to build all dependent channels, contrary to the r

Re: G-exps: thunk instead of top-level references?

dateutil > > and uses > > -(native-inputs (%standard-trytond-native-inputs)) > +(native-inputs > + (cons* trytond-account-payment-clearing > +%standard-trytond-native-inputs)) > Yes it still needs to be a thunk for the same reason: no top-level references to packages in other modules. By the way, (list ...) is not a G-exp, it's rather the new input style. Best, -- Josselin Poiret signature.asc Description: PGP signature

Re: [PATCH 2/2] gnu: grub: Modernize.

Hi Fabio, Fabio Natali writes: > On 2024-03-03, 17:42 +0100, Josselin Poiret wrote: >> From: Josselin Poiret >> >> * gnu/packages/bootloaders.scm (grub-minimal, grub-coreboot, grub-efi32, >> grub-hybrid): Use G-Exps. >> (grub-efi): Use G-Exps. Also

Re: on the bug tracker (Re: Guix Days: Patch flow discussion)

-- Giovanni Biscuolo writes: > Hi Josselin, > > Josselin Poiret writes: > > [...] > >> One thing I would like to get rid of though is debbugs. > > given that a significant part of the Guix infrastructure is provided by > the GNU project, including the bug

Re: Bugs and Patches---or rather, bugs or patches?

ey're on two different lists, right? I don't like the separation between both MLs, sure, but that's it. What would be the pros/cons of such a merge? Best, -- Josselin Poiret signature.asc Description: PGP signature

[PATCH 2/2] gnu: grub: Modernize.

From: Josselin Poiret * gnu/packages/bootloaders.scm (grub-minimal, grub-coreboot, grub-efi32, grub-hybrid): Use G-Exps. (grub-efi): Use G-Exps. Also use OVMF to test. Change-Id: Ic9c73753004739d6027b8426eb46c114a6a31051 --- gnu/packages/bootloaders.scm | 286

[PATCH 1/2] gnu: grub: Update to 2.12.

From: Josselin Poiret * gnu/packages/bootloaders.scm (grub): Update to 2.12. Change-Id: I5d9ae3952b61b47418cb571fc0bcb5318e72 --- gnu/packages/bootloaders.scm | 182 --- 1 file changed, 102 insertions(+), 80 deletions(-) diff --git a/gnu/packages

Re: LUKS2 support in Guix

d simply upgrade to Grub 2.12, which would solve the issue as it supports LUKS2 properly. I have a patch locally upgrading Grub, but it's not in upstreaming shape yet and I haven't had much time to work on it recently. I am running it though, and it's working quite well. Would

Re: Feedback of the GNU Guix manual

nstalling them via their own package manager. Keeping the mention that it is self-contained and that the dependencies are also included might clarify the situation for some users. Best, -- Josselin Poiret signature.asc Description: PGP signature

Re: Core-updates coordination and plans

t ...) in g-exps? I don't really know what the answer to those questions should be, but it probably involves a world rebuild :(. Anyone have an idea/opinion about this conundrum? Other than that, I think that branch is in a pretty ok shape, I've also included a couple of patches that were

Re: Guix Days: Patch flow discussion

quite fast. Best, -- Josselin Poiret signature.asc Description: PGP signature

Re: Guix Days: Patch flow discussion

Hi Felix, Felix Lechner writes: > Hi Josselin, > > On Tue, Feb 13 2024, Josselin Poiret wrote: > >> As long as Debbugs is modifying mails on the MLs it's being >> troublesome. > > Will you please show an example? You mentioned it before but I cannot &g

Re: Keyboard layout in GRUB (Was: On the road to the next release: testing the installer)

hinking about. It's not conceptually hard but kind of annoying to do. Same for the at_keyboard module, although I'm wondering how the current situation works for you then. Best, -- Josselin Poiret signature.asc Description: PGP signature

Re: Guix Days: Patch flow discussion

Hi Felix, Felix Lechner writes: > Hi Josselin, > > On Mon, Feb 12 2024, Josselin Poiret wrote: > >> 1) Doesn't modify any incoming mail; > > What if, in addition, Debbugs were to publish bug reports and their > comments via public-inbox? Why “in addition

Re: Guix Days: Patch flow discussion

ould still not solve 1 and 2 perfectly. Best, -- Josselin Poiret signature.asc Description: PGP signature

Re: Keyboard layout in GRUB (Was: On the road to the next release: testing the installer)

be found. I believe we don't use grub-mkimage directly for the efi case for now, which is the command we want to use to be able to include arbitrary files in the image, hence my comment about the code needing some refactoring. Best, -- Josselin Poiret signature.asc Description: PGP signature

Re: On the road to the next release: testing the installer

Hi Romain, Romain writes: > Hi, > > On February 10, 2024 11:35:56 AM GMT+01:00, Josselin Poiret > wrote: >>We don't try to embed the required keymap in the GRUB image and load it >>early on. It shouldn't be too hard, but would require a bit of >>refac

Re: On the road to the next release: testing the installer

n/user/1000` was not even present. This is usually a symptom of elogind's PAM module not running/working. Did you use %desktop-services as a base for services? Best, -- Josselin Poiret signature.asc Description: PGP signature

Re: Guix Days: Patch flow discussion

Hi again Sunhail, Josselin Poiret writes: > Hi Sunhail, > >> Josselin Poiret writes: >> >>> One thing I would like to get rid of though is debbugs. It causes a >>> lot of pain for everyone, eg. when sending patchsets, it completely >>> breaks moder

Re: Guix Days: Patch flow discussion

Hi Sunhail, > Josselin Poiret writes: > >> One thing I would like to get rid of though is debbugs. It causes a >> lot of pain for everyone, eg. when sending patchsets, it completely >> breaks modern email because it insists on rewriting DMARC-protected >> headers

Re: Guix Days: Patch flow discussion

, breaking the reply chain). Could you please fix this? This is quite on-topic in a discussion about the mail-based workflow :) [1] https://datatracker.ietf.org/doc/html/rfc2822#section-3.6.4 Best, -- Josselin Poiret signature.asc Description: PGP signature

Re: Guix Days: Patch flow discussion

#x27;s bigger user-base and dev time, and also from the fact that these tools are made to work together (b4 can automatically mark patchsets as accepted)! Best, -- Josselin Poiret signature.asc Description: PGP signature

Re: guix installation why internet connection required?

nt-guix` hack that basically uses a guix checkout at the current guix version as the source for the guix package. In both cases though, we shouldn't see any differences in other package's derivations… Best, -- Josselin Poiret signature.asc Description: PGP signature

Core-updates coordination and plans

hat it's too late to introduce more complications and delay the update any longer. Best, -- Josselin Poiret signature.asc Description: PGP signature

Re: An update on ‘core-updates’

tional patches I'll try to send soon. I'd be happy leading the effort and merging the branch. Best, -- Josselin Poiret signature.asc Description: PGP signature

Re: problems installing on LUKS2 encrypted device

nd I'll look into updating it in Guix soon. Best, -- Josselin Poiret signature.asc Description: PGP signature

Re: Heisenbug

y error? Thanks! Usually, these Heisenbugs come from the lack of dependency tracking in Guile: module dependencies have changed but their dependents weren't rebuilt. I would usually suggest `make clean-go` then `make`, and if the error happens again then you most likely are in front of the “actual” error. Best, -- Josselin Poiret signature.asc Description: PGP signature

Re: Meet Guix at Capitole du Libre in Toulouse, nov. 18-19

is in? Do not be shy and drop > an email; off-list possibly. I will be there! When will you arrive in Toulouse? Best, -- Josselin Poiret signature.asc Description: PGP signature

Re: [RFC]: Skipping rust crate tests by default

ever, this would require refactoring *all* guix package definitions, after first coming up with a satisfying testing strategy and system. I don't think this will ever happen unfortunately. Best, -- Josselin Poiret signature.asc Description: PGP signature

Re: IDEA: missing-tests-pypi-error? condition

Hi jgart, > Is there a way to open the guix manual directly? > > Not sure why info opens a "main page" with all my texinfo manuals when > I give it doc/guix.info as an argument... 🦆 You want `info -f doc/guix.info`. HTH, -- Josselin Poiret signature.asc Description: PGP signature

Re: Implementing the guix-dameon in Guile

nform the direction to take. I think the #1 feature for me would be to have it completely unpriviledged using mount namespaces, so that you could still build software without needing to run the daemon on the system. You won't be able to run the built software without using namespaces as well though, but that still a step in the right direction imo. WDYT? -- Josselin Poiret signature.asc Description: PGP signature

Re: hard dependency on Git? (was bug#65866: [PATCH 0/8] Add built-in builder for Git checkouts)

m that we want to do everything in Scheme, but we're unable to do it as well as Git itself. If I had to choose, a Guile library wrapping the Git commands would be the best, especially since we're managing long-living checkouts, something libgit2 doen't seem too interested in. Be

Re: Building from git

committers, > then > this is completely fine. But the documentation does not currently read that > way. Yes, I believe this should then be clarified. Best, -- Josselin Poiret signature.asc Description: PGP signature

Re: Building from git

to do the authentication. `make authenticate` is here for committers to check that their commits are all properly signed before pushing (it's used as a pre-push hook). Best, -- Josselin Poiret signature.asc Description: PGP signature

Re: Guix pull speed

pull” is slow, no? It's the same process, but in one case it's done with an already compiled tree, so loading the files is instantaneous, but on `guix pull` the tree is not compiled yet (that's the whole point of `guix pull`!) and so loading these 300+ guile files is extremely

Re: Guix pull speed

Hi Simon, Simon Tournier writes: > Hi Josselin, > > On Tue, 29 Aug 2023 at 13:58, Josselin Poiret wrote: > >> After looking a bit more into guix pull speed, or to be more precise the >> "Computing Guix derivation..." step, which is not substitutable. I

Re: How can we decrease the cognitive overhead for contributors?

with a knife is inherently better because more people have knives compared to lawnmowers. Regarding the “mom argument”, I would disagree and say that this is completely related: interruptions are more costly, you're more likely to have less attention span, and overall you probably don't

Re: 03/08: build: Add dependency on guix script for help2man targets.

run `guix home --help` and see what the error is, if it's an ABI error I usually run `grep -Rl "" --include '*.go' . | xargs rm`. Best, -- Josselin Poiret signature.asc Description: PGP signature

Guix pull speed

he dependencies and then add them in later, similar to what is done with build-aux/build-self.scm to be able to load (guix self) in the first place. That seems quite complex though. Best, -- Josselin Poiret signature.asc Description: PGP signature

Re: How can we decrease the cognitive overhead for contributors?

owse because of all the formatting that you have available, and the hyperlinks. I've also not had any issues adding stuff to the manual while not knowing anything about the format, just mimicking stuff found nearby. YMMV though, depending on what changes you might want to make. Best, -- Jos

Re: How can we decrease the cognitive overhead for contributors?

s, but I feel like they're a bit orthogonal to the requirements that the ChangeLog format imposes on us. With the git tools we have, I'm not sure the ChangeLog format is really needed, it dates back to an era where they didn't exist. Best, -- Josselin Poiret signature.asc Description: PGP signature

Re: Updates for Go

'd need to also export a "default" version of each package for those two to work properly. Also, while having pinned versions of dependencies upstream seems like the consensus, I'm not sure we'd like doing that, be it for the exponential CI work that would be required.

Re: [bug#62047] [PATCH 0/2] '--with-input' & co. no longer replace hidden packages

e you're doing this in Guile? If so, package-input-rewriting doesn't have that same behavior, and still replaces hidden packages! HTH, -- Josselin Poiret signature.asc Description: PGP signature

Re: Rebasing or merging? [was: Re: 01/03: gnu: wxwidgets: Add libxtst to inputs.]

its with more than one parent. This is > exactly the same as --max-parents=1. > > Thanks for finding that option. I used these kinds of options for the last core-updates merge, and this one only hides the merge commits themselves, not the merged commits. For that, you need to

Re: Ideas for ocaml-team

Guix, but will try to help if I can (time- and > competence-wise) ! :) I can also give a hand regarding Coq and libraries, since I have a vested interest in having everything up-to-date :) Best, -- Josselin Poiret signature.asc Description: PGP signature

Re: 02/03: gnu: openblas: Update architectures we provide substitutes for.

or this behavior. Best, -- Josselin Poiret signature.asc Description: PGP signature

Re: qtbase 6.3.2 FTBFS

unless it's something like OOM). Best, -- Josselin Poiret signature.asc Description: PGP signature

Re: qtbase 6.3.2 FTBFS

Hi Felix, Does this happen on master? Best, -- Josselin Poiret signature.asc Description: PGP signature

Re: Should commit signing always be required for local work? [was Re: bug#63261: Recent changes to git config cause errors for non-committers]

in general (not Guix because we have a pre-push hook), how do you make sure you always publish signed commits? I don't want to put unsigned commits anywhere except locally, but it feels like I might just forget to sign them before pushing. Best, -- Josselin Poiret signature.asc Description: PGP signature

Re: What's needed to get things building for i586-gnu (the hurd) post core-updates?

based on the architecture. Unfortunately, it is used in an origin snippet, and there you can't really case over the target system. Best, -- Josselin Poiret signature.asc Description: PGP signature

Re: What's needed to get things building for i586-gnu (the hurd) post core-updates?

ter on that could be removed with pure Guile. That would be a world rebuild though so let's leave that for later. - m4 and findutils both have some failing tests, and they seem to be crashing. I haven't investigated this yet. [1] https://issues.guix.gnu.org/63501 -- Josselin Poiret signature.asc Description: PGP signature

Small presentation from a new committer

y I'm also a mathematician working on type theory, proof assistants, logic and higher categories, and I happen to use Guix to work on Agda, although it hasn't caught on quite yet :) [1] https://jpoiret.xyz/jpoiret.pub See you soon, -- Josselin Poiret jpoiret.pub Description: My PGP

Re: Tooling for branch workflows

be running there for the foreseeable future? Best, -- Josselin Poiret signature.asc Description: PGP signature

Re: evince: Is this a bug?

s choice of packages. Best, -- Josselin Poiret signature.asc Description: PGP signature

Re: bug#63267: gcc-toolchain is missing libstdc++.so

"-F" was > added to "guix shell"). Small note: `ldd` is only a wrapper around setting `LD_TRACE_LOADED_OBJECTS=1`, so you don't really need to pull in all of glibc just for this. There's also LD_DEBUG with possible values explained by LD_DEBUG=help, which I u

Re: What's needed to get things building for i586-gnu (the hurd) post core-updates?

compilation as above :( Best, -- Josselin Poiret signature.asc Description: PGP signature

Re: Help! Having troubles testing my generalization of home-redshift-service

x27;m missing something essential here. > > Any ideas? The Guix that is included inside the `guix vm` corresponds to the guix package definition in guix, not the current guix checkout you're using! You could try to modify the guix-service-type's configuration to use (current-

Re: proot-static build failures (master and core-updates)

he failing test it looks like an actual regression. Best, -- Josselin Poiret signature.asc Description: PGP signature

Re: [Rust Team] Status post core-updates merge

st getting further and further down into the dependency chain, this is vital work, and you all seem to be handling it very well. I'm also curious, since you're "early adopters": how are you managing with the team workflow? Any tips, remarks or impressions that you could share with other teams? Best, --- Josselin Poiret signature.asc Description: PGP signature

Re: `mumi send-email' means no more debbugs dance to send multiple patches

tried twice now, with the same issue both times, with [1] and [2]. [1] mid:cover.1682364024.git@jpoiret.xyz https://yhetil.org/guix/cover.1682364024.git@jpoiret.xyz/ [2] mid:cover.1682452738.git@jpoiret.xyz https://yhetil.org/guix/cover.1682452738.git@jpoiret.

Re: `mumi send-email' means no more debbugs dance to send multiple patches

don't remember how long it took yesterday for the issue to appear on mumi though, but more than the 15 retries of mumi send-email (I manually checked). > Thanks for the feedback, and happy hacking! :-) Thanks for your tool! Best, -- Josselin Poiret signature.asc Description: PGP signature

Re: Setuid handling?

e that, but if you do anything else with env variables it might get shadowed. I am not too sure of how guix home deals with this, you might have to dig deeper there. Best, -- Josselin Poiret signature.asc Description: PGP signature

Re: Core-updates merge

ber how far in the future it is), so we could maybe try to create a calendar for it, and set team goals accordingly? Best, -- Josselin Poiret signature.asc Description: PGP signature

Re: Setuid handling?

xpect this to fail > root's password: > > $ mailq > mailq: need root privileges > > Has the handling for such executables changed? What is `command -v su`, and `ls /run/setuid-programs/`? Have you rebooted since reconfiguring? Best, -- Josselin Poiret signature.asc Description: PGP signature

Re: `mumi send-email' means no more debbugs dance to send multiple patches

n't receive the mail in time and it just timed out sending the replies :( is there anything that could be done on that front? Does mumi use IMAP IDLE? Best, -- Josselin Poiret signature.asc Description: PGP signature

[PATCH] gnu: python-shiboken-2: Do not rely on _Py_Mangle being available.

* gnu/packages/patches/python-shiboken-2-compat.patch: Fix the patch according to upstream. --- .../patches/python-shiboken-2-compat.patch| 29 +-- 1 file changed, 14 insertions(+), 15 deletions(-) diff --git a/gnu/packages/patches/python-shiboken-2-compat.patch b/gnu/package

Re: Core-updates, the last metres

still getting a build error that boils down to the following: --8<---cut here---start->8--- import importlib importlib.machinery --8<---cut here---end--->8--- errors out with python-minimal@3.10, but not with python@3.10!

Re: PSA for LUKS users

but > apparently this is not realistic: As for LUKS2 support in Grub, as long as you use PBKDF2 it should now be supported by HEAD. Best, -- Josselin Poiret signature.asc Description: PGP signature

[PATCH core-updates] gnu: python-pytest: Fix failing test_raising_repr.

* gnu/packages/patches/pytest-fix-unstrable-exception-test.patch: Add new patch from upstream. * gnu/packages/check.scm (python-pytest): Use it. * gnu/local.mk (dist_patch_DATA): Register it. --- Hey Andreas and Kaelyn, This should also fix it without bumping python-pytest to a new version (since

Re: A Joyous Core-Updates Week-End 🎉

ependencies that impact multiple packages could be reviewed on the spot while leaf packages could wait until later. Best, -- Josselin Poiret signature.asc Description: PGP signature

Re: staging merge into master

n on core-updates before this week-end. I don't have a particularly strong opinion either way, but if you do merge it, could you make sure to also merge master into c-u and launch a CI evaluation right afterwards? Thanks for taking care of staging! Best, -- Josselin Poiret signature.asc Description: PGP signature

Re: rrdtool hash mismatch

try to download it from upstream, Guix rightfully complains that the hash has changed and refuses to go forward! Best, -- Josselin Poiret signature.asc Description: PGP signature

Re: i686 core-updates failure.

n't need to download all of that part of the dependency chain. Best, -- Josselin Poiret signature.asc Description: PGP signature

[PATCH] WIP upgrade qt 6 to 6.5.0

--- gnu/packages/qt.scm | 32 ++-- 1 file changed, 18 insertions(+), 14 deletions(-) diff --git a/gnu/packages/qt.scm b/gnu/packages/qt.scm index acf2d70736..46fbdb2368 100644 --- a/gnu/packages/qt.scm +++ b/gnu/packages/qt.scm @@ -68,6 +68,7 @@ (define-module (gnu pac

Re: [core-updates] qtbase 6 ssl tests fail.

atch I have for now. Best, -- Josselin Poiret signature.asc Description: PGP signature

A Joyous Core-Updates Week-End 🎉

fer them your assistance! Feel free to reply to this if you have any questions about the process, or with your attempts, struggles and successes! See you this week-end. [1] https://gitlab.com/pjotrp/guix-days-fosdem-2023/-/blob/main/releases-branches.txt Best, -- Josselin Poiret signature.asc Description: PGP signature

Re: [core-updates] qtbase 6 ssl tests fail.

Hi again Ricardo, I just saw that you disabled these tests with 03580b5f1d997df066a5119cf0a242f827354ba8, by saying that not all key types are supported by our build of OpenSSL. Wouldn't this be an issue on our part, especially if Qt expects these to be available? Best, -- Josselin P

Re: [core-updates] qtbase 6 ssl tests fail.

st abandoned the idea of doing it myself. I might revisit it by just building in a `guix shell -C` instead. Best, -- Josselin Poiret signature.asc Description: PGP signature

Re: Building more of ‘core-updates’ on ci.guix

evel, as long as we have enough helping hands for the fateful day(s). If so, would next week-end (15-16 april) work? Best, -- Josselin Poiret signature.asc Description: PGP signature

Re: gstreamer 2.22, webkitgtk 2.40.0, qt 5.15.8 and ffmpeg 6 on staging

is also available from bordeaux. Best, -- Josselin Poiret signature.asc Description: PGP signature

Re: Time travel accident

ch afaik cannot be transformed. By the way, we can also "fix the past" by using guix/quirks.scm. Since that version of openssl doesn't build anymore, I wonder if we could just change its derivation retroactively to at least make it build. Best, -- Josselin Poiret signature.asc Description: PGP signature

Re: [core-updates] It would be nice to fix libsndfile CVE-2021-3246 (arbitrary code execution via crafted WAV file)

t; defective version [3] while NIST scored the vulnerability as "8.8 > HIGH" [4] although we seem to have company. > > Kind regards > Felix Lechner > > [3] https://repology.org/project/libsndfile/versions > [4] https://nvd.nist.gov/vuln/detail/CVE-2021-3246 Maybe we could graft it on master, and ungraft it after core-updates has been merged? Best, -- Josselin Poiret signature.asc Description: PGP signature

Re: Syntax and gexp for ff5f34ae757d709987896d6164bf125319a0f764

Hi Leo and Andreas, Leo Famulari writes: > On Thu, Mar 30, 2023 at 08:49:43PM +0200, Josselin Poiret wrote: >> Usually errors which involve # somewhere are caused >> by stale .go files (guile doesn't know how to recompile dependent .scm >> files). I would suggest a go

Re: Syntax and gexp for ff5f34ae757d709987896d6164bf125319a0f764

Hence, in dependent .go files, the variable didn't get expanded, and is then used at runtime, hence the error. Best, -- Josselin Poiret signature.asc Description: PGP signature

Re: Syntax and gexp for ff5f34ae757d709987896d6164bf125319a0f764

ckages/gd.scm:103:2: package `perl-gd@2.73' has an > invalid input: ("_" #) Usually errors which involve # somewhere are caused by stale .go files (guile doesn't know how to recompile dependent .scm files). I would suggest a good old `grep -Rl --include '*.go&

Re: A friendlier API for operating-system declarations

gt; configuration, with a syntax similar enough to docker and ansible that > sysadmins familiar with it can quickly get up and running, thus exposing > more people to Guix. > > What do you think ? You've got me interested :) especially since you already have customer feedback! Best, -- Josselin Poiret signature.asc Description: PGP signature

Re: more package transformations: overrides

e dependency graph, as some sort of override. Seems like a good idea! Cc'ing Sarthak as they might be also interested in implementing this, as a good first experience with package transformations. Best, -- Josselin Poiret signature.asc Description: PGP signature

Re: Interest in Participating for GSoC '23

he draft proposal > 4. Would anyone here be interested in co-mentoring this project I unfortunately don't think I can co-mentor the project, but I'll always be happy to answer questions whenever I'm available :) [1] https://issues.guix.gnu.org/61684#16 Best, -- Josselin Poiret signature.asc Description: PGP signature

Re: Gnome dans core-updates

g bug that is fixed in newer releases, but updating swig would cause a world rebuild). Best, -- Josselin Poiret signature.asc Description: PGP signature

Re: Gnome dans core-updates

Hi Andreas, Andreas Enge writes: > Am Sun, Mar 19, 2023 at 10:20:27AM +0100 schrieb Josselin Poiret: >> The project does seem functional, they just seem to not care about >> making new releases, since they direct users to official builds of HEAD >> [1]. Maybe we could jus

Re: Gnome dans core-updates

roject does seem functional, they just seem to not care about making new releases, since they direct users to official builds of HEAD [1]. Maybe we could just point there as well? [1] https://github.com/ipxe/ipxe/discussions/679 Best, -- Josselin Poiret signature.asc Description: PGP signature

Re: Core-updates and cross-compilation

-- Andreas Enge writes: > Hello, > > Am Sat, Mar 11, 2023 at 01:56:27PM +0100 schrieb Josselin Poiret: >> I've been looking at the state of most failures for the CI jobset for >> core-updates, and we have a couple of problems: >> - gcc < 9 and gcc == 12

Re: State of core-updates

seable on Linux kernels with a page size > 4K and requires building the > whole rust chain to Icecat working. Since jemalloc is indeed a dependency of icecat, it would also get built by the CI job if the latter is added. Best, -- Josselin Poiret signature.asc Description: PGP signature

Re: Caching test results separately?

packages, and better environment management for tests (we could rely on better interaction with other packages, more complicated mocking, use linux namespaces to their fullest extent, etc.). That would require a huge change to Guix though, so it's more of a dream than anything concrete.

  1   2   >