mdebray/tvl-depot
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
tvl-depot/third_party/sources/sources.json

51 lines
2.2 KiB
JSON
Raw Normal View History

refactor(3p/nixpkgs): Pin nixpkgs sources via niv There's no need for us to reinvent the wheel here. niv pins are in //third_party/sources, and niv commands need to be run with `niv -s third_party/sources/sources.json` to operate on the correct file. Note that niv by default wants to put the loader file in //nix/sources.nix. This file has been moved to //third_party/sources/default.nix which makes niv throw a warning, but everything still works as intended. Change-Id: I2b2a6f8edf33c429a6d7be9d174ba1996d9a0193 Reviewed-on: https://cl.tvl.fyi/c/depot/+/5143 Reviewed-by: grfn <grfn@gws.fyi> Reviewed-by: sterni <sternenseemann@systemli.org> Tested-by: BuildkiteCI Autosubmit: tazjin <tazjin@tvl.su>
2022-01-31 12:19:21 +01:00
{
refactor(3p/overlays): Fetch emacs-overlay through niv Change-Id: I1c59d463eb1f50fa6e24774ec75ccd2e2d98e120 Reviewed-on: https://cl.tvl.fyi/c/depot/+/5144 Tested-by: BuildkiteCI Autosubmit: tazjin <tazjin@tvl.su> Reviewed-by: sterni <sternenseemann@systemli.org>
2022-01-31 12:24:28 +01:00
"emacs-overlay": {
"branch": "master",
"description": "Bleeding edge emacs overlay [maintainer=@adisbladis] ",
"homepage": "",
"owner": "nix-community",
"repo": "emacs-overlay",
chore(3p/sources): Bump channels & overlays * //3p/overlays/tvl: propagate git as a native build input from magit, because magit checks the version of git at load time ever since a recent commit [1]. This check been escalated to a failure in a subsequent commit [2]. The result is that anything require-ing magit will fail with an error if git is not in PATH (or a path to git provided) which is basically what happens in byte compilation of all packages that depend on magit. For now the easiest way to work around it is letting magit have its way and provide git which easy enough for it. Upstream should probably think about this behaviour or emacs-overlay address it somehow. For now I've opened an issue with magit [3]. [1]: https://github.com/magit/magit/commit/6c4ff54a0836985fac6d72c7e4bfeff964775efe [2]: https://github.com/magit/magit/commit/8394f0d4ea5ffa6858db314efabe91d99f78e67a [3]: https://github.com/magit/magit/issues/4614 Change-Id: I6aaf8258c3798b76cdaa6eef066c6224e374e02e Reviewed-on: https://cl.tvl.fyi/c/depot/+/5326 Autosubmit: sterni <sternenseemann@systemli.org> Tested-by: BuildkiteCI Reviewed-by: tazjin <tazjin@tvl.su>
2022-02-26 12:35:45 +01:00
"rev": "9a35488970b3f33a6df6a0d9387a0c8c4c555c1d",
"sha256": "0akpaw2j5b2jfil9jgyisl5w72np3jm0a3amq2xr5wss8fpnqgxl",
refactor(3p/overlays): Fetch emacs-overlay through niv Change-Id: I1c59d463eb1f50fa6e24774ec75ccd2e2d98e120 Reviewed-on: https://cl.tvl.fyi/c/depot/+/5144 Tested-by: BuildkiteCI Autosubmit: tazjin <tazjin@tvl.su> Reviewed-by: sterni <sternenseemann@systemli.org>
2022-01-31 12:24:28 +01:00
"type": "tarball",
chore(3p/sources): Bump channels & overlays * //3p/overlays/tvl: propagate git as a native build input from magit, because magit checks the version of git at load time ever since a recent commit [1]. This check been escalated to a failure in a subsequent commit [2]. The result is that anything require-ing magit will fail with an error if git is not in PATH (or a path to git provided) which is basically what happens in byte compilation of all packages that depend on magit. For now the easiest way to work around it is letting magit have its way and provide git which easy enough for it. Upstream should probably think about this behaviour or emacs-overlay address it somehow. For now I've opened an issue with magit [3]. [1]: https://github.com/magit/magit/commit/6c4ff54a0836985fac6d72c7e4bfeff964775efe [2]: https://github.com/magit/magit/commit/8394f0d4ea5ffa6858db314efabe91d99f78e67a [3]: https://github.com/magit/magit/issues/4614 Change-Id: I6aaf8258c3798b76cdaa6eef066c6224e374e02e Reviewed-on: https://cl.tvl.fyi/c/depot/+/5326 Autosubmit: sterni <sternenseemann@systemli.org> Tested-by: BuildkiteCI Reviewed-by: tazjin <tazjin@tvl.su>
2022-02-26 12:35:45 +01:00
"url": "https://github.com/nix-community/emacs-overlay/archive/9a35488970b3f33a6df6a0d9387a0c8c4c555c1d.tar.gz",
refactor(3p/overlays): Fetch emacs-overlay through niv Change-Id: I1c59d463eb1f50fa6e24774ec75ccd2e2d98e120 Reviewed-on: https://cl.tvl.fyi/c/depot/+/5144 Tested-by: BuildkiteCI Autosubmit: tazjin <tazjin@tvl.su> Reviewed-by: sterni <sternenseemann@systemli.org>
2022-01-31 12:24:28 +01:00
"url_template": "https://github.com/<owner>/<repo>/archive/<rev>.tar.gz"
},
refactor(3p/nixpkgs): Pin nixpkgs sources via niv There's no need for us to reinvent the wheel here. niv pins are in //third_party/sources, and niv commands need to be run with `niv -s third_party/sources/sources.json` to operate on the correct file. Note that niv by default wants to put the loader file in //nix/sources.nix. This file has been moved to //third_party/sources/default.nix which makes niv throw a warning, but everything still works as intended. Change-Id: I2b2a6f8edf33c429a6d7be9d174ba1996d9a0193 Reviewed-on: https://cl.tvl.fyi/c/depot/+/5143 Reviewed-by: grfn <grfn@gws.fyi> Reviewed-by: sterni <sternenseemann@systemli.org> Tested-by: BuildkiteCI Autosubmit: tazjin <tazjin@tvl.su>
2022-01-31 12:19:21 +01:00
"nixpkgs": {
"branch": "nixos-unstable",
"description": "Nix Packages collection",
"homepage": "",
"owner": "NixOS",
"repo": "nixpkgs",
chore(3p/sources): Bump channels & overlays * //3p/overlays/tvl: propagate git as a native build input from magit, because magit checks the version of git at load time ever since a recent commit [1]. This check been escalated to a failure in a subsequent commit [2]. The result is that anything require-ing magit will fail with an error if git is not in PATH (or a path to git provided) which is basically what happens in byte compilation of all packages that depend on magit. For now the easiest way to work around it is letting magit have its way and provide git which easy enough for it. Upstream should probably think about this behaviour or emacs-overlay address it somehow. For now I've opened an issue with magit [3]. [1]: https://github.com/magit/magit/commit/6c4ff54a0836985fac6d72c7e4bfeff964775efe [2]: https://github.com/magit/magit/commit/8394f0d4ea5ffa6858db314efabe91d99f78e67a [3]: https://github.com/magit/magit/issues/4614 Change-Id: I6aaf8258c3798b76cdaa6eef066c6224e374e02e Reviewed-on: https://cl.tvl.fyi/c/depot/+/5326 Autosubmit: sterni <sternenseemann@systemli.org> Tested-by: BuildkiteCI Reviewed-by: tazjin <tazjin@tvl.su>
2022-02-26 12:35:45 +01:00
"rev": "7f9b6e2babf232412682c09e57ed666d8f84ac2d",
"sha256": "03nb8sbzgc3c0qdr1jbsn852zi3qp74z4qcy7vrabvvly8rbixp2",
refactor(3p/nixpkgs): Pin nixpkgs sources via niv There's no need for us to reinvent the wheel here. niv pins are in //third_party/sources, and niv commands need to be run with `niv -s third_party/sources/sources.json` to operate on the correct file. Note that niv by default wants to put the loader file in //nix/sources.nix. This file has been moved to //third_party/sources/default.nix which makes niv throw a warning, but everything still works as intended. Change-Id: I2b2a6f8edf33c429a6d7be9d174ba1996d9a0193 Reviewed-on: https://cl.tvl.fyi/c/depot/+/5143 Reviewed-by: grfn <grfn@gws.fyi> Reviewed-by: sterni <sternenseemann@systemli.org> Tested-by: BuildkiteCI Autosubmit: tazjin <tazjin@tvl.su>
2022-01-31 12:19:21 +01:00
"type": "tarball",
chore(3p/sources): Bump channels & overlays * //3p/overlays/tvl: propagate git as a native build input from magit, because magit checks the version of git at load time ever since a recent commit [1]. This check been escalated to a failure in a subsequent commit [2]. The result is that anything require-ing magit will fail with an error if git is not in PATH (or a path to git provided) which is basically what happens in byte compilation of all packages that depend on magit. For now the easiest way to work around it is letting magit have its way and provide git which easy enough for it. Upstream should probably think about this behaviour or emacs-overlay address it somehow. For now I've opened an issue with magit [3]. [1]: https://github.com/magit/magit/commit/6c4ff54a0836985fac6d72c7e4bfeff964775efe [2]: https://github.com/magit/magit/commit/8394f0d4ea5ffa6858db314efabe91d99f78e67a [3]: https://github.com/magit/magit/issues/4614 Change-Id: I6aaf8258c3798b76cdaa6eef066c6224e374e02e Reviewed-on: https://cl.tvl.fyi/c/depot/+/5326 Autosubmit: sterni <sternenseemann@systemli.org> Tested-by: BuildkiteCI Reviewed-by: tazjin <tazjin@tvl.su>
2022-02-26 12:35:45 +01:00
"url": "https://github.com/NixOS/nixpkgs/archive/7f9b6e2babf232412682c09e57ed666d8f84ac2d.tar.gz",
refactor(3p/nixpkgs): Pin nixpkgs sources via niv There's no need for us to reinvent the wheel here. niv pins are in //third_party/sources, and niv commands need to be run with `niv -s third_party/sources/sources.json` to operate on the correct file. Note that niv by default wants to put the loader file in //nix/sources.nix. This file has been moved to //third_party/sources/default.nix which makes niv throw a warning, but everything still works as intended. Change-Id: I2b2a6f8edf33c429a6d7be9d174ba1996d9a0193 Reviewed-on: https://cl.tvl.fyi/c/depot/+/5143 Reviewed-by: grfn <grfn@gws.fyi> Reviewed-by: sterni <sternenseemann@systemli.org> Tested-by: BuildkiteCI Autosubmit: tazjin <tazjin@tvl.su>
2022-01-31 12:19:21 +01:00
"url_template": "https://github.com/<owner>/<repo>/archive/<rev>.tar.gz"
},
"nixpkgs-stable": {
"branch": "nixos-21.11",
"description": "Nix Packages collection",
"homepage": "",
"owner": "NixOS",
"repo": "nixpkgs",
chore(3p/sources): Bump channels & overlays * //3p/overlays/tvl: propagate git as a native build input from magit, because magit checks the version of git at load time ever since a recent commit [1]. This check been escalated to a failure in a subsequent commit [2]. The result is that anything require-ing magit will fail with an error if git is not in PATH (or a path to git provided) which is basically what happens in byte compilation of all packages that depend on magit. For now the easiest way to work around it is letting magit have its way and provide git which easy enough for it. Upstream should probably think about this behaviour or emacs-overlay address it somehow. For now I've opened an issue with magit [3]. [1]: https://github.com/magit/magit/commit/6c4ff54a0836985fac6d72c7e4bfeff964775efe [2]: https://github.com/magit/magit/commit/8394f0d4ea5ffa6858db314efabe91d99f78e67a [3]: https://github.com/magit/magit/issues/4614 Change-Id: I6aaf8258c3798b76cdaa6eef066c6224e374e02e Reviewed-on: https://cl.tvl.fyi/c/depot/+/5326 Autosubmit: sterni <sternenseemann@systemli.org> Tested-by: BuildkiteCI Reviewed-by: tazjin <tazjin@tvl.su>
2022-02-26 12:35:45 +01:00
"rev": "4275a321beab5a71872fb7a5fe5da511bb2bec73",
"sha256": "1p3pn7767ifbg08nmgjd93iqk0z87z4lv29ypalj9idwd3chsm69",
refactor(3p/nixpkgs): Pin nixpkgs sources via niv There's no need for us to reinvent the wheel here. niv pins are in //third_party/sources, and niv commands need to be run with `niv -s third_party/sources/sources.json` to operate on the correct file. Note that niv by default wants to put the loader file in //nix/sources.nix. This file has been moved to //third_party/sources/default.nix which makes niv throw a warning, but everything still works as intended. Change-Id: I2b2a6f8edf33c429a6d7be9d174ba1996d9a0193 Reviewed-on: https://cl.tvl.fyi/c/depot/+/5143 Reviewed-by: grfn <grfn@gws.fyi> Reviewed-by: sterni <sternenseemann@systemli.org> Tested-by: BuildkiteCI Autosubmit: tazjin <tazjin@tvl.su>
2022-01-31 12:19:21 +01:00
"type": "tarball",
chore(3p/sources): Bump channels & overlays * //3p/overlays/tvl: propagate git as a native build input from magit, because magit checks the version of git at load time ever since a recent commit [1]. This check been escalated to a failure in a subsequent commit [2]. The result is that anything require-ing magit will fail with an error if git is not in PATH (or a path to git provided) which is basically what happens in byte compilation of all packages that depend on magit. For now the easiest way to work around it is letting magit have its way and provide git which easy enough for it. Upstream should probably think about this behaviour or emacs-overlay address it somehow. For now I've opened an issue with magit [3]. [1]: https://github.com/magit/magit/commit/6c4ff54a0836985fac6d72c7e4bfeff964775efe [2]: https://github.com/magit/magit/commit/8394f0d4ea5ffa6858db314efabe91d99f78e67a [3]: https://github.com/magit/magit/issues/4614 Change-Id: I6aaf8258c3798b76cdaa6eef066c6224e374e02e Reviewed-on: https://cl.tvl.fyi/c/depot/+/5326 Autosubmit: sterni <sternenseemann@systemli.org> Tested-by: BuildkiteCI Reviewed-by: tazjin <tazjin@tvl.su>
2022-02-26 12:35:45 +01:00
"url": "https://github.com/NixOS/nixpkgs/archive/4275a321beab5a71872fb7a5fe5da511bb2bec73.tar.gz",
refactor(3p/nixpkgs): Pin nixpkgs sources via niv There's no need for us to reinvent the wheel here. niv pins are in //third_party/sources, and niv commands need to be run with `niv -s third_party/sources/sources.json` to operate on the correct file. Note that niv by default wants to put the loader file in //nix/sources.nix. This file has been moved to //third_party/sources/default.nix which makes niv throw a warning, but everything still works as intended. Change-Id: I2b2a6f8edf33c429a6d7be9d174ba1996d9a0193 Reviewed-on: https://cl.tvl.fyi/c/depot/+/5143 Reviewed-by: grfn <grfn@gws.fyi> Reviewed-by: sterni <sternenseemann@systemli.org> Tested-by: BuildkiteCI Autosubmit: tazjin <tazjin@tvl.su>
2022-01-31 12:19:21 +01:00
"url_template": "https://github.com/<owner>/<repo>/archive/<rev>.tar.gz"
chore(3p/rustsec-advisory-db): track using niv This will make sure that the db is updated regularly (on every channel bump). This is fine, because an advisory no longer implies a build failure. Change-Id: I1dc0b335e0881b5c58015da63c3c47f1ab1e645f Reviewed-on: https://cl.tvl.fyi/c/depot/+/4554 Tested-by: BuildkiteCI Reviewed-by: tazjin <tazjin@tvl.su>
2021-12-24 12:24:04 +01:00
},
"rustsec-advisory-db": {
"branch": "main",
"description": "Security advisory database for Rust crates published through crates.io",
"homepage": "https://rustsec.org",
"owner": "RustSec",
"repo": "advisory-db",
chore(3p/sources): Bump channels & overlays * //3p/overlays/tvl: propagate git as a native build input from magit, because magit checks the version of git at load time ever since a recent commit [1]. This check been escalated to a failure in a subsequent commit [2]. The result is that anything require-ing magit will fail with an error if git is not in PATH (or a path to git provided) which is basically what happens in byte compilation of all packages that depend on magit. For now the easiest way to work around it is letting magit have its way and provide git which easy enough for it. Upstream should probably think about this behaviour or emacs-overlay address it somehow. For now I've opened an issue with magit [3]. [1]: https://github.com/magit/magit/commit/6c4ff54a0836985fac6d72c7e4bfeff964775efe [2]: https://github.com/magit/magit/commit/8394f0d4ea5ffa6858db314efabe91d99f78e67a [3]: https://github.com/magit/magit/issues/4614 Change-Id: I6aaf8258c3798b76cdaa6eef066c6224e374e02e Reviewed-on: https://cl.tvl.fyi/c/depot/+/5326 Autosubmit: sterni <sternenseemann@systemli.org> Tested-by: BuildkiteCI Reviewed-by: tazjin <tazjin@tvl.su>
2022-02-26 12:35:45 +01:00
"rev": "0ff38eb722fac2ef0f0f353b4775580bfd2067db",
"sha256": "1xqlgc8fyv927v4khxbhmv5391r02a0zk3jnmrm1g30lsdhvxs69",
chore(3p/rustsec-advisory-db): track using niv This will make sure that the db is updated regularly (on every channel bump). This is fine, because an advisory no longer implies a build failure. Change-Id: I1dc0b335e0881b5c58015da63c3c47f1ab1e645f Reviewed-on: https://cl.tvl.fyi/c/depot/+/4554 Tested-by: BuildkiteCI Reviewed-by: tazjin <tazjin@tvl.su>
2021-12-24 12:24:04 +01:00
"type": "tarball",
chore(3p/sources): Bump channels & overlays * //3p/overlays/tvl: propagate git as a native build input from magit, because magit checks the version of git at load time ever since a recent commit [1]. This check been escalated to a failure in a subsequent commit [2]. The result is that anything require-ing magit will fail with an error if git is not in PATH (or a path to git provided) which is basically what happens in byte compilation of all packages that depend on magit. For now the easiest way to work around it is letting magit have its way and provide git which easy enough for it. Upstream should probably think about this behaviour or emacs-overlay address it somehow. For now I've opened an issue with magit [3]. [1]: https://github.com/magit/magit/commit/6c4ff54a0836985fac6d72c7e4bfeff964775efe [2]: https://github.com/magit/magit/commit/8394f0d4ea5ffa6858db314efabe91d99f78e67a [3]: https://github.com/magit/magit/issues/4614 Change-Id: I6aaf8258c3798b76cdaa6eef066c6224e374e02e Reviewed-on: https://cl.tvl.fyi/c/depot/+/5326 Autosubmit: sterni <sternenseemann@systemli.org> Tested-by: BuildkiteCI Reviewed-by: tazjin <tazjin@tvl.su>
2022-02-26 12:35:45 +01:00
"url": "https://github.com/RustSec/advisory-db/archive/0ff38eb722fac2ef0f0f353b4775580bfd2067db.tar.gz",
chore(3p/rustsec-advisory-db): track using niv This will make sure that the db is updated regularly (on every channel bump). This is fine, because an advisory no longer implies a build failure. Change-Id: I1dc0b335e0881b5c58015da63c3c47f1ab1e645f Reviewed-on: https://cl.tvl.fyi/c/depot/+/4554 Tested-by: BuildkiteCI Reviewed-by: tazjin <tazjin@tvl.su>
2021-12-24 12:24:04 +01:00
"url_template": "https://github.com/<owner>/<repo>/archive/<rev>.tar.gz"
refactor(3p/nixpkgs): Pin nixpkgs sources via niv There's no need for us to reinvent the wheel here. niv pins are in //third_party/sources, and niv commands need to be run with `niv -s third_party/sources/sources.json` to operate on the correct file. Note that niv by default wants to put the loader file in //nix/sources.nix. This file has been moved to //third_party/sources/default.nix which makes niv throw a warning, but everything still works as intended. Change-Id: I2b2a6f8edf33c429a6d7be9d174ba1996d9a0193 Reviewed-on: https://cl.tvl.fyi/c/depot/+/5143 Reviewed-by: grfn <grfn@gws.fyi> Reviewed-by: sterni <sternenseemann@systemli.org> Tested-by: BuildkiteCI Autosubmit: tazjin <tazjin@tvl.su>
2022-01-31 12:19:21 +01:00
}
}
Reference in a new issue Copy permalink