#10176: ImportError: No module named sagenb on openSUSE
------------------------------+---------------------------------------------
Reporter: mpatel | Owner: jason, was
Type: defect | Status: needs_work
Priority: blocker | Milestone: sage-4.6.1
Component: notebook | Keywords:
Author: Leif Leonhardy | Upstream: N/A
Reviewer: | Merged:
Work_issues: |
------------------------------+---------------------------------------------
Comment(by leif):
Replying to [comment:57 jdemeyer]:
> Leif: my patch is the same as yours, expect that it's a `hg` patch and
that it doesn't change the version number.
My Mercurial patch(es) contain a lot of commit messages with notes; the
diff was not intended to get merged.
Replying to [comment:55 jdemeyer]:
> Note that (as release manager) I don't care about the spkg, only about
the diffs.
At the moment the whole purpose of the spkg is to aid debugging the
problems mentioned on sage-devel; nobody opened a ticket I asked for, or
replied on that thread yet.
In case the spkg helps, I suggest opening a new ticket with a description
of the newly encountered problems, then "clean" Mercurial patches, and
with just a back-reference to this ticket since the two patches from here
will (most probably) be also included there.
[Error] messages given by my current spkg may lead to further work. I
can't do that until I get some feedback and know what's really going
wrong.
Testing upgrading ''with the current buildbot / scripts'' seems less
useful; cf. sage-release.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/10176#comment:60>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en.
