Description of problem: /var/cache/urpmi/rpms/libreoffice-core-5.1.0.1-0.2.mga6.x86_64.rpm: Missing signature (OK ((none))) /var/cache/urpmi/rpms/libreoffice-pyuno-5.1.0.1-0.2.mga6.x86_64.rpm: Missing signature (OK ((none))) Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. urpmi --download-all --downloader wget --auto-update --keep --split-level=1 --split-length=1 --auto 2. 3. Reproducible: Steps to Reproduce:
Also saw mention of this on IRC. Hopefully it'll be fixed on the next rebuild and there isn't a larger issue with the build system.
Assignee: bugsquad => thierry.vignaud
I cannot do anything about this. There're other packages that are unsigned BS needs to be fixed, then latest packages need to be resigned. This is sysadmin job
CC: (none) => sysadmin-bugsComponent: RPM Packages => Release (media or process)Assignee: thierry.vignaud => bugsquad
CC: (none) => thierry.vignaudComponent: Release (media or process) => BuildSystemVersion: Cauldron => unspecifiedProduct: Mageia => Infrastructure
CC: (none) => olav
(In reply to David Walser from comment #1) > Also saw mention of this on IRC. Hopefully it'll be fixed on the next > rebuild and there isn't a larger issue with the build system. Hmmm, I wonder: bug 17435 - mga6: geronimo-jms Missing signature bug 17434 - mga6: apache-commons Missing signature Now that libreoffice signatures has been fixed do I close this bug and open new sig problems like the above or what? With new signature bugs I have a chance of getting the packager to submit a new compile and I can get on with trying to boot/test.
don't for java packages.
Status: NEW => RESOLVEDCC: (none) => mageiaResolution: (none) => FIXED