Custom query (906 matches)

Filters
 
or
 
  
 
Columns

Show under each result:


Results (34 - 36 of 906)

2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22
Ticket Resolution Summary Owner Reporter
#1157 fixed pgrouting fails to install after postgis update dkastl kalxas
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 dkastl hamish
Description

Hi,

moving this into its own ticket from #1233.

  • connect to pgrouting PostGIS database in QGIS works, but the ways table doesn't look very healthy, all links back to one spot. or maybe that is the shortest path from a->b? as-is doesn't look healthy anyway. see screenshot.

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

#1523 fixed 52nSOS: DescribeSensor fails for "52NorthWS1" ehjuerrens ehjuerrens
Description

When executing describe sensor for procedure "52NorthWS1", the server returns an internal server error message and nothing is logged.

2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22
Note: See TracQuery for help on using queries.