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. :) Also, no, this should have NEVER been a bad RED error. The package still would continue to work if not using po-debconf. Because of hard error from Lintian, I'm setting Severity: important for this false-positive. Cheers, Thomas Goirand (zigo)
Control: severity -1 normal 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. 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. 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
Hi, Thanks for the follow-up! I'm merging templates from openstack-pkg-tools that is used in many OpenStack services. It's just more convenient this way, to write the clean target (ie: rm -rf debian/po). The machinery would be a way more complicated if I had to force myself to use debian/po in the source tree. This is, IMO, a common case that should be addressed. If you have suggestions to do it in another way, let me know. different name, you may suggest to use .in instead. If you were to ask me to switch to another directory name, to avoid the Lintian warninig, I would do it. Right, I don't think there's any authoritative list. IMO, errors is what makes a package having RC issues. But let's not discuss this, I don't mind much as long as this false positive is fixed. No worries, your call... :) Cheers, Thomas Goirand (zigo)
Hello, Bug #1149975 in lintian reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/lintian/lintian/-/commit/f2a10af0e351e2d0c33014c5376d8cf74593d052 (this message was generated automatically) -- Greetings https://bugs.debian.org/1149975