unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Pjotr Prins <pjotr.public12@thebird.nl>
To: guix-devel@gnu.org
Subject: sqlite update causes failure of python-sqlalchemy
Date: Mon, 8 Feb 2016 17:46:41 +0100	[thread overview]
Message-ID: <20160208164641.GA28440@thebird.nl> (raw)

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?

Or live with the fact that python-sqlalchemy is broken for now. Maybe
it is possible to override the sqlite bindings to an earlier version,
but even if that worked I would think it tricky.

Personally I think we should revert. But then so many packages depend
on sqlite. Tricky.

Pj.

             reply	other threads:[~2016-02-08 16:47 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-08 16:46 Pjotr Prins [this message]
2016-02-09 21:15 ` sqlite update causes failure of python-sqlalchemy Ludovic Courtès
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

  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=20160208164641.GA28440@thebird.nl \
    --to=pjotr.public12@thebird.nl \
    --cc=guix-devel@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).