From: Tobias Geerinckx-Rice via Guix-patches via <guix-patches@gnu.org>
To: Morgan.J.Smith@outlook.com
Cc: 61408-done@debbugs.gnu.org, guix-patches@gnu.org
Subject: bug#61408: [PATCH v2] gnu: bees: Update to 0.9.1.
Date: Thu, 23 Feb 2023 23:57:18 +0100 [thread overview]
Message-ID: <87bklkq8vu.fsf@nckx> (raw)
In-Reply-To: <DM5PR03MB31630468C686EA7FC31AE876C5DC9@DM5PR03MB3163.namprd03.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 1099 bytes --]
Hi Morgan,
I've pushed an updated & modified version of this patch as
4f08551a83f3a9f5e22c70e51e488f38171e6937. Thanks!
Morgan.J.Smith@outlook.com 写道:
> * gnu/packages/file-systems.scm (bees): Update to 0.9.1.
> [arguments]: Add fixtest phase.
Since you reported this failure upstream, 0.9.2 was released with
your fix. \o/
I used that instead.
> * gnu/local.mk: Remove
> bees-beesd-honor-destdir-on-installation.patch
> *
> gnu/packages/patches/bees-beesd-honor-destdir-on-installation.patch:
> Delete
> file
I prefer writing this as
*
gnu/packages/patches/bees-beesd-honor-destdir-on-installation.patch:
Delete file.
* gnu/local.mk (dist_patch_DATA): Remove it.
> + license:gpl2)))) ; include/crucible/btrfs.h
Nice! Well spotted.
Now, any copyrightable change by BEES to this file would/will be
GPL3+. I didn't notice any in its commit log, though, so this
point is academic.
I erred on the side of keeping this, and added an explicit comment
that the combined work is GPL3+.
Kind regards,
T G-R
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
prev parent reply other threads:[~2023-02-23 23:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-10 18:08 [bug#61408] [PATCH] gnu: bees: Update to 0.9.1 Morgan.J.Smith
2023-02-12 18:12 ` [bug#61408] [PATCH v2] " Morgan.J.Smith
2023-02-23 22:57 ` Tobias Geerinckx-Rice via Guix-patches via [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bklkq8vu.fsf@nckx \
--to=guix-patches@gnu.org \
--cc=61408-done@debbugs.gnu.org \
--cc=Morgan.J.Smith@outlook.com \
--cc=me@tobias.gr \
/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.