-
-
Notifications
You must be signed in to change notification settings - Fork 15.4k
openafs: 1.8.6 → 1.8.7 (emergency fix for unix timestamp 0x60000000) #109428
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
Conversation
Signed-off-by: Anders Kaseorg <andersk@mit.edu>
We should probably consider backporting this to 20.09. |
Result of 12 packages marked as broken and skipped:
1 package failed to build:
14 packages built:
|
linux-libre is broke on its own. So this looks good to me. |
Backported however we use openafs 1.6 by default and 1.8 is a package user can choose instead. Can someone write an announcement to update to 1.8 on 20.09 or to make 1.8 default in 20.09? |
Where would be a fitting place for such an announcement? Still the release notes? |
Anyhow, openafs_1_6 is already marked broken in 20.09. So, the few users that still forced openafs_1_6 will be aware of immanent problems. So, I think we are all set up. |
Backport in 3403628. |
Motivation for this change
This fixes a critical upstream issue with OpenAFS clients started after 14 Jan 2021 08:25:36 AM UTC (Unix epoch time 0x60000000). See https://lists.openafs.org/pipermail/openafs-announce/2021/000539.html.
Things done
sandbox
innix.conf
on non-NixOS linux)nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
./result/bin/
)nix path-info -S
before and after)