Le Fri, Sep 12, 2025 at 08:09:01PM +0530, Nilesh Patra a écrit :
Are you saying that we can have test data not inside the debian/ directory and also not have MUT? If so, I am interested in how we can achieve that -- could you explain how to do this? (The only way I can think of here is downloading the upstream tar, unpacking, adding additional data and repacking it for each upstream release but we absolutely should not tamper with upstream sources)
Hi Nilesh, yes indeed, in the stringtie package for instance, if one deletes debian/gbp.conf, which contains `component=['debian-tests-data']`, the package builds fine with an orig.tar.xz that contains the entirety of the `upstream` branch, which is the upstream sources plus the `debian-tests-data` directory. Gbp buildpackage or git debpush are doing the repacking for us. We are already tampering with upstream tarballs, for instance by removing instance HTML documentations that contains minified JavaScript that we can not rebuild with only the files provided in the tarball, etc., so why would adding test data recommended by upstream be a bad thing, given that the multi-tarball approach does not appear to save space in our archive? Have a nice week-end! Charles -- Charles Plessy Nagahama, Yomitan, Okinawa, Japan Debian Med packaging team http://www.debian.org/devel/debian-med Tooting from work, https://fediscience.org/@charles_plessy Tooting from home, https://framapiaf.org/@charles_plessy
