-
-
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
vdirsyncer: deprecate vdirsyncerStable #103073
Conversation
khal:
|
@SuperSandro2000 Thanks for the feedback, but I am not getting those errors. Both How did you install khal? |
@SuperSandro2000 is that on darwin? |
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.
Looks good!
e2feb75
to
425f1f9
Compare
yes but now it fails with
|
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.
Thank you for your work. When I read the changes made by the commit in this PR, I see:
stable.nix
was deleted andvdirsyncerStable
is deprecated;default.nix
is changed significantly.
I think the story your commits should tell is something like:
- what was in
default.nix
is deleted stable.nix
becomes the new default
To tell this story, I think I would decompose the PR into 2 commits:
- The first commit deletes
default.nix
and makesvdirsyncer
points tostable.nix
- The second commit renames
stable.nix
intodefault.nix
The deprecation of vdirsyncerStable
can happen in any of these 2 commits or a third one. I would put it in a third commit because I like small and atomic commits but that's up to you.
425f1f9
to
160e6d9
Compare
@DamienCassou Like this? |
160e6d9
to
29740fa
Compare
Exactly, great job. This is so much easier to understand, thank you. I would only add a sentence to the first commit explaining why the file is deleted. |
How would you word it? |
|
TLDR: default.nix was pointing to an unmaintained code base whereas stable.nix is up-to-date and maintained. History 1. At first their was one Python version of vdirsyncer that had been working fine for years. Then, maintenance decreased and the package was marked as broken in nixpkgs. 2. The original author (@untitaker on github.com) of vdirsyncer decided to re-implement (part of) vdirsyncer in Rust. Nixpkgs made `vdirsyncer` point to the Rust version and renamed the Python historical version to `vdirsyncerStable`. 3. Eventually, @untitaker gave up on the Rust version. 4. Someone else (@WhyNotHugo on github.com) decided to take over maintenance of the Python version. 5. Mario Rodas (@marsam on github) and Damien Cassou updated the `vdirsyncerStable` to point to the work of @WhyNotHugo and mark the package as working again.
29740fa
to
8668e88
Compare
@DamienCassou Thanks for the text! |
1bf3f89
to
6069aaa
Compare
Result of 1 package failed to build:
2 packages built:
khal
|
6069aaa
to
879bd1a
Compare
All good - tested here! |
This seems to have broken the hydra build (and it won't build for me locally either)? First evaluation after the merge broke, subsequent evaluations use the cached failure: Looking at the log, the error seems to be the same as the one I'm seeing locally and which was also discussed previously in this nixpkgs PR and this upstream Issue. If I locally disable the flaky test, it works for me locally: --- a/pkgs/development/python-modules/vdirsyncer/default.nix
+++ b/pkgs/development/python-modules/vdirsyncer/default.nix
@@ -53,7 +53,10 @@ buildPythonPackage rec {
- disabledTests = [ "test_verbosity" ];
+ disabledTests = [
+ "test_verbosity" # was always disabled
+ "test_create_collections" # flaky test sometimes exceeds its deadline
+ ]; |
@wirew0rm if would like to make a PR, I'll be happy to review it |
Motivation for this change
Things done
sandbox
innix.conf
on non-NixOS linux)nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
./result/bin/
)nix path-info -S
before and after)