libecap 1.0.1-3.2build1 source package in Ubuntu

Changelog

libecap (1.0.1-3.2build1) focal; urgency=medium

  * No-change rebuild for libgcc-s1 package name change.

 -- Matthias Klose <email address hidden>  Sat, 21 Mar 2020 13:28:01 +0100

Upload details

Uploaded by:
Matthias Klose
Uploaded to:
Focal
Original maintainer:
Luigi Gangitano
Architectures:
any
Section:
misc
Urgency:
Medium Urgency

See full publishing history Publishing

Series Pocket Published Component Section

Downloads

File Size SHA-256 Checksum
libecap_1.0.1.orig.tar.gz 331.0 KiB 675f1a40a74a103864cb771ff30162bcdd1caeef4c808799a8293a9e9fe57d8c
libecap_1.0.1-3.2build1.debian.tar.xz 4.8 KiB 66f9f3cd647f1c0df74b3fe59593d706066023503de0f34bac2c1cf31cd40897
libecap_1.0.1-3.2build1.dsc 1.8 KiB ed73222805aa30f93e903369f6f5144a6e6aa1abe542e9972940ccde74c29cc5

View changes file

Binary packages built by this source

libecap3: eCAP library

 eCAP is a software interface that allows a network application,
 such as an HTTP proxy or an ICAP server, to outsource content
 analysis and adaptation to a loadable module. For each applicable
 protocol message being processed, an eCAP-enabled host application
 supplies the message details to the adaptation module and gets
 back an adapted message, a "not interested" response, or a "block
 this message now!" instruction. These exchanges often include
 message bodies.

libecap3-dbgsym: debug symbols for libecap3
libecap3-dev: eCAP development libraries

 eCAP is a software interface that allows a network application,
 such as an HTTP proxy or an ICAP server, to outsource content
 analysis and adaptation to a loadable module. For each applicable
 protocol message being processed, an eCAP-enabled host application
 supplies the message details to the adaptation module and gets
 back an adapted message, a "not interested" response, or a "block
 this message now!" instruction. These exchanges often include
 message bodies.