Elgato_dark/hypopg
1
0
Fork 0
mirror of https://github.com/HypoPG/hypopg synced 2026-05-24 09:38:21 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

Debian: Upload for PostgreSQL 13.

Browse source 
* Use dh --with pgxs_loop.
* DH 13.
* R³: no.
* debian/tests: Use 'make' instead of postgresql-server-dev-all.
This commit is contained in:
Christoph Berg 2020-10-18 22:28:25 +02:00
parent 1c7be949a8
commit 7c42baaf71
7 changed files with 23 additions and 64 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

10
debian/changelog vendored
View file

@ -1,3 +1,13 @@
hypopg (1.1.4-2) unstable; urgency=medium
* Team upload for PostgreSQL 13.
* Use dh --with pgxs_loop.
* DH 13.
* R³: no.
* debian/tests: Use 'make' instead of postgresql-server-dev-all.
-- Christoph Berg <myon@debian.org> Sun, 18 Oct 2020 22:16:44 +0200
hypopg (1.1.4-1) unstable; urgency=medium
* New upstream version with PG13 support.

1
debian/compat vendored
View file

@ -1 +0,0 @@
9

50
debian/control vendored
View file

@ -2,59 +2,19 @@ Source: hypopg
Section: database
Priority: optional
Maintainer: Julien Rouhaud <rjuju123@gmail.com>
Standards-Version: 4.1.3
Build-Depends: debhelper (>=9~), postgresql-server-dev-all (>= 141~)
Standards-Version: 4.5.0
Rules-Requires-Root: no
Build-Depends: debhelper-compat (= 13), postgresql-all (>= 217~)
Homepage: https://hypopg.readthedocs.io/
Vcs-Browser: https://github.com/hypopg/hypopg
Vcs-Git: https://github.com/hypopg/hypopg.git
Package: postgresql-9.3-hypopg
Package: postgresql-13-hypopg
Architecture: any
Depends: ${misc:Depends}, ${shlibs:Depends}, postgresql-9.3
Depends: ${misc:Depends}, ${shlibs:Depends}, postgresql-13
Description: PostgreSQL extension adding support for hypothetical indexes.
An hypothetical, or virtual, index is an index that doesn't really exists, and
thus doesn't cost CPU, disk or any resource to create. They're useful to know
if specific indexes can increase performance for problematic queries, since
you can know if PostgreSQL will use these indexes or not without having to
spend resources to create them.
Package: postgresql-9.4-hypopg
Architecture: any
Depends: ${misc:Depends}, ${shlibs:Depends}, postgresql-9.4
Description: PostgreSQL extension adding support for hypothetical indexes.
An hypothetical, or virtual, index is an index that doesn't really exists, and
thus doesn't cost CPU, disk or any resource to create. They're useful to know
if specific indexes can increase performance for problematic queries, since
you can know if PostgreSQL will use these indexes or not without having to
spend resources to create them.
Package: postgresql-9.5-hypopg
Architecture: any
Depends: ${misc:Depends}, ${shlibs:Depends}, postgresql-9.5
Description: PostgreSQL extension adding support for hypothetical indexes.
An hypothetical, or virtual, index is an index that doesn't really exists, and
thus doesn't cost CPU, disk or any resource to create. They're useful to know
if specific indexes can increase performance for problematic queries, since
you can know if PostgreSQL will use these indexes or not without having to
spend resources to create them.
Package: postgresql-9.6-hypopg
Architecture: any
Depends: ${misc:Depends}, ${shlibs:Depends}, postgresql-9.6
Description: PostgreSQL extension adding support for hypothetical indexes.
An hypothetical, or virtual, index is an index that doesn't really exists, and
thus doesn't cost CPU, disk or any resource to create. They're useful to know
if specific indexes can increase performance for problematic queries, since
you can know if PostgreSQL will use these indexes or not without having to
spend resources to create them.
Package: postgresql-10-hypopg
Architecture: any
Depends: ${misc:Depends}, ${shlibs:Depends}, postgresql-10
Description: PostgreSQL extension adding support for hypothetical indexes.
An hypothetical, or virtual, index is an index that doesn't really exists, and
thus doesn't cost CPU, disk or any resource to create. They're useful to know
if specific indexes can increase performance for problematic queries, since
you can know if PostgreSQL will use these indexes or not without having to
spend resources to create them.

5
debian/control.in vendored
View file

@ -2,8 +2,9 @@ Source: hypopg
Section: database
Priority: optional
Maintainer: Julien Rouhaud <rjuju123@gmail.com>
Standards-Version: 4.1.3
Build-Depends: debhelper (>=9~), postgresql-server-dev-all (>= 141~)
Standards-Version: 4.5.0
Rules-Requires-Root: no
Build-Depends: debhelper-compat (= 13), postgresql-all (>= 217~)
Homepage: https://hypopg.readthedocs.io/
Vcs-Browser: https://github.com/hypopg/hypopg
Vcs-Git: https://github.com/hypopg/hypopg.git

17
debian/rules vendored
View file

@ -3,26 +3,15 @@
PKGVER = $(shell dpkg-parsechangelog | awk -F '[:-]' '/^Version:/ { print substr($$2, 2) }')
EXCLUDE = --exclude-vcs --exclude=debian
include /usr/share/postgresql-common/pgxs_debian_control.mk
override_dh_auto_build:
# do nothing
override_dh_auto_test:
# nothing to do here, upstream tests used, see debian/tests/*
override_dh_auto_install:
# build all supported versions
+pg_buildext loop postgresql-%v-hypopg
override_dh_installdocs:
dh_installdocs --all CONTRIBUTORS.md README.md
rm -rvf debian/*/usr/share/doc/postgresql-doc-*
override_dh_installchangelogs:
dh_installchangelogs CHANGELOG.md upstream
dh_installchangelogs CHANGELOG.md
orig: debian/control clean
cd .. && tar czf hypopg_$(PKGVER).orig.tar.gz $(EXCLUDE) hypopg-$(PKGVER)
%:
dh $@
dh $@ --with pgxs_loop

2
debian/tests/control vendored
View file

@ -1,3 +1,3 @@
Depends: @, postgresql-server-dev-all, postgresql-contrib-9.3, postgresql-contrib-9.4, postgresql-contrib-9.5, postgresql-contrib-9.6, postgresql-contrib-10
Depends: @, make, postgresql-contrib-13
Tests: installcheck
Restrictions: allow-stderr

2
debian/tests/control.in vendored
View file

@ -1,3 +1,3 @@
Depends: @, postgresql-server-dev-all, postgresql-contrib-PGVERSION
Depends: @, make, postgresql-contrib-PGVERSION
Tests: installcheck
Restrictions: allow-stderr