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
pythonPackages.gtimelog: 0.9.1 -> unstable-2020-05-16 #66332
Conversation
4866ba6
to
bab0629
Compare
bab0629
to
5619bf4
Compare
I have updated the PR to the most recent commit of the gtimelog repository. Furthermore, I rebased my PR branch to not conflict with the current master after 72e7d56. |
After nearly a year I have rebased my PR and updated it to the newest unstable version, because there is still no real release. |
Result of 3 packages built:- gtimelog (python27Packages.gtimelog) - python37Packages.gtimelog - python38Packages.gtimelog |
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.
If the package has no tests you should add pythonImportChecks.
Co-authored-by: Martin Weinelt <mweinelt@users.noreply.github.com>
Apparently I missed the |
No problem, now it checks it twice. |
Motivation for this change
The content of this PR is the update of the gtimelog package.
Here it was updated from the outdated 0.9.1 version to the current HEAD, because the last release is a bit old and in the meantime SMTP support has been added. As soon as the next stable version is released, I would again set a release as a version.
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)Notify maintainers
cc @ocharles