This bug was fixed in the package fwupd-signed - 1.27.1ubuntu7
---
fwupd-signed (1.27.1ubuntu7) focal; urgency=medium
* remove fwupd-unsigned from the Recommends of fwupd-signed.
This is backported from v1.43 (LP: #1960783)
-- Yuan-Chen Cheng Wed, 16 Feb 2022 19:14:12
+0800
This bug was fixed in the package fwupd-efi - 1:1.2-2~20.04.1
---
fwupd-efi (1:1.2-2~20.04.1) focal; urgency=medium
[ Yuan-Chen Cheng ]
* Upload as par of the new fwupd 1.7 serie SRU, needed for hardware
as the Dell's new Atomic Docking and WD22TB4 (lp: #1949412).
* change
This bug was fixed in the package fwupd - 1.7.5-3~20.04.1
---
fwupd (1.7.5-3~20.04.1) focal; urgency=medium
* Backport 1.7.5-3 from jammy to focal.
* Support several new devices (LP: #1949412, LP: #1954965, LP: #1953573)
* fwupd / fwupd-efi source package split (LP: #1955386)
This bug was fixed in the package fwupd - 1.7.5-3~21.10.1
---
fwupd (1.7.5-3~21.10.1) impish; urgency=medium
* Backport 1.7.5-3 from jammy to impish.
* Support several new devices (LP: #1949412, LP: #1954965, LP: #1953573)
* fwupd / fwupd-efi source package split (LP: #1955386)
This bug was fixed in the package fwupd-efi - 1:1.2-2~21.10.1
---
fwupd-efi (1:1.2-2~21.10.1) impish; urgency=medium
[ Yuan-Chen Cheng ]
* Upload as par of the new fwupd 1.7 serie SRU, needed for hardware
as the Dell's new Atomic Docking and WD22TB4 (lp: #1949412).
* change
One worrying thing we discussed today with YuanChen Cheng about the
fwupd situation is the fact of an unversioned dependency on libjcat1
right now. I am a bit concerned that there is no versioned dep in
neither of the packages, meaning that some users might only upgrade
fwupd but not libjcat1 and
** Attachment removed: "dell-embargo.conf"
https://bugs.launchpad.net/oem-priority/+bug/1949412/+attachment/5566398/+files/dell-embargo.conf
** Changed in: oem-priority
Status: In Progress => Confirmed
** Changed in: oem-priority
Status: Confirmed => Fix Committed
--
You
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1949412
Title:
Upgrade fwupd for Atomic Docking Support
To manage notifications
test on impish, install fwupd/libjcat1 from focal proposed channel.
fwupd: 1.7.5-3~21.10.1
libjcat1: 0.1.4~0ubuntu0.21.10.1
put the dell-embargo.conf to /etc/fwupd/remote.d
$ fwupdmgr enable-remote dell-embargo
$ sudo fwupdmgr update
upgrade Atomic docking fw: passed
Devices that have been
test on jammy, install fwupd/libjcat1 from focal proposed channel.
secure boot on
1. upgrade install nvme fw from snap-store: passed
2. upgrade os bios cab from the command line: passed
3. upgrade os bios from gnome-software: passed
4. AI: upgrade WD19SC FW.
5. AI: upgrade Atomic docking fw.
--
dirk test install local cab for wd22tb4 and atomic docking with fwupd
from the proposed channel, and it test passed.
I also run the fwupd-tests old/new version and both passed.
Given all above, mark verification-done-focal.
** Tags removed: verification-needed-focal
** Tags added:
on focal, with the fwupd/fwupd-signed in the proposed channel, test
passed on the following items:
1. upgrade OS bios from snap-store: passed
2. reinstall firmware of WD19, a NVME module: passed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
on focal, target machine: Latitude 5300, with the fwupd/fwupd-signed in
the proposed channel, secure boot on, reinstall system bios, test
passed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1949412
for focal, fwupd dbus 1.7.5 interface change compare to existing 1.5.11. It
looks fine per
previously test criteria we define in the SRU exception.
$ diff -u fwupd-dbus-1.5.11.log fwupd-dbus-1.7.5.log
--- fwupd-dbus-1.5.11.log 2022-03-02 06:31:45.690734046 +0800
+++ fwupd-dbus-1.7.5.log
** Description changed:
This is to support Dell's new Atomic Docking and WD22TB4 in focal.
- As fwupd 1.7.x efi splie is done, let use 1.7.5 for this.
+ As fwupd 1.7.x efi split is done, let use 1.7.5 for this.
In this SRU, it include source package: fwupd-efi, fwupd, fwupd-signed and
** Description changed:
This is to support Dell's new Atomic Docking and WD22TB4 in focal.
- As fwupd 1.7.x efi splie is done, let use 1.7.4 for this.
+ As fwupd 1.7.x efi splie is done, let use 1.7.5 for this.
+
+ In this SRU, it include source package: fwupd-efi, fwupd, fwupd-signed and
+
** Changed in: fwupd (Ubuntu Focal)
Milestone: ubuntu-20.04.4 => focal-updates
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1949412
Title:
Upgrade fwupd for Atomic Docking Support
To manage
Steve and Mario, I create another bug for not install fwupd-unsigned in
lp:1960783
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1949412
Title:
Upgrade fwupd for Atomic Docking Support
To manage
per test, if fwupd-unsigned is not installed, then re-install bios will
be failed if secure boot is not turned on.
We need a patch around
https://github.com/fwupd/fwupd/blob/main/plugins/uefi-capsule/fu-uefi-
common.c#L89
--
You received this bug notification because you are a member of Ubuntu
Yeah that still works, and is exactly why it should remain a Recommends.
You should be able to have SB off, apt install fwupd and have it work
for UEFI updates.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@Mario, the annoying means: we still can ask the one who did the testing
to manually install fwupd-unsigned and turned off secure to do the
testing. This is still working if we need to use the non-signed EFI,
right?
--
You received this bug notification because you are a member of Ubuntu
Bugs,
In theory it sounds harmless, but in practice there was a long period of
time that shim chainloading to fwupd was broken in Ubuntu.
If we didn't have that codepath available to use the non-signed EFI
package without chainloading through shim there wouldn't have been a
workaround to install
IMO, use the signed one as the secure boot disable seems harmless.
However, that makes it a little annoying in the development phase (ex:
share build in PPA) if we have fwupd / fwupd-efi version dependency in
the future.
If we won't have version dependency between the two binary for good, it
I notice Steve just uploaded to Jammy a change that removes the
Recommends.
I don't really understand why; IMO it really should be a Recommends.
- If you have secure boot disabled you use the binary provided by
fwupd-unsigned.
- If you have secure boot enabled you use the binary provided by
Guess Steve means we need to explicitly tell the SRU team that they need
to copy fwupd-unsiged into main in the first place we do SRU.
It is just something that nobody has the whole picture and things just
happen at the same time maybe.
--
You received this bug notification because you are a
That's a side effect of the fwupd/fwupd-efi split.
It truly is optional in the version that YC is doing the SRU. The daemon
will check for the EFI binary existing at the time of installing a
firmware update (either signed or unsigned depending upon
circumstances) and will issue an error message
The SRU of fwupd adds a new Recommends on fwupd-unsigned which is
incorrect. The incorrect added package relationship was detected
because the package in focal-proposed is in universe and this causes an
image build failure; but while fwupd-unsigned should be promoted to main
as it is in jammy, it
Hello Yuan-Chen, or anyone else affected,
Accepted fwupd into focal-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/fwupd/1.7.4-1~20.04.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Yuan-Chen, or anyone else affected,
Accepted fwupd-efi into focal-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/fwupd-
efi/1:1.2-2~20.04.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package. See
Hello Yuan-Chen, or anyone else affected,
Accepted fwupd-efi into impish-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/fwupd-
efi/1:1.2-2~21.10.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package. See
** Changed in: fwupd (Ubuntu Focal)
Milestone: None => ubuntu-20.04.4
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1949412
Title:
Upgrade fwupd for Atomic Docking Support
To manage
I've uploaded the packages in the SRU queue for impish now
Let's start with that serie to check how the SRU team feels about the
updates and get some testing before uploading for the LTS.
Wontfixing for hirsute as it's not likely we will SRU to that serie now
** Changed in: fwupd-signed (Ubuntu
fwupd dbus 1.7.3 interface change compare to 1.5.11. It looks fine per
previously test criteria we define in the SRU exception.
$ diff -u fwupd-dbus-1.5.11.log fwupd-dbus-1.7.3.log
--- fwupd-dbus-1.5.11.log 2022-01-28 13:02:17.288157828 +0800
+++ fwupd-dbus-1.7.3.log2022-01-28
** Description changed:
This is to support Dell's new Atomic Docking.
Plan to still use 1.5.x branch given the tight schedule.
It's time we start to work on upgrading to 1.7.x and splitting its EFI
source package.
[Impact]
- * Several components that are used in OEM
** Description changed:
This is to support Dell's new Atomic Docking.
Plan to still use 1.5.x branch given the tight schedule.
It's time we start to work on upgrading to 1.7.x and splitting its EFI
source package.
+
+ [Impact]
+
+ * Several components that are used in OEM
Note on SRU:
1. shall we also SRU libjcat from jammy to focal/impish?
fwupd is the only consumer of libjcat. For now, there is no
major bug needed also to SRU libjcat, however, it seems
better also to SRU it so that we have consistent behaviors.
2. Per what I know, we'd like to use the
note that the deb in the #15 ppa got positive test results with atomic
docking and wd22tb.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1949412
Title:
Upgrade fwupd for Atomic Docking Support
To
fwupd 1.7.4 ppa:
https://launchpad.net/~ycheng-twn/+archive/ubuntu/fwupd174
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1949412
Title:
Upgrade fwupd for Atomic Docking Support
To manage
Will do, but maybe a little bit latter, so I won’t kill myself XD
Thank you for your notice.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1949412
Title:
Upgrade fwupd for Atomic Docking Support
#11:
I think you'll want to update it to 1.7.4 which is in Jammy now so to keep them
the same at least for now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1949412
Title:
Upgrade fwupd for
fwupd-signed from the jammy-update archive.
** Attachment added: "fwupd-signed_1.42+1.1-3_amd64.deb"
https://bugs.launchpad.net/oem-priority/+bug/1949412/+attachment/072/+files/fwupd-signed_1.42+1.1-3_amd64.deb
--
You received this bug notification because you are a member of Ubuntu
first ppa for focal and impish.
https://launchpad.net/~ycheng-twn/+archive/ubuntu/fwupd-17x-v2
Note:
1. No plan to prepare deb for hirsute
2. if you want to test secure boot, install fwupd-signed from jammy.
I kind of believe we will copy the fwupd-signed binary from jammy
to focal and
Fixed in Jammy by the 1.7.1 upgrade.
** Changed in: fwupd (Ubuntu Jammy)
Status: Fix Committed => Fix Released
** Changed in: fwupd-signed (Ubuntu Jammy)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
we need 1.6 in focal per lp:1954965.
I don't think we'd like such version diversity. Let's also SRU 1.7.x
back to focal.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1949412
Title:
Upgrade fwupd
some said other OEM project need 1.7.x on focal. Wait a bit for details
to come.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1949412
Title:
Upgrade fwupd for Atomic Docking Support
To manage
per request by the customer, we'd like to support the atomic docking in
focal by using fwupd 1.5.13
AI: wait 1.7.x land in jammy.
plus
Plan 1:
- land 1.5.13 in impish.
- SRU 1.5.13 in focal.
OR
Plan 2:
- SRU 1.7.X in impish.
- SRU 1.7.X in focal.
If we want to use the same fwupd-efi binary
The new fwupd and fwupd-efi have been uploaded to jammy now
** Changed in: fwupd (Ubuntu Jammy)
Importance: Undecided => High
** Changed in: fwupd (Ubuntu Jammy)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
for the record, for today:
1. debian sid: 1.5.7
2. upstream: 1.7.2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1949412
Title:
Upgrade fwupd for Atomic Docking Support
To manage notifications
@Yuan, right, I'm going to wait until december and upload to Ubuntu if
there is no update
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1949412
Title:
Upgrade fwupd for Atomic Docking Support
To
Just found that they don't really need SRU fwupd to support new docking
very soon.
IMHO, If Debian didn't land 1.7.x in unstable before a certain day, then
Ubuntu should just go land it so it's available in 22.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Specifically staged here:
fwupd-efi: https://salsa.debian.org/efi-team/fwupd-efi/-/tree/debian/unstable
fwupd: https://salsa.debian.org/efi-team/fwupd
The packaging should be ready for both Debian and Ubuntu, but has been
intentionally waiting to upload to Ubuntu until it can be sponsored into
51 matches
Mail list logo
