Am Donnerstag, 26. Mai 2016, 10:54:20 schrieb Todd Rme:

What packages have the problem? What are the Requires and BuildRequires in the spec files?

See: https://build.opensuse.org/package/show/Application:ERP:Tryton:4.0/trytond_s... As build requiement is has just python3-setuptools. For run it needs some other trytond-modules (but that should not be an issue) Cheers Axel

On Thu, May 26, 2016 at 5:25 AM, Axel Braun wrote:

...

Hello,

in between I managed to get some python3 packages build. But on Installation I get an error from an unsolved requirement:

Requires python < PYTHON-NOT-FOUND python >= PYTHON-NOT-FOUND python python3 python(abi) = 3.4 python3-base ....

Anyone seen this before? and knows how I could suppres the requirement?

-- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org

Hi Todd,

Gesendet: Freitag, 27. Mai 2016 um 16:35 Uhr Von: "Todd Rme" An: "openSUSE Packaging Mailingliste" Betreff: Re: [opensuse-packaging] python3 - Symbol PYTHON-NOT-FOUND

On Fri, May 27, 2016 at 2:52 AM, Axel Braun wrote:

...

Am Donnerstag, 26. Mai 2016, 10:54:20 schrieb Todd Rme:

...

What packages have the problem? What are the Requires and BuildRequires in the spec files?

See: https://build.opensuse.org/package/show/Application:ERP:Tryton:4.0/trytond_s... As build requiement is has just python3-setuptools. For run it needs some other trytond-modules (but that should not be an issue)

You are mixing up python 2 and python 3. %py_requires and %python_sitelib come from python 2, but you are building against python 3. Also, %py_requires is no longer needed at all. You should get rid of %py_requires completely, and use %{python3_sitelib}. The same applies for all the other python or python 3 packages in the repo.

Thanks for this hint - seems I did not catch all python-sitelib strings for conversion.

Further, I suggest you follow python package file naming guidelines [1]. Specifically, the packages should be of the format "python3-{NAME}", where "{NAME}" is the name used for the package in pypi [2]. So for example it should be "python3-trytond_sale", not just "trytond_sale"

Thanks for this hint as well. I feel at this point the project naming should overrule the python naming - first of all it is a Tryton module and should follow their naming convention. Additionally, it will never show up in d.l:p, so this should not create confusion Best regards Axel -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org

Morning all, Am Freitag, 27. Mai 2016, 10:35:20 schrieb Todd Rme:

...

See: https://build.opensuse.org/package/show/Application:ERP:Tryton:4.0/trytond _sale As build requiement is has just python3-setuptools. For run it needs some other trytond-modules (but that should not be an issue)

Cheers Axel

You are mixing up python 2 and python 3. %py_requires and %python_sitelib come from python 2, but you are building against python 3. Also, %py_requires is no longer needed at all. You should get rid of %py_requires completely, and use %{python3_sitelib}. The same applies for all the other python or python 3 packages in the repo.

It seems that I did not get rid of this problem for all packages. Another quite simple package https://build.opensuse.org/package/show/Application:ERP:Tryton:4.0/trytond_c... is still struggeling the python < PYTHON-NOT-FOUND dependency issue, although it uses only python 3 packages. Is there a way to override the dependency? Thanks Axel -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org

Hello, Am Sonntag, 5. Juni 2016, 11:07:12 CEST schrieb Axel Braun:

Am Sonntag, 5. Juni 2016, 10:52:57 schrieb Axel Braun:

...

It seems that I did not get rid of this problem for all packages. Another quite simple package https://build.opensuse.org/package/show/Application:ERP:Tryton:4.0/t rytond_c urrency is still struggeling the python < PYTHON-NOT-FOUND dependency issue, although it uses only python 3 packages. Is there a way to override the dependency?

Every now and then you find the reason by chance... it is not sufficient to uncomment the line #%py_requires It has to be removed completely to get rid of python < PYTHON-NOT-FOUND

That's not too surprising - rpm macros still gets expanded even if they are commented out, and this will explode if they expand to more than one line. # rpm --eval '%{py_requires}' BuildRequires: /usr/bin/python PreReq: python = 2.7 So you basically end up with # BuildRequires: /usr/bin/python PreReq: python = 2.7 (s/2.7/PYTHON_NOT_FOUND/ in your case) When commenting out a macro, you should remove the % sign to avoid this. BTW: to explain where PYTHON_NOT_FOUND comes from: # grep -r -A2 py_requires /etc/rpm/ /etc/rpm/macros.python:%py_requires(d) \ /etc/rpm/macros.python-BuildRequires: /usr/bin/python %{-d:python-devel} \ /etc/rpm/macros.python-PreReq: python = %{py_ver} # grep -r py_ver /etc/rpm/ | head -n1 /etc/rpm/macros.python:%py_ver %(python -c "import sys; v=sys.version_info[:2]; print '%%d.%%d'%%v" 2>/dev/null || echo PYTHON-NOT-FOUND) So for some reason python isn't installed, and %py_ver gets set to PYTHON_NOT_FOUND instead of the python version. Regards, Christian Boltz -- Und wenn du denkst dich mag niemand mehr, dann kommt der Christopher und siggt dich sehr. [Christopher Splinter in dag°] -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org