Politely, my relatively-new-user observations about `guix pull` and home/system
reconfigure commands,
1. The commands, in my experience, always fail with network troubles, and the
commands must be re-issued multiple times for
things to complete. Other internet-requesting utilities such as wget,
Hi Ludo’,
Thank you for getting back to me!
l...@gnu.org (Ludovic Courtès) writes:
> Hi Chris, and sorry for the delay!
>
> Chris Marusich skribis:
>
>> Backtrace:
>> In ice-9/boot-9.scm:
>> 157: 15 [catch #t # ...]
>> In unknown file:
>>?:
->8---
+ exec autoreconf -vfi
./bootstrap: line 5: exec: autoreconf: not found
--8<---cut here---end--->8---
This makes me wonder: has something changed, and the manual is now
incorrect?
--
Chris
signature.asc
Description: PGP signature
John Darrington writes:
> On Tue, Sep 27, 2016 at 09:18:30PM -0700, Chris Marusich wrote:
> Hi,
>
> The manual says ((guix) Building from Git):
>
> --8<---cut here---start->8---
> The easiest
wrench in my plans. When I try to rebase onto
master, there are multiple conflicts, and I am not sure yet what the
best way to resolve them will be. In any case, I think it will be more
productive to ask for feedback now, rather than to continue on my own
down u
guix-devel package that always builds from the Git repo?
>
> - Dave
That would certainly make it obvious and easy to use. I think it's a
good idea.
--
Chris
signature.asc
Description: PGP signature
-->8---
Regardless, I appreciate you mentioning the -e option; that is useful to
know, and it highlights the difference between the name of the variable
used to refer to the package object and the name of the package, which I
often forget are not the same.
--
Chris
signature.asc
Description: PGP signature
l...@gnu.org (Ludovic Courtès) writes:
> "Thompson, David" skribis:
>
>> On Wed, Sep 28, 2016 at 5:20 PM, Ludovic Courtès wrote:
>>> Hi Chris,
>>>
>>> Chris Marusich skribis:
>>>
>>>> John Darrington writes:
>>>
27;t include the signature. If you know how to make it
include the signature, please let me know!
I verified that the new package builds. Notably, it did not build on my
GuixSD machine until I shortened the version string.
--
Chris
From 3fa2bc4f0d11fc695bfab9b85981228c1a88e007 Mon Sep 17 00:00:00 2
Hi,
l...@gnu.org (Ludovic Courtès) writes:
> Hi,
>
> Chris Marusich skribis:
>
>> Here's a patch to address the following issue ('guix environment guix
>> doesn't provide guix dependencies'):
>>
>> https://lists.gnu.org/archive/html/guix
Hi,
l...@gnu.org (Ludovic Courtès) writes:
> Hi!
>
> Chris Marusich skribis:
>
>> I believe my patch does NOT yet make the regenerated grub.cfg a GC root,
>> so it is possible that after rolling back or switching generations,
>> invoking GC might clean up some t
Hi Ludo,
l...@gnu.org (Ludovic Courtès) writes:
> Hello,
>
> Chris Marusich skribis:
>
>> l...@gnu.org (Ludovic Courtès) writes:
>
> [...]
>
>>> Sorry about that! Hopefully we can work around the conflicts.
>>
>> I think we can. But I think it w
aw some interesting-looking references in the Protego
paper linked above, but I didn't go down the rabbit hole.
For what it's worth, the Nix/NixOS people have not (to my knowledge)
solved this problem, either. They didn't mention any setuid
alternatives in any of the papers I checked here:
http://nixos.org/docs/papers.html
Best regards,
--
Chris
signature.asc
Description: PGP signature
s, only the 3 in (gnu tests install) really test
> the ‘guix system’ command, which is what we’re interested in here.
Good to know! All the other tests passed. I'll look into adding new
tests for these new actions.
--
Chris
signature.asc
Description: PGP signature
hat the generated grub.cfg is what we expect in several
> different scenario.
Thank you for taking the extra time to test it.
> If that’s fine with you, I’d like to commit this version. With that
> done, the rest of the patch series will be rather easy.
>
> WDYT?
>
Sounds go
455843d7249894cb7456d8d5.)
>
> It makes me happy that these involved scenarios are tested, so I wanted
> to share. :-)
These are really nice! Just wanted to say I really like these automated
tests. Are they being run automatically anywhere?1
--
Chris
signature.asc
Description: PGP signature
follows:
* version: `04f4afb-dirty'
* extra version: `'
* build: `Sat May 14 01:48:09 UTC 2016'
I hope that helps.
--
Chris
signature.asc
Description: PGP signature
Hi,
I realized I forgot to include some info in the manual, so here's one
more patch to add the missing info.
Thank you,
--
Chris
From faee634b5ae6a3033671e6bca07fc5ed1bc699c8 Mon Sep 17 00:00:00 2001
From: Chris Marusich
Date: Wed, 2 Nov 2016 20:38:26 -0700
Subject: [PATCH] doc: Add de
Chris Marusich writes:
> Leo Famulari writes:
>
>> I wonder, has anybody besides ng0 tried using this with libreboot? They
>> recently reconfigured their GuixSD system after this was committed, and
>> since then they aren't able to boot.
>>
>> Th
Danny Milosavljevic writes:
> Hi,
>
> On Thu, 03 Nov 2016 03:35:42 -0700
> Chris Marusich wrote:
>> Additional info: I've just now upgraded my x200 laptop to the latest
>> release of Libreboot (r20160907), and I can still boot into GuixSD
>> normally.
>
&
Chris Marusich writes:
> I'm actually not sure what fancy tricks Libreboot (and its GRUB payload)
> might be using to find the grub.cfg file. But hopefully that
> information helps.
Upon further investigation, it seems that Libreboot searches for
grub.cfg in addition
umented in the manual, or was there a reason why
we didn't mention it there?
--
Chris
signature.asc
Description: PGP signature
ly became an official GNU package [1], it would be super nice to
have it in GNU Guix!
[1] https://lists.gnu.org/archive/html/ring/2016-11/msg4.html
--
Chris
signature.asc
Description: PGP signature
that whatever grub version is currently
available in guix (e.g., as seen via 'guix package --show=grub') will be
used.
Hope that helps!
--
Chris
signature.asc
Description: PGP signature
e so
> we can restart system services upon roll-back.
Right. Eventually we should have all the stuff discussed here:
https://lists.gnu.org/archive/html/guix-devel/2016-06/msg00173.html
Thank you for all your help and feedback. It's helped me to understand
Guile and Guix better.
e set
correctly in the executables? Why would we need to add code here to do
that for this one package? I thought it would happen automatically.
--
Chris
signature.asc
Description: PGP signature
s, though.
That said, I have found that in practice Python's packaging system is
very complicated, and .pth files almost always add an order of magnitude
to that complexity. So I will not be surprised if the answer here is
"there are no plans at this time."
> Note: Importing setuptools also adds two sub-commands:
> "install_egg_info" and "install_scripts". These sub-commands are
> executed even if "--single-version-externally-managed" is set, thus
> the .egg-info directory and the scripts defined in entry-points will
> always be created.
>
> Note: Even if the "easy-install.pth" is not longer created, we kept this
> phase. There still may be packages creating an "easy-install.pth" manually
> for some good reason.
Are these notes truly necessary? Can they perhaps just be comments in
the source code instead? If they are truly necessary in the manual,
please consider including them as footnotes, so it is easy to tell which
section of text you wanted to associate these notes with.
--
Chris
signature.asc
Description: PGP signature
when installing? Or, would it be better
to just describe what needs to be done in the manual?
[1] https://lists.gnu.org/archive/html/help-guix/2016-04/msg00052.html
[2] https://debbugs.gnu.org/cgi/bugreport.cgi?bug=22707
--
Chris
signature.asc
Description: PGP signature
ides a script to perform garbage collection, can't we just
invoke that script? It isn't clear to me why we would need to model
domain-specific actions like that in Shepherd, although I can see why it
might be convenient. Am I missing something?
--
Chris
signature.asc
Description: PGP signature
Hi Chris!
Thanks for entertaining my questions.
Christopher Allan Webber writes:
>> So sure, we can run "foo-db gc" occasionally (though system
>> administrators sometimes have to run these kinds of commands by hand).
>> But what about "foo-db dumpdb"?
Hi Chris,
Thank you for taking the time to clarify the motivation! It helped a
lot.
Christopher Allan Webber writes:
> The command you *want* to run is something like:
>
> `foo-db dumpdb --config=/path/to/foodb.cfg'
>
> Now... your GuixSD system has, somewhere buried
back welcome!
>
> Ludo’.
Wow! This is super cool! Using OCR is a neat idea. It looks simpler
to implement than I would have imagined it might be. Thank you for
continuing to pave the way for system tests.
Is anyone actively working on documenting the new encrypted root stuff?
If not, I
)
This patch works for me. I built qemu successfully using it. The info
docs are present now, and they were missing before. I'd say ship it!
--
Chris
signature.asc
Description: PGP signature
gotten an optimistic start on that work, and
many things are building successfully. Exciting!!
--
Chris
signature.asc
Description: PGP signature
Hi Vincent, Jack, and Maxim,
Thank you for the quick replies! OK, so gcc differs for each of us:
* Chris:
8aca7f332a1ba8e3c2225c161a7545b0a04ddd690d164dc97afee9c9ea067b0c49bc155e9f06d285c22e24cdd16d91e59730af5f1dd9efcda13a26bede5948a2
* Vincent
" "$(srcdir)/$@"
--8<---cut here---end--->8---
...but I didn't see new messages when I ran "make" (from a clean
checkout). Maybe I didn't invoke make correctly.
If you or anyone else could point out if I'm missing something, that'd
be really helpful. Thank you in advance!
--
Chris
signature.asc
Description: PGP signature
can keep collaborating to make it happen!
Footnotes:
[1] https://debbugs.gnu.org/cgi/bugreport.cgi?bug=41669
[2] https://gitlab.com/lle-bout/guix
--
Chris
signature.asc
Description: PGP signature
it (see: (make) Suffix
Rules). Thank you very much for pointing it out to me!
I'm still not sure about the rest, though... Maybe Ludo knows.
--
Chris
signature.asc
Description: PGP signature
anding
is that whatever version of the "patch" program that Guix has placed in
the PATH environment variable will be used. Therefore, Guix will use
the correct "patch" program, regardless of whether or not the package is
being cross-compiled. Am I misunderstanding something?
Again, thank you for taking the time to bring these topics up. I'm
always trying to make sure I do things the best way I can in Guix, so I
appreciate the feedback.
--
Chris
signature.asc
Description: PGP signature
in Guix.
>
> If it's truly no extra burden, then you could change "--batch" to
> "--force" on line 69 of libffi.c (in the "powerpc-*" case).
OK. I've made this change on master in commit
662e7e28d576ada91fc9dec7d27c100666114f03.
Mark H Weaver
quested derivation's inputs (mainly other derivations, I think?) and
write them to the store, without actually executing any significant
builds.
I suppose that Guix is building these things in order to do just that,
but I don't quite understand why this happens. Can someone explain it
Chris Marusich writes:
> Hi,
>
> I've noticed that Guix builds many things when I ask it to instantiate a
> derivation in the following way:
>
> [0] [env] marusich@garuda-lan:~/guix/repos/guix-worktrees/wip-ppc64
> $ guix build -d --target=powerpc64-linux-gnu -e
Hi Chris,
Christopher Baines writes:
> Grafts.
>
> → guix build --no-grafts -d --target=powerpc64-linux-gnu -e '(@@ (gnu
> packages make-bootstrap) %gcc-static)'
> /gnu/store/i5wn3xl6p0zw1vglscgk0bs9dwc6hdh6-gcc-static-5.5.0.drv
>
> They're on by default, so
use problems in
build environments, since /bin/sh isn't available there?
Anyway, I'm fine with making a change like
2da8fcfdee7cfde8110a68806f3c4d497f217fe5 for powerpc64le-linux, since it
clearly seems like a necessary reference on that architecture. That's
probably what I'll do.
--
Chris
signature.asc
Description: PGP signature
closing brackets (<>)? Or is there an Emacs command that does it
for you? I've briefly looked on the Internet, but this is the kind of
thing that seems difficult to search for.
--
Chris
signature.asc
Description: PGP signature
p-ppc. I have
already cherry-picked one of your commits
(2da8fcfdee7cfde8110a68806f3c4d497f217fe5) onto wip-ppc64le (as commit
52f0b3db6ef3d3c5067c704c2190f72d2994a999), since it was needed. How
would you like to coordinate this work?
- Are there any other tips/advice/rules?
Thank you,
--
Chris
signature.asc
Description: PGP signature
. I think I'll try something
similar.
Bengt Richter writes:
> I am not sure I understand your context or goal in searching ;/
I'm always interested in finding more effective ways to get things done.
Sometimes, asking people how they do something is the best way to
discover new methods, even if the answer seems simple or obvious.
--
Chris
signature.asc
Description: PGP signature
(and commit any changes)
3) Run make guix-binary.powerpc64le-linux.tar.xz
That should give us a distributable binary copy of guix to work with,
which will be helpful. Right now, I'm just manually running
pre-inst-env from a checkout on a Debian ppc64le machine, where I've
manually cobbled together the dependencies required to build Guix.
--
Chris
signature.asc
Description: PGP signature
anaged by the foreign distro, and this
code is intended primarily to be used on the build side, where we
wouldn't encounter such cases anyway.
My understanding is that skipping this test is the right solution,
rather than attempting to teach gremlin to always be able to find
libraries when the runpath is empty. What do you think?
--
Chris
signature.asc
Description: PGP signature
-ppc64le at this time.
I have also taken the liberty of cherry-picking Tobias' commit
65fb3a3eb9a759e3dba18e78113e80d7e5b353f4 from master, which adds Léo to
.guix-authorizations. This should allow him to add commits on
wip-ppc64le without worrying about causing problems for "guix pull
l here is just to get Guix to build and pass its
tests on powerpc64le-linux. Getting things like rust and emacs to work
after that will be another challenge.
--
Chris
signature.asc
Description: PGP signature
.
I've confirmed that works for emacs, except that you actually have to
also do it for gtk+, too, since rust gets pulled in via gtk+ also. So,
something like this:
From 649c89e5862e1ed887f5fd863ef7bb32f97bbe74 Mon Sep 17 00:00:00 2001
From: Chris Marusich
Date: Sun, 7 Mar 2021 17:42:37 -0
(_ gdk-pixbuf)))
("libepoxy" ,libepoxy)
("libxcursor" ,libxcursor)
("libxi" ,libxi)
I've tested this patch (on its own, applied to wip-ppc64le locally,
without the other two patches mentioned earlier in this thread), a
Chris Marusich writes:
> How about a patch like the following - would it be acceptable to you?
Actually, I've realized that that patch wasn't quite right. I've
attached a corrected version to this email.
Although the %current-system parameter will look like "x86_64-lin
resolve those in the coming weeks.
The real question, I think, is when do we plan to upgrade GCC on
core-updates? It's still on GCC 7.5.0. The powerpc64le-linux port will
require GCC 8 or greater, since core-updates is now using glibc 2.32.
--
Chris
signature.asc
Description: PGP signature
s not use glibc-mesboot (i.e., any system
other than x86_64-linux or i686-linux). We could limit the change to
just fix it for powerpc64le-linux, but I think the other systems will
need the fix, too.
In short, I think it will be simplest to just merge wip-ppc64le into
core-updates and then merge core-updates into master.
--
Chris
signature.asc
Description: PGP signature
ith other architectures, when we can be. Then we
can share the same problems and help fix them together.
--
Chris
signature.asc
Description: PGP signature
ant to break anything for the other system types,
but you never know what will happen. This sort of testing might uncover
problems on core-updates, too, since wip-ppc64le is currently based off
of core-updates.
Anyway, I'll email you privately about VM access later.
--
Chris
signature.asc
Description: PGP signature
system*:
ERROR: Wrong type (expecting string): #f
--8<---cut here---end------->8---
Something about the way in which we are searching for the patch is off,
but I don't have time just now to investigate. Efraim, if you can
figure it out, that'd be nice, but I'll look into it more tomorrow.
It's probably something simple and related to commit 2712703.
--
Chris
signature.asc
Description: PGP signature
27;m still working on getting you access to ppc64le hardware or a VM.
Andreas Enge writes:
> Am Fri, Mar 12, 2021 at 12:33:18AM -0800 schrieb Chris Marusich:
>> The proc man page has this to say about column 7:
>> (7) optional fields: zero or more fields of the form "tag[:v
Chris Marusich writes:
> Subject: [PATCH] syscalls: mount: Fix a matching bug.
In the patch message, "mount" should be "mounts". Sorry for the typo!
--
Chris
signature.asc
Description: PGP signature
Hi,
I have good news!
Chris Marusich writes:
> Subject: [PATCH] syscalls: mount: Fix a matching bug.
If there are no concerns about this patch, I will commit it to master
(with the "mount" typo fixed so it reads "mounts") in the next few days.
> Efraim Flashner wr
thread like this. Thank
you for noticing it and replying. In the future, I'll send bugs/patches
to bug-guix/guix-patches to increase their visibility.
--
Chris
signature.asc
Description: PGP signature
Hi simon,
zimoun writes:
> First, thanks to Chris and folks, powerpc64le-linux will be [1] in the
> next release, great! Isn’t it? :-)
I'm very excited about this! Efraim was able to rework our patches so
they could be applied to master without rebuilding the entire world.
The
e manual (info "(guix) GNU Distribution").
OK! I was planning to add some commits to update the docs, anyway. I
can do those two tasks.
Additionally, I plan to finally merge wip-ppc64le-for-master to master
later today. I'll send a note when that's done.
--
Chris
signature.asc
Description: PGP signature
hat we can make a release!
--
Chris
signature.asc
Description: PGP signature
. Link counts (e.g., the number of hard links) do
not seem to play a role here.
In addition to the C++ code, the Nix thesis has a good discussion of the
garbage collection algorithm. I don't know if it's accurate, but it
helps shed light on the intent.
--
Chris
signature.asc
Description: PGP signature
e in the "install" procedure in guix/scripts/system.scm.
--
Chris
signature.asc
Description: PGP signature
Gábor Boskovits writes:
> Thanks for all your help. The talk went well, they asked me to repeat it on
> the Free Software Conference on the 12. of May.
That's awesome! It's great to see more people spreading the word. :-)
--
Chris
signature.asc
Description: PGP signature
e derivation?
My interpretation of the intended behavior of "guix environment foo" is
that is that only the inputs of (the bag of) foo should show up in the
environment, not the transitive closure of inputs. I am surprised to
hear that that is not the case, but perhaps I am missing something.
--
Chris
signature.asc
Description: PGP signature
that
might be to add either the system installation or the build user's
installation of Guix (the latter should be at ~/.config/guix/latest) to
the GUILE_LOAD_PATH in your build user's ~/.bashrc on the Debian host.
Another way might be to run "guix package -i guix" as the build user on
the Debian host.
Hope that helps! Good luck.
--
Chris
signature.asc
Description: PGP signature
ix" as the build user on
>> the Debian host.
>
> but this did. Too bad, I wanted avoid installing guix into the profile.
Glad it worked. To figure out precisely why only the last method worked
for you, I guess it would be necessary to debug the exact logic that is
importing the modules. It's probably somewhere in
guix/scripts/offload.scm, maybe?
--
Chris
signature.asc
Description: PGP signature
Devan writes:
> Hi all,
>
> Pjotr Prins transcribed 0.6K bytes:
>> Hi Chris,
>>
>> That was a lengthy writeup, thanks :). I think the first step is to
>> think in terms of (container/VM) provisioning. Then build that up towards
>> orchestration and workf
didn't test this because I'm not familiar with
how to test the website and I'm a little pressed for time right now.
--
Chris
From 19bc5d9f53a7d6f0a1bc64428e6224cd07c74f3c Mon Sep 17 00:00:00 2001
From: Chris Marusich
Date: Sat, 17 Mar 2018 19:40:13 +0100
Subject: [PATCH] website: co
Chris Marusich writes:
> l...@gnu.org (Ludovic Courtès) writes:
>
>> Hello Guix!
>>
>> What about allowing posts on help-guix in one of the languages that
>> regular contributors know, in addition to English?
>
> I like it! Here's a patch for Japanese
t;teach" Java how to follow store
references, and the class loader machinery is well pretty documented.
The tricks we (and Nix) do with the linker (e.g., ld-wrapper) to always
use rpaths for C programs and libraries is similar in spirit: if the
machine does not know our rules by default, we must teach the machine
how to play by our rules.
--
Chris
signature.asc
Description: PGP signature
l...@gnu.org (Ludovic Courtès) writes:
> Chris Marusich skribis:
>
>> From e817d96b6a52eb6450c2edb4e03ccbfdce30d9d6 Mon Sep 17 00:00:00 2001
>> From: Chris Marusich
>> Date: Sat, 17 Mar 2018 19:40:13 +0100
>> Subject: [PATCH] website: contacts: Add Japa
in the .drv file of the grafting
> derivation, which will include the file name of the original ungrafted
> derivation among its input derivations.
In this case, you can actually just add --no-grafts to the invocation,
as in:
guix build --no-grafts --log-file guile
This will show you the log of the build, before applying any grafts.
--
Chris
signature.asc
Description: PGP signature
ix, too. If it isn't possible to install plugins, then
that's not so great, but if the browser is usable in spite of that, then
it's probably better to add the browser now and iterate on it - we could
figure out how to accommodate the plugins later.
--
Chris
signature.asc
Description: PGP signature
service as the first argument and the result of applying
‘compose’ to the extension values as the second argument. It
must return a value that is a valid parameter value for the
service instance.
What do you think?
--
Chris
signature.asc
Description: PGP signature
"compose" procedure to a
single list. So why does the activation-service-type use the append
procedure as its "compose" procedure? Wouldn't it more accurately
reflect our intent if we used the identity procedure instead?
--
Chris
signature.asc
Description: PGP signature
t
home page contained malware, then surely that would be a problem.
> Thanks for taking a look at this :)
My pleasure! Thank you for taking the time to work on it.
--
Chris
signature.asc
Description: PGP signature
tory is.
However, if we really want to modify the heuristics, I can think of some
possible ideas for how to do it:
* Don't canonicalize the path in the first place.
* Stop just before the first path that is in the store.
* Stop at the first path that is in the store.
* Stop at a path that matches a special pattern that we control,
like "guix-python-site" or something. We could create
> 4. Path-handling in Python's start-up sequence
As you've shown, the way Python handles paths when it starts up is quite
complicated. This is another reason why I would prefer not to change
the heuristics, but instead to expose a way for us to explicitly tell
Python where its site is.
--
Chris
signature.asc
Description: PGP signature
l...@gnu.org (Ludovic Courtès) writes:
> Hello!
>
> Chris Marusich skribis:
>
>> Is the description of "compose" correct? The manual claims that it
>> "must return a value that is a valid parameter value for the service
>> instance," but I d
a
"compute" procedure that accepts a single argument (which will be your
service's value) and returns a G-Expression that creates the directory.
Different extensible services have different expectations, so you would
need to implement different "compute" procedures to extend them.
Thankfully, even if an extensible service is not clearly documented, you
can usually tell what its contract is by looking at some services that
extend it already.
I hope that helps!
Footnotes:
[1] https://lists.gnu.org/archive/html/guix-devel/2018-03/msg00307.html
--
Chris
signature.asc
Description: PGP signature
l...@gnu.org (Ludovic Courtès) writes:
> Chris Marusich skribis:
>
>> The fold-services procedure always applies the "compose" procedure to a
>> single list. So why does the activation-service-type use the append
>> procedure as its "compose" proced
useful for operating build farms and measuring improvements in their
performance. There are a lot of great tools out there for analyzing
metrics / telemetry data, including fancy dashboarding software (e.g.,
Kibana and Grafana come to mind). Does Guile have any existing
libraries for logging me
Thorsten Wilms writes:
> Thank you, Chris, for taking the time to go into such detail!
I found the service documentation to be a little confusing when I first
read it. The slight incorrect statements (which I have now corrected
after confirming the intended behavior with Ludo) did not h
dealing with dependency graphs.)
I think you may have forgotten some words. When you said "it’s also
become clearer Scheme as convenient as C when it comes to systems
programming and things like dealing with dependency graphs", what did
you mean?
--
Chris
signature.asc
Description: PGP signature
program find the classes here via the CLASSPATH environment
variable, which was set earlier during the configure phase by the
generate-classpath procedure?
--
Chris
signature.asc
Description: PGP signature
. However, if you want to change the user/group
structure, you ought to be able to do so. I believe you can do that by
customizing the "users" and "groups" fields of your
declaration (see: (guix) operating-system Reference). You even should
to be able to remove the "users" group entirely if you don't want it.
Hope that helps!
--
Chris
signature.asc
Description: PGP signature
runtime, the software will detect the CPU and
either perform better or make more features available. Is that right?
I see you added the "--enable-sse" configure flag, and it not present
before. Why did you add it?
--
Chris
signature.asc
Description: PGP signature
;s story is a great example of this! For this
reason, some people will still choose to build things from source
themselves, even if substitutes are available from some other place.
--
Chris
signature.asc
Description: PGP signature
tputs? For example, put the libraries into the default "out" output
and the programs into the "bin" output.
--
Chris
signature.asc
Description: PGP signature
ot too bad
It worked for me just fine!
--
Chris
signature.asc
Description: PGP signature
script and the "pre-generated non-source files"
you're talking about?
--
Chris
signature.asc
Description: PGP signature
57nxslq
$ guix hash --recursive /tmp/test
1xmr8jicvzszfzpz46g37mlpvbzjl2wpwvl2b05psipssyp1sm8h
What's going on here? No matter what I try (e.g., change recursive? to
#t), I can't seem to escape this hash mismatch. I think I'm missing
something obvious, but I can't see what
#x27;sha256' is instead a procedure which computes the sha256 hash
> of its argument.
This was the problem! I misunderstood what the daemon was telling me,
and I didn't realize that "sha256" was the field name.
I knew a second pair of eyes would help! Thank you for helping me to
see more clearly, Mark. :-)
--
Chris
signature.asc
Description: PGP signature
Marius Bakke writes:
> Building 'bootstrap-tarballs' for other architectures fails on
> core-updates.
Could this be related to the following bug report?
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=24841
--
Chris
signature.asc
Description: PGP signature
such a build system decoupled from Guix, the package manager.
--
Chris
signature.asc
Description: PGP signature
1 - 100 of 657 matches
Mail list logo
