------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 13.0-systemd_20170628-214240 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-6.3.0 * Available Python interpreters, in order of preference: [1] python3.4 [2] python3.5 (fallback) [3] python2.7 (fallback) [4] pypy3 (fallback) [5] pypy (fallback) Available Ruby profiles: [1] ruby21 (with Rubygems) * [2] ruby22 (with Rubygems)
Created attachment 480886 [details] emerge-info.txt
Created attachment 480888 [details] dev-perl:RedisDB-2.360.0:20170705-013258.log
Created attachment 480890 [details] emerge-history.txt
Created attachment 480892 [details] environment
Created attachment 480894 [details] etc.portage.tbz2
Created attachment 480896 [details] temp.tbz2
Should point out the latest in tree was shipped in 2014 But the latest on CPAN is v=2.53 shipped in 2016
Would you be able to test against 2.540.0 ( just bumped )? Its really hard to see what's wrong from this context and hopefully its fixed upstream.
Can you please retest ( but not on hardened, due to bug #643266 ) and see if you can reproduce? I can't reproduce this issue, and logging is not sufficient to determine cause.