Bug#1061216: Please upgrade to llvm-toolchain-17
If a fix for this can't be released on time, I'm requesting an exception for llvm-15. Removing OpenVDB from Debian will affect Blender, which is is relatively high-profile and should not just be axed for the sake if a pruning operation. You still have time, we aren't going to release the trixie anytime soon :) but we won't probably block the removal in testing for openvdb (the popcon isn't high IMHO). Let's hope upstream notices the issue and fixes it. In the meantime, it may be possible to remove the immediate pressure by simply disabling the build of libopenvdb-ax. The rest of OpenVDB doesn't require LLVM 15, and I couldn't find any Debian package that depends on it (save for python3-openvdb, which will simply not have AX support). This should at least bring Blender back into trixie. I did a quick build test with the AX component disabled, and that seems to work fine. Blender also compiles. Didn't try to install and run the final result, though.
Bug#1061216: Please upgrade to llvm-toolchain-17
Le 06/05/2024 à 10:27, Gregor Riepl a écrit :
Which LLVM versions are you planning to remove?
15, 16 soon. 17 later.
Would it be possible to keep at least LLVM 15 until upstream has
upgraded their code base?
Sounds very unlikely for the next Debian release.
If a fix for this can't be released on time, I'm requesting an
exception for llvm-15. Removing OpenVDB from Debian will affect
Blender, which is is relatively high-profile and should not just be
axed for the sake if a pruning operation.
You still have time, we aren't going to release the trixie anytime soon
:) but we won't probably block the removal in testing for openvdb (the
popcon isn't high IMHO).
Is there any other reason why llvm-15 couldn't be kept, aside from the
reason mentioned in
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050070 ("too many
llvm version") ?
llvm-toolchain-X.Y is a very complex and heavy package. There are a lot
of changes in each release (every 6 months).
Between the new release, the port to archs, debian changes, new bugs,
etc, it is a lot of work to keep up.
So, we, Debian, have to make efforts to limit the number of versions and
push our upstream developers to also keep up with upstream versions
(they probably have too anyway).
Is there an upstream bug to follow the progress on their upgrade of
LLVM?
There is now:
https://github.com/AcademySoftwareFoundation/openvdb/issues/1804
Thanks. I subscribed!
Sylvestre
Bug#1061216: Please upgrade to llvm-toolchain-17
Which LLVM versions are you planning to remove?
15, 16 soon. 17 later.
Would it be possible to keep at least LLVM 15 until upstream has
upgraded their code base?
Sounds very unlikely for the next Debian release.
If a fix for this can't be released on time, I'm requesting an exception
for llvm-15. Removing OpenVDB from Debian will affect Blender, which is
is relatively high-profile and should not just be axed for the sake if a
pruning operation.
Is there any other reason why llvm-15 couldn't be kept, aside from the
reason mentioned in
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050070 ("too many
llvm version") ?
Is there an upstream bug to follow the progress on their upgrade of LLVM?
There is now:
https://github.com/AcademySoftwareFoundation/openvdb/issues/1804
Bug#1061216: Please upgrade to llvm-toolchain-17
Le 05/05/2024 à 02:30, Gregor Riepl a écrit : As part of the effort to limit the number of llvm packages in the archive, it would be great if you could upgrade to -17. This package depends on 14. Not possible at this time. Trying to build openvdb 10.0.1 against LLVM 17 results in the following error: CMake Error at openvdb_ax/openvdb_ax/CMakeLists.txt:118 (message): OpenVDB AX does not currently support LLVM versions >= 15 due to opaque pointer changes in LLVM. Found unsuitable LLVM version "17.0.6" The release notes for openvdb 11.1.0[1] mention compatibility with LLVM 15, but not later versions. There's nothing listed for 11.0.0, and a quick test shows that this hasn't changed: CMake Error at openvdb_ax/openvdb_ax/CMakeLists.txt:118 (message): OpenVDB AX does not currently support LLVM versions >= 16 due to opaque pointer changes in LLVM. Found unsuitable LLVM version "17.0.6" Which LLVM versions are you planning to remove? 15, 16 soon. 17 later. Would it be possible to keep at least LLVM 15 until upstream has upgraded their code base? Sounds very unlikely for the next Debian release. Is there an upstream bug to follow the progress on their upgrade of LLVM? Thanks Sylvestre
Bug#1061216: Please upgrade to llvm-toolchain-17
As part of the effort to limit the number of llvm packages in the archive, it would be great if you could upgrade to -17. This package depends on 14. Not possible at this time. Trying to build openvdb 10.0.1 against LLVM 17 results in the following error: CMake Error at openvdb_ax/openvdb_ax/CMakeLists.txt:118 (message): OpenVDB AX does not currently support LLVM versions >= 15 due to opaque pointer changes in LLVM. Found unsuitable LLVM version "17.0.6" The release notes for openvdb 11.1.0[1] mention compatibility with LLVM 15, but not later versions. There's nothing listed for 11.0.0, and a quick test shows that this hasn't changed: CMake Error at openvdb_ax/openvdb_ax/CMakeLists.txt:118 (message): OpenVDB AX does not currently support LLVM versions >= 16 due to opaque pointer changes in LLVM. Found unsuitable LLVM version "17.0.6" Which LLVM versions are you planning to remove? Would it be possible to keep at least LLVM 15 until upstream has upgraded their code base? [1] https://www.openvdb.org/documentation/doxygen/changes.html#v10_1_0_changes
Bug#1061216: Please upgrade to llvm-toolchain-17
Source: openvdb Severity: important Dear Maintainer, As part of the effort to limit the number of llvm packages in the archive, it would be great if you could upgrade to -17. This package depends on 14. Thanks, Sylvestre
