Bug#914128: perl: usrmerge issues

Niko Tyni ntyni at debian.org
Tue Aug 24 19:55:38 BST 2021


On Thu, Jul 15, 2021 at 04:36:10PM -0700, Vagrant Cascadian wrote:
> On 2021-07-15, Vagrant Cascadian wrote:
> > On 2018-11-19, Niko Tyni wrote:
> >> Diffoscoping a perl built on a usrmerged [1] system with
> >> one built on a non-usrmerged system reveals the configure
> >> process hardcoding some paths in the build results,

> With all three patches applied, perl builds reproducibly!

Many thanks!

> Attached patch also fixes these issues, by adjusting libpth and libspath
> in debian/config.over ... it feels a little hackish ... but ...

Yeah. The "pristine" probed values of libpth and libspath on a
non-usrmerged system look messy enough (/lib/../lib and the like) that
it might be more robust to just override them to some cleaner hardcoded
values rather than have more logic that tries to imitate the mess on
usrmerged systems. But I'll see how that works out.

I'll try to get this fixed in 5.34 / experimental soonish, but it might
only enter sid with the 5.34 transition that we should really start
driving. 5.32 is not a development priority at this point. (No need to
rebase the patches or anything though, happy to handle that.)
-- 
Niko Tyni   ntyni at debian.org




More information about the Perl-maintainers mailing list