On 30/09/17 16:50, Diane Trout wrote:
I am curious if Rebecca is using pandas on a non-intel architecture
though (was wondering how she noticed pandas hadn't built)
No - I found this email thread and checked
https://buildd.debian.org/status/package.php?p=pandas
On Sat, 2017-09-30 at 12:26 +0300, Dmitry Shachnev wrote:
>
>
> > I wonder if it's better to filter sphinxdoc out of the dh line,
> > install
> > sphinx-common, or just always install python3-sphinx?
>
> Adding sphinx-common to B-D and keeping python3-sphinx in B-D-Indep
> is
> probably the easi
Hi Diane,
On Fri, Sep 29, 2017 at 03:55:13PM -0700, Diane Trout wrote:
> Oops.
>
> I thought that it wouldn't try using sphinx when not building doc
> packages. But apparently being listed in "dh --with" counts as being
> used.
Yes, because dh tries to open Sequece/sphinxdoc.pm which is provided
On 29/09/17 23:55, Diane Trout wrote:
On Fri, 2017-09-29 at 22:05 +0100, Rebecca N. Palmer wrote:
statsmodels passed NEW...and FTBFS with
dh: unable to load addon sphinxdoc: Can't locate
Debian/Debhelper/Sequence/sphinxdoc.pm in @INC
That file is in the sphinx-common package, which suggests t
On 29/09/17 23:55, Diane Trout wrote:
I wonder if it's better to filter sphinxdoc out of the dh line, install
sphinx-common, or just always install python3-sphinx?
For local testing of this, use pbuilder --debbuildopts -B
Given earlier messages that we want this working ASAP, always installing
On Fri, 2017-09-29 at 22:05 +0100, Rebecca N. Palmer wrote:
> statsmodels passed NEW...and FTBFS with
>
> dh: unable to load addon sphinxdoc: Can't locate
> Debian/Debhelper/Sequence/sphinxdoc.pm in @INC
> That file is in the sphinx-common package, which suggests that at
> least
> some of the sp
statsmodels passed NEW...and FTBFS with
dh: unable to load addon sphinxdoc: Can't locate
Debian/Debhelper/Sequence/sphinxdoc.pm in @INC
That file is in the sphinx-common package, which suggests that at least
some of the sphinx dependencies need to be Build-Depends and not just
Build-Depends-
Hi again,
On Wed, Sep 27, 2017 at 10:05:15AM +0200, Andreas Tille wrote:
> > I added the readme to README.source with a bit of explanatory text.
> >
> > all changes are pushed.
>
> Seems the updated README.source escaped your push. ;-)
I think I've restored it from the link you posted below and
Dear Diane,
On Wed, Sep 27, 2017 at 12:20:13AM -0700, Diane Trout wrote:
> >
> > I think there is no "right" place to do it - but ftpmaster is used
> > to read README.source in these cases. So why not using it?
> >
>
> I added the readme to README.source with a bit of explanatory text.
>
> al
On Wed, 2017-09-27 at 08:34 +0200, Andreas Tille wrote:
>
> >
> > https://ghic.org/~diane/debian/statsmodels.datasets.README.txt
>
> I think regarding formatting and context its perfectly fine.
>
> > Does it go in README.source? or in upstream/metadata? or something
> > else?
>
> I think ther
Dear Diane,
On Tue, Sep 26, 2017 at 10:47:21PM -0700, Diane Trout wrote:
>
> > Since it is accepted for the R packages and the data are refering
> > to R data I do not see any reason why this should not be accepted.
>
> I traced back from Rdatasets to the original R packages.
>
> Every one of t
Dear Diane,
On Tue, Sep 26, 2017 at 02:49:12PM -0700, Diane Trout wrote:
>
> > While I have not tried to build the current status I wonder what you
> > think about #873512. I'm perfectly fine with your solution to
> > exclude
> > some tests - I just wanted to give a hint that there is a potentia
> Since it is accepted for the R packages and the data are refering
> to R data I do not see any reason why this should not be accepted.
I traced back from Rdatasets to the original R packages.
Every one of the packages are licensed as some combination of GPL-2 and
GPL-3
However it's likely tha
> While I have not tried to build the current status I wonder what you
> think about #873512. I'm perfectly fine with your solution to
> exclude
> some tests - I just wanted to give a hint that there is a potential
> upstream patch.
I think I looked at the upstream commits that fixed it,
https:
Hi Diane,
On Tue, Sep 26, 2017 at 11:36:17AM -0700, Diane Trout wrote:
> > BTW, I'd love if you would merge your work to master branch. I'm a
> > bit
> > confused by the amount of branches and lost track which one to look
> > at.
>
> I verified which was which and deleted the obsolete branch.
>
Thanks for digging into this and sorry I have missed that. I typically
add export http*_proxy to prevent any network interactions but I guess
didn't get that far with statsmodels.
FWIW, for dipy package I now ask upstream to provide me e.g.
dipy_0.12.0.orig-doc-examples.tar.gz
where there a
> > Below is what I've found so far, (before getting tired of licensing
> > issues)
> >
> > Any thoughts about how to handle this?
>
> I wonder how this was dealt with before? If that much data sets were
> needed to build the docs, how did the doc generation process worked
> before?
Perhaps th
On Mon, Sep 25, 2017 at 09:36:43PM -0700, Diane Trout wrote:
> > > * Some of the doc pages call get_rdataset, and there's no network
> > > access in the builder so those calls fail. (ugliest error)
> >
> > Can you pre-fetch the data and provide it in debian/datasets?
>
> I made the changes and ca
On Mon, 2017-09-25 at 09:44 +0200, Andreas Tille wrote:
> Hi Diane,
>
> On Sun, Sep 24, 2017 at 11:45:43PM -0700, Diane Trout wrote:
> > The remaining issues are:
> >
> > * Some of the doc pages call get_rdataset, and there's no network
> > access in the builder so those calls fail. (ugliest erro
Hi Diane,
On Mon, Sep 25, 2017 at 10:38:00AM -0700, Diane Trout wrote:
>
> I'm planning on ignoring it for now.
Sounds sensible. Thanks a lot for your work on this
Andreas.
--
http://fam-tille.de
On Mon, 2017-09-25 at 09:44 +0200, Andreas Tille wrote:
>
> > * Some of the doc pages call get_rdataset, and there's no network
> > access in the builder so those calls fail. (ugliest error)
>
> Can you pre-fetch the data and provide it in debian/datasets?
Looks like it'll take a bit of patching
> > > I made larger changes to statsmodels, by using pybuild instead of the
> > > previous multiple targets in debian/rules.
> > you can simplify it even further by using pybuild's --ext-dest-dir:
> > (I didn't test as this branch FTBFS for me)
> how recent is that feature?
it's available since th
Hi Diane,
On Sun, Sep 24, 2017 at 11:45:43PM -0700, Diane Trout wrote:
> The remaining issues are:
>
> * Some of the doc pages call get_rdataset, and there's no network
> access in the builder so those calls fail. (ugliest error)
Can you pre-fetch the data and provide it in debian/datasets?
> *
On Sun, 2017-09-24 at 11:24 -0700, Diane Trout wrote:
> Status with statsmodels almost done
>
> Trying to deal with jquery.
>
> leaving command
>
> -rm ./build/html/_static/jquery.js
>
> causes a build failure now.
> leaving it in causes a lintain privacy error.
I found the problem, I st
If the jquery.js file is deleted something later errors out. My guess is it's
listed in one of the .install files but I haven't looked yet
On September 24, 2017 3:51:30 PM PDT, Yaroslav Halchenko
wrote:
>
>On Sun, 24 Sep 2017, Andreas Tille wrote:
>
>> On Sun, Sep 24, 2017 at 11:24:10AM -0700,
On Sun, 24 Sep 2017, Andreas Tille wrote:
> Hi Yaroslav,
> On Sat, Sep 23, 2017 at 10:00:35AM -0400, Yaroslav Halchenko wrote:
> > > I would prefer to move pandas to Debian Science or Debian Python. I
> > > fail to see the specific use in NeuroDebian field.
> > I ould repeat that I don't mind
On Sun, 24 Sep 2017, Andreas Tille wrote:
> On Sun, Sep 24, 2017 at 11:24:10AM -0700, Diane Trout wrote:
> > Status with statsmodels almost done
> > Trying to deal with jquery.
> > leaving command
> > -rm ./build/html/_static/jquery.js
> > causes a build failure now.
> Without checking t
On Sun, Sep 24, 2017 at 11:24:10AM -0700, Diane Trout wrote:
> Status with statsmodels almost done
>
> Trying to deal with jquery.
>
> leaving command
>
> -rm ./build/html/_static/jquery.js
>
> causes a build failure now.
Without checking the source: I'm usually doing something like
ov
Status with statsmodels almost done
Trying to deal with jquery.
leaving command
-rm ./build/html/_static/jquery.js
causes a build failure now.
leaving it in causes a lintain privacy error.
there's also lintain warnings about a missing hardening flag, and no
doc-base registration.
At s
Hi Yaroslav,
On Sat, Sep 23, 2017 at 10:00:35AM -0400, Yaroslav Halchenko wrote:
>
> > I would prefer to move pandas to Debian Science or Debian Python. I
> > fail to see the specific use in NeuroDebian field.
>
> I ould repeat that I don't mind having it moved under -science or
> -python teams
On Fri, 22 Sep 2017, Andreas Tille wrote:
> > diff -Nru pandas-0.20.3/debian/changelog pandas-0.20.3/debian/changelog
> > --- pandas-0.20.3/debian/changelog 2017-07-10 20:00:59.0 -0400
> > +++ pandas-0.20.3/debian/changelog 2017-09-21 16:11:29.0 -0400
> > @@ -1,3 +1,14 @@
On Fri, 22 Sep 2017, Piotr Ożarowski wrote:
> [Diane Trout, 2017-09-21]
> > I made larger changes to statsmodels, by using pybuild instead of the
> > previous multiple targets in debian/rules.
> you can simplify it even further by using pybuild's --ext-dest-dir:
> (I didn't test as this branch F
On 22/09/17 20:32, Diane Trout wrote:
On Fri, 2017-09-22 at 10:57 +0200, Piotr Ożarowski wrote:
[Diane Trout, 2017-09-21]
I made larger changes to statsmodels, by using pybuild instead of
the
previous multiple targets in debian/rules.
you can simplify it even further by using pybuild's --ext-
On Fri, 2017-09-22 at 10:57 +0200, Piotr Ożarowski wrote:
> [Diane Trout, 2017-09-21]
> > I made larger changes to statsmodels, by using pybuild instead of
> > the
> > previous multiple targets in debian/rules.
>
> you can simplify it even further by using pybuild's --ext-dest-dir:
> (I didn't tes
[Diane Trout, 2017-09-21]
> I made larger changes to statsmodels, by using pybuild instead of the
> previous multiple targets in debian/rules.
you can simplify it even further by using pybuild's --ext-dest-dir:
(I didn't test as this branch FTBFS for me)
diff --git a/debian/rules b/debian/rules
i
Hi Yaroslav,
On Thu, Sep 21, 2017 at 10:24:53PM -0400, Yaroslav Halchenko wrote:
> On Thu, 21 Sep 2017, Diane Trout wrote:
>
> > On Thu, 2017-09-21 at 17:56 -0400, Yaroslav Halchenko wrote:
> > > If you could allow to review would be great.
> > > Thanks for all the work.
> > > I was btw also tryi
I managed to merge the more important doc changes.
I have a patch to switch doc building to using Python 3 components, as
there's a goal of removing the Python 2 components at some point.
The there's the patch for the nodoc/nocheck build profile, as well as
adding a bunch of other dependencies fo
On Thu, 21 Sep 2017, Diane Trout wrote:
> On Thu, 2017-09-21 at 17:56 -0400, Yaroslav Halchenko wrote:
> > If you could allow to review would be great.
> > Thanks for all the work.
> > I was btw also trying to build with the patch you shared yesterday
> Once I have all the changes for pandas wou
If you could allow to review would be great.
Thanks for all the work.
I was btw also trying to build with the patch you shared yesterday
On September 21, 2017 5:48:58 PM EDT, Diane Trout wrote:
>
>> If my poor opinion counts: For the moment we should run those tests
>> in
>> the build process th
On Thu, 2017-09-21 at 17:56 -0400, Yaroslav Halchenko wrote:
> If you could allow to review would be great.
> Thanks for all the work.
> I was btw also trying to build with the patch you shared yesterday
Once I have all the changes for pandas would you like me to put them on
a branch on alioth? Or
> If my poor opinion counts: For the moment we should run those tests
> in
> the build process than can be easily be run. Everything else should
> probably be sorted out later (in autopkgtest or another later upload
> if
> somebody has a clue how we can solve the circular depenendecies).
>
> We
On 21/09/17 15:22, Andreas Tille wrote:
We somehow need to get some working spatstats to continue with other
packages.
I second Andreas' opinion. In principle, we'd want all tests to run at
build and integration times and we might achieve that at some point
during the Buster cycle.
Right no
Hi,
On Mon, Sep 18, 2017 at 05:48:48PM +1000, Stuart Prescott wrote:
> On Sunday, 17 September 2017 22:14:18 AEST Diane Trout wrote:
> > I just did it that way because it was the least disruptive change I
> > could make that would let me build and test the package.
>
> Sure, that's entirely sensi
> the biggest downside with this approach is that you *completely* skip
> any
> testing on other architectures than amd64. Is that what you really
> want? Dear
> porters, have fun where to search for bugs in packages without
> testsuites!
Ok you convinced me. dh_auto_tests stay.
Is there anythi
On 18.09.2017 19:24, Gordon Ball wrote:
> On 18/09/17 09:48, Stuart Prescott wrote:
>> Hi Diane,
>>
>> On Sunday, 17 September 2017 22:14:18 AEST Diane Trout wrote:
>>> I just did it that way because it was the least disruptive change I
>>> could make that would let me build and test the package.
>
On 18/09/17 09:48, Stuart Prescott wrote:
> Hi Diane,
>
> On Sunday, 17 September 2017 22:14:18 AEST Diane Trout wrote:
>> I just did it that way because it was the least disruptive change I
>> could make that would let me build and test the package.
>
> Sure, that's entirely sensible.
>
>> In m
Hi Diane,
On Sunday, 17 September 2017 22:14:18 AEST Diane Trout wrote:
> I just did it that way because it was the least disruptive change I
> could make that would let me build and test the package.
Sure, that's entirely sensible.
> In my experience I'm much more likely to to notice a build ti
> On Saturday, 16 September 2017 14:18:10 AEST Diane Trout wrote:
> > My solution was to use build-profiles to flag the test dependency
> > with
> > !nocheck
>
> this is, of course, a very elegant solution and exactly what build
> profiles
> are for...
>
> I wonder though, is it really sustaina
Hi Diane & other science+python people,
Thanks for spending time on pandas and statsmodels. They are two very valuable
but very painful packages to work on.
I've not looked at pandas and statsmodels packages carefully beyond "why
hasn't pandas migrated this time!?" investigations but the circul
On 16.09.2017 22:59, Yuri D'Elia wrote:
> On Sat, Sep 16 2017, Diane Trout wrote:
>> python3-pandas: Pandas is not installable
>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875723
>
> I would have expected the rebuild of python packages affected by the
> fpectl extension with a transition,
On Sat, 2017-09-16 at 22:59 +0200, Yuri D'Elia wrote:
> On Sat, Sep 16 2017, Diane Trout wrote:
> > python3-pandas: Pandas is not installable
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875723
>
> I would have expected the rebuild of python packages affected by the
> fpectl extension wit
On Sat, Sep 16 2017, Diane Trout wrote:
> python3-pandas: Pandas is not installable
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875723
I would have expected the rebuild of python packages affected by the
fpectl extension with a transition, but it doesn't seem to be the case?
https://bugs.
52 matches
Mail list logo
