all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Maxime Devos <maximedevos@telenet.be>
To: derekchuank@outlook.com
Cc: "55769@debbugs.gnu.org" <55769@debbugs.gnu.org>, control@debbugs.gnu.org
Subject: [bug#55769] [PATCH] gnu: Add xwhite.
Date: Fri, 03 Jun 2022 21:32:21 +0200	[thread overview]
Message-ID: <15c4829e0b5085a1df976075d898d2acbd142809.camel@telenet.be> (raw)
In-Reply-To: <OS3P286MB112784C433EB82843A61F475BEA19@OS3P286MB1127.JPNP286.PROD.OUTLOOK.COM>

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

user guix
usertags 55769 + reviewed looks-good reviewed-looks-good
thanks
(list available at <https://debbugs.gnu.org/cgi/pkgreport.cgi?tag=reviewed-looks-good&users=guix>)

derekchuank@outlook.com schreef op vr 03-06-2022 om 19:07 [+0000]:
> +     (uri
> +      (string-append "https://github.com/derekchuank/xwhite/"
> +                     "releases/download/v" version
> +                     "/xwhite-" version ".tar.gz"))
> +     (sha256
> +      (base32
> "0jbnlj5a91ib4anprmylqqnbv9wa73cr7fsc1s54df0a0w5yq8sz"))))


New package definition LGTM (looks good to me).
The hash matches, without any malware in the tarball.
Assuming it actually builds (I haven't checked) it should be fine to
apply.

Greetings,
Maxime.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]

  reply	other threads:[~2022-06-03 19:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-02 15:39 [bug#55769] [PATCH] gnu: Add xwhite derekchuank
2022-06-02 18:43 ` Maxime Devos
2022-06-03 19:07 ` derekchuank
2022-06-03 19:32   ` Maxime Devos [this message]
2022-06-07 16:28     ` bug#55769: " Ludovic Courtès
     [not found] <TYCP286MB112305E6ECC94C4EB64342D7BEA19@TYCP286MB1123.JPNP286.PROD.OUTLOOK.COM>
2022-06-03 13:13 ` [bug#55769] " Maxime Devos

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=15c4829e0b5085a1df976075d898d2acbd142809.camel@telenet.be \
    --to=maximedevos@telenet.be \
    --cc=55769@debbugs.gnu.org \
    --cc=control@debbugs.gnu.org \
    --cc=derekchuank@outlook.com \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.