liblog-log4perl-perl 1.49-1 source package in Ubuntu
Changelog
liblog-log4perl-perl (1.49-1) unstable; urgency=medium
* Team upload.
* Import upstream version 1.49.
Fixes "Warnings with Perl 5.24 and newer when "syswrite" and "utf8"
are used together" (Closes: #855894)
* Add debian/gbp.conf to tell gbp import-orig to merge the upstream
branch (instead of replacing it). This is necessary because we have
changes applied (git-dpm, git-debcherry).
* Declare compliance with Debian Policy 4.0.0.
-- gregor herrmann <email address hidden> Tue, 01 Aug 2017 16:39:59 -0400
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 | Published | Component | Section | |
|---|---|---|---|---|
| Focal | release | universe | perl | |
| Bionic | release | universe | perl |
Downloads
| File | Size | SHA-256 Checksum |
|---|---|---|
| liblog-log4perl-perl_1.49-1.dsc | 2.3 KiB | 6fd776e1a7aa18ca3c5014b7a99600ae2eeb03470a24227f997060fcf30e0015 |
| liblog-log4perl-perl_1.49.orig.tar.gz | 273.0 KiB | b739187f519146cb6bebcfc427c64b1f4138b35c5f4c96f46a21ed4a43872e16 |
| liblog-log4perl-perl_1.49-1.debian.tar.xz | 16.8 KiB | e520a341ef15856f12b71eb13780e11aa4a02b0fb45a9fe980b1eb6fb3ef93b8 |
Available diffs
- diff from 1.48-1 to 1.49-1 (7.0 KiB)
No changes file available.
Binary packages built by this source
- liblog-log4perl-perl: Perl port of the widely popular log4j logging package
Log::Log4perl is a pure Perl port of the widely popular Apache/Jakarta
log4j library for Java. In the spirit of log4j, Log::Log4perl
addresses the shortcomings of typical ad-hoc or homegrown logging
systems by providing three mechanisms to control the amount of data
being logged and where it ends up at:
* Levels allow you to specify the priority of log
messages. Low-priority messages are suppressed when the system's
setting allows for only higher-priority messages.
* Categories define which parts of the system you want to enable
logging in. Category inheritance allows you to elegantly reuse
and override previously defined settings of different parts in the
category hierarchy. So, at a central location in your system (either
in a configuration file or in the startup code) you may specify which
components (classes,functions) of your system should generate logs.
* Appenders allow you to choose which output devices the log data
is being written to, once it clears the previously listed
hurdles.
