unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Simon South <simon@simonsouth.net>
To: 46873@debbugs.gnu.org
Subject: [bug#46873] [PATCH 1/2] gnu: knot-resolver: Ensure all custom phases return #t on success.
Date: Tue,  2 Mar 2021 08:53:26 -0500	[thread overview]
Message-ID: <da92549ffd4f17be006ddb45366657ff729a3aac.1614691387.git.simon@simonsouth.net> (raw)
In-Reply-To: <cover.1614691387.git.simon@simonsouth.net>

* gnu/packages/dns.scm (knot-resolver)[arguments]<#:phases>: Return #t from
"move-doc" phase on success.
---
 gnu/packages/dns.scm | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/gnu/packages/dns.scm b/gnu/packages/dns.scm
index 2c4008559f..5b0e310a0c 100644
--- a/gnu/packages/dns.scm
+++ b/gnu/packages/dns.scm
@@ -979,7 +979,8 @@ synthesis, and on-the-fly re-configuration.")
                                (string-append doc "/share/" dir)))
                 '("doc/knot-resolver/examples"
                   "doc/knot-resolver/html"
-                  "info")))))
+                  "info"))
+               #t)))
          (add-after 'install 'wrap-binary
            (lambda* (#:key inputs outputs #:allow-other-keys)
              (let* ((out (assoc-ref outputs "out"))
-- 
2.30.1





  reply	other threads:[~2021-03-02 13:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-02 13:52 [bug#46873] [PATCH 0/2] gnu: knot-resolver: Fix phase return value; update to 5.3.0 Simon South
2021-03-02 13:53 ` Simon South [this message]
2021-03-02 14:22   ` [bug#46873] [PATCH 1/2] gnu: knot-resolver: Ensure all custom phases return #t on success Tobias Geerinckx-Rice via Guix-patches via
2021-03-02 13:53 ` [bug#46873] [PATCH 2/2] gnu: knot-resolver: Update to 5.3.0 Simon South
2021-03-02 15:12   ` bug#46873: " Tobias Geerinckx-Rice via Guix-patches via

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=da92549ffd4f17be006ddb45366657ff729a3aac.1614691387.git.simon@simonsouth.net \
    --to=simon@simonsouth.net \
    --cc=46873@debbugs.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).