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

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://b

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

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/correct

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

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

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

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=7313

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

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 wond

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

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 an

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

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 auto

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

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

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

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..

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

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-

[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)

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 dis

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

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 `

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

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-

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

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

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

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 $L

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

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] c

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

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 chan

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

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.

Processed: unarchiving 540294

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

Build failed in Jenkins: lintian-tests_sid #2757

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; -

Build failed in Jenkins: lintian-tests_buster #743

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-liby

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

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

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

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 reope

Build failed in Jenkins: lintian-tests_sid #2758

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:Di

Processed: your mail

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 proce