Hi,
I just noticed, rpmlint doesn't warn about overly long %changelog entries anymore.
Did the FPG change (and me having missed/forgotten about this change) or is this a bug in rpmlint?
Ralf
On Thu, Oct 24, 2013 at 10:07 AM, Ralf Corsepius rc040203@freenet.de wrote:
I just noticed, rpmlint doesn't warn about overly long %changelog entries anymore.
I don't think it has ever done that. It does warn about "too long" summaries and description lines though.
On 10/24/2013 09:48 AM, Ville Skyttä wrote:
On Thu, Oct 24, 2013 at 10:07 AM, Ralf Corsepius rc040203@freenet.de wrote:
I just noticed, rpmlint doesn't warn about overly long %changelog entries anymore.
I don't think it has ever done that.
I could have sworn, it once had done, but I would not want to exclude being wrong ;)
It does warn about "too long" summaries and description lines though.
So, what do we want to do about overly long changelog entries in general (FPG-wise) and about rpmlint?
* Do we want to have a limit? If yes, which? * Can rpmlint (easily) be extended to warn about them?
Background of this question is this review request: https://bugzilla.redhat.com/show_bug.cgi?id=476234
Its %changelog contains %changelog entries up to ~300 chars.
Ralf
On Thu, Oct 24, 2013 at 11:42 AM, Ralf Corsepius rc040203@freenet.de wrote:
So, what do we want to do about overly long changelog entries in general (FPG-wise) and about rpmlint?
- Do we want to have a limit? If yes, which?
- Can rpmlint (easily) be extended to warn about them?
Offhand I think it'd be easy to add this in rpmlint. Go ahead and file a bug if you'd like to see it, preferably along with suggestions for the default limit (will be made configurable) AND text for the extended explanation for the issue (rpmlint -I).
packaging@lists.fedoraproject.org