The problem is that these dependencies are all in factory, and the
changes in d:l:p get pushed to factory pretty quickly (usually a
matter of hours), so I doubt this would have helped a huge amount..
On Thu, Aug 27, 2015 at 3:59 PM, Robert Schweikert <rjschwei(a)suse.com> wrote:
On 08/27/2015 09:50 AM, Todd Rme wrote:
Short version: please do not accept any submit
requests or make any
other changes to devel:languages:python until the following package
has built at least once: python-jupyter_ipywidgets
For the last 16 days I have been trying to get all of the core Jupyter
packages in devel:languages:python and devel:languages:python3.
Jupyter is a renaming and modularization of the enormously popular
IPython project. This has been very slow going, because they split
the packages into many parts, and these parts have a lot of
dependencies (including quite a few new ones).
These dependencies include many common python packages. That means
that, in OBS, if any of these dependencies is changed in any way (or
any of its dependencies are changeda, and so on), then everything is
rebuilt from scratch. And unfortunately these new packages seem to be
given a very low priority for building, which means it takes a long
time before OBS actually gets around to building them. This means it
is a process of: get a package in, wait 2 days for it to build, get
another package in, wait 2 days for it to build, and so on for weeks.
I have one more package to go: python-jupyter. Once it is in, the
process is complete. For the last 4 days I have been waiting for the
python-jupyter_notebook package to build. It had one dependency left
before it was going to build, and then an submit request python-Cython
was accepted. Since this is a dependency of all of the
jupyter-related packages, everything will need to rebuild now. That
may very well mean another 2 days wait for me.
Until all of its dependencies have built at least once, I can't
properly package python-jupyter. It will outright refuse to build.
Of the two dependencies that have not built yet,
python-jupyter_ipywidgets package is the most "leaf" one. That means
that once it has built once, all of the other dependencies have as
So if everyone could refrain from making any changes of any kind to
devel:languages:python until that package has been built at least
once, I would greatly appreciate it.
Fair enough. However, while d:l:p is a devel project I think it would
have made sense to get the initial setup done in your home project and
then push everything into d:l:p. That way you could have isolated
yourself from changes in d:l:p
Robert Schweikert MAY THE SOURCE BE WITH YOU
Public Cloud Architect LINUX
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org