Hi Jakub and Dmitry (ccing you both, not sure if you are subscribed to the bug)
>You are probably[0] referring to: > >P: gdbm source: license-problem-gfdl-non-official-text doc/gdbm.info invariant >part is: with no invariant sections, no front-cover, and no back-cover texts >P: gdbm source: license-problem-gfdl-non-official-text doc/gdbm.texinfo >invariant part is: with no invariant sections, no front-cover, and no >back-cover texts completely exact! >The tag name is not great, and it's debatable whether it's useful (which >is why it's pedantic), but this is true positive. > >The tag description is: > >>The given source file is licensed under GFDL, but using a non-official >>text for the "no invariant sections" part. >> >>Please ask upstream to always use (case insensitive): with no Invariant >>Sections, no Front-Cover Texts, and no Back-Cover Texts. > >(IMO it's a bug in Lintian that it treats the text case-insensitively, >because "Invariant Sections", "Front-Cover Texts" and "Back-Cover Texts" >are terms defined in the license and therefore should be spelled exactly >this way. But I digress...) actually I did the same reasoning when I read that... I don't think case sensitiveness is a legal issue >In the gdbm, you have: > >>with no Invariant Sections, no Front-Cover, and no Back-Cover texts. > >Note missing "Texts" after "Front-Cover" and lowercase "texts" at the >end. so, Dmitry, can you please open an upstream bug here? >[0] Please always paste exact output of static analysis tools. This will >help people diagnose the problem without the hassle of downloading >packages and running the tools themselves. Also, the output may vary >with the tool's version, used options, or the phase of the moon. you are completely true, but I usually end up in being superficial, to allow sponsoree do the same and report back. (giving the exact output might force my reasoning in the sponsoree mind, and I prefer to see *him* giving me the answer, even if sometimes I already know it) but yeah, in case of this possible lintian bug I for sure could have provided more information :) (actually it is an upstream bug the missing word, and a lintian bug the case sensitive issue, at least to my reasoning, but IANAL) thanks again! Gianfranco
