R. Ryantm
5ba2e3e8de
rqlite: 8.23.2 -> 8.23.4
2024-04-28 03:24:17 +00:00
R. Ryantm
6fb45e01f4
dolt: 1.35.10 -> 1.35.11
2024-04-26 23:20:12 +00:00
Mario Rodas
2becf6e837
maintainers: drop marsam
2024-04-24 04:20:00 +00:00
Mario Rodas
183a604e7a
Merge pull request #305572 from wolfgangwalther/remove-promscale-pgx
...
promscale_extension,buildPgxExtension: remove
2024-04-24 22:11:14 -05:00
R. Ryantm
2ebdbcf974
rqlite: 8.23.1 -> 8.23.2
2024-04-23 00:13:31 +00:00
Mario Rodas
c30c183bae
postgresqlPackages.lantern: set pname to postgresql-lantern
...
To avoid Repology to mistake it for another project named Lantern.
2024-04-21 04:20:00 +00:00
R. Ryantm
63b8343b8d
dolt: 1.35.8 -> 1.35.10
2024-04-21 16:34:45 +00:00
Wolfgang Walther
a0a1328606
buildPgxExtension: remove old versions
...
pgx had been renamed to pgrx in April 2023 already [1]. Newer versions
are already in nixpkgs as pgrx. Since the previous commit removed
the only remaining instance of a package still depending on
pgx 0.6.1, we can now remove all of buildPgxExtension and cargo-pgx.
[1]: https://github.com/pgcentralfoundation/pgrx/issues/1106
2024-04-20 20:10:13 +02:00
Wolfgang Walther
945a3bbb8b
postgresqlPackages.promscale_extension: remove deprecated and broken package
...
postgresql14Packages.promscale_extension breaks with:
Error:
0: `pgx-0.6.1` shouldn't be used with `cargo-pgx-0.7.4`,
please use `pgx = "~0.7.4"` in your `Cargo.toml`.
However, pinning cargo-pgx to 0_6_1 via the following
buildPgxExtension.override { cargo-pgx = cargo-pgx_0_6_1; }
does not work either, because the build then fails with:
thread 'main' panicked at /build/promscale_extension-0.8.0-vendor.tar.gz/proc-macro2/src/fallback.rs:756:9:
"__mbstate_t_union_(unnamed_at_/nix/store/ij144ma6vs8acil8r9hgr8xkb1dp9azg-glibc-2_39-5-dev/include/bits/types/__mbstate_t_h_16_3)" is not a valid Ident
This seems to be related to [1], which indicates that this is a
problem with newer LLVM / clang toolchains.
At the same time th upstream package is deprecated / archived since
the 2nd of April 2024 [2]. Additionally this package is unfree and
thus very unlikely to be forked. Since we can't expect this to be
fixed, the only sensible thing to do is to remove the package.
[1]: https://github.com/rust-lang/rust-bindgen/issues/2312
[2]: https://github.com/timescale/promscale/issues/1836
2024-04-20 20:10:13 +02:00
github-actions[bot]
4908c48bf5
Merge master into staging-next
2024-04-15 12:01:00 +00:00
R. Ryantm
b9a629203c
postgresql13Packages.lantern: 0.2.3 -> 0.2.4
2024-04-15 03:41:04 +00:00
Weijia Wang
f3a1652b09
Merge branch 'master' into staging-next
2024-04-13 19:10:53 +02:00
Maximilian Bosch
2705b9062f
Merge pull request #299136 from wolfgangwalther/pg-safeupdate
...
postgresql{12,13}Packages.pg_safeupdate: 1.5 -> 1.4
2024-04-13 16:47:51 +00:00
Vladimír Čunát
24d4f2cd52
Merge branch 'staging' into staging-next
...
Conflicts (tried to quickly resolve somehow, checked eval):
pkgs/development/python-modules/apsw/default.nix
pkgs/development/python-modules/mido/default.nix
pkgs/development/python-modules/pytest-bdd/default.nix
pkgs/development/python-modules/sparse/default.nix
2024-04-12 07:06:54 +02:00
Mario Rodas
86a264e727
Merge pull request #303031 from r-ryantm/auto-update/dolt
...
dolt: 1.35.7 -> 1.35.8
2024-04-10 05:02:50 -05:00
R. Ryantm
d4502d8520
dolt: 1.35.7 -> 1.35.8
2024-04-10 05:59:07 +00:00
R. Ryantm
f9157e0977
postgresql13Packages.lantern: 0.2.2 -> 0.2.3
2024-04-10 03:00:50 +00:00
Weijia Wang
3f59355d84
Merge branch 'staging-next' into staging
2024-04-09 08:26:23 +02:00
R. Ryantm
0c979c7daf
postgresql16JitPackages.pgtap: 1.3.2 -> 1.3.3
2024-04-09 01:39:31 +00:00
github-actions[bot]
c3b3326391
Merge staging-next into staging
2024-04-06 00:02:50 +00:00
Mario Rodas
88c619a6a3
Merge pull request #301870 from r-ryantm/auto-update/rqlite
...
rqlite: 8.23.0 -> 8.23.1
2024-04-05 18:38:56 -05:00
github-actions[bot]
882e0f27d3
Merge staging-next into staging
2024-04-05 18:01:27 +00:00
Pol Dellaiera
0b46528d06
Merge pull request #301544 from mmusnjak/pgsql-datasketches-update
...
apache_datasketches: update to 1.7.0
2024-04-05 17:20:46 +02:00
R. Ryantm
fd62cce119
rqlite: 8.23.0 -> 8.23.1
2024-04-05 15:03:34 +00:00
github-actions[bot]
caf9b7e92b
Merge staging-next into staging
2024-04-05 12:02:18 +00:00
R. Ryantm
9ed2202f70
dolt: 1.35.4 -> 1.35.7
2024-04-05 00:00:12 +00:00
Marko Mušnjak
7cea84dade
apache_datasketches: update to 1.7.0
2024-04-04 15:21:59 +02:00
Silvan Mosberger
b9261ad2e6
Merge pull request #301066 from philiptaron/compatible-typos
...
treewide: fix typos around "compatible" and "compatibility"
2024-04-04 04:18:31 +02:00
R. Ryantm
25a5f227f7
postgresql15JitPackages.pg_partman: 5.0.1 -> 5.1.0
2024-04-03 02:29:01 +00:00
Philip Taron
562b2c5896
postgresqlPackages.pg_bigm: fix typo: compatiblity to compatibility
2024-04-02 14:51:42 -07:00
Philip Taron
269a99d6b8
postgresqlPackages.citus: fix typo: compatibilty to compatibility
2024-04-02 14:45:11 -07:00
Wolfgang Walther
5e0eeb362b
postgresql{12,13}Packages.pg_safeupdate: 1.5 -> 1.4
...
pg_safeupdate was updated to 1.5 in #269755 . v1.5 is not compatible with
PostgreSQL 12 and 13 anymore, so those were marked as broken.
However, this blocks anyone using PostgreSQL 12 or 13 with pg_safeupdate
from updating nixpkgs.
Instead, the old version should have been kept for PG 12 and 13.
2024-03-31 19:32:31 +02:00
Wolfgang Walther
7a358ffd0e
postgresqlPackages.postgis: add myself as maintainer
2024-03-31 19:32:31 +02:00
Wolfgang Walther
156f69bbcb
postgresqlPackages.pg_safeupdate: add myself as maintainer
2024-03-31 19:32:29 +02:00
Ivan Mincik
75e7b2b097
Merge pull request #300347 from marsam/update-pgrouting
...
postgresqlPackages.pgrouting: 3.6.1 -> 3.6.2
2024-03-31 14:24:44 +00:00
R. Ryantm
b7c2c96026
postgresql12JitPackages.plpgsql_check: 2.7.4 -> 2.7.5
2024-03-31 02:12:10 +00:00
Mario Rodas
ce8a906462
postgresqlPackages.pgrouting: 3.6.1 -> 3.6.2
...
Diff: https://github.com/pgRouting/pgrouting/compare/v3.6.1...v3.6.2
Changelog: https://github.com/pgRouting/pgrouting/releases/tag/v3.6.2
2024-03-30 04:20:00 +00:00
R. Ryantm
334b49ce2a
postgresql13Packages.lantern: 0.2.1 -> 0.2.2
2024-03-27 13:43:45 +00:00
Mario Rodas
93883e16ec
Merge pull request #299094 from marsam/add-pg_roaringbitmap
...
postgresqlPackages.pg_roaringbitmap: init at 0.5.4
2024-03-26 18:12:39 -05:00
Mario Rodas
e4b3f3f652
Merge pull request #298190 from jopejoe1/postgresql-libversion
...
postgresqlPackages.pg_libversion: init at 2.0.0
2024-03-26 00:06:39 -05:00
Nick Cao
60f5ab8a3e
postgresql: enable spinlock on riscv
2024-03-25 16:15:05 -04:00
Mario Rodas
2d8a9a0bf4
postgresqlPackages.pg_roaringbitmap: init at 0.5.4
2024-03-25 04:20:00 +00:00
Weijia Wang
7c7fb17b30
Merge pull request #297065 from r-ryantm/auto-update/monetdb
...
monetdb: 11.49.1 -> 11.49.5
2024-03-24 23:52:58 +01:00
Yt
86de7cd867
Merge pull request #296336 from marsam/refactor-cargo-pgrx
...
cargo-pgrx: refactor
2024-03-23 11:51:28 +00:00
jopejoe1
b7cdcb35cb
postgresqlPackages.pg_libversion: init at 2.0.0
2024-03-22 21:26:54 +01:00
Maximilian Bosch
0cf4b07939
Merge pull request #297155 from Ma27/fix-pg_anonymizer-meta
...
postgresqlPackages.pg_anonymizer: fix meta
2024-03-22 17:00:02 +00:00
R. Ryantm
4ace79fb70
postgresql16JitPackages.pg_uuidv7: 1.4.1 -> 1.5.0
2024-03-22 01:43:07 +00:00
Maximilian Bosch
8ec284b8c4
postgresqlPackages.pg_anonymizer: fix meta
...
Previously the entire `meta` section from `pg-dump-anon` was copied
over including `mainProgram` which doesn't belong here. To avoid similar
issues, fields from the meta section of pg-dump-anon are copied over
explicitly.
2024-03-19 12:25:48 +01:00
Martin Weinelt
3321e63b12
Merge remote-tracking branch 'origin/master' into staging-next
...
Conflicts:
- pkgs/development/python-modules/sphinx-autobuild/default.nix
2024-03-19 04:00:32 +01:00
Martin Weinelt
afa65506cb
Merge pull request #297084 from stuebinm/trivial-meta-mainprograms
...
treewide: add meta.mainProgram to (almost) all packages with a single binary
2024-03-19 03:57:54 +01:00
