Hi Stefano,
Am 15.04.22 um 16:08 schrieb Stefano Rivera:
Aha, of course. You can try to use the pyproject plugin, directly (we
should retire the flit plugin in favour of it, at some point).
I did that and it indeed fixes the problem.
But yes, fixing the flit plugin should be simple enough...
Hi Philip (2022.04.15_14:06:28_+)
> I think I found a way to fix it, just like you did it here
> https://salsa.debian.org/python-team/tools/dh-python/-/commit/6137db4dc870672615c31c9d1c9535dafe5b0d2a
> I'll create a MR later.
Aha, of course. You can try to use the pyproject plugin, directly (
Hi Stefano,
Am 15.04.22 um 15:44 schrieb Stefano Rivera:
It'll be something related to
https://lists.debian.org/debian-python/2022/03/msg00039.html
So true, thanks for the pointer.
I'll have a more detailed look, later today.
I think I found a way to fix it, just like you did it here
http
Hi Philip (2022.04.15_08:44:42_+)
> I'm writing to the list as I'm not sure what the source of the problem is.
It'll be something related to
https://lists.debian.org/debian-python/2022/03/msg00039.html
I'll have a more detailed look, later today.
SR
--
Stefano Rivera
http://tumbleweed.or
Hi,
I missed one details: these three packages are the only ones which fail with
this specific error (dh_usrlocal: error: debian/solo-python/usr/local/bin/solo
is not a directory) in the rebuild of unstable Lucas did (see
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220412;users=l
Hi,
I'm writing to the list as I'm not sure what the source of the problem is. The
symptom is that at least three packages (flit, solo-python and weasyprint)
start to FTBFS as flit installs the binaries to usr/local/bin instead of
usr/bin - see #1009392, #1009397 and #1009461. I looked through
6 matches
Mail list logo
