Bug 7814

Summary: 3_a2:kmahjongg-handbook hasn't been signed on upload
Product: Infrastructure Reporter: Bit Twister <bittwister2>
Component: BuildSystemAssignee: Sysadmin Team <sysadmin-bugs>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: Normal CC: deleted-user-1, pterjan, sysadmin-bugs, thierry.vignaud
Version: unspecified   
Target Milestone: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Source RPM: kdegames4-4.9.2-1.mga3.src.rpm CVE:
Status comment:

Description Bit Twister 2012-10-16 03:57:22 CEST 
Description of problem:
The following package has bad signature:
kmahjongg-handbook-4.9.2-1.mga3.noarch.rpm

Version-Release number of selected component (if applicable):


How reproducible: Always


Steps to Reproduce:
1. urpmi kmahjongg
2.
3.
Manuel Hiebel 2012-10-16 11:13:23 CEST

CC: (none) => pterjan
Assignee: bugsquad => balcaen.john

Comment 1 Thierry Vignaud 2012-10-16 21:50:30 CEST 
It needs to be reuploaded.
And sysadmin team must find out why it wasn't signed

CC: (none) => mageia-sysadm, thierry.vignaud
Summary: 3_a2:kmahjongg-handbook has bad signature => 3_a2:kmahjongg-handbook hasn't been signed on upload

Comment 2 Bit Twister 2012-11-16 17:04:38 CET 
Problem is resolved in 3 Alpha3.

Should the problem Component: be moved from RPM Packages to Release?
Comment 3 Thierry Vignaud 2012-11-16 21:49:48 CET 
No

CC: (none) => sysadmin-bugs
Component: RPM Packages => BuildSystem
Version: Cauldron => unspecified
Assignee: balcaen.john => sysadmin-bugs
Product: Mageia => Infrastructure

Comment 4 Manuel Hiebel 2012-12-09 00:15:37 CET 
closing (was fixed age ago)

Status: NEW => RESOLVED
Resolution: (none) => FIXED

Comment 5 Bit Twister 2012-12-09 01:21:12 CET 
(In reply to comment #4)
> closing 

How unfortunate. 

> (was fixed age ago)

Although the package signature was fixed, seems nobody has found out why some packages are still not signed. This bug for example, then there was bug 8273, that you closed, and bug 8274.   :(
Comment 6 Manuel Hiebel 2012-12-09 12:38:16 CET 
well sysadmin are awake since some months about this issue, the cause is still unknown (it comes randomly)