upgrade sagenb to version 0.10.8

[ohanar]

Includes a number of small bug fixes.

"Upstream" Tarball: ​sagenb-0.10.8.tar

[git]

Branch pushed to git repo; I updated commit sha1. New commits:

​5e0e0f9

sagenb: fix wrong tarball name in checksums.ini

[jhpalmieri]

On two different OS X machines, I get a doctest failure:

sage -t src/sage/all.py
**********************************************************************
File "src/sage/all.py", line 30, in sage.all
Failed example:
    for i in frames:
        filename, lineno, funcname, linelist, indx = inspect.getframeinfo(i)
        for nm in allowed:
            if nm in filename:
                break
        else:
            print filename
Expected nothing
Got:
    /Users/palmieri/Desktop/Sage_stuff/git/sage/local/lib/python2.7/site-packages/pytz-20\
13.8-py2.7.egg/pytz/__init__.py
**********************************************************************

[jhpalmieri]

Downgrading pytz to the version in sagenb-0.10.7.2 seems to fix the problem. Can you put together a new tarball with that change?

[git]

Branch pushed to git repo; I updated commit sha1. New commits:

​69c56e2

sagenb: update checksum

[ohanar]

Replying to jhpalmieri:

Downgrading pytz to the version in sagenb-0.10.7.2 seems to fix the problem.

sagenb's dist.sh script seems to just grab the most recent release of its dependencies.

Can you put together a new tarball with that change?

Ok, done.

[ohanar]

Actually, this seems to break the build. Will look at it later.

[jhpalmieri]

I guess if you're using an older version of pytz so you're making the tarball manually, then you have to update (or regress) install_order by hand, too. Is that the problem?

[ppurka]

I think if we want to install pytz within a range, we should use the following in util/fetch_deps.py:

                    , 'pytz >=2011n, <=2013b'

[jhpalmieri]

Here's a new version.

---

New commits:

​5fed454	update the Sage notebook to version 0.10.7.3
​aae4f8c	sage-fix-pkg-checksums: appropriately handle uncompressed tarballs

[jhpalmieri]

I'm not sure why this included the changes from #15570, and I don't have time to figure out git well enough to fix it right now...

[jhpalmieri]

New commits:

​d0af1a7

Update sagenb to version 0.10.7.3

[ppurka]

Please check the ​pull request 194 which should fix openid logins. If possible, we should not release yet another broken sagenb.

[ppurka]

I must add that I had no errors with the latest pytz on Linux x64 machine. So, the error seems MacOSX specific.

Edit Sorry, I just now noticed that the error was not in sagenb but in sage.

[ppurka]

I don't understand one thing. I ran the following commands

# Make the sagenb package
~/Installations/sagenb» ./dist.sh
~/Installations/sagenb» cp -a dist sagenb-0.10.8
~/Installations/sagenb» tar cf sagenb-0.10.8.tar sagenb-0.10.8
~/Installations/sagenb» mv sagenb-0.10.8.tar ~/Installations/sage/upstream/.

# Prepare the sagenb package in sage
~/Installations/sage» ./sage --dev checkout --ticket 15569
~/Installations/sage» echo "0.10.8" > build/pkgs/sagenb/package-version.txt
~/Installations/sage» mv upstream/sagenb-0.10.7.2.tar.bz2 /tmp
~/Installations/sage» sage -sh -c sage-fix-pkg-checksums

# Check the diff before committing
~/Installations/sage» git diff
diff --git a/build/pkgs/sagenb/checksums.ini b/build/pkgs/sagenb/checksums.ini
index 7843f0e..2f4e2e6 100644
--- a/build/pkgs/sagenb/checksums.ini
+++ b/build/pkgs/sagenb/checksums.ini
@@ -1,4 +1,4 @@
-tarball=sagenb-VERSION.tar
-sha1=7a822ca573748fcd2034a8cd887b813876ea036d
-md5=04af0903431905d9ac3e65d0e636a040
-cksum=624578127
+tarball=sagenb-VERSION.tar.sagenb-0.10.8.tar
+sha1=17ae39492a1176efbc62006315afb025c4b19d92
+md5=23b448c9d5207bfa017640d32a013b6f
+cksum=2809114274
diff --git a/build/pkgs/sagenb/package-version.txt b/build/pkgs/sagenb/package-version.txt
index e0ee8dd..1a46c7f 100644
--- a/build/pkgs/sagenb/package-version.txt
+++ b/build/pkgs/sagenb/package-version.txt
@@ -1 +1 @@
-0.10.7.3
+0.10.8

Why is the tarball line so weird. Should I fix it by hand?

+tarball=sagenb-VERSION.tar.sagenb-0.10.8.tar

I noticed that the branch in this ticket is very behind develop. Is the above weird tarball naming fixed in develop? If so, I can try to merge develop on to this ticket and then make changes from there.

~/Installations/sage» git diff --stat develop ticket/15569 | tail -n 1
 135 files changed, 3421 insertions(+), 10729 deletions(-)

[ohanar]

You should fix it by hand, there is a bug in the sage-fix-pkg-checksums script that is fixed in #15570, but that won't be in develop until Volker releases the next beta.

[ppurka]

New commits:

​6f6ec5b

Update sagenb version to 0.10.8

[vbraun]

Our build system doesn't accept tar files, it must be .gz or .bz2.

[vbraun]

Rather, the tarball mirror script (/home/sagemath/www2-dev/mirror_upstream.py) for the web page doesn't understand .tar. Harald, do you think that is fixable?

[vbraun]

Harald says that this can be fixed ;-)

[ppurka]

Replying to vbraun:

Harald says that this can be fixed ;-)

Great! It makes little sense to compress the sagenb tarball since it consists of compressed tarballs. :)

[ppurka]

Better wait for 0.10.8.1; see ​https://github.com/sagemath/sagenb/issues/195

[jhpalmieri]

That pull request fixes the problem for me, so I would suggest getting 0.10.8.1 into Sage (and releasing maybe version 6.1.1 of Sage) as soon as possible. Having a broken notebook is bad...

[vbraun]

I've made #15778 for the 0.10.8.1 upgrade. Ideally with a doctest in Sage so that it doesn't happen again...