Ubuntu
libtest-poe-server-tcp-perl package

libtest-poe-server-tcp-perl 1.20-2 source package in Ubuntu

Changelog

libtest-poe-server-tcp-perl (1.20-2) unstable; urgency=medium

  [ gregor herrmann ]
  * debian/copyright: change Copyright-Format 1.0 URL to HTTPS.
  * Remove Antonio Radici from Uploaders. Thanks for your work!
  * Remove Jonathan Yu from Uploaders. Thanks for your work!
  * Remove Nathan Handler from Uploaders. Thanks for your work!
  * Remove Ryan Niebur from Uploaders. Thanks for your work!

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

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

  [ Debian Janitor ]
  * Bump debhelper from old 9 to 12.
  * Set debhelper-compat version in Build-Depends.
  * Set upstream metadata fields: Bug-Database, Bug-Submit.
  * Remove obsolete fields Contact, Name from debian/upstream/metadata
    (already present in machine-readable debian/copyright).

 -- Jelmer Vernooij <email address hidden>  Tue, 28 Jun 2022 19:17:43 +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-poe-server-tcp-perl_1.20-2.dsc 2.2 KiB dba413a7c5376a49455ce06413cca917087730d9bdc17b55cdf4f20bbea944d4
libtest-poe-server-tcp-perl_1.20.orig.tar.gz 21.9 KiB 9368ceb63580f0f3a877a9295268cbdab538e399e67c0cb5e7d175cac0042c5c
libtest-poe-server-tcp-perl_1.20-2.debian.tar.xz 3.3 KiB dcb48633c516d8c446496d25dac7ace48a07d0dc860f70d24d41f453c82fe14f

Available diffs

No changes file available.

Binary packages built by this source

libtest-poe-server-tcp-perl: test framework for TCP client libraries using POE

 Test::POE::Server::TCP is a Perl Object Environment (POE, see libpoe-perl)
 component that provides a TCP server framework for inclusion in your client
 module's test cases. Once registered, a session will receive events related
 to client connections, disconnections, input and any flushed output. It will
 also get a unique client identifier which may be used in communication with
 the client component when sending data to the client or ending a connection.