I'm working on an old version of Plone (buildout for Plone 3.3.6, coming from Plone 3.1).
It includes a custom product which relies on p4a.videoembed and a few other p4a related products. When I run 'bin/buildout' I get the following error:
Installing instance1.
While:
Installing instance1.
Error: There is a version conflict.
We already have: p4a.video 1.3
but p4a.plonevideoembed 1.3 requires 'p4a.video>1.3'.
I checked there is no p4a.video > 1.3 in pypi so, of course it won't retrieve for a higher version of p4a.video.
The solution was to pin p4a.plonevideoembed to an older version. I added a [versions] section to my buildout and "pinned" p4a.plonevideoembed to an older version.
[versions]
p4a.plonevideoembed = 1.1
Related
Having an issue running airflow on my M1 Mac. Keeps erroring out with error in Flask-OpenID setup command: use_2to3 is invalid. I have setuptools < 58 and still having issues.
ERROR: Could not find a version that satisfies the requirement flask-openid==1.2.5 (from versions: 0.9, 0.9.1, 1.0, 1.0.1, 1.1, 1.1.1, 1.2, 1.2.1, 1.2.2, 1.2.3, 1.2.4, 1.2.5, 1.3.0)
ERROR: No matching distribution found for flask-openid==1.2.5
Yes. It's been fixed in flask_openid 1.2.6 (It's not a problem with Airflow but with FlaskOpenID).
Looks like for some reason your setuptools is not what you think it is. See:
https://github.com/pallets-eco/flask-openid/issues/59
You have not explained a crucial things - how you are installing airflow, neither which version of Airflow you try to install - which does not help in trying to help you unfortunately, so I have to make some guesses. Here is what you can do if you cannot - for any reason - downgrade to setuptools < 0.58.
If you are using Airlfow 2 and using constraints (as you should - this is the only supported way https://airflow.apache.org/docs/apache-airflow/stable/installation/installing-from-pypi.html) for some older version of Airflow, then possibly flask-openid is 1.2.5 in those old constraint versions. Please check it and if you REALLY want to stay with an older version, then you can download the constraint file locally, modify flask-openid version to 1.2.6 and point to the file instead of the github URL as you should do normally (If you don't use constraints - start using them immediately).
However, better option than installing an old version of Airflow, will be to update to the latest version of Airflow (currently 2.2.2 but we are about to start voting on 2.2.3), where this problem is for sure fixed (also in few other versions). Airflow folows SemVer so you should be generally safe to migrate to 2.2.2 if you've used an earlier version of Airflow 2.
If you are trying to install Airflow 1.10.* - then don't do it. Move Airflow 2 immediately. Airflow 1.10 has reached end of life in June 2021 and it's almost half a year as it did not receive any fixes - it won't receive any fixes for the Flask OpenID problem, so you are pretty much on your own here.
Also you make yourself vulnerable to unpatched security issues (Airlfow 1.10 stopped receiving also critical security fixes as of June 2021).
I've downloaded a working UWP solution targeting 16299 which I changed to target 14393 (Anniversary) so it would work on all Windows 10 Phones as well. Apart from the obvious errors where the solution uses newer W10 version methods and namespaces, I also get:
Error NU1202 Package Microsoft.Data.Sqlite.Core 2.0.0 is not compatible with uap10.0.14393 (UAP,Version=v10.0.14393) / win10-x64. (multiple times)
But according to https://blogs.windows.com/buildingapps/2017/02/06/using-sqlite-databases-uwp-apps/ Microsoft SQLite should work from 14393.
I've tried installing the oldest version number available (2.0.0 instaed of 2.1.0 now included) but that doesn't change the error.
How can I solve this problem?
Dick
sqlite.core is the core version and will work only from fall creators update and above. if you want to use sqlite on older versions then you can see details here : https://learn.microsoft.com/en-us/windows/uwp/data-access/sqlite-databases
phpunit had an option --log-xml in Version 3.2.8, but it vanished in version 3.7.24.
On the other side, Version 3.7.24 has an option --log-junit, which was not available in version 3.2.8 of phpunit. At what version(s) did the change occur?
As I cannot find a corresponding changelog or similar, I cannot answer this question myself.
The PHPUnit manuals contain the information:
3.3 (Sep 2008): http://phpunit.de/manual/3.3/en/textui.html#textui.clioptions
contains --log-xml
3.4 (Sep 2009): http://phpunit.de/manual/3.4/en/textui.html#textui.clioptions
does not contain --log-xml but --log-junit
I wrote a small module that extends https://raw.github.com/collective/buildout.plonetest/master/test-4.2.x.cfg. If I change the version from 4.2 to 4.3 it throws the error when running bin/buildout:
...
While:
Installing.
Getting section test.
Initializing section test.
Installing recipe zc.recipe.testrunner.
Error: There is a version conflict.
We already have: zc.recipe.egg 2.0.0
I suppose that the error is produced because some packages listed in the buildout.plonetest have conflicting versions and that is a bug in the 4.3 version set. I'm right or I'm making a mistake in the buildout.cfg file?
The buildout that I'm using is:
[buildout]
extends =
https://raw.github.com/collective/buildout.plonetest/master/test-4.2.x.cfg
package-name = conaride.theme
package-extras = [test]
[instance]
eggs +=
Pillow
[test]
defaults = ['-s', '${buildout:package-name}', '--auto-color', '--auto-progress']
There is no bug in the 4.3 version set; you need to fix the version conflict. Try any or all of the following approaches to this very-common problem:
(1) Remove the already-downloaded version and re-run Buildout e.g.:
$ rm -rf eggs/zc.recipe.egg\*
$ bin/buildout
(2) Remove the installed config and re-run Buildout e.g.:
$ rm .installed.cfg
$ bin/buildout
(3) Specify the version you want to use in your local config e.g.
[versions]
zc.recipe.egg = 2.0.0
I want to use mysql form ploneformgen, but I
Can't buildout plone.
buildout log http://pastie.org/5345272.js
Getting required 'MySQL-python>=1.2.1'
required by Products.ZMySQLDA 3.1.1.
We have no distributions for MySQL-python that satisfies 'MySQL-python>=1.2.1'.
Getting distribution for 'MySQL-python>=1.2.1'.
Running easy_install:
/usr/local/Plone/Python-2.6/bin/python "-c" "from setuptools.command.easy_install import main; main()" "-mUNxd" "/usr/local/Plone/zeocluster/../buildout-cache/eggs/tmpDSODu0" "-Z" "/usr/local/Plone/buildout-cache/downloads/dist/MySQL-python-1.2.4c1.zip"
path=/usr/local/Plone/buildout-cache/eggs/distribute-0.6.21-py2.6.egg
Processing MySQL-python-1.2.4c1.zip
Running MySQL-python-1.2.4c1/setup.py -q bdist_egg --dist-dir /tmp/easy_install-gFbWLf/MySQL-python-1.2.4c1/egg-dist-tmp-16g1TE
The required version of distribute (>=0.6.28) is not available,
and can't be installed while this script is running. Please
install a more recent version first, using
'easy_install -U distribute'.
(Currently using distribute 0.6.19 (/usr/local/Plone/Python-2.6/lib/python2.6/site-packages/distribute-0.6.19-py2.6.egg))
error: Setup script exited with 2
An error occured when trying to install MySQL-python 1.2.4c1. Look above this message for any errors that were output by easy_install.
While:
Installing client1.
Getting distribution for 'MySQL-python>=1.2.1'.
Error: Couldn't install: MySQL-python 1.2.4c1
*************** PICKED VERSIONS ****************
[versions]
Products.PloneFormGen = 1.7.1
Products.ZMySQLDA = 3.1.1
collective.classifieds = 1.6
plone.app.ldap = 1.2.8
quintagroup.dropdownmenu = 1.2.5
quintagroup.pfg.captcha = 1.0.5
zettwerk.ui = 1.1.1
buildout conf http://pastie.org/5345300
some links:
http://blog.mysqlboy.com/2010/08/installing-mysqldb-python-module.html
http://plone.293351.n2.nabble.com/Plone-amp-MySQL-No-quot-Z-MYSQL-Database-Connection-quot-from-ZMI-td5487160.html
It appears the MySQLdb egg requires a newer version of distribute:
The required version of distribute (>=0.6.28) is not available,
and
(Currently using distribute 0.6.19 (/usr/local/Plone/Python-2.6/lib/python2.6/site-packages/distribute-0.6.19-py2.6.egg))
Upgrade your distribute egg first; if you are using the unified installer, for example, versions.cfg pins the version. If so, edit versions.cfg to correct the version number there:
[versions]
...
# Buildout infrastructure
...
distribute = 0.6.28
While you have a perfectly good answer for the specific problem, I highly recommend forgetting about ZMySQLDA and use SQLAlchemyDA which gives you access to any database supported by SQLAlchemy (I've used all of MySQL, PostGreSQL, Oracle, SQLServer) with a single product, and is better supported.