libpoe-component-client-ping-perl 1.175-1 source package in Ubuntu

Changelog

libpoe-component-client-ping-perl (1.175-1) unstable; urgency=medium

  * Team upload

  [ gregor herrmann ]
  * debian/control: update {versioned,alternative} (build) dependencies.

  [ Salvatore Bonaccorso ]
  * Change Vcs-Git to canonical URI (git://anonscm.debian.org)
  * Change search.cpan.org based URIs to metacpan.org based URIs

  [ Florian Schlichting ]
  * Import Upstream version 1.173, 1.174

  [ gregor herrmann ]
  * Strip trailing slash from metacpan URLs.

  [ Salvatore Bonaccorso ]
  * Update Vcs-Browser URL to cgit web frontend
  * debian/control: Use HTTPS transport protocol for Vcs-Git URI

  [ gregor herrmann ]
  * debian/copyright: change Copyright-Format 1.0 URL to HTTPS.

  [ Florian Schlichting ]
  * Import upstream version 1.175
  * Bump dh compat to level 9
  * Declare compliance with Debian Policy 4.1.0
  * Mark package autopkgtest-able

 -- Florian Schlichting <email address hidden>  Sat, 16 Sep 2017 22:49:09 +0200

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
Focal release universe perl
Bionic release universe perl

Builds

Bionic: [FULLYBUILT] amd64

Downloads

File Size SHA-256 Checksum
libpoe-component-client-ping-perl_1.175-1.dsc 2.2 KiB 7d8db1de91d5049a6f9a6bfa7877cdcb18bd3f74440a4d9d81319ddcab85e3ce
libpoe-component-client-ping-perl_1.175.orig.tar.gz 15.3 KiB 0c1136b136fa2e90ea422d19f8d11aefab02c3daee1b18b715adb708c15d9ddf
libpoe-component-client-ping-perl_1.175-1.debian.tar.xz 2.5 KiB 71152f9a5d1b80ec8a488e140f0f905d5ededc6d8697f90ee024c2732fb7ce82

Available diffs

No changes file available.

Binary packages built by this source

libpoe-component-client-ping-perl: ICMP ping client component for POE

 POE::Component::Client::Ping is an asynchronous, event driven client
 for ICMP ping. It accepts events containing the specifics of ICMP
 ping requests, and it returns events carrying the results of those
 pings.
 .
 Ping client components are not proper objects. Instead of being
 created, as most objects are, they are "spawned" as separate sessions.
 To avoid confusion (and hopefully not cause other confusion), they
 must be spawned with a spawn method, not created anew with a new
 one.