errors upgrading from 14.04 to 16.04 about Unknown Multi-Arch type for compiz, libkf5akonadisearch-bin...
I'm trying to upgrade my 14.04 machine to 16.04 using do-release-upgrade. After downloading the package lists for wily, I see the following errors:
Unknown Multi-Arch type 'no' for package 'compiz-core'
Unknown Multi-Arch type 'no' for package 'compiz-gnome'
Ignoring Provides line with DepCompareOp for package python-cffi-backend-api-max
Ignoring Provides line with DepCompareOp for package python-cffi-backend-api-min
Ignoring Provides line with DepCompareOp for package python3-cffi-backend-api-max
Ignoring Provides line with DepCompareOp for package python3-cffi-backend-api-min
Unknown Multi-Arch type 'no' for package 'libkf5akonadisearch-bin'
Ignoring Provides line with DepCompareOp for package php-psr-http-message-implementation
Ignoring Provides line with DepCompareOp for package php-psr-log-implementation
Ignoring Provides line with DepCompareOp for package php-math-biginteger
Unknown Multi-Arch type 'no' for package 'compiz-core'
Unknown Multi-Arch type 'no' for package 'compiz-gnome'
Ignoring Provides line with DepCompareOp for package python-cffi-backend-api-max
Ignoring Provides line with DepCompareOp for package python-cffi-backend-api-min
Ignoring Provides line with DepCompareOp for package python3-cffi-backend-api-max
Ignoring Provides line with DepCompareOp for package python3-cffi-backend-api-min
Unknown Multi-Arch type 'no' for package 'libkf5akonadisearch-bin'
Unknown Multi-Arch type 'no' for package 'compiz-core'
Unknown Multi-Arch type 'no' for package 'compiz-gnome'
Unknown Multi-Arch type 'no' for package 'compiz-core'
Unknown Multi-Arch type 'no' for package 'compiz-gnome'
You may want to run apt-get update to correct these problems
It then proceeds to abort the installation. The suggested run of apt-get update doesn't seem to do anything. Googling for the above error messages yielded others having similar problems when upgrading to other, previous releases, although I've not come across any apparent fixes. It's suggested that an apt upgrade could fix the problem, but I don't see a way to easily do that (it's up to date with the latest trusty package).
What should I do in order to upgrade directly to 16.04?
14.04 upgrade package-management 16.04 multiarch
edited Jul 10 '16 at 5:17
Josip Rodin
300111
asked Apr 21 '16 at 17:41
Jason RJason R
250139
add a comment |
I'm trying to upgrade my 14.04 machine to 16.04 using do-release-upgrade. After downloading the package lists for wily, I see the following errors:
Unknown Multi-Arch type 'no' for package 'compiz-core'
Unknown Multi-Arch type 'no' for package 'compiz-gnome'
Ignoring Provides line with DepCompareOp for package python-cffi-backend-api-max
Ignoring Provides line with DepCompareOp for package python-cffi-backend-api-min
Ignoring Provides line with DepCompareOp for package python3-cffi-backend-api-max
Ignoring Provides line with DepCompareOp for package python3-cffi-backend-api-min
Unknown Multi-Arch type 'no' for package 'libkf5akonadisearch-bin'
Ignoring Provides line with DepCompareOp for package php-psr-http-message-implementation
Ignoring Provides line with DepCompareOp for package php-psr-log-implementation
Ignoring Provides line with DepCompareOp for package php-math-biginteger
Unknown Multi-Arch type 'no' for package 'compiz-core'
Unknown Multi-Arch type 'no' for package 'compiz-gnome'
Ignoring Provides line with DepCompareOp for package python-cffi-backend-api-max
Ignoring Provides line with DepCompareOp for package python-cffi-backend-api-min
Ignoring Provides line with DepCompareOp for package python3-cffi-backend-api-max
Ignoring Provides line with DepCompareOp for package python3-cffi-backend-api-min
Unknown Multi-Arch type 'no' for package 'libkf5akonadisearch-bin'
Unknown Multi-Arch type 'no' for package 'compiz-core'
Unknown Multi-Arch type 'no' for package 'compiz-gnome'
Unknown Multi-Arch type 'no' for package 'compiz-core'
Unknown Multi-Arch type 'no' for package 'compiz-gnome'
You may want to run apt-get update to correct these problems
It then proceeds to abort the installation. The suggested run of apt-get update doesn't seem to do anything. Googling for the above error messages yielded others having similar problems when upgrading to other, previous releases, although I've not come across any apparent fixes. It's suggested that an apt upgrade could fix the problem, but I don't see a way to easily do that (it's up to date with the latest trusty package).
What should I do in order to upgrade directly to 16.04?
14.04 upgrade package-management 16.04 multiarch
edited Jul 10 '16 at 5:17
Josip Rodin
300111
asked Apr 21 '16 at 17:41
Jason RJason R
250139
It looks like those three packages -libkf5akonadisearch-bin,compiz-core,compiz-gnomehave broken meta data, though it's unclear whether that is so in the old ones or in the new ones. In case it's in the old packages, could you try removing the three temporarily and see if it helps?
– Josip Rodin
Jul 9 '16 at 21:18
Also, if it's 16.04 you want, that should be xenial, not wily.
– Josip Rodin
Jul 10 '16 at 9:06
Fwiw, this is not an issue with the installed packages; I get it too, and I don't have any of those packages installed.
– Doug
Jul 13 '16 at 0:39
Agreed with @Doug. None of these packages are installed for me, and I still get the error. Totally stuck.
– sstringer
Aug 25 '16 at 21:01
add a comment |
I'm trying to upgrade my 14.04 machine to 16.04 using do-release-upgrade. After downloading the package lists for wily, I see the following errors:
Unknown Multi-Arch type 'no' for package 'compiz-core'
Unknown Multi-Arch type 'no' for package 'compiz-gnome'
Ignoring Provides line with DepCompareOp for package python-cffi-backend-api-max
Ignoring Provides line with DepCompareOp for package python-cffi-backend-api-min
Ignoring Provides line with DepCompareOp for package python3-cffi-backend-api-max
Ignoring Provides line with DepCompareOp for package python3-cffi-backend-api-min
Unknown Multi-Arch type 'no' for package 'libkf5akonadisearch-bin'
Ignoring Provides line with DepCompareOp for package php-psr-http-message-implementation
Ignoring Provides line with DepCompareOp for package php-psr-log-implementation
Ignoring Provides line with DepCompareOp for package php-math-biginteger
Unknown Multi-Arch type 'no' for package 'compiz-core'
Unknown Multi-Arch type 'no' for package 'compiz-gnome'
Ignoring Provides line with DepCompareOp for package python-cffi-backend-api-max
Ignoring Provides line with DepCompareOp for package python-cffi-backend-api-min
Ignoring Provides line with DepCompareOp for package python3-cffi-backend-api-max
Ignoring Provides line with DepCompareOp for package python3-cffi-backend-api-min
Unknown Multi-Arch type 'no' for package 'libkf5akonadisearch-bin'
Unknown Multi-Arch type 'no' for package 'compiz-core'
Unknown Multi-Arch type 'no' for package 'compiz-gnome'
Unknown Multi-Arch type 'no' for package 'compiz-core'
Unknown Multi-Arch type 'no' for package 'compiz-gnome'
You may want to run apt-get update to correct these problems
It then proceeds to abort the installation. The suggested run of apt-get update doesn't seem to do anything. Googling for the above error messages yielded others having similar problems when upgrading to other, previous releases, although I've not come across any apparent fixes. It's suggested that an apt upgrade could fix the problem, but I don't see a way to easily do that (it's up to date with the latest trusty package).
What should I do in order to upgrade directly to 16.04?
14.04 upgrade package-management 16.04 multiarch
edited Jul 10 '16 at 5:17
Josip Rodin
300111
asked Apr 21 '16 at 17:41
Jason RJason R
250139
I'm trying to upgrade my 14.04 machine to 16.04 using do-release-upgrade. After downloading the package lists for wily, I see the following errors:
Unknown Multi-Arch type 'no' for package 'compiz-core'
Unknown Multi-Arch type 'no' for package 'compiz-gnome'
Ignoring Provides line with DepCompareOp for package python-cffi-backend-api-max
Ignoring Provides line with DepCompareOp for package python-cffi-backend-api-min
Ignoring Provides line with DepCompareOp for package python3-cffi-backend-api-max
Ignoring Provides line with DepCompareOp for package python3-cffi-backend-api-min
Unknown Multi-Arch type 'no' for package 'libkf5akonadisearch-bin'
Ignoring Provides line with DepCompareOp for package php-psr-http-message-implementation
Ignoring Provides line with DepCompareOp for package php-psr-log-implementation
Ignoring Provides line with DepCompareOp for package php-math-biginteger
Unknown Multi-Arch type 'no' for package 'compiz-core'
Unknown Multi-Arch type 'no' for package 'compiz-gnome'
Ignoring Provides line with DepCompareOp for package python-cffi-backend-api-max
Ignoring Provides line with DepCompareOp for package python-cffi-backend-api-min
Ignoring Provides line with DepCompareOp for package python3-cffi-backend-api-max
Ignoring Provides line with DepCompareOp for package python3-cffi-backend-api-min
Unknown Multi-Arch type 'no' for package 'libkf5akonadisearch-bin'
Unknown Multi-Arch type 'no' for package 'compiz-core'
Unknown Multi-Arch type 'no' for package 'compiz-gnome'
Unknown Multi-Arch type 'no' for package 'compiz-core'
Unknown Multi-Arch type 'no' for package 'compiz-gnome'
You may want to run apt-get update to correct these problems
It then proceeds to abort the installation. The suggested run of apt-get update doesn't seem to do anything. Googling for the above error messages yielded others having similar problems when upgrading to other, previous releases, although I've not come across any apparent fixes. It's suggested that an apt upgrade could fix the problem, but I don't see a way to easily do that (it's up to date with the latest trusty package).
What should I do in order to upgrade directly to 16.04?
14.04 upgrade package-management 16.04 multiarch
14.04 upgrade package-management 16.04 multiarch
edited Jul 10 '16 at 5:17
Josip Rodin
300111
asked Apr 21 '16 at 17:41
Jason RJason R
250139
edited Jul 10 '16 at 5:17
Josip Rodin
300111
asked Apr 21 '16 at 17:41
Jason RJason R
250139
edited Jul 10 '16 at 5:17
Josip Rodin
300111
edited Jul 10 '16 at 5:17
Josip Rodin
300111
edited Jul 10 '16 at 5:17
Josip Rodin
300111
300111
asked Apr 21 '16 at 17:41
Jason RJason R
250139
asked Apr 21 '16 at 17:41
Jason RJason R
250139
asked Apr 21 '16 at 17:41
Jason RJason R
250139
250139
It looks like those three packages -libkf5akonadisearch-bin,compiz-core,compiz-gnomehave broken meta data, though it's unclear whether that is so in the old ones or in the new ones. In case it's in the old packages, could you try removing the three temporarily and see if it helps?
– Josip Rodin
Jul 9 '16 at 21:18
Also, if it's 16.04 you want, that should be xenial, not wily.
– Josip Rodin
Jul 10 '16 at 9:06
Fwiw, this is not an issue with the installed packages; I get it too, and I don't have any of those packages installed.
– Doug
Jul 13 '16 at 0:39
Agreed with @Doug. None of these packages are installed for me, and I still get the error. Totally stuck.
– sstringer
Aug 25 '16 at 21:01
add a comment |
It looks like those three packages -libkf5akonadisearch-bin,compiz-core,compiz-gnomehave broken meta data, though it's unclear whether that is so in the old ones or in the new ones. In case it's in the old packages, could you try removing the three temporarily and see if it helps?
– Josip Rodin
Jul 9 '16 at 21:18
Also, if it's 16.04 you want, that should be xenial, not wily.
– Josip Rodin
Jul 10 '16 at 9:06
Fwiw, this is not an issue with the installed packages; I get it too, and I don't have any of those packages installed.
– Doug
Jul 13 '16 at 0:39
Agreed with @Doug. None of these packages are installed for me, and I still get the error. Totally stuck.
– sstringer
Aug 25 '16 at 21:01
It looks like those three packages -
libkf5akonadisearch-bin, compiz-core, compiz-gnome have broken meta data, though it's unclear whether that is so in the old ones or in the new ones. In case it's in the old packages, could you try removing the three temporarily and see if it helps?– Josip Rodin
Jul 9 '16 at 21:18
It looks like those three packages -
libkf5akonadisearch-bin, compiz-core, compiz-gnome have broken meta data, though it's unclear whether that is so in the old ones or in the new ones. In case it's in the old packages, could you try removing the three temporarily and see if it helps?– Josip Rodin
Jul 9 '16 at 21:18
Also, if it's 16.04 you want, that should be xenial, not wily.
– Josip Rodin
Jul 10 '16 at 9:06
Also, if it's 16.04 you want, that should be xenial, not wily.
– Josip Rodin
Jul 10 '16 at 9:06
Fwiw, this is not an issue with the installed packages; I get it too, and I don't have any of those packages installed.
– Doug
Jul 13 '16 at 0:39
Fwiw, this is not an issue with the installed packages; I get it too, and I don't have any of those packages installed.
– Doug
Jul 13 '16 at 0:39
Agreed with @Doug. None of these packages are installed for me, and I still get the error. Totally stuck.
– sstringer
Aug 25 '16 at 21:01
Agreed with @Doug. None of these packages are installed for me, and I still get the error. Totally stuck.
– sstringer
Aug 25 '16 at 21:01
add a comment |
5 Answers
5
active
oldest
votes
This is a bug in apt, and yes, the fix is to upgrade apt.
Edit /etc/apt/sources.list and uncomment these lines:
deb http://au.archive.ubuntu.com/ubuntu/ wily main restricted
deb http://au.archive.ubuntu.com/ubuntu/ wily-updates main restricted
Now run apt-get update and you'll see the same errors about 'Unknown Multi-Arch type'.
Now upgrade apt:
apt-get install --only-upgrade apt
Now run the release installer:
do-release-upgrade
:)
answered Jul 13 '16 at 0:55
DougDoug
35659
2
Unfortunately, this didn't work for me. Tried several mirror variants and I always get "apt is already the newest version" and still the original show-stopping error described by OP.
– sstringer
Aug 25 '16 at 21:02
@sstringer All I can suggest is make absolutely sure that you're updated the sources list and are pulling down the package list from the next major version (ie. Wily).apt-get updateshould show it downloading a whole pile of packages. ...sorry I can't be more help. This is a super frustrating bug I know. All I can say is: However you do it, you need to upgrade apt to get past the issue, it's the only solution I've ever found to this issue.
– Doug
Aug 26 '16 at 2:38
One has to ensure that no apt-pinning is in place.
– koppor
Mar 18 '17 at 0:29
add a comment |
What seems to have worked for me was
apt-get -f install libc6
apt-get install --only-upgrade apt
answered Sep 17 '16 at 22:51
Willem P. BothaWillem P. Botha
1686
I used this to help with w/ a Mint 17->18 upgrade. These errors seem like false positives.
– Michael Cole
Sep 18 '16 at 19:29
add a comment |
You have to do this:
sudo apt-get install -f
answered Jan 21 '17 at 10:45
flavio.trojaflavio.troja
32913
add a comment |
I also get the "newest version" message, but according to https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1404783/comments/12
I added sources for vivid and vivid-updates to sources.list and installed the apt/vivid version.
sudo apt-get -t vivid install apt/vivid
Then I deleted vivid source from sources.list and apt-get update finished without any warning.
answered Dec 6 '16 at 16:47
RuprechtRuprecht
11
1
apt-getdoesn't have a -t option.
– Elder Geek
Dec 6 '16 at 17:25
It does actually, the -t flag is for --target-release.
– Software_Programineer
Apr 27 '18 at 17:24
add a comment |
Here's what worked for me :
sudo rm -r /var/lib/apt/lists/*
sudo apt-get clean
sudo apt-get update
I had segmentation faults errors during the install, so I cleared the archives again:
sudo apt-get clean
And everything went fine.
Hope it'll help !
answered 9 hours ago
madjaouemadjaoue
1012
New contributor
madjaoue 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%2f760071%2ferrors-upgrading-from-14-04-to-16-04-about-unknown-multi-arch-type-for-compiz-l%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
5 Answers
5
active
oldest
votes
5 Answers
5
active
oldest
votes
active
oldest
votes
active
oldest
votes
This is a bug in apt, and yes, the fix is to upgrade apt.
Edit /etc/apt/sources.list and uncomment these lines:
deb http://au.archive.ubuntu.com/ubuntu/ wily main restricted
deb http://au.archive.ubuntu.com/ubuntu/ wily-updates main restricted
Now run apt-get update and you'll see the same errors about 'Unknown Multi-Arch type'.
Now upgrade apt:
apt-get install --only-upgrade apt
Now run the release installer:
do-release-upgrade
:)
answered Jul 13 '16 at 0:55
DougDoug
35659
2
Unfortunately, this didn't work for me. Tried several mirror variants and I always get "apt is already the newest version" and still the original show-stopping error described by OP.
– sstringer
Aug 25 '16 at 21:02
@sstringer All I can suggest is make absolutely sure that you're updated the sources list and are pulling down the package list from the next major version (ie. Wily).apt-get updateshould show it downloading a whole pile of packages. ...sorry I can't be more help. This is a super frustrating bug I know. All I can say is: However you do it, you need to upgrade apt to get past the issue, it's the only solution I've ever found to this issue.
– Doug
Aug 26 '16 at 2:38
One has to ensure that no apt-pinning is in place.
– koppor
Mar 18 '17 at 0:29
add a comment |
This is a bug in apt, and yes, the fix is to upgrade apt.
Edit /etc/apt/sources.list and uncomment these lines:
deb http://au.archive.ubuntu.com/ubuntu/ wily main restricted
deb http://au.archive.ubuntu.com/ubuntu/ wily-updates main restricted
Now run apt-get update and you'll see the same errors about 'Unknown Multi-Arch type'.
Now upgrade apt:
apt-get install --only-upgrade apt
Now run the release installer:
do-release-upgrade
:)
answered Jul 13 '16 at 0:55
DougDoug
35659
2
Unfortunately, this didn't work for me. Tried several mirror variants and I always get "apt is already the newest version" and still the original show-stopping error described by OP.
– sstringer
Aug 25 '16 at 21:02
@sstringer All I can suggest is make absolutely sure that you're updated the sources list and are pulling down the package list from the next major version (ie. Wily).apt-get updateshould show it downloading a whole pile of packages. ...sorry I can't be more help. This is a super frustrating bug I know. All I can say is: However you do it, you need to upgrade apt to get past the issue, it's the only solution I've ever found to this issue.
– Doug
Aug 26 '16 at 2:38
One has to ensure that no apt-pinning is in place.
– koppor
Mar 18 '17 at 0:29
add a comment |
This is a bug in apt, and yes, the fix is to upgrade apt.
Edit /etc/apt/sources.list and uncomment these lines:
deb http://au.archive.ubuntu.com/ubuntu/ wily main restricted
deb http://au.archive.ubuntu.com/ubuntu/ wily-updates main restricted
Now run apt-get update and you'll see the same errors about 'Unknown Multi-Arch type'.
Now upgrade apt:
apt-get install --only-upgrade apt
Now run the release installer:
do-release-upgrade
:)
answered Jul 13 '16 at 0:55
DougDoug
35659
This is a bug in apt, and yes, the fix is to upgrade apt.
Edit /etc/apt/sources.list and uncomment these lines:
deb http://au.archive.ubuntu.com/ubuntu/ wily main restricted
deb http://au.archive.ubuntu.com/ubuntu/ wily-updates main restricted
Now run apt-get update and you'll see the same errors about 'Unknown Multi-Arch type'.
Now upgrade apt:
apt-get install --only-upgrade apt
Now run the release installer:
do-release-upgrade
:)
answered Jul 13 '16 at 0:55
DougDoug
35659
answered Jul 13 '16 at 0:55
DougDoug
35659
answered Jul 13 '16 at 0:55
DougDoug
35659
answered Jul 13 '16 at 0:55
DougDoug
35659
35659
2
Unfortunately, this didn't work for me. Tried several mirror variants and I always get "apt is already the newest version" and still the original show-stopping error described by OP.
– sstringer
Aug 25 '16 at 21:02
@sstringer All I can suggest is make absolutely sure that you're updated the sources list and are pulling down the package list from the next major version (ie. Wily).apt-get updateshould show it downloading a whole pile of packages. ...sorry I can't be more help. This is a super frustrating bug I know. All I can say is: However you do it, you need to upgrade apt to get past the issue, it's the only solution I've ever found to this issue.
– Doug
Aug 26 '16 at 2:38
One has to ensure that no apt-pinning is in place.
– koppor
Mar 18 '17 at 0:29
add a comment |
2
Unfortunately, this didn't work for me. Tried several mirror variants and I always get "apt is already the newest version" and still the original show-stopping error described by OP.
– sstringer
Aug 25 '16 at 21:02
@sstringer All I can suggest is make absolutely sure that you're updated the sources list and are pulling down the package list from the next major version (ie. Wily).apt-get updateshould show it downloading a whole pile of packages. ...sorry I can't be more help. This is a super frustrating bug I know. All I can say is: However you do it, you need to upgrade apt to get past the issue, it's the only solution I've ever found to this issue.
– Doug
Aug 26 '16 at 2:38
One has to ensure that no apt-pinning is in place.
– koppor
Mar 18 '17 at 0:29
2
2
Unfortunately, this didn't work for me. Tried several mirror variants and I always get "apt is already the newest version" and still the original show-stopping error described by OP.
– sstringer
Aug 25 '16 at 21:02
Unfortunately, this didn't work for me. Tried several mirror variants and I always get "apt is already the newest version" and still the original show-stopping error described by OP.
– sstringer
Aug 25 '16 at 21:02
@sstringer All I can suggest is make absolutely sure that you're updated the sources list and are pulling down the package list from the next major version (ie. Wily).
apt-get update should show it downloading a whole pile of packages. ...sorry I can't be more help. This is a super frustrating bug I know. All I can say is: However you do it, you need to upgrade apt to get past the issue, it's the only solution I've ever found to this issue.– Doug
Aug 26 '16 at 2:38
@sstringer All I can suggest is make absolutely sure that you're updated the sources list and are pulling down the package list from the next major version (ie. Wily).
apt-get update should show it downloading a whole pile of packages. ...sorry I can't be more help. This is a super frustrating bug I know. All I can say is: However you do it, you need to upgrade apt to get past the issue, it's the only solution I've ever found to this issue.– Doug
Aug 26 '16 at 2:38
One has to ensure that no apt-pinning is in place.
– koppor
Mar 18 '17 at 0:29
One has to ensure that no apt-pinning is in place.
– koppor
Mar 18 '17 at 0:29
add a comment |
What seems to have worked for me was
apt-get -f install libc6
apt-get install --only-upgrade apt
answered Sep 17 '16 at 22:51
Willem P. BothaWillem P. Botha
1686
I used this to help with w/ a Mint 17->18 upgrade. These errors seem like false positives.
– Michael Cole
Sep 18 '16 at 19:29
add a comment |
What seems to have worked for me was
apt-get -f install libc6
apt-get install --only-upgrade apt
answered Sep 17 '16 at 22:51
Willem P. BothaWillem P. Botha
1686
I used this to help with w/ a Mint 17->18 upgrade. These errors seem like false positives.
– Michael Cole
Sep 18 '16 at 19:29
add a comment |
What seems to have worked for me was
apt-get -f install libc6
apt-get install --only-upgrade apt
answered Sep 17 '16 at 22:51
Willem P. BothaWillem P. Botha
1686
What seems to have worked for me was
apt-get -f install libc6
apt-get install --only-upgrade apt
answered Sep 17 '16 at 22:51
Willem P. BothaWillem P. Botha
1686
answered Sep 17 '16 at 22:51
Willem P. BothaWillem P. Botha
1686
answered Sep 17 '16 at 22:51
Willem P. BothaWillem P. Botha
1686
answered Sep 17 '16 at 22:51
Willem P. BothaWillem P. Botha
1686
1686
I used this to help with w/ a Mint 17->18 upgrade. These errors seem like false positives.
– Michael Cole
Sep 18 '16 at 19:29
add a comment |
I used this to help with w/ a Mint 17->18 upgrade. These errors seem like false positives.
– Michael Cole
Sep 18 '16 at 19:29
I used this to help with w/ a Mint 17->18 upgrade. These errors seem like false positives.
– Michael Cole
Sep 18 '16 at 19:29
I used this to help with w/ a Mint 17->18 upgrade. These errors seem like false positives.
– Michael Cole
Sep 18 '16 at 19:29
add a comment |
You have to do this:
sudo apt-get install -f
answered Jan 21 '17 at 10:45
flavio.trojaflavio.troja
32913
add a comment |
You have to do this:
sudo apt-get install -f
answered Jan 21 '17 at 10:45
flavio.trojaflavio.troja
32913
add a comment |
You have to do this:
sudo apt-get install -f
answered Jan 21 '17 at 10:45
flavio.trojaflavio.troja
32913
You have to do this:
sudo apt-get install -f
answered Jan 21 '17 at 10:45
flavio.trojaflavio.troja
32913
answered Jan 21 '17 at 10:45
flavio.trojaflavio.troja
32913
answered Jan 21 '17 at 10:45
flavio.trojaflavio.troja
32913
answered Jan 21 '17 at 10:45
flavio.trojaflavio.troja
32913
32913
add a comment |
add a comment |
I also get the "newest version" message, but according to https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1404783/comments/12
I added sources for vivid and vivid-updates to sources.list and installed the apt/vivid version.
sudo apt-get -t vivid install apt/vivid
Then I deleted vivid source from sources.list and apt-get update finished without any warning.
answered Dec 6 '16 at 16:47
RuprechtRuprecht
11
1
apt-getdoesn't have a -t option.
– Elder Geek
Dec 6 '16 at 17:25
It does actually, the -t flag is for --target-release.
– Software_Programineer
Apr 27 '18 at 17:24
add a comment |
I also get the "newest version" message, but according to https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1404783/comments/12
I added sources for vivid and vivid-updates to sources.list and installed the apt/vivid version.
sudo apt-get -t vivid install apt/vivid
Then I deleted vivid source from sources.list and apt-get update finished without any warning.
answered Dec 6 '16 at 16:47
RuprechtRuprecht
11
1
apt-getdoesn't have a -t option.
– Elder Geek
Dec 6 '16 at 17:25
It does actually, the -t flag is for --target-release.
– Software_Programineer
Apr 27 '18 at 17:24
add a comment |
I also get the "newest version" message, but according to https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1404783/comments/12
I added sources for vivid and vivid-updates to sources.list and installed the apt/vivid version.
sudo apt-get -t vivid install apt/vivid
Then I deleted vivid source from sources.list and apt-get update finished without any warning.
answered Dec 6 '16 at 16:47
RuprechtRuprecht
11
I also get the "newest version" message, but according to https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1404783/comments/12
I added sources for vivid and vivid-updates to sources.list and installed the apt/vivid version.
sudo apt-get -t vivid install apt/vivid
Then I deleted vivid source from sources.list and apt-get update finished without any warning.
answered Dec 6 '16 at 16:47
RuprechtRuprecht
11
answered Dec 6 '16 at 16:47
RuprechtRuprecht
11
answered Dec 6 '16 at 16:47
RuprechtRuprecht
11
answered Dec 6 '16 at 16:47
RuprechtRuprecht
11
11
1
apt-getdoesn't have a -t option.
– Elder Geek
Dec 6 '16 at 17:25
It does actually, the -t flag is for --target-release.
– Software_Programineer
Apr 27 '18 at 17:24
add a comment |
1
apt-getdoesn't have a -t option.
– Elder Geek
Dec 6 '16 at 17:25
It does actually, the -t flag is for --target-release.
– Software_Programineer
Apr 27 '18 at 17:24
1
1
apt-get doesn't have a -t option.– Elder Geek
Dec 6 '16 at 17:25
apt-get doesn't have a -t option.– Elder Geek
Dec 6 '16 at 17:25
It does actually, the -t flag is for --target-release.
– Software_Programineer
Apr 27 '18 at 17:24
It does actually, the -t flag is for --target-release.
– Software_Programineer
Apr 27 '18 at 17:24
add a comment |
Here's what worked for me :
sudo rm -r /var/lib/apt/lists/*
sudo apt-get clean
sudo apt-get update
I had segmentation faults errors during the install, so I cleared the archives again:
sudo apt-get clean
And everything went fine.
Hope it'll help !
answered 9 hours ago
madjaouemadjaoue
1012
New contributor
madjaoue 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 |
Here's what worked for me :
sudo rm -r /var/lib/apt/lists/*
sudo apt-get clean
sudo apt-get update
I had segmentation faults errors during the install, so I cleared the archives again:
sudo apt-get clean
And everything went fine.
Hope it'll help !
answered 9 hours ago
madjaouemadjaoue
1012
New contributor
madjaoue 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 |
Here's what worked for me :
sudo rm -r /var/lib/apt/lists/*
sudo apt-get clean
sudo apt-get update
I had segmentation faults errors during the install, so I cleared the archives again:
sudo apt-get clean
And everything went fine.
Hope it'll help !
answered 9 hours ago
madjaouemadjaoue
1012
New contributor
madjaoue is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Here's what worked for me :
sudo rm -r /var/lib/apt/lists/*
sudo apt-get clean
sudo apt-get update
I had segmentation faults errors during the install, so I cleared the archives again:
sudo apt-get clean
And everything went fine.
Hope it'll help !
answered 9 hours ago
madjaouemadjaoue
1012
New contributor
madjaoue 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
madjaouemadjaoue
1012
New contributor
madjaoue 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
madjaouemadjaoue
1012
answered 9 hours ago
madjaouemadjaoue
1012
1012
New contributor
madjaoue is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
madjaoue is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
madjaoue 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%2f760071%2ferrors-upgrading-from-14-04-to-16-04-about-unknown-multi-arch-type-for-compiz-l%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
It looks like those three packages -
libkf5akonadisearch-bin,compiz-core,compiz-gnomehave broken meta data, though it's unclear whether that is so in the old ones or in the new ones. In case it's in the old packages, could you try removing the three temporarily and see if it helps?– Josip Rodin
Jul 9 '16 at 21:18
Also, if it's 16.04 you want, that should be xenial, not wily.
– Josip Rodin
Jul 10 '16 at 9:06
Fwiw, this is not an issue with the installed packages; I get it too, and I don't have any of those packages installed.
– Doug
Jul 13 '16 at 0:39
Agreed with @Doug. None of these packages are installed for me, and I still get the error. Totally stuck.
– sstringer
Aug 25 '16 at 21:01