3
0
Fork 0
forked from mirrors/nixpkgs
Commit graph

2841 commits

Author SHA1 Message Date
Maximilian Bosch fcc8660d35
Merge pull request #81967 from Ma27/brutespray
brutespray: init at 1.6.6
2020-03-09 20:47:06 +01:00
Mario Rodas 791a24da1b
Merge pull request #82058 from helsinki-systems/fix/bitwarden_rs-vault
bitwarden_rs-vault: fix directory structure
2020-03-08 20:26:45 -05:00
Benjamin Hipple 6331093673
b3sum: upgrade cargo fetcher and cargoSha256 (#82086) 2020-03-08 21:06:25 -04:00
Benjamin Hipple d1cdeb7aae
ripasso-cursive: upgrade cargo fetcher and cargoSha256 (#81988) 2020-03-08 19:18:40 -04:00
ajs124 bc21f7a0ce bitwarden_rs-vault: fix directory structure 2020-03-08 16:41:00 +01:00
Maximilian Bosch e0a5d34664
brutespray: init at 1.6.6 2020-03-08 10:52:13 +01:00
Maximilian Bosch 3d6908bca1
medusa-unstable: init at 2018-12-16 2020-03-08 10:52:13 +01:00
Frederik Rietdijk 0eb0ddc4db Merge staging-next into master 2020-03-08 08:11:01 +01:00
Doron Behar 25151bcbb6 sequoia: 0.14.0 -> 0.15.0 2020-03-06 20:03:05 +02:00
Mario Rodas ef4b914b11
vault: 1.3.2 -> 1.3.3 2020-03-06 04:20:00 -05:00
Frederik Rietdijk 188c3a4d03 Merge staging-next into staging 2020-03-06 07:09:30 +01:00
Vincent Breitmoser 7cc68a961d gnupg: apply patch to allow import of key updates without user ids
This adds a patch series which allows GnuPG to import updates
(revocations and subkeys) from certificates that contain no user ids.
This is relevant for refreshing keys from the default keyserver
keys.openpgp.org, where only user ids that contain verified email
addresses will be distributed, and revoked keys never contain any user
ids.

This patch series was originally authored and submitted to upstream half
a year ago (by me), but now comes from Debian packaging where it's been
included since then.

Relates to the following upstream issue: https://dev.gnupg.org/T4393
2020-03-06 06:58:56 +01:00
R. RyanTM 7948c35be6 bitwarden_rs-vault: 2.12.0c -> 2.12.0e 2020-03-05 15:12:09 -08:00
Mario Rodas a7454c0a18
Merge pull request #81700 from r-ryantm/auto-update/nwipe
nwipe: 0.26 -> 0.27
2020-03-04 08:47:01 -05:00
R. RyanTM 37f9f898ad nwipe: 0.26 -> 0.27 2020-03-04 08:31:40 +00:00
Mario Rodas 5d9c31572b
Merge pull request #81128 from deingithub/keybase-5-2-1-update
keybase,kbfs,keybase-gui: 5.1.1 -> 5.2.1
2020-03-01 10:14:38 -05:00
Maximilian Bosch ee32de777a
Merge pull request #81243 from bhipple/u/rust-cargo-bitwarden_rs
bitwarden_rs: upgrade cargo fetcher and cargoSha256
2020-02-28 20:44:56 +01:00
Maximilian Bosch a1ce8740fa
Merge pull request #81249 from bhipple/u/rust-cargo-jwt-cli
jwt-cli: upgrade cargo fetcher and cargoSha256
2020-02-28 20:25:43 +01:00
Benjamin Hipple d31aae2865 jwt-cli: upgrade cargo fetcher and cargoSha256
Infra upgrade as part of #79975; no functional change expected.
2020-02-27 23:19:22 -05:00
Benjamin Hipple e660d86a4c rage: upgrade cargo fetcher and cargoSha256
Infra upgrade as part of #79975; no functional change expected.
2020-02-27 22:59:05 -05:00
Benjamin Hipple 584a852210 bitwarden_rs: upgrade cargo fetcher and cargoSha256
Infra upgrade as part of #79975; no functional change expected.
2020-02-27 22:53:52 -05:00
Cassidy Dingenskirchen 87854a7457
keybase,kbfs,keybase-gui: 5.1.1 -> 5.2.1 2020-02-26 17:33:05 +01:00
Mario Rodas 4baba1a06b
Merge pull request #80533 from msteen/bitwarden_rs
bitwarden_rs-vault: 2.12.0b -> 2.12.0c
2020-02-19 09:07:01 -05:00
Maximilian Bosch 5ea19307fe
Merge pull request #80512 from xfix/tor-disable-monotonic-tests
tor: fix build
2020-02-19 13:48:49 +01:00
Matthijs Steen 425db300c1 bitwarden_rs-vault: 2.12.0b -> 2.12.0c 2020-02-19 13:26:48 +01:00
Konrad Borowski 58af3177c0 tor: fix build
Monotonic timer test expects sleep(200ms) to take at most 1s. On
loaded systems like hydra, it's possible for such a test to take
longer than 1 second.

Tests expecting sleep(200ms) to take at least 175ms weren't removed,
because load shouldn't cause sleep to be shorter.
2020-02-19 09:11:46 +01:00
zowoq 72c145115b metasploit: 5.0.45 -> 5.0.74 2020-02-18 08:32:09 -08:00
Franz Pletz 37f35dc779
clevis: init at 12 2020-02-17 15:14:28 +01:00
Benjamin Hipple 131a32a5af rust: update docs on legacyCargoFetcher; remove unnecessary defaults
As mentioned in #79975, the default on `legacyCargoFetcher` if left unspecified
is now `false`.
2020-02-15 22:07:47 -08:00
Benjamin Hipple 993719b88a sequoia: fix build by migrating off legacy fetchCargo implementation
Currently broken; see #79975 for details. Would also be fixed by #80153
eventually, but since we want to upgrade either way we might as well do so now.
2020-02-15 16:33:10 -05:00
R. RyanTM 97303641ca clamav: 0.102.1 -> 0.102.2 2020-02-15 17:52:24 +01:00
Daniel Schaefer 6befabd559
Merge pull request #74458 from r-ryantm/auto-update/mkp224o
mkp224o: 1.3.0 -> 1.4.0
2020-02-15 15:34:46 +01:00
Benjamin Hipple eb11feaa0b treewide: change fetchCargoTarball default to opt-out
Changes the default fetcher in the Rust Platform to be the newer
`fetchCargoTarball`, and changes every application using the current default to
instead opt out.

This commit does not change any hashes or cause any rebuilds. Once integrated,
we will start deleting the opt-outs and recomputing hashes.

See #79975 for details.
2020-02-13 22:41:37 -08:00
worldofpeace 3565f1782d
Merge pull request #79758 from doronbehar/update-sequoia
sequoia: 0.13.0 -> 0.14.0
2020-02-12 16:06:45 -05:00
Frederik Rietdijk 424697d512 Merge master into staging-next 2020-02-12 09:55:31 +01:00
lewo 2a773b1506
Merge pull request #79325 from eonpatapon/safe
safe: init at 1.5.1
2020-02-11 16:27:00 +01:00
Jean-Philippe Braun dd759b3b67 safe: init at 1.5.1 2020-02-11 16:09:54 +01:00
Frederik Rietdijk 1a6c3cb06b Merge staging into staging-next 2020-02-11 07:59:53 +01:00
Oleksii Filonenko 0ea4e9940b keybase,keybase-gui: 5.1.0 -> 5.1.1 2020-02-10 20:41:28 +01:00
Oleksii Filonenko 85b93ef20e keybase,keybase-gui: add filalex77 to maintainers 2020-02-10 20:41:28 +01:00
Oleksii Filonenko 0aa6230b58 keybase,keybase-gui: 5.0.0 -> 5.1.0 2020-02-10 20:41:28 +01:00
Daniel Schaefer 8a24d3f892 chipsec: 1.4.1 -> 1.4.7 2020-02-10 19:50:25 +01:00
R. RyanTM 6a64f267a0 tor: 0.4.2.5 -> 0.4.2.6 2020-02-10 19:43:58 +01:00
Doron Behar 4f6d905d1c sequoia: 0.13.0 -> 0.14.0 2020-02-10 19:54:04 +02:00
Benjamin Hipple 2115a2037c fetchcargo: use flat tar.gz file for vendored src instead of recursive hash dir
This has several advantages:

1. It takes up less space on disk in-between builds in the nix store.
2. It uses less space in the binary cache for vendor derivation packages.
3. It uses less network traffic downloading from the binary cache.
4. It plays nicely with hashed mirrors like tarballs.nixos.org, which only
   substitute --flat hashes on single files (not recursive directory hashes).
5. It's consistent with how simple `fetchurl` src derivations work.
6. It provides a stronger abstraction between input src-package and output
   package, e.g., it's harder to accidentally depend on the src derivation at
   runtime by referencing something like `${src}/etc/index.html`. Likewise, in
   the store it's harder to get confused with something that is just there as a
   build-time dependency vs. a runtime dependency, since the build-time
   src dependencies are tarred up.

Disadvantages are:
1. It takes slightly longer to untar at the start of a build.

As currently implemented, this attaches the compacted vendor.tar.gz feature as a
rider on `verifyCargoDeps`, since both of them are relatively newly implemented
behavior that change the `cargoSha256`.

If this PR is accepted, I will push forward the remaining rust packages with a
series of treewide PRs to update the `cargoSha256`s.
2020-02-10 10:17:29 -05:00
Mario Rodas b153b71523
rage: 0.2.0 -> 0.3.0
Changelog: https://github.com/str4d/rage/releases/tag/v0.3.0
2020-02-09 16:20:00 -05:00
Robert Helgesson d084221b36
jwt-cli: 2.5.1 -> 2.5.2 2020-02-09 17:33:08 +01:00
Frederik Rietdijk 30f0909e3a Merge master into staging-next 2020-02-07 19:27:52 +01:00
Marek Mahut 58ce5a3f47
Merge pull request #79419 from r-ryantm/auto-update/chrome-token-signing
chrome-token-signing: 1.1.0 -> 1.1.1
2020-02-07 14:26:59 +01:00
R. RyanTM 3f5e8c2d08 chrome-token-signing: 1.1.0 -> 1.1.1 2020-02-07 07:04:05 +00:00