Re: Changes made to pysqlite-2.6.3 without changing the version number

2014-02-09 Thread Andreas Enge
On Sat, Feb 08, 2014 at 05:58:27PM +0100, Ludovic Courtès wrote: > The solution is for ‘core-updates’ to switch to Guile 2.0.10 (hopefully > released within a couple of weeks, thanks to Mark), or to introduce a > patch like the one Cyril posted some time ago. If we only have to wait for a couple o

Re: Changes made to pysqlite-2.6.3 without changing the version number

2014-02-08 Thread Ludovic Courtès
Andreas Enge skribis: > On Sat, Feb 08, 2014 at 12:19:32AM +0100, Ludovic Courtès wrote: >> Commit 7a03af7 changes the version number and URL as a stopgap measure. > > But we still have the problem that pypi.python.org requires TLS, which > does not work, see >http://hydra.gnu.org/build/38210

Re: Changes made to pysqlite-2.6.3 without changing the version number

2014-02-08 Thread Andreas Enge
On Sat, Feb 08, 2014 at 12:19:32AM +0100, Ludovic Courtès wrote: > Commit 7a03af7 changes the version number and URL as a stopgap measure. But we still have the problem that pypi.python.org requires TLS, which does not work, see http://hydra.gnu.org/build/38210/nixlog/1/raw Is there any soluti

Re: Changes made to pysqlite-2.6.3 without changing the version number

2014-02-07 Thread Ludovic Courtès
Mark H Weaver skribis: > We don't have a working pysqlite-2.6.3 package in Guix right now. The > reason is that the upstream source tarball has changed without changing > the version number. For the record, I've attached the diff here. Commit 7a03af7 changes the version number and URL as a sto

Changes made to pysqlite-2.6.3 without changing the version number

2014-02-06 Thread Mark H Weaver
Hello all, We don't have a working pysqlite-2.6.3 package in Guix right now. The reason is that the upstream source tarball has changed without changing the version number. For the record, I've attached the diff here. I mailed the author about this, but he never replied. It would be good if so