Processed: your mail

2018-04-03 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> unblock 731340 by 862373
Bug #731340 [lintian] lintian: Check if debian/upstream files are valid YAML
731340 was blocked by: 894747 862373
731340 was not blocking any bugs.
Removed blocking bug(s) of 731340: 862373
>
End of message, stopping processing here.

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

Build failed in Jenkins: lintian-tests_sid #2758

2018-04-03 Thread jenkins 
See 

--
[...truncated 245.05 KB...]
Adding debian:DigiCert_Global_Root_CA.pem
Adding debian:DigiCert_Assured_ID_Root_G3.pem
Adding debian:DigiCert_Assured_ID_Root_G2.pem
Adding debian:DigiCert_Assured_ID_Root_CA.pem
Adding debian:Deutsche_Telekom_Root_CA_2.pem
Adding debian:DST_Root_CA_X3.pem
Adding debian:DST_ACES_CA_X6.pem
Adding debian:D-TRUST_Root_Class_3_CA_2_EV_2009.pem
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 m

Processed: Re: Bug#540294 closed by Niels Thykier (Bug#540294: fixed in lintian 2.5.51)

2018-04-03 Thread Debian Bug Tracking System 
Processing control commands:

> reopen -1
Bug #540294 {Done: Niels Thykier } [lintian] [new check] 
Check if Vcs-* and changelog distribution match
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions lintian/2.5.51.

-- 
540294: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=540294
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#540294: closed by Niels Thykier (Bug#540294: fixed in lintian 2.5.51)

2018-04-03 Thread Simon McVittie 
Control: reopen -1

On Sun, 18 Jun 2017 at 09:21:14 +, Debian Bug Tracking System wrote:
> #540294: [new check] Check if Vcs-* and changelog distribution match
...
>* checks/changes-file.{desc,pm}:
>  + [BR] Apply patch by Simon McVittie to detect unreleased package
>uploaded to unstable and  mismatched .changes and
>Changes: distribution.  (Closes: #540294).

That was a different feature request, #542747 aka #647028 (which I
have now closed). It's sufficiently closely related to be confusing,
but not actually the same. I think I used the wrong bug number in my
git branch name when proposing that patch.

The feature request in #540294 has not been implemented, although I'm
not sure how feasible it really is.

smcv

Build failed in Jenkins: lintian-tests_buster #743

2018-04-03 Thread jenkins 
See 


Changes:

[lamby] Avoid false-positives in Mallard XML files;  tags are

[lamby] Re-enable YAML parsing of upstream metadata which was disabled in 2.5.51

[lamby] Add a minimum requirement for libyaml-libyaml-perl for $LoadBlessed;

--
[...truncated 248.45 KB...]
Adding debian:DigiCert_Assured_ID_Root_G3.pem
Adding debian:DigiCert_Assured_ID_Root_G2.pem
Adding debian:DigiCert_Assured_ID_Root_CA.pem
Adding debian:Deutsche_Telekom_Root_CA_2.pem
Adding debian:DST_Root_CA_X3.pem
Adding debian:DST_ACES_CA_X6.pem
Adding debian:D-TRUST_Root_Class_3_CA_2_EV_2009.pem
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-3) ...
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

Build failed in Jenkins: lintian-tests_sid #2757

2018-04-03 Thread jenkins 
See 


Changes:

[lamby] Re-enable YAML parsing of upstream metadata which was disabled in 2.5.51

[lamby] Add a minimum requirement for libyaml-libyaml-perl for $LoadBlessed;

--
[...truncated 245.06 KB...]
Adding debian:DigiCert_Global_Root_CA.pem
Adding debian:DigiCert_Assured_ID_Root_G3.pem
Adding debian:DigiCert_Assured_ID_Root_G2.pem
Adding debian:DigiCert_Assured_ID_Root_CA.pem
Adding debian:Deutsche_Telekom_Root_CA_2.pem
Adding debian:DST_Root_CA_X3.pem
Adding debian:DST_ACES_CA_X6.pem
Adding debian:D-TRUST_Root_Class_3_CA_2_EV_2009.pem
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 t

Processed: unarchiving 540294

2018-04-03 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> unarchive 540294
Bug #540294 {Done: Niels Thykier } [lintian] [new check] 
Check if Vcs-* and changelog distribution match
Unarchived Bug 540294
> thanks
Stopping processing here.

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

Bug#881491: lintian: update gir checks for gobject-introspection/1.54.1-3 mini-policy

2018-04-03 Thread Simon McVittie 
On Sun, 12 Nov 2017 at 12:35:40 +, Simon McVittie wrote:
> gobject-introspection/1.54.1-3 [contains] GIR mini-policy
> updates aimed at reducing false positives from Lintian.
...
> This gives Lintian enough information to avoid some unnecessary warnings
> when the attached patches are applied.

On Sun, 12 Nov 2017 at 13:29:05 +, Simon McVittie wrote:
> Looking at the archive's Lintian warnings, we also need to specify what
> to do about the rare typelibs that contain underscores (like v_sim)

I've rebased these patches (no changes) and pushed them to:

https://salsa.debian.org/smcv/lintian.git -b gir-881491

Reviews welcome. They still pass tests against current Lintian, after I
re-wrap an (unrelated) over-long line in d/changelog that trips a coding
style check.

The mini-policy change that mandates the same thing checked by the last
commit was released in gobject-introspection/1.54.1-4 and has been in
buster since late December.

Most (all?) GNOME packages already comply with the new mini-policy, so
applying these patches would fix many of their false-positives.

Thanks,
smcv

Bug#542747: marked as done ([checks/changes-file] check mismatch between Distribution and Changes in *.changes)

2018-04-03 Thread Debian Bug Tracking System 
Your message dated Tue, 3 Apr 2018 23:34:39 +0100
with message-id <20180403223439.ga6...@espresso.pseudorandom.co.uk>
and subject line Re: Bug#542747: [frontend] check mismatch between Distribution 
and Changes in *.changes
has caused the Debian Bug report #542747,
regarding [checks/changes-file] check mismatch between Distribution and Changes 
in *.changes
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 ow...@bugs.debian.org
immediately.)


-- 
542747: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=542747
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: lintian
Version: 2.2.14
Severity: wishlist

While we can't easily check for mismatches between the *.changes file
and the debian/changelog file in the source package, the latter is
copied into *.changes as the Changes field.  We can therefore check
whether the distribution in the first line of the Changes field matches
the Distribution.

I think we only want to do this check if the first line of the Changes
file says UNRELEASED, since there are valid use cases for a mismatch
otherwise.  But in the UNRELEASED case, that means that someone forgot
to update debian/changelog and only modified what went into the
Distribution header, which deserves a tag.

-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)

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

Versions of packages lintian depends on:
ii  binutils  2.19.51.20090723-1 The GNU assembler, linker and bina
ii  diffstat  1.47-1 produces graph of changes introduc
ii  dpkg-dev  1.15.3.1   Debian package development tools
ii  file  5.03-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  libapt-pkg-perl   0.1.24 Perl interface to libapt-pkg
ii  libipc-run-perl   0.84-1 Perl module for running processes
ii  libparse-debianchange 1.1.1-2parse Debian changelogs and output
ii  libtimedate-perl  1.1600-9   Time and date functions for Perl
ii  liburi-perl   1.37+dfsg-1Manipulates and accesses URI strin
ii  man-db2.5.5-3on-line manual pager
ii  perl [libdigest-sha-p 5.10.0-24  Larry Wall's Practical Extraction 

lintian recommends no packages.

Versions of packages lintian suggests:
pn  binutils-multiarch (no description available)
ii  libtext-template-perl 1.45-1 Text::Template perl module
ii  man-db2.5.5-3on-line manual pager

-- no debconf information


--- End Message ---
--- Begin Message ---
Version: 2.5.51

On Thu, 23 Feb 2017 at 13:44:07 +, Simon McVittie wrote:
> On Thu, 20 Aug 2009 at 23:07:38 -0700, Russ Allbery wrote:
> > While we can't easily check for mismatches between the *.changes file
> > and the debian/changelog file in the source package, the latter is
> > copied into *.changes as the Changes field.  We can therefore check
> > whether the distribution in the first line of the Changes field matches
> > the Distribution.
> 
> This has come up on -devel again, which reminded me that this didn't get
> merged.

It was merged a few months later, in June 2017 (but unfortunately
mislabelled as closing Bug #540294 - I'm not sure where that bug number
came from, it seems to have been my mistake).

smcv--- End Message ---

Bug#647028: marked as done (lintian: warn when changelog contains UNRELEASED even if .changes contains something valid)

2018-04-03 Thread Debian Bug Tracking System 
Your message dated Tue, 3 Apr 2018 23:34:39 +0100
with message-id <20180403223439.ga6...@espresso.pseudorandom.co.uk>
and subject line Re: Bug#542747: [frontend] check mismatch between Distribution 
and Changes in *.changes
has caused the Debian Bug report #542747,
regarding lintian: warn when changelog contains UNRELEASED even if .changes 
contains something valid
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 ow...@bugs.debian.org
immediately.)


-- 
542747: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=542747
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: lintian
Version: 2.5.3
Severity: wishlist

I build my package with sbuild and it writes the Distribution
field in the .changes according to the parameter given on the command
line.

I recently had the case that I have left UNRELEASED in debian/changelog
and built my package with sbuild and lintian did not warn me.

I'm not sure what the proper solution is. Ideally it would detect the
mismatch beween the .changes and the changelog in the source package but
I guess it's not easy.

-- System Information:
Debian Release: wheezy/sid
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 
'unstable'), (500, 'testing'), (500, 'stable'), (150, 'experimental')
Architecture: i386 (x86_64)

Kernel: Linux 3.0.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages lintian depends on:
ii  binutils   2.21.90.20111025-1 
ii  bzip2  1.0.5-7
ii  diffstat   1.54-1 
ii  file   5.09-2 
ii  gettext0.18.1.1-5 
ii  intltool-debian0.35.0+20060710.1  
ii  libapt-pkg-perl0.1.25 
ii  libclass-accessor-perl 0.34-1 
ii  libdpkg-perl   1.16.2~49.gbp8cc36f
ii  libemail-valid-perl0.185-1
ii  libipc-run-perl0.90-1 
ii  libparse-debianchangelog-perl  1.2.0-1
ii  libtimedate-perl   1.2000-1   
ii  liburi-perl1.59-1 
ii  locales2.13-21
ii  locales-all [locales]  2.13-21
ii  man-db 2.6.0.2-2  
ii  patchutils 0.3.2-1
ii  perl [libdigest-sha-perl]  5.12.4-6   
ii  unzip  6.0-5  

lintian recommends no packages.

Versions of packages lintian suggests:
ii  binutils-multiarch
ii  dpkg-dev   1.16.2~49.gbp8cc36f  
ii  libhtml-parser-perl3.69-1   
ii  libtext-template-perl  1.45-2   
ii  man-db 2.6.0.2-2
ii  xz-utils   5.1.1alpha+20110809-3

-- no debconf information


--- End Message ---
--- Begin Message ---
Version: 2.5.51

On Thu, 23 Feb 2017 at 13:44:07 +, Simon McVittie wrote:
> On Thu, 20 Aug 2009 at 23:07:38 -0700, Russ Allbery wrote:
> > While we can't easily check for mismatches between the *.changes file
> > and the debian/changelog file in the source package, the latter is
> > copied into *.changes as the Changes field.  We can therefore check
> > whether the distribution in the first line of the Changes field matches
> > the Distribution.
> 
> This has come up on -devel again, which reminded me that this didn't get
> merged.

It was merged a few months later, in June 2017 (but unfortunately
mislabelled as closing Bug #540294 - I'm not sure where that bug number
came from, it seems to have been my mistake).

smcv--- End Message ---

[lintian] 01/01: Add a minimum requirement for libyaml-libyaml-perl for $LoadBlessed; thanks Mattia!

2018-04-03 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 4db80edb1b2f91d76e6330998f7182a61b35a682
Author: Chris Lamb 
Date:   Tue Apr 3 22:38:30 2018 +0100

Add a minimum requirement for libyaml-libyaml-perl for $LoadBlessed; thanks 
Mattia!
---
 debian/control | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/debian/control b/debian/control
index 8bdf463..6337ab4 100644
--- a/debian/control
+++ b/debian/control
@@ -55,7 +55,7 @@ Build-Depends: aspell ,
libtext-template-perl ,
libtimedate-perl ,
liburi-perl ,
-   libyaml-libyaml-perl ,
+   libyaml-libyaml-perl (>= 0.69) ,
libxml-simple-perl ,
man-db ,
node-uglify ,
@@ -102,7 +102,7 @@ Depends: binutils,
  libtext-levenshtein-perl,
  libtimedate-perl,
  liburi-perl,
- libyaml-libyaml-perl,
+ libyaml-libyaml-perl (>= 0.69),
  libxml-simple-perl,
  man-db,
  patchutils,

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

[lintian] branch master updated (fd55f0d -> 4db80ed)

2018-04-03 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  fd55f0d   Re-enable YAML parsing of upstream metadata which was 
disabled in 2.5.51 (via #861958) to close CVE-2017-8829 as we can now use the 
$LoadBlessed option of YAML:XS. (Closes: #894747)
   new  4db80ed   Add a minimum requirement for libyaml-libyaml-perl for 
$LoadBlessed; thanks Mattia!

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/control | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

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

Processed: Re: lintian: Re-enable YAML parsing for d/upstream/metadata files

2018-04-03 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> tags 894747 + pending
Bug #894747 [lintian] lintian: Re-enable YAML parsing for d/upstream/metadata 
files
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#894747: lintian: Re-enable YAML parsing for d/upstream/metadata files

2018-04-03 Thread Chris Lamb 
tags 894747 + pending
thanks

Thanks Dylan — fixed in Git, pending upload:

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


Regards,

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

[lintian] 01/01: Re-enable YAML parsing of upstream metadata which was disabled in 2.5.51 (via #861958) to close CVE-2017-8829 as we can now use the $LoadBlessed option of YAML:XS. (Closes: #894747)

2018-04-03 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 fd55f0d4df464b05446573768ac7826530d3c308
Author: Chris Lamb 
Date:   Tue Apr 3 22:31:47 2018 +0100

Re-enable YAML parsing of upstream metadata which was disabled in 2.5.51 
(via #861958) to close CVE-2017-8829 as we can now use the $LoadBlessed option 
of YAML:XS. (Closes: #894747)
---
 checks/upstream-metadata.pm| 3 ++-
 debian/changelog   | 5 +
 t/tests/upstream-metadata-invalid-yml/skip | 1 -
 3 files changed, 7 insertions(+), 2 deletions(-)

diff --git a/checks/upstream-metadata.pm b/checks/upstream-metadata.pm
index c9d347b..4e2da86 100644
--- a/checks/upstream-metadata.pm
+++ b/checks/upstream-metadata.pm
@@ -27,6 +27,8 @@ use Lintian::Tags qw(tag);
 
 use YAML::XS;
 
+$YAML::XS::LoadBlessed = 0;
+
 sub run {
 my (undef, undef, $info) = @_;
 my $yamlfile = $info->index_resolved_path('debian/upstream/metadata');
@@ -38,7 +40,6 @@ sub run {
 
 if ($yamlfile->is_open_ok) {
 my $yaml;
-return if 1; # YAML::XS executes code
 eval { $yaml = YAML::XS::LoadFile($yamlfile->fs_path); };
 if (!$yaml) {
 my $msg;
diff --git a/debian/changelog b/debian/changelog
index 302dc51..c3017c1 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -27,6 +27,11 @@ lintian (2.5.81) UNRELEASED; urgency=medium
 + [CL] Apply patch from Thomas Dallmair to avoid false positives in the
   udev-rule-missing-subsystem tag when SUBSYSTEM GOTO is not the last
   "GOTO" statement.  Thanks!  (Closes: #894356)
+  * checks/upstream-metadata.pm:
++ Re-enable YAML parsing of upstream metadata which was disabled in
+  2.5.51 (via #861958) to close CVE-2017-8829 as we can now use the
+  $LoadBlessed option of YAML:XS. Thanks to Dylan Aïssi for the report.
+  (Closes: #894747)
 
   * lib/Lintian/Check.pm:
 + [CL] Avoid false positives in spelling detection by allowing "(s)"
diff --git a/t/tests/upstream-metadata-invalid-yml/skip 
b/t/tests/upstream-metadata-invalid-yml/skip
deleted file mode 100644
index d623a2b..000
--- a/t/tests/upstream-metadata-invalid-yml/skip
+++ /dev/null
@@ -1 +0,0 @@
-YAML::XS executes code by default and code has not been converted
\ No newline at end of file

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

[lintian] branch master updated (b3fd60a -> fd55f0d)

2018-04-03 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  b3fd60a   Avoid false-positives in Mallard XML files;  tags are anchor elements and not followed automatically. (Closes: 
#894690)
   new  fd55f0d   Re-enable YAML parsing of upstream metadata which was 
disabled in 2.5.51 (via #861958) to close CVE-2017-8829 as we can now use the 
$LoadBlessed option of YAML:XS. (Closes: #894747)

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/upstream-metadata.pm| 3 ++-
 debian/changelog   | 5 +
 t/tests/upstream-metadata-invalid-yml/skip | 1 -
 3 files changed, 7 insertions(+), 2 deletions(-)
 delete mode 100644 t/tests/upstream-metadata-invalid-yml/skip

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

Bug#894690: lintian: false positives for privacy-breach-generic when Mallard docs have a

2018-04-03 Thread Chris Lamb 
tags 894690 + pending
thanks

Hi Simon,

Thanks for the report. I've fixed in Git with a testcase, pending upload:

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


Regards,

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

Processed: Re: lintian: false positives for privacy-breach-generic when Mallard docs have a

2018-04-03 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> tags 894690 + pending
Bug #894690 [lintian] lintian: false positives for privacy-breach-generic when 
Mallard docs have a 
Added tag(s) pending.
> thanks
Stopping processing here.

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

[lintian] branch master updated (cd397b8 -> b3fd60a)

2018-04-03 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  cd397b8   spelling: Add another correction
   new  b3fd60a   Avoid false-positives in Mallard XML files;  tags are anchor elements and not followed automatically. (Closes: 
#894690)

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/files.pm|  9 +++
 debian/changelog   |  3 +
 .../mallard-falsepositive.xml  | 64 ++
 3 files changed, 76 insertions(+)
 create mode 100644 
t/tests/files-privacybreach/debian/src/privacy-breach-generic/mallard-falsepositive.xml

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

[lintian] 01/01: Avoid false-positives in Mallard XML files; tags are anchor elements and not followed automatically. (Closes: #894690)

2018-04-03 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 b3fd60aa18eebbe9db8455e4a31dbdb3e64541d6
Author: Chris Lamb 
Date:   Tue Apr 3 22:18:09 2018 +0100

Avoid false-positives in Mallard XML files;  tags are 
anchor elements and not followed automatically. (Closes: #894690)
---
 checks/files.pm|  9 +++
 debian/changelog   |  3 +
 .../mallard-falsepositive.xml  | 64 ++
 3 files changed, 76 insertions(+)

diff --git a/checks/files.pm b/checks/files.pm
index 67ec724..4f7d909 100644
--- a/checks/files.pm
+++ b/checks/files.pm
@@ -2092,6 +2092,15 @@ sub _check_tag_url_privacy_breach {
 return;
 }
 
+# In Mallard XML,  is a clickable anchor that will not be
+# followed automatically.
+if($file->basename =~ '.xml$'
+&& $tagattr eq 'link'
+&& $file->file_contents
+=~ qr{ xmlns="http://projectmallard\.org/1\.0/"}) {
+return;
+}
+
 # track well known site
 foreach my $breaker ($PRIVACY_BREAKER_WEBSITES->all) {
 my $value = $PRIVACY_BREAKER_WEBSITES->value($breaker);
diff --git a/debian/changelog b/debian/changelog
index 4c69553..302dc51 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -20,6 +20,9 @@ lintian (2.5.81) UNRELEASED; urgency=medium
 + [CL] Add .ogg files to the list of non-license file extensions to
   avoid a false-positive in extra-license-file. Thanks to Innocent De
   Marchi for the report.  (Closes: #894139)
++ [CL] Avoid false-positives in Mallard XML files; 
+  tags are anchor element and not followed automatically. Thanks to
+  Simon McVittie for the report.  (Closes: #894690)
   * checks/udev.pm:
 + [CL] Apply patch from Thomas Dallmair to avoid false positives in the
   udev-rule-missing-subsystem tag when SUBSYSTEM GOTO is not the last
diff --git 
a/t/tests/files-privacybreach/debian/src/privacy-breach-generic/mallard-falsepositive.xml
 
b/t/tests/files-privacybreach/debian/src/privacy-breach-generic/mallard-falsepositive.xml
new file mode 100644
index 000..86ada9b
--- /dev/null
+++ 
b/t/tests/files-privacybreach/debian/src/privacy-breach-generic/mallard-falsepositive.xml
@@ -0,0 +1,64 @@
+http://projectmallard.org/1.0/";>
+
+Sender:
+The sender's email address or the name of the sender.
+
+Recipients:
+The recipients of the message.
+
+CC:
+Only the CC recipients of the message.
+
+BCC:
+Only the BCC recipients of the message. Obviously this can only be applied 
to outgoing filters.
+
+Sender or Recipients:
+The sender's email address or the name of the sender or the recipients of 
the message.
+
+Subject:
+The subject line of the message.
+
+Specific Header:
+Any header including custom 
ones.
+If a message uses a header more than once, Evolution pays 
attention only to the first instance, even if the message defines the header 
differently the second time. For example, if a message declares the 
Resent-From: header as "engineer...@example.com" and then restates it as 
"market...@example.com", Evolution filters as though the second 
declaration did not occur. To filter on messages that use headers multiple 
times, use a regular expression.
+
+Message Body:
+Searches in the actual text of the message.
+
+Expression:
+(For programmers only) Match a message according to an expression you write 
in the Scheme language used to define filters 
in Evolution.
+
+Free Form Expression:
+(For advanced users only) Combine numerous conditions by using a https://bugzilla.gnome.org/show_bug.cgi?id=550796#c10";>special 
syntax.
+
+Date sent:
+Filters messages according to the date on which they were sent. First, 
choose the conditions you want a message to meet, such as before a given date 
or after a given date. Then choose the time. The filter compares the message's 
time stamp to the system clock when the filter is run, or to a specific time 
and date you choose from a calendar. You can also have it look for a message 
within a range of time relative to the filter, such as two to four days 
ago.
+
+Date received:
+This works the same way as the Date Sent option, except that it compares 
the time you received the message with the dates you specify.
+
+Label:
+Messages can have labels of Important, 
Work, Personal, To Do, or Later. You can set labels with other filters or 
manually.
+
+Score:
+Sets the message score to any whole number greater than 0. You can have one 
filter set or change a message score, and then set up another filter to move 
the messages you have scored. A message score is not based on anything in 
particular: it is simply a number you can assign to messages so other filters 
can process them.
+
+Size (kB):
+Sorts based on the size of the message in kilobytes.
+
+Status:
+Filters according to the status of a message. The status can be Replied To, 
Draft, Important, Read, or

Bug#894747: lintian: Re-enable YAML parsing for d/upstream/metadata files

2018-04-03 Thread Dylan Aïssi 
Package: lintian
Version: 2.5.80
Severity: wishlist
Control: block 731340 by -1

Hi,

Currently, the lintian checks for validity of d/u/metadata are
disabled since 2.5.50.4 [1] due to a security problem [2]
(CVE-2017-8829), but now we can safety use YAML::XS with the
$LoadBlessed option [3]. I wondering if we can re-enable the
d/u/metadata checks in lintian using the safety method?

Best,
Dylan

[1] 
https://anonscm.debian.org/git/lintian/lintian.git/commit/checks/upstream-metadata.pm?id=6119d49c3b
[2] https://bugs.debian.org/861958
[3] https://bugs.debian.org/862373#59

Processed: lintian: Re-enable YAML parsing for d/upstream/metadata files

2018-04-03 Thread Debian Bug Tracking System 
Processing control commands:

> block 731340 by -1
Bug #731340 [lintian] lintian: Check if debian/upstream files are valid YAML
731340 was blocked by: 862373
731340 was not blocking any bugs.
Added blocking bug(s) of 731340: 894747

-- 
731340: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=731340
894747: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894747
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

[lintian] branch master updated (e416c20 -> cd397b8)

2018-04-03 Thread Paul Wise 
This is an automated email from the git hooks/post-receive script.

pabs pushed a change to branch master
in repository lintian.

  from  e416c20   spelling: Add another correction
   new  cd397b8   spelling: Add another correction

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/spelling/corrections | 1 +
 1 file changed, 1 insertion(+)

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

[lintian] 01/01: spelling: Add another correction

2018-04-03 Thread Paul Wise 
This is an automated email from the git hooks/post-receive script.

pabs pushed a commit to branch master
in repository lintian.

commit cd397b8f0b1f238e18437e2cb5cafa8604f0124d
Author: Paul Wise 
Date:   Tue Apr 3 17:21:43 2018 +0800

spelling: Add another correction
---
 data/spelling/corrections | 1 +
 1 file changed, 1 insertion(+)

diff --git a/data/spelling/corrections b/data/spelling/corrections
index 52e527c..0554085 100644
--- a/data/spelling/corrections
+++ b/data/spelling/corrections
@@ -3523,6 +3523,7 @@ sheduled||scheduled
 shedule||schedule
 shedules||schedules
 sheduling||scheduling
+shiped||shipped
 shoud||should
 should'nt||shouldn't
 shouldnt||shouldn't

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

Bug#894690: lintian: false positives for privacy-breach-generic when Mallard docs have a

2018-04-03 Thread Simon McVittie 
Package: lintian
Version: 2.5.80
Severity: normal

Running Lintian against evolution reports lots of instances of
privacy-breach-generic, for example:

> usr/share/help/C/evolution/xinclude-filter-vfolder-conditions.xml [ href="https://bugzilla.gnome.org/show_bug.cgi?id=550796#c10";>] 
> (https://bugzilla.gnome.org/show_bug.cgi?id=550796#c10)
> usr/share/help/C/evolution/xinclude-filter-vfolder-conditions.xml [ href="https://en.wikipedia.org/wiki/regular_expression";>] 
> (https://en.wikipedia.org/wiki/regular_expression)

These are false positives: in Mallard XML,  is a clickable link that
will not be followed automatically, corresponding to  in HTML.
Mallard can be detected reasonably reliably by looking for
qr{ xmlns="http://projectmallard\.org/1\.0/"} in the first few lines.

Regards,
smcv