Defective conda package in the main channel: where to raise a ticket?

[Pav A]

werkzeug has lost debug/shared folder between 0.11.8 and 0.11.9.

Compare https://repo.continuum.io/pkgs/free/win-32/werkzeug-0.11.8-py35_0.tar.bz2
to https://repo.continuum.io/pkgs/free/win-32/werkzeug-0.11.9-py35_0.tar.bz2

Side effect: unable to debug flask apps using 0.11.9 or newer.

I'm able to create a valid conda package locally.

Where can I create an issue or a pull request or upload a corrected package?

[Alexey Strokach]

Try installing werkzeug from conda-forge. If the conda-forge package does not work either, file an issue on the werkzeug-feedstock repo.

​

--
You received this message because you are subscribed to the Google Groups "conda - Public" group.
To unsubscribe from this group and stop receiving emails from it, send an email to conda+un...@continuum.io.
To post to this group, send email to co...@continuum.io.
Visit this group at https://groups.google.com/a/continuum.io/group/conda/.
To view this discussion on the web visit https://groups.google.com/a/continuum.io/d/msgid/conda/d4ca23f4-924d-4979-911b-9165fb4b26e7%40continuum.io.
For more options, visit https://groups.google.com/a/continuum.io/d/optout.

[Antoine Pitrou]

Hi,

On Tue, 22 Nov 2016 02:19:44 -0800 (PST)
Pav A <rootsum...@gmail.com> wrote:
>
> Where can I create an issue or a pull request or upload a corrected package?

Issues with official conda packages should be filed
at https://github.com/ContinuumIO/anaconda-issues/issues

Regards

Antoine.

[Ilan Schnell]

The latest available werkzeug version is 0.11.11.  Does the problem also exist with this versions?  Or is ti just 0.11.9?

We haven't changed the way we build werkzeug, so I'm wondering if this is an upstream werkzeug change which flask is breaking.  Maybe the fix needs to be that flask requires `werkzeug >=0.7,<=0.11.8`?

--
You received this message because you are subscribed to the Google Groups "conda - Public" group.
To unsubscribe from this group and stop receiving emails from it, send an email to conda+un...@continuum.io.
To post to this group, send email to co...@continuum.io.
Visit this group at https://groups.google.com/a/continuum.io/group/conda/.

To view this discussion on the web visit https://groups.google.com/a/continuum.io/d/msgid/conda/20161122180648.0fde5134%40fsol.

[Pav A]

* 0.11.11 conda package is also defective. 

* No upstream changes in werkzeug. 

* werkzeug 0.11.11 wheel is correct on pypi: https://pypi.python.org/packages/a9/5e/41f791a3f380ec50f2c4c3ef1399d9ffce6b4fe9a7f305222f014cf4fe83/Werkzeug-0.11.11-py2.py3-none-any.whl#md5=c63a21eedce9504d223ed89358c4bdc9

One can build a correct conda package from that pip wheel using conda convert.

What's the process for building and uploading conda tarballs to https://repo.continuum.io/pkgs/free/win-32 ?

 

To view this discussion on the web visit https://groups.google.com/a/continuum.io/d/msgid/conda/CAMJkBYBhCqFSWLFKX_ZLNNcG-kh20wuT-JM0RsvsyNH9K-K5PA%40mail.gmail.com.

[Ilan Schnell]

The problem is that Werkzeug needs to be build using setuptools, even though setup.py indicated that this build dependency is optional.  I've fixed the problem by adding setuptools as a build dependency, and also added a test for the existence of a file from the debug/shared folder, see https://github.com/ContinuumIO/anaconda-recipes/blob/master/werkzeug/run_test.py#L12

Anyway, the fixed Werkzeug 0.11.11 (build 1) is now available for all platforms.

- Ilan

[Pav A]

👍