Your message dated Sat, 6 Jun 2026 20:28:37 +0200
with message-id <[email protected]>
and subject line Re: Bug#1139157: Bug: postgis: Null-byte (\x00) in
postgis--3.5.2.sql causes CREATE EXTENSION to fail
has caused the Debian Bug report #1139157,
regarding Bug: postgis: Null-byte (\x00) in postgis--3.5.2.sql causes CREATE
EXTENSION to fail
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1139157: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1139157
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: postgis
Version: 3.5.2+dfsg-1
Severity: important
Architecture: arm64
Dear Maintainer,
When trying to enable the PostGIS extension on a fresh PostgreSQL 17
installation running on Debian Trixie (arm64 / Raspberry Pi 5), the database
throws the following error:
ERROR: invalid byte sequence for encoding "UTF8": 0x00
We tracked this down to a physical null-byte (\x00) inside the SQL extension
script provided by the package.
File: /usr/share/postgresql/17/extension/postgis--3.5.2.sql
Location: Inside the definition string for EPSG 8796 (around the string
"AUTHORITY["EPSG","42")
Running the following command confirms the physical presence of the
null-byte in the file:
grep -Pa '\x00' /usr/share/postgresql/17/extension/postgis--3.5.2.sql
Workaround:
Removing the null-byte with 'tr -d "\000"' and manually fixing the resulting
unterminated string/syntax errors at the end of the file allowed the
extension to load successfully.
It seems there was a compilation or packaging error when building this
specific version for arm64.
Best regards,
Roland Wagner
Gemini helped me, its really a great tool. Many thanks also to you, because
you maintain also a great tool!
[Dein Name]
--- End Message ---
--- Begin Message ---
Control: tags -1 unreproducible
On 6/6/26 7:52 PM, Roland Wagner wrote:
When trying to enable the PostGIS extension on a fresh PostgreSQL 17
installation running on Debian Trixie (arm64 / Raspberry Pi 5), the database
throws the following error:
ERROR: invalid byte sequence for encoding "UTF8": 0x00
We tracked this down to a physical null-byte (\x00) inside the SQL extension
script provided by the package.
File: /usr/share/postgresql/17/extension/postgis--3.5.2.sql
Location: Inside the definition string for EPSG 8796 (around the string
"AUTHORITY["EPSG","42")
This file is provided by postgresql-17-postgis-3-scripts which works as
expected on amd64, and because it's an arch:all package it's the same on all
other architectures.
Running the following command confirms the physical presence of the
null-byte in the file:
grep -Pa '\x00' /usr/share/postgresql/17/extension/postgis--3.5.2.sql
Unreproducible with the package from the archive as retrieved by debsnap:
$ grep -nPa '\x00'
binary-postgresql-17-postgis-3-scripts/postgresql-17-postgis-3-scripts_3.5.2+dfsg-1_all/usr/share/postgresql/17/extension/postgis--3.5.2.sql
$
Workaround:
Removing the null-byte with 'tr -d "\000"' and manually fixing the resulting
unterminated string/syntax errors at the end of the file allowed the
extension to load successfully.
It seems there was a compilation or packaging error when building this
specific version for arm64.
Best regards,
Roland Wagner
Gemini helped me, its really a great tool. Many thanks also to you, because
you maintain also a great tool!
Since you have a solution to your problem, there is nothing for the package
maintainer to do.
Kind Regards,
Bas
--
PGP Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
--- End Message ---
