Opened 4 years ago
Closed 4 years ago
#4693 closed defect (invalid)
PostGIS 3.1.0 still showing 3.1.0alpha1 in output
Reported by: | robe | Owned by: | robe |
---|---|---|---|
Priority: | blocker | Milestone: | PostGIS 3.1.0 |
Component: | build | Version: | master |
Keywords: | Cc: |
Description
I thought I ticked this before - but noticing this on the outputs
PostgreSQL 13beta1, compiled by Visual C++ build 1914, 64-bit Postgis 3.1.0dev - (3.1.0alpha1-122-g16121bf79) - 2020-05-23 22:57:55 scripts 3.1.0dev 3.1.0alpha1-122-g16121bf79 GEOS: 3.9.0-CAPI-1.14.0 PROJ: Rel. 5.2.0, September 15th, 2018
So I assume when I flipped the version number I missed a spot?
SELECT postgis_full_version();
shows similar ugliness On my workstation shows this
POSTGIS="3.1.0dev 3.1.0alpha1-122-g16121bf79" [EXTENSION] PGSQL="130" GEOS="3.9.0-CAPI-1.14.0" SFCGAL="1.3.2" PROJ="6.2.1" GDAL="GDAL 3.0.2, released 2019/10/28" LIBXML="2.9.9" LIBJSON="0.12" LIBPROTOBUF="1.2.1" WAGYU="0.5.0 (Internal)" TOPOLOGY RASTER
Change History (2)
comment:1 by , 4 years ago
comment:2 by , 4 years ago
Resolution: | → invalid |
---|---|
Status: | assigned → closed |
okay I'll close out then as a invalid guess it's okay I was just puzzled and worried it would say that forever.
Note:
See TracTickets
for help on using tickets.
This is not ugliness :D, it is the output of
git describe
that allow us to know exactly which commit are you on. The3.1.0alpha1
comes from the latest tag, the122
I think comes from the number of commits since that tag, and then itsg$HASH
to know the exact commit.I personally don't see anything wrong with this, but I'm already used to
git describe
output.