From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS3215 2.0.0.0/16 X-Spam-Status: No, score=-3.3 required=3.0 tests=AWL,BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_HI,SPF_HELO_NONE, SPF_PASS shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from out10.migadu.com (out10.migadu.com [IPv6:2001:41d0:2:e8e3::]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dcvr.yhbt.net (Postfix) with ESMTPS id 4B4C11F9F3 for ; Sat, 16 Oct 2021 17:21:41 +0000 (UTC) X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kyleam.com; s=key1; t=1634404897; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=hLX6yas5t10hOHcM/pWuLL/2nQKSYuHTZpofcpuIssg=; b=QhlyNMl6JEbrxVpwCiqFK19wHJRDH6GqN49PjQ5pFAKFG7QDO2ccTOmhFtWGorRP1ueFjG V1LtFHwDRCnDcyPpP5qnpqIZfA/bI9xJOJgNoleQ8kuLRgatmQwO5hlXlLRsQCDndqXbjH 5F5r6lH7tMwyG1/ad/sQgZQ0iBLJi/Tjesjh1tqwNHHgtVFaS21EY1LiYOR1QHYYaiNfqy KlQu8iJebyHeaoXrQp3/jmdLvYoUZr0IsqbEQ5mNfPaT4c+7mNuxb8i0Rb1N1RK2unMldn kyX5PJQMdYIpuIm2CeHceNKCUtMywEEXhczZqjRksxjbEiZMm855pMDtpal7Pw== From: Kyle Meyer To: Eric Wong Cc: meta@public-inbox.org Subject: Re: [PATCH 2/2] doc: lei: add manpages for remaining commands In-Reply-To: <20211016170352.GA22949@dcvr> References: <20211016053944.494064-1-kyle@kyleam.com> <20211016053944.494064-3-kyle@kyleam.com> <20211016070753.M426387@dcvr> <87lf2t0zq2.fsf@kyleam.com> <20211016170352.GA22949@dcvr> Date: Sat, 16 Oct 2021 13:21:35 -0400 Message-ID: <87fst028dc.fsf@kyleam.com> MIME-Version: 1.0 Content-Type: text/plain X-Migadu-Flow: FLOW_OUT X-Migadu-Auth-User: kyle@kyleam.com List-Id: Eric Wong writes: > The failure is probably caused by > 00d5dff2cce9d2c9 (eml: avoid Encode 2.87..3.12 leak, 2021-10-13) > but I can't reproduce it across CentOS 7.x, FreeBSD 11.x, nor > Debian 10 & 11. Hmm, yeah, as mentioned in my other reply, I'm now not having any luck triggering this either. > Which versions of Encode and Perl are you using? Perl v5.32.1 from Debian 11 and... > At least in Debian, libencode-perl is available as a separate package > but it's also part of libperl5.xx (possibly w/ a different version); > only the latter is required for us, but two packages offering > the same thing gets confusing :/ > > I use: perl -MEncode -E 'say $Encode::VERSION' > to determine which gets loaded. ... it looks like I'm using the on that's ships with libperl5: $ perl -MEncode -E 'say $Encode::VERSION' 3.06 $ apt-cache policy libencode-perl libencode-perl: Installed: (none) Candidate: 3.08-1+deb11u1 Version table: 3.08-1+deb11u1 500 500 http://ftp.us.debian.org/debian bullseye/main amd64 Packages 500 http://security.debian.org/debian-security bullseye-security/main amd64 Packages