** 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.
+ docking WD19 needs the new fwupd to support it.
That needs new fwupd to support.
* Background:
1. most user does firmwar
** Changed in: oem-priority
Status: Fix Committed => Fix Released
--
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
This bug was fixed in the package fwupd - 1.2.10-1ubuntu2~ubuntu18.04.3
---
fwupd (1.2.10-1ubuntu2~ubuntu18.04.3) bionic; urgency=medium
* d/p/0001-dont-semver-conversion.patch, d/p/0001-version-handling.patch
d/p/0001-plain_support_in_version.patch:
backport regression fix
This bug was fixed in the package libxmlb - 0.1.8-1~ubuntu18.04.1
---
libxmlb (0.1.8-1~ubuntu18.04.1) bionic; urgency=medium
* Upload of libxmlb to bionic, it's needed to update fwupd to the
current upstream version (lp: #1820768)
* debian/patches/old_meson_build.patch:
-
This bug was fixed in the package fwupd-signed - 1.10~ubuntu18.04.3
---
fwupd-signed (1.10~ubuntu18.04.3) bionic; urgency=medium
* Upload to bionic, Build-Depends on the current fwupd version
(LP: #1820768)
-- Łukasz 'sil2100' Zemczak Tue, 21 Jan
2020 17:37:35 +0100
** Chan
This bug was fixed in the package fwupdate - 12-7~ubuntu18.04.3
---
fwupdate (12-7~ubuntu18.04.3) bionic; urgency=medium
* control: Drop Breaks on libfwup{1,-dev}. (LP: #1820768)
-- Timo Aaltonen Thu, 19 Dec 2019 19:33:29 +0200
--
You received this bug notification because you
per test 1.2.10-1ubuntu2~ubuntu18.04.3, with stock ubuntu and oem ubuntu
image, fwupd upgrading with update-manager work perfetctly.
the version also can properly get thunderbolt docking information.
"fwupdmgr install XX.cab" also works fine here.
Given that, mark verified done.
** Tags removed
saninty check for 1.2.10-1ubuntu2~ubuntu18.04.3 passed.
1. downgrade to the previous bios via capsule file locally
2. upgrade to the latest bios version via online LVFS
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
per test 1.2.10-1ubuntu2~ubuntu18.04.3, it fix the regression mentioned
in #60.
Will to saninty check for other test cases very soon.
--
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:
[S
sorry for the noise, it's a problem on my system which is a kde neonized
ubuntu where the ID in /etc/os-release is set to neon. once switching
back to ubuntu fwupd worked...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.
I installed fwupd and fwupd-signed from -proposed and removed fwupdate
as a update for my bios is available I would like to upgrade but:
$ fwupdmgr update
Downloading 0.2.13.0 for XPS 13 9360 System Firmware...
Decompressing… [***]
Authenticating…
@sil2100, Most of us still taking the Chinese New Year Holidays. I
believe this can be verified in the first two days of next week. Let me
know if you do need it earlier than that.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:
Can we get this verified for bionic? 18.04.4 is nearing, so I'd like to
move as many things from -proposed to -updates as possible.
--
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]
right, my mistake.. I've recovered the upload from the rejected queue
and accepted
--
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
@Timo: Is that true even when the subsequent proposed upload merges all
changes into the same package version?
--
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
upload 1.2.10-1ubuntu2~ubuntu18.04.3~oem2 to the ppa in #61,
add patch:
https://github.com/fwupd/fwupd/commit/a5df5b0e20726985cc971bfdb6f3872cf387f258
to clean up fwupdate files.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:
version 1.2.10-1ubuntu2~ubuntu18.04.3~oem1 in ppa https://launchpad.net
/~ycheng-twn/+archive/ubuntu/fwupd-1.2.10-p3 fix the regression on #60.
The three patches is backported and merged in the upstream 1.2.X branch.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
regression: https://github.com/fwupd/fwupd/issues/1675
** Bug watch added: github.com/fwupd/fwupd/issues #1675
https://github.com/fwupd/fwupd/issues/1675
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
I verified following functions in fwupd 1.2.10 on Dell Latitude 5300:
`sudo fwupdmgr refresh`: Could connect to remote server and update metadata.
u@u-Latitude-5300:~$ sudo fwupdmgr refresh
[sudo] password for u:
Fetching metadata https://cdn.fwupd.org/downloads/firmware.xml.gz
Downloading…
On Tue, Dec 17, 2019 at 09:00:13PM -, Mario Limonciello wrote:
> I think that leaves two options then:
> 1) Remove unversioned Breaks: fwupdate-signed from fwupdate source package,
>convert fwupdate-signed into transition package in Ubuntu as part of this
> SRU.
> 2) Change unversioned Bre
for D-5 verification:
/var/cache/fwupdate is removed. Maybe that's because I install the
machine from the iso image, and do the upgrade without using it.
/var/lib/fwupdate have a empty file 'done' still left behind.
/boot/efi/EFI/ubuntu does have the fwupx64.efi left behind.
--
You received thi
per
fwupdate 12-7~ubuntu18.04.3
fwupd 1.2.10-1ubuntu2~ubuntu18.04.2
fwupd-signed 1.10~ubuntu18.04.2+1.2.10-1ubuntu2~ubuntu18.04.2
from the proposed channel, I can properly upgrade to it per stuck bionic
and oem bionic image.
test case C also works perfectly.
TODO: test case A, B.
TODO: test cas
Not sure we need Steve or someone else can just help on the version
issue below.
The new fwupdate work perfectly on stock ubuntu even use update-manager.
In oem image, we released packages with version
fwupd: 1.2.5-1~somerville1
fwupd-signed: 1.6+1.2.5-1~somerville1+1.2.5-1ubuntu1
libfwupd2:amd6
The transitional fwupdate-signed is definitely needed, since all the
desktop metapackages Recommend it and the image build fails due to the
breaks. I've uploaded a new version with the preinst cleanup modified as
on gitlab, it looks fine to me.
--
You received this bug notification because you ar
comment 30 is handle in another bug LP: #1856896. Per Robert, he upload
another version to bionic queue.
--
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 do
Here is the revised preinst that should cover the different problems outlined:
https://salsa.debian.org/efi-team/fwupdate/commit/85533b1f392399ee53f88e71091044a69dabbdc4
It hasn't yet been uploaded to unstable, would like to align the correct
thing to do with breaks/conflicts first and do upload w
> /boot/efi/EFI/ubuntu
'Yes, looks like that was missed in the conversion to a transition package.
It used to be cleaned up like this:
https://salsa.debian.org/efi-team/fwupdate/commit/b4daba89c567d4cf52f5deaab1ea2ee13039d03f#d0f1e7a780c0b1a978596fc9585a70ce84d2602d
I think we can bring that exa
I've tested an apt upgrade on a chroot, and I see that fwupx64.efi is
indeed left behind in /boot/efi/EFI/ubuntu, just like on my laptop
install (eoan).
So that'd need to be fixed in fwupdate preinst like the other cleanups?
And in focal/eoan too..
--
You received this bug notification because y
per test again today with stock ubuntu image, it behaves differently
from oem image.
On the update-manager, there will be two button 'Continue' and 'Partial Upgrade'
(check attached picture)
I click Continue first, it does not install any package that's related to fwupd.
After that, the windows w
Just manage to do a quick test on case D and it does fail.
Need some work based on #32 to make it work.
** Tags removed: verification-needed-bionic
** Tags added: erification-failed-bionic
** Tags removed: erification-failed-bionic
** Tags added: verification-failed-bionic
--
You received this
On Mon, Dec 16, 2019 at 02:54:12AM -, Mario Limonciello wrote:
> Archive administrator needs to release UEFI archives.
Sorry, this was actually stuck in the NEW queue because of the
"signed-template" packages (which are unused in Ubuntu). I've accepted
these now.
The fwupd-signed package sho
Archive administrator needs to release UEFI archives.
--
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.10
To manage n
@Steve, not sure what went wrong, the archive seems not properly update.
$ rmadison fwupd-signed | grep bionic
fwupd-signed | 1.2~ubuntu18.04.1 | bionic-proposed | source
$ rmadison fwupd | grep bionic
fwupd | 1.0.6-2 | bionic | source, amd64,
arm64, armhf,
#37: need to check.
#38: please check #13. Shall be fine. Will still test again.
** Changed in: oem-priority
Status: Triaged => 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
$ ls -l /boot/efi/EFI/ubuntu/fwup*
-rwxr-xr-x 1 root root 71400 Mar 21 2018 /boot/efi/EFI/ubuntu/fwupx64.efi
$
Is this a bug that I don't have any newer EFI executable from fwupd
copied to my ESP?
I think it *is* a bug that the binary from fwupdate has not been removed
on upgrade.
** Descriptio
Additionally I notice that on my eoan system which has been continuously
upgraded, I have both a /var/lib/fwupdate and a /var/cache/fwupdate
directory left behind. Something should be taking care of cleaning
these directories up on upgrade. Since the fwupdate transitional
package in later release
Sorry, I was looking at a wrong path in the diff and it seems the tpm2-*
Recommends: are only present in contrib/debian/control.in, not in
debian/control.in. So that was done correctly and doesn't need
changing. I'll still be dropping the Recommends: on bolt however.
--
You received this bug no
I have added an explicit test case for the packaging changes, since that
is a large part of why this SRU has taken as long to sort out - we need
to ensure that the package upgrades work correctly.
This test case uses update-manager, and NOT apt-get, because the
behavior is different between the tw
** 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 fwupd.
@Timo and Steve, for the patch in #30, I simply put the commit in
debian/patch and modify series, then it can be perperly built.
The testing ppa build is in https://launchpad.net/~ycheng-
twn/+archive/ubuntu/fwupd-1.2.10-4 (without Timo's make up).
Per my reading of the blog article, we should in
Hello, any updates on this? It would be good to get any review comments
because the SRU will need to be modified again to include this as well:
https://github.com/fwupd/fwupd/commit/004a0624d05211e8436060bb7af6b0c6f2d805a3
(See https://blogs.gnome.org/hughsie/2019/12/11/improving-the-security-
mo
** Changed in: oem-priority
Status: In Progress => Triaged
--
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.10
Can we please follow up on this? This type of smooth upgrade stuff
needs to happen before focal too so that people can jump from
bionic->focal.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1820768
T
** Changed in: fwupdate (Ubuntu)
Importance: Undecided => High
** Changed in: fwupdate (Ubuntu Bionic)
Importance: Undecided => High
--
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:
Steve, could you have another look at this? Mario addressed the concerns
in #19, and fwupdate backport in the queue should make the upgrade
smooth.
I've also sponsored a new fwupd based on 1.2.10 from eoan.
** Changed in: fwupd (Ubuntu Bionic)
Status: Incomplete => Triaged
** Changed in:
the updated the fwupd 1.2.10 ppa. It need the libxmlb that already in proposed
channel.
https://launchpad.net/~ycheng-twn/+archive/ubuntu/fwupd-1.2.10-2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1
I've uploaded the transitional fwupdate to the queue, and rejected the
old fwupd upload because it was based on 1.2.5 and AIUI the desire is to
get 1.2.10 in bionic, ycheng promised to prepare that soon.
** Also affects: fwupdate (Ubuntu)
Importance: Undecided
Status: New
** Changed in:
FYI That did sync back to Ubuntu eoan as well. I think that as part of
transitioning 18.04, it should come back to 18.04 with the updated SRU.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1820768
Ti
** 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 fwupd.
** 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 fwupd.
Here's link for what's happening in Debian at 12-6.
https://tracker.debian.org/news/1061561/accepted-fwupdate-12-6-source-into-unstable/
--
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:
fwupdate has been dropped from eaon in bug #1841744.
It's also said discussed in debian to do so in debian.
https://salsa.debian.org/efi-
team/fwupdate/commit/b4daba89c567d4cf52f5deaab1ea2ee13039d03f
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
@Bearsh, Thank you for testing.
You also need to install fwupd-signed so it can work. Currently it only
avaialbe to 1.2.5 ppa which is https://launchpad.net/~ycheng-
twn/+archive/ubuntu/fwupd-14
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Yuan-Chen, I installed fwupd from your ppa. Logitech fw-update works, thanks.
unfortunately system firmware on my xps13 does not as fwupd complains about
missing signed bootloader:
"UpdateError: missing signed bootloader for secure boot:
/usr/lib/fwupd/efi/fwupdx64.efi.signed cannot be f
** Summary changed:
- [SRU] support new cab and new docking firmware upgrade in fwupd 1.2.5/1.2.10
+ [SRU] support new cab and new docking firmware upgrade in fwupd 1.2.10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
55 matches
Mail list logo
