Commit Graph

8 Commits

Author SHA1 Message Date
Weijia Wang
1d3a9a9601 invidious: fix build on aarch64-darwin 2022-12-11 20:17:49 +01:00
schnusch
9a1264cab0 invidious.lsquic.boringssl: fix gcc11 build 2022-05-16 23:12:06 +02:00
squalus
728b0c81fe invidious: fix build
The build was broken since 52f8cf58a4 when
gcc was updated from 10 to 11. This forces lsquic's version of boringssl
to build with gcc 10.
2022-05-12 17:08:36 -07:00
Silvan Mosberger
ada1ed885c
Merge pull request #150898 from schnusch/invidious
invidious: unstable-2021-11-08 -> unstable-2022-03-16
2022-03-17 23:50:00 +01:00
schnusch
a4811f1fa3 invidious: move versions, revs and sha256s to JSON file
This way updating these values is much less hacky. A downside is that tools
like nix-update will no longer be able to update these, but this should not
be too important for invidious.
2022-03-16 16:20:42 +01:00
Vikram Narayanan
ed3cfc8abe invidious/lsquic: fix build 2021-11-26 22:21:55 -08:00
Simon Bruder
970d249d39
invidious: unstable-2021-11-08 -> unstable-2021-11-13
This update disables QUIC by default which fixes Invidious not loading
anything except for the home page due to YouTube no longer accepting
HTTP/3 (Upstream Issue:
https://github.com/iv-org/invidious/issues/2577).

It therefore uses Crystal’s internal HTTP client, which failed because
the statically linked boringssl (required by lsquic) overrides OpenSSL’s
CA certificate file location. This is fixed by applying the same patch
to boringssl that is applied to openssl for using the correct CA
certificate file.
2021-11-14 10:07:09 +01:00
Silvan Mosberger
c5286421bc
invidious: init at unstable-2021-10-15
This also adds a derivation for lsquic, but places it inside invidious’
directory. That is because lsquic.cr (the library used by invidious)
requires a specific lsquic version that is probably not useful for other
derivations.

Co-authored-by: Simon Bruder <simon@sbruder.de>
2021-10-30 16:33:22 +02:00