Ubuntu
fwupdate-signed package

fwupdate-signed: arch-qualified package names, but not coinstallable

Bug #1559578 reported by Steve Langasek
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
fwupdate-signed (Ubuntu)
Fix Released
Medium
Mario Limonciello

Bug Description

The fwupdate-signed source package produces binary packages that each have the architecture name: fwupdate-{amd64,arm64,armhf,i386}-signed. However, unlike in the case of grub, these binary packages are not coinstallable, as each contains the file /usr/lib/fwupdate/version.

Given this, I don't see any reason to have the architecture name in the package name. I would suggest renaming all the binary packages to 'fwupdate-signed' instead.

Since the fwupdate-amd64-signed binary package was already in the archive, I didn't consider this a blocker for binary NEW and have let the others in. A resolution for this bug should include appropriate transition handling for all architectures.

Steve Langasek (vorlon)
Changed in fwupdate-signed (Ubuntu):
importance: Undecided → Medium
Revision history for this message
Mario Limonciello (superm1) wrote :

Before doing this transition, I just want to confirm it's the correct approach to take.

Maintaining the ability to be co-installable would seem appealing in the event that you are running on a 64 bit architecture with a 32 bit EFI implementation for example.

So yes, currently they all contain /usr/lib/fwupdate/version, but I don't think there is actually a reason to include this in all of the binary packages. To my knowledge this information is not used by any other packages. A matter of fact the same information can be found in the version field of the package.

 Version: 1.8+0.5-2ubuntu2

What do you think about just removing the version file?

Revision history for this message
Mario Limonciello (superm1) wrote :

I just looked into this a bit further and fwupdate itself isn't actually co-installable, so I think your approach is right. I've done this in the 1.9 upload.

Changed in fwupdate-signed (Ubuntu):
status: New → Fix Committed
assignee: nobody → Mario Limonciello (superm1)
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package fwupdate-signed - 1.11

---------------
fwupdate-signed (1.11) xenial; urgency=medium

  * Really build depends on 0.5-2ubuntu4

 -- Mario Limonciello <email address hidden> Sun, 20 Mar 2016 18:33:07 -0500

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

Other bug subscribers

Remote bug watches

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