Bug#943811: Fwd: Bug#943811: perl:any is possible the following way and I suggest doing this

Mdasoh Kyaeppd mingdaisung at gmail.com
Thu Oct 31 06:16:04 GMT 2019


---------- Forwarded message ---------
From: Mdasoh Kyaeppd <mingdaisung at gmail.com>
Date: Thu, Oct 31, 2019 at 12:14 AM
Subject: Re: Bug#943811: perl:any is possible the following way and I
suggest doing this
To: Niko Tyni <ntyni at debian.org>


Hello,
        In preparation to address this, I have made a list of packages to
test, which meet the following criteria:
Architecture: amd64
Depends: perlapi-5.30.0:any or perlapi-5.30.0
libapache-authenhook-perl libapache2-mod-perl2 libapache2-request-perl
libbsd-resource-perl libcompress-raw-bzip2-perl libcompress-raw-zlib-perl
libcrypt-openssl-bignum-perl libcrypt-openssl-dsa-perl
libcrypt-openssl-pkcs12-perl libcrypt-openssl-x509-perl libcrypt-smime-perl
libdbi-perl libdigest-sha-perl libencode-perl libfile-fcntllock-perl
libfilter-perl libgssapi-perl libnet-dbus-perl libnet-idn-encode-perl
libnet-libidn-perl libscalar-list-utils-perl libsocket-perl libsocket6-perl
libsodium-dev libterm-readline-gnu-perl libtext-soundex-perl
libunicode-collate-perl libunicode-map8-perl libunicode-string-perl
libversion-perl libyaml-libyaml-perl libyaml-syck-perl

now since you have expressed the idea that none of them are working,
perhaps you could help me test them out and make sure.
This would make a significant difference, so some packages would have to
change, to match architectures on my system.
Keep in mind I still think things are working, since they seem to be
running okay.  Help me help you.

yours,
        - Mdasoh Kyaeppd.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/perl-maintainers/attachments/20191031/e8af3dc0/attachment-0001.html>


More information about the Perl-maintainers mailing list