all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Pjotr Prins <pjotr.public12@thebird.nl>
To: Andreas Enge <andreas@enge.fr>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: python-sqlalchemy: Update to 1.0.11 (oops: fixed name).
Date: Mon, 8 Feb 2016 22:09:25 +0100	[thread overview]
Message-ID: <20160208210925.GA29609@thebird.nl> (raw)
In-Reply-To: <20160208205710.GA12844@debian>

Yes, that is what I have already done. I can't afford to wait ;)

I am just wondering how many packages are broken (visibly or not).

Sqlite changed something fundamental.

Pj.

On Mon, Feb 08, 2016 at 09:57:10PM +0100, Andreas Enge wrote:
> On Mon, Feb 08, 2016 at 09:49:51PM +0100, Pjotr Prins wrote:
> > They will fix it when they upgrade sqlite. python-sqlalchemy is under
> > active development. Question is what we do for the time being with
> > sqlite. 
> 
> I would say the culprit is python-sqlalchemy and not sqlite. So if you
> cannot wait for upstream to fix their package, one possibility would be
> to add a package for on older version of sqlite (assuming it does not
> present security problems) and to build python-sqlalchemy with it.
> It could even be a private variable only used in this input instead of
> a user visible variant.
> 
> Andreas
> 

-- 

  reply	other threads:[~2016-02-08 21:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-08 16:55 [PATCH] gnu: python-sqlalchemy: Update to 1.0.11 (oops: fixed name) Pjotr Prins
2016-02-08 17:26 ` Christopher Allan Webber
2016-02-08 19:46   ` Leo Famulari
2016-02-08 23:03     ` Christopher Allan Webber
2016-02-08 20:06 ` Andreas Enge
2016-02-08 20:07   ` Andreas Enge
2016-02-08 20:49     ` Pjotr Prins
2016-02-08 20:57       ` Andreas Enge
2016-02-08 21:09         ` Pjotr Prins [this message]
2016-02-10 16:51           ` Efraim Flashner

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=20160208210925.GA29609@thebird.nl \
    --to=pjotr.public12@thebird.nl \
    --cc=andreas@enge.fr \
    --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 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.