Hello community, here is the log from the commit of package python3-alembic for openSUSE:Factory checked in at 2016-07-27 16:13:20 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Comparing /work/SRC/openSUSE:Factory/python3-alembic (Old) and /work/SRC/openSUSE:Factory/.python3-alembic.new (New) ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "python3-alembic" Changes: -------- --- /work/SRC/openSUSE:Factory/python3-alembic/python3-alembic.changes 2016-07-21 08:14:37.000000000 +0200 +++ /work/SRC/openSUSE:Factory/.python3-alembic.new/python3-alembic.changes 2016-07-27 16:13:30.000000000 +0200 @@ -1,0 +2,42 @@ +Tue Jul 26 15:36:58 UTC 2016 - [email protected] + +- update to version 0.8.7: + * [bug] [versioning] Fixed bug where upgrading to the head of a + branch which is already present would fail, only if that head were + also the dependency of a different branch that is also upgraded, + as the revision system would see this as trying to go in the wrong + direction. The check here has been refined to distinguish between + same-branch revisions out of order vs. movement along sibling + branches. + * [bug] [versioning] Adjusted the version traversal on downgrade + such that we can downgrade to a version that is a dependency for a + version in a different branch, without needing to remove that + dependent version as well. Previously, the target version would be + seen as a “merge point” for it’s normal up-revision as well as the + dependency. This integrates with the changes for #377 and #378 to + improve treatment of branches with dependencies overall. + * [bug] [versioning] Fixed bug where a downgrade to a version that + is also a dependency to a different branch would fail, as the + system attempted to treat this as an “unmerge” of a merge point, + when in fact it doesn’t have the other side of the merge point + available for update. + * [bug] [versioning] Fixed bug where the “alembic current” command + wouldn’t show a revision as a current head if it were also a + dependency of a version in a different branch that’s also + applied. Extra logic is added to extract “implied” versions of + different branches from the top-level versions listed in the + alembic_version table. + * [bug] [versioning] Fixed bug where a repr() or str() of a Script + object would fail if the script had multiple dependencies. + * [bug] [autogenerate] Fixed bug in autogen where if the DB + connection sends the default schema as “None”, this “None” would + be removed from the list of schemas to check if include_schemas + were set. This could possibly impact using include_schemas with + SQLite. + * [bug] [batch] Small adjustment made to the batch handling for + reflected CHECK constraints to accommodate for SQLAlchemy 1.1 now + reflecting these. Batch mode still does not support CHECK + constraints from the reflected table as these can’t be easily + differentiated from the ones created by types such as Boolean. + +------------------------------------------------------------------- Old: ---- alembic-0.8.6.tar.gz New: ---- alembic-0.8.7.tar.gz ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Other differences: ------------------ ++++++ python3-alembic.spec ++++++ --- /var/tmp/diff_new_pack.I7Ms2m/_old 2016-07-27 16:13:31.000000000 +0200 +++ /var/tmp/diff_new_pack.I7Ms2m/_new 2016-07-27 16:13:31.000000000 +0200 @@ -17,7 +17,7 @@ Name: python3-alembic -Version: 0.8.6 +Version: 0.8.7 Release: 0 Url: https://pypi.python.org/pypi/alembic Summary: A database migration tool for SQLAlchemy ++++++ alembic-0.8.6.tar.gz -> alembic-0.8.7.tar.gz ++++++ ++++ 7786 lines of diff (skipped)
