|
Bugzilla – Full Text Bug Listing |
| Summary: | postgresql12-llvmjit has broken dependencies | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Distribution | Reporter: | Moritz Duge <duge> |
| Component: | Other | Assignee: | Reinhard Max <max> |
| Status: | RESOLVED DUPLICATE | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | bruno |
| Version: | Leap 15.3 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Moritz Duge
2021-06-04 11:07:57 UTC
Also visible on OBS (Me building postgis) nothing provides postgresql12-server = 12.6-3.24.1 needed by postgresql12-llvmjit, (got version 12.6-8.16.1) nothing provides postgresql13-llvmjit nothing provides postgresql96-devel >= 9.6, nothing provides postgresql96-server >= 9.6 nothing provides postgresql11-devel >= 9.6, nothing provides postgresql11-server-devel >= 9.6, nothing provides postgresql11-server >= 9.6, nothing provides postgresql11-llvmjit So only postgresql10 on openSUSE Leap 15.3 seems to be ok :-( For some reason we ended up with postgresql12-llvmjit having a lower %release number than postgresql12. Normally they should come from the very same build and hence have the exact same build run. I guess this has to do with my recent re-enablement of building the llvmjit on SLE. It used to be disabled, because LLVM and clang are not supported on SLE, but we re-enabled it to be able to have it on Leap and Package Hub, but will not ship that subpackage on SLE. Now I guess that this change had already been released on SP1, but not yet on SP2 at the point in time that the binary packages for Leap 15.3 were snapshot from SLE-15. Because the llvmjit subpackage did not (yet) exist on SP2, it was taken from SP1 instead where it was from a newer revision of the package, but with a lower release number. To make the confusion even worse, I just noticed that I had forgotten to also re-enable building the llvmjit subpackage in the "postgresql" noarch package, causing postgresql-llvmjit to have version 12 o 15.3 which prohibits the installation of postgresql13-llvmjit which wasn't on the original media at all, but would now be available as an update in a version that matches the rest of the postgresql13 packages. I just fixed the latter with sr#242901 and sr#242902, so when these updates arrive together with the latest round of PostgreSQL patchlevel updates, everything should be OK. I am closing this as duplicate, because it is just a different manifestation of the same problem. *** This bug has been marked as a duplicate of bug 1183118 *** |