It seems like this might be a good fit for dh-autoreconf¹ to ensure that the buildsystem is actually rebuilt after patching configure.in. Otherwise this risks silently regressing on further uploads. Is there a particular reason that dh-autoreconf has not been used here?
It seems like this might be a good fit for dh-autoreconf¹ to ensure that the buildsystem is actually rebuilt after patching configure.in. Otherwise this risks silently regressing on further uploads. Is there a particular reason that dh-autoreconf has not been used here?
¹: https:/ /manpages. debian. org/testing/ dh-autoreconf/ dh-autoreconf. 7.en.html