Commit Graph

10 Commits

Author SHA1 Message Date
stefan
2e384ab387 bugstalker: 0.3.1 -> 0.4.1
Diff: https://github.com/godzie44/BugStalker/compare/v0.3.1...v0.4.1
Changelog: https://github.com/godzie44/BugStalker/blob/v0.4.1/CHANGELOG.md
2026-01-22 11:30:17 -08:00
TomaSajt
398b16e16c treewide: remove useFetchCargoVendor usages 2025-07-26 11:39:35 +02:00
Peder Bergebakken Sundt
13fb53529f bugstalker: 0.3.0 -> 0.3.1
Diff: https://github.com/godzie44/BugStalker/compare/v0.3.0...v0.3.1
2025-06-04 17:20:02 +02:00
emaryn
e25a1f4f1d bugstalker: 0.2.2 -> 0.3.0
Diff: https://github.com/godzie44/BugStalker/compare/v0.2.2...v0.3.0
2025-04-26 02:24:20 +08:00
Winter
a19cd4ffb1 Revert "treewide: replace rev with tag"
This reverts commit 65a333600d.

This wasn't tested for correctness with something like fodwatch [0],
and should not have been (self-)merged so quickly, especially without
further review.

It also resulted in the breakage of at least one package [1] (and that's
the one we know of and was caught).

A few packages that were updated in between this commit and this revert
were not reverted back to using `rev`, but other than that, this is a
1:1 revert.

[0]: https://codeberg.org/raphaelr/fodwatch
[1]: https://github.com/NixOS/nixpkgs/pull/396904 / 758551e458
2025-04-08 02:57:25 -04:00
Pol Dellaiera
65a333600d treewide: replace rev with tag 2025-04-07 16:57:22 +02: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
Silvan Mosberger
667d42c00d 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 57b193d8dd
    result/bin/apply-formatting $NIXPKGS_PATH
2024-12-10 20:27:17 +01:00
Alyssa Ross
e639bd4516 bugstalker: 0.1.4 -> 0.2.2
Required to build with Rust 1.80.

Link: https://github.com/rust-lang/rust/issues/127343
2024-08-14 13:37:32 +02:00
Jacek Generowicz
118da49d1a bugstalker: init at 0.1.4 (#306479)
* bugstalker: init at 0.1.4

* Enable checks which don't fail in the sandbox

66 tests which pass in a normal development environment fail in the
sandbox because of "file not found". I think that this is because they
are trying to find the source code of the examples, but I haven't found
a way of investigating this interactively in the sandbox, it's very
difficult to get to the bottom of it.

So, for now, I have simply disabled the tests that fail in the sandbox.
2024-05-12 01:41:19 +08:00