-
-
Notifications
You must be signed in to change notification settings - Fork 14.9k
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
valhalla: 3.4.0 -> 3.5.1 #375449
valhalla: 3.4.0 -> 3.5.1 #375449
Conversation
Running nixpkgs-review right now and I already see |
You can move libspatialite changes to separate PR to get it merged sooner. |
|
I'm not in a hurry. |
Does osmscout-server work with valhalla 3.5.1? There's no valhalla.json-3.5.1 here: https://github.com/rinigus/osmscout-server/tree/master/data, so it probably won't work (There are no unit-tests, so you'd need to run osmscout-server manually and test it with e.g. pure-maps to see if routing still works correctly). Since osmscout-server is currently the only package in nixpkgs that depends on valhalla, either we need to keep a copy of valhalla 3.4 around for osmscout-server to use, or we need to wait until osmscout-server is able to use valhalla 3.5 before updating the main valhalla package. |
Merged :) |
In testing #375451, I see valhalla is also broken in a similar-but-different way. I assume the easiest way to fix valhalla is to update it to 3.5.1? In which case, we presumably have two options to get osmscout-server building and working:
If it was just the valhalla update that was breaking osmscout-server, I would probably go with option 1 to start with. However, as osmscout-server is already broken, I don't really mind which route we take, as long as we try not to leave it buildable-but-broken for too long. |
Co-authored-by: Gaétan Lepage <[email protected]>
3b6c0e6
to
afc3d4a
Compare
That was at least the first thing I tried and it worked. It is also the reason I'd prefer to go with your option 2 for osmscout-server. Since you already added support for 3.4.0, may I ask you to do this update? I myself don't know what would be needed for that.
Maybe you could add a post installation test to make it not buildable when broken? |
This issue is solved now. All linux builds are green in nixpkgs-unstable https://github.com/imincik/nix-utils/actions/runs/13151221904 . |
|
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.
LGTM
Unfortunately, this PR is breaking spatialite_tools
and possibly breaking otb as well. Also, I see many packages broken on darwin . @GaetanLepage , did you broken packages reported by your nixpkgs-review properly ? Look to me that we should consider to revert this PR |
This is unfortunate indeed. I did not assume those three failures on Linux to be regressions, my bad. |
Just checked on Hydra, otb was already broken before this PR, but spatialite_tools was broken by THIS PR. |
|
Also:
Things done
nix.conf
? (See Nix manual)sandbox = relaxed
sandbox = true
nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD"
. Note: all changes have to be committed, also see nixpkgs-review usage./result/bin/
)Add a 👍 reaction to pull requests you find important.