Hello community,

here is the log from the commit of package python3-alembic for openSUSE:Factory 
checked in at 2015-04-30 11:50:30
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
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  
2015-01-25 21:14:58.000000000 +0100
+++ /work/SRC/openSUSE:Factory/.python3-alembic.new/python3-alembic.changes     
2015-04-30 11:50:32.000000000 +0200
@@ -1,0 +2,48 @@
+Sat Apr 25 16:14:28 UTC 2015 - [email protected]
+
+- update to 0.7.5.post2:
+  * Added a new feature Config.attributes, to help with the use
+    case of sharing state such as engines and connections on the
+    outside with a series of Alembic API calls; also added a new
+    cookbook section to describe this simple but pretty important
+    use case.
+  * The format of the default env.py script has been refined a bit;
+    it now uses context managers not only for the scope of the
+    transaction, but also for connectivity from the starting
+    engine. The engine is also now called a “connectable” in
+    support of the use case of an external connection being passed
+    in.
+  * Added support for “alembic stamp” to work when given “heads” as
+    an argument, when multiple heads are present.
+  * The --autogenerate option is not valid when used in conjunction
+    with “offline” mode, e.g. --sql. This now raises a
+    CommandError, rather than failing more deeply later on. Pull
+    request courtesy Johannes Erdfelt.
+  * Fixed bug where the mssql DROP COLUMN directive failed to
+    include modifiers such as “schema” when emitting the DDL.
+  * Postgresql “functional” indexes are necessarily skipped from
+    the autogenerate process, as the SQLAlchemy backend currently
+    does not support reflection of these structures. A warning is
+    emitted both from the SQLAlchemy backend as well as from the
+    Alembic backend for Postgresql when such an index is detected.
+  * Fixed bug where MySQL backend would report dropped unique
+    indexes and/or constraints as both at the same time. This is
+    because MySQL doesn’t actually have a “unique constraint”
+    construct that reports differently than a “unique index”, so it
+    is present in both lists. The net effect though is that the
+    MySQL backend will report a dropped unique index/constraint as
+    an index in cases where the object was first created as a
+    unique constraint, if no other information is available to make
+    the decision. This differs from other backends like Postgresql
+    which can report on unique constraints and unique indexes
+    separately.
+  * Fixed bug where using a partial revision identifier as the
+    “starting revision” in --sql mode in a downgrade operation
+    would fail to resolve properly.
+- set minimum version for SQLAlchemy to 0.7.6
+- remove unzip from BuildRequires, unneeded
+- use update-alternatives for alembic binary
+- always run the tests when building the package
+- add python3-mock as BuildRequires for the tests
+
+-------------------------------------------------------------------

Old:
----
  alembic-0.7.4.tar.gz

New:
----
  alembic-0.7.5.post2.tar.gz

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Other differences:
------------------
++++++ python3-alembic.spec ++++++
--- /var/tmp/diff_new_pack.6Iii6o/_old  2015-04-30 11:50:32.000000000 +0200
+++ /var/tmp/diff_new_pack.6Iii6o/_new  2015-04-30 11:50:32.000000000 +0200
@@ -1,7 +1,7 @@
 #
 # spec file for package python3-alembic
 #
-# Copyright (c) 2015 SUSE LINUX Products GmbH, Nuernberg, Germany.
+# Copyright (c) 2015 SUSE LINUX GmbH, Nuernberg, Germany.
 #
 # All modifications and additions to the file contributed by third parties
 # remain the property of their copyright owners, unless otherwise agreed
@@ -17,7 +17,7 @@
 
 
 Name:           python3-alembic
-Version:        0.7.4
+Version:        0.7.5.post2
 Release:        0
 Url:            https://pypi.python.org/pypi/alembic
 Summary:        A database migration tool for SQLAlchemy
@@ -28,13 +28,15 @@
 BuildRequires:  python3
 BuildRequires:  python3-devel
 BuildRequires:  python3-distribute
-BuildRequires:  unzip
 # Test requirements:
 BuildRequires:  python3-Mako
-BuildRequires:  python3-SQLAlchemy >= 0.7.5
+BuildRequires:  python3-SQLAlchemy >= 0.7.6
+BuildRequires:  python3-mock
 BuildRequires:  python3-nose >= 0.11
 Requires:       python3-Mako
-Requires:       python3-SQLAlchemy >= 0.7.5
+Requires:       python3-SQLAlchemy >= 0.7.6
+Requires(post): update-alternatives
+Requires(postun): update-alternatives
 BuildArch:      noarch
 
 %description
@@ -59,16 +61,29 @@
 
 %install
 python3 setup.py install --prefix=%{_prefix} --root=%{buildroot}
-# Avoid conflict with alembic python2 package
-mv %{buildroot}/%{_bindir}/alembic %{buildroot}/%{_bindir}/alembic-%{py3_ver}
-
-# (posophe) Tests fail for every open/SUSE version; disable it
-#%check
-#nosetests-%{py3_ver}
+# update-alternatives
+mv %{buildroot}%{_bindir}/alembic %{buildroot}%{_bindir}/alembic-%{py3_ver}
+mkdir -p %{buildroot}%{_sysconfdir}/alternatives
+touch %{buildroot}%{_sysconfdir}/alternatives/alembic
+ln -sf %{_sysconfdir}/alternatives/alembic %{buildroot}%{_bindir}/alembic
+
+%check
+python3 setup.py test
+
+%post
+update-alternatives \
+       --install %{_bindir}/alembic alembic %{_bindir}/alembic-%{py3_ver} 30
+
+%postun
+if [ $1 -eq 0 ] ; then
+       update-alternatives --remove alembic %{_bindir}/alembic-%{py3_ver}
+fi
 
 %files
 %defattr(-,root,root,-)
 %doc CHANGES LICENSE README.rst html
+%ghost %{_sysconfdir}/alternatives/alembic
+%{_bindir}/alembic
 %{_bindir}/alembic-%{py3_ver}
 %{python3_sitelib}/*
 


Reply via email to