libcatalyst-view-component-subinclude-perl 0.10-3 source package in Ubuntu

Changelog

libcatalyst-view-component-subinclude-perl (0.10-3) unstable; urgency=medium

  * Team upload.

  [ Salvatore Bonaccorso ]
  * Update Vcs-Browser URL to cgit web frontend

  [ Axel Beckert ]
  * debian/copyright: Update Chisel Wright's e-mail address. Issue
    reported by DUCK.

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

  [ gregor herrmann ]
  * Fix autopkgtests. Don't run smoke tests in t/author/.
  * Mark package as autopkgtest-able.
  * Declare compliance with Debian Policy 4.0.0.
  * Drop version constraints from libcatalyst-perl (build) dependency.
  * Bump debhelper compatibility level to 9.

 -- gregor herrmann <email address hidden>  Wed, 02 Aug 2017 13:00:59 -0400

Upload details

Uploaded by:
Debian Perl Group on 2017-08-02
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
Eoan release on 2019-04-18 universe perl
Disco release on 2018-10-30 universe perl
Cosmic release on 2018-05-01 universe perl
Bionic release on 2017-10-24 universe perl
Artful release on 2017-08-02 universe perl

Builds

Artful: [FULLYBUILT] amd64

Downloads

File Size SHA-256 Checksum
libcatalyst-view-component-subinclude-perl_0.10-3.dsc 2.7 KiB 70b7d16b8a6bb0c5e869b582021242dbf14da11c17772ddb421711b40c3374fd
libcatalyst-view-component-subinclude-perl_0.10.orig.tar.gz 36.4 KiB 53f9e285c86842ba4abedc4481ab0e75c3f0a59fd8bf1b1848c3e18ae617f1ec
libcatalyst-view-component-subinclude-perl_0.10-3.debian.tar.xz 4.0 KiB 6d3be6d4f8d6070040847652e56b76c03b5b5c1e386120054c234b79735a47a6

Available diffs

No changes file available.

Binary packages built by this source

libcatalyst-view-component-subinclude-perl: Use subincludes in your Catalyst views

 Catalyst::View::Component::SubInclude allows you to include content in
 your templates (or, more generally, somewhere in your view's render
 processing) which comes from another action in your application. It's
 implemented as a Moose::Role, so using Moose in your view is required.