Bug 1381004 - gpg sign public virtio-win rpms
Summary: gpg sign public virtio-win rpms
Keywords:
Status: CLOSED DUPLICATE of bug 1353036
Alias: None
Product: Virtualization Tools
Classification: Community
Component: virtio-win
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Cole Robinson
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-02 07:11 UTC by Frank Büttner
Modified: 2019-03-28 23:57 UTC (History)
10 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2019-03-28 23:57:55 UTC
Embargoed:

Attachments (Terms of Use)

Description Frank Büttner 2016-10-02 07:11:45 UTC 
Description of problem:
The last version of it seem not to be digital signet.

Version-Release number of selected component (if applicable):
virtio-win-0.1.126-2 not signet

How reproducible:
every time

Steps to Reproduce:
1. dnf update


Actual results:
DNF error:
Error: Package virtio-win-0.1.126-2.noarch.rpm is not signed

Expected results:
working update

Additional info:
Comment 1 Vadim Rozenfeld 2016-10-02 12:28:13 UTC 
Hi Cole,

I'm not sure how it works. Do we usually sign virtio-win RPMs available publicly?

Thanks,
Vadim.
Comment 2 Cole Robinson 2016-10-10 13:10:10 UTC 
The signing referred to by dnf is about RPM gpg signatures, which have never been set up for the public virtio-win repo/RPMs. Not sure what changed here that dnf is suddenly warning about this. You can use the --nogpgcheck option to work around it.
Comment 3 Cole Robinson 2019-03-28 23:57:55 UTC 

*** This bug has been marked as a duplicate of bug 1353036 ***
Note You need to log in before you can comment on or make changes to this bug.