unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Christopher Baines <mail@cbaines.net>
To: Hilton Chain <hako@ultrarare.space>
Cc: 57587@debbugs.gnu.org
Subject: [bug#57587] [PATCH v2] gnu: python-apsw: Update to 3.39.2.1.
Date: Tue, 06 Sep 2022 09:01:22 +0100	[thread overview]
Message-ID: <87r10p2ao0.fsf@cbaines.net> (raw)
In-Reply-To: <y76v8q2nyf4.wl-hako@ultrarare.space>

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


Hilton Chain via Guix-patches via <guix-patches@gnu.org> writes:

> From 5bcc29595eefa3632c4ac3ed9e77d8c5a3a7765d Mon Sep 17 00:00:00 2001
> From: Hilton Chain <hako@ultrarare.space>
> Date: Mon, 5 Sep 2022 10:45:11 +0800
> Subject: [PATCH v2] gnu: python-apsw: Update to 3.39.2.1.
>
> * gnu/packages/databases.scm (python-apsw): Update to 3.39.2.1.
> [arguments]: Use bundled Makefile.
> ---
> v1 -> v2: Enable parallel compilation.
>
>  gnu/packages/databases.scm | 21 +++++++++++++--------
>  1 file changed, 13 insertions(+), 8 deletions(-)

I think this breaks the calibre package on x86_64-linux, could you take
a look at whether it builds for you with this change?

Thanks,

Chris

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 987 bytes --]

  reply	other threads:[~2022-09-06  8:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-05  2:45 [bug#57587] [PATCH] gnu: python-apsw: Update to 3.39.2.1 Hilton Chain via Guix-patches via
2022-09-05  6:11 ` [bug#57587] [PATCH v2] " Hilton Chain via Guix-patches via
2022-09-06  8:01   ` Christopher Baines [this message]
2022-09-06 10:46     ` [bug#57587] " Hilton Chain via Guix-patches via
2022-09-06 11:35       ` Hilton Chain via Guix-patches via
2022-09-06 12:54   ` [bug#57587] [PATCH] " Hilton Chain via Guix-patches via
2022-09-06 12:59     ` [bug#57587] [PATCH v3] " Hilton Chain via Guix-patches via
2022-09-07 17:16       ` bug#57587: " Marius Bakke

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=87r10p2ao0.fsf@cbaines.net \
    --to=mail@cbaines.net \
    --cc=57587@debbugs.gnu.org \
    --cc=hako@ultrarare.space \
    /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).