libtest-taint-perl 1.08-1 source package in Ubuntu

Changelog

libtest-taint-perl (1.08-1) unstable; urgency=medium

  * Team upload.

  [ Salvatore Bonaccorso ]
  * Update Vcs-* headers for switch to salsa.debian.org

  [ gregor herrmann ]
  * Import upstream version 1.08.
  * Add debian/upstream/metadata.
  * Drop Test-Taint-1.06-Test-taintedness-on-X-instead-of-environment-
    variabl.patch which was taken from an upstream ticket.
  * Annotate test-only build dependencies with <!nocheck>.
  * Declare compliance with Debian Policy 4.4.0.
  * Bump debhelper-compat to 12.
  * debian/watch: use uscan version 4.

 -- gregor herrmann <email address hidden>  Mon, 15 Jul 2019 17:42:57 -0300

Upload details

Uploaded by:
Debian Perl Group
Uploaded to:
Sid
Original maintainer:
Debian Perl Group
Architectures:
any
Section:
perl
Urgency:
Medium Urgency

See full publishing history Publishing

Series Pocket Published Component Section

Downloads

File Size SHA-256 Checksum
libtest-taint-perl_1.08-1.dsc 2.2 KiB 649163d228819f7d5c18eb1bde996a7df2707d5a8af73b7e897c811c135d2503
libtest-taint-perl_1.08.orig.tar.gz 13.1 KiB 5d594d4257352c93785024c63aa0a7b73d912ceca9611cd975ce83aab021a97d
libtest-taint-perl_1.08-1.debian.tar.xz 2.5 KiB 0c9cb82297ce8cf4ddb9b59e298c99a77253351735b12b581e42c8192226b8fd

No changes file available.

Binary packages built by this source

libtest-taint-perl: Module to test taintedness

 The Test::Taint module provides tools to test taintedness.
 Tainted data is data that comes from an unsafe source, such as the
 command line, or, in the case of web apps, any GET or POST transactions.
 Read the perlsec man page for details on why tainted data is bad,
 and how to untaint the data.
 .
 When you're writing unit tests for code that deals with tainted data,
 you'll want to have a way to provide tainted data for your routines to
 handle, and easy ways to check and report on the taintedness of your data,
 in standard Test::More style.

libtest-taint-perl-dbgsym: debug symbols for libtest-taint-perl