sync/ports
1
0
Fork 0
mirror of https://git.freebsd.org/ports.git synced 2025-04-28 09:36:41 -04:00
Code Issues Projects Releases Packages Wiki Activity Actions

databases/py-pgmigrate: update to 1.0.9

Browse source 
Changelog: https://github.com/yandex/pgmigrate/releases/tag/1.0.9

PR:		283465
Approved by:	dmitry.wagin@ya.ru (maintainer)
This commit is contained in:
Älven 2025-01-04 18:52:48 +01:00 • committed by Robert Clausecker
parent 2ae03d3a68
commit 26d5b3fe27
3 changed files with 17 additions and 7 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

7
databases/py-pgmigrate/Makefile
View file

@ -1,6 +1,5 @@
PORTNAME= pgmigrate
PORTVERSION= 1.0.8
PORTREVISION= 1
DISTVERSION= 1.0.9
CATEGORIES= databases python
PKGNAMEPREFIX= ${PYTHON_PKGNAMEPREFIX}
@ -12,8 +11,8 @@ LICENSE= PostgreSQL
LICENSE_FILE= ${WRKSRC}/LICENSE
RUN_DEPENDS= ${PYTHON_PKGNAMEPREFIX}psycopg2>=2.8.2:databases/py-psycopg2@${PY_FLAVOR} \
${PYTHON_PKGNAMEPREFIX}sqlparse>=0.3.0:databases/py-sqlparse@${PY_FLAVOR} \
${PYTHON_PKGNAMEPREFIX}pyyaml>=5.2:devel/py-pyyaml@${PY_FLAVOR}
${PYTHON_PKGNAMEPREFIX}pyyaml>=5.2:devel/py-pyyaml@${PY_FLAVOR} \
${PYTHON_PKGNAMEPREFIX}sqlparse>=0.3.0:databases/py-sqlparse@${PY_FLAVOR}
USES= python
USE_GITHUB= yes

6
databases/py-pgmigrate/distinfo
View file

@ -1,3 +1,3 @@
TIMESTAMP = 1710627814
SHA256 (yandex-pgmigrate-1.0.8_GH0.tar.gz) = d54679b5c7395d183c92d3a6f1a01186454768bb4c75385adc14fa9ef812afb5
SIZE (yandex-pgmigrate-1.0.8_GH0.tar.gz) = 31152
TIMESTAMP = 1734776042
SHA256 (yandex-pgmigrate-1.0.9_GH0.tar.gz) = 0b411fd495b1fcbc1c5bbbae07ca02c403d44f815b700405159e30c82eb775db
SIZE (yandex-pgmigrate-1.0.9_GH0.tar.gz) = 31656

11
databases/py-pgmigrate/pkg-descr
View file

@ -1 +1,12 @@
PGmigrate is a database migration tool developed by Yandex.
PGmigrate has the following key-features:
- Transactional and nontransactional migrations: you can enjoy whole power of
PostgreSQL DDL
- Callbacks: you can run some DDL on specific steps of migration process
(e.g. drop some code before executing migrations, and create it back after
migrations were applied)
- Online migrations: you can execute series of transactional migrations and
callbacks in a single transaction (so, if something goes wrong simple ROLLBACK
will bring you in consistent state)