On 04/29/2018 at 10:19 Carlo Zancanaro writes:
> Hey George,
>
> On Sat, Apr 28 2018, George myglc2 Clemmer wrote:
>> g1@sysi17 ~ [env]$ guix environment
>> --substitute-urls=https://g1.local:8080
>
> The guix substitute command only runs a normal http server, so you
> have to use http://, not
Hey George,
On Sat, Apr 28 2018, George myglc2 Clemmer wrote:
g1@sysi17 ~ [env]$ guix environment
--substitute-urls=https://g1.local:8080
The guix substitute command only runs a normal http server, so you
have to use http://, not https://. I think the other servers you
mention are behind
On 04/28/2018 at 15:16 George myglc2 Clemmer writes:
> I am attempting to supply substitutes from a GuixSD install (g1) to a
> 'guix system vm-image' (sysi17.local). I did this on g1 ...
Oops, here are configs (sys.scm was used for g1)...
sys.scm
Description: Binary data
sysi17.scm
I am attempting to supply substitutes from a GuixSD install (g1) to a
'guix system vm-image' (sysi17.local). I did this on g1 ...
g1@g1 ~$ sudo guix publish
guix publish: warning: server running as root; consider using the '--user'
option!
publishing /gnu/store on 0.0.0.0, port 8080
... and I
For example, if you specify 'glib:bin' as an input, it will add only 'glib' as
an input. (It's not recognising a specified output of a package recipe that
produces multiple outputs.)
Ansible currently is broken.
As noted by sturm/Guest2732 on #guix, running any `ansible-'
commands leads ansible to think that we are calling the `ansible' script
directly, instead of via a `ansible-' script.
This is related to [1], and possibly might be solved by [2].
[1]:
