[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#463900: marked as done (False positive for missing dh_desktop call in packages without MimeType fields)

Your message dated Mon, 03 Mar 2008 18:20:09 -0800
with message-id <87ejar44di.fsf@windlord.stanford.edu>
and subject line Re: Bug#463900: False positive for missing dh_desktop call in packages without MimeType fields
has caused the Debian Bug report #463900,
regarding False positive for missing dh_desktop call in packages without MimeType fields
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 owner@bugs.debian.org
immediately.)


-- 
463900: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=463900
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: lintian
Version: 1.23.42
Severity: normal

  One of my packages produces this lintian warning:

W: heroes source: desktop-file-but-no-dh_desktop-call
N:
N:   It looks like your package includes a .desktop file and you use
N:   debhelper to build it, but you don't call dh_desktop in your rules
N:   file.

  But according to dh_desktop(1), this is only needed or useful for
files that contain a Mime-Type entry.  Should lintian really be telling
me to run no-ops?

  Daniel

-- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 2.6.22-3-686 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages lintian depends on:
ii  binutils            2.18.1~cvs20080103-1 The GNU assembler, linker and bina
ii  diffstat            1.45-2               produces graph of changes introduc
ii  dpkg-dev            1.14.16.6            package building tools for Debian
ii  file                4.23-1               Determines file type using "magic"
ii  gettext             0.17-2               GNU Internationalization utilities
ii  intltool-debian     0.35.0+20060710.1    Help i18n of RFC822 compliant conf
ii  libparse-debianchan 1.1.1-2              parse Debian changelogs and output
ii  liburi-perl         1.35.dfsg.1-1        Manipulates and accesses URI strin
ii  man-db              2.5.0-4              on-line manual pager
ii  perl [libdigest-md5 5.8.8-12             Larry Wall's Practical Extraction 

lintian recommends no packages.

-- no debconf information

--- End Message ---
--- Begin Message --- 
Russ Allbery <rra@debian.org> writes:
> Daniel Burrows <dburrows@debian.org> writes:
>
>> Package: lintian
>> Version: 1.23.42
>> Severity: normal
>>
>>   One of my packages produces this lintian warning:
>>
>> W: heroes source: desktop-file-but-no-dh_desktop-call
>> N:
>> N:   It looks like your package includes a .desktop file and you use
>> N:   debhelper to build it, but you don't call dh_desktop in your rules
>> N:   file.
>>
>>   But according to dh_desktop(1), this is only needed or useful for
>> files that contain a Mime-Type entry.  Should lintian really be telling
>> me to run no-ops?
>
> Yes, I believe so.  As I understand it, the intention is future-proofing:
> right *now*, the only thing update-desktop-database does is update MIME
> databases, and hence dh_desktop does nothing if there is no MimeType
> field, but this may not always be the case.  With a dh_desktop call, any
> future needs can be handled with a binNMU against the latest debhelper
> should something additional be needed.
>
> It's possibly mind-reading on my part, but I think that's what the
> "currently be ignored" part is intended to get at.

I'm going ahead and closing this bug with the above rationale.  I believe
that always calling dh_desktop is the right thing to do, even if it
currently is a no-op.  If you run into other information that indicates
I'm wrong, please reopen this bug and let us know.

Thanks!

-- 
Russ Allbery (rra@debian.org)               <http://www.eyrie.org/~eagle/>

--- End Message ---
Reply to: