Re: RFS: matplotlib 0.90.1-3
On Sat, Feb 23, 2008 at 5:08 PM, Ondrej Certik <[EMAIL PROTECTED]> wrote: > > On Sat, Feb 23, 2008 at 4:31 PM, Eike Nicklas <[EMAIL PROTECTED]> wrote: > > Hi Ondrej et al., > > > > > > > > > > Yes, I read that bug. There are more problems with matplotlib - it is > > > not lintian clean, > > > it still uses Numerics and numarray besides numpy (I don't know if > > > this is a feature or a bug), > > > > > > > I think upstream deprecated Numerics and numarray and the latest > > version only uses numpy. > > > > Changelog excerpts: > > > > 2007-06-01 Deprecate Numeric and numarray for use as numerix. > > 2007-06-02 Released 0.90.1 at revision 3352 > > 2007-06-07 Disable build of numarray and Numeric extensions for > >internal MPL use and the numerix layer. > > 2007-07-19 replaced the Python code in numerix/ by a minimal wrapper > >around numpy that explicitly mentions all symbols that need > >to be addressed for further numpification > > [...] > > and only numpy is mentioned in the current README. > > > > Anyway, as a matplotlib user, I am happy that you want to fix the > > current issues, but sadly I currently don't have the time to help with > > that. > > It shouldn't be a big problem and I'll do it, as I also use and need it. We > are actually only waiting for an approval from the matplotlib maintainers. Anyway, this seems it will take quite some time before it gets resolved, so I compiled the fixed packages for i386 and amd64 and put them here to my repository: http://debian.certik.cz/ Ondrej -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: RFS: matplotlib 0.90.1-3
On Sat, Feb 23, 2008 at 4:31 PM, Eike Nicklas <[EMAIL PROTECTED]> wrote: > Hi Ondrej et al., > > > > > > Yes, I read that bug. There are more problems with matplotlib - it is > > not lintian clean, > > it still uses Numerics and numarray besides numpy (I don't know if > > this is a feature or a bug), > > > > I think upstream deprecated Numerics and numarray and the latest > version only uses numpy. > > Changelog excerpts: > > 2007-06-01 Deprecate Numeric and numarray for use as numerix. > 2007-06-02 Released 0.90.1 at revision 3352 > 2007-06-07 Disable build of numarray and Numeric extensions for >internal MPL use and the numerix layer. > 2007-07-19 replaced the Python code in numerix/ by a minimal wrapper >around numpy that explicitly mentions all symbols that need >to be addressed for further numpification > [...] > and only numpy is mentioned in the current README. > > Anyway, as a matplotlib user, I am happy that you want to fix the > current issues, but sadly I currently don't have the time to help with > that. It shouldn't be a big problem and I'll do it, as I also use and need it. We are actually only waiting for an approval from the matplotlib maintainers. Ondrej -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: RFS: matplotlib 0.90.1-3
Hi Ondrej et al., > > Yes, I read that bug. There are more problems with matplotlib - it is > not lintian clean, > it still uses Numerics and numarray besides numpy (I don't know if > this is a feature or a bug), > I think upstream deprecated Numerics and numarray and the latest version only uses numpy. Changelog excerpts: 2007-06-01 Deprecate Numeric and numarray for use as numerix. 2007-06-02 Released 0.90.1 at revision 3352 2007-06-07 Disable build of numarray and Numeric extensions for internal MPL use and the numerix layer. 2007-07-19 replaced the Python code in numerix/ by a minimal wrapper around numpy that explicitly mentions all symbols that need to be addressed for further numpification [...] and only numpy is mentioned in the current README. Anyway, as a matplotlib user, I am happy that you want to fix the current issues, but sadly I currently don't have the time to help with that. Eike pgpoLmGwQJO0k.pgp Description: PGP signature
Re: RFS: matplotlib 0.90.1-3
On Sat, Feb 23, 2008 at 1:22 PM, Eike Nicklas <[EMAIL PROTECTED]> wrote: > Hi, > > > On Sat, 23 Feb 2008 13:07:24 +0100 Ondrej Certik wrote: > > > > > currently, matplotlib doesn't install with numpy in sid, when numpy > > switched to gfortran and it conflicts with matplotlib. > > > > That might also (partly) fix a bug I reassigned to matplotlib: > > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=466818 > > It was initially reported against pondus, which does not explicitely use > python-numpy, but only python-matplotlib (which it correctly depends on) Yes, I read that bug. There are more problems with matplotlib - it is not lintian clean, it still uses Numerics and numarray besides numpy (I don't know if this is a feature or a bug), and a new upstream release is out. To put it short, the package should be comaintained in DPMT and fixed. :) Ondrej -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: RFS: matplotlib 0.90.1-3
Hi, On Sat, 23 Feb 2008 13:07:24 +0100 Ondrej Certik wrote: > > currently, matplotlib doesn't install with numpy in sid, when numpy > switched to gfortran and it conflicts with matplotlib. > That might also (partly) fix a bug I reassigned to matplotlib: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=466818 It was initially reported against pondus, which does not explicitely use python-numpy, but only python-matplotlib (which it correctly depends on) Eike pgppYeU57Siv3.pgp Description: PGP signature
RFS: matplotlib 0.90.1-3
Hi, currently, matplotlib doesn't install with numpy in sid, when numpy switched to gfortran and it conflicts with matplotlib. It seems just a recompile of matplotlib fixes the problem. I imported matplotlib to DPMT svn: svn://svn.debian.org/svn/python-modules/packages/matplotlib/ and committed the necessary change. Unfortunatley, the maintainer and uploaders of matplotlib didn't yet reply to my email and bug: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=467099 and a simple NMU will not fix the problem, as numpy conflicts with python-matplotlib (<< 0.90.1-3). So what should I do to get this fixed soon? Should I upload (I can do that as a DM) a new revision of numpy not conflicting with python-matplotlib? Or can you upload the new matplotlib as I prepared in the svn? The best solution is the one I offered to the maintainers of matplotlib in the bug above - to maintain matplotlib in DPMT. But unless they approve it, I don't think we can do that. Ondrej -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
