From: Jonathan Brielmaier <jonathan.brielmaier@web.de>
To: guix-devel@gnu.org
Subject: Re: Pushed a fix (?) for ACL key location
Date: Sun, 12 Jul 2020 13:42:29 +0200 [thread overview]
Message-ID: <522d8a75-a2ba-d6a0-908f-a6e5029c3309@web.de> (raw)
In-Reply-To: <877dv98q1z.fsf@dustycloud.org>
On 12.07.20 03:44, Christopher Lemmer Webber wrote:
> Commit 6680880f9b8dceb4f2f3f91bd2b13c659b53835e pushed out a new version
> of Guix, and it looks like it wasn't possible to build new systems from
> that because the filename for the "Berlin ACL key" changed. (Or at
> least, I couldn't run "guix system vm".)
>
> I pushed out a "fix" for this. I hope it's ok.
Thanks for the fix.
As I ran into all those little errors with `guix pull` this week-end, I
wonder if we can do better.
So maybe some pre-checkin CI which tests that a commit/commit series
doesn't break `guix pull`. What do you think? Is this doable?
I find those little errors pretty annoying as they seem to be avoidable
through technical counter measures...
next prev parent reply other threads:[~2020-07-12 11:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-12 1:44 Pushed a fix (?) for ACL key location Christopher Lemmer Webber
2020-07-12 11:14 ` Marius Bakke
2020-07-12 11:42 ` Jonathan Brielmaier [this message]
2020-07-12 12:33 ` Marius Bakke
2020-07-12 14:21 ` zimoun
2020-07-12 16:27 ` Jonathan Brielmaier
2020-07-12 13:57 ` zimoun
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=522d8a75-a2ba-d6a0-908f-a6e5029c3309@web.de \
--to=jonathan.brielmaier@web.de \
--cc=guix-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).