This will finally make the builds reproducible. Python 3.6 stored
timestamps in the .pyc files but Python 3.7 implements PEP 552 [0].
[0]: https://www.python.org/dev/peps/pep-0552/
Changelog:
https://cryptography.io/en/latest/changelog/#v2-5
Important changes:
- BACKWARDS INCOMPATIBLE: U-label strings were deprecated in version
2.1, but this version removes the default idna dependency as well.
- BACKWARDS INCOMPATIBLE: The minimum supported PyPy version is now 5.4.
Due to stdenv changes the binaries where broken during the fixup phase
(while stripping all binaries). The current solution isn't optimal but
there must not be any cyclic dependencies on $out.
The current repository (debian/signing-party) was actually the old one
(last activity 4 months ago) and signing-party-team/signing-party is the
new upstream repository.
The Ed25519 test was failing inside of the sandbox because /dev/tty is
not available:
### generating ed25519 key for testuser...
gpg: cannot open '/dev/tty': No such device or address
FAILED!
Unfortunately the tarball was modified for the official release and
"nix-store -r --check $(nix-instantiate -A scons.src)" did not catch
this (not sure why ATM).
Thanks @pbogdan for noticing this :)
This also covers "androidStudioPackages.preview".
I believe that the name is confusing (is it from the beta or dev/canary
channel?) and with this error message it should be obvious how to update
ones configuration.
The old name "android-studio-preview" was a bit misleading while
"android-studio-beta" should clearly reflect that this is from the beta
channel. I hope that this does not break any workflows but since
"android-studio-preview" was most likely not called from any scripts the
risk should be low (also: most people probably use the stable version
anyway).
Changelog:
https://cryptography.io/en/latest/changelog/#v2-4-2
Important changes:
- BACKWARDS INCOMPATIBLE: Dropped support for LibreSSL 2.4.x.
- Deprecated OpenSSL 1.0.1 support. OpenSSL 1.0.1 is no longer supported
by the OpenSSL project. At this time there is no time table for
dropping support, however we strongly encourage all users to upgrade
or install cryptography from a wheel.
scons: 3.0.2 -> 3.0.3
"This release should be used instead of 3.0.2. This release fixes
several issues. This release supports Python versions 2.7.* as well as
3.5+." [0]
Details can be found in the changelog [1].
"NOTE: 3.0.2 release was dropped because there was a packaging bug. Please
consider all 3.0.2 content."
There where no regressions and no deprecations in this release (at least it does
not break any builds in nixpkgs).
[0]: https://scons.org/scons-303-is-available.html
[1]: https://raw.githubusercontent.com/SConsProject/scons/rel_3.0.3/src/CHANGES.txt
"Update to iproute2 utility to support new features in Linux 4.20.
This release is mostly small fixes but there are several changes
related to ip neigh support for offloaded entries." [0]
File changes:
+share/man/man8/tc-taprio.8.gz
nix path-info -S:
4.19.0 42681224
4.20.0 42714224
[0]: https://www.spinics.net/lists/netdev/msg543288.html
A few packages broke due to the SCons upgrade (they depended on
deprecated options that got removed), I've kept them on version 3.0.1
for now. The rest of the rebuilds seems fine (the failing ones where
already in a broken state before this change).
The package doesn't exist anymore (even the deprecation notice is gone
[0]) and the build is currently broken:
Collecting google-apputils==0.4.1 (from gcutil==1.16.1)
Could not find a version that satisfies the requirement
google-apputils==0.4.1 (from gcutil==1.16.1) (from versions: )
No matching distribution found for google-apputils==0.4.1 (from
gcutil==1.16.1)
[0]: https://download.huihoo.com/google/gdgdevkit/DVD1/developers.google.com/compute/docs/gcutil.1.html
> "Warning: gcutil is deprecated. We encourage you to transition to
> using gcloud compute ."
The build was broken [0] due to an incorrect dependency (not sure why it
was working before, maybe the libraries where compatible).
[0]: https://hydra.nixos.org/build/86085666
Unfortunately this package was unmaintained for years, which is why I
had to change quite some stuff (it's probably still not perfect) and set
myself as maintainer (replacing the existing ones, which maintained it
until version 1.9).
Michael Weiss