Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

build-specs.sh fails if there is no python #4

Open
Habbie opened this issue Nov 30, 2017 · 3 comments
Open

build-specs.sh fails if there is no python #4

Habbie opened this issue Nov 30, 2017 · 3 comments

Comments

@Habbie
Copy link
Member

Habbie commented Nov 30, 2017

If the Dockerfile does not have yum install -y python-rpm-macros python-srpm-macros python3-rpm-macros python34, then:

Step 30/31 : RUN builder/helpers/build-specs.sh builder-support/specs/xxx.spec
 ---> Running in d844335a3e0c
/usr/bin/env: python3: No such file or directory
+ '[' '!' -z '' ']'

it then continues to be very useless. Perhaps build-specs.sh should install these RPMs if it needs them?

@wojas
Copy link
Member

wojas commented Nov 30, 2017

That's indeed a bug, the build step MUST fail if python3 is not available.

Trying to install it from the build scripts would not be very consistent, as we do not do that for other things we require for building. If we would correctly fail at that point, it would be clear what is missing. Installing it automatically would make the build slower, as it will not be cached in an earlier layer and reinstalled every time the thing you are building changes.

Are you sure the python rpm macros are needed? They should only be needed if you are building python rpm packages, in which case they should be listed as some kind of Requires in the specs. Am I right here @pieterlexis?

@Habbie
Copy link
Member Author

Habbie commented Nov 30, 2017

Are you sure the python rpm macros are needed?

No - I just copied that whole line from another project and then things worked :)

@Habbie
Copy link
Member Author

Habbie commented Nov 30, 2017

That's indeed a bug, the build step MUST fail if python3 is not available.

Note that it does fail eventually, because the deps the spec requires are not installed and hence the actual build fails.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants