-
-
Notifications
You must be signed in to change notification settings - Fork 14.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
go1.16: remove #168480
go1.16: remove #168480
Conversation
Result of 3 packages marked as broken and skipped:
17 packages built:
|
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 see a lot of packages here that have go references removed without corresponding package bumps - have you verified that the software still works with newer go versions? (beyond just building?)
@@ -11,7 +11,15 @@ buildGoModule rec { | |||
sha256 = "1lanighxhnn28dfzils7i55zgxbw2abd6y723mq7x9wg1aa2bd0z"; | |||
}; | |||
|
|||
vendorSha256 = "04nywhkil5xkipcibrp6vi63rfcvqgv7yxbxmmrhqys2cdxfvazv"; | |||
patches = [ |
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.
we should wait for a release or use an untagged commit - randomly pulling in patches sucks for everyone.
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.
There isn't one, yet. We can wait, but then we'll need to keep this EOL go release around.
@@ -120,5 +120,7 @@ in buildBazelPackage rec { | |||
license = licenses.asl20; | |||
maintainers = with maintainers; [ andrew-d ]; | |||
platforms = [ "x86_64-linux" ]; | |||
# the version we have right now does not compile with go 1.17 | |||
broken = true; |
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.
latest builds with go1.17 - lets bump before landing this PR. https://github.com/google/gvisor/blob/master/go.mod#L3
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.
Can you bump it? I think I tried and it was non-trivial. IMO this is the maintainer's (@andrew-d) job not ours.
The release is ~10 months out of date, with a software that releases very often, looking at https://github.com/google/gvisor/tags.
}; | ||
|
||
patches = [ | ||
(fetchpatch { | ||
url = "https://github.com/dinedal/textql/commit/a0d7038c8c30671dfd618f47322814ab492c11a1.patch"; |
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.
This is a commit from a fork - we should reference it via the fork to avoid confusion and to be explicit.
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.
done
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.
we should reference it via the fork
Revert this change. If the fork is deleted the patch will disappear. Please add a comment linking the PR the commit came from.
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.
It'll be in the binary cache either way, so I don't really care, tbh.
The same diff can be gotten many ways, so how can we find a consensus here? I assume nixpkgs doesn't have a policy for this, despite there being dozens if not hundreds of occurrences of this throughout the codebase, as always?
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.
Using a source that won't disappear instead of one that may disappear seems link a better idea.
I've seen lots of reviews asking for a comment referencing the PR that a commit is sourced from, I haven't seen anyone ask that we actually use the PR authors fork to source the commits.
iirc I've tested ones with tests, e.g. ncdns |
This breaks ipfs-migrator-all-fs-repo-migrations. See #161547, where I tested this and documented it in the PR description and commit message. Feel free to test this again as described in the commit message. Also see ipfs/fs-repo-migrations#156, which I just created. Please also run the IPFS NixOS test. Go 1.17 support seems to still be in progress: ipfs/kubo#8815. |
so |
See ipfs/kubo#8815 for why the currently existing migrations probably won't be updated to support a newer Go version. This means, we either need to keep Go 1.16 or remove the incompatible migrations. In the second case I could write a stub to replace them, which prints some text, explaining the situation. |
@Luflosi can you go ahead and do that? go1.16 is EOL and I'd very much like to see it removed before branch-off. |
I'd like to remind the people here that branch-off is scheduled for tomorrow and depending on how good the staging builds progress, we will branch off rather soon. |
This reverts commit cee6ccf.
51cda9a
to
8a51267
Compare
@@ -30,7 +30,8 @@ buildGoModule { | |||
description = "A high-performance, POSIX-ish Amazon S3 file system written in Go."; | |||
license = [ lib.licenses.mit ]; | |||
maintainers = [ lib.maintainers.adisbladis ]; | |||
broken = stdenv.isDarwin; # needs to update gopsutil to at least v3.21.3 to include https://github.com/shirou/gopsutil/pull/1042 | |||
# does not build with go 1.17 | |||
broken = true; |
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.
ping @adisbladis , I don't think you've been notified?
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.
Thanks for the ping. Fixed in #176255.
Description of changes
go1.16 reached EOL with the release of go1.18
Things done
sandbox = true
set innix.conf
? (See Nix manual)nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD"
. Note: all changes have to be committed, also see nixpkgs-review usage./result/bin/
)nixos/doc/manual/md-to-db.sh
to update generated release notes