bug#66510: `this-package' references reintroduce pre-transformation packages.

Suppose you have a package that is using a gexp in its argument list and, like a good citizen of the gexp world, it uses this-package-input to refer to its own input packages. In fact, let's suppose that it's the model citizen depicted in https://guix.gnu.org/en/blog/2021/the-big-change/ under

bug#66027: [PATCH v3 2/3] gnu: patman: Apply patch for new Change-Id setting.

* gnu/packages/bootloaders.scm (u-boot) [source]: Apply patch. * gnu/packages/patches/u-boot-patman-change-id.patch: New file. * gnu/local.mk (dist_patch_DATA): Register it. * .patman (keep_change_id): Use it. Change-Id: I33c03013f6a260b5f5d80212b7b6ebe8a3f97efa --- Changes in v3: - New commit

bug#66027: [PATCH v3 3/3] etc: teams: Parse 'From' commit more leniently.

When a Change-Id is used, patman prepends a Message-Id field on the first line of the patch, which broke the assumption that the 'From $commit' line must appear on the first line. * etc/teams.scm.in (git-patch->commit-id): Loop each line of the file until a match is found. Update doc.

bug#66027: [PATCH v3 1/3] build: Add a commit-msg hook that embeds Change-Id in commit messages.

Partially implements . This will make it possible to track a merged commit back to its original posting on the mailing list, and open the door to new opportunities such as closing fully merged series automatically. * Makefile.am (COMMIT_MSG_MAGIC): New

bug#65665: package-mapping with #:deep? #t doesn't get all the implicit inputs

Ludovic Courtès writes: > Ulf Herrman skribis: > >> -(define (build-system-with-package-mapping bs rewrite) >> +(define (build-system-with-package-mapping bs rewrite-input >> rewrite-argument) >>"Return a variant of BS, a build system, that rewrites a bag's inputs by >> passing them

bug#65665: package-mapping with #:deep? #t doesn't get all the implicit inputs

Maxim Cournoyer writes: > Any build system accepting package as arguments are subject to this > problem, if I understand correctly. It's not quite everywhere a package is accepted as an argument: there are many cases where a package is passed as a package argument but doesn't end up in the

bug#58497: opam import doesn't work with ocaml_intrinsics among others

Simon Tournier writes: > Hi, > > It is about bug#58497 [1], and I cannot reproduce. I think the reported > bug had been fixed. I am in favor to close. WDYT? > > 1: https://issues.guix.gnu.org/issue/58497 > > On Thu, 13 Oct 2022 at 18:07, Csepp wrote: > >> guix import opam

bug#66033: Package name conflict for "helm"

Hi Panos, On Sat, Sep 16, 2023 at 05:39 PM, Panos Alevropoulos wrote: > Hi, > > There seems to be a recently introduced package name conflict. > There are two packages named "helm". One is is the package manager for > Kubernetes and the other is a synthesizer. I noticed after upgrading > and

bug#64856: guix shell cache doesn't consider grafts

Hello, Maxim Cournoyer skribis: > While investigating https://issues.guix.gnu.org/64836, I discovered that > the cache of 'guix shell' doesn't take into account grafts for > subsequent invocations. Fixed in 75bdf8e06a325b90bf387a03f88726d338acbbf6. Thanks, Ludo’.

bug#65665: package-mapping with #:deep? #t doesn't get all the implicit inputs

Hi, Ludovic Courtès writes: > Ulf Herrman skribis: > >> -(define (build-system-with-package-mapping bs rewrite) >> +(define (build-system-with-package-mapping bs rewrite-input >> rewrite-argument) >>"Return a variant of BS, a build system, that rewrites a bag's inputs by >> passing them

bug#65665: package-mapping with #:deep? #t doesn't get all the implicit inputs

Hi Ludovic, Ludovic Courtès writes: > Hi Ulf, > > Ulf Herrman skribis: > >> In short, the current approach of having the build-system lower >> procedure leave the arguments mostly unchanged and letting the >> bag->derivation procedure (the "bag builder") fill in lots of defaults >> means that

bug#64858: ~guix shell -C -f guix.scm …~ should not always need ~--rebuild-cache~ option to build the expected environment.

Hi Pierre-Henry, Pierre-Henry Fröhring skribis: > $ guix shell -C -f guix.scm ripgrep fd coreutils emacs [...] > This very file (~pkgex.el.org~) is updated with this content then the > package is > built again. > > #+begin_example > $ make build # equivalent to: guix build -f guix.scm > … >

bug#66380: Derivation pb with curl on aarch64-linux

Hello! :-) Pierre Ramet skribis: > Please find the following backtrace obtained on Debian virtual machine > aarch64 (from a Mac M1 host) : [...] >> message: "build of >> `/gnu/store/m819aix1w6b6x1dki7fhnizmy45fipw9-curl-8.3.0a.drv' failed" AFAICS there are now substitutes for this

bug#57878: Emacs native compilation on startup can crash the system

Hello, Konrad, Emacs team: is this bug still happening today? https://issues.guix.gnu.org/57878 TIA, Ludo’. Liliana Marie Prikler skribis: > Am Samstag, dem 17.09.2022 um 17:45 +0200 schrieb Konrad Hinsen: >> Konrad Hinsen writes: >> >> > Here is a minimal containerized example that >> >

bug#65665: [PATCH] Really get all the implicit inputs.

Hi Maxim, On Thu, 05 Oct 2023 at 22:36, Maxim Cournoyer wrote: > I've reviewed it, and it makes sense to me. I'd like to apply it to the > core-updates branch. Core team, what say you? Well, I am not sure to deeply understand some details to get all the implications here, so I have nothing

bug#66027: [PATCH v2] build: Add a commit-msg hook that embeds Change-Id in commit messages.

Hi, On Mon, 09 Oct 2023 at 11:03, Maxim Cournoyer wrote: > + particularly if a first version of your proposed > +changes was already published. Sorry if my English is not good enough. Here, it is not clear for me what “published” means. Does it mean “tracked” by Debbugs?

bug#63331: Guile-GnuTLS/Git circular dependency

Ludovic Courtès skribis: > Ludovic Courtès skribis: > >> The longer-term solution is to add a “builtin:git-download” derivation >> builder, just like we have “builtin:download”. The implementation >> should be relatively easy, but we’ll have to be able to deal with >> daemons that lack this

bug#66305: Error with recursive git checkout

Ludovic Courtès skribis: > Pushed as 762fdbdef52b4c17df578478cadc8655d56171a4. > > Now to update ‘guix’… Done last week in 16fd9d6e3d626fc624c38cb3096331905a4161e4. Closing!

bug#66419: Incorrect handling of -L flag on guix system commands

Hi, Sergio Pastor Pérez skribis: > λ guix system build -L . bordercollie.scm > error: %useful-gnome-extensions: unbound variable > hint: Did you forget `(use-modules (base-system))'? > > /gnu/store/gf21yc9ii1cfd3ki9hnn8ac5d65923ir-system ‘-L’ does more than setting ‘GUILE_LOAD_PATH’; it’s

bug#66472: Wrong ‘glibc-utf8-locales’ package used on GNU/Hurd

Ludovic Courtès writes: Hey! > We discussed it briefly on IRC the other day: our packages get built on > i586-gnu with the wrong ‘glibc-utf8-locales’ package (2.35 instead of > 2.37), which causes Coreutils among others to fail to build: > > environment variable `GUIX_LOCPATH' set to >

bug#65665: package-mapping with #:deep? #t doesn't get all the implicit inputs

Ulf Herrman skribis: > -(define (build-system-with-package-mapping bs rewrite) > +(define (build-system-with-package-mapping bs rewrite-input rewrite-argument) >"Return a variant of BS, a build system, that rewrites a bag's inputs by > passing them through REWRITE, a procedure that takes an

bug#65665: package-mapping with #:deep? #t doesn't get all the implicit inputs

Hi Ulf, Ulf Herrman skribis: > In short, the current approach of having the build-system lower > procedure leave the arguments mostly unchanged and letting the > bag->derivation procedure (the "bag builder") fill in lots of defaults > means that there are implicit inputs that cannot be touched

bug#65665: package-mapping with #:deep? #t doesn't get all the implicit inputs

Hi, Ulf Herrman skribis: > I've also been using this patch, which rebinds `this-package' within > package variants to refer instead to the variant rather than the > original. Could you send it as a separate issue? (I think I once reported a bug for this issue, but I can’t find it.) Ludo’.

bug#66254: "guix --version | head -1" crashes most of the time

Simon Tournier writes: > Hi Clément, Hey Simon, [...] > Anyway. The issue is from leave-on-EPIPE. This patch fixes the issue, > I guess. > > diff --git a/guix/ui.scm b/guix/ui.scm > index 6f2d4fe245..507bc67f1d 100644 > --- a/guix/ui.scm > +++ b/guix/ui.scm > @@ -2309,7 +2309,7 @@ (define

bug#66358: Can't import package using archive command

Hi, On Mon, 09 Oct 2023 at 14:25, Tobias Geerinckx-Rice via Bug reports for GNU Guix wrote: > I think it would be less surprising if these ‘single, mutually exclusive > actions’ should always be (sub)subcommands, e.g., ‘guix archive import’, > ‘guix archive authorize’, … I am proposing to

bug#66254: "guix --version | head -1" crashes most of the time

Hi Clément, On Thu, 28 Sep 2023 at 12:20, Clément Lassieur wrote: >> guix --version | cat | head -1 > works Not for me. --8<---cut here---start->8--- $ guix --version | cat | head -1 guix (GNU Guix) 6113e0529d61df7425f64e30a6bf77f7cfdfe5a5 Backtrace:

bug#66297: guix-daemon not starting after boot

Hi Sharlatan, Sharlatan Hellseher skribis: > I think I just get used to kick it manually and forgot to replay on > this issue =) Ouch. :-) > sudo grep -i "shepherd\|herd" /var/log/messages | tail > grep: /var/log/messages: binary file matches Looks like grep didn’t actually output

bug#65665: [PATCH] Really get all the implicit inputs.

Hi! Maxim Cournoyer skribis: > Ulf Herrman writes: > >> This patch series causes package-mapping to recurse into package and bag >> arguments when #:deep? #t is given. It also recurses into gexps and >> gexp inputs in search of packages to devour. It also ensures that build >> systems leave