bug#47428: Problems building the up-to-date "devel" manual for the website

Hi Ludovic! Ludovic Courtès writes: > Hi, > > Maxim Cournoyer skribis: > >> Ludovic Courtès writes: > > [...] > >>> FWIW, the map(PROT_NONE) issue was (I think) fixed by >>> 0aef94e7bcbd272720f14c5343f74da5201ef90a (in May), itself a followup to >>> 47d48f0c43c13c0b43bc3e37b6239efd4bf2f74c, so

bug#49477: [core-updates] python-pyyaml fails on sanity-check

Pushed a fix as 80506bc6daa1d106e6f836f741eedfa92ad4e4b6 to core-updates, thanks!

bug#49485: [core-updates] Coreutils test failures on emulated ARMv7/AArch64

Ludovic Courtès skribis: > As can be seen in , the > Coreutils test suite fails on emulated hardware because argv[0] is an > absolute file name whereas the test suite expects it to be a basename: [...] > -tail: cannot fstat 'standard input' > -tail:

bug#49459: [core-updates] Coreutils 8.32 test failures on armhf-linux

Ludovic Courtès skribis: > This is apparently fixed by this Gnulib commit: > > commit 175e0bc72808d564074c4adcc72aeadb74adfcc6 > Author: Paul Eggert > Date: Thu Aug 27 17:52:58 2020 -0700 > > perror, strerror_r: remove unportable tests > > Problem reported by Florian Weimer i

bug#49498: Duplicate grafting derivations?

I tried to reproduce this bug now, because the derivations I mentioned are maybe a couple months old (I saved that list back then). However, it seems like grafted derivations are being substituted now... awesome! When did that happen? But it's not easy to try to reproduce the bug.

bug#49477: [core-updates] python-pyyaml fails on sanity-check

Le 8 juillet 2021 23:55:30 GMT-04:00, John Kehayias via Bug reports for GNU Guix a écrit : >Perhaps due to recent addition/changes for python sanity-check? > >Here is the relevant portion of the log from running ./pre-inst-env >guix build python-pyyaml on core-updates: > >warning: build_py: byte-

bug#49498: Duplicate grafting derivations?

In recent months, I noticed some confusing information during the grafting phase of updating my profiles. While doing `guix package -u .` on a large-ish profile (119 packages), I noticed that webkitgtk is being grafted more than once, like this: -- applying 25 grafts for /gnu/store/fm6a97lzv

bug#49145: Cannot build Guix (Texinfo failure)

*bump* Any idea, or anything I can try?

bug#47428: Problems building the up-to-date "devel" manual for the website

Hi, Maxim Cournoyer skribis: > Ludovic Courtès writes: [...] >> FWIW, the map(PROT_NONE) issue was (I think) fixed by >> 0aef94e7bcbd272720f14c5343f74da5201ef90a (in May), itself a followup to >> 47d48f0c43c13c0b43bc3e37b6239efd4bf2f74c, so I think the comment is >> stale. [...] > Sadly, th

bug#49490: [Cuirass] Failed dependency reported as failed build

Hello Guix! Look at this build (‘python-jupyter-sphinx-0.3.2’ on i686-linux): https://ci.guix.gnu.org/build/658660/details Its status is “Failed” and all the dependencies shown on that page have a green tick. But! The build log linked from the page suggests a dependency failed to build: --8

bug#49295: mumi: mu-debug is unbound in mu-message-send

Hi, Maxime Devos skribis: > ERROR: In procedure mu-message-send: > In procedure module-lookup: Unbound variable: mu-debug > processing > job: mail:162506283631699 > options: ((from . "Maxime Devos") (subject . "[PATCH] isc-dhcp: Fix > dhclient-script wrapper when cross-compiling.") (to . >

bug#49485: [core-updates] Coreutils test failures on emulated ARMv7/AArch64

As can be seen in , the Coreutils test suite fails on emulated hardware because argv[0] is an absolute file name whereas the test suite expects it to be a basename: --8<---cut here---start->8--- @ build-started /gnu/

bug#44906: [PATCH 3/3] ci: Properly construct URLs.

Implement a new function "api-url", which constructs URLs using relative URI and "resolve-uri-reference" (which implements the algorithm specified in RFC 3986 section 5.2.2) for building the URL, instead of just appending strings. This avoids issued if the server-url ends with a slash. Since "api-

bug#44906: [PATCH 2/3] substitutes: Properly construct URLs.

Use relative URIs and "resolve-uri-reference" (which implements the algorithm specified in RFC 3986 section 5.2.2) for building the URL, instead of just appending strings. This avoids issued if the cache-url ends with a slash. * guix/substitutes.scm (narinfo-request): Use resolve-uri-reference for

bug#44906: [PATCH 1/3] substitute: Fix handling of short option "-h".

The short option was listed in the help-text, but not recognized. --- guix/scripts/substitute.scm | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/guix/scripts/substitute.scm b/guix/scripts/substitute.scm index 03115ffe44..c044e1d47a 100755 --- a/guix/scripts/substitute.scm +++

bug#44906: [PATCH 0/3] Properly construct URLs if base-url has trailing slash

Here is now an attempt to solve the issue. It had to be fixed in guix/substitutes.scm and guix/ci.scm only. In guix/scripts/publish.scm I did not spot any place where wrong URLs are constructed. Many thanks to Mark for pointing to 'resolve-uri-reference'. Regarding CI: I did some tests, so these