This FTBFS is due to autopkgtest running "debian/rules build" without running "debian/rules clean" first.
The clean target removes config.{guess,sub} file, then in conig.status target the ln command assumes these files are not there. This can be easily fixed by using "-f" option for ln, but since all buildd runs "debian/rules clean" before building, and policy explicitly says build target may need clean target to be run first, shouldn't autopkgtest be less restrictive on this?
This FTBFS is due to autopkgtest running "debian/rules build" without running "debian/rules clean" first.
The clean target removes config.{guess,sub} file, then in conig.status target the ln command assumes these files are not there. This can be easily fixed by using "-f" option for ln, but since all buildd runs "debian/rules clean" before building, and policy explicitly says build target may need clean target to be run first, shouldn't autopkgtest be less restrictive on this?