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
desync: 0.4.0 -> 0.9.0 #106403
desync: 0.4.0 -> 0.9.0 #106403
Conversation
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.
Upstream uses go modules now. Could you please also update the derivation to use buildGoModule
? And remove deps.nix
.
1925c76
to
c29bd44
Compare
@doronbehar done, thank you -- I hadn't been aware of That said, with the cutover, the tests are no longer able to succeed -- it looks like the data they need at runtime (stored in the |
c29bd44
to
6138dc5
Compare
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 you could please squash the commits - migrating to buildGoModule is part of the update.
6138dc5
to
63b752c
Compare
63b752c
to
4f8057e
Compare
Me too 😕 . Tried to debug this a bit locally and failed to see why. |
Motivation for this change
The desync package has fallen far behind upstream, and consequently missed out on a great deal of feature and bugfix development.
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)46,885,312 -> 51,176,648 -- an increase, but not an out-of-range one given the dependency chain updates supporting new features.