On Sunday, 19 September 2021 17:53:26 CET Diederik de Haas wrote:
> According to 'buildd' version 1.5.7-4+b1 has been built 28 days ago,
> but because this issue is still present, fwupd can't be updated.
> I'm fine with waiting a couple of days as that happens with other
> packages from time to time as well. When it last for more then a week,
> I tend to investigate why. It's now almost a month.
> And it's consistently recurring.
Thus bug is supposed to be fixed, but the above described problem still exists
on my system, although it's not a month (yet?).
root@bagend:~# aptitude full-upgrade -s
The following NEW packages will be installed:
fwupd-unsigned{a} libfwupdplugin5{a}
The following packages will be REMOVED:
libfwupdplugin1{u}
The following packages will be upgraded:
fwupd
1 packages upgraded, 2 newly installed, 1 to remove and 0 not upgraded.
Need to get 2,769 kB of archives. After unpacking 1,660 kB will be used.
The following packages have unmet dependencies:
fwupd-amd64-signed : Depends: fwupd (< 1.5.7-6) but 1.7.4-1 is to be
installed
The following actions will resolve these dependencies:
Keep the following packages at their current version:
1) fwupd [1.5.7-5 (now, testing)]
2) fwupd-unsigned [Not Installed]
3) libfwupdplugin1 [1.5.7-5 (now, testing)]
Accept this solution? [Y/n/q/?] qAttachment:
signature.asc
Description: This is a digitally signed message part.