unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: "Nicolò Balzarotti" <nicolo@nixo.xyz>
To: "Ludovic Courtès" <ludo@gnu.org>,
	"Nicolò Balzarotti" <anothersms@gmail.com>
Cc: 33064-done@debbugs.gnu.org
Subject: [bug#33064] [PATCH 1/1] gnu: Add enchive
Date: Sat, 20 Oct 2018 02:10:29 +0200	[thread overview]
Message-ID: <b68c8cae-738b-1365-d701-8d33c4273158@nixo.xyz> (raw)
In-Reply-To: <87in1xejm9.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1909 bytes --]

Thanks! This was the first one, but many more are coming :)

I'll try to be more careful when linting (also, I didn't notice the 
commit message previously)

Thanks again :)

On 10/19/18 11:01 PM, Ludovic Courtès wrote:
> Hello Nicolò,
>
> Nicolò Balzarotti <anothersms@gmail.com> skribis:
>
>> From: nixo <nicolo@nixo.xyz>
>>
>> ---
>>   gnu/packages/crypto.scm | 32 ++++++++++++++++++++++++++++++++
>>   1 file changed, 32 insertions(+)
> Applied with the minor changes below reported by ‘guix lint’ and in the
> build log.  I also added a commit log that follows our conventions.
>
> Thank you, and welcome! :-)
>
> Ludo’.
>
>
> diff --git a/gnu/packages/crypto.scm b/gnu/packages/crypto.scm
> index 08faccfa1..77b4dba6d 100644
> --- a/gnu/packages/crypto.scm
> +++ b/gnu/packages/crypto.scm
> @@ -866,7 +866,8 @@ cannot sign messages in OpenBSD format yet.")
>                                     version ".tar.gz"))
>                 (sha256
>                  (base32
> -                "17hrxpp4cpn10bk48sfvfjc8hghky34agsnypam1v9f36kbalqfk"))))
> +                "17hrxpp4cpn10bk48sfvfjc8hghky34agsnypam1v9f36kbalqfk"))
> +              (file-name (string-append name "-" version ".tar.gz"))))
>       (build-system gnu-build-system)
>       (arguments
>        '(#:tests? #f                      ; no check target         '
> @@ -877,7 +878,8 @@ cannot sign messages in OpenBSD format yet.")
>                       (lambda _
>                         (let* ((out (assoc-ref %outputs "out"))
>                                (lisp (string-append out "/share/emacs/site-lisp")))
> -                        (install-file "enchive-mode.el" lisp)))))))
> +                        (install-file "enchive-mode.el" lisp)
> +                        #t))))))
>       (synopsis "Encrypted personal archives")
>       (description
>        "Enchive is a tool to encrypt files to yourself for long-term

[-- Attachment #2: Type: text/html, Size: 2616 bytes --]

      reply	other threads:[~2018-10-20  0:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-16 12:18 [bug#33063] [PATCH 0/1] gnu: Add enchive Nicolò Balzarotti
2018-10-16 12:18 ` [bug#33064] [PATCH 1/1] " Nicolò Balzarotti
2018-10-19 21:01   ` bug#33064: " Ludovic Courtès
2018-10-20  0:10     ` Nicolò Balzarotti [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=b68c8cae-738b-1365-d701-8d33c4273158@nixo.xyz \
    --to=nicolo@nixo.xyz \
    --cc=33064-done@debbugs.gnu.org \
    --cc=anothersms@gmail.com \
    --cc=ludo@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).