Commit Graph

104 Commits

Author SHA1 Message Date
Ihar Hrachyshka
567e8dfd8e treewide: clean up 'meta = with' pattern
This commit was created by a combination of scripts and tools:
- an ast-grep script to prefix things in meta with `lib.`,
- a modified nixf-diagnose / nixf combination to remove unused `with
lib;`, and
- regular nixfmt.

Co-authored-by: Wolfgang Walther <walther@technowledgy.de>
2025-12-10 18:09:49 +01:00
Wolfgang Walther
5a0711127c treewide: run nixfmt 1.0.0 2025-07-24 13:55:40 +02:00
Silvan Mosberger
4f0dadbf38 treewide: format all inactive Nix files
After final improvements to the official formatter implementation,
this commit now performs the first treewide reformat of Nix files using it.
This is part of the implementation of RFC 166.

Only "inactive" files are reformatted, meaning only files that
aren't being touched by any PR with activity in the past 2 months.
This is to avoid conflicts for PRs that might soon be merged.
Later we can do a full treewide reformat to get the rest,
which should not cause as many conflicts.

A CI check has already been running for some time to ensure that new and
already-formatted files are formatted, so the files being reformatted here
should also stay formatted.

This commit was automatically created and can be verified using

    nix-build a08b3a4d19.tar.gz \
      --argstr baseRev b32a094368
    result/bin/apply-formatting $NIXPKGS_PATH
2024-12-10 20:26:33 +01:00
Artturin
c55b931644 treewide: fix lints and remove a unneeded cmake input 2022-12-09 01:16:08 +02:00
Yorick van Pelt
941367cba5 linuxPackages_5_4.wireguard: fix cross build 2022-09-12 13:00:20 +02:00
Yorick van Pelt
32cfc505c6 linuxPackages.wireguard: 1.0.20211208 -> 1.0.20220627 2022-09-12 12:59:02 +02:00
Alyssa Ross
ae8e8aaee7 treewide: remove obsolete kernel version checks
We no longer support any Linux kernel older than 4.9.
2022-04-08 09:56:09 +00:00
Jörg Thalheim
ef7be2a3f6 linuxPackages_4_14.wireguard: 1.0.20210606 -> 1.0.20211208 2022-04-05 11:03:55 +02:00
efim
4c205b2e8b wireguard: meta update 2021-08-13 13:54:09 +03:00
Maximilian Bosch
96c89ab82a linuxPackages_5_4.wireguard: 1.0.20210424 -> 1.0.20210606
ChangeLog: https://lists.zx2c4.com/pipermail/wireguard/2021-June/006781.html
2021-06-13 23:07:33 +02:00
Maximilian Bosch
b5c423bedd linuxPackages.wireguard: 1.0.20210219 -> 1.0.20210424
ChangeLog: https://lists.zx2c4.com/pipermail/wireguard/2021-April/006664.html
2021-05-11 22:59:55 +02:00
Maximilian Bosch
eb8911786c linuxPackages.wireguard: 1.0.20210124 -> 1.0.20210219
ChangeLog: https://lists.zx2c4.com/pipermail/wireguard/2021-February/006404.html
2021-02-24 00:30:49 +01:00
Maximilian Bosch
801c70690a linuxPackaes.wireguard: 1.0.20201221 -> 1.0.20210124
Announcement: https://lists.zx2c4.com/pipermail/wireguard/2021-January/006349.html
2021-02-12 11:23:35 +01:00
Ben Siraphob
16d91ee628 pkgs/os-specific: stdenv.lib -> lib 2021-01-17 23:26:08 +07:00
Profpatsch
4a7f99d55d treewide: with stdenv.lib; in meta -> with lib;
Part of: https://github.com/NixOS/nixpkgs/issues/108938

meta = with stdenv.lib;

is a widely used pattern. We want to slowly remove
the `stdenv.lib` indirection and encourage people
to use `lib` directly. Thus let’s start with the meta
field.

This used a rewriting script to mostly automatically
replace all occurances of this pattern, and add the
`lib` argument to the package header if it doesn’t
exist yet.

The script in its current form is available at
https://cs.tvl.fyi/depot@2f807d7f141068d2d60676a89213eaa5353ca6e0/-/blob/users/Profpatsch/nixpkgs-rewriter/default.nix
2021-01-11 10:38:22 +01:00
Maximilian Bosch
d815581d98 linuxPackages.wireguard: 1.0.20201112 -> 1.0.20201221
https://lists.zx2c4.com/pipermail/wireguard/2020-December/006210.html
2021-01-04 21:20:42 +01:00
Justin Humm
6b9f23267e linuxPackages.wireguard: 1.0.20200908 -> 1.0.20201112 2020-11-12 13:10:20 +01:00
Ivan Kozik
c945b47a25 linuxPackages.wireguard: fix the build on linux 5.4.76
Patch copied from https://github.com/archlinux/svntogit-packages/blob/packages/wireguard-dkms/trunk/lts.diff

This fixes:

```
In file included from <command-line>:
/build/source/src/compat/compat-asm.h:44: warning: "SYM_FUNC_START" redefined
   44 | #define SYM_FUNC_START ENTRY
      |
In file included from /build/source/src/compat/compat-asm.h:9,
                 from <command-line>:
/nix/store/cz60577g5hwk78c2z7rhxl21bklaqr0d-linux-5.4.77-dev/lib/modules/5.4.77-hardened/source/include/linux/linkage.h:218: note: this is the location of the previous definition
  218 | #define SYM_FUNC_START(name)    \
      |
In file included from <command-line>:
/build/source/src/compat/compat-asm.h:45: warning: "SYM_FUNC_END" redefined
   45 | #define SYM_FUNC_END ENDPROC
      |
In file included from /build/source/src/compat/compat-asm.h:9,
                 from <command-line>:
/nix/store/cz60577g5hwk78c2z7rhxl21bklaqr0d-linux-5.4.77-dev/lib/modules/5.4.77-hardened/source/include/linux/linkage.h:265: note: this is the location of the previous definition
  265 | #define SYM_FUNC_END(name)    \
      |
/build/source/src/crypto/zinc/blake2s/blake2s-x86_64.S: Assembler messages:
/build/source/src/crypto/zinc/blake2s/blake2s-x86_64.S:50: Error: invalid character '(' in mnemonic
/build/source/src/crypto/zinc/blake2s/blake2s-x86_64.S:176: Error: invalid character '(' in mnemonic
/build/source/src/crypto/zinc/blake2s/blake2s-x86_64.S:180: Error: invalid character '(' in mnemonic
/build/source/src/crypto/zinc/blake2s/blake2s-x86_64.S:257: Error: invalid character '(' in mnemonic
make[3]: *** [/nix/store/cz60577g5hwk78c2z7rhxl21bklaqr0d-linux-5.4.77-dev/lib/modules/5.4.77-hardened/source/scripts/Makefile.build:348: /build/source/src/crypto/zinc/blake2s/blake2s-x86_64.o] Error 1
make[3]: *** Waiting for unfinished jobs....
In file included from <command-line>:
/build/source/src/compat/compat-asm.h:44: warning: "SYM_FUNC_START" redefined
   44 | #define SYM_FUNC_START ENTRY
      |
In file included from /build/source/src/compat/compat-asm.h:9,
                 from <command-line>:
/nix/store/cz60577g5hwk78c2z7rhxl21bklaqr0d-linux-5.4.77-dev/lib/modules/5.4.77-hardened/source/include/linux/linkage.h:218: note: this is the location of the previous definition
  218 | #define SYM_FUNC_START(name)    \
      |
In file included from <command-line>:
/build/source/src/compat/compat-asm.h:45: warning: "SYM_FUNC_END" redefined
   45 | #define SYM_FUNC_END ENDPROC
      |
In file included from /build/source/src/compat/compat-asm.h:9,
                 from <command-line>:
/nix/store/cz60577g5hwk78c2z7rhxl21bklaqr0d-linux-5.4.77-dev/lib/modules/5.4.77-hardened/source/include/linux/linkage.h:265: note: this is the location of the previous definition
  265 | #define SYM_FUNC_END(name)    \
      |
/build/source/src/crypto/zinc/chacha20/chacha20-x86_64.S: Assembler messages:
/build/source/src/crypto/zinc/chacha20/chacha20-x86_64.S:123: Error: invalid character '(' in mnemonic
/build/source/src/crypto/zinc/chacha20/chacha20-x86_64.S:185: Error: invalid character '(' in mnemonic
/build/source/src/crypto/zinc/chacha20/chacha20-x86_64.S:187: Error: invalid character '(' in mnemonic
/build/source/src/crypto/zinc/chacha20/chacha20-x86_64.S:319: Error: invalid character '(' in mnemonic
/build/source/src/crypto/zinc/chacha20/chacha20-x86_64.S:1016: Error: invalid character '(' in mnemonic
/build/source/src/crypto/zinc/chacha20/chacha20-x86_64.S:1616: Error: invalid character '(' in mnemonic
/build/source/src/crypto/zinc/chacha20/chacha20-x86_64.S:1620: Error: invalid character '(' in mnemonic
/build/source/src/crypto/zinc/chacha20/chacha20-x86_64.S:1810: Error: invalid character '(' in mnemonic
/build/source/src/crypto/zinc/chacha20/chacha20-x86_64.S:1812: Error: invalid character '(' in mnemonic
/build/source/src/crypto/zinc/chacha20/chacha20-x86_64.S:1959: Error: invalid character '(' in mnemonic
make[3]: *** [/nix/store/cz60577g5hwk78c2z7rhxl21bklaqr0d-linux-5.4.77-dev/lib/modules/5.4.77-hardened/source/scripts/Makefile.build:348: /build/source/src/crypto/zinc/chacha20/chacha20-x86_64.o] Error 1
make[2]: *** [/nix/store/cz60577g5hwk78c2z7rhxl21bklaqr0d-linux-5.4.77-dev/lib/modules/5.4.77-hardened/source/Makefile:1729: /build/source/src] Error 2
make[1]: *** [/nix/store/cz60577g5hwk78c2z7rhxl21bklaqr0d-linux-5.4.77-dev/lib/modules/5.4.77-hardened/source/Makefile:179: sub-make] Error 2
make: *** [Makefile:26: module] Error 2
builder for '/nix/store/hll3sjyrwa55arzlsxnbacqdd8s842l1-wireguard-1.0.20200908.drv' failed with exit code 2
```
2020-11-10 23:23:35 -08:00
Maximilian Bosch
c73ef96b7e linuxPackages.wireguard: 1.0.20200729 -> 1.0.20200908
https://lists.zx2c4.com/pipermail/wireguard/2020-September/005817.html
2020-09-08 22:33:06 +02:00
Maximilian Bosch
41f959293b linuxPackages.wireguard: 1.0.20200712 -> 1.0.20200729
https://lists.zx2c4.com/pipermail/wireguard/2020-July/005720.html
2020-07-30 19:28:06 +02:00
Maximilian Bosch
2c275f8513 linuxPackages.wireguard: 1.0.20200623 -> 1.0.20200712
https://lists.zx2c4.com/pipermail/wireguard/2020-July/005639.html
2020-07-17 15:55:58 +02:00
Maximilian Bosch
053db07ba7 linuxPackages.wireguard: 1.0.20200611 -> 1.0.20200623
https://lists.zx2c4.com/pipermail/wireguard/2020-June/005597.html
2020-06-26 18:57:47 +02:00
Maximilian Bosch
52633ca14b linuxPackages.wireguard: 1.0.20200520 -> 1.0.20200611
https://lists.zx2c4.com/pipermail/wireguard/2020-June/005480.html
2020-06-17 02:31:31 +02:00
Maximilian Bosch
e90c5fe0ec linuxPackages.wireguard: 1.0.20200506 -> 1.0.20200520
https://lists.zx2c4.com/pipermail/wireguard/2020-May/005450.html
2020-05-31 21:25:56 +02:00
Maximilian Bosch
f887d09c89 linuxPackages.wireguard: 1.0.20200429 -> 1.0.20200506
https://lists.zx2c4.com/pipermail/wireguard/2020-May/005408.html
2020-05-10 01:35:30 +02:00
Josef Schlehofer
e008d5fc98 wireguard-compat: 1.0.20200426 -> 1.0.20200429 2020-05-03 18:39:08 +02:00
David Terry
e9c44e8956 wireguard-compat: 1.0.20200413 -> 1.0.20200426
https://lists.zx2c4.com/pipermail/wireguard/2020-April/005237.html
2020-04-27 08:15:39 +02:00
Jörg Thalheim
21ec1f5ead wireguard: 1.0.20200401 -> 1.0.20200413 2020-04-25 11:16:10 +01:00
Maximilian Bosch
b503b2c75f linuxPackages.wireguard: 0.0.20200318 -> 1.0.20200401
https://lists.zx2c4.com/pipermail/wireguard/2020-April/005237.html

Resolves #84009
2020-04-01 22:42:15 +02:00
Maximilian Bosch
e758e95c1d linuxPackages.wireguard: 0.0.20200215 -> 0.0.20200318
https://lists.zx2c4.com/pipermail/wireguard/2020-March/005188.html
2020-03-19 08:42:34 +01:00
David Terry
b76dab8fc8 linuxPackages.wireguard: 0.0.20200214 -> 0.0.20200215 2020-02-15 08:01:42 +01:00
Maximilian Bosch
7666bf47c7 linuxPackages.wireguard: 0.0.20200205 -> 0.0.20200214
https://lists.zx2c4.com/pipermail/wireguard/2020-February/005013.html
2020-02-14 17:16:10 +01:00
Frederik Rietdijk
419bc0a4cd Revert "Revert "Merge master into staging-next""
In 87a19e9048 I merged staging-next into master using the GitHub gui as intended.
In ac241fb7a5 I merged master into staging-next for the next staging cycle, however, I accidentally pushed it to master.
Thinking this may cause trouble, I reverted it in 0be87c7979. This was however wrong, as it "removed" master.

This reverts commit 0be87c7979.
2020-02-05 19:41:25 +01:00
Frederik Rietdijk
0be87c7979 Revert "Merge master into staging-next"
I merged master into staging-next but accidentally pushed it to master.
This should get us back to 87a19e9048.

This reverts commit ac241fb7a5, reversing
changes made to 76a439239e.
2020-02-05 19:18:35 +01:00
Maximilian Bosch
f8a0576f6c linuxPackages.wireguard: 0.0.20200128 -> 0.0.20200205
https://lists.zx2c4.com/pipermail/wireguard/2020-February/004962.html
2020-02-05 16:47:41 +01:00
Maximilian Bosch
0ab53979bc linuxPackages.wireguard: 0.0.20200121 -> 0.0.20200128
https://lists.zx2c4.com/pipermail/wireguard/2020-January/004905.html
2020-01-28 20:29:59 +01:00
Maximilian Bosch
5a8e936da8 linuxPackages.wireguard: 0.0.20200105 -> 0.0.20200121
https://lists.zx2c4.com/pipermail/wireguard/2020-January/004870.html
2020-01-21 17:58:35 +01:00
David Terry
ed72b90dd6 wireguard: 0.0.20191226 -> 0.0.20200105
https://lists.zx2c4.com/pipermail/wireguard/2020-January/004844.html
2020-01-06 17:24:28 +01:00
David Terry
9681bc7147 wireguard: 0.0.20191219 -> 0.0.20191226
the wireguard kernel module has been pulled out into it's own repo as
announced in this mailing list post:

https://lists.zx2c4.com/pipermail/wireguard/2019-December/004796.html
2019-12-27 21:01:54 +01:00
volth
08f68313a4 treewide: remove redundant rec 2019-08-28 11:07:32 +00:00
volth
46420bbaa3 treewide: name -> pname (easy cases) (#66585)
treewide replacement of

stdenv.mkDerivation rec {
  name = "*-${version}";
  version = "*";

to pname
2019-08-15 13:41:18 +01:00
Maximilian Bosch
2c3ab523d3 linuxPackages.wireguard: fix build
Ensure that only module-related targets from the project's Makefile are
built.

Co-authored-by: elseym <elseym@me.com>
Co-authored-by: Franz Pletz <fpletz@fnordicwalking.de>
2019-03-15 22:45:14 +01:00
Franz Pletz
73d7046362 linuxPackages.wireguard: fix wireguard-tools bump
See 6fb56af8b2.

cc #50833
2018-11-22 14:41:08 +01:00
volth
52f53c69ce pkgs/*: remove unreferenced function arguments 2018-07-21 02:48:04 +00:00
Yegor Timoshenko
9807281253 wireguard{,-go,-tools}: 0.0.20180531 -> 0.0.20180613 2018-06-14 19:45:15 +00:00
Jason A. Donenfeld
8d575415ad wireguard: fix up text, maintainer, and version 2018-05-22 02:58:13 +02:00
Yegor Timoshenko
f8ed43e600 wireguard: use src from wireguard-tools 2018-05-19 17:20:33 +03:00
Kirill Elagin
95cf07fc95 wireguard: use fetchzip instead of fetchurl
Because cgit snapshots are not deterministic.
2018-05-19 13:09:14 +03:00
Kirill Elagin
865abfa609 wireguard: Enable tools on other platforms
Wireguard is now split into two pretty much independent packages:
`wireguard` (Linux-specific kernel module) and `wireguard-tools`,
which is cross-platform.
2018-05-19 01:17:26 +03:00
R. RyanTM
2355a7f0e4 linuxPackages.wireguard: 0.0.20180420 -> 0.0.20180514 (#40631)
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.

This update was made based on information from https://repology.org/metapackage/wireguard/versions.

These checks were done:

- built on NixOS

- 0 of 0 passed binary check by having a zero exit code.
- 0 of 0 passed binary check by having the new version present in output.
- directory tree listing: https://gist.github.com/ed69b3dfb89cc9d82136b356d54d21bb
- du listing: https://gist.github.com/0f8c8caf71b9d18efa2341ce03a212f1
2018-05-18 22:57:13 +02:00