> AIUI it won't automatically run either that's exactly the problem, the configure.ac file might be updated to fix a bug, but the build might not run autoreconf to actually update the configure file, and so the package would be built *without* including the added fix - in fact, it might even *regress* the package if the configure file checked in contains less fixes than the configure.ac file from the last build (and autoreconf isn't run).
> I don't see a specific problem it would fix, nor do I see a significant > future > risk of a problem being exposed. the [test case] section shows how this problem can manifest; and this *actually did happen* with the bionic build, as explained in [impact] section. I honestly don't understand the resistance to what seems completely safe and correct to me, nor do I understand if my [impact] and [test case] sections are unclear, so maybe I'm missing something in @racb's logic. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1842947 Title: dpkg 1.19.0.5ubuntu2.2 build did not recreate 'configure' file, losing changes in 'configure.ac' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1842947/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
