New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
upgrade ZODB to version 3.10.5 #10352
Comments
comment:1
NOTE ABOUT spkg-checkI tried adding an spkg-check, but the fact is that the ZODB test suite fails miserably all over the place. This is true both of the version in Sage (3.7.0) and the version posted here. The failures start with:
but there is no Regarding spkg-check, here's what it should look like:
|
comment:2
ZODB is used by the database_cremona optional spkg. Thus a way to test this package is to install that optional package, then do:
and not get an error. Just that is enough to show that the ZODB is doing pretty much all we use it for in Sage. Running the test suite for ZODB is unfortunately not possible :-(. Also, be sure to test the "devel/sage/sage/databases" directory, and you of course should do "make test" in SAGE_ROOT to test the whole library. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
comment:4
I just tried installing this and at the end got:
so somehow setuptools is still thinking partly that it needs to install ZODB 3.7.0. So screw it. I'm changing this to needs work and not messing with it anymore. |
This comment has been minimized.
This comment has been minimized.
comment:6
Ticket #1634 should be marked as a duplicate. |
comment:7
I am bumping it up to "major", since it turns out that zodb screws up refcounts, which makes the debug version of Sage (#13864) fail. |
comment:8
Can we change this ticket and update to zodb3-3.10.5? Namely, in contrast to 3.10.1, version 3.10.5 does fix one of the problems from #13864. |
comment:9
Replying to @simon-king-jena:
Will do. Got an spkg ready here. |
comment:10
For review purposes, I've just taken William's original upgrade to 3.10.1 and dumped 3.10.5 in instead. As it turns out, our present ZODB3 version does not support Python 2.7, so upgrading is very much recommended. |
This comment has been minimized.
This comment has been minimized.
Author: William Stein, Nils Bruin |
comment:14
There are some version mismatches, this needs
|
comment:15
Thanks for catching! spkg updated. |
comment:18
How about
|
comment:19
Replying to @vbraun:
Why should an independent module only be shipped as part of another independent module? Even if zope.interface was currently only used by sagenb, I'd still think zope.interface should be an separate spkg.
That sounds good to me. |
comment:20
The sagenb spkg contains already a dozen of python dependencies:
|
comment:21
Not sure exactly what changed in the new spkg, but there are still version mismatches:
|
comment:22
Replying to @vbraun:
Is sagenb a system that should be able to run independent of another system, or is sagenb supposed to be installed on top of another system (such as Sage)? In the former case, I could understand why sagenb comes with batteries included. But if sagenb is intended to be a small brick in a large wall, then it seems to me that a small brick shouldn't attempt to contain other small bricks... But I am not a software engineer. Anyway, the fact that sagenb contains a lot of dependencies (taking the risk that the same dependency is provided twice, perhaps even in different versions) should not force us to add yet another module to sagenb. |
comment:23
Replying to @simon-king-jena:
Yes, it is supposed to be something that can run without Sage (it is supposed to only require python). I don't know to what extent that is currently the case. William |
comment:24
Replying to @jdemeyer:
These are different versions than you reported before. I put the files in there you requested last time. to any zope version expert: please put versions in there that make Jeroen happy. |
comment:25
Perhaps the problem is simply the order of packages installed. |
comment:26
Can somebody actually post a log from a failed install attempt? It works for me. The version mismatches shouldn't matter either, distutils is checking that each package's dependencies are satisfied. You don't need matching versions of all zope* packages (indeed, they are not in sync). Also I don't understand what Jeroen posted, the spkg from the ticket issue contains zope.exceptions-4.0.4.zip and zope.interface-4.0.2.tar.gz and not the versions you mention. |
comment:27
Replying to @vbraun:
The problem is this:
When transaction is installing, zope.interface hasn't been installed yet and must be downloaded from the internet. |
comment:28
I guess you can indeed easily reproduce that by shutting down your internet connection and making sure no previous installation of zope.interface is available (e.g. do not upgrade the zodb spkg on an existing sage install). |
Changed author from William Stein, Nils Bruin to William Stein, Nils Bruin, Volker Braun |
comment:29
I've built sage-5.6.beta2 from scratch with the new spkg and verified that zodb is not downloading anything (that is, no "Downloading" or urls in the spkg log). |
This comment has been minimized.
This comment has been minimized.
comment:30
Looks good to me (but it's going to be removed anyway, right?) |
Reviewer: Jeroen Demeyer |
comment:31
Its probably premature to remove it in sage-5.6, let's first fix the sagenb dependency. I've created sagemath/sagenb#126 to raise awareness on the sagenb side. |
Merged: sage-5.6.beta3 |
comment:33
Just as a point of information, this was indeed added to upstream, see also #10353 where that was confirmed. |
Upgrade ZODB to the latest upstream version.
The new spkg is here:
http://www.stp.dias.ie/~vbraun/Sage/spkg/zodb3-3.10.5.spkg
See also: #10353.
Component: packages: standard
Author: William Stein, Nils Bruin, Volker Braun
Reviewer: Jeroen Demeyer
Merged: sage-5.6.beta3
Issue created by migration from https://trac.sagemath.org/ticket/10352
The text was updated successfully, but these errors were encountered: