no python on fedora 29 copr
one of my src rpm submitted to copr for build failed because there is no python; is this because something is wrong with the src rpm itself, or there is simply no python on copr machines, or I missed some settings?
checking for perl... /usr/bin/perl
checking for python... no
BUILDSTDERR: configure: error: You need 'python' to compile XXX
fedora rpmbuild
add a comment |
one of my src rpm submitted to copr for build failed because there is no python; is this because something is wrong with the src rpm itself, or there is simply no python on copr machines, or I missed some settings?
checking for perl... /usr/bin/perl
checking for python... no
BUILDSTDERR: configure: error: You need 'python' to compile XXX
fedora rpmbuild
add a comment |
one of my src rpm submitted to copr for build failed because there is no python; is this because something is wrong with the src rpm itself, or there is simply no python on copr machines, or I missed some settings?
checking for perl... /usr/bin/perl
checking for python... no
BUILDSTDERR: configure: error: You need 'python' to compile XXX
fedora rpmbuild
one of my src rpm submitted to copr for build failed because there is no python; is this because something is wrong with the src rpm itself, or there is simply no python on copr machines, or I missed some settings?
checking for perl... /usr/bin/perl
checking for python... no
BUILDSTDERR: configure: error: You need 'python' to compile XXX
fedora rpmbuild
fedora rpmbuild
edited 22 hours ago
peterh
4,32592957
4,32592957
asked yesterday
CykerCyker
1,42821531
1,42821531
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
It's very likely that you are missing one or more of:
BuildRequires: python2-devel
BuildRequires: python3-devel
BuildRequires: python-unversioned-command
in your spec file. The build environment starts out rather minimal and BuildRequires are used to pull in additional things. Python is rather large, so there was effort to move it from the default buildroot a little while ago.
See Dependencies in the Python section of the Fedora Packaging Guidelines.
If your program refers to /usr/bin/python without a version number, you'll need python-unversion-command. See this Fedora change for detail on that — in short, upstream Python has decided that /usr/bin/python can refer to either version depending on what the user wants, which means that operating system packages should really use either python2 or python3 explicitly. Requiring the unversioned command is an option for when you don't want to patch your program to do that for whatever reason.
hello, i added that line in spec, but configure still fails; same error (no python); it's the webkitgtk source rpm pulled from fedora 26 (because it was removed since fedora 27);
– Cyker
yesterday
Possible that that requires Python 2?
– mattdm
yesterday
it seems on fedora 29/usr/bin/pythonis installed by packagepython-unversioned-command, neitherpython2norpython3; does this matter? source
– Cyker
yesterday
looks like problem goes away when i addedBuildRequires: python-unversioned-commandin addition to the other twoBuildRequires; now it passed configure and started make; thank you very much;
– Cyker
yesterday
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f494139%2fno-python-on-fedora-29-copr%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
It's very likely that you are missing one or more of:
BuildRequires: python2-devel
BuildRequires: python3-devel
BuildRequires: python-unversioned-command
in your spec file. The build environment starts out rather minimal and BuildRequires are used to pull in additional things. Python is rather large, so there was effort to move it from the default buildroot a little while ago.
See Dependencies in the Python section of the Fedora Packaging Guidelines.
If your program refers to /usr/bin/python without a version number, you'll need python-unversion-command. See this Fedora change for detail on that — in short, upstream Python has decided that /usr/bin/python can refer to either version depending on what the user wants, which means that operating system packages should really use either python2 or python3 explicitly. Requiring the unversioned command is an option for when you don't want to patch your program to do that for whatever reason.
hello, i added that line in spec, but configure still fails; same error (no python); it's the webkitgtk source rpm pulled from fedora 26 (because it was removed since fedora 27);
– Cyker
yesterday
Possible that that requires Python 2?
– mattdm
yesterday
it seems on fedora 29/usr/bin/pythonis installed by packagepython-unversioned-command, neitherpython2norpython3; does this matter? source
– Cyker
yesterday
looks like problem goes away when i addedBuildRequires: python-unversioned-commandin addition to the other twoBuildRequires; now it passed configure and started make; thank you very much;
– Cyker
yesterday
add a comment |
It's very likely that you are missing one or more of:
BuildRequires: python2-devel
BuildRequires: python3-devel
BuildRequires: python-unversioned-command
in your spec file. The build environment starts out rather minimal and BuildRequires are used to pull in additional things. Python is rather large, so there was effort to move it from the default buildroot a little while ago.
See Dependencies in the Python section of the Fedora Packaging Guidelines.
If your program refers to /usr/bin/python without a version number, you'll need python-unversion-command. See this Fedora change for detail on that — in short, upstream Python has decided that /usr/bin/python can refer to either version depending on what the user wants, which means that operating system packages should really use either python2 or python3 explicitly. Requiring the unversioned command is an option for when you don't want to patch your program to do that for whatever reason.
hello, i added that line in spec, but configure still fails; same error (no python); it's the webkitgtk source rpm pulled from fedora 26 (because it was removed since fedora 27);
– Cyker
yesterday
Possible that that requires Python 2?
– mattdm
yesterday
it seems on fedora 29/usr/bin/pythonis installed by packagepython-unversioned-command, neitherpython2norpython3; does this matter? source
– Cyker
yesterday
looks like problem goes away when i addedBuildRequires: python-unversioned-commandin addition to the other twoBuildRequires; now it passed configure and started make; thank you very much;
– Cyker
yesterday
add a comment |
It's very likely that you are missing one or more of:
BuildRequires: python2-devel
BuildRequires: python3-devel
BuildRequires: python-unversioned-command
in your spec file. The build environment starts out rather minimal and BuildRequires are used to pull in additional things. Python is rather large, so there was effort to move it from the default buildroot a little while ago.
See Dependencies in the Python section of the Fedora Packaging Guidelines.
If your program refers to /usr/bin/python without a version number, you'll need python-unversion-command. See this Fedora change for detail on that — in short, upstream Python has decided that /usr/bin/python can refer to either version depending on what the user wants, which means that operating system packages should really use either python2 or python3 explicitly. Requiring the unversioned command is an option for when you don't want to patch your program to do that for whatever reason.
It's very likely that you are missing one or more of:
BuildRequires: python2-devel
BuildRequires: python3-devel
BuildRequires: python-unversioned-command
in your spec file. The build environment starts out rather minimal and BuildRequires are used to pull in additional things. Python is rather large, so there was effort to move it from the default buildroot a little while ago.
See Dependencies in the Python section of the Fedora Packaging Guidelines.
If your program refers to /usr/bin/python without a version number, you'll need python-unversion-command. See this Fedora change for detail on that — in short, upstream Python has decided that /usr/bin/python can refer to either version depending on what the user wants, which means that operating system packages should really use either python2 or python3 explicitly. Requiring the unversioned command is an option for when you don't want to patch your program to do that for whatever reason.
edited yesterday
answered yesterday
mattdmmattdm
28.4k1172112
28.4k1172112
hello, i added that line in spec, but configure still fails; same error (no python); it's the webkitgtk source rpm pulled from fedora 26 (because it was removed since fedora 27);
– Cyker
yesterday
Possible that that requires Python 2?
– mattdm
yesterday
it seems on fedora 29/usr/bin/pythonis installed by packagepython-unversioned-command, neitherpython2norpython3; does this matter? source
– Cyker
yesterday
looks like problem goes away when i addedBuildRequires: python-unversioned-commandin addition to the other twoBuildRequires; now it passed configure and started make; thank you very much;
– Cyker
yesterday
add a comment |
hello, i added that line in spec, but configure still fails; same error (no python); it's the webkitgtk source rpm pulled from fedora 26 (because it was removed since fedora 27);
– Cyker
yesterday
Possible that that requires Python 2?
– mattdm
yesterday
it seems on fedora 29/usr/bin/pythonis installed by packagepython-unversioned-command, neitherpython2norpython3; does this matter? source
– Cyker
yesterday
looks like problem goes away when i addedBuildRequires: python-unversioned-commandin addition to the other twoBuildRequires; now it passed configure and started make; thank you very much;
– Cyker
yesterday
hello, i added that line in spec, but configure still fails; same error (no python); it's the webkitgtk source rpm pulled from fedora 26 (because it was removed since fedora 27);
– Cyker
yesterday
hello, i added that line in spec, but configure still fails; same error (no python); it's the webkitgtk source rpm pulled from fedora 26 (because it was removed since fedora 27);
– Cyker
yesterday
Possible that that requires Python 2?
– mattdm
yesterday
Possible that that requires Python 2?
– mattdm
yesterday
it seems on fedora 29
/usr/bin/python is installed by package python-unversioned-command, neither python2 nor python3; does this matter? source– Cyker
yesterday
it seems on fedora 29
/usr/bin/python is installed by package python-unversioned-command, neither python2 nor python3; does this matter? source– Cyker
yesterday
looks like problem goes away when i added
BuildRequires: python-unversioned-command in addition to the other two BuildRequires; now it passed configure and started make; thank you very much;– Cyker
yesterday
looks like problem goes away when i added
BuildRequires: python-unversioned-command in addition to the other two BuildRequires; now it passed configure and started make; thank you very much;– Cyker
yesterday
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f494139%2fno-python-on-fedora-29-copr%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown