-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
proj: update to 9.1.1 #40347
proj: update to 9.1.1 #40347
Conversation
proj 7.2.1 is two major versions behind. I am running 9.1 without problems. |
I tested everything with 7.2 and have been using that. When v8 came out there were some issues with v8 in combination with other packages as I recall. That may well have been solved but I'd rather get this in now since it's ready and tested. The CI failures are unrelated (Python 3.11 packages not yet available). |
386fff1
to
f986851
Compare
@ar-jan, I have updated proj to 9.1.0 in the forked repository (https://github.com/kruceter/void-packages/tree/proj). In my attempts to revbump reverse dependencies I could fix some issues related I hope my changes will prove to be useful for you in some way. |
Ah great. I've also been testing proj 9.1.0 and I thought there's a few more things to solve. Here's my notes:
|
It should work.
UPD: I could not open it due to "missing GUI" (possibly refers to wxPython). I will look into it on my side.
It did for me with proj 9.0.1.
I am at fault for overlooking it. I will update it on my side to see whether it works or not. |
Iirc had to start explicitly using something like |
Still the same outcome. I will try to update it 7.8.7 and see how it turns out. |
Grass GUI never worked, in older version on Void, I had to hack the startup script. Now that I use v8.2, it doesn't start also but I don't need it as I use QGIS. If I try to start the grass GUI I get:
The problem refers to the wxPython package, it's an old issue: Updating also grass would pave the way for having qgis as a package. Hope this helps |
Yeah, grass was the reason my previous PR #31687 didn't get merged, and I spent a long time trying things with wxPython, but I did actually get it to work with |
I managed to build grass 7.8.7 with proj 9.1.0. Its GUI started without any surprises; and what is more important, it works with python 3 (at least I swapped out everything related to python 2). That was my original purpose for picking this package, so I am content. vtk 9.1.0 is not tested yet; it is quite a large piece of software to build on my machine. @ar-jan, I have pushed all changes to the "proj" branch in kruceter/void-packages, so you can use them however you wish.
Thank you for mentioning this. I was a little afraid to think that I broke grass by tampering with it in a related pull request. As for versions starting from 8, I had learned of incompatibility with the current wxPython4 through trial and error; this includes that issue you have referred to. Unless wxPython4 is updated, nothing can be done about upgrading to grass 8. |
@kruceter I see though in the grass template you have in your fork that you still rely on python2. I confirm also that grass and QGIS 3.28 builds with proj 9.1. |
|
Thanks @kruceter. I've cherry-picked your commits for grass, XyGrib, and OpenOrienteering-Mapper. Now building 9.1 &co again. |
As discussed on irc, vtk will have to be upgraded first separately because it provides shlibs which are used by other packages: #40423. |
fa3d286
to
6e016c8
Compare
e0766a6
to
f8e13ea
Compare
Oh, proj-9.1.1 was just released, I'll update to that. |
I think this is ready, I've been running proj-9.1.1 for over a month. Only sore point is grass. But afaict the version of grass that's currently packaged is more broken than the update to 7.8.7 included here, because here only the gui is broken while text mode works. Or maybe grass could be removed? I wonder if anyone is even using it on Void given that it seems to be broken to several of us. |
@kruceter Would you care to see if you can get it to work? I gathered these from the error messages involved. I didn't get it working but iirc I stopped before trying all of them combined. Need to backport fixes to wxPython 4.0.7 with Python 3.8+ |
Applied proposed patches and rebuilt wxPython4 with grass. The outcome is same. |
There is no way to disable GUI using build arguments, their old manual misled me. Rebase and apply this patch (and change version in the commit message too): 0001-fixup-grass-update-to-7.8.7-rebuild-for-proj-9.1.txt There is nothing we can do about broken gui at present time, so leave it be. If GUI does not work, grass falls back to the text mode. We can live with it at least until wxPython is updated. If you are interested in enforcing the text mode, add the following block to the template: post_install() {
# This package is broken with wxPython4 (<=4.0.7),
# hence the GUI is compulsorily disabled.
vsed -i "${DESTDIR}/usr/bin/grass" -e "s/\(default_gui =\).*/\1 \"text\"/"
} Aside from grass I think this pull request can be merged. |
I wonder if it wouldn't be cleaner to drop the grass package for now, instead of patching it to be text-only. Any thoughts, @alexjarosch @classabbyamp? |
If you drop GRASS then you will lose the functionality also from the QGIS Toolbox. I have read that GRASS8 works with the latest QGIS (since v3.24). Even if as a standalone it does not work, the toolbox options are handy. |
removing grass is not the right way. i think the right way would be to update wxpython but that's a bit of scope creep :) better to just patch it for now |
I agree with the two posts above from @classabbyamp and @nezos . I think we don't want to loose the functionality in QGIS as well as GRASS. Updating wxpython is really another scope as pointed out above, so I second the opinion tp better just patch it for now. |
The current release does not support the new API of PROJ (>=8.0.0); included patch aims to solve the issue. Conditional make_build_args prevents crossbuilding with failing ninja ("unknown target LINK=${XBPS_CROSS_TRIPLET}-c++"). I suspect that this approach is a relique of the past and therefore is removed from the template. No other issues did arise due to this change.
OK, agree having the grass toolbox algorithms in QGIS will be useful. I've briefly tested a new QGIS build with Grass 8.2.1 and looks good. @kruceter I've used your patch but also updated to grass-8.2.1 which was just released, so the patches could be dropped again. |
No problem at all. This would be for the best. |
Testing the changes
Followup to #31687.