-
-
Notifications
You must be signed in to change notification settings - Fork 15.3k
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
systemd: v243.3 -> v243.4 #74207
systemd: v243.3 -> v243.4 #74207
Conversation
@@ -36,10 +36,10 @@ in stdenv.mkDerivation { | |||
# When updating, use https://github.com/systemd/systemd-stable tree, not the development one! | |||
# Also fresh patches should be cherry-picked from that tree to our current one. | |||
src = fetchFromGitHub { | |||
owner = "NixOS"; | |||
owner = "flokli"; |
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.
I'll push this to NixOS/systemd
(and change back the expression) once everybody agrees with the changes there.
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.
The commit should be reachable through the NixOS repo as well as long as it exists somewhere in the fork network, so this shouldn't even be necessary. (Here this feature is convenient, but it can also be bad, see e.g. 7b4c9e9d012)
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.
Yes, I know. Still, I want to push it properly.
IF you are referring to flokli/systemd@cc103c7 then that shouldn't matter for us since we disabled manual changing of timezones anyway. In general please provide links to those places that did have to be manually changed instead of sending people on a hunt when asking for feedback. GitHub is terrible at displaying merges and which commits were introduced in which merge.... |
Yes, that was what I meant, and I agree it shouldn't matter for NixOS. |
Only if time.timeZone is set! Otherwise timezones can still be set using |
I'm not sure if this is properly supported at all. Does this mean this PR should be done differently? |
Well, it's worked since #26608 ;)
I'm not sure, haven't looked at the actual code yet. I just wanted to correct the assumption that the timezone is always fixed on nixos for now :) EDIT: Just saw that I introduced a test with the change, so if nixos/tests/timezone.nix still passes it should all be good. |
This breaks |
@lheckemann ping ;-) |
@lheckemann ping ;-) |
mayflower/systemd@17b4843 fixes it, should probably be squashed into flokli/systemd@cc103c7 with a corresponding explanation |
@lheckemann feel free to prepare another branch at github.com/mayflower/systemd and take over this PR - I think you know best how to wire this into the existing commit history ;-) |
closing in favour of #76134. |
This bumps
systemd
to thev243.4
stable release.#74026 already bumped to
243.3
, but that was not sufficient enough to include the fixes mentioned in #73504 (comment).I'd appreciate some thorough looks, especially given upstream also did some changes in
src/timedate/timedated.c
, which had to be treated manually while merging in thev243.4
branch.Things done
sandbox
innix.conf
on non-NixOS linux)nix-shell -p nix-review --run "nix-review wip"
./result/bin/
)nix path-info -S
before and after)