warnings from apt: W: Unknown Multi-Arch type 'no' for package 'compiz-core'

[Paul Wise (Debian)]

When running apt-get update on Ubuntu vivid I get these warnings:

W: Unknown Multi-Arch type 'no' for package 'compiz-core'
W: Unknown Multi-Arch type 'no' for package 'compiz-gnome'

 affects ubuntu/compiz

--
bye,
pabs

https://wiki.debian.org/PaulWise

[Stephen M. Webb (bregma)]

This appears to be Debian bug #759099 [1] fixed in apt 1.0.7 which should not be occurring in Ubuntu Vivid which provides apt 1.0.9.3ubuntu1. I can not reproduce this problem on any of my local Ubuntu Vivid installations.

Is it possible you have a locally-installed version of the apt package that does not contain the fix for#759099?

[1] ttps://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759099

[Paul Wise (Debian) (pabs)]

On Mon, 2014-12-22 at 13:38 +0000, Stephen M. Webb wrote:

> Is it possible you have a locally-installed version of the apt package
> that does not contain the fix for#759099?

This warning is actually occurring on a Debian wheezy system running the
Debian derivatives census. If you don't want to remove the unnecessary
Multi-Arch field then I suppose I can add a workaround to filter it out.

https://wiki.debian.org/Derivatives/Census

The warnings will also occur when using earlier versions of Ubuntu but
having vivid in sources.list for some specific packages that weren't in
utopic. The warnings will also occur when having a chdist for vivid on
Debian wheezy or Ubuntu utopic.

--
bye,
pabs

https://wiki.debian.org/PaulWise

[Launchpad Janitor (janitor)]

[Expired for compiz (Ubuntu) because there has been no activity for 60 days.]

[Paul Wise (Debian) (pabs)]

 status confirmed

--
bye,
pabs

https://wiki.debian.org/PaulWise

[PeterDaveHello (hsu-8)]

Sorry that I did something wrong here.

[Paul Wise (Debian) (pabs)]

On Sun, 2015-04-26 at 23:20 +0000, PeterDaveHello wrote:

> Sorry that I did something wrong here.
>
> ** Also affects: compiz
> Importance: Undecided
> Status: New
>
> ** Changed in: compiz
> Status: New => Invalid
>

You didn't do anything wrong here until this message.
I expect that you intended to change another bug?

 status confirmed

--
bye,
pabs

https://wiki.debian.org/PaulWise

[Byoungchan Lee (bclee)]

I also get same warnings:

W: Unknown Multi-Arch type 'no' for package 'compiz-core'
W: Unknown Multi-Arch type 'no' for package 'compiz-gnome'
W: Unknown Multi-Arch type 'no' for package 'compiz-core'
W: Unknown Multi-Arch type 'no' for package 'compiz-gnome'
W: You may want to run apt-get update to correct these problems

I'm using Ubuntu 14.04, but, in order to cherry-pick a package from the newer repository, I added the following line in the /etc/apt/source.list
deb http://kr.archive.ubuntu.com/ubuntu/ utopic main restricted universe multiverse

Warnings for apt-get have occurred after I change that line from 'utopic' to 'vivid'. Update for packages have no problem, however It still displays warnings.

I guess that there are several differences from 14.10's repo to 15.04's repo, so apt-get won't interpret well. (Version of apt is 1.0.1ubuntu2)

[Paul Wise (Debian) (pabs)]

I am no longer affected by this bug as the machine where I was having
this issue has been upgraded from Debian wheezy to Debian jessie.

 unsubscribe <email address hidden>

--
bye,
pabs

https://wiki.debian.org/PaulWise

[Pete Phillips (pete-smtl)]

Had this today. I upgraded from 14.04 to 14.10 to 15.04 and somewhere along the line I started getting messages such as

   Errors were encountered while processing:
    cups-client
    printer-driver-postscript-hp
    printer-driver-foo2zjs
    cups-bsd
    cups

and

   W: Unknown Multi-Arch type 'no' for package 'compiz-core'
   W: Unknown Multi-Arch type 'no' for package 'compiz-gnome'
   W: Unknown Multi-Arch type 'no' for package 'compiz-core'
   W: Unknown Multi-Arch type 'no' for package 'compiz-gnome'
   W: You may want to run apt-get update to correct these problems

Unfortunately I didn't document the exact steps I took to resolve the issue, but it was a combination of

    dpkg --configure -a

and

    apt-get install -f

and then going into synaptic and upgrading 'apt' and 'apt-utils'

I then used synaptic (as I was in there) to mark all upgrades, and it wen through (with a fair smattering of warnings) to completion.

I had an error message at the end:

   zram-config there is no script in the new version of the package

but closed that and then re-ran apt-get update, apt-get upgrade - nothing else to install, so rebooted and everything came up OK.

Clearly the apt-get issue identified above was causing a conflict, but a combination of the above sorted it for me. Vivid now running nicely!

[Sebastian Unger (sebunger44)]

This just started happening for me here. I'm on 14.04.2.

[Sebastian Unger (sebunger44)]

Interestingly it only happens the first time I run apt-get dist-upgrade after running apt-get update:

seb@ws3559:~$ sudo apt-get update
....
Fetched 1,581 kB in 9s (167 kB/s)
seb@ws3559:~$ sudo apt-get dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
W: Unknown Multi-Arch type 'no' for package 'compiz-core'
W: Unknown Multi-Arch type 'no' for package 'compiz-gnome'
W: Unknown Multi-Arch type 'no' for package 'compiz-core'
W: Unknown Multi-Arch type 'no' for package 'compiz-gnome'
W: You may want to run apt-get update to correct these problems
seb@ws3559:~$ sudo apt-get dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
seb@ws3559:~$ sudo apt-get dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
seb@ws3559:~$

[Decembry Quentin (qedinux)]

I got the same issue when I added 2 repositories Vivid and Wily

My system is Trusty based and I have set APT::Default-Release "trusty"; in /etc/apt/apt.conf

I fix it by upgrading apt with command

sudo apt-get -t vivid install apt/vivid

[Bill Pechter (pechter)]

Same problem trying to upgrade from trusty to vivid. No work around yet.

[Hoang Tua Nguyen (hoangtua-vn)]

also effects me on trusty

[takiz (takiz)]

>also effects me on trusty
too

[Mark Thornton (mthornton-2)]

It appears to be preventing me from upgrading from 14.04.5 to 16.04.1

[Macro Zhu (zhu-macro)]

It prevents me from upgrading from 14.04.5 to 16.04

[Joerg Kuenstner (jogi-k)]

It also prevents me from upgrading from 14.04.5 to 16.04

[Pavel (ppv)]

These messages are only warnings, not errors. If you check the exit code (echo $?) after "apt-get update", you will see 0. So it is safe to upgrade the distribution despite these warnings. I have myself upgraded from Trusty to Xenial. Sure, it is unpleasant to see such warnings before upgrading of the distribution and it would be great if apt 1.0.7 or newer were backported to Trusty.

[Seán Ó Séaghdha (seanos)]

This appears to be preventing me from fixing broken packages in Synaptic after failed 14.04 -> 16.04.3 upgrade. I still haven’t entirely figured that one out, the only clue being where it seemed to fail:

2017-12-20 13:43:58,269 ERROR got an error from dpkg for pkg: '/var/cache/apt/archives/ppp_2.4.7-1+2ubuntu1_amd64.deb': 'subprocess new pre-installation script returned error exit status 1'