date:20180410

Jenkins build is back to normal : lintian-tests_buster #767

2018-04-10 Thread jenkins

See

Build failed in Jenkins: lintian-tests_buster #766

2018-04-10 Thread jenkins

See 

--
[...truncated 221.73 KB...]
Adding debian:Cybertrust_Global_Root.pem
Adding debian:Comodo_Trusted_Services_root.pem
Adding debian:Comodo_Secure_Services_root.pem
Adding debian:Comodo_AAA_Services_root.pem
Adding debian:China_Internet_Network_Information_Center_EV_Certificates_Root.pem
Adding debian:Chambers_of_Commerce_Root_-_2008.pem
Adding debian:Certum_Trusted_Network_CA_2.pem
Adding debian:Certum_Trusted_Network_CA.pem
Adding debian:Certum_Root_CA.pem
Adding debian:Certplus_Root_CA_G2.pem
Adding debian:Certplus_Root_CA_G1.pem
Adding debian:Certplus_Class_2_Primary_CA.pem
Adding debian:Certinomis_-_Root_CA.pem
Warning: there was a problem reading the certificate file 
/etc/ssl/certs/Certinomis_-_Autorit?_Racine.pem. Message:
  /etc/ssl/certs/Certinomis_-_Autorit?_Racine.pem (No such file or directory)
Adding debian:Certigna.pem
Adding debian:Camerfirma_Global_Chambersign_Root.pem
Adding debian:Camerfirma_Chambers_of_Commerce_Root.pem
Adding debian:COMODO_RSA_Certification_Authority.pem
Adding debian:COMODO_ECC_Certification_Authority.pem
Adding debian:COMODO_Certification_Authority.pem
Adding debian:CNNIC_ROOT.pem
Adding debian:CFCA_EV_ROOT.pem
Adding debian:CA_Disig_Root_R2.pem
Adding debian:CA_Disig_Root_R1.pem
Adding debian:Buypass_Class_3_Root_CA.pem
Adding debian:Buypass_Class_2_Root_CA.pem
Adding debian:Baltimore_CyberTrust_Root.pem
Adding debian:Autoridad_de_Certificacion_Firmaprofesional_CIF_A62634068.pem
Adding debian:Atos_TrustedRoot_2011.pem
Adding debian:Amazon_Root_CA_4.pem
Adding debian:Amazon_Root_CA_3.pem
Adding debian:Amazon_Root_CA_2.pem
Adding debian:Amazon_Root_CA_1.pem
Adding debian:AffirmTrust_Premium_ECC.pem
Adding debian:AffirmTrust_Premium.pem
Adding debian:AffirmTrust_Networking.pem
Adding debian:AffirmTrust_Commercial.pem
Adding debian:AddTrust_Qualified_Certificates_Root.pem
Adding debian:AddTrust_Public_Services_Root.pem
Adding debian:AddTrust_Low-Value_Services_Root.pem
Adding debian:AddTrust_External_Root.pem
Adding debian:Actalis_Authentication_Root_CA.pem
Adding debian:AC_RAIZ_FNMT-RCM.pem
Adding debian:ACEDICOM_Root.pem
Adding debian:ACCVRAIZ1.pem
done.
Setting up openjdk-9-jdk-headless:amd64 (9.0.4+12-4) ...
update-alternatives: using /usr/lib/jvm/java-9-openjdk-amd64/bin/jlink to 
provide /usr/bin/jlink (jlink) in auto mode
update-alternatives: using /usr/lib/jvm/java-9-openjdk-amd64/bin/idlj to 
provide /usr/bin/idlj (idlj) in auto mode
update-alternatives: using /usr/lib/jvm/java-9-openjdk-amd64/bin/jdeps to 
provide /usr/bin/jdeps (jdeps) in auto mode
update-alternatives: using /usr/lib/jvm/java-9-openjdk-amd64/bin/wsimport to 
provide /usr/bin/wsimport (wsimport) in auto mode
update-alternatives: using /usr/lib/jvm/java-9-openjdk-amd64/bin/rmic to 
provide /usr/bin/rmic (rmic) in auto mode
update-alternatives: using /usr/lib/jvm/java-9-openjdk-amd64/bin/jinfo to 
provide /usr/bin/jinfo (jinfo) in auto mode
update-alternatives: using /usr/lib/jvm/java-9-openjdk-amd64/bin/jstat to 
provide /usr/bin/jstat (jstat) in auto mode
update-alternatives: using /usr/lib/jvm/java-9-openjdk-amd64/bin/javadoc to 
provide /usr/bin/javadoc (javadoc) in auto mode
update-alternatives: using /usr/lib/jvm/java-9-openjdk-amd64/bin/jmod to 
provide /usr/bin/jmod (jmod) in auto mode
update-alternatives: using /usr/lib/jvm/java-9-openjdk-amd64/bin/javah to 
provide /usr/bin/javah (javah) in auto mode
update-alternatives: using /usr/lib/jvm/java-9-openjdk-amd64/bin/jhsdb to 
provide /usr/bin/jhsdb (jhsdb) in auto mode
update-alternatives: using /usr/lib/jvm/java-9-openjdk-amd64/bin/jstack to 
provide /usr/bin/jstack (jstack) in auto mode
update-alternatives: using /usr/lib/jvm/java-9-openjdk-amd64/bin/jrunscript to 
provide /usr/bin/jrunscript (jrunscript) in auto mode
update-alternatives: using /usr/lib/jvm/java-9-openjdk-amd64/bin/javac to 
provide /usr/bin/javac (javac) in auto mode
update-alternatives: using /usr/lib/jvm/java-9-openjdk-amd64/bin/javap to 
provide /usr/bin/javap (javap) in auto mode
update-alternatives: using /usr/lib/jvm/java-9-openjdk-amd64/bin/jar to provide 
/usr/bin/jar (jar) in auto mode
update-alternatives: using /usr/lib/jvm/java-9-openjdk-amd64/bin/jaotc to 
provide /usr/bin/jaotc (jaotc) in auto mode
update-alternatives: using /usr/lib/jvm/java-9-openjdk-amd64/bin/policytool to 
provide /usr/bin/policytool (policytool) in auto mode
update-alternatives: using /usr/lib/jvm/java-9-openjdk-amd64/bin/schemagen to 
provide /usr/bin/schemagen (schemagen) in auto mode
update-alternatives: using /usr/lib/jvm/java-9-openjdk-amd64/bin/jshell to 
provide /usr/bin/jshell (jshell) in auto mode
update-alternatives: using /usr/lib/jvm/java-9-openjdk-amd64/bin/jps to provide 
/usr/bin/jps (jps) in auto mode
update-alternatives: using /usr/lib/jvm/java-9-openjdk-amd64/bin/xjc to provide 
/usr/bin/xjc (xjc) in auto mode
update-alternatives: using /usr/lib/jv

Jenkins build is back to normal : lintian-tests_stretch-backports #344

2018-04-10 Thread jenkins

See

Jenkins build is back to normal : lintian-tests_sid #2787

2018-04-10 Thread jenkins

See

Build failed in Jenkins: lintian-tests_stretch-backports #343

2018-04-10 Thread jenkins

See 


--
[...truncated 223.83 KB...]
Adding debian:Buypass_Class_2_CA_1.pem
Adding debian:Baltimore_CyberTrust_Root.pem
Adding debian:Autoridad_de_Certificacion_Firmaprofesional_CIF_A62634068.pem
Adding debian:Atos_TrustedRoot_2011.pem
Adding debian:ApplicationCA_-_Japanese_Government.pem
Adding debian:AffirmTrust_Premium_ECC.pem
Adding debian:AffirmTrust_Premium.pem
Adding debian:AffirmTrust_Networking.pem
Adding debian:AffirmTrust_Commercial.pem
Adding debian:AddTrust_Qualified_Certificates_Root.pem
Adding debian:AddTrust_Public_Services_Root.pem
Adding debian:AddTrust_Low-Value_Services_Root.pem
Adding debian:AddTrust_External_Root.pem
Adding debian:Actalis_Authentication_Root_CA.pem
Warning: there was a problem reading the certificate file 
/etc/ssl/certs/AC_Ra?z_Certic?mara_S.A..pem. Message:
  /etc/ssl/certs/AC_Ra?z_Certic?mara_S.A..pem (No such file or directory)
Adding debian:ACEDICOM_Root.pem
Adding debian:ACCVRAIZ1.pem
done.
Setting up dh-autoreconf (17~bpo9+1) ...
Setting up openjdk-8-jdk-headless:amd64 (8u151-b12-1~deb9u1) ...
update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/idlj to 
provide /usr/bin/idlj (idlj) in auto mode
update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jdeps to 
provide /usr/bin/jdeps (jdeps) in auto mode
update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/wsimport to 
provide /usr/bin/wsimport (wsimport) in auto mode
update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/rmic to 
provide /usr/bin/rmic (rmic) in auto mode
update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jinfo to 
provide /usr/bin/jinfo (jinfo) in auto mode
update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jsadebugd to 
provide /usr/bin/jsadebugd (jsadebugd) in auto mode
update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/native2ascii 
to provide /usr/bin/native2ascii (native2ascii) in auto mode
update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jstat to 
provide /usr/bin/jstat (jstat) in auto mode
update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/javac to 
provide /usr/bin/javac (javac) in auto mode
update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/javah to 
provide /usr/bin/javah (javah) in auto mode
update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jstack to 
provide /usr/bin/jstack (jstack) in auto mode
update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jrunscript to 
provide /usr/bin/jrunscript (jrunscript) in auto mode
update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/javadoc to 
provide /usr/bin/javadoc (javadoc) in auto mode
update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/javap to 
provide /usr/bin/javap (javap) in auto mode
update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jar to provide 
/usr/bin/jar (jar) in auto mode
update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/extcheck to 
provide /usr/bin/extcheck (extcheck) in auto mode
update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/schemagen to 
provide /usr/bin/schemagen (schemagen) in auto mode
update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jps to provide 
/usr/bin/jps (jps) in auto mode
update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/xjc to provide 
/usr/bin/xjc (xjc) in auto mode
update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jarsigner to 
provide /usr/bin/jarsigner (jarsigner) in auto mode
update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jmap to 
provide /usr/bin/jmap (jmap) in auto mode
update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jstatd to 
provide /usr/bin/jstatd (jstatd) in auto mode
update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jhat to 
provide /usr/bin/jhat (jhat) in auto mode
update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jdb to provide 
/usr/bin/jdb (jdb) in auto mode
update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/serialver to 
provide /usr/bin/serialver (serialver) in auto mode
update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/wsgen to 
provide /usr/bin/wsgen (wsgen) in auto mode
update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jcmd to 
provide /usr/bin/jcmd (jcmd) in auto mode
Setting up default-jre-headless (2:1.8-58) ...
Setting up default-jdk-headless (2:1.8-58) ...
Setting up debhelper (11.1.6~bpo9+1) ...
Setting up pkg-php-tools (1.35) ...
Setting up dh-elpa (1.6) ...
Setting up javahelper (0.59) ...
Setting up lintian-build-deps (2.5.66) ...
Processing triggers for libc-bin (2.24-11+deb9u3) ...
Processing triggers for systemd (232-25+deb9u2) ...
Processing triggers for dictionaries-common (1.27.2) ...
aspell-autobuildhash: processing: en [en-common].
aspell-autobuildhash: processing: en [en-

Build failed in Jenkins: lintian-tests_sid #2786

2018-04-10 Thread jenkins

See 

--
[...truncated 219.19 KB...]
Adding debian:D-TRUST_Root_Class_3_CA_2_2009.pem
Adding debian:Cybertrust_Global_Root.pem
Adding debian:Comodo_Trusted_Services_root.pem
Adding debian:Comodo_Secure_Services_root.pem
Adding debian:Comodo_AAA_Services_root.pem
Adding debian:China_Internet_Network_Information_Center_EV_Certificates_Root.pem
Adding debian:Chambers_of_Commerce_Root_-_2008.pem
Adding debian:Certum_Trusted_Network_CA_2.pem
Adding debian:Certum_Trusted_Network_CA.pem
Adding debian:Certum_Root_CA.pem
Adding debian:Certplus_Root_CA_G2.pem
Adding debian:Certplus_Root_CA_G1.pem
Adding debian:Certplus_Class_2_Primary_CA.pem
Adding debian:Certinomis_-_Root_CA.pem
Warning: there was a problem reading the certificate file 
/etc/ssl/certs/Certinomis_-_Autorit?_Racine.pem. Message:
  /etc/ssl/certs/Certinomis_-_Autorit?_Racine.pem (No such file or directory)
Adding debian:Certigna.pem
Adding debian:Camerfirma_Global_Chambersign_Root.pem
Adding debian:Camerfirma_Chambers_of_Commerce_Root.pem
Adding debian:COMODO_RSA_Certification_Authority.pem
Adding debian:COMODO_ECC_Certification_Authority.pem
Adding debian:COMODO_Certification_Authority.pem
Adding debian:CNNIC_ROOT.pem
Adding debian:CFCA_EV_ROOT.pem
Adding debian:CA_Disig_Root_R2.pem
Adding debian:CA_Disig_Root_R1.pem
Adding debian:Buypass_Class_3_Root_CA.pem
Adding debian:Buypass_Class_2_Root_CA.pem
Adding debian:Baltimore_CyberTrust_Root.pem
Adding debian:Autoridad_de_Certificacion_Firmaprofesional_CIF_A62634068.pem
Adding debian:Atos_TrustedRoot_2011.pem
Adding debian:Amazon_Root_CA_4.pem
Adding debian:Amazon_Root_CA_3.pem
Adding debian:Amazon_Root_CA_2.pem
Adding debian:Amazon_Root_CA_1.pem
Adding debian:AffirmTrust_Premium_ECC.pem
Adding debian:AffirmTrust_Premium.pem
Adding debian:AffirmTrust_Networking.pem
Adding debian:AffirmTrust_Commercial.pem
Adding debian:AddTrust_Qualified_Certificates_Root.pem
Adding debian:AddTrust_Public_Services_Root.pem
Adding debian:AddTrust_Low-Value_Services_Root.pem
Adding debian:AddTrust_External_Root.pem
Adding debian:Actalis_Authentication_Root_CA.pem
Adding debian:AC_RAIZ_FNMT-RCM.pem
Adding debian:ACEDICOM_Root.pem
Adding debian:ACCVRAIZ1.pem
done.
Setting up openjdk-9-jdk-headless:amd64 (9.0.4+12-4) ...
update-alternatives: using /usr/lib/jvm/java-9-openjdk-amd64/bin/jlink to 
provide /usr/bin/jlink (jlink) in auto mode
update-alternatives: using /usr/lib/jvm/java-9-openjdk-amd64/bin/idlj to 
provide /usr/bin/idlj (idlj) in auto mode
update-alternatives: using /usr/lib/jvm/java-9-openjdk-amd64/bin/jdeps to 
provide /usr/bin/jdeps (jdeps) in auto mode
update-alternatives: using /usr/lib/jvm/java-9-openjdk-amd64/bin/wsimport to 
provide /usr/bin/wsimport (wsimport) in auto mode
update-alternatives: using /usr/lib/jvm/java-9-openjdk-amd64/bin/rmic to 
provide /usr/bin/rmic (rmic) in auto mode
update-alternatives: using /usr/lib/jvm/java-9-openjdk-amd64/bin/jinfo to 
provide /usr/bin/jinfo (jinfo) in auto mode
update-alternatives: using /usr/lib/jvm/java-9-openjdk-amd64/bin/jstat to 
provide /usr/bin/jstat (jstat) in auto mode
update-alternatives: using /usr/lib/jvm/java-9-openjdk-amd64/bin/javadoc to 
provide /usr/bin/javadoc (javadoc) in auto mode
update-alternatives: using /usr/lib/jvm/java-9-openjdk-amd64/bin/jmod to 
provide /usr/bin/jmod (jmod) in auto mode
update-alternatives: using /usr/lib/jvm/java-9-openjdk-amd64/bin/javah to 
provide /usr/bin/javah (javah) in auto mode
update-alternatives: using /usr/lib/jvm/java-9-openjdk-amd64/bin/jhsdb to 
provide /usr/bin/jhsdb (jhsdb) in auto mode
update-alternatives: using /usr/lib/jvm/java-9-openjdk-amd64/bin/jstack to 
provide /usr/bin/jstack (jstack) in auto mode
update-alternatives: using /usr/lib/jvm/java-9-openjdk-amd64/bin/jrunscript to 
provide /usr/bin/jrunscript (jrunscript) in auto mode
update-alternatives: using /usr/lib/jvm/java-9-openjdk-amd64/bin/javac to 
provide /usr/bin/javac (javac) in auto mode
update-alternatives: using /usr/lib/jvm/java-9-openjdk-amd64/bin/javap to 
provide /usr/bin/javap (javap) in auto mode
update-alternatives: using /usr/lib/jvm/java-9-openjdk-amd64/bin/jar to provide 
/usr/bin/jar (jar) in auto mode
update-alternatives: using /usr/lib/jvm/java-9-openjdk-amd64/bin/jaotc to 
provide /usr/bin/jaotc (jaotc) in auto mode
update-alternatives: using /usr/lib/jvm/java-9-openjdk-amd64/bin/policytool to 
provide /usr/bin/policytool (policytool) in auto mode
update-alternatives: using /usr/lib/jvm/java-9-openjdk-amd64/bin/schemagen to 
provide /usr/bin/schemagen (schemagen) in auto mode
update-alternatives: using /usr/lib/jvm/java-9-openjdk-amd64/bin/jshell to 
provide /usr/bin/jshell (jshell) in auto mode
update-alternatives: using /usr/lib/jvm/java-9-openjdk-amd64/bin/jps to provide 
/usr/bin/jps (jps) in auto mode
update-alternatives: using /usr/lib/jvm/java-9-openjdk-amd64/bin/xjc to provide 
/usr/bin/xjc (xjc) in a

Bug#895370: lintian: maintainer-script-should-not-use-recursive-chown-or-chmod should also look for find.exec.chown

2018-04-10 Thread Chris Lamb

Hi dkg!

> I note the first half of the regex looks for chown and chmod, but the
> last half looks only for chown.  maybe look for chmod on the last half
> too?

Ah, of course! Fixed in:

  
https://anonscm.debian.org/git/lintian/lintian.git/commit/?id=5b3351ed335e782f602ef276e906849bd401113b


> also, my last name has no "e" in it :P

Oh dear... I have no idea how that snuck in. Fixed in:

  
https://anonscm.debian.org/git/lintian/lintian.git/commit/?id=39ff631186abff93e1eafda77cc1dec3d351f509

> thanks for the prompt action, Lamby!

No problem. But on that note, I'm very much a "lamby" rather than
a "Lamby" ;-)


Best wishes,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

[lintian] branch master updated (39ff631 -> 5b3351e)

2018-04-10 Thread Chris Lamb

This is an automated email from the git hooks/post-receive script.

lamby pushed a change to branch master
in repository lintian.

  from  39ff631   Correct dkg's name in changelog entry.
   new  5b3351e   Also check for chmod calls, not just chown for find(1) 
for maintainer-script-should-not-use-recursive-chown-or-chmod. (re. #895370)

The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "adds" were already present in the repository and have only
been added to this reference.


Summary of changes:
 data/scripts/maintainer-script-bad-command| 2 +-
 debian/changelog  | 4 ++--
 t/tests/scripts-maintainer-general/debian/debian/postinst | 1 +
 t/tests/scripts-maintainer-general/tags   | 1 +
 4 files changed, 5 insertions(+), 3 deletions(-)

-- 
Alioth's /usr/local/bin/git-commit-notice on 
/srv/git.debian.org/git/lintian/lintian.git

[lintian] 01/01: Also check for chmod calls, not just chown for find(1) for maintainer-script-should-not-use-recursive-chown-or-chmod. (re. #895370)

2018-04-10 Thread Chris Lamb

This is an automated email from the git hooks/post-receive script.

lamby pushed a commit to branch master
in repository lintian.

commit 5b3351ed335e782f602ef276e906849bd401113b
Author: Chris Lamb 
Date:   Tue Apr 10 19:49:57 2018 +0100

Also check for chmod calls, not just chown for find(1) for 
maintainer-script-should-not-use-recursive-chown-or-chmod. (re. #895370)
---
 data/scripts/maintainer-script-bad-command| 2 +-
 debian/changelog  | 4 ++--
 t/tests/scripts-maintainer-general/debian/debian/postinst | 1 +
 t/tests/scripts-maintainer-general/tags   | 1 +
 4 files changed, 5 insertions(+), 3 deletions(-)

diff --git a/data/scripts/maintainer-script-bad-command 
b/data/scripts/maintainer-script-bad-command
index 6c2b606..1852a97 100644
--- a/data/scripts/maintainer-script-bad-command
+++ b/data/scripts/maintainer-script-bad-command
@@ -35,7 +35,7 @@ maintainer-script-should-not-use-dpkg-status-directly 
  ~~ 1 ~~^(base-fi
 maintainer-script-should-not-use-fc-cache   ~~ 0 
~~^(fontconfig)$  ~~  ~~${LEADIN}(?:/usr/bin/)?fc-cache(?:\s|\Z)
 maintainer-script-should-not-use-gconftool  ~~ 1 
~~^(gconf\d)$ ~~  ~~(?:/usr/bin/)?gconftool(?:-\d)?(?:\s|\Z)
 maintainer-script-should-not-use-install-sgmlcatalog~~ 1 ~~
~~  ~~\binstall-sgmlcatalog\b
-maintainer-script-should-not-use-recursive-chown-or-chmod   ~~ 1 ~~
~~  
~~\b(?:(?:chmod|chown).*(?:-R|--recursive)|find.*exec.*chown)\b
+maintainer-script-should-not-use-recursive-chown-or-chmod   ~~ 1 ~~
~~  
~~\b(?:(?:chmod|chown).*(?:-R|--recursive)|find.*exec.*(?:chmod|chown))\b
 maintainer-script-should-not-use-service~~ 1 ~~
~~  ~~${LEADIN}service\b
 maintainer-script-should-not-use-start-stop-daemon  ~~ 0 ~~
~~  ~~\bstart-stop-daemon(?=\s)(?!.*\s--stop\b)
 maintainer-script-should-not-use-update-alternatives-remove ~~ 1 ~~
~~^postrm$  ~~\b update\-alternatives\s+\-\-remove\b
diff --git a/debian/changelog b/debian/changelog
index e6a1d92..c3f2c05 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -26,8 +26,8 @@ lintian (2.5.82) UNRELEASED; urgency=medium
 
   * data/scripts/maintainer-script-bad-command:
 + [CL] Also check for find(1) calls when checking for maintainer
-  scripts that use a recursive chown.  Thanks to Daniel Kahn Gillmor
-  for the report.  (Closes: #895370)
+  scripts that use a recursive chmod or chown.  Thanks to Daniel Kahn
+  Gillmor for the report.  (Closes: #895370)
 
   * vendors/pureos/main/data/changes-file/derivative-versions:
 + [CL] Ensure that PureOS packages always end with (eg. pureosX).
diff --git a/t/tests/scripts-maintainer-general/debian/debian/postinst 
b/t/tests/scripts-maintainer-general/debian/debian/postinst
index 02c4a6b..f5d5803 100755
--- a/t/tests/scripts-maintainer-general/debian/debian/postinst
+++ b/t/tests/scripts-maintainer-general/debian/debian/postinst
@@ -217,5 +217,6 @@ chmod 777 -R /bad
 chmod 777 --recursive /bad
 chmod --recursive 777 /bad
 find /bad -maxdepth 2 -type d -exec chown root:root {} \; # (#895370)
+find /bad -maxdepth 2 -type d -exec chmod 777  # (#895370)
 
 #DEBHELPER#
diff --git a/t/tests/scripts-maintainer-general/tags 
b/t/tests/scripts-maintainer-general/tags
index 6beaeae..51e5cf3 100644
--- a/t/tests/scripts-maintainer-general/tags
+++ b/t/tests/scripts-maintainer-general/tags
@@ -50,6 +50,7 @@ W: scripts-maintainer-general: 
maintainer-script-should-not-use-recursive-chown-
 W: scripts-maintainer-general: 
maintainer-script-should-not-use-recursive-chown-or-chmod postinst:217
 W: scripts-maintainer-general: 
maintainer-script-should-not-use-recursive-chown-or-chmod postinst:218
 W: scripts-maintainer-general: 
maintainer-script-should-not-use-recursive-chown-or-chmod postinst:219
+W: scripts-maintainer-general: 
maintainer-script-should-not-use-recursive-chown-or-chmod postinst:220
 W: scripts-maintainer-general: 
maintainer-script-should-not-use-recursive-chown-or-chmod postinst:84
 W: scripts-maintainer-general: 
maintainer-script-should-not-use-start-stop-daemon postinst:138
 W: scripts-maintainer-general: 
maintainer-script-should-not-use-start-stop-daemon postinst:78

-- 
Alioth's /usr/local/bin/git-commit-notice on 
/srv/git.debian.org/git/lintian/lintian.git

[lintian] branch master updated (52e1bfa -> 39ff631)

2018-04-10 Thread Chris Lamb

This is an automated email from the git hooks/post-receive script.

lamby pushed a change to branch master
in repository lintian.

  from  52e1bfa   Also check for find(1) calls when checking for maintainer 
scripts that use a recursive chown. (Closes: #895370)
   new  39ff631   Correct dkg's name in changelog entry.

The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "adds" were already present in the repository and have only
been added to this reference.


Summary of changes:
 debian/changelog | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

-- 
Alioth's /usr/local/bin/git-commit-notice on 
/srv/git.debian.org/git/lintian/lintian.git

[lintian] 01/01: Correct dkg's name in changelog entry.

2018-04-10 Thread Chris Lamb

This is an automated email from the git hooks/post-receive script.

lamby pushed a commit to branch master
in repository lintian.

commit 39ff631186abff93e1eafda77cc1dec3d351f509
Author: Chris Lamb 
Date:   Tue Apr 10 19:45:19 2018 +0100

Correct dkg's name in changelog entry.
---
 debian/changelog | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/debian/changelog b/debian/changelog
index a19ef8c..e6a1d92 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -26,7 +26,7 @@ lintian (2.5.82) UNRELEASED; urgency=medium
 
   * data/scripts/maintainer-script-bad-command:
 + [CL] Also check for find(1) calls when checking for maintainer
-  scripts that use a recursive chown.  Thanks to Daniel Kahn Gillmore
+  scripts that use a recursive chown.  Thanks to Daniel Kahn Gillmor
   for the report.  (Closes: #895370)
 
   * vendors/pureos/main/data/changes-file/derivative-versions:

-- 
Alioth's /usr/local/bin/git-commit-notice on 
/srv/git.debian.org/git/lintian/lintian.git

Bug#895370: lintian: maintainer-script-should-not-use-recursive-chown-or-chmod should also look for find.exec.chown

2018-04-10 Thread Daniel Kahn Gillmor

On Tue 2018-04-10 18:37:06 +0100, Chris Lamb wrote:
> Thanks for looking at this. Fixed in Git with a testcase, pending upload:
>
>   
> https://anonscm.debian.org/git/lintian/lintian.git/commit/?id=52e1bfac52ddba315ba66778570eb00b10c473de

thanks for the prompt action, Lamby!

i note the first half of the regex looks for chown and chmod, but the
last half looks only for chown.  maybe look for chmod on the last half
too?

also, my last name has no "e" in it :P

> (Can you point to a package that appears to have moved to find(1) to bypass
> the Lintian warning? I looked at lava-server but could not see anything in
> the changelog that was relevant.)

https://salsa.debian.org/ruby-team/schleuder/commit/644ad3de296e3328ca6ed0e70a41b30515e33b4a

Regards,

--dkg


signature.asc
Description: PGP signature

Bug#895370: lintian: maintainer-script-should-not-use-recursive-chown-or-chmod should also look for find.exec.chown

2018-04-10 Thread Antoine Beaupre

On Tue, Apr 10, 2018 at 06:37:06PM +0100, Chris Lamb wrote:
> Thanks for looking at this. Fixed in Git with a testcase, pending upload:
> 
>   
> https://anonscm.debian.org/git/lintian/lintian.git/commit/?id=52e1bfac52ddba315ba66778570eb00b10c473de

Dang you're quick! :)

> (Can you point to a package that appears to have moved to find(1) to bypass
> the Lintian warning? I looked at lava-server but could not see anything in
> the changelog that was relevant.)

There are a bunch. An example dkg gave me is:

https://salsa.debian.org/ruby-team/schleuder/commit/644ad3de296e3328ca6ed0e70a41b30515e33b4a

then he also found this:

https://sources.debian.org/src/4store/1.1.6+20151109-2/debian/4store.init/?hl=47#L47

Then of course there's the broader:

https://codesearch.debian.net/search?q=find.*exec.*chown&perpkg=1

At the time of writing:

112256 files grepped (75 results)

Cheers!

A.


signature.asc
Description: PGP signature

Processed: Re: lintian: maintainer-script-should-not-use-recursive-chown-or-chmod should also look for find.exec.chown

2018-04-10 Thread Debian Bug Tracking System

Processing commands for cont...@bugs.debian.org:

> tags 895370 + pending
Bug #895370 [lintian] lintian: 
maintainer-script-should-not-use-recursive-chown-or-chmod should also look for 
find.*exec.*chown
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
895370: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895370
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#895370: lintian: maintainer-script-should-not-use-recursive-chown-or-chmod should also look for find.exec.chown

2018-04-10 Thread Chris Lamb

tags 895370 + pending
thanks

Hi dkg!

Thanks for looking at this. Fixed in Git with a testcase, pending upload:

  
https://anonscm.debian.org/git/lintian/lintian.git/commit/?id=52e1bfac52ddba315ba66778570eb00b10c473de

(Can you point to a package that appears to have moved to find(1) to bypass
the Lintian warning? I looked at lava-server but could not see anything in
the changelog that was relevant.)


Best wishes,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

[lintian] 01/01: Also check for find(1) calls when checking for maintainer scripts that use a recursive chown. (Closes: #895370)

2018-04-10 Thread Chris Lamb

This is an automated email from the git hooks/post-receive script.

lamby pushed a commit to branch master
in repository lintian.

commit 52e1bfac52ddba315ba66778570eb00b10c473de
Author: Chris Lamb 
Date:   Tue Apr 10 18:30:13 2018 +0100

Also check for find(1) calls when checking for maintainer scripts that use 
a recursive chown. (Closes: #895370)
---
 checks/scripts.desc   | 3 ++-
 data/scripts/maintainer-script-bad-command| 2 +-
 debian/changelog  | 5 +
 t/tests/scripts-maintainer-general/debian/debian/postinst | 1 +
 t/tests/scripts-maintainer-general/tags   | 1 +
 5 files changed, 10 insertions(+), 2 deletions(-)

diff --git a/checks/scripts.desc b/checks/scripts.desc
index eba0c8e..da057dc 100644
--- a/checks/scripts.desc
+++ b/checks/scripts.desc
@@ -817,7 +817,8 @@ Tag: 
maintainer-script-should-not-use-recursive-chown-or-chmod
 Severity: normal
 Certainty: certain
 Info: The maintainer script appears to call chmod or
- chown with an --recursive or -R argument.
+ chown with a --recursive/-R argument, or
+ uses find(1) in a similar manner.
  .
  This is vulnerable to hardlink attacks on mainline, non-Debian kernels
  that do not have fs.protected_hardlinks=1,
diff --git a/data/scripts/maintainer-script-bad-command 
b/data/scripts/maintainer-script-bad-command
index ef5a159..6c2b606 100644
--- a/data/scripts/maintainer-script-bad-command
+++ b/data/scripts/maintainer-script-bad-command
@@ -35,7 +35,7 @@ maintainer-script-should-not-use-dpkg-status-directly 
  ~~ 1 ~~^(base-fi
 maintainer-script-should-not-use-fc-cache   ~~ 0 
~~^(fontconfig)$  ~~  ~~${LEADIN}(?:/usr/bin/)?fc-cache(?:\s|\Z)
 maintainer-script-should-not-use-gconftool  ~~ 1 
~~^(gconf\d)$ ~~  ~~(?:/usr/bin/)?gconftool(?:-\d)?(?:\s|\Z)
 maintainer-script-should-not-use-install-sgmlcatalog~~ 1 ~~
~~  ~~\binstall-sgmlcatalog\b
-maintainer-script-should-not-use-recursive-chown-or-chmod   ~~ 1 ~~
~~  ~~\b(?:chmod|chown).*(?:-R|--recursive)\b
+maintainer-script-should-not-use-recursive-chown-or-chmod   ~~ 1 ~~
~~  
~~\b(?:(?:chmod|chown).*(?:-R|--recursive)|find.*exec.*chown)\b
 maintainer-script-should-not-use-service~~ 1 ~~
~~  ~~${LEADIN}service\b
 maintainer-script-should-not-use-start-stop-daemon  ~~ 0 ~~
~~  ~~\bstart-stop-daemon(?=\s)(?!.*\s--stop\b)
 maintainer-script-should-not-use-update-alternatives-remove ~~ 1 ~~
~~^postrm$  ~~\b update\-alternatives\s+\-\-remove\b
diff --git a/debian/changelog b/debian/changelog
index 593aa1c..a19ef8c 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -24,6 +24,11 @@ lintian (2.5.82) UNRELEASED; urgency=medium
   some currently-problematic packages such as gcc-8-cross-ports
   preventing the update of https://lintian.debian.org/.  (See #890873)
 
+  * data/scripts/maintainer-script-bad-command:
++ [CL] Also check for find(1) calls when checking for maintainer
+  scripts that use a recursive chown.  Thanks to Daniel Kahn Gillmore
+  for the report.  (Closes: #895370)
+
   * vendors/pureos/main/data/changes-file/derivative-versions:
 + [CL] Ensure that PureOS packages always end with (eg. pureosX).
   * vendors/pureos/main/data/fields/derivative-fields:
diff --git a/t/tests/scripts-maintainer-general/debian/debian/postinst 
b/t/tests/scripts-maintainer-general/debian/debian/postinst
index 706d7cf..02c4a6b 100755
--- a/t/tests/scripts-maintainer-general/debian/debian/postinst
+++ b/t/tests/scripts-maintainer-general/debian/debian/postinst
@@ -216,5 +216,6 @@ chmod -R 777 /bad
 chmod 777 -R /bad
 chmod 777 --recursive /bad
 chmod --recursive 777 /bad
+find /bad -maxdepth 2 -type d -exec chown root:root {} \; # (#895370)
 
 #DEBHELPER#
diff --git a/t/tests/scripts-maintainer-general/tags 
b/t/tests/scripts-maintainer-general/tags
index 2813747..6beaeae 100644
--- a/t/tests/scripts-maintainer-general/tags
+++ b/t/tests/scripts-maintainer-general/tags
@@ -49,6 +49,7 @@ W: scripts-maintainer-general: 
maintainer-script-should-not-use-recursive-chown-
 W: scripts-maintainer-general: 
maintainer-script-should-not-use-recursive-chown-or-chmod postinst:216
 W: scripts-maintainer-general: 
maintainer-script-should-not-use-recursive-chown-or-chmod postinst:217
 W: scripts-maintainer-general: 
maintainer-script-should-not-use-recursive-chown-or-chmod postinst:218
+W: scripts-maintainer-general: 
maintainer-script-should-not-use-recursive-chown-or-chmod postinst:219
 W: scripts-maintainer-general: 
maintainer-script-should-not-use-recursive-chown-or-chmod postinst:84
 W: scripts-maintainer-general: 
maintainer-script-should-not-use-start-stop-daemon postinst:138
 W: scripts-mai

[lintian] branch master updated (12be328 -> 52e1bfa)

2018-04-10 Thread Chris Lamb

This is an automated email from the git hooks/post-receive script.

lamby pushed a change to branch master
in repository lintian.

  from  12be328   Add missing changlog entries.
   new  52e1bfa   Also check for find(1) calls when checking for maintainer 
scripts that use a recursive chown. (Closes: #895370)

The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "adds" were already present in the repository and have only
been added to this reference.


Summary of changes:
 checks/scripts.desc   | 3 ++-
 data/scripts/maintainer-script-bad-command| 2 +-
 debian/changelog  | 5 +
 t/tests/scripts-maintainer-general/debian/debian/postinst | 1 +
 t/tests/scripts-maintainer-general/tags   | 1 +
 5 files changed, 10 insertions(+), 2 deletions(-)

-- 
Alioth's /usr/local/bin/git-commit-notice on 
/srv/git.debian.org/git/lintian/lintian.git

Bug#895370: lintian: maintainer-script-should-not-use-recursive-chown-or-chmod should also look for find.exec.chown

2018-04-10 Thread Daniel Kahn Gillmor

Package: lintian
Version: 2.5.81
Severity: normal

i've seen a few places in the debian archive where maintscripts or
initscripts avoid chown -R by using something like:


find /etc/lava-server/dispatcher.d/ -maxdepth 1 -exec chown 
$LAVA_SYS_USER:$LAVA_SYS_USER {}

 (the above is from lava-server.postinst; similar things found in
 openguides, 4store, schleuder, jwchat, firebird3.0, etc)

This presents the exact same risk as "chown -R", but it's not captured
at all by the current matcher.  even worse, it appears that some of
these techniques are done specifically because they think it avoids
the problem of chown -R (e.g. 4store.init has a TOCTOU race condition
that leaves it vulnerable, but is commented as "avoiding "chown -R
hardlink attacks")

I think the lintian test should check for something like:

   find.*exec.*chown

as well as looking for chown -R.

   --dkg



-- System Information:
Debian Release: buster/sid
  APT prefers testing-debug
  APT policy: (500, 'testing-debug'), (500, 'testing'), (500, 'oldstable'), 
(200, 'unstable-debug'), (200, 'unstable'), (1, 'experimental-debug'), (1, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.15.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages lintian depends on:
ii  binutils  2.30-8
ii  bzip2 1.0.6-8.1
ii  diffstat  1.61-1+b1
ii  dpkg  1.19.0.5
ii  file  1:5.32-2
ii  gettext   0.19.8.1-6
ii  intltool-debian   0.35.0+20060710.4
ii  libapt-pkg-perl   0.1.33
ii  libarchive-zip-perl   1.60-1
ii  libclass-accessor-perl0.51-1
ii  libclone-perl 0.39-1
ii  libdpkg-perl  1.19.0.5
ii  libemail-valid-perl   1.202-1
ii  libfile-basedir-perl  0.07-1
ii  libipc-run-perl   0.99-1
ii  liblist-moreutils-perl0.416-1+b3
ii  libparse-debianchangelog-perl 1.2.0-12
ii  libperl5.24 [libdigest-sha-perl]  5.24.1-7
ii  libperl5.26 [libdigest-sha-perl]  5.26.1-5
ii  libtext-levenshtein-perl  0.13-1
ii  libtimedate-perl  2.3000-2
ii  liburi-perl   1.73-1
ii  libxml-simple-perl2.25-1
ii  libyaml-libyaml-perl  0.69+repack-1
ii  man-db2.8.2-1
ii  patchutils0.3.4-2
ii  perl  5.26.1-5
ii  t1utils   1.41-2
ii  xz-utils  5.2.2-1.3

Versions of packages lintian recommends:
pn  libperlio-gzip-perl  

Versions of packages lintian suggests:
pn  binutils-multiarch 
ii  dpkg-dev   1.19.0.5
ii  libhtml-parser-perl3.72-3+b2
ii  libtext-template-perl  1.47-1

-- no debconf information

Cron lintian/reporting/harness --no-generate-reports -i

2018-04-10 Thread Lintian role account

Subroutine Cwd::fastcwd redefined at /usr/share/perl/5.24/XSLoader.pm line 114.
Subroutine Cwd::getcwd redefined at /usr/share/perl/5.24/XSLoader.pm line 114.
Subroutine Cwd::abs_path redefined at /usr/share/perl/5.24/XSLoader.pm line 114.

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

2018-04-10 Thread Chris Lamb

Neil,

> Lintian needs to stay in step with dpkg - dpkg does not generate a
> ${python3:Depends} substitution if none of the python content of the
> binary package is in /usr/bin or /usr/sbin.

Do you have a citation for that? I had not heard of this magic before.

> It's a git repo, things change... there is history ...
[…]
> > I also remain confused why we are using python3 here
[…]
> We have not made a release based solely on Python3 yet, so we have not
> uploaded to Debian

Sure, I understand things are in flux, but it is not making fixing
this issue for you any easier when quasi-canonical links change
within hours of linking them or even explicit links to .deb packages
do not even match the Python variant. :)


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

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

2018-04-10 Thread Neil Williams

On Tue, 10 Apr 2018 09:19:55 +0100
Chris Lamb  wrote:

> Hi Neil,
> 
> Apologies, but I am now more confused than ever. When I look at your
> link, ie.
> 
>https://github.com/Linaro/pkg-lava-server/blob/master/debian/control#L79
> 
> I see:
> 
>   libjs-jquery-ui, python3:any,

It's a git repo, things change... there is history ...

The historical version of the file at the time in question is:

https://github.com/Linaro/pkg-lava-server/blob/b1c7feeefc13fd5788f8c35411f4b3039380b483/debian/control

> 
> whilst you quoted in your previous mail:
> 
>   libjs-jquery-ui, python3 | python3-all | python3-dev |
> python3-all-dev
> 
> I also remain confused why we are using python3 here as the .deb I
> downloaded had a Python 2.x shebang.

The URL is a staging-repo containing nightly builds (plus some older
builds for some corner cases). The current URL for lava-dev is
http://images.validation.linaro.org/staging-repo/pool/main/l/lava-server/lava-dev_2018.2+7178.53c57de9-1+stretch_all.deb

The python scripts in that binary are all in /usr/share// and
all have a Python3 shebang, as will be all future builds.

Upstream are in the middle of transitioning the entire codebase from Python2
runtimes to Python3 runtime. We've had Python2 & Python3 unit test
support for a while, now we're dropping the packaging of anything
Python2 and moving the scripts to Python3.

We have not made a release based solely on Python3 yet, so we have not
uploaded to Debian, yet. So all changes, development, testing and
debugging is on a constantly moving master branch.

> > Maybe this is a bug in dpkg:  
> […]
> > Lintian needs to check for this behaviour of dpkg-gencontrol and
> > skip the python-script-but-no-python-dep check if there are no
> > scripts in usr/bin or usr/sbin in the binary package. dpkg seems to
> > not care about /usr/share.  
> 
> I am not sure what behaviour of dpkg you believe this is triggering
> and/or what is so special about /usr/share.

Irrespective of Python2 vs Python3, if a Python package installs
scripts *only* into /usr/share then dpkg-gencontrol does not populate
${python3:Depends} and also removes any mention of python3 |
python3-all | python3-dev | python3-all-dev which causes lintian to
complain.

> 
> Perhaps you are not calling dh-python entirely correctly? I am unsure
> and I would would have to leave it with you to debug.

I'm working around this whole mess with:
https://github.com/Linaro/pkg-lava-server/commit/ac3f2ef4e9b796f1176305f885fa815d0c756508

> 
> I still don't see (or, more likely, comprehend) any bug in Lintian
> here, sorry — the generated .debs I have seen appear to be triggering
> this correctly.

From the last email:

> Maybe it is because lava-dev puts all it's scripts
> into /usr/share/lava-server?
> 
> Indeed, artificially changing debian/lava-dev.install to put one of
> the scripts into /usr/sbin fixes the problem. The variable is
> substituted as python3:any and lintian doesn't complain (it complains
> about other things now but not this false positive).
> 
> Lintian needs to check for this behaviour of dpkg-gencontrol and skip
> the python-script-but-no-python-dep check if there are no scripts in
> usr/bin or usr/sbin in the binary package. dpkg seems to not care
> about /usr/share.
> 
> Arguably it's a bug in dpkg-gencontrol which could catch out binary
> packages which only put minimal Python3 scripts in /usr/share but it's
> unlikely to be caught that way as some dependency will end up being
> added by the maintainer on one python3 module or other.
> 
> Replacing the python3 | python3-all | python3-dev | python3-all-dev
> with python3:any actually fixes the problem but then that isn't needed
> except when all the scripts are installed into /usr/share/ so that's
> anachronistic and undocumented Debian "magic" but it's what I'll use
> to workaround this bug. Other binaries in the same control file don't
> need either:
> python3 | python3-all | python3-dev | python3-all-dev
> or
> python3:any

So, to summarise:

Lintian needs to stay in step with dpkg - dpkg does not generate a
${python3:Depends} substitution if none of the python content of the
binary package is in /usr/bin or /usr/sbin. Therefore, lintian should
not be checking / complaining about python-script-but-no-python-dep if
there are no python scripts installed into /usr/bin or /usr/sbin
because that raises a false positive. The packaging can assert what it
likes but unless a python script exists in /usr/bin or /usr/sbin, dpkg
ignores it and lintian gets it wrong.

Alternatively, lintian is interpreting Policy correctly and dpkg is
getting Policy wrong. Then, this bug needs to be reassigned to
dpkg-gencontrol so that dpkg *does* check /usr/share//
and then populate ${python3:Depends} so that lintian is happy.

What we should *not* be doing is forcing this kind of workaround by maintainers:
https://github.com/Linaro/pkg-lava-server/commit/ac3f2ef4e9b796f1176305f885fa815d0c756508

It all comes down to a python source pa

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

2018-04-10 Thread Chris Lamb

Hi Neil,

Apologies, but I am now more confused than ever. When I look at your
link, ie.

   https://github.com/Linaro/pkg-lava-server/blob/master/debian/control#L79

I see:

  libjs-jquery-ui, python3:any,

whilst you quoted in your previous mail:

  libjs-jquery-ui, python3 | python3-all | python3-dev | python3-all-dev

I also remain confused why we are using python3 here as the .deb I downloaded
had a Python 2.x shebang.

> Maybe this is a bug in dpkg:
[…]
> Lintian needs to check for this behaviour of dpkg-gencontrol and skip
> the python-script-but-no-python-dep check if there are no scripts in
> usr/bin or usr/sbin in the binary package. dpkg seems to not care
> about /usr/share.

I am not sure what behaviour of dpkg you believe this is triggering
and/or what is so special about /usr/share.

Perhaps you are not calling dh-python entirely correctly? I am unsure
and I would would have to leave it with you to debug.

I still don't see (or, more likely, comprehend) any bug in Lintian
here, sorry — the generated .debs I have seen appear to be triggering
this correctly.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Jenkins build is back to normal : lintian-tests_buster #767

Build failed in Jenkins: lintian-tests_buster #766

Jenkins build is back to normal : lintian-tests_stretch-backports #344

Jenkins build is back to normal : lintian-tests_sid #2787

Build failed in Jenkins: lintian-tests_stretch-backports #343

Build failed in Jenkins: lintian-tests_sid #2786

Bug#895370: lintian: maintainer-script-should-not-use-recursive-chown-or-chmod should also look for find.exec.chown

[lintian] branch master updated (39ff631 -> 5b3351e)

[lintian] 01/01: Also check for chmod calls, not just chown for find(1) for maintainer-script-should-not-use-recursive-chown-or-chmod. (re. #895370)

[lintian] branch master updated (52e1bfa -> 39ff631)

[lintian] 01/01: Correct dkg's name in changelog entry.

Bug#895370: lintian: maintainer-script-should-not-use-recursive-chown-or-chmod should also look for find.exec.chown

Bug#895370: lintian: maintainer-script-should-not-use-recursive-chown-or-chmod should also look for find.exec.chown

Processed: Re: lintian: maintainer-script-should-not-use-recursive-chown-or-chmod should also look for find.exec.chown

Bug#895370: lintian: maintainer-script-should-not-use-recursive-chown-or-chmod should also look for find.exec.chown

[lintian] 01/01: Also check for find(1) calls when checking for maintainer scripts that use a recursive chown. (Closes: #895370)

[lintian] branch master updated (12be328 -> 52e1bfa)

Bug#895370: lintian: maintainer-script-should-not-use-recursive-chown-or-chmod should also look for find.exec.chown

Cron lintian/reporting/harness --no-generate-reports -i

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

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

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

22 matches

Site Navigation

Mail list logo

Footer information