Hi,
The pyFAI upstream developer answering: there are newer releases of
pyFAI fixing the compatibility with numpy2. There is no resources on
our side to backport compatibility with newer ABI.
Cheers,
Jerome
On Wed, 05 Feb 2025 12:50:16 +0100
Giacomo Mulas wrote:
> Package: python3-pyfai
> Ve
the kernel
between 5.10 and 6.1. I know few people are using this module thus I struggle
to find additionnal information.
Thanks for you help
Jerome Kieffer
-- System Information:
Debian Release: 12.8
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, '
Platform Name Portable Computing Language
Platform Vendor The pocl project
Platform VersionOpenCL 3.0 PoCL 3.1+debian
Linux, None+Asserts, RELOC, SPIR, LLVM 15.0.6, SLEEF, DISTRO, POCL_DEBUG
This looks good to be. Thanks for your contribution.
Cheers,
--
Jérôme Kieffer
Hi,
I am the upstream author of FabIO and indeed, there is a regression in
the tests when run for the first time. This is linked to an un-flushed
file. This can simply be corrected with this simple patch
https://github.com/silx-kit/fabio/pull/550/files
It is probably simpler to debian to just app
Hi,
Apparently this bug comes from the tool used to build the source package:
"meson-python" ... it does not set properly timestamps in the source archive.
https://github.com/mesonbuild/meson-python/issues/450
Cheers,
Jerome
Hi Matthias,
I am the upstream developper of pyFAI. This version is >1 year old and
I don't have the resources to backport bug-fixes. I develop on a daily
basis on debian 12 and python 3.11 and the latest version is OK there.
https://pypi.org/project/pyfai/#history
How much work would it represen
On Sun, 22 Jan 2023 16:56:46 +0100
Andreas Tille wrote:
> Thanks for commenting on this. Would you be able to push the needed changes
> to Salsa (and preferably upload)?
Hi Andreas,
I know a bit about debian packaging and also about the gitlab-CI, but I never
used the later for the former.
I
Hi Andreas,
Thanks for taking care of the packaging of pyFAI. I had a look at what
the logs and apparently you are packaging the version 0.21.3 ... while
I released the verison 2023.1 last week:
https://pypi.org/project/pyfai/
I just checked on the i386-debian sid chroot I have and none of the 3
Dear Lucas,
I suspect the issue is once again the "numpy.distutils" which enforces
"setuptools<60"...
I have started to port FabIO to the meson-python builder, in a similar
way to what is done for scipy-1.9 (still not packaged for debian).
It is now close to production ready and can release a ver
Hi Lucas,
All my packages (and probably many more) are marked for removal because of this
bug.
I believe this bugs comes from a specificity of Debian which does not
install python3-pip together with python3. If python3-pip is now needed by
pybuild it should be a build dependency.
Cheers,
Jerom
Hi Lucas,
Thanks for the report. This looks like a bug I recently fixed in pyFAI ... I'll
have a look tomorrow. Probably just a missing dependency like in
https://github.com/silx-kit/pyFAI/commit/7bcb6dd7419b48580d97cd91a28d05f86b301f1c
Cheers,
Jerome
On Sat, 26 Mar 2022 22:57:37 +0100
Lucas N
Dear Paul,
I am the upstream author of pyFAI and the release 0.21.1 is a bugfix
for the regressions spotted by the debian CI on a couple of 32-bit
computer architectures (thanks to debian for that).
Thus I don't understand why the migration from unstable to testing is
blocked, especially that th
Dear Paul, Dear Fred.
Those 3-broken tests are exactly the same as the one reported by
Fred Picca on i386 with Python3.10.
I tried to reproduce them manually on a Zen computer with an i386
debian system installed on it, without success. I will try to reproduce
the bug on an ARM system: I own a T
pgrade the package in debian.
Conda based system with recent version of pyopencl are not subject to
this kind of crashes.
Thanks for your help,
Jerome Kieffer
-- System Information:
Debian Release: 10.6
APT prefers stable
APT policy: (800, 'stable'), (500, 'stable-updates'
Package: pymca
Version: 5.4.3+dfsg-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
I installed "pymca" on a debian 10 system, this draggs the dependencies:
* python3-pymca5
* python3-silx
The package python3-silx apparently requires python3-scipy, the graphical user
in
Thanks Fred for the time spent on this. It looks like it is a very deep problem
!
Concerning the code:
This medfilt code never properly worked on POCL CPU-thread version
while it works as expected on CUDA (POCL+CUDA) or other drivers.
There is a huge amount of shared memory involved which may
Hi,
This FBFS bug comes down to the POCL on i386 which is not able to
perform calculation as described by the OpenCL spec.
It is likely a numerical optimization at the wrong place as those tests
ensures the calculation are performed as expected.
This is described in:
https://en.wikipedia.org/wiki
first the kernel via wheezy-backports packages before upgrading to
Jessie.
Best regards,
Jerome Kieffer
-- System Information:
Debian Release: 8.0
APT prefers stable
APT policy: (800, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.16.0-4-amd64 (S
Hi,
The new upstream version (0.14) will include a "debian-friendly" source
tree which includes test images (this makes the source package > 100MB)
and exclude all auto-generated files like from cython, sphinx, pylint,
epydoc, ... to keep it compatible with debian rules.
Once upon a time I read u
On Thu, 22 Mar 2012 08:12:00 +0100
Treinen wrote:
> Package: remote-tty,python-rfoo
> Version: remote-tty/4.0-13
> Version: python-rfoo/1.3.0-1
> Severity: serious
> User: trei...@debian.org
> Usertags: edos-file-overwrite
Thanks Ralf for the bug report, the fault is on our side.
I contacted th
21 matches
Mail list logo
