Hi,
If removing "(expanse packages sterm)" from sterm.scm doesn't work you
could define expanse as a module in
expanse/expanse/packages.scm:
(define-module (expanse packages)
#:use-module (gnu packages))
On Sat, 24 Apr 2021 at 12:05, Julien Lepiller wrote:
>
> Hi,
>
> Are you sure expanse/p
Hello, Maxime!
> No, it is not supposed to work! Only guix/build/... and
> gnu/build/utils/... (and maybe others I forgot) are supposed to be
> imported, so source-module-closure excludes other modules. The reason
> is that gnu/packages/*.scm are supposed to be changeable without
> causing a
Hello Bone Baboon!
Great to hear that you got it working!
Bone Baboon writes:
> David Dashyan writes:
>> It is not 100% clear from your message how do you want to build a docker
>> image. I'm assuming that you want to use standard docker tooling and
>> you want to have docker daemon on YOUR s
Agr typos... need to make habit running ispell all the time...
...
I'm not sure why it is done this way. Perhaps because you could have
different service types providing same provision symbols? And you as a
user/admin CHOOSE which to CHOOSE. And also the dependency graph of guix
services NOT
David Dashyan schreef op di 27-04-2021 om 20:03 [+0300]:
>
> Hello, Maxime!
>
> > No, it is not supposed to work! Only guix/build/... and
> > gnu/build/utils/... (and maybe others I forgot) are supposed to be
> > imported, so source-module-closure excludes other modules. The reason
> > is that
Thank you Maxime for your answer :)
Maxime Devos writes:
> e...@beaver-labs.com schreef op zo 11-04-2021 om 21:31 [+0200]:
>> Dear fellow Guixers,
>
>> [...]
>> But, when I try to run it with shepherd, it fails because it can't find
>> flask (a dependency of the software, which I've put as a
>> p
