-
-
Notifications
You must be signed in to change notification settings - Fork 14.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[staging] merge from staging-next #370761
Conversation
Fixes the following in server.log: <launcher> ERROR sdnotify - failed to load ubnt_sdnotify_jni java.lang.UnsatisfiedLinkError: /var/lib/unifi/lib/native/Linux/x86_64/libubnt_sdnotify_jni.so: libsystemd.so.0: cannot open shared object file: No such file or directory
Let's use unifi's sd_notify now that it's patched
This allows the controller to restart when restoring from a backup
Currently users upgrading from 24.05 to 24.11 may stumble across an overly-restrictive BaseURL and ServerURL check in headscale[1]. A fix has been merged upstream[2], this is backport, so users can have it easier upgrading from 24.05 to 24.11 or unstable. The patch does not apply cleanly on v0.23.0, so putting it here instead. Supersedes NixOS#357969, this will be backported to 24.11 with a tag. [1]: juanfont/headscale#2210 [2]: juanfont/headscale#2248
This program wants to call `env rofi`, however when pinentry-rofi is configured as the pinentry program for gpg-agent via a systemd service, these dependencies might not be available in the service's PATH.
Also removes unused `rec`.
Add patches for bundled libraries (rnp and libsexpp) to handle clang 19 lack of char_traits for unsigned char.
…onflict-1735949935
The PR's base branch is set to staging, but 144 commits from the master branch are included. Make sure you know the right base branch for your changes, then:
|
(We tend to push these directly because GitHub is… like this, and our CI isn’t great at handling it either. Though I do wish we had a way of doing proper review.) |
I thought |
The PR's base branch is set to staging, but 144 commits from the master branch are included. Make sure you know the right base branch for your changes, then:
|
For force pushes I expect so, but people regularly make direct commits to |
(Anyway the Gist looks good to me, and I even maintain some of those packages. I’d make this a proper approval but clicking the tab I need to be on for that makes my browser die.) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My browser is too powerful to be stopped by a mere 3000 changes
cc @mweinelt about the fix for the botched |
huh, i was working out a git fetch upstream staging
git fetch upstream staging-next
git worktree add ../fix/merge-conflict upstream/staging
cd ../fix/merge-conflict
git checkout -b fix-merge-conflict --track upstream/staging
git merge upstream/staging-next
# do fixes
git commit
git push What do you commonly do @emilazy? |
I think people usually just do the very basic |
It's wrong. |
fixes https://github.com/NixOS/nixpkgs/actions/runs/12605651116
caused by #368177
manual fixes: https://gist.github.com/pbsds/d417f0759e75ec34b81f389efa564fd0
of interest is
pkgs/development/python-modules/music-assistant-models/default.nix
which was migrated totag
incorrectlyThings done
nix.conf
? (See Nix manual)sandbox = relaxed
sandbox = true
nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD"
. Note: all changes have to be committed, also see nixpkgs-review usage./result/bin/
)Add a 👍 reaction to pull requests you find important.