Skip to content

flake.lock: Update#903

Merged
Mic92 merged 1 commit intomasterfrom
update_flake_lock_action
Dec 12, 2024
Merged

flake.lock: Update#903
Mic92 merged 1 commit intomasterfrom
update_flake_lock_action

Conversation

@github-actions
Copy link
Copy Markdown
Contributor

@github-actions github-actions bot commented Nov 28, 2024

Automated changes by the update-flake-lock GitHub Action.

Flake lock file updates:

• Updated input 'nixpkgs':
    'github:NixOS/nixpkgs/8edf06bea5bcbee082df1b7369ff973b91618b8d?narHash=sha256-sQxuJm8rHY20xq6Ah%2BGwIUkF95tWjGRd1X8xF%2BPkk38%3D' (2024-11-22)
  → 'github:NixOS/nixpkgs/bc27f0fde01ce4e1bfec1ab122d72b7380278e68?narHash=sha256-%2B5qdtgXceqhK5ZR1YbP1fAUsweBIrhL38726oIEAtDs%3D' (2024-12-09)

Running GitHub Actions on this PR

GitHub Actions will not run workflows on pull requests which are opened by a GitHub Action.

To run GitHub Actions workflows on this PR, run:

git branch -D update_flake_lock_action
git fetch origin
git checkout update_flake_lock_action
git commit --amend --no-edit
git push origin update_flake_lock_action --force

iFreilicht added a commit that referenced this pull request Nov 30, 2024
Fixes #900

This was caused by NixOS/nixpkgs#354535
originally. The breaking changes introduced there have been resolved by
NixOS/nixpkgs#360413, but one addition survived,
which was the line `source $stdenv/setup`.

Because we used `>` instead of `>>`, `saved-env` was overwritten, so
even with the second PR, the script failed with the following error:

    /nix/store/pw...ykc-vm-run-stage2: line 16: stdenv: unbound variable

Once this and the second PR mentioned above are merged, #903 will be
unblocked.
@github-actions github-actions bot force-pushed the update_flake_lock_action branch from 12995c6 to a0eedc2 Compare December 2, 2024 01:52
@iFreilicht
Copy link
Copy Markdown
Contributor

@Mic92 I added a commit yesterday to fix the jsonTypes check, but it has vanished. Should I submit that as a separate PR instead?

@Mic92
Copy link
Copy Markdown
Member

Mic92 commented Dec 2, 2024

@iFreilicht sounds like a good idea. You can still find it here: 12995c6

@github-actions github-actions bot force-pushed the update_flake_lock_action branch 2 times, most recently from 92cd4d6 to b4ea777 Compare December 9, 2024 01:53
@mergify
Copy link
Copy Markdown
Contributor

mergify bot commented Dec 9, 2024

This pull request has been removed from the queue for the following reason: pull request manually updated.

The pull request #903 has been manually updated.

You should look at the reason for the failure and decide if the pull request needs to be fixed or if you want to requeue it.

If you want to requeue this pull request, you need to post a comment with the text: @mergifyio requeue

Flake lock file updates:

• Updated input 'nixpkgs':
    'github:NixOS/nixpkgs/8edf06bea5bcbee082df1b7369ff973b91618b8d?narHash=sha256-sQxuJm8rHY20xq6Ah%2BGwIUkF95tWjGRd1X8xF%2BPkk38%3D' (2024-11-22)
  → 'github:NixOS/nixpkgs/bc27f0fde01ce4e1bfec1ab122d72b7380278e68?narHash=sha256-%2B5qdtgXceqhK5ZR1YbP1fAUsweBIrhL38726oIEAtDs%3D' (2024-12-09)
@github-actions github-actions bot force-pushed the update_flake_lock_action branch from b4ea777 to 9c74188 Compare December 12, 2024 01:50
@mergify
Copy link
Copy Markdown
Contributor

mergify bot commented Dec 12, 2024

This pull request has been removed from the queue for the following reason: pull request manually updated.

The pull request #903 has been manually updated.

You should look at the reason for the failure and decide if the pull request needs to be fixed or if you want to requeue it.

If you want to requeue this pull request, you need to post a comment with the text: @mergifyio requeue

@Mic92 Mic92 merged commit 0f31ad7 into master Dec 12, 2024
@Mic92 Mic92 deleted the update_flake_lock_action branch December 12, 2024 13:46
@mergify
Copy link
Copy Markdown
Contributor

mergify bot commented Dec 12, 2024

This pull request has been removed from the queue for the following reason: pull request dequeued.

Pull request #903 has been dequeued. The pull request has been merged manually. The pull request has been merged manually at 0f31ad7.

You should look at the reason for the failure and decide if the pull request needs to be fixed or if you want to requeue it.

If you want to requeue this pull request, you need to post a comment with the text: @mergifyio requeue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants