[ckan-dev] After upgrading extensions CKAN fails due to new SQLAlchemy.

Mon Oct 7 11:55:53 UTC 2013

Hilde,

Pleased to hear my solution worked.

Ah yes, ckanext-spatial asks for GeoAlchemy which must pull in
SQLAlchemy, but I don't see how that would override ckan's
pip-requirements.txt, whichever order you did them in. Anyway,
probably not worth pursuing.

David

On 7 October 2013 10:47, Hildegard Gerlach
<hildegard.gerlach at jrc.ec.europa.eu> wrote:
> Hi David,
>
> after I had fixed it I tried again to find out why I get a wrong version of
> sqlalchemy.
> It happens when upgrading the spatial extension to the master branch
>
> Here an extract of the screen doing pip install --upgrade -r
> pip-requirements.txt
>
>   Found existing installation: pyparsing 1.5.6
>     Uninstalling pyparsing:
>       Successfully uninstalled pyparsing
>   Running setup.py install for pyparsing
>   Found existing installation: SQLAlchemy 0.7.8
>     Uninstalling SQLAlchemy:
>       Successfully uninstalled SQLAlchemy
>   Running setup.py install for SQLAlchemy
> /usr/local/mtester.ies.jrc.it/pyenv/build/SQLAlchemy/setup.py:118:
> DeprecationWarning: Features are deprecated and will be removed in a future
> version. See http://bitbucket.org/pyp                               .
>       ext_modules=ext_modules
>     /usr/lib64/python2.6/distutils/core.py:113: DeprecationWarning: Features
> are deprecated and will be removed in a future version. See
> http://bitbucket.org/pypa/setuptools/65.
>       _setup_distribution = dist = klass(attrs)
>     building 'sqlalchemy.cprocessors' extension
>     gcc -pthread -fno-strict-aliasing -O2 -g -pipe -Wall
> -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector
> --param=ssp-buffer-size=4 -m64 -mtune=generic -D_GNU_SOURCE -fPIC -fwrap
> -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector
> --param=ssp-buffer-size=4 -m64 -mtune=generic -D_GNU_SOURCE -fPIC -fwrapv
> -fPIC -I/usr/include/python2.6 -c lib/sq
> sion/processors.c -o
> build/temp.linux-x86_64-2.6/lib/sqlalchemy/cextension/processors.o
>     gcc -pthread -shared
> build/temp.linux-x86_64-2.6/lib/sqlalchemy/cextension/processors.o
> -L/usr/lib64 -lpython2.6 -o
> build/lib.linux-x86_64-2.6/sqlalchemy/cprocessors.so
>     building 'sqlalchemy.cresultproxy' extension
>     gcc -pthread -fno-strict-aliasing -O2 -g -pipe -Wall
> -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector
> --param=ssp-buffer-size=4 -m64 -mtune=generic -D_GNU_SOURCE -fPIC -fwrap
> -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector
> --param=ssp-buffer-size=4 -m64 -mtune=generic -D_GNU_SOURCE -fPIC -fwrapv
> -fPIC -I/usr/include/python2.6 -c lib/sq
> sion/resultproxy.c -o
> build/temp.linux-x86_64-2.6/lib/sqlalchemy/cextension/resultproxy.o
>     gcc -pthread -shared
> build/temp.linux-x86_64-2.6/lib/sqlalchemy/cextension/resultproxy.o
> -L/usr/lib64 -lpython2.6 -o
> build/lib.linux-x86_64-2.6/sqlalchemy/cresultproxy.so
>     building 'sqlalchemy.cutils' extension
>     gcc -pthread -fno-strict-aliasing -O2 -g -pipe -Wall
> -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector
> --param=ssp-buffer-size=4 -m64 -mtune=generic -D_GNU_SOURCE -fPIC -fwrap
> -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector
> --param=ssp-buffer-size=4 -m64 -mtune=generic -D_GNU_SOURCE -fPIC -fwrapv
> -fPIC -I/usr/include/python2.6 -c lib/sq
> sion/utils.c -o
> build/temp.linux-x86_64-2.6/lib/sqlalchemy/cextension/utils.o
>     gcc -pthread -shared
> build/temp.linux-x86_64-2.6/lib/sqlalchemy/cextension/utils.o -L/usr/lib64
> -lpython2.6 -o build/lib.linux-x86_64-2.6/sqlalchemy/cutils.so
>     warning: no files found matching '*.jpg' under directory 'doc'
>     no previously-included directories found matching 'doc/build/output'
>   Found existing installation: python-dateutil 1.5
>     Uninstalling python-dateutil:
>       Successfully uninstalled python-dateutil
>   Running setup.py install for python-dateutil
>   Found existing installation: pytz 2013.7
>     Uninstalling pytz:
>       Successfully uninstalled pytz
>   Running setup.py install for pytz
>     warning: no files found matching '*.pot' under directory 'pytz'
>     warning: no previously-included files found matching 'test_zdump.py'
> Successfully installed GeoAlchemy Shapely owslib lxml argparse pyparsing
> SQLAlchemy python-dateutil pytz
> Cleaning up...
>
> Hilde
>
>
>
> On 10/5/2013 10:29 AM, David Read wrote:
>>
>> Hilde,
>>
>> This should correct your version of sqlalchemy, and correct any others
>> that got wrong versions:
>>
>> pip install -r /usr/lib/ckan/default/src/ckan/requirements.txt
>>
>> I've no clue how you got the wrong version of sqlalchemy as in the
>> CKAN world it is only specified in ckan's requirements file, with a
>> fixed version. Unless you actually did 'pip install sqlalchemy' or
>> installed something unrelated to CKAN that asked for it. Curious!
>>
>> David
>>
>> On 4 October 2013 14:52, Hildegard Gerlach
>> <hildegard.gerlach at jrc.ec.europa.eu> wrote:
>>>
>>> Hello,
>>>
>>> I just upgraded CKAN and the harvesting and spatial extension to the
>>> master
>>> branch. I got the same error.
>>>
>>> I think it happened upgrading the spatial extension.
>>>
>>> What can I do to get another version of sqalchemy ?
>>>
>>> Hilde
>>>
>>>
>>> On 9/23/2013 5:13 PM, Vitor Baptista wrote:
>>>
>>> Hi Hendrik,
>>>
>>> You shouldn't be able to upgrade SQLAlchemy, as we have version 0.7.8
>>> pinned
>>> in requirements.txt. Did you get it installing an extension's
>>> requirements.txt? Which one?
>>>
>>> Cheers,
>>>
>>> Vítor Baptista
>>>
>>> Developer  |  http://vitorbaptista.com | LinkedIn | @vitorbaptista
>>>
>>> The Open Knowledge Foundation
>>>
>>> Empowering through Open Knowledge
>>>
>>> http://okfn.org/  |  @okfn  |  OKF on Facebook  |  Blog  |  Newsletter
>>>
>>>
>>>
>>> 2013/9/23 Henrik Aagaard Sørensen <BU1G at tmf.kk.dk>
>>>>
>>>> After upgrading all extensions I get the following error:
>>>>
>>>> ValueError: VDM only works with SQLAlchemy versions 0.4 through 0.7,
>>>> not:
>>>> 0.8.2
>>>>
>>>>
>>>>
>>>> Any idea on how to update VDM?
>>>>
>>>>
>>>>
>>>>
>>>>
>
>
>
> _______________________________________________
> ckan-dev mailing list
> ckan-dev at lists.okfn.org
> http://lists.okfn.org/mailman/listinfo/ckan-dev
> Unsubscribe: http://lists.okfn.org/mailman/options/ckan-dev