Bug 2327967 - postgresql17 fails to build with Python 3.14: jsonb_jsonpath fails: - "12:34:56-07:00" != + "12:34:56-08:00"
Summary: postgresql17 fails to build with Python 3.14: jsonb_jsonpath fails: - "12:34:...
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: postgresql17
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Filip Januš
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: PYTHON3.14
TreeView+ depends on / blocked
 
Reported: 2024-11-22 09:39 UTC by Karolina Surma
Modified: 2025-03-31 10:35 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Type: Bug
Embargoed:


Attachments (Terms of Use)
Fix for jsonpath test failure (3.52 KB, patch)
2025-01-15 14:48 UTC, Zenon Panoussis
no flags Details | Diff

Description Karolina Surma 2024-11-22 09:39:00 UTC
postgresql17 fails to build with Python 3.14.0a2.

=== make failure: src/test/regress/regression.diffs ===
diff -U3 /builddir/build/BUILD/postgresql17-17.0-build/postgresql-17.0/src/test/regress/expected/jsonb_jsonpath.out /builddir/build/BUILD/postgresql17-17.0-build/postgresql-17.0/src/test/regress/results/jsonb_jsonpath.out
--- /builddir/build/BUILD/postgresql17-17.0-build/postgresql-17.0/src/test/regress/expected/jsonb_jsonpath.out	2024-09-23 20:02:53.000000000 +0000
+++ /builddir/build/BUILD/postgresql17-17.0-build/postgresql-17.0/src/test/regress/results/jsonb_jsonpath.out	2024-11-21 09:36:02.456183740 +0000
@@ -2637,7 +2637,7 @@
 select jsonb_path_query_tz('"12:34:56"', '$.time_tz().string()');
  jsonb_path_query_tz 
 ---------------------
- "12:34:56-07:00"
+ "12:34:56-08:00"
 (1 row)
 
 select jsonb_path_query('"12:34:56"', '$.time().string()');

https://docs.python.org/3.14/whatsnew/3.14.html

For the build logs, see:
https://copr-be.cloud.fedoraproject.org/results/@python/python3.14/fedora-rawhide-x86_64/08290778-postgresql17/

For all our attempts to build postgresql17 with Python 3.14, see:
https://copr.fedorainfracloud.org/coprs/g/python/python3.14/package/postgresql17/

Testing and mass rebuild of packages is happening in copr.
You can follow these instructions to test locally in mock if your package builds with Python 3.14:
https://copr.fedorainfracloud.org/coprs/g/python/python3.14/

Let us know here if you have any questions.

Python 3.14 is planned to be included in Fedora 43.
To make that update smoother, we're building Fedora packages with all pre-releases of Python 3.14.
A build failure prevents us from testing all dependent packages (transitive [Build]Requires),
so if this package is required a lot, it's important for us to get it fixed soon.

We'd appreciate help from the people who know this package best,
but if you don't want to work on this now, let us know so we can try to work around it on our side.

Comment 1 Zenon Panoussis 2025-01-15 13:58:56 UTC
See https://perconadev.atlassian.net/browse/PG-1117 . They say it's been fixed upstream.

Comment 2 Zenon Panoussis 2025-01-15 14:48:00 UTC
Created attachment 2066111 [details]
Fix for jsonpath test failure

Tested on postgresql17-17.0-1.fc42.src.rpm in mock for epel 10 and it built correctly. The test failure was caused by the test itself and is unrelated to python. I did get some other errors, also unrealated to this bug: 

RPM build warnings:
    line 228: second Description
    File listed twice: /usr/lib/.build-id/1d/1d2f33c51720490575663773f9e6d3dfff493d
    File listed twice: /usr/lib/.build-id/33/32e1534f5bb5ab4176722c65c57af77a92acc1
    File listed twice: /usr/lib/.build-id/71/0526f460f152e03d4ab553e8527c659c75916b
    File listed twice: /usr/lib/.build-id/85/cb22fbe67cf9696ec19c474d61c2a26fb0fc1d
Finish: rpmbuild postgresql17-17.0-1.el10.src.rpm

Comment 3 Zenon Panoussis 2025-01-15 14:53:37 UTC
BTW, the patch reflects upstream jsonb_jsonpath.sql and jsonb_jsonpath.out at git #af21152.

Comment 4 Aoife Moloney 2025-02-26 13:17:20 UTC
This bug appears to have been reported against 'rawhide' during the Fedora Linux 42 development cycle.
Changing version to 42.


Note You need to log in before you can comment on or make changes to this bug.