failed to install quantal-core-armhf_default(20120921): some packages(mountall:amd64, upstart:amd64, iproute:amd64) have have unmet dependencies
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu |
Fix Released
|
High
|
Unassigned | ||
Quantal |
Fix Released
|
High
|
Unassigned |
Bug Description
Link to the test:
https:/
Error:
E: Some index files failed to download. They have been ignored, or old ones used instead.
Reading package lists...
Building dependency tree...
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:
mountall:amd64 : Depends: plymouth:amd64 but it is not going to be installed
upstart:amd64 : Depends: libc6:amd64 (>= 2.9) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
Reading package lists...
Building dependency tree...
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:
iproute:amd64 : Depends: libc6:amd64 (>= 2.14) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
done
Generating LXC configuration lxc.cfg
Copying rc.local
I'm not sure which package should I choose for this bug, but I found some similar issue with lxc chosen, so I just use lxc first here.
if you know the exact answer, feel free to change it.
Very unlikely to be lxc. I'm just moving this to Ubuntu for now so that it gets off the server team's list.
This could well be transient, since multiarch routinely gets upset during development cycles while packages are out of sync; this isn't a problem after release. Still needs investigation to confirm that though.