bug#74332: zig: tuning-compiler flag translation

Hi, Since 2cc6e09a03c34da832b360fe4e848a9339d9360b we are using a simple conversion for -Dcpu and -march that is not correct in every single case. Gentoo made a translator for CFLAGS and CHOST to Zig flags that we can use to make a proper conversion: https://github.com/gentoo/gentoo/blob/

bug#74216: [science team] flint build failure

On Tue, Nov 12, 2024 at 9:01 AM Andreas Enge wrote: > > Hello Greg, > > Am Tue, Nov 05, 2024 at 03:43:31PM -0500 schrieb Greg Hogan: > > flint fails to build for me with the following error unless I include > > as an input a newer gcc version. > > out of curiosity, what is your exact build archite

bug#67240: dev: “make” of Guix fails, non-existent .git/hooks directory

Hi, On Tue, 12 Nov 2024 at 16:06, Maxim Cournoyer wrote: >> cp: cannot create regular file '.git/hooks/pre-push': No such file or >> directory >> make[2]: *** [Makefile:7454: .git/hooks/pre-push] Error 1 >> make[2]: Leaving directory '/home/simon/src/guix/guix' >> make[1]: *** [Makefile:6137: a

bug#73166: shell-autorized-directories

Nicolas Graves writes: > Building a package yes, but you can have external commands in a > manifest.scm or guix.scm. > > ... > > What I was saying is that we could restrain recording `guix shell --allow` > only if the manifest builds properly containerized and without network > access (outside pa

bug#67535: Does anyone use i686-linux? [was Re: bug#67535: ci.guix.gnu.org 'Cannot allocate memory' while building for i686-linux]

Hi, On Tue, 12 Nov 2024 21:59:42 +0900 Maxim Cournoyer wrote: > Great. That said, I wouldn't be against stopping building i686 > packages on our build farm. Nobody has shown much interested in > fixing the broken ones or hunting down test failures... it seems > better to focus our energy elsewh

bug#73166: shell-autorized-directories

On 2024-11-12 09:50, Suhail Singh wrote: > I was under the impression that the build phase in guix is always > containerized and without network access. Could you please elaborate on > this? Building a package yes, but you can have external commands in a manifest.scm or guix.scm. Saku provided

bug#74015: 'guix shell --export-manifest' fails for some transformations

Simon Tournier writes: > However, I am proposing: Aside the profile ’manifest’ file (lossy > process), we could store all the manifests provided by the command > line. Something as: > > /gnu/store/-profile/manifest > /gnu/store/

bug#73166: shell-autorized-directories

Nicolas Graves writes: > My last message to Saku basically agreed to this ;) Yes, my bad for only noticing that message after having sent mine. Whoops. > I'm actually willing to improve that patch series if you have better > ideas/implementations, I was just building on what I know > (direnv/.d

bug#74216: [science team] flint build failure

Hello Greg, Am Tue, Nov 05, 2024 at 03:43:31PM -0500 schrieb Greg Hogan: > flint fails to build for me with the following error unless I include > as an input a newer gcc version. out of curiosity, what is your exact build architecture and processor line? The package builds without problems on my

bug#67984: build of docbook-xsl-1.79.2-0.fe16c90 failed

Hi, Russell Hernandez Ruiz writes: > Terminal log follows. Build log attached. > > building /gnu/store/cr5cmzdjs74s32m6yzfl076l292cr7vf-docbook-xsl- > 1.79.2-0.fe16c90.drv... > |builder for `/gnu/store/cr5cmzdjs74s32m6yzfl076l292cr7vf-docbook-xsl- > 1.79.2-0.fe16c90.drv' failed with exit code 1

bug#67535: Does anyone use i686-linux? [was Re: bug#67535: ci.guix.gnu.org 'Cannot allocate memory' while building for i686-linux]

Hi, Leo Famulari writes: > On Sun, Nov 10, 2024 at 08:56:33PM +0900, Maxim Cournoyer wrote: >> I was about to write this; thanks for be6g faster :-). I believe the >> unpacking should now be fine even for i686, Leo? > > Yes, it's working now! Fantastic! Great. That said, I wouldn't be against

bug#73306: guix deploy fails with dropbear ssh server

> this seems to be an upstream regression: > > https://github.com/mkj/dropbear/issues/321 this has been fixed upstream. <#secure method=pgpmime mode=sign> -- • attila lendvai • PGP: 963F 5D5F 45C7 DFCD 0A39 -- “Those who are able to see beyond the shadows and lies of their culture will never

bug#73085: libjami fails to build

Hi, Kjartan Óli Águstsson writes: > I am trying to install GNU Jami but building libjami fails due to a > missing header > . At first > I thought it was a missing input but webrtc-audio-processing is listed > as an input. However when I look in the store directory of > webrtc-audo-processing i

bug#67985: sha256 hash mismatch for qyd6h3h0piaxj1wpibar66wjm8vycvdg-apr-1.7.0.tar.bz2

Hi, Russell Hernandez Ruiz writes: > Seems the problem was a bad mirror. > > Fixed? > https://git.savannah.gnu.org/cgit/guix.git/commit/?id=766822aa87b94eacb3c49fd68261ae4ce9088a56 It appears this was indeed a temporary fluke or bad mirror: --8<---cut here---start--

bug#67984: [PATCH core-updates] gnu: docbook-xsl: Disable parallel tests.

* gnu/packages/docbook.scm (docbook-xsl) [arguments] <#:parallel-tests?>: New argument. Fixes: Change-Id: I29180345bf48cb2f2c7d0e3b6fd59406fd545c6b --- gnu/packages/docbook.scm | 3 +++ 1 file changed, 3 insertions(+) diff --git a/gnu/packages/docbook.scm b/gn