“curl : Depends: libcurl4 (= 7.61.0-1ubuntu2.2) but it is not going to be installed” on Ubuntu 18.10 with...
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
I am struggling with installing cURL module in Ubuntu 18.10. While upgrading from 17.10 to 18.10 cURL was removed/deleted. Now when I try to execute the command
sudo apt-get install php7.2-curl
I get this error:
The following packages have unmet dependencies:
php7.2-curl :
Depends: libcurl4 (>= 7.44.0) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
sudo apt-get install curl
gives the error
The following packages have unmet dependencies:
curl : Depends: libcurl4 (= 7.61.0-1ubuntu2.2) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.




apt package-management curl php7
|
show 1 more comment
I am struggling with installing cURL module in Ubuntu 18.10. While upgrading from 17.10 to 18.10 cURL was removed/deleted. Now when I try to execute the command
sudo apt-get install php7.2-curl
I get this error:
The following packages have unmet dependencies:
php7.2-curl :
Depends: libcurl4 (>= 7.44.0) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
sudo apt-get install curl
gives the error
The following packages have unmet dependencies:
curl : Depends: libcurl4 (= 7.61.0-1ubuntu2.2) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.




apt package-management curl php7
1
There is no supported upgrade path directly from 17.10 to 18.10. Please edit your question to include 1) a clear and complete explanation of how you upgraded, 2) the complete contents of /etc/apt/sources.list and 3) the complete output ofapt-cache policyfor bothphp7.20curlandcurl
– user535733
Dec 8 '18 at 13:00
Please ensure that you have enabled all software repositories (especially -updates and -security) then runsudo apt updateandsudo apt dist-upgrade(to get new dependencies). Also add output ofapt-cache policy php7.2-curl curl libcurl4to the question.
– N0rbert
Dec 8 '18 at 13:05
@user535733 and N0rbert I have edited the question hope this will be helpful
– Mustafa Taheri
Dec 8 '18 at 14:44
Muistafa, try the duplicates first and keep the results. If none of the duplicates work, edit in the results from the steps you took over there. And please? Don't post screenshots, but copy-paste the text of terminal output so we can just copy-paste it as well...
– Fabby
Dec 14 '18 at 8:23
Apologies for inconvenience @Fabby but none of the above duplicate answer worked for me. I have followed the instructions given by user535733 and that solved my problem.
– Mustafa Taheri
Dec 15 '18 at 12:03
|
show 1 more comment
I am struggling with installing cURL module in Ubuntu 18.10. While upgrading from 17.10 to 18.10 cURL was removed/deleted. Now when I try to execute the command
sudo apt-get install php7.2-curl
I get this error:
The following packages have unmet dependencies:
php7.2-curl :
Depends: libcurl4 (>= 7.44.0) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
sudo apt-get install curl
gives the error
The following packages have unmet dependencies:
curl : Depends: libcurl4 (= 7.61.0-1ubuntu2.2) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.




apt package-management curl php7
I am struggling with installing cURL module in Ubuntu 18.10. While upgrading from 17.10 to 18.10 cURL was removed/deleted. Now when I try to execute the command
sudo apt-get install php7.2-curl
I get this error:
The following packages have unmet dependencies:
php7.2-curl :
Depends: libcurl4 (>= 7.44.0) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
sudo apt-get install curl
gives the error
The following packages have unmet dependencies:
curl : Depends: libcurl4 (= 7.61.0-1ubuntu2.2) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.




apt package-management curl php7
apt package-management curl php7
edited Dec 15 '18 at 16:54
Zanna
51.4k13140243
51.4k13140243
asked Dec 8 '18 at 11:18
Mustafa TaheriMustafa Taheri
203
203
1
There is no supported upgrade path directly from 17.10 to 18.10. Please edit your question to include 1) a clear and complete explanation of how you upgraded, 2) the complete contents of /etc/apt/sources.list and 3) the complete output ofapt-cache policyfor bothphp7.20curlandcurl
– user535733
Dec 8 '18 at 13:00
Please ensure that you have enabled all software repositories (especially -updates and -security) then runsudo apt updateandsudo apt dist-upgrade(to get new dependencies). Also add output ofapt-cache policy php7.2-curl curl libcurl4to the question.
– N0rbert
Dec 8 '18 at 13:05
@user535733 and N0rbert I have edited the question hope this will be helpful
– Mustafa Taheri
Dec 8 '18 at 14:44
Muistafa, try the duplicates first and keep the results. If none of the duplicates work, edit in the results from the steps you took over there. And please? Don't post screenshots, but copy-paste the text of terminal output so we can just copy-paste it as well...
– Fabby
Dec 14 '18 at 8:23
Apologies for inconvenience @Fabby but none of the above duplicate answer worked for me. I have followed the instructions given by user535733 and that solved my problem.
– Mustafa Taheri
Dec 15 '18 at 12:03
|
show 1 more comment
1
There is no supported upgrade path directly from 17.10 to 18.10. Please edit your question to include 1) a clear and complete explanation of how you upgraded, 2) the complete contents of /etc/apt/sources.list and 3) the complete output ofapt-cache policyfor bothphp7.20curlandcurl
– user535733
Dec 8 '18 at 13:00
Please ensure that you have enabled all software repositories (especially -updates and -security) then runsudo apt updateandsudo apt dist-upgrade(to get new dependencies). Also add output ofapt-cache policy php7.2-curl curl libcurl4to the question.
– N0rbert
Dec 8 '18 at 13:05
@user535733 and N0rbert I have edited the question hope this will be helpful
– Mustafa Taheri
Dec 8 '18 at 14:44
Muistafa, try the duplicates first and keep the results. If none of the duplicates work, edit in the results from the steps you took over there. And please? Don't post screenshots, but copy-paste the text of terminal output so we can just copy-paste it as well...
– Fabby
Dec 14 '18 at 8:23
Apologies for inconvenience @Fabby but none of the above duplicate answer worked for me. I have followed the instructions given by user535733 and that solved my problem.
– Mustafa Taheri
Dec 15 '18 at 12:03
1
1
There is no supported upgrade path directly from 17.10 to 18.10. Please edit your question to include 1) a clear and complete explanation of how you upgraded, 2) the complete contents of /etc/apt/sources.list and 3) the complete output of
apt-cache policy for both php7.20curl and curl– user535733
Dec 8 '18 at 13:00
There is no supported upgrade path directly from 17.10 to 18.10. Please edit your question to include 1) a clear and complete explanation of how you upgraded, 2) the complete contents of /etc/apt/sources.list and 3) the complete output of
apt-cache policy for both php7.20curl and curl– user535733
Dec 8 '18 at 13:00
Please ensure that you have enabled all software repositories (especially -updates and -security) then run
sudo apt update and sudo apt dist-upgrade (to get new dependencies). Also add output of apt-cache policy php7.2-curl curl libcurl4 to the question.– N0rbert
Dec 8 '18 at 13:05
Please ensure that you have enabled all software repositories (especially -updates and -security) then run
sudo apt update and sudo apt dist-upgrade (to get new dependencies). Also add output of apt-cache policy php7.2-curl curl libcurl4 to the question.– N0rbert
Dec 8 '18 at 13:05
@user535733 and N0rbert I have edited the question hope this will be helpful
– Mustafa Taheri
Dec 8 '18 at 14:44
@user535733 and N0rbert I have edited the question hope this will be helpful
– Mustafa Taheri
Dec 8 '18 at 14:44
Muistafa, try the duplicates first and keep the results. If none of the duplicates work, edit in the results from the steps you took over there. And please? Don't post screenshots, but copy-paste the text of terminal output so we can just copy-paste it as well...
– Fabby
Dec 14 '18 at 8:23
Muistafa, try the duplicates first and keep the results. If none of the duplicates work, edit in the results from the steps you took over there. And please? Don't post screenshots, but copy-paste the text of terminal output so we can just copy-paste it as well...
– Fabby
Dec 14 '18 at 8:23
Apologies for inconvenience @Fabby but none of the above duplicate answer worked for me. I have followed the instructions given by user535733 and that solved my problem.
– Mustafa Taheri
Dec 15 '18 at 12:03
Apologies for inconvenience @Fabby but none of the above duplicate answer worked for me. I have followed the instructions given by user535733 and that solved my problem.
– Mustafa Taheri
Dec 15 '18 at 12:03
|
show 1 more comment
2 Answers
2
active
oldest
votes
The problem: Seems like you upgraded some non-standard, unsupported way...looks like you used the Debian dist-upgrade method...which (unsurprisingly) made a big mess. Always use do-release-upgrade for Ubuntu systems. While closely based on Debian, Ubuntu is not Debian.
When preparing your non-standard upgrade, you made mistakes:
- You failed to disable a 17.10 repository.
- You failed to uninstall non-Ubuntu software, and did not disable those PPAs.
Now you are stuck with a mixture of wrong-version packages which are (understandably) blocking apt. We would usually call this a partial or incomplete upgrade. All this information is from the output you provided.
The solution: You have two options:
Clean up the mess.
- Uninstall all PPA and other non-Ubuntu software, and disable the sources they came from.
- Disable the 17.10 repo.
- Then run an apt update and dist-upgrade to get you as close to stock 18.10 as possible.
- Then, one by one, start adding back non-Ubuntu sources and software.
If you don't know how to do #1, then preserve your data and do a clean-install of 18.10.
can you please suggest how can this be fixed by 1st option as I can't install fresh 18.10. Please tell me the sequence of commands so that I can clear this mess.
– Mustafa Taheri
Dec 10 '18 at 7:17
If you cannot clean-install 18.10, the you must keep your system packages clean, release-upgrade on schedule, and other basic maintenance. Bad news, sorry - there is no single set of magic incantations to solve your problem: You must learn the skills required to do each step, including reading your output and understanding how the package manager works. AskUbuntu's format is poorly suited to this kind of learning - I suggest opening a thread in our sibling site ubuntuforums.org, where you can have days or weeks of interactive hand-holding with experts while you learn.
– user535733
Dec 10 '18 at 9:41
hey, @user535733 just need some of your help I have removed all the repo which include 17.10 and bionic in there title as they are not of 18.10 but there are still some of them and I am unable to judge whether to remove them or not. Adding the image in Que to refer with name Other Software List.
– Mustafa Taheri
Dec 14 '18 at 7:34
Re-read the answer above. The relevant instruction is clear.
– user535733
Dec 14 '18 at 12:55
I have solved that by your instruction. thanx, a lot brother @user535733. You have saved me...
– Mustafa Taheri
Dec 15 '18 at 12:01
|
show 1 more comment
SIMPLE SOLUTION: (worked for me)
sudo apt remove libcurl4
sudo apt install curl
New contributor
kaiz3n is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
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: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
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%2faskubuntu.com%2fquestions%2f1099366%2fcurl-depends-libcurl4-7-61-0-1ubuntu2-2-but-it-is-not-going-to-be-instal%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
The problem: Seems like you upgraded some non-standard, unsupported way...looks like you used the Debian dist-upgrade method...which (unsurprisingly) made a big mess. Always use do-release-upgrade for Ubuntu systems. While closely based on Debian, Ubuntu is not Debian.
When preparing your non-standard upgrade, you made mistakes:
- You failed to disable a 17.10 repository.
- You failed to uninstall non-Ubuntu software, and did not disable those PPAs.
Now you are stuck with a mixture of wrong-version packages which are (understandably) blocking apt. We would usually call this a partial or incomplete upgrade. All this information is from the output you provided.
The solution: You have two options:
Clean up the mess.
- Uninstall all PPA and other non-Ubuntu software, and disable the sources they came from.
- Disable the 17.10 repo.
- Then run an apt update and dist-upgrade to get you as close to stock 18.10 as possible.
- Then, one by one, start adding back non-Ubuntu sources and software.
If you don't know how to do #1, then preserve your data and do a clean-install of 18.10.
can you please suggest how can this be fixed by 1st option as I can't install fresh 18.10. Please tell me the sequence of commands so that I can clear this mess.
– Mustafa Taheri
Dec 10 '18 at 7:17
If you cannot clean-install 18.10, the you must keep your system packages clean, release-upgrade on schedule, and other basic maintenance. Bad news, sorry - there is no single set of magic incantations to solve your problem: You must learn the skills required to do each step, including reading your output and understanding how the package manager works. AskUbuntu's format is poorly suited to this kind of learning - I suggest opening a thread in our sibling site ubuntuforums.org, where you can have days or weeks of interactive hand-holding with experts while you learn.
– user535733
Dec 10 '18 at 9:41
hey, @user535733 just need some of your help I have removed all the repo which include 17.10 and bionic in there title as they are not of 18.10 but there are still some of them and I am unable to judge whether to remove them or not. Adding the image in Que to refer with name Other Software List.
– Mustafa Taheri
Dec 14 '18 at 7:34
Re-read the answer above. The relevant instruction is clear.
– user535733
Dec 14 '18 at 12:55
I have solved that by your instruction. thanx, a lot brother @user535733. You have saved me...
– Mustafa Taheri
Dec 15 '18 at 12:01
|
show 1 more comment
The problem: Seems like you upgraded some non-standard, unsupported way...looks like you used the Debian dist-upgrade method...which (unsurprisingly) made a big mess. Always use do-release-upgrade for Ubuntu systems. While closely based on Debian, Ubuntu is not Debian.
When preparing your non-standard upgrade, you made mistakes:
- You failed to disable a 17.10 repository.
- You failed to uninstall non-Ubuntu software, and did not disable those PPAs.
Now you are stuck with a mixture of wrong-version packages which are (understandably) blocking apt. We would usually call this a partial or incomplete upgrade. All this information is from the output you provided.
The solution: You have two options:
Clean up the mess.
- Uninstall all PPA and other non-Ubuntu software, and disable the sources they came from.
- Disable the 17.10 repo.
- Then run an apt update and dist-upgrade to get you as close to stock 18.10 as possible.
- Then, one by one, start adding back non-Ubuntu sources and software.
If you don't know how to do #1, then preserve your data and do a clean-install of 18.10.
can you please suggest how can this be fixed by 1st option as I can't install fresh 18.10. Please tell me the sequence of commands so that I can clear this mess.
– Mustafa Taheri
Dec 10 '18 at 7:17
If you cannot clean-install 18.10, the you must keep your system packages clean, release-upgrade on schedule, and other basic maintenance. Bad news, sorry - there is no single set of magic incantations to solve your problem: You must learn the skills required to do each step, including reading your output and understanding how the package manager works. AskUbuntu's format is poorly suited to this kind of learning - I suggest opening a thread in our sibling site ubuntuforums.org, where you can have days or weeks of interactive hand-holding with experts while you learn.
– user535733
Dec 10 '18 at 9:41
hey, @user535733 just need some of your help I have removed all the repo which include 17.10 and bionic in there title as they are not of 18.10 but there are still some of them and I am unable to judge whether to remove them or not. Adding the image in Que to refer with name Other Software List.
– Mustafa Taheri
Dec 14 '18 at 7:34
Re-read the answer above. The relevant instruction is clear.
– user535733
Dec 14 '18 at 12:55
I have solved that by your instruction. thanx, a lot brother @user535733. You have saved me...
– Mustafa Taheri
Dec 15 '18 at 12:01
|
show 1 more comment
The problem: Seems like you upgraded some non-standard, unsupported way...looks like you used the Debian dist-upgrade method...which (unsurprisingly) made a big mess. Always use do-release-upgrade for Ubuntu systems. While closely based on Debian, Ubuntu is not Debian.
When preparing your non-standard upgrade, you made mistakes:
- You failed to disable a 17.10 repository.
- You failed to uninstall non-Ubuntu software, and did not disable those PPAs.
Now you are stuck with a mixture of wrong-version packages which are (understandably) blocking apt. We would usually call this a partial or incomplete upgrade. All this information is from the output you provided.
The solution: You have two options:
Clean up the mess.
- Uninstall all PPA and other non-Ubuntu software, and disable the sources they came from.
- Disable the 17.10 repo.
- Then run an apt update and dist-upgrade to get you as close to stock 18.10 as possible.
- Then, one by one, start adding back non-Ubuntu sources and software.
If you don't know how to do #1, then preserve your data and do a clean-install of 18.10.
The problem: Seems like you upgraded some non-standard, unsupported way...looks like you used the Debian dist-upgrade method...which (unsurprisingly) made a big mess. Always use do-release-upgrade for Ubuntu systems. While closely based on Debian, Ubuntu is not Debian.
When preparing your non-standard upgrade, you made mistakes:
- You failed to disable a 17.10 repository.
- You failed to uninstall non-Ubuntu software, and did not disable those PPAs.
Now you are stuck with a mixture of wrong-version packages which are (understandably) blocking apt. We would usually call this a partial or incomplete upgrade. All this information is from the output you provided.
The solution: You have two options:
Clean up the mess.
- Uninstall all PPA and other non-Ubuntu software, and disable the sources they came from.
- Disable the 17.10 repo.
- Then run an apt update and dist-upgrade to get you as close to stock 18.10 as possible.
- Then, one by one, start adding back non-Ubuntu sources and software.
If you don't know how to do #1, then preserve your data and do a clean-install of 18.10.
edited Dec 8 '18 at 15:07
answered Dec 8 '18 at 15:00
user535733user535733
8,97623044
8,97623044
can you please suggest how can this be fixed by 1st option as I can't install fresh 18.10. Please tell me the sequence of commands so that I can clear this mess.
– Mustafa Taheri
Dec 10 '18 at 7:17
If you cannot clean-install 18.10, the you must keep your system packages clean, release-upgrade on schedule, and other basic maintenance. Bad news, sorry - there is no single set of magic incantations to solve your problem: You must learn the skills required to do each step, including reading your output and understanding how the package manager works. AskUbuntu's format is poorly suited to this kind of learning - I suggest opening a thread in our sibling site ubuntuforums.org, where you can have days or weeks of interactive hand-holding with experts while you learn.
– user535733
Dec 10 '18 at 9:41
hey, @user535733 just need some of your help I have removed all the repo which include 17.10 and bionic in there title as they are not of 18.10 but there are still some of them and I am unable to judge whether to remove them or not. Adding the image in Que to refer with name Other Software List.
– Mustafa Taheri
Dec 14 '18 at 7:34
Re-read the answer above. The relevant instruction is clear.
– user535733
Dec 14 '18 at 12:55
I have solved that by your instruction. thanx, a lot brother @user535733. You have saved me...
– Mustafa Taheri
Dec 15 '18 at 12:01
|
show 1 more comment
can you please suggest how can this be fixed by 1st option as I can't install fresh 18.10. Please tell me the sequence of commands so that I can clear this mess.
– Mustafa Taheri
Dec 10 '18 at 7:17
If you cannot clean-install 18.10, the you must keep your system packages clean, release-upgrade on schedule, and other basic maintenance. Bad news, sorry - there is no single set of magic incantations to solve your problem: You must learn the skills required to do each step, including reading your output and understanding how the package manager works. AskUbuntu's format is poorly suited to this kind of learning - I suggest opening a thread in our sibling site ubuntuforums.org, where you can have days or weeks of interactive hand-holding with experts while you learn.
– user535733
Dec 10 '18 at 9:41
hey, @user535733 just need some of your help I have removed all the repo which include 17.10 and bionic in there title as they are not of 18.10 but there are still some of them and I am unable to judge whether to remove them or not. Adding the image in Que to refer with name Other Software List.
– Mustafa Taheri
Dec 14 '18 at 7:34
Re-read the answer above. The relevant instruction is clear.
– user535733
Dec 14 '18 at 12:55
I have solved that by your instruction. thanx, a lot brother @user535733. You have saved me...
– Mustafa Taheri
Dec 15 '18 at 12:01
can you please suggest how can this be fixed by 1st option as I can't install fresh 18.10. Please tell me the sequence of commands so that I can clear this mess.
– Mustafa Taheri
Dec 10 '18 at 7:17
can you please suggest how can this be fixed by 1st option as I can't install fresh 18.10. Please tell me the sequence of commands so that I can clear this mess.
– Mustafa Taheri
Dec 10 '18 at 7:17
If you cannot clean-install 18.10, the you must keep your system packages clean, release-upgrade on schedule, and other basic maintenance. Bad news, sorry - there is no single set of magic incantations to solve your problem: You must learn the skills required to do each step, including reading your output and understanding how the package manager works. AskUbuntu's format is poorly suited to this kind of learning - I suggest opening a thread in our sibling site ubuntuforums.org, where you can have days or weeks of interactive hand-holding with experts while you learn.
– user535733
Dec 10 '18 at 9:41
If you cannot clean-install 18.10, the you must keep your system packages clean, release-upgrade on schedule, and other basic maintenance. Bad news, sorry - there is no single set of magic incantations to solve your problem: You must learn the skills required to do each step, including reading your output and understanding how the package manager works. AskUbuntu's format is poorly suited to this kind of learning - I suggest opening a thread in our sibling site ubuntuforums.org, where you can have days or weeks of interactive hand-holding with experts while you learn.
– user535733
Dec 10 '18 at 9:41
hey, @user535733 just need some of your help I have removed all the repo which include 17.10 and bionic in there title as they are not of 18.10 but there are still some of them and I am unable to judge whether to remove them or not. Adding the image in Que to refer with name Other Software List.
– Mustafa Taheri
Dec 14 '18 at 7:34
hey, @user535733 just need some of your help I have removed all the repo which include 17.10 and bionic in there title as they are not of 18.10 but there are still some of them and I am unable to judge whether to remove them or not. Adding the image in Que to refer with name Other Software List.
– Mustafa Taheri
Dec 14 '18 at 7:34
Re-read the answer above. The relevant instruction is clear.
– user535733
Dec 14 '18 at 12:55
Re-read the answer above. The relevant instruction is clear.
– user535733
Dec 14 '18 at 12:55
I have solved that by your instruction. thanx, a lot brother @user535733. You have saved me...
– Mustafa Taheri
Dec 15 '18 at 12:01
I have solved that by your instruction. thanx, a lot brother @user535733. You have saved me...
– Mustafa Taheri
Dec 15 '18 at 12:01
|
show 1 more comment
SIMPLE SOLUTION: (worked for me)
sudo apt remove libcurl4
sudo apt install curl
New contributor
kaiz3n is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
SIMPLE SOLUTION: (worked for me)
sudo apt remove libcurl4
sudo apt install curl
New contributor
kaiz3n is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
SIMPLE SOLUTION: (worked for me)
sudo apt remove libcurl4
sudo apt install curl
New contributor
kaiz3n is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
SIMPLE SOLUTION: (worked for me)
sudo apt remove libcurl4
sudo apt install curl
New contributor
kaiz3n is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
edited 3 hours ago
Philippe Delteil
6561522
6561522
New contributor
kaiz3n is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered 9 hours ago
kaiz3nkaiz3n
12
12
New contributor
kaiz3n is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
kaiz3n is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
kaiz3n is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- 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%2faskubuntu.com%2fquestions%2f1099366%2fcurl-depends-libcurl4-7-61-0-1ubuntu2-2-but-it-is-not-going-to-be-instal%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
1
There is no supported upgrade path directly from 17.10 to 18.10. Please edit your question to include 1) a clear and complete explanation of how you upgraded, 2) the complete contents of /etc/apt/sources.list and 3) the complete output of
apt-cache policyfor bothphp7.20curlandcurl– user535733
Dec 8 '18 at 13:00
Please ensure that you have enabled all software repositories (especially -updates and -security) then run
sudo apt updateandsudo apt dist-upgrade(to get new dependencies). Also add output ofapt-cache policy php7.2-curl curl libcurl4to the question.– N0rbert
Dec 8 '18 at 13:05
@user535733 and N0rbert I have edited the question hope this will be helpful
– Mustafa Taheri
Dec 8 '18 at 14:44
Muistafa, try the duplicates first and keep the results. If none of the duplicates work, edit in the results from the steps you took over there. And please? Don't post screenshots, but copy-paste the text of terminal output so we can just copy-paste it as well...
– Fabby
Dec 14 '18 at 8:23
Apologies for inconvenience @Fabby but none of the above duplicate answer worked for me. I have followed the instructions given by user535733 and that solved my problem.
– Mustafa Taheri
Dec 15 '18 at 12:03