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

Bug#507917: marked as done (debhelper + data-only packages = annoying lintian warning)

Your message dated Sun, 07 Dec 2008 10:26:45 +0200
with message-id <493B88C5.7060102@gmail.com>
and subject line Re: Bug#507917: debhelper + data-only packages = annoying lintian warning
has caused the Debian Bug report #507917,
regarding debhelper + data-only packages = annoying lintian warning
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.)


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

Hello.

Lintian recently started to produce 'debhelper-but-no-misc-depends'
warnings. While it reveal true issues, it also produces false positives
in case of data-only packages, which have no 'Depends' field at all.
And I can't fix this warnings, because putting
'Depends: ${misc:Depends}' will in 99% of my cases result in empty
'Depends:' line which is Policy violation. I guess this is archive-wide
issue, so I am waiting for advice from you (I can just override false
positives in all my packages, but I am not very happy with this solution.)

Regards,
Eugene.

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.26-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages lintian depends on:
ii  binutils            2.18.1~cvs20080103-7 The GNU assembler, linker and bina
ii  diffstat            1.46-1               produces graph of changes introduc
ii  dpkg-dev            1.14.22              Debian package development tools
ii  file                4.26-1               Determines file type using "magic"
ii  gettext             0.17-6               GNU Internationalization utilities
ii  intltool-debian     0.35.0+20060710.1    Help i18n of RFC822 compliant conf
ii  libipc-run-perl     0.80-2               Perl module for running processes
ii  libparse-debianchan 1.1.1-2              parse Debian changelogs and output
ii  libtimedate-perl    1.1600-9             Time and date functions for Perl
ii  liburi-perl         1.35.dfsg.1-1        Manipulates and accesses URI strin
ii  man-db              2.5.2-3              on-line manual pager
ii  perl [libdigest-sha 5.10.0-16            Larry Wall's Practical Extraction 

lintian recommends no packages.

Versions of packages lintian suggests:
pn  binutils-multiarch            <none>     (no description available)
ii  libtext-template-perl         1.44-1.2   Text::Template perl module
ii  man-db                        2.5.2-3    on-line manual pager

-- no debconf information

--- End Message ---
--- Begin Message --- 
Raphael Geissert wrote:
> 2008/12/6 Eugene V. Lyubimkin <jackyf.devel@gmail.com>:
> Oh, and:
>> 'Depends: ${misc:Depends}' will in 99% of my cases result in empty
>> 'Depends:' line which is Policy violation.
> 
> No, it won't (unless you are building the package all by yourself
> without the assistance of dpkg, which is very unlikely to happen as
> the package would easily break and debhelper would probably not be
> used either).
You are right. I had to check this before. dpkg-gencontrol is more smarter than I thought.
It correctly throws away empty 'Depends'. Sorry. I'm closing this bug.

-- 
Eugene V. Lyubimkin aka JackYF, JID: jackyf.devel(maildog)gmail.com
Ukrainian C++ developer, Debian APT contributor

Attachment: signature.asc
Description: OpenPGP digital signature


--- End Message ---
Reply to: