Skip to content
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

zfec 1.5.4 Windows .whl packages are broken #34

Closed
sajith opened this issue Oct 16, 2020 · 2 comments
Closed

zfec 1.5.4 Windows .whl packages are broken #34

sajith opened this issue Oct 16, 2020 · 2 comments

Comments

@sajith
Copy link
Member

sajith commented Oct 16, 2020

Tahoe-LAFS' Windows CI is not happy with zfec 1.5.4 .whl packages. See tahoe-lafs/tahoe-lafs#862:

zfec==1.5.4
zipp==1.2.0
zope.interface==5.1.2
py27-coverage run-test: commands[1] | tahoe --version
tahoe-lafs: 1.14.0.post1545 [HEAD: eb44944e0d3dc7711e5662ecbeec0873934821ea]
foolscap: 0.13.1
zfec: None [(<type 'exceptions.ImportError'>, 'DLL load failed: %1 is not a valid Win32 application.', ('d:\\a\\tahoe-lafs\\tahoe-lafs\\.tox\\py27-coverage\\lib\\site-packages\\zfec\\__init__.py', 13, '<module>', 'from ._fec import Encoder, Decoder, Error'))]
@sajith
Copy link
Member Author

sajith commented Oct 16, 2020

Tahoe-LAFS CI did not break in the same manner when I tested zfec packages using testpypi: See tahoe-lafs/tahoe-lafs#804.

I have deleted py27+Windows .whl packages of zfec from PyPI in the interim, just so that CI can continue to function.

@exarkun
Copy link
Member

exarkun commented Feb 1, 2022

This was fixed by #37

@exarkun exarkun closed this as completed Feb 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants