Detailed explanation about the bug and how to fix it is in the URL. This is a tracker, please do not discuss here.
I updated details in the wikipage
Should I open new issues if any new findings take place? I learnt many packages that have this issue, I can supply the bugtracker with more packages
should we use plain autoreconf or eautoreconf?
(In reply to Pacho Ramos from comment #3) > should we use plain autoreconf or eautoreconf? Bit late, but always eautoreconf AFAIK. (In reply to Denis Pronin from comment #2) > Should I open new issues if any new findings take place? > I learnt many packages that have this issue, I can supply the bugtracker > with more packages Yes.
Okay, all blockers done. TL;DR is that it's easiest to check ltmain.sh and that elibtoolize from libtool.eclass is insufficient to refresh (at least by itself), so I just used eautoreconf which seemed to be fine.