Your message dated Sun, 15 Sep 2013 12:00:07 +0200
with message-id
<canqxmqec_cmbbfpwwc9botr9t8xsdvqfrg7fqfkpff50uem...@mail.gmail.com>
and subject line Re: Bug#718169:
has caused the Debian Bug report #718169,
regarding Leading underscore in desktop file entry not recognized
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
718169: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=718169
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: lintian
Running Lintian 2.5.15 in sid, I got this warning:
I: gnuhealth-client: desktop-entry-lacks-keywords-entry
usr/share/applications/gnuhealth-client.desktop
I follow the links from the info on the Lintian report page [0], and find
the following example from the Gnome website [1]:
_Keywords=chat;messaging;im;irc;voip;
According to that page, "Maintainers/developers must set a preceding
underscore in "_Keywords" to inform intltool that this field should be
extracted, and its translations merged back into the .desktop.in file."
When running Lintian again, instead of the warning disappearing, a new one
appears ;)
W: gnuhealth-client: desktop-entry-contains-unknown-key
usr/share/applications/gnuhealth-client.desktop:11 _Keywords
I: gnuhealth-client: desktop-entry-lacks-keywords-entry
usr/share/applications/gnuhealth-client.desktop
When removing the underscore, all warnings disappear.
I assume Lintian does not recognize the leading underscore in desktop file
entries (or maybe just for the newer Keywords)?
Cheers,
+Emilien
[0] http://lintian.debian.org/tags/desktop-entry-lacks-keywords-entry.html
[1] https://wiki.gnome.org/GnomeGoals/DesktopFileKeywords
--- End Message ---
--- Begin Message ---
I agree this is non-standard. I don't have currently time to push to
standard body, so closing this bug.
--- End Message ---
