RPMlint upstream milestone 2.0 is shaping up but there are still ticket that needs to be tackled to finalize the release and enjoy the freshness of awesome QA on Tumbleweed/SLE16.
In this hackweek we plan to look on various problems as described at: https://github.com/rpm-software-management/rpmlint/milestone/1
Looking for hackers with the skills:
Nothing? Add some keywords!
This project is part of:
Hack Week 17 Hack Week 18 Hack Week 19
Activity
Comments
-
over 6 years ago by simotek | Reply
https://rpmlint.opensuse.org/rules/openSUSE:Factory/x86_64/standard is a useful resource for getting started in terms of warnings we care about the least.
There are certain checks like the incorrect-fsf-address that maybe worth keeping as info, ie the release team won't enforce and doesn't care about them, but if a packager see's it they might choose to report it upstream.
-
over 6 years ago by simotek | Reply
Another enhancement would be to make the non-executable-script slightly smarter, currently it just checks for files starting with #!/XXXXX, but there are some languages such as python and ruby (I think) where files may start with #! but don't need to be marked as executable to work (think python modules / libraries) so this test currently generates a lot of false positives.
-
over 6 years ago by scarabeus_iv | Reply
Atm merging SUSE patches from devel:openSUSE:Factory:rpmlint/rpmlint to the main code https://github.com/scarabeusiv/rpmlint/tree/tests
-
over 6 years ago by scarabeus_iv | Reply
Actually upstream is against python3 codebase, as such it does not make sense to try to paralelize the thing as it is pretty ugly to make it work on python 2.7 as such I will have to find something else to do on hackweek.
-
over 5 years ago by scarabeus_iv | Reply
In last years run we switched to modularized rpmlint but it is still way off from 2.0 release that could be trusted. Thus there is milestone in upstream git and we will work in HW18 to get it in better shape again.
Similar Projects
This project is one of its kind!