PPA for fwupd 1.2.10.
https://launchpad.net/~ycheng-twn/+archive/ubuntu/fwupd-1.2.10-1
Beware that it add an upstream patch debian/patches/disable-cert-time-
check-in-self-test.patch. Without it, both 1.2.5 and 1.2.10 won't build
today.
--
You received this bug notification because you are a me
** Summary changed:
- [SRU] support new cab and new docking firmware upgrade in fwupd 1.2.5
+ [SRU] support new cab and new docking firmware upgrade in fwupd 1.2.5/1.2.10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.la
I'm unclear on the specifics goals required in terms of fwupdate compatibility
during this transition.
1) 1 signed EFI binary in bionic?
2) Command line compatibility?
3) Other?
Steve, can you and/or Lukasz please clarify.
Currently in bionic:
1. fwupdate provides /usr/bin/fwupdate which is a co
** Description changed:
* Impact
Bios vendor is pushing to put the new design into cab file, and also new
docking DW19 needs the new fwupd to support it.
That needs new fwupd to support.
+
+ * Background:
+ 1. most user does firmware update via gnome-software and it talk to fwup
libxmlb is accepted now into -proposed which is ok, and fwupd-signed has
also been accepted into -proposed but is dep-wait because the
corresponding fwupd has not yet been accepted, so this is also ok
(though the accepting of fwupd-signed may have been an accident).
Accepting fwupd is BLOCKED unti
Hello Yuan-Chen, or anyone else affected,
Accepted libxmlb into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/libxmlb/0.1.8-1~ubuntu18.04.1 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Per information from Mario, we need the new fwupd efi app from the new
fwupd. However it's not compatiable with existing fwupdate. That's how
fwupd break fwupdate.
new fwupd does provide compatiable command, which live in
/usr/lib/fwupd/fwupdate.
--
You received this bug notification because you
Per information from Mario, we need the new fwupd efi app from the new
fwupd. However it's not compatiable with existing fwupdate. That's how
fwupd break fwupdate.
new fwupd does provide compatiable command, which live in
/usr/lib/fwupd/fwupdate.
--
You received this bug notification because you
this sru will break fwupdate package in bionic/main. However fwupdate is
in disco/universe.
Given that, maybe we shall go a clean break.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1820768
Title:
Per comment #8 and #9, #12
I would like to clarify that the way it works with newer fwupd is that
the binary is installed into the EFI system partition dynamically as
needed rather than at install time. This means that only people that
are performing firmware upgrades would have the file installe
** Changed in: oem-priority
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1820768
Title:
[SRU] support new cab and new docking firmware upgrade in fwupd 1.2.5
** Description changed:
* Impact
Bios vendor is pushing to put the new design into cab file, and also new
docking DW19 needs the new fwupd to support it.
That needs new fwupd to support.
* Test case
I
1. install the new fwupd, and plugin the new docking - DW19.
2. fwupd
for #8, in disco, after using "fwupdmgr install xxx.cab", fwupdx64.efi
does been installed in /boot/efi/EFI/ubuntu.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1820768
Title:
[SRU] support new cab
A firmware download from lvfs is in cab format.
We can use the command "fwupdmgr install [--allow-reinstall] file.cab",
and a reboot to install it. [it could brick your computer, don't do it
unless you have someone to save you.]
fwupd 1.0.9-0ubuntu2
libfwupd2:amd64 1.0.9-0ubuntu2
There is not li
A firmware download from lvfs is in cab format.
We can use the command "fwupdmgr install [--allow-reinstall] file.cab",
and a reboot to install it. [it could brick your computer, don't do it
unless you have someone to save you.
fwupd1.0.
per check apt-cache show fwupd / fwupd-signed, I didn't find any
conflict and break on fwupdate.
So maybe the transition is done by other methods per upgrade path from
bionic to disco.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
h
per doing some investigation:
in bionic,
fwupdate-signed: /usr/lib/fwupdate/fwupx64.efi.signed
fwupdate: /usr/lib/fwupdate/fwupx64.efi
and there install script will install them to /boot/efi/EFI/ubuntu/
in disco, it becomes
fwupd-signed: /usr/lib/fwupd/efi/fwupdx64.efi.signed
fwupd: /usr/lib/f
** Tags added: oem-priority
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1820768
Title:
[SRU] support new cab and new docking firmware upgrade in fwupd 1.2.5
To manage notifications about this bug
an archive admin should review all of these at the same time, since
libxmlb/fwupd-signed are in source NEW
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1820768
Title:
[SRU] support new cab and new
** Summary changed:
- [SRU] support new cab and new docking firmware upgrade in version 1.2.5
+ [SRU] support new cab and new docking firmware upgrade in fwupd 1.2.5
** Tags added: originate-from-1806857
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
20 matches
Mail list logo
