Custom query (1087 matches)
Results (46 - 48 of 1087)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#1139 | fixed | Upgrade pgRouting to version 2.0.0 | ||
Description |
With OSGeo Live 7.0 pgRouting should be upgraded to version 2.0.0, but the packages on Launchpad have not been build yet. Once this is done, update the install script as well. |
|||
#1157 | fixed | pgrouting fails to install after postgis update | ||
Description |
From logs (build10344): =============================================================== install_pgrouting.sh =============================================================== gpg: keyring `/tmp/tmpHDcaw_/secring.gpg' created gpg: keyring `/tmp/tmpHDcaw_/pubring.gpg' created gpg: requesting key B65ADE33 from hkp server keyserver.ubuntu.com gpg: /tmp/tmpHDcaw_/trustdb.gpg: trustdb created gpg: key B65ADE33: public key "Launchpad PPA for Georepublic" imported gpg: Total number processed: 1 gpg: imported: 1 (RSA: 1) OK E: Unable to correct problems, you have held broken packages. ERROR: pgRouting Package install failed! Aborting. |
|||
#1234 | fixed | pgRouting: PostGIS database ways table bad import os OSM data | ||
Description |
Hi, moving this into its own ticket from #1233.
I can confirm that the "all links back to one spot" problem in the pgrouting PostGIS db was not present in the 6.5 version of the live disc, so this is a new pgRouting problem too. (& perhaps a separate issue to the TinyOWS failure) I'm guessing that it can only mess up the routing results. thanks, Hamish |
Note:
See TracQuery
for help on using queries.