a300_[pfp|pm4].fw clashes when installing linux-firmware
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux-firmware (Ubuntu) |
Fix Released
|
Medium
|
Seth Forshee | ||
Xenial |
Fix Released
|
Medium
|
Seth Forshee | ||
Artful |
Fix Released
|
Medium
|
Seth Forshee | ||
linux-firmware-snapdragon (Ubuntu) |
Fix Released
|
Medium
|
Paolo Pisati | ||
Xenial |
Fix Released
|
Medium
|
Paolo Pisati | ||
Artful |
Fix Released
|
Medium
|
Paolo Pisati |
Bug Description
[Impact]
Starting with linux-firmware 1.157.13, two files (a300_[pfp|pm4].fw) that were previously part of linux-firmware-
..
Selecting previously unselected package linux-firmware-
Preparing to unpack .../linux-
Unpacking linux-firmware-
dpkg: error processing archive
/var/cache/
(--unpack):
trying to overwrite '/lib/firmware/
package linux-firmware 1.157.13
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Selecting previously unselected package linux-image-
Preparing to unpack .../linux-
Unpacking linux-image-
Errors were encountered while processing:
/var/cache/
E: Sub-process /usr/bin/dpkg returned an error code (1)
make: *** [all] Error 100
...
This problem is particularly evident when a new snapdragon kernel snap is assembled, since the the building process breaks (and no kernel snap is generated):
To fix the problem i removed the two files from linux-firmware-
https:/
linux-firmware-
[Test case]
Try to build a snapdragon kernel snap using Xenial/updates - with linux-firmware 1.157.13 and linux-firmware-
[Regression risk]
The files imported in linux-firmware are the same files we
shipped in linux-firmware-
$ md5sum /lib/firmware/
25aa81977303142
$ md5sum /lib/firmware/
d657cacd951742d
$ md5sum dragon410c-
25aa81977303142
$ md5sum dragon410c-
d657cacd951742d
so the regression risk is very low.
CVE References
Changed in linux-firmware (Ubuntu): | |
assignee: | nobody → Seth Forshee (sforshee) |
importance: | Undecided → Medium |
status: | New → In Progress |
Changed in linux-firmware (Ubuntu Xenial): | |
assignee: | nobody → Seth Forshee (sforshee) |
importance: | Undecided → Medium |
status: | New → In Progress |
Changed in linux-firmware (Ubuntu Artful): | |
assignee: | nobody → Seth Forshee (sforshee) |
importance: | Undecided → Medium |
status: | New → In Progress |
Changed in linux-firmware-snapdragon (Ubuntu): | |
assignee: | nobody → Paolo Pisati (p-pisati) |
importance: | Undecided → Medium |
status: | New → In Progress |
Changed in linux-firmware-snapdragon (Ubuntu Xenial): | |
assignee: | nobody → Paolo Pisati (p-pisati) |
importance: | Undecided → Medium |
status: | New → In Progress |
Changed in linux-firmware-snapdragon (Ubuntu Artful): | |
assignee: | nobody → Paolo Pisati (p-pisati) |
importance: | Undecided → Medium |
status: | New → In Progress |
Changed in linux-firmware (Ubuntu Xenial): | |
status: | In Progress → Fix Committed |
Changed in linux-firmware (Ubuntu Artful): | |
status: | In Progress → Fix Committed |
What we have is scenario #9 from https:/ /wiki.debian. org/PackageTran sition, which means linux-firmware- snapdragon needs a "Breaks: linux-firmware (<= ...)" and linux-firmware needs "Breaks: linux-firmware- snapdragon (<= ...) Replaces: linux-firmware- snapdragon (<= ...)".