You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
(The nixpkgs-update cache is only trusted for this store-path realization.)
For the cached download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A nushell https://github.com/r-ryantm/nixpkgs/archive/dd13071e31e02934e7307229747e64194ee12812.tar.gz
After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/rmdsw85vh8cd31aaa9axcndm6g1f3kh0-nushell-0.110.0
ls -la /nix/store/rmdsw85vh8cd31aaa9axcndm6g1f3kh0-nushell-0.110.0/bin
Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.
I'd like to use the opportunity to rise the question, what is keeping us from moving nushell from pkgs/shells to pkgs/by-name? It might probably worth it's own discussion and PR if the pkgs/shells dir might be worth getting dissolved at all, as it only contains bash, fish and nushell but no other shell.
And nushell would be tremendously helpful to become mergable by bot imo.
it never clicked for me it's just those three in there, having nushell moved to pkgs/by-name would be a huge boon for not letting plugins fall behind every other cycle.
I'm not familiar with how a decision is made in this repo but I'd +1 for moving.
after a quick chat on discord (thanks to the ever helpful NobbZ) it seems to deprecate the pkgs/shells dir at all requires patience until some process reaches a stage where a treewide move of packages might happen. But since nushell suffers from lagging on updates we could use the opportunity of this version bump to move it now.
I could open a PR for this unless any of the package maintainers desires to do this themselves.
Edit: just found this PR taking care of which proposes a different approach for the plugins: #482543, but it would not be compatible with bot-handled merges off the bat, so I guess it is more of a long run solution when the bot gains more abilities.
I think it would be great if you could get a draft PR going for this. Until the big migration happens and the merge bot gets possibly updated to handle pkgs/sets, it'd be a good stop-gap. Should we tag the other plugin maintainers for their opinions as well?
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
nixpkgs-ci
bot
added
10.rebuild-linux: 11-100
Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for nushell is: Modern shell written in Rust
meta.homepage for nushell is: https://www.nushell.sh/
Updates performed
To inspect upstream changes
Impact
Checks done
passthru.tests, if any, passedRebuild report (if merged into master) (click to expand)
Instructions to test this update (click to expand)
Either download from the cache:
(The nixpkgs-update cache is only trusted for this store-path realization.)
For the cached download to work, your user must be in the
trusted-userslist or you can usesudosince root is effectively trusted.Or, build yourself:
Or:
After you've downloaded or built it, look at the files and if there are any, run the binaries:
Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
nixpkgs-reviewresultGenerated using
nixpkgs-review.Command:
nixpkgs-review --extra-nixpkgs-config '{ allowBroken = false; }'Commit:
dd13071e31e02934e7307229747e64194ee12812x86_64-linux✅ 13 packages built:
Maintainer pings
cc @JohnTitor @JoaquinTrinanes @ryan4yin for testing.
Tip
As a maintainer, if your package is located under
pkgs/by-name/*, you can comment@NixOS/nixpkgs-merge-bot mergeto automatically merge this update using thenixpkgs-merge-bot.Add a 👍 reaction to pull requests you find important.