- Add v4l2loopback-rpmlintrc with addFilter("kmp-missing-supplements")
to catch build errors with the new rpmlint under Factory/TW.
(E: kmp-missing-supplements (Badness: 10000))
Ok, thanks. The rejection was almost clear to me and with the explanation, similar to yours, dimstar is certainly not wrong.
Basically I just wanted to avoid that in the course of kernel updates modules (which I use among others) lag behind the current version because of this problem.
I will investigate further what the status is with the actual problem in rpmlint (or whatever is responsible for it).
Note: And to be honest, I can't tell why the extra line helps either.
With rpmlint and the checks and compares I slowly but surely don't see through anymore.
- Add v4l2loopback-rpmlintrc with addFilter("kmp-missing-supplements")
to catch build errors with the new rpmlint under Factory/TW.
(E: kmp-missing-supplements (Badness: 10000))
Is it proper to just ignore rpmlint errors? Or is it a WiP thing?
I think this is just an interim solution until the checks work again as originally.
It seems that other KMP projects are also affected.
https://lists.opensuse.org/archives/list/kernel@lists.opensuse.org/thread/J2T3BWW3SGKIKOACCK7BSALMHSC5TKNS/
If you want to make your argument, see sr#917091
Ok, thanks. The rejection was almost clear to me and with the explanation, similar to yours, dimstar is certainly not wrong.
Basically I just wanted to avoid that in the course of kernel updates modules (which I use among others) lag behind the current version because of this problem.
I will investigate further what the status is with the actual problem in rpmlint (or whatever is responsible for it).
I have found another possible solution that does not require an rpmlintrc file,
but an extension in the preamble - see
https://build.opensuse.org/package/rdiff/home:munix9/v4l2loopback?opackage=v4l2loopback&oproject=multimedia%3Aapps&rev=2
The additional line in question is:
Supplements: (kernel-%1 and %name)
But I won't open another SR, because I don't know if this approach is allowed, compliant, legal or whatever.
So it serves only as a hint.
Note: And to be honest, I can't tell why the extra line helps either.
With rpmlint and the checks and compares I slowly but surely don't see through anymore.
The notification for this had fallen into my spam filter. Basically we should wait for the rpmlint fix to percolate through Factory to Tumbleweed.