Re: scipy 1.2.0 and joining DPMT
On Sun, Mar 17, 2019 at 02:50:32AM +0800, Drew Parsons wrote: > On 2019-03-17 02:48, Drew Parsons wrote: > > > > Hi Dmitry, the Tools section still refers to git-dpm. > > Ah, that would be MR-5, still in discussion. Yes. I will give the original submitter (Yao Wei) some time to fix this, but if he does not respond, I will merge it with my suggestion applied. (I hope Ondřej does not mind.) -- Dmitry Shachnev signature.asc Description: PGP signature
Re: scipy 1.2.0 and joining DPMT
On 2019-03-17 02:48, Drew Parsons wrote: Hi Dmitry, the Tools section still refers to git-dpm. Ah, that would be MR-5, still in discussion.
Re: scipy 1.2.0 and joining DPMT
On 2019-03-17 02:39, Dmitry Shachnev wrote: On Fri, Mar 15, 2019 at 02:34:26PM +0100, Ondrej Novy wrote: > https://salsa.debian.org/python-team/tools/python-modules/merge_requests/4 let's merge it without "Configurations" section now, please. Done! I will now also review the follow-up merge requests. Hi Dmitry, the Tools section still refers to git-dpm. Drew.
Re: scipy 1.2.0 and joining DPMT
On Fri, Mar 15, 2019 at 02:34:26PM +0100, Ondrej Novy wrote: > > https://salsa.debian.org/python-team/tools/python-modules/merge_requests/4 > > let's merge it without "Configurations" section now, please. Done! I will now also review the follow-up merge requests. -- Dmitry Shachnev signature.asc Description: PGP signature
Re: unblock request: python-scipy/1.1.0-4 skimage/0.14.2-2: autopkgtest passes (Re: bug#919929)
On 2019-03-16 22:07, Paul Gevers wrote: On 16-03-2019 13:48, Drew Parsons wrote: Is there enough will to add more scipy patches for the buster release to reduce the remaining DeprecationWarnings? (they don't break tests, they're just annoying) Or should we just let it go at this point and let them get cleared in future versions?) I'd let it be for now. No problem, will do (more precisely, not do). That being the case, in the interests of making a stable release that passes it own tests, I'd like to request an unblock for python-scipy/1.1.0-4 (together with skimage/0.14.2-2) skimage was already unblocked. I'll unblock python-scipy as well. Thanks Paul. Looks like we'll be able to close Bug#919929 once python-scipy/1.1.0-4 is settled into testing. Drew
Re: unblock request: python-scipy/1.1.0-4 skimage/0.14.2-2: autopkgtest passes (Re: bug#919929)
Hi Drew, On 16-03-2019 13:48, Drew Parsons wrote: >> The numpy.sparse tests pass with this patch, and most of the matrix >> PendingDeprecationWarnings are gone (the upstream patch missed >> integrate/tests/test_ivp.py, but the remaining warnings are few enough >> to not need to worry about). > > Well, turns out the other warnings worried Aurelien enough to file > Bug#924396. > > Is there enough will to add more scipy patches for the buster release to > reduce the remaining DeprecationWarnings? (they don't break tests, > they're just annoying) > Or should we just let it go at this point and let them get cleared in > future versions?) I'd let it be for now. > That being the case, in the interests of making a stable release that > passes it own tests, I'd like to request an unblock for > python-scipy/1.1.0-4 (together with skimage/0.14.2-2) skimage was already unblocked. I'll unblock python-scipy as well. Paul signature.asc Description: OpenPGP digital signature
unblock request: python-scipy/1.1.0-4 skimage/0.14.2-2: autopkgtest passes (Re: bug#919929)
On 2019-03-11 14:39, Drew Parsons wrote: I've adapted the 3 patches and pushed to salsa, matrix_API_614847c5.patch matrix_API_more_e0cfa29e2.patch matrix_API_filter_check_87e48c3c5.patch https://salsa.debian.org/python-team/modules/python-scipy/tree/master/debian/patches ... The numpy.sparse tests pass with this patch, and most of the matrix PendingDeprecationWarnings are gone (the upstream patch missed integrate/tests/test_ivp.py, but the remaining warnings are few enough to not need to worry about). Well, turns out the other warnings worried Aurelien enough to file Bug#924396. Is there enough will to add more scipy patches for the buster release to reduce the remaining DeprecationWarnings? (they don't break tests, they're just annoying) Or should we just let it go at this point and let them get cleared in future versions?) ... With these patches, the sparse matrix tests pass. There remain three errors unrelated to sparse matrix: spatial/tests/test__plotutils.py::TestPlotting::test_delaunay FAILED [ 76%] spatial/tests/test__plotutils.py::TestPlotting::test_voronoi FAILED [ 76%] spatial/tests/test__plotutils.py::TestPlotting::test_convex_hull FAILED [ 76%] ,,, > with suppress_warnings as sup: E AttributeError: __enter__ Apart from that, I'm happy to upload the sparse matrix patches once the s390x update reaches testing. Those errors must have been local to me. scipy 1.1.0-4 now passes debci tests cleanly. That being the case, in the interests of making a stable release that passes it own tests, I'd like to request an unblock for python-scipy/1.1.0-4 (together with skimage/0.14.2-2) Drew
Re: scipy 1.2.0 and joining DPMT
On 2019-03-15 21:15, Ondrej Novy wrote: Hi, Thanks Ondrej, read and accepted. welcome :) Thanks :) I fixed scipy's test failures :) The policy on Maintainer/Upload fields is interesting. I've installed git-dpm, likely it will be useful for my other packages. please don't use git-dpm in DPMT :) Yeah, I got the update :) quilt / dpkg-source --commit will do. Drew