pythonPackage shortuuid: init at 0.4.2 #11401
Conversation
|
This is the same as you got @FRidh right? |
|
Yes, exactly. #11320 |
|
also the exact same hashes, although vice versa |
|
Oh boy. Could the CDN or some cache have a broken version? That's what the checksum are for after all. |
|
Anything I can do here? |
|
|
||
| src = pkgs.fetchurl { | ||
| url = "https://pypi.python.org/packages/source/s/shortuuid/${name}.tar.gz"; | ||
| md5 = "142e3ae4e7cd32d41a71deb359db4cfe"; |
There was a problem hiding this comment.
could you use a sha256 instead? It's the preferred hash.
There was a problem hiding this comment.
Generally yes. The md5 is the one which is published on pypi, making it trivial to add. So if it's not a huge problem, I'd stick with that.
|
Looks fine to me. Did you test whether it builds for all interpreters and versions? |
|
I thought I did. But I'm not sure anymore. Will re-check. |
|
Okay, now I did something with git which was probably wrong. :/ |
| }; | ||
|
|
||
|
|
||
| shortuuid = buildPythonPackage rec { |
zagy
force-pushed
the
add/shortuuid
branch
4 times, most recently
from
a2841d8
to
9fa18b1
Compare
|
better now? |
|
@zagy still no :( check travis build or use nox locally to verify... currently it looks like you're using isPy32 which was removed |
Yeah, sorry. My workflow and knowledge aren't good enough, yet. Didn’t even know about nox. Will try that. Thanks for your patience. Dipl. Inform. (FH) Christian Zagrodnick · cz@flyingcircus.io · +49 345 219401 0 |
|
Ping. |
|
@vcunat Hi. Sorry for the late response. There was this state where master wasn't building (the bash thing) and I just couldn't get to the point of testing this reliably. |
pythonPackage shortuuid: init at 0.4.2
No description provided.