From mboxrd@z Thu Jan  1 00:00:00 1970
From: Pjotr Prins <pjotr.public12@thebird.nl>
Subject: Re: [PATCH] gnu: python-sqlalchemy: Update to 1.0.11 (oops: fixed
	name).
Date: Mon, 8 Feb 2016 22:09:25 +0100
Message-ID: <20160208210925.GA29609@thebird.nl>
References: <56b8c867.Mt4UAAdU6v84queb%pjotr.public12@thebird.nl>
	<20160208200627.GA6422@debian> <20160208200746.GA6441@debian>
	<20160208204951.GB29510@thebird.nl> <20160208205710.GA12844@debian>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Return-path: <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:36357)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <pjotr2016@thebird.nl>) id 1aSt4f-0001mF-Vr
	for guix-devel@gnu.org; Mon, 08 Feb 2016 16:10:22 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <pjotr2016@thebird.nl>) id 1aSt4b-0007Z6-1R
	for guix-devel@gnu.org; Mon, 08 Feb 2016 16:10:21 -0500
Received: from mail.thebird.nl ([95.154.246.10]:38059)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <pjotr2016@thebird.nl>) id 1aSt4a-0007YP-S7
	for guix-devel@gnu.org; Mon, 08 Feb 2016 16:10:16 -0500
Content-Disposition: inline
In-Reply-To: <20160208205710.GA12844@debian>
List-Id: "Development of GNU Guix and the GNU System distribution."
	<guix-devel.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/guix-devel>
List-Post: <mailto:guix-devel@gnu.org>
List-Help: <mailto:guix-devel-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=subscribe>
Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org
Sender: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org
To: Andreas Enge <andreas@enge.fr>
Cc: guix-devel@gnu.org

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
> 

--