Re: fixing --check saying outputs not valid

Ludovic Courtès writes: > Dave Love skribis: >>> Then you can run “guix build hwloc --check -L --no-grafts”, which will >>> build hwloc locally and raise an error if hwloc:{out,lib} are not >>> bit-identical to what you had in store. >> >> [Should

Re: fixing --check saying outputs not valid

Ludovic Courtès writes: > To run --check, you must first already have the store item(s) available. > > So you would first run: > > guix build hwloc > > which will ensure both hwloc and hwloc:lib are in your store, possibly > by downloading substitutes. > > Then you can run “guix build hwloc --c

fixing --check saying outputs not valid

I ran build --check on a new package and it complained that some output of the derivation aren't valid. Then I checked hwloc, which also has a "lib" output and it has the same problem: guix build: error: build failed: some outputs of `/gnu/store/bsafscmmaw43ssb0lhnri3vdi0wi0chx-hwloc-1.11.7.dr

Re: various packaging issues

Adonay Felipe Nogueira writes: > About own opinions and blocked contributions: Since you commented on a > contribution to a GNU project, I wonder if the issue was taken to the > FSF's Licensing and Compliance Lab and also to copyright-related > lawyers? Remember that the second one is usually th

debugging cycles in build

I changed a package to have a "lib" output, which failed because it detected a cycle (whereas it's OK with everything in "out"). Is there a good way to debug that? I couldn't easily find the code implementing the check.

Re: various packaging issues

l...@gnu.org (Ludovic Courtès) writes: > Honestly it’s unclear to me that this would bring much to > > and related sections. I'm seeing it from the point of view of view of someone who's quite experienced with Fedora and

Re: many 404s for substitutes

Ludovic Courtès writes: > A temporary workaround is to use > --substitute-urls=https://hydra.gnu.org, which can trigger a > regeneration of the missing archives. However use with care because > that poor machine is already loaded. I had 404s from hydra at the time, too. Anyway, things look OK

many 404s for substitutes

I've had many 404s for substitutes, both from mirror.hydra.gnu.org and hydra itself. This means that I can't, for instance, install the Guix version of Emacs, because with --fallback it runs out of the ~1GB I have in TMPDIR while trying to run cmake tests. [I'm surprised that installing Emacs pul

Re: various packaging issues

Ricardo Wurmus writes: > One example is “kentutils” in (gnu packages bioinformatics). It has > “samtabix” among its native-inputs and these additional sources are > unpacked in a separate build phase “prepare-samtabix”. Ah, thanks! Has anyone done or considered a rough idiom conversion guide f

Re: various packaging issues

Adonay Felipe Nogueira writes: > About the license field notation, I don't know if this is indeed what > the GNU Guix project interpretes about it, but for me I always see a > list of licenses as being connected with a series of "or"'s. That appears to be wrong, and certainly wouldn't be the usu

Re: various packaging issues

course). [I'm surprised that something with HPC interest doesn't have Openfabrics support, which is what I was looking at.] > Dave Love skribis: > >> * I should specify a disjunction of licences like "BSD or GPLv2" rather >> than the conjunction, which seems

various packaging issues

I was looking at making packages for HPC-related stuff I'm familiar with and I'm wondering how to translate features of the rpm or dpkg packaging that I understand. I couldn't see answers in the doc or immediately find examples; apologies if I've missed something obvious. * I should specify a dis