Hi Mark,
Mark H Weaver writes:
> Hi Jakob,
>
> zerodaysford...@sdf.lonestar.org (Jakob L. Kreuze) writes:
>
>> Thanks for the input; I wasn't aware that the activation process was
>> taking so long for some people. One of Ludovic's suggestions was to
>> create a single derivation, rather than th
Hi Jakob,
zerodaysford...@sdf.lonestar.org (Jakob L. Kreuze) writes:
> Thanks for the input; I wasn't aware that the activation process was
> taking so long for some people. One of Ludovic's suggestions was to
> create a single derivation, rather than three, to speed up system
> activation. I'll
Hi Mark,
Mark H Weaver writes:
> Hello again,
>
> Mark H Weaver writes:
>
>> As a bonus, this approach might solve another issue I've observed: on my
>> Guix system, where I build everything locally, several derivations are
>> built *during* activation. Based on the terminal output, I get the
Hi Ludo,
Ludovic Courtès writes:
> Jakob, now that we generate scripts for the effectful bits of system
> reconfiguration (one of these bits being service upgrades), couldn’t
> we take it one step further and store those scripts in the “system”
> derivation so we can run them eventually, notably
Hello again,
Mark H Weaver writes:
> Ludovic Courtès writes:
>
>> Jakob, now that we generate scripts for the effectful bits of system
>> reconfiguration (one of these bits being service upgrades), couldn’t we
>> take it one step further and store those scripts in the “system”
>> derivation so
Hi,
Ludovic Courtès writes:
> Jakob, now that we generate scripts for the effectful bits of system
> reconfiguration (one of these bits being service upgrades), couldn’t we
> take it one step further and store those scripts in the “system”
> derivation so we can run them eventually, notably upon
Hey Chris & Jakob,
Chris Marusich skribis:
> zerodaysford...@sdf.lonestar.org (Jakob L. Kreuze) writes:
>
>> 'switch-to-system-generation' doesn't call out to
>> 'upgrade-shepherd-services'. I'm not sure if this was an intentional
>> decision or not
>
> It is intentional, but only because there
Hi Robert,
Robert Vollmert writes:
> On 8. Aug 2019, at 18:40, Chris Marusich wrote:
>> zerodaysford...@sdf.lonestar.org (Jakob L. Kreuze) writes:
>>
>>> 'switch-to-system-generation' doesn't call out to
>>> 'upgrade-shepherd-services'. I'm not sure if this was an intentional
>>> decision or n
On 8. Aug 2019, at 18:40, Chris Marusich wrote:
> zerodaysford...@sdf.lonestar.org (Jakob L. Kreuze) writes:
>
>> 'switch-to-system-generation' doesn't call out to
>> 'upgrade-shepherd-services'. I'm not sure if this was an intentional
>> decision or not
>
> It is intentional, but only because t
Hi Jakob,
zerodaysford...@sdf.lonestar.org (Jakob L. Kreuze) writes:
> 'switch-to-system-generation' doesn't call out to
> 'upgrade-shepherd-services'. I'm not sure if this was an intentional
> decision or not
It is intentional, but only because there is currently no way to call
upgrade-shepherd
Hi Chris,
Christopher Lemmer Webber writes:
> Could you look at bug #36878 and commit 1db6f137d... as of latest
> master, is this fixed?
Unfortunately, I don't think that 1db6f137d fixes this. The issue is a
bit more structural as 'switch-to-system-generation' doesn't call out to
'upgrade-sheph
Could you look at bug #36878 and commit 1db6f137d... as of latest
master, is this fixed?
Robert Vollmert writes:
> Could we get some input on this bug?
>
> Maybe I’m misunderstanding something, but it seems that a core guix
> feature (atomic rollbacks) doesn’t work…
>
>> On 30. Jul 2019, at 12:00
Could we get some input on this bug?
Maybe I’m misunderstanding something, but it seems that a core guix
feature (atomic rollbacks) doesn’t work…
> On 30. Jul 2019, at 12:00, Robert Vollmert wrote:
>
> What I see:
>
> 1. edit ~/pzprnode/pzprnode
>
> rob@garp ~/pzprnode$ git diff
> diff --git
Could we get some input on this bug?
Maybe I’m misunderstanding something, but it seems that a core guix
feature (atomic rollbacks) doesn’t work…
> On 30. Jul 2019, at 12:00, Robert Vollmert wrote:
>
> What I see:
>
> 1. edit ~/pzprnode/pzprnode
>
> rob@garp ~/pzprnode$ git diff
> diff --git
Hi Robert,
Robert Vollmert writes:
> The line with “updated version” should not be there.
>
> Presumably, this is due to switch-generations not calling
> upgrade-shepherd-services.
I can confirm that 'switch-to-system-generation', the procedure that
carries out 'guix system switch-generation',
What I see:
1. edit ~/pzprnode/pzprnode
rob@garp ~/pzprnode$ git diff
diff --git a/pzprnode b/pzprnode
index 612e6a8..d8ef0ea 100755
--- a/pzprnode
+++ b/pzprnode
@@ -190,5 +190,6 @@ const server = http.createServer((req, res) => {
});
server.listen(port, hostname, () => {
+ console.log
16 matches
Mail list logo
