libtest-distribution-perl 2.00-6 source package in Ubuntu

Changelog

libtest-distribution-perl (2.00-6) unstable; urgency=medium

  [ Salvatore Bonaccorso ]
  * debian/control: Use HTTPS transport protocol for Vcs-Git URI

  [ gregor herrmann ]
  * Change bugtracker URL(s) to HTTPS.
  * debian/copyright: change Copyright-Format 1.0 URL to HTTPS.
  * Remove Jose Luis Rivas from Uploaders. Thanks for your work!

  [ Damyan Ivanov ]
  * change Priority from 'extra' to 'optional'

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

  [ gregor herrmann ]
  * debian/watch: use uscan version 4.

 -- Jelmer Vernooij <email address hidden>  Fri, 17 Jun 2022 12:05:49 +0100

Upload details

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

See full publishing history Publishing

Series Pocket Published Component Section

Builds

Kinetic: [FULLYBUILT] amd64

Downloads

File Size SHA-256 Checksum
libtest-distribution-perl_2.00-6.dsc 2.2 KiB 17373799d7760fec54c5e45466de028c959620d527ffac51eef6301c84f50b0f
libtest-distribution-perl_2.00.orig.tar.gz 11.1 KiB 50ecd07fb6cab7b2b2a73b5526ee43b90e77734c9bcec95ce8822b9c0a912b68
libtest-distribution-perl_2.00-6.debian.tar.xz 5.6 KiB 883e7d1b2bf05462045ef0289aaed386c0306b7f484cf9d4544b34c506cfe460

Available diffs

No changes file available.

Binary packages built by this source

libtest-distribution-perl: perform tests on all modules of a distribution

 When using Test::Distribution in a test script, it goes through all the
 modules in your distribution, checks their POD, checks that they compile ok
 and checks that they all define a $VERSION.
 .
 This module also performs a number of tests on the distribution itself. It
 checks that your files match your SIGNATURE file if you have one. It checks
 that your distribution isn't missing certain 'core' description files. It
 checks to see you haven't missed out listing any pre-requisites in Makefile.PL
 .
 It defines its own testing plan, so you usually don't use it in conjunction
 with other Test::* modules in the same file. It's recommended that you just
 create a one-line test script as shown in the SYNOPSIS above. However, there
 are options.