From: ludo@gnu.org (Ludovic Courtès)
To: Pjotr Prins <pjotr.public12@thebird.nl>
Cc: guix-devel@gnu.org
Subject: Re: sqlite update causes failure of python-sqlalchemy
Date: Tue, 09 Feb 2016 22:15:41 +0100 [thread overview]
Message-ID: <87ziv9poua.fsf@gnu.org> (raw)
In-Reply-To: <20160208164641.GA28440@thebird.nl> (Pjotr Prins's message of "Mon, 8 Feb 2016 17:46:41 +0100")
Pjotr Prins <pjotr.public12@thebird.nl> skribis:
> Patch b24765139c8940541b23f84592d3580d53f71d71
>
> (define-public sqlite
> (package
> (name "sqlite")
> - (version "3.8.11.1")
> + (version "3.10.0")
> (source (origin
>
> is the cause of python(2|3)-sqlalchemy breaking. I confirmed that by
> regressing to the original sqlite package. Since the python binding is
> part of the interpreter, I suspect there may be more python modules
> vulnerable. I updated python-sqlalchemy to latest and that makes no
> difference. Its tests fail on sqlite 3.10.0 and pass on 3.8.11.1.
>
> What do we do? Revert on this sqlite patch for the new guix release?
> Or add a second sqlite package and have that as a python dependency?
I would do the latter, assuming that soon a new python-sqlalchemy
release would solve the problem. WDYT?
This is probably OK since python-sqlalchemy is a leaf, and so we’re
unlikely to end up mixing two different SQLite versions.
Ludo’.
next prev parent reply other threads:[~2016-02-09 21:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-08 16:46 sqlite update causes failure of python-sqlalchemy Pjotr Prins
2016-02-09 21:15 ` Ludovic Courtès [this message]
2016-02-13 0:13 ` [PATCH] Add and use sqlite-legacy-for-python Christopher Allan Webber
2016-02-13 0:23 ` Thompson, David
2016-02-13 1:09 ` Christopher Allan Webber
2016-02-15 2:40 ` Christopher Allan Webber
2016-02-15 19:38 ` Christopher Allan Webber
2016-02-15 20:13 ` Christopher Allan Webber
2016-02-15 21:03 ` Pjotr Prins
2016-02-21 21:11 ` Ludovic Courtès
2016-02-13 7:59 ` Andreas Enge
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=87ziv9poua.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=pjotr.public12@thebird.nl \
/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.