[opensuse-packaging] rpmlint: sh: /usr/bin/python: No such file or directory
I see quite often when building (check e.g. osc remotebuildlog home:a_jaeger:branches:openSUSE:Factory haveged Factory_snapshot i586) the following: RPMLINT report: =============== sh: /usr/bin/python: No such file or directory but this is followed by normal rpmlint output. Python really does not seem to be installed in the chroot. Any ideas what's going on here? Andreas -- Andreas Jaeger, Program Manager openSUSE, aj@{novell.com,opensuse.org} Twitter: jaegerandi | Identica: jaegerandi SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
On Monday 08 November 2010 14:09:13 Andreas Jaeger wrote:
I see quite often when building (check e.g. osc remotebuildlog home:a_jaeger:branches:openSUSE:Factory haveged Factory_snapshot i586) the following:
RPMLINT report: =============== sh: /usr/bin/python: No such file or directory
but this is followed by normal rpmlint output. Python really does not seem to be installed in the chroot.
Any ideas what's going on here?
I just found the following, is this the culprit? aj@byrd:/abuild/osc/buildroot_x86_64/opt/testing> grep -r /usr/bin/python * share/rpmlint/rpmlint-mini.config:#!/usr/bin/python Andreas -- Andreas Jaeger, Program Manager openSUSE, aj@{novell.com,opensuse.org} Twitter: jaegerandi | Identica: jaegerandi SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
El 08/11/10 10:09, Andreas Jaeger escribió:
I see quite often when building (check e.g. osc remotebuildlog home:a_jaeger:branches:openSUSE:Factory haveged Factory_snapshot i586) the following:
RPMLINT report: =============== sh: /usr/bin/python: No such file or directory
but this is followed by normal rpmlint output. Python really does not seem to be installed in the chroot.
Any ideas what's going on here?
Seeing it here as well, since a lot of time, no idea what's behind it though. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
On 11/08/2010 02:17 PM, Cristian Rodríguez wrote:
El 08/11/10 10:09, Andreas Jaeger escribió:
I see quite often when building (check e.g. osc remotebuildlog home:a_jaeger:branches:openSUSE:Factory haveged Factory_snapshot i586) the following:
RPMLINT report: =============== sh: /usr/bin/python: No such file or directory
but this is followed by normal rpmlint output. Python really does not seem to be installed in the chroot.
Any ideas what's going on here?
Seeing it here as well, since a lot of time, no idea what's behind it though. shell magic.
Calling a script directly will start the interpreter specified in the '#!' line. Calling it with 'sh <script>' will fail to do so. So it looks as if someone calls 'rpmlint' with sh rpmlint should work if the 'sh' is removed. Cheers, Hannes -- Dr. Hannes Reinecke zSeries & Storage hare@suse.de +49 911 74053 688 SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg GF: Markus Rex, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
On Monday 08 November 2010 14:12:04 Andreas Jaeger wrote:
On Monday 08 November 2010 14:09:13 Andreas Jaeger wrote:
I see quite often when building (check e.g. osc remotebuildlog home:a_jaeger:branches:openSUSE:Factory haveged Factory_snapshot i586) the following:
RPMLINT report: =============== sh: /usr/bin/python: No such file or directory
but this is followed by normal rpmlint output. Python really does not seem to be installed in the chroot.
Any ideas what's going on here?
I just found the following, is this the culprit?
aj@byrd:/abuild/osc/buildroot_x86_64/opt/testing> grep -r /usr/bin/python * share/rpmlint/rpmlint-mini.config:#!/usr/bin/python
This does not fix it ;-( Andreas -- Andreas Jaeger, Program Manager openSUSE, aj@{novell.com,opensuse.org} Twitter: jaegerandi | Identica: jaegerandi SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
On Monday 08 November 2010 14:30:07 Hannes Reinecke wrote:
On 11/08/2010 02:17 PM, Cristian Rodríguez wrote:
El 08/11/10 10:09, Andreas Jaeger escribió:
I see quite often when building (check e.g. osc remotebuildlog home:a_jaeger:branches:openSUSE:Factory haveged Factory_snapshot i586) the following:
RPMLINT report: =============== sh: /usr/bin/python: No such file or directory
but this is followed by normal rpmlint output. Python really does not seem to be installed in the chroot.
Any ideas what's going on here?
Seeing it here as well, since a lot of time, no idea what's behind it though.
shell magic.
Calling a script directly will start the interpreter specified in the '#!' line.
Calling it with 'sh <script>' will fail to do so. So it looks as if someone calls 'rpmlint' with
sh rpmlint
should work if the 'sh' is removed.
It's something called by rpmlint, as rpmlint is run correctly... Andreas -- Andreas Jaeger, Program Manager openSUSE, aj@{novell.com,opensuse.org} Twitter: jaegerandi | Identica: jaegerandi SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
On Monday 08 November 2010, Andreas Jaeger wrote:
It's something called by rpmlint, as rpmlint is run correctly...
Did you file a bugreport at https://bugzilla.novell.com? Thanks, Dirk -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
On Sunday 14 November 2010, Dirk Müller wrote:
It's something called by rpmlint, as rpmlint is run correctly... Did you file a bugreport at https://bugzilla.novell.com?
debugging it, it is actually a fault in the rpm package. $ fgrep "%(" /usr/lib/rpm/macros | grep python %python_sitelib %(%{__python} -c "from distutils.sysconfig import get_python_lib; import sys; sys.stdout.write(get_python_lib())") running rpm.expandMacro() causes parsing of the global macros file, which causes a bunch of shell scripts being invoked, including one that tries to run /usr/bin/python,which does not exist. To me it looks quite stupid to invoke that many shell scripts or define macros for something that is optional. IMHO those paths should be hardcoded instead of runtime-defined, or the runtime-definition should be provided by /etc/rpm/macros.python But anyway, for now, I can workaround this issue by not invoking expandMacro() (it is only used for minor rpmlint checks which I just removed in our package). So the issue at hand is resolved, albeit with an ugly hack. Greetings, Dirk -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
participants (4)
-
Andreas Jaeger -
Cristian Rodríguez -
Dirk Müller -
Hannes Reinecke