jade/lix
0
0
Fork 0
forked from lix-project/lix
Code Pull requests Activity
lix/flake.lock

96 lines
2.5 KiB
Text
Raw Normal View History

Add flake lockfile
2019-04-16 13:47:15 +00:00
{
flake.lock: Update Flake input changes: * Updated 'nixpkgs': 'github:NixOS/nixpkgs/81fa5f4501372671b464fe0104fe47f5327b46fe' -> 'github:NixOS/nixpkgs/b88ff468e9850410070d4e0ccd68c7011f15b2be'
2020-03-30 11:33:08 +00:00
"nodes": {
add flake-compat to flake.nix and use sha256 in default.nix
2023-03-06 19:51:58 +00:00
"flake-compat": {
"flake": false,
"locked": {
Add `pre-commit` checks The big ones here are `trim-trailing-whitespace` and `end-of-file-fixer` (which makes sure that every file ends with exactly one newline character). Change-Id: Idca73b640883188f068f9903e013cf0d82aa1123
2024-03-27 17:16:16 +00:00
"lastModified": 1696426674,
"narHash": "sha256-kvjfFW7WAETZlt09AgDn1MrtKzP7t90Vf7vypd3OL1U=",
add flake-compat to flake.nix and use sha256 in default.nix
2023-03-06 19:51:58 +00:00
"owner": "edolstra",
"repo": "flake-compat",
Add `pre-commit` checks The big ones here are `trim-trailing-whitespace` and `end-of-file-fixer` (which makes sure that every file ends with exactly one newline character). Change-Id: Idca73b640883188f068f9903e013cf0d82aa1123
2024-03-27 17:16:16 +00:00
"rev": "0f9255e01c2351cc7d116c072cb317785dd33b33",
add flake-compat to flake.nix and use sha256 in default.nix
2023-03-06 19:51:58 +00:00
"type": "github"
},
"original": {
"owner": "edolstra",
"repo": "flake-compat",
"type": "github"
}
},
Rewrite docker to be sensible and smaller I have checked the image can build things and inspected `diff -ru` compared to the old image. As far as I can tell it is more or less the same besides the later git change. Layers are now 65MB or less, and we aren't against the maxLayers limit for the broken automatic layering to do anything but shove one store path in a layer (which is good behaviour, actually). This uses nix2container which streams images, so the build time is much shorter. I have also taken the opportunity to, in addition to fixing the 400MB single layer (terrible, and what motivated this in the first place), delete about 200MB of closure size inflicted by git vs gitMinimal causing both perl and python to get into closure. People mostly use this thing for CI, so I don't really think you need advanced git operations, and large git can be added at the user side if really motivated. With love for whichever container developer somewhat ironically assumed that one would not run skopeo in a minimal container that doesn't have a /var/tmp. Fixes: https://git.lix.systems/lix-project/lix/issues/378 Change-Id: Icc3aa20e64446276716fbbb87535fd5b50628010
2024-06-07 08:35:26 +00:00
"nix2container": {
"flake": false,
"locked": {
flake.lock: update everything Periodic updating of everything. Change-Id: Ie006fd7c2dc0725309dea831685ea7b24b569df5
2024-09-26 01:42:16 +00:00
"lastModified": 1724996935,
"narHash": "sha256-njRK9vvZ1JJsP8oV2OgkBrpJhgQezI03S7gzskCcHos=",
Rewrite docker to be sensible and smaller I have checked the image can build things and inspected `diff -ru` compared to the old image. As far as I can tell it is more or less the same besides the later git change. Layers are now 65MB or less, and we aren't against the maxLayers limit for the broken automatic layering to do anything but shove one store path in a layer (which is good behaviour, actually). This uses nix2container which streams images, so the build time is much shorter. I have also taken the opportunity to, in addition to fixing the 400MB single layer (terrible, and what motivated this in the first place), delete about 200MB of closure size inflicted by git vs gitMinimal causing both perl and python to get into closure. People mostly use this thing for CI, so I don't really think you need advanced git operations, and large git can be added at the user side if really motivated. With love for whichever container developer somewhat ironically assumed that one would not run skopeo in a minimal container that doesn't have a /var/tmp. Fixes: https://git.lix.systems/lix-project/lix/issues/378 Change-Id: Icc3aa20e64446276716fbbb87535fd5b50628010
2024-06-07 08:35:26 +00:00
"owner": "nlewo",
"repo": "nix2container",
flake.lock: update everything Periodic updating of everything. Change-Id: Ie006fd7c2dc0725309dea831685ea7b24b569df5
2024-09-26 01:42:16 +00:00
"rev": "fa6bb0a1159f55d071ba99331355955ae30b3401",
Rewrite docker to be sensible and smaller I have checked the image can build things and inspected `diff -ru` compared to the old image. As far as I can tell it is more or less the same besides the later git change. Layers are now 65MB or less, and we aren't against the maxLayers limit for the broken automatic layering to do anything but shove one store path in a layer (which is good behaviour, actually). This uses nix2container which streams images, so the build time is much shorter. I have also taken the opportunity to, in addition to fixing the 400MB single layer (terrible, and what motivated this in the first place), delete about 200MB of closure size inflicted by git vs gitMinimal causing both perl and python to get into closure. People mostly use this thing for CI, so I don't really think you need advanced git operations, and large git can be added at the user side if really motivated. With love for whichever container developer somewhat ironically assumed that one would not run skopeo in a minimal container that doesn't have a /var/tmp. Fixes: https://git.lix.systems/lix-project/lix/issues/378 Change-Id: Icc3aa20e64446276716fbbb87535fd5b50628010
2024-06-07 08:35:26 +00:00
"type": "github"
},
"original": {
"owner": "nlewo",
"repo": "nix2container",
"type": "github"
}
},
Update flake.lock
2020-02-03 17:59:29 +00:00
"nixpkgs": {
"locked": {
flake: Use nixpkgs 24.11 nixpkgs 24.11 changes how we access xonsh yet again and updates clang. Unfortunately, clang 18 produces significantly more warnings on existing code that is challenging to fix. Make sure that doesn't error when we're running `-Werror` builds. Change-Id: If0141a46a8b445a0e7d6f86f939e8c8e03569bf5
2024-11-21 22:58:12 +00:00
"lastModified": 1732237847,
"narHash": "sha256-WwtrPxym9sQtwZkemxUfT00iCWfXxzuVAC7uFP1m1Y0=",
flake: complete update to 23.05 (cherry picked from commit f264d9ff0862277523a207c7afaed4894a40dc11)
2023-09-22 01:00:35 +00:00
"owner": "NixOS",
Update flake.lock
2020-02-03 17:59:29 +00:00
"repo": "nixpkgs",
flake: Use nixpkgs 24.11 nixpkgs 24.11 changes how we access xonsh yet again and updates clang. Unfortunately, clang 18 produces significantly more warnings on existing code that is challenging to fix. Make sure that doesn't error when we're running `-Werror` builds. Change-Id: If0141a46a8b445a0e7d6f86f939e8c8e03569bf5
2024-11-21 22:58:12 +00:00
"rev": "9bbcb9a5a7e54369faaced5fb0ddad1fda21b751",
Update flake.lock
2020-02-03 17:59:29 +00:00
"type": "github"
},
"original": {
flake: complete update to 23.05 (cherry picked from commit f264d9ff0862277523a207c7afaed4894a40dc11)
2023-09-22 01:00:35 +00:00
"owner": "NixOS",
flake: Use nixpkgs 24.11 nixpkgs 24.11 changes how we access xonsh yet again and updates clang. Unfortunately, clang 18 produces significantly more warnings on existing code that is challenging to fix. Make sure that doesn't error when we're running `-Werror` builds. Change-Id: If0141a46a8b445a0e7d6f86f939e8c8e03569bf5
2024-11-21 22:58:12 +00:00
"ref": "nixos-24.11-small",
flake: use github: reference to nixpkgs This allows flakes that don't override the Nixpkgs input and also have a different flake registry.
2022-05-16 18:46:44 +00:00
"repo": "nixpkgs",
"type": "github"
Update flake.lock
2020-02-03 17:59:29 +00:00
}
flake.lock: Update Flake input changes: * Updated 'nixpkgs': 'github:NixOS/nixpkgs/81fa5f4501372671b464fe0104fe47f5327b46fe' -> 'github:NixOS/nixpkgs/b88ff468e9850410070d4e0ccd68c7011f15b2be'
2020-03-30 11:33:08 +00:00
},
Add regression / performance tests against a fixed revision of Nixpkgs
2022-01-24 23:02:48 +00:00
"nixpkgs-regression": {
"locked": {
"lastModified": 1643052045,
"narHash": "sha256-uGJ0VXIhWKGXxkeNnq4TvV3CIOkUJ3PAoLZ3HMzNVMw=",
"owner": "NixOS",
"repo": "nixpkgs",
"rev": "215d4d0fd80ca5163643b03a33fde804a29cc1e2",
"type": "github"
},
"original": {
flake: use github: reference to nixpkgs This allows flakes that don't override the Nixpkgs input and also have a different flake registry.
2022-05-16 18:46:44 +00:00
"owner": "NixOS",
"repo": "nixpkgs",
Add regression / performance tests against a fixed revision of Nixpkgs
2022-01-24 23:02:48 +00:00
"rev": "215d4d0fd80ca5163643b03a33fde804a29cc1e2",
flake: use github: reference to nixpkgs This allows flakes that don't override the Nixpkgs input and also have a different flake registry.
2022-05-16 18:46:44 +00:00
"type": "github"
Add regression / performance tests against a fixed revision of Nixpkgs
2022-01-24 23:02:48 +00:00
}
},
Add `pre-commit` checks The big ones here are `trim-trailing-whitespace` and `end-of-file-fixer` (which makes sure that every file ends with exactly one newline character). Change-Id: Idca73b640883188f068f9903e013cf0d82aa1123
2024-03-27 17:16:16 +00:00
"pre-commit-hooks": {
pre-commit: stop using the flake The flake for pre-commit-checks is rather questionable. We ignored it so it uses our own nixpkgs and doesn't reimport nixpkgs. This should save a couple of seconds of eval time! Change-Id: I4584982beb32e0122f791fa29f6a544bdbb9e201
2024-04-08 03:05:19 +00:00
"flake": false,
Add `pre-commit` checks The big ones here are `trim-trailing-whitespace` and `end-of-file-fixer` (which makes sure that every file ends with exactly one newline character). Change-Id: Idca73b640883188f068f9903e013cf0d82aa1123
2024-03-27 17:16:16 +00:00
"locked": {
flake: Use nixpkgs 24.11 nixpkgs 24.11 changes how we access xonsh yet again and updates clang. Unfortunately, clang 18 produces significantly more warnings on existing code that is challenging to fix. Make sure that doesn't error when we're running `-Werror` builds. Change-Id: If0141a46a8b445a0e7d6f86f939e8c8e03569bf5
2024-11-21 22:58:12 +00:00
"lastModified": 1733318908,
"narHash": "sha256-SVQVsbafSM1dJ4fpgyBqLZ+Lft+jcQuMtEL3lQWx2Sk=",
Use upstream `cachix/git-hooks.nix` for pre-commit Change-Id: I6bbc7d6da9accd7d2daffa9d780384df7226670e
2024-04-01 17:34:30 +00:00
"owner": "cachix",
Add `pre-commit` checks The big ones here are `trim-trailing-whitespace` and `end-of-file-fixer` (which makes sure that every file ends with exactly one newline character). Change-Id: Idca73b640883188f068f9903e013cf0d82aa1123
2024-03-27 17:16:16 +00:00
"repo": "git-hooks.nix",
flake: Use nixpkgs 24.11 nixpkgs 24.11 changes how we access xonsh yet again and updates clang. Unfortunately, clang 18 produces significantly more warnings on existing code that is challenging to fix. Make sure that doesn't error when we're running `-Werror` builds. Change-Id: If0141a46a8b445a0e7d6f86f939e8c8e03569bf5
2024-11-21 22:58:12 +00:00
"rev": "6f4e2a2112050951a314d2733a994fbab94864c6",
Add `pre-commit` checks The big ones here are `trim-trailing-whitespace` and `end-of-file-fixer` (which makes sure that every file ends with exactly one newline character). Change-Id: Idca73b640883188f068f9903e013cf0d82aa1123
2024-03-27 17:16:16 +00:00
"type": "github"
},
"original": {
Use upstream `cachix/git-hooks.nix` for pre-commit Change-Id: I6bbc7d6da9accd7d2daffa9d780384df7226670e
2024-04-01 17:34:30 +00:00
"owner": "cachix",
Add `pre-commit` checks The big ones here are `trim-trailing-whitespace` and `end-of-file-fixer` (which makes sure that every file ends with exactly one newline character). Change-Id: Idca73b640883188f068f9903e013cf0d82aa1123
2024-03-27 17:16:16 +00:00
"repo": "git-hooks.nix",
"type": "github"
}
},
flake.lock: Update Flake input changes: * Updated 'nixpkgs': 'github:NixOS/nixpkgs/81fa5f4501372671b464fe0104fe47f5327b46fe' -> 'github:NixOS/nixpkgs/b88ff468e9850410070d4e0ccd68c7011f15b2be'
2020-03-30 11:33:08 +00:00
"root": {
"inputs": {
add flake-compat to flake.nix and use sha256 in default.nix
2023-03-06 19:51:58 +00:00
"flake-compat": "flake-compat",
Rewrite docker to be sensible and smaller I have checked the image can build things and inspected `diff -ru` compared to the old image. As far as I can tell it is more or less the same besides the later git change. Layers are now 65MB or less, and we aren't against the maxLayers limit for the broken automatic layering to do anything but shove one store path in a layer (which is good behaviour, actually). This uses nix2container which streams images, so the build time is much shorter. I have also taken the opportunity to, in addition to fixing the 400MB single layer (terrible, and what motivated this in the first place), delete about 200MB of closure size inflicted by git vs gitMinimal causing both perl and python to get into closure. People mostly use this thing for CI, so I don't really think you need advanced git operations, and large git can be added at the user side if really motivated. With love for whichever container developer somewhat ironically assumed that one would not run skopeo in a minimal container that doesn't have a /var/tmp. Fixes: https://git.lix.systems/lix-project/lix/issues/378 Change-Id: Icc3aa20e64446276716fbbb87535fd5b50628010
2024-06-07 08:35:26 +00:00
"nix2container": "nix2container",
Add regression / performance tests against a fixed revision of Nixpkgs
2022-01-24 23:02:48 +00:00
"nixpkgs": "nixpkgs",
Add `pre-commit` checks The big ones here are `trim-trailing-whitespace` and `end-of-file-fixer` (which makes sure that every file ends with exactly one newline character). Change-Id: Idca73b640883188f068f9903e013cf0d82aa1123
2024-03-27 17:16:16 +00:00
"nixpkgs-regression": "nixpkgs-regression",
"pre-commit-hooks": "pre-commit-hooks"
}
Update flake.lock
2020-02-03 17:59:29 +00:00
}
},
flake.lock: Update Flake input changes: * Updated 'nixpkgs': 'github:NixOS/nixpkgs/81fa5f4501372671b464fe0104fe47f5327b46fe' -> 'github:NixOS/nixpkgs/b88ff468e9850410070d4e0ccd68c7011f15b2be'
2020-03-30 11:33:08 +00:00
"root": "root",
Fix clang build
2020-08-24 19:13:39 +00:00
"version": 7
Add newline at end of lockfile Suggested by @grahamc.
2019-05-08 16:20:35 +00:00
}
Copy permalink