Ubuntu 18.10 Cannot install php7.2-dev for install phpize
I'm having still issues with this on Ubuntu 18.10 with ondrej packages. I want to install php-dev for firebase. When I try to install grpc using pecl It throws me phpize doesn't exist, when I check what I need it is from php7.2-dev. I check held packages but anything on there.
I try to downgrade as you said but appears like explain here:
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Version ‘2:8.39-9’ for ‘libpcre3’ was not found
E: Version ‘2:8.39-9’ for ‘libpcre3-dev’ was not found
And:
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Version ‘1.1.0g-2ubuntu4.1’ for ‘libssl1.1’ was not found
E: Version ‘1.1.0g-2ubuntu4.1’ for ‘libssl-dev’ was not found
Thank you in advance.
apt php 18.10
New contributor
add a comment |
I'm having still issues with this on Ubuntu 18.10 with ondrej packages. I want to install php-dev for firebase. When I try to install grpc using pecl It throws me phpize doesn't exist, when I check what I need it is from php7.2-dev. I check held packages but anything on there.
I try to downgrade as you said but appears like explain here:
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Version ‘2:8.39-9’ for ‘libpcre3’ was not found
E: Version ‘2:8.39-9’ for ‘libpcre3-dev’ was not found
And:
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Version ‘1.1.0g-2ubuntu4.1’ for ‘libssl1.1’ was not found
E: Version ‘1.1.0g-2ubuntu4.1’ for ‘libssl-dev’ was not found
Thank you in advance.
apt php 18.10
New contributor
add a comment |
I'm having still issues with this on Ubuntu 18.10 with ondrej packages. I want to install php-dev for firebase. When I try to install grpc using pecl It throws me phpize doesn't exist, when I check what I need it is from php7.2-dev. I check held packages but anything on there.
I try to downgrade as you said but appears like explain here:
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Version ‘2:8.39-9’ for ‘libpcre3’ was not found
E: Version ‘2:8.39-9’ for ‘libpcre3-dev’ was not found
And:
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Version ‘1.1.0g-2ubuntu4.1’ for ‘libssl1.1’ was not found
E: Version ‘1.1.0g-2ubuntu4.1’ for ‘libssl-dev’ was not found
Thank you in advance.
apt php 18.10
New contributor
I'm having still issues with this on Ubuntu 18.10 with ondrej packages. I want to install php-dev for firebase. When I try to install grpc using pecl It throws me phpize doesn't exist, when I check what I need it is from php7.2-dev. I check held packages but anything on there.
I try to downgrade as you said but appears like explain here:
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Version ‘2:8.39-9’ for ‘libpcre3’ was not found
E: Version ‘2:8.39-9’ for ‘libpcre3-dev’ was not found
And:
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Version ‘1.1.0g-2ubuntu4.1’ for ‘libssl1.1’ was not found
E: Version ‘1.1.0g-2ubuntu4.1’ for ‘libssl-dev’ was not found
Thank you in advance.
apt php 18.10
apt php 18.10
New contributor
New contributor
New contributor
asked Dec 28 '18 at 9:05
Carl A. Rondoni
33
33
New contributor
New contributor
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Let's look at the available sources in the Ununtu repositories for those packages:
$ apt-cache madison libpcre3
libpcre3 | 2:8.39-11 | http://us.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
Ah, there's the problem. On 18.10, you are telling apt to install -9 instead of -11. You're tying to install an OLDER version that's not in the 18.10 repos. This means you have unwisely added a non-Ubuntu source that is intended for an older release of Ubuntu (like 18.04).
When a release of Ubuntu is built from Debian sources, all the versions are synchronized. All of the thousands of package depend upon a single version of each dependency. And then that one version goes into the repos. That's why Ubuntu is referred to as a snapshot distro. When you change versions, you might break all those dependencies. And that's why a release-upgrade involved replacing thousands of packages...all the dependencies must be updated to the new snapshot.
The problem you have is caused by trying to add packages with 18.04 dependencies to an 18.10 system. It won't work without expert ongoing maintenance. You can add 18.10 packages to an 18.10 system, or you can add 18.04 packages to an 18.04 system. But you cannot cross versions with the risk of breaking your system quite horribly, so the whole distro, repos, releases, and apt are set up to stop you from doing that.
Now let's take a look at libssl:
$ apt-cache madison libssl1.1
libssl1.1 | 1.1.1-1ubuntu2.1 | http://us.archive.ubuntu.com/ubuntu cosmic-updates/main amd64 Packages
libssl1.1 | 1.1.1-1ubuntu2.1 | http://security.ubuntu.com/ubuntu cosmic-security/main amd64 Packages
libssl1.1 | 1.1.1-1ubuntu2 | http://us.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
Same problem. Version 1.1.0g-2ubuntu4.1 is in 18.04, not 18.10. You are trying to add 18.04 packages to an 18.10 system. Stop doing that.
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
});
}
});
Carl A. Rondoni is a new contributor. Be nice, and check out our Code of Conduct.
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%2f1105077%2fubuntu-18-10-cannot-install-php7-2-dev-for-install-phpize%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
Let's look at the available sources in the Ununtu repositories for those packages:
$ apt-cache madison libpcre3
libpcre3 | 2:8.39-11 | http://us.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
Ah, there's the problem. On 18.10, you are telling apt to install -9 instead of -11. You're tying to install an OLDER version that's not in the 18.10 repos. This means you have unwisely added a non-Ubuntu source that is intended for an older release of Ubuntu (like 18.04).
When a release of Ubuntu is built from Debian sources, all the versions are synchronized. All of the thousands of package depend upon a single version of each dependency. And then that one version goes into the repos. That's why Ubuntu is referred to as a snapshot distro. When you change versions, you might break all those dependencies. And that's why a release-upgrade involved replacing thousands of packages...all the dependencies must be updated to the new snapshot.
The problem you have is caused by trying to add packages with 18.04 dependencies to an 18.10 system. It won't work without expert ongoing maintenance. You can add 18.10 packages to an 18.10 system, or you can add 18.04 packages to an 18.04 system. But you cannot cross versions with the risk of breaking your system quite horribly, so the whole distro, repos, releases, and apt are set up to stop you from doing that.
Now let's take a look at libssl:
$ apt-cache madison libssl1.1
libssl1.1 | 1.1.1-1ubuntu2.1 | http://us.archive.ubuntu.com/ubuntu cosmic-updates/main amd64 Packages
libssl1.1 | 1.1.1-1ubuntu2.1 | http://security.ubuntu.com/ubuntu cosmic-security/main amd64 Packages
libssl1.1 | 1.1.1-1ubuntu2 | http://us.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
Same problem. Version 1.1.0g-2ubuntu4.1 is in 18.04, not 18.10. You are trying to add 18.04 packages to an 18.10 system. Stop doing that.
add a comment |
Let's look at the available sources in the Ununtu repositories for those packages:
$ apt-cache madison libpcre3
libpcre3 | 2:8.39-11 | http://us.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
Ah, there's the problem. On 18.10, you are telling apt to install -9 instead of -11. You're tying to install an OLDER version that's not in the 18.10 repos. This means you have unwisely added a non-Ubuntu source that is intended for an older release of Ubuntu (like 18.04).
When a release of Ubuntu is built from Debian sources, all the versions are synchronized. All of the thousands of package depend upon a single version of each dependency. And then that one version goes into the repos. That's why Ubuntu is referred to as a snapshot distro. When you change versions, you might break all those dependencies. And that's why a release-upgrade involved replacing thousands of packages...all the dependencies must be updated to the new snapshot.
The problem you have is caused by trying to add packages with 18.04 dependencies to an 18.10 system. It won't work without expert ongoing maintenance. You can add 18.10 packages to an 18.10 system, or you can add 18.04 packages to an 18.04 system. But you cannot cross versions with the risk of breaking your system quite horribly, so the whole distro, repos, releases, and apt are set up to stop you from doing that.
Now let's take a look at libssl:
$ apt-cache madison libssl1.1
libssl1.1 | 1.1.1-1ubuntu2.1 | http://us.archive.ubuntu.com/ubuntu cosmic-updates/main amd64 Packages
libssl1.1 | 1.1.1-1ubuntu2.1 | http://security.ubuntu.com/ubuntu cosmic-security/main amd64 Packages
libssl1.1 | 1.1.1-1ubuntu2 | http://us.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
Same problem. Version 1.1.0g-2ubuntu4.1 is in 18.04, not 18.10. You are trying to add 18.04 packages to an 18.10 system. Stop doing that.
add a comment |
Let's look at the available sources in the Ununtu repositories for those packages:
$ apt-cache madison libpcre3
libpcre3 | 2:8.39-11 | http://us.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
Ah, there's the problem. On 18.10, you are telling apt to install -9 instead of -11. You're tying to install an OLDER version that's not in the 18.10 repos. This means you have unwisely added a non-Ubuntu source that is intended for an older release of Ubuntu (like 18.04).
When a release of Ubuntu is built from Debian sources, all the versions are synchronized. All of the thousands of package depend upon a single version of each dependency. And then that one version goes into the repos. That's why Ubuntu is referred to as a snapshot distro. When you change versions, you might break all those dependencies. And that's why a release-upgrade involved replacing thousands of packages...all the dependencies must be updated to the new snapshot.
The problem you have is caused by trying to add packages with 18.04 dependencies to an 18.10 system. It won't work without expert ongoing maintenance. You can add 18.10 packages to an 18.10 system, or you can add 18.04 packages to an 18.04 system. But you cannot cross versions with the risk of breaking your system quite horribly, so the whole distro, repos, releases, and apt are set up to stop you from doing that.
Now let's take a look at libssl:
$ apt-cache madison libssl1.1
libssl1.1 | 1.1.1-1ubuntu2.1 | http://us.archive.ubuntu.com/ubuntu cosmic-updates/main amd64 Packages
libssl1.1 | 1.1.1-1ubuntu2.1 | http://security.ubuntu.com/ubuntu cosmic-security/main amd64 Packages
libssl1.1 | 1.1.1-1ubuntu2 | http://us.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
Same problem. Version 1.1.0g-2ubuntu4.1 is in 18.04, not 18.10. You are trying to add 18.04 packages to an 18.10 system. Stop doing that.
Let's look at the available sources in the Ununtu repositories for those packages:
$ apt-cache madison libpcre3
libpcre3 | 2:8.39-11 | http://us.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
Ah, there's the problem. On 18.10, you are telling apt to install -9 instead of -11. You're tying to install an OLDER version that's not in the 18.10 repos. This means you have unwisely added a non-Ubuntu source that is intended for an older release of Ubuntu (like 18.04).
When a release of Ubuntu is built from Debian sources, all the versions are synchronized. All of the thousands of package depend upon a single version of each dependency. And then that one version goes into the repos. That's why Ubuntu is referred to as a snapshot distro. When you change versions, you might break all those dependencies. And that's why a release-upgrade involved replacing thousands of packages...all the dependencies must be updated to the new snapshot.
The problem you have is caused by trying to add packages with 18.04 dependencies to an 18.10 system. It won't work without expert ongoing maintenance. You can add 18.10 packages to an 18.10 system, or you can add 18.04 packages to an 18.04 system. But you cannot cross versions with the risk of breaking your system quite horribly, so the whole distro, repos, releases, and apt are set up to stop you from doing that.
Now let's take a look at libssl:
$ apt-cache madison libssl1.1
libssl1.1 | 1.1.1-1ubuntu2.1 | http://us.archive.ubuntu.com/ubuntu cosmic-updates/main amd64 Packages
libssl1.1 | 1.1.1-1ubuntu2.1 | http://security.ubuntu.com/ubuntu cosmic-security/main amd64 Packages
libssl1.1 | 1.1.1-1ubuntu2 | http://us.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
Same problem. Version 1.1.0g-2ubuntu4.1 is in 18.04, not 18.10. You are trying to add 18.04 packages to an 18.10 system. Stop doing that.
answered Dec 28 '18 at 13:12
user535733
7,68222942
7,68222942
add a comment |
add a comment |
Carl A. Rondoni is a new contributor. Be nice, and check out our Code of Conduct.
Carl A. Rondoni is a new contributor. Be nice, and check out our Code of Conduct.
Carl A. Rondoni is a new contributor. Be nice, and check out our Code of Conduct.
Carl A. Rondoni is a new contributor. Be nice, and check out our Code of Conduct.
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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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%2f1105077%2fubuntu-18-10-cannot-install-php7-2-dev-for-install-phpize%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