Your message dated Wed, 29 Mar 2023 17:27:34 +0100
with message-id <zcrm9m6n+ggx9...@powdarrmonkey.net>
and subject line Re: Bug#1033638: unblock: pocl/3.1-3
has caused the Debian Bug report #1033638,
regarding unblock: pocl/3.1-3
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1033638: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033638
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian....@packages.debian.org
Usertags: unblock
Control: block -1 with 1032887
Please unblock package pocl
[ Reason ]
build pocl against llvm-15 insteal of llvm-14
this is blocked by llvm-toolchain-15 since it picked up a dependency on
the version in sid
[ Impact ]
Loading multiple OpenCL ICDs into an application is quite common (if
only to enumerate the available platforms). Having the common ones
(mesa-opencl-icd for gpus, poc-opencl-icd for cpus) built against
different llvm versions frequently causes trouble since loading multiple
different llvm lib versions into one application sometimes causes havoc
due to symbol mixup, #1025003. So far we haven't succeeded linking the
ICDs in a way that would fully separate their llvm usage.
Therefore I try to have them built against the same version in stable.
[ Tests ]
pocl has a testsuite run at build time, but I haven't gotten around
turning that into a proper autopkgtest. (There is currently only a
superficial autopkgtest running clinfo).
pyopencl has an autopkgtest suite that makes use of pocl.
(And the llvm-15 switch caused a regression there because it exposed
a buggy test expecting numerical identity, fix from pyopencl upstream
is in bookworm.) There should be more packages using pocl in their
autopkgtests with no known regressions since the package was uploaded
in January.
[ Risks ]
The change is trivial and could easily be reverted.
[ Checklist ]
[+] all changes are documented in the d/changelog
[+] I reviewed all changes and I approve them
[+] attach debdiff against the package in testing
diff --git a/debian/changelog b/debian/changelog
index 690df65c..73714f77 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+pocl (3.1-3) unstable; urgency=medium
+
+ * Switch to llvm 15. (Closes: #1025003)
+
+ -- Andreas Beckmann <a...@debian.org> Tue, 24 Jan 2023 11:19:20 +0100
+
pocl (3.1-2) unstable; urgency=medium
* Fix segmentation fault. (Closes: #1028636)
diff --git a/debian/control b/debian/control
index 4bb11c05..3075509e 100644
--- a/debian/control
+++ b/debian/control
@@ -7,10 +7,10 @@ Uploaders: Vincent Danjean <vdanj...@debian.org>,
Build-Depends:
debhelper-compat (= 13),
gcc (>= 4:12),
- clang-14,
- libclang-14-dev,
- libclang-cpp14-dev,
- llvm-14-dev,
+ clang-15,
+ libclang-15-dev,
+ libclang-cpp15-dev,
+ llvm-15-dev,
cmake,
libhwloc-dev,
ocl-icd-dev,
unblock pocl/3.1-3
--- End Message ---
--- Begin Message ---
On Wed, Mar 29, 2023 at 10:03:28AM +0200, Andreas Beckmann wrote:
> [ Reason ]
> build pocl against llvm-15 insteal of llvm-14
> this is blocked by llvm-toolchain-15 since it picked up a dependency on
> the version in sid
Unblocked; thanks.
--
Jonathan Wiltshire j...@debian.org
Debian Developer http://people.debian.org/~jmw
4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51
ed25519/0x196418AAEB74C8A1: CA619D65A72A7BADFC96D280196418AAEB74C8A1
--- End Message ---
