| Summary: | rpmlint reports a lot of strange invalid warnings | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Kamil Rytarowski <n54> |
| Component: | RPM Packages | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | Normal | CC: | marja11 |
| Version: | 1 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | rpmlint-1.2-1.mga1.src.rpm | CVE: | |
| Status comment: | |||
|
Description
Kamil Rytarowski
2011-11-26 01:59:54 CET
Hi Kamil, Thank you for this report. I'm not sure if this is a real problem report or not as to me (with perhaps exception of the libx11 notification) these are valid findings that rpmlint reports. True, some warnings might be overly tight in your opinion, but rpmlint is meant to give warnings where it can. I'm assigning this report to the maintainer of rpmlint for further handling. (In reply to comment #0) > 1) when doing rpmlint over a SRC.RPM it reports "strange-permission" 0664L for > a spec and files - 0664 is correct! Is it? Why should these files be group writable? I'd expect 0644 instead of 0664 for them. > 4) It reports that about no packager tag > > W: no-packager-tag Seems correct to me. > This annoys a lot and beguiles especially apprentices. Perhaps this can is better discussed on the dev list than in bugzilla. Assignee:
bugsquad =>
misc About 1 you are right. When I read https://fedoraproject.org/wiki/ParagNemade/CommonRpmlintErrors I make a mistake - 0644 and 0664 look very similar. These warnings for me, an apprentice without real RPM-distro experiences, obfuscated my mind a lot - when I read one one the wiki and rpmlint warnings against it.. then this isn't normal. For an experienced packager this doesn't mean something but it's unpleasant to follow one style, and suggest to use rpmlint, that warnings against this style and marks as improper. And this actually is an error! There are differences between rpmlint of a spec directly and in a .src.rpm! And this was just a single example of rpmlint over 1 single package.. Can you fill separate bug report for separate problems ? For libx11, that's a false positive, and the goal is to explictely not use libfoo$major-devel, so that's just a exception to add. For the missing changelog, that's also something to filter in our config For running rpmlint on a spec and on a srpm, there is not the same check run, because there isn't the same type of information ( for example, how to check content of file with just the spec ? ). For %setup, that's a rpmlint bug, but since that's the first time I see it in 7 years, I think it is not that urgent to fix ( ie, will wait for a new release ).
Marja Van Waes
2012-07-12 00:14:53 CEST
CC:
(none) =>
marja11 This message is a reminder that Mageia 1 is nearing its end of life. In approximately 25 days from now, Mageia will stop maintaining and issuing updates for Mageia 1. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '1'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version prior to Mageia 1's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 1 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. -- Mageia Bugsquad Mageia 1 changed to end-of-life (EOL) status on ''1st December''. Mageia 1 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Mageia please feel free to click on "Version" change it against that version of Mageia and reopen this bug. Thank you for reporting this bug and we are sorry it could not be fixed. -- Mageia Bugsquad Status:
NEW =>
RESOLVED |