qo.is/infrastructure
4
0
Fork 0
Code Issues 13 Pull requests 1 Projects 1 Activity Actions

chore(deps): lock file maintenance #78

Merged
renovate merged 2 commits from renovate/lock-file-maintenance into main 2025-06-25 22:57:17 +02:00
Conversation 7 Commits 2 Files changed 3 +17 -34
renovate commented 2025-06-20 18:10:21 +02:00
Member
Copy link

This PR contains the following updates:

Update Change
lockFileMaintenance All locks refreshed

🔧 This Pull Request updates lock files to use the latest dependency versions.

Configuration

📅 Schedule: Branch creation - "* 18-19 * * *" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

  • If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

This PR contains the following updates: | Update | Change | |---|---| | lockFileMaintenance | All locks refreshed | 🔧 This Pull Request updates lock files to use the latest dependency versions. --- ### Configuration 📅 **Schedule**: Branch creation - "* 18-19 * * *" (UTC), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Enabled. ♻ **Rebasing**: Whenever PR is behind base branch, or you tick the rebase/retry checkbox. 👻 **Immortal**: This PR will be recreated if closed unmerged. Get [config help](https://github.com/renovatebot/renovate/discussions) if that's undesired. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzOC4xMDUuMiIsInVwZGF0ZWRJblZlciI6IjM4LjEwNS4yIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6W119-->
renovate added 1 commit 2025-06-20 18:10:22 +02:00
chore(deps): lock file maintenance
Some checks failed
CI / build (push) Failing after 3m29s
Details
CI / deploy (docs-ops.qo.is) (push) Has been skipped
Details
CI / deploy (system-physical) (push) Has been skipped
Details
CI / deploy (system-vm) (push) Has been skipped
Details
3295f6f128
renovate scheduled this pull request to auto merge when all checks succeed 2025-06-20 18:10:22 +02:00
renovate commented 2025-06-20 18:10:22 +02:00
Author
Member
Copy link

Branch automerge failure

This PR was configured for branch automerge. However, this is not possible, so it has been raised as a PR instead.

  • Branch has one or more failed status checks
### Branch automerge failure This PR was configured for branch automerge. However, this is not possible, so it has been raised as a PR instead. ___ * Branch has one or more failed status checks
das-g commented 2025-06-21 11:45:33 +02:00
Owner
Copy link

Fails on Hydra, too: https://hydra.nixos.org/build/300013420

Fails on Hydra, too: https://hydra.nixos.org/build/300013420
das-g commented 2025-06-22 01:39:58 +02:00
Owner
Copy link

I've now filed a NixPkgs build failure report: https://github.com/NixOS/nixpkgs/issues/418867

I've now filed a NixPkgs build failure report: https://github.com/NixOS/nixpkgs/issues/418867
das-g commented 2025-06-22 10:32:28 +02:00
Owner
Copy link

https://github.com/NixOS/nixpkgs/pull/418926 fixes the issue. Should we

  • wait for that to hit nixos-unstable
    or
  • (temporarily) bump our nixpkgs input to the fix revision a9d546262893acd54ba13733f5a59a668ecd0a1d
    or
  • (temporarily) patch nixos-unstable with the fix change for our nixpkgs input
    or
  • use a temporary overlay

?

https://github.com/NixOS/nixpkgs/pull/418926 fixes the issue. Should we - wait for that to hit `nixos-unstable` or - (temporarily) bump our nixpkgs input to the fix revision `a9d546262893acd54ba13733f5a59a668ecd0a1d` or - (temporarily) patch `nixos-unstable` with the fix change for our nixpkgs input or - use a temporary overlay ?
raphiz commented 2025-06-22 10:47:18 +02:00
Owner
Copy link

Thanks for the investigations and the issue. Another fix for us would be to use the version from 25.05 (upgrading is something we must do anyhow someday) - i don't think we aleays need the unstable version, right?

Thanks for the investigations and the issue. Another fix for us would be to use the version from 25.05 (upgrading is something we must do anyhow someday) - i don't think we aleays need the unstable version, right?
das-g commented 2025-06-22 13:04:13 +02:00
Owner
Copy link

@raphiz wrote in #78 (comment):

use the version from 25.05

That's also a possibility, either for the whole system or for that package specifically.

(upgrading is something we must do anyhow someday)

That'd be a downgrade though, as unstable is always what will eventually become the next release (thus currently what will become 25.11). Shouldn't be a problem, as security fixes should all get backported to the newest released release, but something to be aware of.

@raphiz wrote in https://git.qo.is/qo.is/infrastructure/pulls/78#issuecomment-464: > use the version from 25.05 That's also a possibility, either for the whole system or for that package specifically. > (upgrading is something we must do anyhow someday) That'd be a *down*grade though, as unstable is always what will eventually become the _next_ release (thus currently what will become 25.11). Shouldn't be a problem, as security fixes should all get backported to the newest released release, but something to be aware of.
fabianhauser added 1 commit 2025-06-25 22:53:13 +02:00
Replace nixpkgs with stable and update inputs
Some checks failed
CI / build (push) Failing after 1m25s
Details
CI / deploy (docs-ops.qo.is) (push) Has been skipped
Details
CI / deploy (system-physical) (push) Has been skipped
Details
CI / deploy (system-vm) (push) Has been skipped
Details
e76a4f04cc
renovate merged commit e76a4f04cc into main 2025-06-25 22:57:17 +02:00
fabianhauser commented 2025-06-25 23:01:43 +02:00
Owner
Copy link

I switched everything to nixpkgs stable (24.11 for now). Seems the reason we had - a nix version that did not properly support git submodules - was resolved in the meantime.

I switched everything to nixpkgs stable (24.11 for now). Seems the reason we had - a `nix` version that did not properly support git submodules - was resolved in the meantime.
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
bug

Something is not working

  
duplicate

This issue or pull request already exists

  
enhancement

New feature

  
help wanted

Need some help

  
invalid

Something is wrong

  
question

More information is needed

  
urgent

This issue should be tackled soon

  
wontfix

This won't be fixed

No labels
bug
duplicate
enhancement
help wanted
invalid
question
urgent
wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
4 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: qo.is/infrastructure#78
No description provided.
Delete branch "renovate/lock-file-maintenance"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?