> Backporting sounds like a reasonable approach. If that does not work
> as expected, I'll restore the symlink.
Excellent. Let me know when this is done, and I'll then update mrbuild
to use it, and the builds will then work again.
I see you just tagged 1:1.26.4+ds-6 in git with the .pc stuff.
Hi Dima,
* Dima Kogan [2024-03-21 07:23]:
My feeling is that being confused by that symlink is a bug, but I
didn't read #998084 in great detail, so maybe I'm missing some
nuance. So let's make this work.
My understanding is that /usr/include/pythonX.Y as Python header
directory will be made
Hi Timo. Thanks for replying.
My feeling is that being confused by that symlink is a bug, but I didn't
read #998084 in great detail, so maybe I'm missing some nuance. So let's
make this work.
** Short version **
Proposal: if pkg-config files will be added in the near future, can we
wait until
Hi Dima,
* Dima Kogan [2024-03-20 18:23]:
Can we get that symlink back, please?
I removed that symlink in the latest release, because it is not
created by upstream but a Debian specific patch, and according to
#998084 [1], it can badly interfere with venv setups.
I would very much prefer
Package: python3-numpy
Version: 1:1.26.4+ds-5
Severity: important
X-Debbugs-Cc: none, Dima Kogan
Hi.
Many of my packages just started to FTBFS. For instance this:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067270
This is due to the
/usr/include/python3.11/numpy (and/or other
5 matches
Mail list logo
