On Fri, Sep 21 2018, Rafael Fontenelle wrote:
Please check if the commit message is as expected.
I changed your commit message slightly (ironically, fixing a typo)
and pushed it as 86b3ef0fdc0d1374cb0a822755887b3d58142c26.
Thanks!
Carlo
Hi there, Carlo
Em qui, 20 de set de 2018 às 18:31, Carlo Zancanaro
escreveu:
>
> Could you send the patch through as formatted by "git
> format-patch" and with a commit message in the "ChangeLog"[1]
> format? It's probably easiest to just copy the style of commit
> messages in the repository.
N
Hello,
After installing guixsd (0.15) on a VM and doing "guix pull", "guix --version"
gives 0.14-.
I asked about this on IRC a few weeks ago and got a helpful answer. All
I needed to do to fix is was to run a simple bash command.
Unfortunately, I've forgotten what that was :-(
Reporting here sin
Hey Rafael!
On Fri, Sep 21 2018, Rafael Fontenelle wrote:
diff --git a/ANNOUNCE--0.5 b/ANNOUNCE--0.5
...
diff --git a/ANNOUNCE--0.6 b/ANNOUNCE--0.6
...
diff --git a/ChangeLog-2003 b/ChangeLog-2003
...
I am a bit conflicted about these ones, because in my mind these
are "append only" files.
Hello,
Running a spellcheck tool in the source code, I was able to find a few
typos. Please see the attached git-diff file for a fix.
Best regards,
Rafael Fontenelle
diff --git a/ANNOUNCE--0.5 b/ANNOUNCE--0.5
index 077bacb..ba30c95 100644
--- a/ANNOUNCE--0.5
+++ b/ANNOUNCE--0.5
@@ -6,7 +6,7 @@ Th
> A package will be grafted when any
> of its inputs (direct or transitive) have been replaced.
I understand why that would happen when _updating_ fish, but why does it happen
when (re-)building it from scratch, for instance when the graft source is gone
from the store?
--
Pierre Neidhardt
http
Pierre Neidhardt writes:
> I'm not so well versed in grafting, so let me ask a few questions:
>
> - Why is fish grafted in the first place?
Almost any package can be grafted. A package will be grafted when any
of its inputs (direct or transitive) have been replaced. The goal of
grafting is t
Hey Ludo’,
From the POV of the Shepherd, services carry no semantics.
In Guix we have as much information as possible about the
services. We should be know which services should be upgraded
automatically, which ones we should prompt the user to upgrade,
and which ones are never safe to upgr
Hello Xero,
Xero skribis:
> guix pull fails with the following message:
>
> ```
>
> guix pull: error: You found a bug: the program
> '/gnu/store/i1vsxyy6vnzdngfxylcanwmh9f8ax8ky-compute-guix-derivation'
>
> failed to compute the derivation for Guix (version:
> "e266043e670f4318679664f3af4401dab7
Carlo Zancanaro skribis:
> We still need to work out what we want to do on the Guix side once the
> Shepherd is released. Do we want to restart services that we can, or
> print a message telling users how to do so? Maybe individual services
> should be able to specify their preference?
I would r
[...] so presumably messages go to /dev/kmsg and/or the console.
I don't remember seeing anything about the exception in any of the
output that I looked at. I'm a bit confused about where different
bits of output go, so I'll take a look at how output is handled in
a few weeks, when the rest o
Hi,
Carlo Zancanaro skribis:
> On Thu, Sep 20 2018, Ludovic Courtès wrote:
>> Commit c4ba8c79db0aa4ba3517acc82ebafe16105fbb97 reinstates the
>> commit and removes the leftover #:replace, which was responsible for
>> the problem: ...
>
> That's great! I didn't even know about the #:replace option
Clément Lassieur writes:
> It builds now, closing.
Actually, the build error was my fault: it was a Cuirass issue: it was
taking the Chromium package from the Guix shipped with Cuirass, and
everything else from the Guix that was an input, so it didn't make
sense. Sorry for the noise.
> Clément
Hi,
Cuirass is unable to recover from this crash, which happens when
'github.com' (which is one of my inputs) is unreachable.
The Shepherd can't restart it (because 'github.com' is still
unreachable) so it disables it.
--8<---cut here---start->8---
2018-09-20T
14 matches
Mail list logo
