Skip to content
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

rmount: init at 1.0.1 #48120

Closed
wants to merge 3 commits into from
Closed

rmount: init at 1.0.1 #48120

wants to merge 3 commits into from

Conversation

Qubasa
Copy link
Contributor

@Qubasa Qubasa commented Oct 9, 2018

Motivation for this change
Things done
  • Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
  • Built on platform(s)
    • NixOS
    • macOS
    • other Linux distributions
  • Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
  • Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
  • Tested execution of all binary files (usually in ./result/bin/)
  • Determined the impact on package closure size (by running nix path-info -S before and after)
  • Fits CONTRIBUTING.md.

Copy link
Member

@samueldr samueldr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👋 Hi! Thanks for your first contribution!

Just a couple things to fix, nothing serious. If you have any questions, hesitations, don't hesitate and ask.

pkgs/tools/filesystems/rmount/default.nix Outdated Show resolved Hide resolved
pkgs/tools/filesystems/rmount/default.nix Outdated Show resolved Hide resolved
pkgs/tools/filesystems/rmount/default.nix Show resolved Hide resolved
pkgs/tools/filesystems/rmount/default.nix Outdated Show resolved Hide resolved
@samueldr
Copy link
Member

Additionally, it may or may not be an issue, the git commit's author isn't properly linked to the github account; it could either be that you didn't add that e-mail address in your github account (not really an issue) or misconfigured git (maybe more of an issue). (The e-mail address used seems a bit... placeholder~ish.)

@Qubasa
Copy link
Contributor Author

Qubasa commented Nov 23, 2018

Thank you very much for your help. I fixed every issue you described, the email was intentionally placeholder~ish but to eliminate conflicts, I just changed it to a real one.

@Qubasa
Copy link
Contributor Author

Qubasa commented Nov 23, 2018

Should I close this Pull request and reopen a new one?

Copy link
Member

@samueldr samueldr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No need to close it, you could force push on your branch, with one squashed commit, that commit having the right author information :).

Additionally, new notes, one I missed initially.

pkgs/tools/filesystems/rmount/default.nix Show resolved Hide resolved
pkgs/tools/filesystems/rmount/default.nix Outdated Show resolved Hide resolved
@Qubasa
Copy link
Contributor Author

Qubasa commented Dec 11, 2018

Thanks! Now it's squashed and the minor things are fixed :-)

stdenv.mkDerivation rec {
name = "rmount-${version}";
version = "1.0.1";
rev = "v${version}";
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please move this declaration directly into the fetchFromGitHub call instead of calling inherit rev;

{ stdenv, nmap, jq, cifs-utils, sshfs, fetchFromGitHub, makeWrapper }:

stdenv.mkDerivation rec {
name = "rmount-${version}";
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please change to pname = "rmount";

@aanderse
Copy link
Member

aanderse commented Apr 9, 2019

@luis-hebendanz in addition to the 2 requests I have made could you please rewrite the git history to contain 2 commits: the first simply adding yourself to the list of maintainers with an appropriate commit message, and the second commit adding the package?

After these changes we'll get this merged right away.

@Qubasa
Copy link
Contributor Author

Qubasa commented Apr 25, 2019

@aanderse Closing this branch I opened up a new one with desired changes: #60204

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants