Your message dated Sun, 26 Nov 2017 15:02:09 +0000
with message-id <[email protected]>
and subject line Bug#855894: fixed in liblog-log4perl-perl 1.48-1+deb9u1
has caused the Debian Bug report #855894,
regarding liblog-log4perl-perl: Warnings with Perl 5.24 and newer when 
"syswrite" and "utf8" are used together
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
855894: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855894
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: liblog-log4perl-perl
Version: 1.48-1
Severity: normal
Tags: patch upstream

Dear Maintainer,

Perl 5.24 warns when syswrite is used on file handles with enabled utf8 layer.
This is intentional, see https://rt.perl.org/Public/Bug/Display.html?id=125760

This affects Log::Log4perl::Appender::File when something like the following is 
used:
...
log4perl.appender.LOGFILE=Log::Log4perl::Appender::File
log4perl.appender.LOGFILE.syswrite=1
log4perl.appender.LOGFILE.utf8=1
...

The upstream bug report and fix is at 
https://github.com/mschilli/log4perl/issues/78 
(https://github.com/mschilli/log4perl/commit/e8d8f6600312670a156399e220998dbd0832915f)
 or in the freshly released Log4perl 1.49.

Note that the commit and release also contain a minor change of behaviour for 
the utf8 option:
Previously "...utf8=0" would still enable the utf8 layer, now it won't.

Regards,
Marc

--- End Message ---
--- Begin Message ---
Source: liblog-log4perl-perl
Source-Version: 1.48-1+deb9u1

We believe that the bug you reported is fixed in the latest version of
liblog-log4perl-perl, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Salvatore Bonaccorso <[email protected]> (supplier of updated 
liblog-log4perl-perl package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Thu, 23 Nov 2017 14:36:00 +0100
Source: liblog-log4perl-perl
Binary: liblog-log4perl-perl
Architecture: source
Version: 1.48-1+deb9u1
Distribution: stretch
Urgency: medium
Maintainer: Debian Perl Group <[email protected]>
Changed-By: Salvatore Bonaccorso <[email protected]>
Closes: 855894
Description: 
 liblog-log4perl-perl - Perl port of the widely popular log4j logging package
Changes:
 liblog-log4perl-perl (1.48-1+deb9u1) stretch; urgency=medium
 .
   * Team upload.
   * Workaround for Perl 5.24 no longer allowing syswrite and utf8 together
     (Closes: #855894)
Checksums-Sha1: 
 5a3b3fe12f27d26a19a9948932ac035dc8d0ea86 2434 
liblog-log4perl-perl_1.48-1+deb9u1.dsc
 613019495e31a512e71b20293b3a3cd51e9470b3 17892 
liblog-log4perl-perl_1.48-1+deb9u1.debian.tar.xz
Checksums-Sha256: 
 b417d0fa38e8be52be15a093a0d85c23fe8209d7de37683288d43e091e027452 2434 
liblog-log4perl-perl_1.48-1+deb9u1.dsc
 defae0006808971f8b2255f3862a833e6a963184cedb42e02337c123dc5faea7 17892 
liblog-log4perl-perl_1.48-1+deb9u1.debian.tar.xz
Files: 
 3c3ad6827e1bcd4cd4effafea358b80f 2434 perl optional 
liblog-log4perl-perl_1.48-1+deb9u1.dsc
 9bb3f0f4ba08be37803a33245a17b075 17892 perl optional 
liblog-log4perl-perl_1.48-1+deb9u1.debian.tar.xz

-----BEGIN PGP SIGNATURE-----

iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAloWz4lfFIAAAAAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2
NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk
ZWJpYW4ub3JnAAoJEAVMuPMTQ89E7LgQAKJ484qtY76VV8XGTHHdf9rvUJ8ZVSw4
B+Rsjosza+GuOZHSktAnxDTUQjxSoaoGQKIFN1iw6F3Mt2gbbz0+pOqnJQE8Jw7Y
U6k3u62362336mLoyZ6KM8VtnglIHryfAu1BY8E4oN9liAuUOlJcSKqLkcLL7/93
Q1Avo96zj1RtUG5zKWu1+GaH3AVkvwJVYu5itr+6675lN2hiz9kH/vbOdP3YgCPQ
IT3NYy337b6nvgvL0pFf37UazqAiDBODPKNqG7lqFQ5DojAUEA8giUB7nAJx413R
Uq8eu+FsE8L1R2dCNwVV02nzUpj/CXsFhcqkdXcCDfqhh9QTkr1784SyaxVhzGwn
mPshF4XEaaAdB4/S3AAwZwS4MQdLovN9ibSav1WTzG73B7fWYZIYrp6kqN1zcYAr
ETZvlN6/MKAcAXh4U9FZweRmSt0O1KtUJKOrTeELXznCUeo5IP7/XYNHHZ/lDKzw
/+j8+m7gchyH4y3rbwbyxp4TIidx2+OuxH26CkTEexDt+XeB7jE5GUjQbSgIfWBo
JniARKKRGwmykNinVWn0MAtACkljGMDu6Awlx3Vei/HozXdcyGs8bOOFhT0avpwP
8hEK41JD+atC+IKEzKDpWW7y19J/pKlkhF9ToB5FvhM3FgF+PcYoCMVXERwBTlDJ
JzWwlyKoIXTR
=pcDP
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to