Description of problem: Title says it all. This was checked prior to pushing with rpmlint on srpm and no error was shown. http://pkgsubmit.mageia.org/uploads/rejected/cauldron/core/release/20121120220434.barjac.valstar.15131.youri Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3.
No action since over 2 yrs ago and still assigned to Bug Squad Closing as OLD Please reopen if this report is still valid for _current_ cauldron and/or fully updated Mageia 4
Status: NEW => RESOLVEDResolution: (none) => OLD
I just changed a sub-package group in gnuradio to "Garbage". Running rpmlint on the new srpm reports no errors, so this is still valid.
Status: RESOLVED => REOPENEDResolution: OLD => (none)
Still Valid for Mageia 5 :\
Assignee: bugsquad => rpmstack
I don't know if this issue is valid with the latest upstream version of rpmlint. We're currently on rpmlint-1.5, while upstream released rpmlint-1.9 at the end of June[1]. Some kind of effort to rebase our rpmlint patches, our rpmlint policy, etc. needs to be made prior to working on rpmlint related bugs. Otherwise we're just going to create more problems for us in the future. [1]: https://github.com/rpm-software-management/rpmlint/releases/tag/rpmlint-1.9
CC: (none) => ngompa13