Bug#1005326: no-code-sections triggered on non-ELF files

[duck]

Package: lintian
Version: 2.114.0


Quack,

no-code-sections is triggered on dxvk, and also on wine, but these are 
not ELF files since it's targeted for Windows. Of course an override is 
possible but here there's an obvious way to avoid a false positive since 
readelf fails with "readelf: Error: Not an ELF file - it has the wrong 
magic bytes at the start", or maybe by using `objdump -a` or some other 
method to first check the archive format (I'm really not an expert in 
this area). Could you consider improving the check?


Regards.
\_o<

--
Marc Dequènes

Bug#905258: lintian: ruby-script-but-no-ruby-dep does not accept :any dependency

[duck]

Package: lintian
Version: 2.5.94

Quack,

I was changing multiarch-related dependency settings on a Ruby package, 
setting depends to "ruby:any | ruby-interpreter", but this raises 
`ruby-script-but-no-ruby-dep`. I asked help from Helmut Grohne to be 
sure I was doing the right things and we believe this is a lintian bug. 
Moreover, in 'data/scripts/interpreters' :any is accepted for Python but 
not Ruby.


Regards.
\_o<

--
Marc Dequènes

Bug#818609: lintian: python-script-but-no-python-dep false positive

[duck]

Quack,

I stumbled into such false positive while preparing a new upstream 
release.


$ dpkg -I weboob_1.3-1_all.deb | grep Depends
 Depends: python:any (<< 2.8), python:any (>= 2.7.5-5~), python-weboob 
(>= 1.3-1), python-html2text, python-prettytable


$ lintian weboob_1.3-1_all.deb
E: weboob: python-script-but-no-python-dep usr/share/weboob/imm-o-matic
E: weboob: python-script-but-no-python-dep 
usr/share/weboob/replace-backends-pass.py


So maybe the test do not cope with versioning or maultiarch. This was 
generated with ${python:Depends}.


Regards.
\_o<

--
Marc Dequènes

Bug#521960: lintian: desktop-mimetype-without-update-call false positive with CDBS

[Marc Dequènes (Duck)]

Package: lintian
Version: 2.2.8


Coin,

When using CDBS and the gnome class, the dh_desktop call is done  
automatically, thus does

not appear in the debian/rules file.

To match this behavior the debian/rules file must contain the  
following lines, in that

_exact_ order of appearance :
include /usr/share/cdbs/1/rules/debhelper.mk
include /usr/share/cdbs/1/class/gnome.mk
(but may be separated by other include calls or definitions)

Thanks.


--
Marc Dequènes (Duck)


pgpXC960sgeiL.pgp
Description: PGP Digital Signature

Bug#521960: lintian: desktop-mimetype-without-update-call false positive with CDBS

[Marc Dequènes (Duck)]

reassign 521960 debhelper
retitle 521960 debhelper: dh_desktop fails if PATH contains relative path
thanks

Coin,

Quoting Russ Allbery r...@debian.org:


Could you check your generated postinst and be sure that the call is
actually in there?


You're right, the postinst does not contain the needed call.

I found dh_desktop does not sanitize the PATH variable, thus resulting  
to the following error due to '~/bin' being in my path when building  
the package:
find: The relative path `~/bin' is included in the PATH environment  
variable, which is insecure in combination with the -execdir action of  
find.  Please remove that entry from $PATH


I think a DD shoud be able to work with its custom scripts in ~/bin or  
anywhere else, and debhelper scripts should sanitize their environment.


Thanks for your help, Russ.

--
Marc Dequènes (Duck)


pgpbjOhVqRsE6.pgp
Description: PGP Digital Signature

Bug#365466: lintian: wrong build-depends-without-arch-dep patchutils

[Duck]

Coin,

Russ Allbery [EMAIL PROTECTED] writes:

 This one is a *little* harder since patchutils isn't actually required,
 only used if it's available.  This is only for the simple-patchsys rule
 set, correct?  Or is it also used for dpatch and quilt?

It is used for the 3 of them (they use lsdiff only), and you're right,
it is not absolutly required. But since it is here to prevent nasty
modifications of build-generated files and avoid breakages, i think this
should be considered necessary.

I think having cdbs with import of any of the 3 patch system should be a
sufficient condition to allow patchutils. if you think it is not, please
reassign this bug to cdbs, so as to request the necessary modifications
of both the rules and the Build-dependency generation helper.

Thanks.

-- 
Marc Dequènes (Duck)


pgpZP4lAePbZs.pgp
Description: PGP signature

Bug#365030: lintian: build-depends-without-arch-dep python-all-dev

[Duck]

Package: lintian
Version: 1.23.18


Coin,

Python is needed for the clean rule:
  python setup.py clean -a
then lintian should not complain.

Regards.

-- 
Marc Dequènes (Duck)


pgpm5f9Izebu7.pgp
Description: PGP signature

Bug#365041: lintian: wrong build-depends-without-arch-dep quilt

[Duck]

Package: lintian
Version: 1.23.18


Coin,

With CDBS, or any packaging system, patch management may be used and the
selected patch tool is necessary in the clean rule to unpatch. Then
quilt (and dpatch) should not trigger this error.

Regards.

-- 
Marc Dequènes (Duck)


pgplh42wJNuY1.pgp
Description: PGP signature

Bug#364943: missing-build-dependency python | python-dev with python-all-dev

[Duck]

Package: lintian
Version: 1.23.18


Coin,

New python-all-dev is a adequate build-depends if using python-support.

Thanks.

-- 
Marc Dequènes (Duck)


pgpeKWcJ6J5gU.pgp
Description: PGP signature