On 23. 11. 21 20:26, Matthew Miller wrote:
On Tue, Nov 23, 2021 at 07:13:19PM +0100, Miro Hrončok wrote:
> The files are not supposed to be in the package. It could lead to
> conflicts, as you can see.
Thanks. Is this is a common test artifact which could "leak" in other
pacages, and there maybe a standard CI check (or gate?) we could put in
place? Or is it just a coincidence that both packages made a similarly-named
mistake?
It is a mistake that I'Ve seen again and again over the years. Upstream Python
packaging is somewhat immune to this problem (pip will happily override files
like this), so it usually only turns into a problem when packaged as RPM.
Yes, it is possible to check this automatically. For instance, I believe
rpmlint >= 2 does it.
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok