From: Christopher Schwan <cschwan@students.uni-mainz.de>
To: <gentoo-science@lists.gentoo.org>
Subject: Re: [gentoo-science] [sage-on-gentoo] 4.6.1.alpha2 and absence
Date: Sun, 21 Nov 2010 11:13:55 +0100 [thread overview]
Message-ID: <201011211113.55461.cschwan@students.uni-mainz.de> (raw)
In-Reply-To: <201011202313.49091.f.r.bissey@massey.ac.nz>
Hi,
On Saturday 20 November 2010 11:13:48 François Bissey wrote:
> Hi all,
>
> After a false start earlier this week it appears that sage-4.6.1.alpha2
> is finally released. The previous "release" was aborted after I reported
> tests results from sage-on-gentoo to the sage-devel mailing list.
> We have an impact upstream. Thanks to Steve Trogdon for running the test
> in question against my ebuilds.
>
> There are many things of interest planned for 4.6.1:
> * numpy-1.5/scipy-0.8 - we already have this but now it is official
> upstream * maxima-5.22.1 - again we already have this but upstream is
> getting there * cvxopt-1.1.3 - see above
> * sphinx-1.0.4 - is stable on gentoo but broke a test in sage, with
> upstream upgrading the test is fixed.
>
> While we have a lot of this already, the main point is that the number of
> patches we are applying is actually going down in this release.
> And if I had been a bit more attentive working with upstream it may have
> been going down further.
>
> We have a handle on all the issues reported except for two. One about gap
> from which we haven't heard in ages. Some changes we have made months
> ago would have reduced the impact of this problem dramatically anyway.
> A report by Vladimir that sage doesn't work on his system. This is more
> worrying but we are unable to reproduce it. I am hoping it is related to
> some tickets upstream on pynac. If it is, Vladimir's problem could be
> solved in 4.6.1 or 4.6.2.
>
>
> ------------------------
>
> Other matters. Some of you already know this. I am relocating on the 1st of
> December and will be probably out of action for most of December.
> Christopher will be the sole person in charge of the overlay during that
> time. I am sure he will have the support of the usual suspects.
Lets hope so ;) But yes, I will take care for the overlay. Since I am very
busy this lecture period expect me to be active on weekends.
>
> I am not sure what his plans are regarding making alpha releases.
I do not plan to make alpha releases - again, lack of time :-/
> It was
> quite good to do some for 4.6 as there was a lot of changes being put in
> place upstream. 4.6.1 is more interesting than I thought it would be, so
> there is some value in doing some alpha releases.
Definitely - 4.6 and 4.6.1 introduced a lot of new packages.
> I think we are in good shape for 4.6.1 as it is unlikely there will be
> another disruptive change at this stage.
>
>
> Oh yes, I will lose my ppc machine :( - I will get some more at my new work
> but they won't be running gentoo (although I am already thinking of trying
> to run prefix on them) they are running aix.
>
> Francois
prev parent reply other threads:[~2010-11-21 10:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-20 10:13 [gentoo-science] [sage-on-gentoo] 4.6.1.alpha2 and absence François Bissey
2010-11-21 10:13 ` Christopher Schwan [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201011211113.55461.cschwan@students.uni-mainz.de \
--to=cschwan@students.uni-mainz.de \
--cc=gentoo-science@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox