On Mon, 2021-03-01 at 10:40 +0100, Emilio Pozuelo Monfort wrote: > You can ship the files directly in the debian.tar by adding them to > debian/source/include-binaries, and that way you don't need to call chmod as > their mode will be preserved. That would probably help with this autopkgtest > patch issue.
Unfortunately, dpkg does not see these new files because it first applies an autogenerated patch. At least, .debian.tar.xz archive has no files I mentioned in the include-binaries list. https://salsa.debian.org/freedesktop-team/xdg-utils/-/pipelines/235570 On Sun, 2021-02-28 at 10:20 -0300, Antonio Terceiro wrote: > Please drop patching from the test entirely. autopkgtests are supposed > to _start_ running against a fully patched source tree. autopkgtest(1) > does this automatically. > > I understand that this might be convenient when working on the package, > but please automate it in a way that it's not also done when running the > autopkgtest "for real". Any ideas how to preserve executable bit of new files in other way? For now, I see only one option: manually chmod +x either by the debian/rules patch target or repeated for dh_auto_test and in the autopkgtest runner.
signature.asc
Description: This is a digitally signed message part
