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
[WIP] cyrus_imapd: init at 3.0.11 #64616
Conversation
The perl scripts can not find the required modules, but otherwise it looks ok. |
Can someone tell me where the bad indent is? OfBorg says it should be in line 1, but it looks fine to me. |
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.
As always looking good @petabyteboy 👍
@GrahamcOfBorg eval |
@petabyteboy why the WIP ? because of the perl issue : it can't find perl belonging to cyrus_imap or 3rd party plugins ? you might need to create an environment perl.withPackages ? |
Yes because of the perl thing.
Some of the bin files will have to be wrapped because they are shell scripts and reference perl without an absolute path. |
I'm wondering if perl should be in nativeBuildInputs or in buildInputs. The perl interpreter is used during the build, but it is also needed at run-time. |
I have fixed PERL5LIB and sieveshell can find the perl libraries in the output, but I am now stuck with a different problem I can not solve:
|
Small update: I am still interested but could not find a solution to the last problem yet. Suggestions are welcome. |
@petabyteboy I bet @volth knows the solution to this problem without having to do any research at all... |
Hello, I'm a bot and I thank you in the name of the community for your contributions. Nixpkgs is a busy repository, and unfortunately sometimes PRs get left behind for too long. Nevertheless, we'd like to help committers reach the PRs that are still important. This PR has had no activity for 180 days, and so I marked it as stale, but you can rest assured it will never be closed by a non-human. If this is still important to you and you'd like to remove the stale label, we ask that you leave a comment. Your comment can be as simple as "still important to me". But there's a bit more you can do: If you received an approval by an unprivileged maintainer and you are just waiting for a merge, you can @ mention someone with merge permissions and ask them to help. You might be able to find someone relevant by using Git blame on the relevant files, or via GitHub's web interface. You can see if someone's a member of the nixpkgs-committers team, by hovering with the mouse over their username on the web interface, or by searching them directly on the list. If your PR wasn't reviewed at all, it might help to find someone who's perhaps a user of the package or module you are changing, or alternatively, ask once more for a review by the maintainer of the package/module this is about. If you don't know any, you can use Git blame on the relevant files, or GitHub's web interface to find someone who touched the relevant files in the past. If your PR has had reviews and nevertheless got stale, make sure you've responded to all of the reviewer's requests / questions. Usually when PR authors show responsibility and dedication, reviewers (privileged or not) show dedication as well. If you've pushed a change, it's possible the reviewer wasn't notified about your push via email, so you can always officially request them for a review, or just @ mention them and say you've addressed their comments. Lastly, you can always ask for help at our Discourse Forum, or more specifically, at this thread or at #nixos' IRC channel. |
I marked this as stale due to inactivity. → More info |
I'm not planning to work on this anymore |
Motivation for this change
Things done
sandbox
innix.conf
on non-NixOS)nix-shell -p nix-review --run "nix-review wip"
./result/bin/
)nix path-info -S
before and after)