Your message dated Sat, 06 Apr 2019 10:58:44 +0000 with message-id <E1hCj24-0004Ws-AK@respighi.debian.org> and subject line unblock libanyevent-perl has caused the Debian Bug report #925450, regarding unblock: libanyevent-perl/7.140-3 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 owner@bugs.debian.org immediately.) -- 925450: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925450 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: unblock: libanyevent-perl/7.140-3
- From: Peter Pentchev <roam@ringlet.net>
- Date: Mon, 25 Mar 2019 11:24:06 +0200
- Message-id: <155350562335.9902.4775293517484379157.reportbug@straylight.m.ringlet.net>
Package: release.debian.org Severity: normal User: release.debian.org@packages.debian.org Usertags: unblock Hi, Please unblock package libanyevent-perl if you consider it fine to. The reason for the 7.140-3 upload was to change the default size of the DH parameters generated by AnyEvent::TLS, since OpenSSL 1.1.1 no longer accepts < 2048. This came up in the stunnel4 tests that I added to the Debian package; they use a Perl client/server program and connect to or accept connections from stunnel4, and they broke with OpenSSL 1.1.1; see https://bugs.debian.org/923448 for the stunnel4 bug and https://bugs.debian.org/923615 for the libanyevent-perl bug that I cloned from the former. At the time I decided that the AnyEvent::TLS bug itself was not that important, but I've since realized that it is actually bad - it means that any Perl programs that depend on AnyEvent::TLS will no longer work with OpenSSL 1.1.1 unless they override the defaults as I did in the stunnel4 test. So IMHO libanyevent-perl 7.140-3 should migrate to testing if you agree with this reasoning; I could also raise the severity of #923615 to provide a formal justification. I'm attaching the debdiff between 7.140-2 and 7.140-3; the DH params change is the only one affecting the package's behavior. Thanks in advance for your consideration even if you decide to decline my request, and keep up the great work! unblock libanyevent-perl/7.140-3 G'luck, Peter -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (990, 'testing'), (500, 'testing-debug') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-2-amd64 (SMP w/8 CPU cores) Locale: LANG=bg_BG.UTF-8, LC_CTYPE=bg_BG.UTF-8 (charmap=UTF-8), LANGUAGE=bg_BG.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabledAttachment: signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
- To: 925450-done@bugs.debian.org
- Subject: unblock libanyevent-perl
- From: Ivo De Decker <ivodd@respighi.debian.org>
- Date: Sat, 06 Apr 2019 10:58:44 +0000
- Message-id: <E1hCj24-0004Ws-AK@respighi.debian.org>
Unblocked libanyevent-perl.
--- End Message ---