Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 651876 - sys-apps/fwupd-1.0.5: Failed to update metadata for lvfs: Not compiled with GPG support
Summary: sys-apps/fwupd-1.0.5: Failed to update metadata for lvfs: Not compiled with G...
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Lars Wendler (Polynomial-C) (RETIRED)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-03-29 03:32 UTC by BT
Modified: 2018-06-09 15:23 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
emerge --info (emerge.info,6.05 KB, text/plain)
2018-03-29 03:32 UTC, BT
Details

Note You need to log in before you can comment on or make changes to this bug.
Description BT 2018-03-29 03:32:31 UTC
Created attachment 526022 [details]
emerge --info

I'm unable to get the list of updates with fwupd-1.0.5:

# fwupdmgr get-updates
Firmware metadata has not been updated for 30 days and may not be up to date.

Update now? (Requires internet connection) [y|N]: y
Fetching metadata https://s3.amazonaws.com/lvfsbucket/downloads/firmware.xml.gz
Downloading…           [***************************************]
Fetching signature https://s3.amazonaws.com/lvfsbucket/downloads/firmware.xml.gz.asc

Failed to update metadata for lvfs: Not compiled with GPG support

fwupdmgr complains about a lack of GPG support, but sys-apps/fwupd is built with the gpg USE flag enabled.
Comment 1 BT 2018-03-29 22:48:00 UTC
1.0.6 has been released, but the NEWS file doesn't mention anything about this issue.
Comment 2 Lars Wendler (Polynomial-C) (RETIRED) gentoo-dev 2018-04-03 14:11:02 UTC
Please test version 1.0.6 and report back success/failure.
Comment 3 BT 2018-04-03 23:46:03 UTC
The issue is fixed with 1.0.6.
Comment 4 nyronium 2018-06-09 15:23:36 UTC
I encountered the same problem with =sys-apps/fwupd-1.0.6 today.
Even after enabling the gpg use flag and reemerging the package, the error persisted.

Interestingly i was able to resolve the issue by simply rebooting the system and reemerging the package again. Therefore i suspect that the build system of the package caches some critical files which are cleared at boot time.

I was able to reproduce the issue by unmerging the package and emerging the version without gpg first, followed by the version with the gpg flag enabled. Executing it then will produce the error. Rebooting and reemerging solves it.