Project

General

Profile

Actions
Copy link

Bug #3545

closed

Foreman-release 1.3.0 RPM plugins repo sets gpgcheck=1 even though the repo is not signed

Added by Martin Jackson about 11 years ago. Updated about 11 years ago.

Status:
Duplicate
Priority:
Normal
Assignee:
-
Category:
Packaging
Target version:
-
Difficulty:
Triaged:
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

/etc/yum.repos.d/foreman-plugins.repo from foreman-release-1.3.0-1.fc19.noarch ships with gpgcheck=1. But the files in the foreman-plugins repo are not actually signed.

I see two solutions to this problem:
1) Sign the packages, and leave the file as is
2) Set gpgcheck=0 in the file.

Related issues 1 (0 open — 1 closed)

Is duplicate of Foreman - Bug #3251: Plugins repo definition is unsigned, should not have gpgcheck=1ClosedDominic Cleal10/15/2013Actions
Actions
Copy link
 #1

Updated by Dominic Cleal about 11 years ago

  • Is duplicate of Bug #3251: Plugins repo definition is unsigned, should not have gpgcheck=1 added
Actions
Copy link
 #2

Updated by Dominic Cleal about 11 years ago

  • Category set to Packaging
  • Status changed from New to Duplicate

Thanks for the report Martin, we've disabled gpgcheck for 1.3.1 which will be out shortly.

Actions
Copy link

Also available in: Atom PDF