Package Details: geoda-bin 1.8.12-13

Git Clone URL: https://aur.archlinux.org/geoda-bin.git (read-only, click to copy)
Package Base: geoda-bin
Description: GeoDa is an Exploratory (Spatial) Data Analysis and Spatial Regression software, for spatial data analysis including spatial econometrics.
Upstream URL: http://geodacenter.github.io/download_linux.html
Licenses: custom:free_for_non_commercial_use
Submitter: wen
Maintainer: None
Last Packager: wen
Votes: 3
Popularity: 0.000172
First Submitted: 2020-12-27 22:03 (UTC)
Last Updated: 2020-12-27 22:06 (UTC)

Latest Comments

1 2 Next › Last »

sgoodall commented on 2022-05-08 09:47 (UTC) (edited on 2022-05-08 10:06 (UTC) by sgoodall)

I have run into the same problem, have been trying to find where the problem lies but can't work it out so as to contribute

/usr/local/geoda/GeoDa: symbol lookup error: /usr/lib/libtracker-sparql-3.0.so.0: undefined symbol: sqlite3_expanded_sql

mafes commented on 2022-04-01 20:46 (UTC)

Hello, thanks for maintaing this package, but it is no longer working to me. Here I post the error I have when trying to open geoda:

/usr/local/geoda/GeoDa: symbol lookup error: /usr/lib/libtracker-sparql-3.0.so.0: undefined symbol: sqlite3_expanded_sql

Nevertheless, version 1.20 is now available. When I try to modify the PKGBUILD to update the package to 1.20 for bionic, I face this issue:

/usr/local/geoda/GeoDa: error while loading shared libraries: libgdal.so.20: cannot open shared object file: No such file or directory

Doing the same for 1.20 focal does not work either, with a similar error (ligdal.so.26 does not exist). Trying making a symbolic link with available libgdal does not work.

Would someone know how to fix it?

wen commented on 2021-11-22 13:22 (UTC)

@tapajos, could you take over the maintenance of this package?

wen commented on 2021-08-03 18:41 (UTC)

Thank you.

Would you like to post the new PKGBUILD here?

Alternatively, would you like to take over this package?

williamloures commented on 2021-07-23 01:00 (UTC)

Thank you for the package! I've noticed two things, however:

1) It doesn't build when setting the BUILDDIR option in /etc/makepkg.conf. It builds otherwise though.

2) The version here in the AUR page is 1.8.12-13, but 1.18.0 in the PKGBUILD. At least here this makes yay confused, giving a warning on every update that the local package is newer.

I'm currently using a version that I installed using debtap, which converts .deb packages to the Arch format. Apparently can also generate PKGBUILDs, so maybe that's an option too...

wen commented on 2020-12-30 12:47 (UTC)

Great! Thank you very much for your help too!

Happy new year!

mafes commented on 2020-12-28 15:10 (UTC)

Hello, I tested the package and it works, thank you very much!

wen commented on 2020-12-28 10:59 (UTC)

Hello!

aur's management approved the merge request.

Now geoda-bin is the package.

Could you please try to install geoda-bin on your system? Thank you!

wen commented on 2020-12-27 22:07 (UTC)

Thank you!

You referred me to correct web pages. I now created a geoda-bin package. I just submitted a request to merge geoda to the geoda-bin package.

mafes commented on 2020-12-27 19:56 (UTC)

Thank you very much, now it works!

I'm sorry, but I don't know how to change the name. In this issue it is said to create another package with the correct name and then merge this package to the other one. In this page (AUR package) there is an option named Submit Request in Package Actions, which points to a Merge Request. I think this should be the way. However, I do not know how to manage the changes in PKGFILE, but as I said in the last comment, to build the package I had to rename the file geoda.install to geoda-bin.install.