#5246 closed defect (fixed)
bessies failing on upgrade
Reported by: | robe | Owned by: | strk |
---|---|---|---|
Priority: | blocker | Milestone: | PostGIS 3.4.0 |
Component: | build | Version: | master |
Keywords: | Cc: |
Description ¶
Bessies do not like these recent upgrade changes.
https://debbie.postgis.net/view/PostGIS/job/PostGIS_Worker_Run/label=bessie/3980/consoleFull
1:54:49 ln -fs "postgis--TEMPLATED--TO--ANY.sql" /usr/local/share/postgresql/extension/postgis--3.4.0dev--ANY.sql; \ 21:54:49 /usr/home/jenkins/workspace/PostGIS_Worker_Run/label/bessie/f24ef85568c1c38b81b36cbceab60d298d103dab/loader/postgis \ 21:54:49 install-extension-upgrades \ 21:54:49 --extension postgis \ 21:54:49 --pg_sharedir /usr/local/share/postgresql \ 21:54:49 2.0.0 2.0.1 2.0.2 2.0.3 2.0.4 2.0.5 2.0.6 2.0.7 2.1.0 2.1.1 2.1.2 2.1.3 2.1.4 2.1.5 2.1.6 2.1.7 2.1.8 2.1.9 2.2.0 2.2.1 2.2.2 2.2.3 2.2.4 2.2.5 2.2.6 2.2.7 2.2.8 2.3.0 2.3.1 2.3.2 2.3.3 2.3.4 2.3.5 2.3.6 2.3.7 2.3.8 2.3.9 2.3.10 2.3.11 2.4.0 2.4.1 2.4.2 2.4.3 2.4.4 2.4.5 2.4.6 2.4.7 2.4.8 2.4.9 2.4.10 2.5.0 2.5.1 2.5.2 2.5.3 2.5.4 2.5.5 2.5.6 2.5.7 2.5.8 3.0.0 3.0.1 3.0.2 3.0.3 3.0.4 3.0.5 3.0.6 3.0.7 3.1.0 3.1.1 3.1.2 3.1.3 3.1.4 3.1.5 3.1.6 3.1.7 3.2.0 3.2.1 3.2.2 3.2.3 3.2.4 3.3.0 3.3.1 21:54:49 /bin/sh: /usr/home/jenkins/workspace/PostGIS_Worker_Run/label/bessie/f24ef85568c1c38b81b36cbceab60d298d103dab/loader/postgis: not found 21:54:49 gmake[3]: *** [../upgrade-paths-rules.mk:22: install-upgrade-paths] Error 127 21:54:49 gmake[3]: Leaving directory '/usr/home/jenkins/workspace/PostGIS_Worker_Run/label/bessie/f24ef85568c1c38b81b36cbceab60d298d103dab/extensions/postgis' 21:54:49 gmake[2]: *** [Makefile:29: install] Error 1 21:54:49 gmake[2]: Leaving directory '/usr/home/jenkins/workspace/PostGIS_Worker_Run/label/bessie/f24ef85568c1c38b81b36cbceab60d298d103dab/extensions'
Change History (4)
comment:1 by , 2 years ago
comment:2 by , 2 years ago
Status: | new → assigned |
---|
comment:4 by , 2 years ago
@strk this fixed the bessies, but Cirrus freebsd are still having issues. I'll open a separate ticket for them, since I'm not sure it's quite the same issue
Note:
See TracTickets
for help on using tickets.
must be the annoying @EXESUFFIX@