Chris, On Mon, Oct 8, 2018 at 9:41 AM Chris Lamb <la...@debian.org> wrote: > > Paul, > > > [..] > > Unfortunately I have very little insight or input to share on fonts or > sections more generally in Debian so I will just have to leave this up > to someone else. Apologies that I could not make progress here.
All's well that ends well. I know now that the status quo is just fine with my package. > (I do somehow doubt a mass bug filing would be really appropriate or > welcome, mind you. I'm sure many facing the business end of a mass bug filing would find displeasure with it. :-) I expected that would be the least popular option. But IMHO I felt that if it was a bug, there should be a bug filing against my package, and if it was not a bug, then the lintian message should probably be removed. > Did you consider "fixing" Lintian instead?) Indeed I did, but I was not sure how to approach the issue properly, so I posed the question on debian-policy thinking that might be the best place to start[1]. I only received one response, which indicated that section assignment was within the purview of the FTP Masters[2], so then I followed up with an email to them. In retrospect, I have learned by seeing how Russ phrased this bug report. Chalk one more up for experience... > Again, sorry I can't be of more help. Actually, this bug that Russ filed is being resolved by taking two of the actions that I asked about in the debian-policy mailing: the lintian message will be removed, and "fonts" will be removed from the web page description of the "x11" section, so that certainly helps. Note, however, that there _are_ a few "xfonts-*" fonts in the "x11" section. If you and the rest of the FTP Team agrees, I suppose you could change the lintian message to encourage those packages to set their d/control section to "fonts". Sorry I did not notice this bug until just before it was to be archived. I only saw it while searching to see if another bug had been filed about something else in lintian (concerning "wrong-path-for-interpreter" with the relaxed 4.2.1 policy), and in fact that bug was already filed by someone else and already closed (#908350). Thank you for your detailed responses, Paul Hardy [1] https://lists.debian.org/debian-policy/2018/06/msg00098.html [2] https://lists.debian.org/debian-policy/2018/06/msg00099.html
