Age | Commit message (Collapse) | Author | Files | Lines |
|
In preparation for the deprecation of `stdenv.isX`.
These shorthands are not conducive to cross-compilation because they
hide the platforms.
Darwin might get cross-compilation for which the continued usage of `stdenv.isDarwin` will get in the way
One example of why this is bad and especially affects compiler packages
https://www.github.com/NixOS/nixpkgs/pull/343059
There are too many files to go through manually but a treewide should
get users thinking when they see a `hostPlatform.isX` in a place where it
doesn't make sense.
```
fd --type f "\.nix" | xargs sd --fixed-strings "stdenv.is" "stdenv.hostPlatform.is"
fd --type f "\.nix" | xargs sd --fixed-strings "stdenv'.is" "stdenv'.hostPlatform.is"
fd --type f "\.nix" | xargs sd --fixed-strings "clangStdenv.is" "clangStdenv.hostPlatform.is"
fd --type f "\.nix" | xargs sd --fixed-strings "gccStdenv.is" "gccStdenv.hostPlatform.is"
fd --type f "\.nix" | xargs sd --fixed-strings "stdenvNoCC.is" "stdenvNoCC.hostPlatform.is"
fd --type f "\.nix" | xargs sd --fixed-strings "inherit (stdenv) is" "inherit (stdenv.hostPlatform) is"
fd --type f "\.nix" | xargs sd --fixed-strings "buildStdenv.is" "buildStdenv.hostPlatform.is"
fd --type f "\.nix" | xargs sd --fixed-strings "effectiveStdenv.is" "effectiveStdenv.hostPlatform.is"
fd --type f "\.nix" | xargs sd --fixed-strings "originalStdenv.is" "originalStdenv.hostPlatform.is"
```
|
|
|
|
Diff: https://github.com/google/zx/compare/8.1.7...8.1.8
Changelog: https://github.com/google/zx/releases/tag/8.1.8
|
|
|
|
|
|
|
|
|
|
Diff: https://github.com/tavianator/bfs/compare/3.1.3...4.0.2
Signed-off-by: Muhammad Falak R Wani <falakreyaz@gmail.com>
|
|
|
|
Diff: https://github.com/google/zx/compare/8.1.6...8.1.7
Changelog: https://github.com/google/zx/releases/tag/8.1.7
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Diff: https://github.com/google/zx/compare/8.1.5...8.1.6
Changelog: https://github.com/google/zx/releases/tag/8.1.6
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Signed-off-by: Felix Singer <felixsinger@posteo.net>
|
|
|
|
Current versions of Intel AMT/vPro only support connecting over SSL, but
our current amtterm version isn't built with SSL support.
Set the `USE_OPENSSL=1` makeFlag and add openssl and pkg-config.
It adds an additional `-C cacert` parameter, which needs to point to
a previously downloaded server certificate.
The server certificate can be retrieved with
`openssl s_client -showcerts -connect $host:16995`.
However, due to the use of `UnsafeLegacyRenegotiation`, `OPENSSL_CONF`
needs to point to a text file explicitly allowing this:
```
openssl_conf = default_conf
[ default_conf ]
ssl_conf = ssl_sect
[ssl_sect]
system_default = ssl_default_sect
[ssl_default_sect]
Options = UnsafeLegacyRenegotiation
```
With this, I'm able to connect to `/dev/ttyS2` inside the host:
```
❯ AMT_PASSWORD='supersecret' amtterm $host 16995 -C cert.pem
amtterm: NONE -> CONNECT (connection to host)
ipv4 $ip [$ip] 16995 open
amtterm: CONNECT -> INIT (redirection initialization)
amtterm: INIT -> AUTH (session authentication)
amtterm: AUTH -> INIT_SOL (serial-over-lan initialization)
amtterm: INIT_SOL -> RUN_SOL (serial-over-lan active)
serial-over-lan redirection ok
connected now, use ^] to escape
Hello World
```
|
|
|
|
|
|
Diff: https://github.com/google/zx/compare/8.1.4...8.1.5
Changelog: https://github.com/google/zx/releases/tag/8.1.5
|
|
|
|
|
|
Signed-off-by: Felix Singer <felixsinger@posteo.net>
|
|
|
|
(#336287)
|
|
- add update script
- remove openssl hash verification logic since the hash is computed
automatically now in the update script
|
|
|
|
nsc: 2.8.6 -> 2.8.7
|
|
|
|
|
|
nats-top: 0.6.1 -> 0.6.2
|
|
stress-ng: 0.18.01 -> 0.18.02
|