-
-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
noarch/black-19.10b0-py_2.tar.bz2 contains files from other packages #13
Comments
Attached is a screenshot of the black package on conda-forge. It seems that a new version of the noarch package has been uploaded months after the other 19.10b0 packages are uploaded. It is uploaded by cf-staging instead of conda-forge. This all looks a bit fishy. |
* add blackd recipe output * MNT: Re-rendered with conda-build 3.19.2, conda-smithy 3.7.3, and conda-forge-pinning 2020.06.24.16.31.11 * fix: test section indent * fix: indent * fix: put back noarch * MNT: Re-rendered with conda-build 3.19.2, conda-smithy 3.7.3, and conda-forge-pinning 2020.06.24.16.31.11 * try using a metapackage * remove pin? * MNT: Re-rendered with conda-build 3.19.2, conda-smithy 3.7.3, and conda-forge-pinning 2020.06.24.16.31.11 * remove jinja template python * try moving noarch section * nope, try something else * MNT: Re-rendered with conda-build 3.19.2, conda-smithy 3.7.3, and conda-forge-pinning 2020.06.24.16.31.11 * add pin version info * fix pin Co-authored-by: Uwe L. Korn <[email protected]> * remove dup output Co-authored-by: Uwe L. Korn <[email protected]> * fix noarch * MNT: Re-rendered with conda-build 3.19.2, conda-smithy 3.7.3, and conda-forge-pinning 2020.06.24.16.31.11 * try moving entry point * put back noarch in blackd * make blackd available in black * separate build script * MNT: Re-rendered with conda-build 3.19.2, conda-smithy 3.7.4, and conda-forge-pinning 2020.07.19.19.30.49 * no build in outputs * try moving entry points to general build section * MNT: Re-rendered with conda-build 3.19.2, conda-smithy 3.7.4, and conda-forge-pinning 2020.07.19.19.30.49 * add back noarch in output * MNT: Re-rendered with conda-build 3.19.2, conda-smithy 3.7.4, and conda-forge-pinning 2020.07.19.19.30.49 * try this * MNT: Re-rendered with conda-build 3.19.2, conda-smithy 3.7.4, and conda-forge-pinning 2020.07.19.19.30.49 * back * check tests Co-authored-by: Carlo Dri <[email protected]> Co-authored-by: conda-forge-linter <[email protected]> Co-authored-by: Uwe L. Korn <[email protected]>
Is it possible to install the previous version of this package? I'm installing black in our CI environment, which is now broken, so I'd like to install the previous build. Earlier it installed However, the file corresponding to build 0 does not seem to exist: https://anaconda.org/conda-forge/black/19.10b0/download/noarch/black-19.10b0-py_0.tar.bz2 So I don't know how to get the previous build back. |
I'm trying to learn what is going on. First off, it is not really clear what the reason behind #12 change is. It just says "add blackd recipe output". My guess is that the idea is to split the package into just 'black' and 'blackd'. This is corroborated by the availability of the blackd package. However, there is almost nothing in
This makes sense, because there is no The |
Ah, the idea was to have separate build steps, but instead the build script has been used to specify the files to include in the output. And it is okay that the blackd package is empty, as it is a metapackage that only has the dependencies for blackd. |
@carlodri can you take care of this? |
@hugobuddel yes, you are right, things are definitely wrong in there, sorry for messing up your CI... The goal was to have a metapackage for @xhochy yes, I can try, and I might need your help there! 🙏 |
actually, I have just tested on my windows machine that in a fresh environment the installation of |
probably the presence of spurious files in the archive comes from the fact that the |
you can pin to the latest good package temporarily with
or whatever python version you need |
@carlodri NP for breaking my build! I'm using this as an opportunity to learn:
My direct problem is solved by pinning the version to |
because it includes "vendored" packages (such as attr, regex and click) (it has been fixed in build number 3) See conda-forge/black-feedstock#13
because it includes "vendored" packages (such as attr, regex and click) (it has been fixed in build number 3) See conda-forge/black-feedstock#13
because it includes "vendored" packages (such as attr, regex and click) (it has been fixed in build number 3) See conda-forge/black-feedstock#13
There are many files in
noarch/black-19.10b0-py_2.tar.bz2
that perhaps should not be there because they are from different packages:As a result, conda complains:
I can submit more details about my specific environment if this is useful.
The text was updated successfully, but these errors were encountered: