Source: wine-development Source-Version: 8.21~repack-1 Severity: important Hi!
This package regenerates the debian/control file on each build, from my reading of the archive https://ftp-master.debian.org/REJECT-FAQ.html, this is not allowed. I realize the regeneration is supposed to not change the content of the file unless the packaging is for stable or development source packages. But the above would still seem to apply. In, practical terms this is causing the following error: ,--- /usr/bin/make -f debian/rules debian/control make[2]: Entering directory '/tmp/bd/wine-9.0~repack' dpkg-buildapi: error: cannot read debian/control: No such file or directory /bin/sh: 1: test: Illegal number: sed "s/VERSION//g;s/DEBSUFFIX/-stable/g" < debian/control.in > debian/control `--- Because the debian/control file gets removed before it gets regenerated. Besides the regeneration issue, I think the control file should not be removed. I think, that the current handling might have multiple intents. One perhaps to generate the debian/control file from debian/control.in if the former is missing, this can be accomplished as of now with a make target. Then there is the generation of the file depending on the source, but that should not change often, or when it changes would be due to changes in control.in, which would trigger the usual target as well, but a new target could be created as well to forcibly touch the source and then depend on the usual target. And finally, perhaps as a check to make sure that the file always contains the expected result. For this latter case I guess adding a new target that generates the file as a temporary, and compares against the canonical debian/control, and then fails if there's any difference, would accomplish the check, while not generating it. Thanks, Guillem
