migrate_0.7.2-2~bpo60+1_amd64.changes is NEW
(new) migrate_0.7.2-2~bpo60+1.debian.tar.gz optional python
(new) migrate_0.7.2-2~bpo60+1.dsc optional python
(new) migrate_0.7.2.orig.tar.gz optional python
(new) python-migrate_0.7.2-2~bpo60+1_all.deb optional python
Database schema migration for SQLAlchemy
Inspired by Ruby on Rails' migrations, migrate provides a way to deal
with database schema changes in SQLAlchemy projects.
.
SQLAlchemy-migrate is build on top of SQLAlchemy and provides a changeset
and a versioning API for database schemas as well as a script utilizing
these APIs. The database change sets are managed in a file based
repository allowing upgrades and downgrades of database schema versions.
The change sets may consist of Python code facilitating the changeset API
or SQL scripts.
.
SQLAlchemy-migrate has support for MySQL, PostgreSQL, SQLite and Oracle
databases. The support for Oracle is not as well tested as the support for
the other database systems.
Changes:
migrate (0.7.2-2~bpo60+1) squeeze-backports; urgency=low
.
* Rebuild for squeeze-backports.
.
migrate (0.7.2-2) unstable; urgency=low
.
* Fix "FTBFS: URLError: <urlopen error [Errno -2] Name or service not
known>" by removing support for python-sphinxcontrib.issuetracker
(Closes: #649621)
- use debian/patches/disable_issuetracker.patch (thanks to Michael
Terry)
- debian/control: remove Build-Depends
python-sphinxcontrib.issuetracker
.
migrate (0.7.2-1) unstable; urgency=low
.
* New upstream release.
* debian/control:
- add python-sphinxcontrib.issuetracker to Build-Depends-Indep
- drop X-Python-Version
- bump python-sphinx build dependency to >= 1.0.7+dfsg~ (for
dh_sphinxdoc)
- bump python-sqlalchemy dependency to >= 0.6 (upstream support for
older version has been dropped)
- add libjs-sphinxdoc and ${sphinxdoc:Depends} to Depends
- remove libjs-jquery from Depends (added automatically by
dh_sphinxdoc)
* debian/rules:
- remove treatment for manage.py_tmpl (removed from upstream release)
- use dh_sphinxdoc
- remove manual sphinx doc installation
* add debian/patches/use-local-intersphinx.patch and
debian/patches/series to avoid fetching objects.inv from the web
.
migrate (0.7.1-2) unstable; urgency=low
.
* Fix "please update dependency on python-sqlalchemy", rebuild to fix
python-sqlalchemy dependency (Closes: #636900)
.
migrate (0.7.1-1) unstable; urgency=low
.
* New upstream release (better fix for column creation for columns with
foreign keys).
.
migrate (0.7-1) unstable; urgency=low
.
* New upstream release.
* add compatibility with SQLAlchemy 0.7
* debian/control: remove unneeded Breaks: ${python:Breaks}
.
migrate (0.6.1-3) unstable; urgency=low
.
* debian/rules: add --buildsystem=python_distutils, remove
override_dh_auto_build
* debian/control: bump Standards-Version to 3.9.2 (no changes needed)
.
migrate (0.6.1-1) unstable; urgency=low
.
* New upstream release.
* debian/control:
- remove dependency on python-support
- bump python dependency version to 2.6.5~
- drop XS-Python-Version, add X-Python-Version
- add Breaks: ${python:Breaks}
* debian/rules:
- add --with python2 to dh call
* remove debian/patches/use-absolute-imports-of-exception-
classes.patch that has been applied upstream
.
migrate (0.6-5) unstable; urgency=low
.
* upload to unstable
.
migrate (0.6-5~exp1) experimental; urgency=low
.
* Fix "objects.inv should not be compressed" exclude objects.inv from
dh_compress in debian/rules, thanks for the report to Michael Fladischer
(Closes: #608747)
* Fix "AttributeError: 'module' object has no attribute
'MigrateDeprecationWarning'" include patch
debian/patches/use-absolute-imports-of-exception-classes.patch by Etienne
Millon (Closes: #609259)
Override entries for your package:
Announcing to debian-backports-changes@lists.debian.org
Your package contains new components which requires manual editing of
the override file. It is ok otherwise, so please be patient. New
packages are usually added to the override file about once a week.
You may have gotten the distribution wrong. You'll get warnings above
if files already exist in other distributions.
.
Reply to: