Conflicts with amd64-microcode

Bug #1112423 reported by Removed by request
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
linux-firmware (Ubuntu)
Fix Released
Medium
Tim Gardner
Raring
Fix Released
Medium
Tim Gardner

Bug Description

On my system amd64-microcode is installed and on upgrading linux-firmware to version 1.100 I'm getting the following error:

sworddragon@ubuntu:~$ sudo apt-get dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
  linux-firmware
1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/21.1 MB of archives.
After this operation, 815 kB of additional disk space will be used.
Do you want to continue [Y/n]?
debconf: delaying package configuration, since apt-utils is not installed
(Reading database ... 90931 files and directories currently installed.)
Preparing to replace linux-firmware 1.99 (using .../linux-firmware_1.100_all.deb) ...
Unpacking replacement linux-firmware ...
dpkg: error processing /var/cache/apt/archives/linux-firmware_1.100_all.deb (--unpack):
 trying to overwrite '/lib/firmware/amd-ucode/microcode_amd_fam15h.bin', which is also in package amd64-microcode 1.20120910-2
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Errors were encountered while processing:
 /var/cache/apt/archives/linux-firmware_1.100_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

Maybe linux-firmware should remove amd64-microcode if it is already included.

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

You may need to run the following:

sudo apt-get install -f
sudo apt-get clean
sudo apt-get update

Then re-install the package.

If that does not resolve your issue, please mark the bug as "Confirmed"

Changed in linux-firmware (Ubuntu):
importance: Undecided → Medium
tags: added: kernel-da-key
Changed in linux-firmware (Ubuntu):
status: New → Incomplete
Revision history for this message
Removed by request (removed3425744) wrote :

This doesn't work but theoretically I have just to remove amd64-microcode to get all working again. But this is not the main problem. I'm wondering why linux-firmware doesn't declare to remove amd64-microcode in its control file.

Changed in linux-firmware (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Tim Gardner (timg-tpi) wrote :

amd64-microcode was never part of the Ubuntu archive. Therefore, no Conflicts statements in the control file.

Changed in linux-firmware (Ubuntu):
status: Confirmed → Invalid
Revision history for this message
Removed by request (removed3425744) wrote :

http://packages.ubuntu.com/raring/ is listing amd64-microcode as a package in the Ubuntu archive.

Changed in linux-firmware (Ubuntu):
status: Invalid → New
Tim Gardner (timg-tpi)
Changed in linux-firmware (Ubuntu Raring):
assignee: nobody → Tim Gardner (timg-tpi)
status: New → In Progress
Tim Gardner (timg-tpi)
Changed in linux-firmware (Ubuntu Raring):
status: In Progress → Fix Committed
Revision history for this message
pqwoerituytrueiwoq (pqwoerituytrueiwoq) wrote :

if the fix was committed, why did linux-firmware not try to remove amd64 microcode when i updated this laptop today (long over due, but it had not been on), it is running raring 64bit xubuntu

Revision history for this message
Removed by request (removed3425744) wrote :

The fix was commited but not released. You have to wait a little more until the fix is in the repository.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package linux-firmware - 1.102

---------------
linux-firmware (1.102) raring; urgency=low

  * Updated asihpi firmware from http://www.audioscience.com/internet/download/drivers/released/v4/08/00/hpklinux-4.08.00.tar.bz2
    -LP: #1122377
 -- Tim Gardner <email address hidden> Tue, 12 Feb 2013 05:47:25 -0700

Changed in linux-firmware (Ubuntu Raring):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.