Commit Graph

10 Commits

Author SHA1 Message Date
Lu Wang
01af1af262 dmlive: 5.6.0-unstable-2025-06-21 -> 5.7.0-unstable-2026-01-02
Diff: 485eae0673...47b06e57fc
2026-01-02 16:12:31 +08:00
TomaSajt
398b16e16c treewide: remove useFetchCargoVendor usages 2025-07-26 11:39:35 +02:00
Lu Wang
dd6e5a497c dmlive: 5.5.8-unstable-2025-04-06 -> 5.6.0-unstable-2025-06-21
Diff: b066a63709...485eae0673
2025-06-27 08:24:21 +08:00
Lu Wang
c8c153cdfc dmlive: 5.5.7-unstable-2025-01-25 -> 5.5.8-unstable-2025-04-06
Diff: 79b4d9430f...b066a63709
2025-04-18 03:19:53 +08:00
A1ca7raz
06309a1c6c dmlive: add mime desktop 2025-02-26 14:20:31 +08:00
A1ca7raz
172ad3c95a dmlive: use ffmpeg_6 2025-02-24 02:47:56 +08:00
Nick Cao
209af06ac7 dmlive: 5.5.4 -> 5.5.7-unstable-2025-01-25
Diff: 688ddda12e...79b4d9430f
2025-02-22 11:09:29 -05:00
Alyssa Ross
63bff8c132 treewide: migrate to fetchCargoVendor, batch 1
Cargo 1.84.0 seems to have changed the output format of cargo vendor
again, once again invalidating fetchCargoTarball FOD hashes.  It's
time to fix this once and for all, switching across the board to
fetchCargoVendor, which is not dependent on cargo vendor's output
format.

It should be possible to reproduce this diff.  To do so, get the list
of files changed by this commit, e.g. with git diff --name-only, then
run the following two commands, each with that list of files as their
standard input:

	xargs sed -i 's/^\(. *\)\(cargoHash\)\b/\1useFetchCargoVendor = true;\n\1cargoHash/'
	cut -d / -f 4 | xargs -n 1 nix-update --version=skip

This will take a long time.  It might be possible to parallelize it
using xargs' -P option.  I haven't tested it.
2025-01-23 11:46:43 +01:00
Nick Cao
9b275ff032 dmlive: format with nixfmt 2024-11-07 13:42:26 -05:00
Nick Cao
7f271a2a68 dmlive: move to by-name 2024-11-07 13:42:25 -05:00