Arch Linux User Repository

Installation fails by conflicts of different versions of llvm-git which seem necessary during installation:

• postgresql seems to require llvm-git-18.0.0_r484887.953ae94149f0-1
• lldb seem to require llvm-git 19.0.0_r495959.9f3334e9932f-1

Some console output::

yay -S postgresql13 
:: There are 2 providers available for clang<19:
:: Repository AUR
    1) clang17-bin 2) llvm-git

Enter a number (default=1): 
==> 2
AUR Explicit (1): postgresql13-13.18-1
AUR Make Dependency (1): llvm-git-18.0.0_r484887.953ae94149f0-1
AUR Dependency (1): llvm-libs-git-18.0.0_r484887.953ae94149f0-1
Sync Make Dependency (1): lldb-19.1.7-1
:: PKGBUILD up to date, skipping download: postgresql13
:: PKGBUILD up to date, skipping download: llvm-git
:: PKGBUILD up to date, skipping download: llvm-git
  2 postgresql13                             (Build Files Exist)
  1 llvm-git                                 (Build Files Exist)
==> Packages to cleanBuild?
==> [N]one [A]ll [Ab]ort [I]nstalled [No]tInstalled or (1 2 3, 1-3, ^4)
==> 
  2 postgresql13                             (Build Files Exist)
  1 llvm-git                                 (Build Files Exist)
==> Diffs to show?
==> [N]one [A]ll [Ab]ort [I]nstalled [No]tInstalled or (1 2 3, 1-3, ^4)
==> 
ldd: /usr/bin/postgres: Bestand of map bestaat niet
ldd: /usr/bin/postgres: Bestand of map bestaat niet
ldd: /home/stani/.cache/yay/postgresql13/pkg/postgresql13/usr/bin/postgres: Bestand of map bestaat niet
==> Pakket postgresql13 13.18-1 (di 04 feb 2025 23:25:53) wordt gemaakt
==> Bronnen ophalen...
  -> postgresql-13.18.tar.bz2 is gevonden
  -> postgresql-run-socket.patch is gevonden
  -> postgresql-perl-rpath.patch is gevonden
  -> postgresql.pam is gevonden
  -> postgresql.logrotate is gevonden
  -> postgresql.service is gevonden
  -> postgresql-check-db-dir is gevonden
  -> postgresql.sysusers is gevonden
  -> postgresql.tmpfiles is gevonden
==> WAARSCHUWING: Verificatie van PGP signaturen van bronbestanden wordt overgeslaan.
==> Valideren van source bestanden met md5sums...
    (...)
==> Valideren van source bestanden met sha256sums...
    (...)
==> Valideren van source bestanden met b2sums...
    (...)
==> Pakket llvm-git 19.0.0_r495959.9f3334e9932f-1 (di 04 feb 2025 23:25:57) wordt gemaakt

Also later when it tries to make llvm-git 19.0.0_r495959.9f3334e9932f-1 it makes llvm-git 1.0.0_r526253.9ccf03861550-1::

==> Pakket llvm-git 19.0.0_r495959.9f3334e9932f-1 (di 04 feb 2025 23:29:58) wordt gemaakt
==> Uitvoerafhankelijkheden controleren...
==> Afhankelijkheden voor creatie controleren
==> Bronnen ophalen...
  -> llvm-project git repo bijwerken...
remote: Enumerating objects: 110, done.
remote: Counting objects: 100% (103/103), done.
remote: Compressing objects: 100% (50/50), done.
Receiving objects: 100% (110/110), 153.45 KiB | 12.79 MiB/s, done.
remote: Total 110 (delta 73), reused 56 (delta 53), pack-reused 7 (from 2)
Resolving deltas: 100% (73/73), completed with 46 local objects.
From https://github.com/llvm/llvm-project
    (...)
  -> llvm-config.h is gevonden
==> Valideren van source bestanden met md5sums...
    llvm-project ... Overgeslaan
    llvm-config.h ... Geslaagd
==> Valideren van source bestanden met sha512sums...
    llvm-project ... Overgeslaan
    llvm-config.h ... Geslaagd
==> Bestaande $srcdir/ map verwijderen...
==> Bronnen uitpakken...
  -> Een werkkopie van pakketlijst llvm-project git aan het aanmaken...
Cloning into 'llvm-project'...
done.
Updating files: 100% (153940/153940), done.
==> Bezig met het uitvoeren van pkgver()...
==> Bijgewerkte versie: llvm-git 21.0.0_r526253.9ccf03861550-1
==> Bronned zijn gereed.
==> Pakket llvm-git 21.0.0_r526253.9ccf03861550-1 (di 04 feb 2025 23:30:42) wordt gemaakt

When I retry I get:: ==> Pakket postgresql13 13.18-1 (wo 05 feb 2025 12:33:21) wordt gemaakt ==> Uitvoerafhankelijkheden controleren... ==> Afhankelijkheden voor creatie controleren ==> Ontbrekende afhankelijkheden: -> llvm<19 ==> FOUT: Kon niet alle afhankelijkheden oplossen.

Installations fails because of xml test:

     xml                          ... FAILED      241 ms
parallel group (9 tests):  hash_part reloptions explain partition_info indexing partition_join partition_aggregate tuplesort partition_prune
     partition_join               ... ok          298 ms
     partition_prune              ... ok          531 ms
     reloptions                   ... ok           19 ms
     hash_part                    ... ok           15 ms
     indexing                     ... ok          277 ms
     partition_aggregate          ... ok          302 ms
     partition_info               ... ok           26 ms
     tuplesort                    ... ok          434 ms
     explain                      ... ok           22 ms
test event_trigger                ... ok           50 ms
test fast_default                 ... ok           56 ms
test stats                        ... ok          561 ms
============== shutting down postmaster               ==============

========================
 1 of 202 tests failed. 
========================

The differences that caused some tests to fail can be viewed in the
file "~/.cache/yay/postgresql13/src/postgresql-13.15/src/test/regress/regression.diffs".  A copy of the test summary that you see
above is saved in the file "~/.cache/yay/postgresql13/src/postgresql-13.15/src/test/regress/regression.out".

make[1]: *** [GNUmakefile:132: check] Error 1
make[1]: Leaving directory '~/.cache/yay/postgresql13/src/postgresql-13.15/src/test/regress'
make: *** [GNUmakefile:69: check] Error 2
make check failure: ./src/test/regress/regression.diffs
diff -U3 ~/.cache/yay/postgresql13/src/postgresql-13.15/src/test/regress/expected/xml.out ~/.cache/yay/postgresql13/src/postgresql-13.15/src/test/regress/results/xml.out
--- ~/.cache/yay/postgresql13/src/postgresql-13.15/src/test/regress/expected/xml.out    2024-05-06 22:26:10.000000000 +0200
+++ ~/.cache/yay/postgresql13/src/postgresql-13.15/src/test/regress/results/xml.out 2024-06-24 23:02:52.037924664 +0200
@@ -223,23 +223,13 @@
 DETAIL:  line 1: xmlParseEntityRef: no name
 <invalidentity>&</invalidentity>
                 ^
-line 1: chunk is not well balanced
-<invalidentity>&</invalidentity>
-                                ^
 SELECT xmlparse(content '<undefinedentity>&idontexist;</undefinedentity>');
 ERROR:  invalid XML content
 DETAIL:  line 1: Entity 'idontexist' not defined
 <undefinedentity>&idontexist;</undefinedentity>
                              ^
-line 1: chunk is not well balanced
-<undefinedentity>&idontexist;</undefinedentity>
-                                               ^
 SELECT xmlparse(content '<invalidns xmlns=''&lt;''/>');
-         xmlparse          
----------------------------
- <invalidns xmlns='&lt;'/>
-(1 row)
-
+ERROR:  invalid XML content
 SELECT xmlparse(content '<relativens xmlns=''relative''/>');
             xmlparse            
 --------------------------------
@@ -254,15 +244,8 @@
 line 1: Opening and ending tag mismatch: twoerrors line 1 and unbalanced
 <twoerrors>&idontexist;</unbalanced>
                                     ^
-line 1: chunk is not well balanced
-<twoerrors>&idontexist;</unbalanced>
-                                    ^
 SELECT xmlparse(content '<nosuchprefix:tag/>');
-      xmlparse       
----------------------
- <nosuchprefix:tag/>
-(1 row)
-
+ERROR:  invalid XML content
 SELECT xmlparse(document '   ');
 ERROR:  invalid XML document
 DETAIL:  line 1: Start tag expected, '<' not found
@@ -992,15 +975,13 @@
 -- error messages, we suppress the DETAIL in this test.
 \set VERBOSITY terse
 SELECT xpath('/*', '<invalidns xmlns=''&lt;''/>');
-ERROR:  could not parse XML document
+ERROR:  invalid XML content at character 20
 \set VERBOSITY default
 -- Again, the XML isn't well-formed for namespace purposes
 SELECT xpath('/*', '<nosuchprefix:tag/>');
-ERROR:  could not parse XML document
-DETAIL:  line 1: Namespace prefix nosuchprefix on tag is not defined
-<nosuchprefix:tag/>
-                 ^
-CONTEXT:  SQL function "xpath" statement 1
+ERROR:  invalid XML content
+LINE 1: SELECT xpath('/*', '<nosuchprefix:tag/>');
+                           ^
 -- XPath deprecates relative namespaces, but they're not supposed to
 -- throw an error, only a warning.
 SELECT xpath('/*', '<relativens xmlns=''relative''/>');
==> ERROR: A failure occurred in check().
    Aborting...
 -> error making: postgresql13-exit status 4
 -> Failed to install the following packages. Manual intervention is required:
postgresql13 - exit status 4

@s_m Yeah that's a "new" feature of pacman (not really new but feels like it should still be experimental) that works only if you do a full system upgrade. The fact that the new version of icu needs to be installed so that you can build the new version of postgres is not really supported. So I guess you have two options: Obtain a newer build before upgrading icu (i.e. by using chroot to build) or remove, upgrade and reinstall postgres (no data gets lost, maybe you need to re-enable it with systemd, not sure actually).

How can I upgrade my system? Now I get this error:

sudo pacman -Syu
:: Synchronizing package databases... core is up to date extra is up to date community is up to date multilib is up to date archlinuxcn is up to date seblu is up to date :: Starting full system upgrade... resolving dependencies... looking for conflicting packages... error: failed to prepare transaction (could not satisfy dependencies) :: installing icu (74.2-1) breaks dependency 'libicui18n.so=73' required by postgresql13 :: installing icu (74.2-1) breaks dependency 'libicuuc.so=73' required by postgresql13 :: installing icu (74.2-1) breaks dependency 'libicudata.so=73' required by postgresql13

Excellent!!! Thank you for responding so amazingly quickly.

@cmc You are correct, postgresql seems to not support LLVM16. I have updated the package.

Please add dependency:

llvm15-libs

Explanation: llvm-libs has moved to v16, which results in the following hard-to-track error message when running queries:

could not load library "/usr/lib/postgresql/llvmjit.so": libLLVM-15.so:

This fixes the problem

pacman -S llvm15-libs

still getting two test failures :/

```sh

2 of 201 tests failed.

The differences that caused some tests to fail can be viewed in the file "/home/janek/.local/cache/yay/postgresql13/src/postgresql-13.7/src/test/regress/regression.diffs". A copy of the test summary that you see above is saved in the file "/home/janek/.local/cache/yay/postgresql13/src/postgresql-13.7/src/test/regress/regression.out".

make[1]: [GNUmakefile:132: check] Error 1 make[1]: Leaving directory '/home/janek/.local/cache/yay/postgresql13/src/postgresql-13.7/src/test/regress' make: [GNUmakefile:69: check] Error 2 make check failure: ./src/test/regress/regression.diffs diff -U3 /home/janek/.local/cache/yay/postgresql13/src/postgresql-13.7/src/test/regress/expected/collate.icu.utf8.out /home/janek/.local/cache/yay/postgresql13/src/postgresql-13.7/src/test/regress/results/collate.icu.utf8.out --- /home/janek/.local/cache/yay/postgresql13/src/postgresql-13.7/src/test/regress/expected/collate.icu.utf8.out 2022-05-09 21:16:30.000000000 +0000 +++ /home/janek/.local/cache/yay/postgresql13/src/postgresql-13.7/src/test/regress/results/collate.icu.utf8.out 2022-07-03 17:28:36.722967733 +0000 @@ -1035,6 +1035,9 @@ quote_literal(current_setting('lc_ctype')) || ');'; END $$; +ERROR: collations with different collate and ctype values are not supported by ICU +CONTEXT: SQL statement "CREATE COLLATION test1 (provider = icu, lc_collate = 'C', lc_ctype = 'en_IE.UTF-8');" +PL/pgSQL function inline_code_block line 3 at EXECUTE CREATE COLLATION test3 (provider = icu, lc_collate = 'en_US.utf8'); -- fail, need lc_ctype ERROR: parameter "lc_ctype" must be specified CREATE COLLATION testx (provider = icu, locale = 'nonsense'); / never fails with ICU / DROP COLLATION testx; @@ -1045,13 +1048,12 @@ collname

test0 - test1 test5 -(3 rows) +(2 rows)

ALTER COLLATION test1 RENAME TO test11; +ERROR: collation "test1" for encoding "UTF8" does not exist ALTER COLLATION test0 RENAME TO test11; -- fail -ERROR: collation "test11" already exists in schema "collate_tests" ALTER COLLATION test1 RENAME TO test22; -- fail ERROR: collation "test1" for encoding "UTF8" does not exist ALTER COLLATION test11 OWNER TO regress_test_role; @@ -1059,18 +1061,19 @@ ERROR: role "nonsense" does not exist ALTER COLLATION test11 SET SCHEMA test_schema; COMMENT ON COLLATION test0 IS 'US English'; +ERROR: collation "test0" for encoding "UTF8" does not exist SELECT collname, nspname, obj_description(pg_collation.oid, 'pg_collation') FROM pg_collation JOIN pg_namespace ON (collnamespace = pg_namespace.oid) WHERE collname LIKE 'test%' ORDER BY 1; collname | nspname | obj_description ----------+---------------+----------------- - test0 | collate_tests | US English test11 | test_schema | test5 | collate_tests | -(3 rows) +(2 rows)

DROP COLLATION test0, test_schema.test11, test5; +ERROR: collation "test0" for encoding "UTF8" does not exist DROP COLLATION test0; -- fail ERROR: collation "test0" for encoding "UTF8" does not exist DROP COLLATION IF EXISTS test0; @@ -1078,10 +1081,17 @@ SELECT collname FROM pg_collation WHERE collname LIKE 'test%'; collname

-(0 rows) + test11 + test5 +(2 rows)

DROP SCHEMA test_schema; +ERROR: cannot drop schema test_schema because other objects depend on it +DETAIL: collation test_schema.test11 depends on schema test_schema +HINT: Use DROP ... CASCADE to drop the dependent objects too. DROP ROLE regress_test_role; +ERROR: role "regress_test_role" cannot be dropped because some objects depend on it +DETAIL: owner of collation test_schema.test11 -- ALTER ALTER COLLATION "en-x-icu" REFRESH VERSION; NOTICE: version has not changed diff -U3 /home/janek/.local/cache/yay/postgresql13/src/postgresql-13.7/src/test/regress/expected/foreign_data.out /home/janek/.local/cache/yay/postgresql13/src/postgresql-13.7/src/test/regress/results/foreign_data.out --- /home/janek/.local/cache/yay/postgresql13/src/postgresql-13.7/src/test/regress/expected/foreign_data.out 2022-05-09 21:16:30.000000000 +0000 +++ /home/janek/.local/cache/yay/postgresql13/src/postgresql-13.7/src/test/regress/results/foreign_data.out 2022-07-03 17:28:42.712971483 +0000 @@ -5,10 +5,13 @@ -- Suppress NOTICE messages when roles don't exist SET client_min_messages TO 'warning'; DROP ROLE IF EXISTS regress_foreign_data_user, regress_test_role, regress_test_role2, regress_test_role_super, regress_test_indirect, regress_unprivileged_role; +ERROR: role "regress_test_role" cannot be dropped because some objects depend on it +DETAIL: owner of collation test_schema.test11 RESET client_min_messages; CREATE ROLE regress_foreign_data_user LOGIN SUPERUSER; SET SESSION AUTHORIZATION 'regress_foreign_data_user'; CREATE ROLE regress_test_role; +ERROR: role "regress_test_role" already exists CREATE ROLE regress_test_role2; CREATE ROLE regress_test_role_super SUPERUSER; CREATE ROLE regress_test_indirect; ==> ERROR: A failure occurred in check(). Aborting... -> error making: postgresql13

```

@Moxon I found the official version of the fix on the postgres 13 stable branch and applied that to the package, so we don't have to wait for the next release.

@gencom Please don't report duplicates. This is a known problem with the latest Perl version.