Control: severity -1 normal

On 05/10/26 2:38 am, Thomas Goirand wrote:
> Package: lintian
> Version: 2.122.0
> Severity: important
> 
> Hi,
> 
> Some of my packages are using debian/po.in, and merge stuff into a debian/po
> folder at build time. You can see this in Octavia for example. IMO, this is a
> very legitimate use of templates, all located in a single place, used by many
> packages.
> 
> And then, Lintian doesn't see this, only expect debian/po, and gives me a
> bad RED ERROR I'M-SO-BAD thingy.
> 
> Please fix this. :)

I see that you do a `cp -auxf debian/po.in debian/po` here[1]. I then don't 
quite understand
the rationale behind having a `.in` - what purpose does it serve?

Given that lintian is a static analysis tool, it becomes a bit hard to detect 
cases like these
where people use non-standard paths. I could check for `d/po.in` directory and 
things inside
the same for po-debconf related checks. But then, someone else may end up using 
`d/po.templates`
or `d/templates` or something else.

Do you happen to have an authoritative list of directories that are common?

The manpage[2] explicitly only lists `d/po` for now.

> Also, no, this should have NEVER been a bad RED error. The package still would
> continue to work if not using po-debconf.

Errors are for cases where it is a policy violation and/or actual packaging 
error [2]. It does not
mean that the package will cease to function.

> Because of hard error from Lintian, I'm setting Severity: important for this
> false-positive.

As per [3] it does not warrant an important severity; lowering to normal.

[1] 
https://salsa.debian.org/openstack-team/services/octavia/-/blob/debian/hibiscus/debian/rules?ref_type=heads#L34
[2] https://manpages.debian.org/trixie/po-debconf/po-debconf.7.en.html#Create
[3] https://lintian.debian.org/manual/index.html
[4] https://www.debian.org/Bugs/Developer#severities

Best,
Nilesh

Reply via email to