> > Also, for some reason, directly modifying (guix ui) (see
> > "call-with-error-handling") to handle our new error doesn't work.
>
> Aha, it's using a released "guix" package in the test VM. Where can I change
> that to "guix-devel"?
(services (modify-services (operating-system-user
> Also, for some reason, directly modifying (guix ui) (see
> "call-with-error-handling") to handle our new error doesn't work.
Aha, it's using a released "guix" package in the test VM. Where can I change
that to "guix-devel"?
Hi Chris,
On Sat, 06 Jan 2018 17:46:46 -0800
Chris Marusich wrote:
> Danny Milosavljevic writes:
>
> > Try this:
> >
> > diff --git a/gnu/build/linux-boot.scm b/gnu/build/linux-boot.scm
> > index 4dd740174..810a0d63f 100644
> > --- a/gnu/build/linux-boot.scm
> > +++ b/gnu/build/linux-boot.scm
Danny Milosavljevic writes:
> Try this:
>
> diff --git a/gnu/build/linux-boot.scm b/gnu/build/linux-boot.scm
> index 4dd740174..810a0d63f 100644
> --- a/gnu/build/linux-boot.scm
> +++ b/gnu/build/linux-boot.scm
> @@ -507,7 +507,14 @@ to it are lost."
> (switch-root "/root")
>
Hi Catonano,
On Mon, 1 Jan 2018 11:54:50 +0100
Catonano wrote:
> thank you so much for this !
You're welcome.
> I don't know if it' s current anymore, though
It's always good to improve the error reporting. I'll try to get it into guix
master (bug 29922).
> Now the trytond test succeeds (ya
Danny,
2018-01-01 0:39 GMT+01:00 Danny Milosavljevic :
> Try this:
>
> diff --git a/gnu/build/linux-boot.scm b/gnu/build/linux-boot.scm
> index 4dd740174..810a0d63f 100644
> --- a/gnu/build/linux-boot.scm
> +++ b/gnu/build/linux-boot.scm
> @@ -507,7 +507,14 @@ to it are lost."
> (sw
Try this:
diff --git a/gnu/build/linux-boot.scm b/gnu/build/linux-boot.scm
index 4dd740174..810a0d63f 100644
--- a/gnu/build/linux-boot.scm
+++ b/gnu/build/linux-boot.scm
@@ -507,7 +507,14 @@ to it are lost."
(switch-root "/root")
(format #t "loading '~a'...\n" to-load)
I made it
the first trytond test (to check if trytond is running) passed successfully
make check-system TESTS="trytond"
And it's exactly midnight !
Happy New Year !
2017-12-31 15:48 GMT+01:00 Catonano :
>
>
> 2017-12-31 15:35 GMT+01:00 Danny Milosavljevic :
>
>> Is the tryton test using mari
2017-12-31 15:35 GMT+01:00 Danny Milosavljevic :
> Is the tryton test using marionette-operating-system ?
>
I believe it is
Anyway, here's the definition of the service
https://gitlab.com/humanitiesNerd/guix-hacks/blob/trytonservice/gnu/services/trytond.scm
And here's the test
https://gitlab.co
Is the tryton test using marionette-operating-system ?
marionette-shepherd-service seems to already try to remote-control the system -
but it seems that this case has not been handled?
Check out marionette-shepherd-service in gnu/tests.scm for the general
mechanism. Maybe add some (display "XX
2017-12-31 13:23 GMT+01:00 Danny Milosavljevic :
> Hi Catonano,
>
> On Sun, 31 Dec 2017 12:39:07 +0100
> Catonano wrote:
>
> > In attempting to test my trytond service wit hthhis line
> >
> > make check-system TESTS="trytond"
> >
> > I get this errror
> >
> > [...]
> > adding user 'guixbuilder08'
Hi Catonano,
On Sun, 31 Dec 2017 12:39:07 +0100
Catonano wrote:
> In attempting to test my trytond service wit hthhis line
>
> make check-system TESTS="trytond"
>
> I get this errror
>
> [...]
> adding user 'guixbuilder08'...
> adding user 'guixbuilder09'...
> adding user 'guixbuilder10'...
>
In attempting to test my trytond service wit hthhis line
make check-system TESTS="trytond"
I get this errror
[...]
adding user 'guixbuilder08'...
adding user 'guixbuilder09'...
adding user 'guixbuilder10'...
adding user 'trytond'...
adding user 'postgres'...
registering public key
'/gnu/store/94
13 matches
Mail list logo