install libicu-dev libicu-dev:i386 at the same time produce error at Ubuntu18 (on Ubuntu16 works fine)
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
apt-get install libicu-dev libicu-dev:i386 produces error on ubuntu18, but works fine at ubuntu16. Does anybody have any ideas? See P.S. for details and PP.S. for OS information
Artem.
P.S.
sudo apt-get install libicu-dev libicu-dev:i386
Reading package lists... Done
Building dependency tree
Reading state information... Done
libicu-dev:i386 is already the newest version (60.2-3ubuntu3).
libicu-dev:i386 set to manually installed.
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
libicu-dev : Conflicts: libicu-dev:i386 but 60.2-3ubuntu3 is to be installed
libicu-dev:i386 : Conflicts: libicu-dev but 60.2-3ubuntu3 is to be installed
E: Unable to correct problems, you have held broken packages.
PP.S.
cat /etc/os-release
NAME="Ubuntu"
VERSION="18.04.2 LTS (Bionic Beaver)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 18.04.2 LTS"
VERSION_ID="18.04"
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
VERSION_CODENAME=bionic
UBUNTU_CODENAME=bionic
apt
asked Feb 22 at 9:27
Artem RufanovArtem Rufanov
61
add a comment |
apt-get install libicu-dev libicu-dev:i386 produces error on ubuntu18, but works fine at ubuntu16. Does anybody have any ideas? See P.S. for details and PP.S. for OS information
Artem.
P.S.
sudo apt-get install libicu-dev libicu-dev:i386
Reading package lists... Done
Building dependency tree
Reading state information... Done
libicu-dev:i386 is already the newest version (60.2-3ubuntu3).
libicu-dev:i386 set to manually installed.
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
libicu-dev : Conflicts: libicu-dev:i386 but 60.2-3ubuntu3 is to be installed
libicu-dev:i386 : Conflicts: libicu-dev but 60.2-3ubuntu3 is to be installed
E: Unable to correct problems, you have held broken packages.
PP.S.
cat /etc/os-release
NAME="Ubuntu"
VERSION="18.04.2 LTS (Bionic Beaver)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 18.04.2 LTS"
VERSION_ID="18.04"
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
VERSION_CODENAME=bionic
UBUNTU_CODENAME=bionic
apt
asked Feb 22 at 9:27
Artem RufanovArtem Rufanov
61
add a comment |
apt-get install libicu-dev libicu-dev:i386 produces error on ubuntu18, but works fine at ubuntu16. Does anybody have any ideas? See P.S. for details and PP.S. for OS information
Artem.
P.S.
sudo apt-get install libicu-dev libicu-dev:i386
Reading package lists... Done
Building dependency tree
Reading state information... Done
libicu-dev:i386 is already the newest version (60.2-3ubuntu3).
libicu-dev:i386 set to manually installed.
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
libicu-dev : Conflicts: libicu-dev:i386 but 60.2-3ubuntu3 is to be installed
libicu-dev:i386 : Conflicts: libicu-dev but 60.2-3ubuntu3 is to be installed
E: Unable to correct problems, you have held broken packages.
PP.S.
cat /etc/os-release
NAME="Ubuntu"
VERSION="18.04.2 LTS (Bionic Beaver)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 18.04.2 LTS"
VERSION_ID="18.04"
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
VERSION_CODENAME=bionic
UBUNTU_CODENAME=bionic
apt
asked Feb 22 at 9:27
Artem RufanovArtem Rufanov
61
apt-get install libicu-dev libicu-dev:i386 produces error on ubuntu18, but works fine at ubuntu16. Does anybody have any ideas? See P.S. for details and PP.S. for OS information
Artem.
P.S.
sudo apt-get install libicu-dev libicu-dev:i386
Reading package lists... Done
Building dependency tree
Reading state information... Done
libicu-dev:i386 is already the newest version (60.2-3ubuntu3).
libicu-dev:i386 set to manually installed.
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
libicu-dev : Conflicts: libicu-dev:i386 but 60.2-3ubuntu3 is to be installed
libicu-dev:i386 : Conflicts: libicu-dev but 60.2-3ubuntu3 is to be installed
E: Unable to correct problems, you have held broken packages.
PP.S.
cat /etc/os-release
NAME="Ubuntu"
VERSION="18.04.2 LTS (Bionic Beaver)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 18.04.2 LTS"
VERSION_ID="18.04"
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
VERSION_CODENAME=bionic
UBUNTU_CODENAME=bionic
apt
apt
asked Feb 22 at 9:27
Artem RufanovArtem Rufanov
61
asked Feb 22 at 9:27
Artem RufanovArtem Rufanov
61
asked Feb 22 at 9:27
Artem RufanovArtem Rufanov
61
asked Feb 22 at 9:27
Artem RufanovArtem Rufanov
61
asked Feb 22 at 9:27
Artem RufanovArtem Rufanov
61
61
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
It is normal behaviour.
If you compare the filelists of both packages obtained from https://packages.ubuntu.com/bionic/libicu-dev you will see that they have at least one identical filepath /usr/bin/icu-config:
amd64:
i386
So you should not have these two packages installed in the same time.
answered Feb 22 at 11:06
N0rbertN0rbert
25.7k855122
add a comment |
Thank you for answer, I got it. This approach doesn't allow to build both i386 & amd64 c++ application at the single machine at single time. For example centos7 & redhat7 allow to install i686 & x86_64 packages at the same time. As far as I understand this approach as designed and no way to install these packages at the same time.
answered Feb 23 at 13:51
Artem RufanovArtem Rufanov
61
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%2f1120326%2finstall-libicu-dev-libicu-devi386-at-the-same-time-produce-error-at-ubuntu18-o%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
It is normal behaviour.
If you compare the filelists of both packages obtained from https://packages.ubuntu.com/bionic/libicu-dev you will see that they have at least one identical filepath /usr/bin/icu-config:
amd64:
i386
So you should not have these two packages installed in the same time.
answered Feb 22 at 11:06
N0rbertN0rbert
25.7k855122
add a comment |
It is normal behaviour.
If you compare the filelists of both packages obtained from https://packages.ubuntu.com/bionic/libicu-dev you will see that they have at least one identical filepath /usr/bin/icu-config:
amd64:
i386
So you should not have these two packages installed in the same time.
answered Feb 22 at 11:06
N0rbertN0rbert
25.7k855122
add a comment |
It is normal behaviour.
If you compare the filelists of both packages obtained from https://packages.ubuntu.com/bionic/libicu-dev you will see that they have at least one identical filepath /usr/bin/icu-config:
amd64:
i386
So you should not have these two packages installed in the same time.
answered Feb 22 at 11:06
N0rbertN0rbert
25.7k855122
It is normal behaviour.
If you compare the filelists of both packages obtained from https://packages.ubuntu.com/bionic/libicu-dev you will see that they have at least one identical filepath /usr/bin/icu-config:
amd64:
i386
So you should not have these two packages installed in the same time.
answered Feb 22 at 11:06
N0rbertN0rbert
25.7k855122
edited Feb 22 at 11:15
answered Feb 22 at 11:06
N0rbertN0rbert
25.7k855122
answered Feb 22 at 11:06
N0rbertN0rbert
25.7k855122
answered Feb 22 at 11:06
N0rbertN0rbert
25.7k855122
25.7k855122
add a comment |
add a comment |
Thank you for answer, I got it. This approach doesn't allow to build both i386 & amd64 c++ application at the single machine at single time. For example centos7 & redhat7 allow to install i686 & x86_64 packages at the same time. As far as I understand this approach as designed and no way to install these packages at the same time.
answered Feb 23 at 13:51
Artem RufanovArtem Rufanov
61
add a comment |
Thank you for answer, I got it. This approach doesn't allow to build both i386 & amd64 c++ application at the single machine at single time. For example centos7 & redhat7 allow to install i686 & x86_64 packages at the same time. As far as I understand this approach as designed and no way to install these packages at the same time.
answered Feb 23 at 13:51
Artem RufanovArtem Rufanov
61
add a comment |
Thank you for answer, I got it. This approach doesn't allow to build both i386 & amd64 c++ application at the single machine at single time. For example centos7 & redhat7 allow to install i686 & x86_64 packages at the same time. As far as I understand this approach as designed and no way to install these packages at the same time.
answered Feb 23 at 13:51
Artem RufanovArtem Rufanov
61
Thank you for answer, I got it. This approach doesn't allow to build both i386 & amd64 c++ application at the single machine at single time. For example centos7 & redhat7 allow to install i686 & x86_64 packages at the same time. As far as I understand this approach as designed and no way to install these packages at the same time.
answered Feb 23 at 13:51
Artem RufanovArtem Rufanov
61
answered Feb 23 at 13:51
Artem RufanovArtem Rufanov
61
answered Feb 23 at 13:51
Artem RufanovArtem Rufanov
61
answered Feb 23 at 13:51
Artem RufanovArtem Rufanov
61
61
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%2f1120326%2finstall-libicu-dev-libicu-devi386-at-the-same-time-produce-error-at-ubuntu18-o%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
