From: Tobias Geerinckx-Rice <me@tobias.gr>
To: Mark H Weaver <mhw@netris.org>
Cc: guix-devel@gnu.org
Subject: Re: 10/18: gnu: polkit: Update phase & snippet style.
Date: Tue, 27 Feb 2018 13:34:03 +0100 [thread overview]
Message-ID: <87b3b1fd9284e5d31200b5e7e4f5d65a@tobias.gr> (raw)
In-Reply-To: <87h8q2dgle.fsf@netris.org>
Hullo Mark,
On 2018-02-27 8:41, Mark H Weaver wrote:
>> nckx pushed a commit to branch master
>> in repository guix.
>>
>> commit 3c4bbb4c52418c8daf8b0e4605e3912685c9f44a
>> Author: Tobias Geerinckx-Rice <me@tobias.gr>
>> Date: Sat Feb 24 13:33:42 2018 +0100
>>
>> gnu: polkit: Update phase & snippet style.
>>
>> * gnu/packages/polkit.scm (polkit)[source]: End snippet with #t.
>> [arguments]: Substitute INVOKE for SYSTEM* and end phases with #t.
>
> This broke the build.
Oh no.
>> @@ -113,12 +116,12 @@
>> ;; to install in /etc, and to instead install the
>> skeletons in the
>> ;; output directory.
>> (let ((out (assoc-ref outputs "out")))
>> - (zero? (apply system*
>> - "make" "install"
>> + (invoke "make" "install"
>> (string-append "sysconfdir=" out "/etc")
>> (string-append "polkit_actiondir="
>> out
>> "/share/polkit-1/actions")
>> - make-flags))))))))
>> + make-flags)
>> + #t))))))
>
> It was a mistake to remove the 'apply'. Before your change, 'apply'
> interpreted its final argument (make-flags) as a _list_ of strings to
> pass to 'system*', after the initial arguments. Now that you've
> removed
> the 'apply', that final list argument is going directly to 'invoke',
> which expects all of its arguments to be strings. Hence, this:
[...]
> Did you test this before pushing it?
Well, obviously, yes, and, obviously, no :-)
I tested a working branch with more significant polkit changes (although
that's turning out to be such a quagmire I'm not sure if it's worth it)
on a remote machine, then pushed... whatever the hell this is from my
signing netbook. I don't remember making or fixing this typo, but there
it is. Nor can I really explain how they got mixed up. I'll not blame my
complete lack of sleep again.
It seemed like a good idea to get preparatory-but-stand-alone changes
like this out of my local branches; maybe not. This is the second time
this week I've managed to look right at a patch and read over the
obvious. Apply is... not that new.
Thanks (as well as to Ludo' for the revert),
T G-R
Sent from a Web browser. Excuse or enjoy my brevity.
prev parent reply other threads:[~2018-02-27 12:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180226191425.26598.22955@vcs0.savannah.gnu.org>
[not found] ` <20180226191428.7F0CF20AF5@vcs0.savannah.gnu.org>
2018-02-27 7:41 ` 10/18: gnu: polkit: Update phase & snippet style Mark H Weaver
2018-02-27 12:34 ` Tobias Geerinckx-Rice [this message]
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=87b3b1fd9284e5d31200b5e7e4f5d65a@tobias.gr \
--to=me@tobias.gr \
--cc=guix-devel@gnu.org \
--cc=mhw@netris.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).