Sign me up Login

Details about package opencl-icd-loader

Name: opencl-icd-loader
Uploader: Dmitry Baryshkov <dbaryshkov@gmail.com> (Debian QA page)
Description: opencl-icd-libopencl1 - Khronos official OpenCL ICD Loader
opencl-icd-loader-dev - Khronos official OpenCL ICD Loader - development files
opencl-icd-loader-bin - Khronos official OpenCL ICD Loader - tools

Package uploads

Upload #2

Information

Version: 0~20250722-1
Uploaded: 2026-02-04 16:58
Source package: opencl-icd-loader_0~20250722-1.dsc
Distribution: unstable
Section: libs
Priority:
Homepage: https://github.com/KhronosGroup/OpenCL-ICD-Loader
Vcs-Browser: https://salsa.debian.org/lumag/opencl-icd-loader
Vcs-Git: https://salsa.debian.org/lumag/opencl-icd-loader.git
Closes bugs: #1126950

Changelog

 opencl-icd-loader (0~20250722-1) unstable; urgency=medium
 .
   * Initial release. (Closes: #1126950))

QA information

Comments

No comments

Upload #1

Information

Version: 0~20250722-1
Uploaded: 2026-02-04 14:28
Source package: opencl-icd-loader_0~20250722-1.dsc
Distribution: unstable
Section: libs
Priority: optional
Homepage: https://github.com/KhronosGroup/OpenCL-ICD-Loader
Vcs-Browser: https://salsa.debian.org/lumag/opencl-icd-loader
Vcs-Git: https://salsa.debian.org/lumag/opencl-icd-loader.git
Closes bugs: #1126950

Changelog

 opencl-icd-loader (0~20250722-1) unstable; urgency=medium
 .
   * Initial release. (Closes: #1126950))

QA information

Comments

  1. 0) Is there a chance that this package gets backported? It might make sense to stick to Standards-Version and watch file format from trixie

1) debian/copyright: you don't need the year in Qcom copyright marking (I can provide details)

2) have you considered enabling tests? (OPENCL_ICD_LOADER_BUILD_TESTING / test subdir) I see some tests are run during build, not sure if it's all tests

3) I tried generating the upstream debian packaging, it's similar, but I found these differences interesting:
a) source package is khronos-opencl-loader; I find this name makes more sense
b) control sets Rules-Requires-Root: no; can obviously added to your tree
c) binary package names are different; I don't necessarily see much reason to align with existing public binary package names as we didn't have requests to see this packaged in Debian for years, if you do rename the source package I'd suggest renaming the binary packages too
d) I didn't find amd-app, is this a well-known name? the upstream deb packaging mentions amd-libopencl1 (and nvidia-libopencl1 which you have too)
e) upstream builds with -DCMAKE_BUILD_TYPE=Release -DBUILD_TESTING=OFF; should these be considered for the Debian build?

4) typo in your changelog: two closing parenthesis "(Closes: #1126950))"; not sure about the email address either :-P

5) could you line-wrap the Provides like you did for build-deps and depends?

6) I don't get the Recommends: libgl-dev; I would drop it

7) copyright: typo, missing T: "2019-2026 he Khronos Group Inc."

8) copyright: Upstream-Contact should probably be "OpenCL ICD Loader" or "OpenCL-ICD-Loader" if you put it

9) copyright: Source: I'd drop the brackets "<>" around the URL

10) copyright: some files are copyrighted earlier (I saw a 2012 mention); I didn't see any 2026, but that doesn't hurt :)

11) copyright: these are missing:
loader/windows/adapter.h:* Copyright (c) 2019 Valve Corporation
loader/windows/adapter.h:* Copyright (c) 2019 LunarG, Inc.

12) copyright: this is missing:
cmake/JoinPaths.cmake:# SPDX-License-Identifier: (MIT OR CC0-1.0)
# Copyright 2020 Jan Tojnar

13) control: I think you can add a Priority field (lintian: W: opencl-icd-loader source: recommended-field (in section for source) Priority [debian/control:1])

14) control: would it make sense to have a dep from opencl-icd-loader-bin to opencl-icd-libopencl1 if it's only making sense with this implementation? the dep should also be strictly version in this case

15) I see Build-Dep opencl-c-headers but the -dev has a dep opencl-clhpp-headers; why is that?

16) autopkgtest would be nice :)


17) I built and installed opencl-icd-libopencl1 and could run Mesa's clinfo with Mesa's opencdl ICD installed. However cllayerinfo reported nothing, is this a bug?


Most items are minor, I'd insist on fixing issues 7-12, and would personally definitely change 6 and 13.
    Needs work Loïc Minier at Feb. 8, 2026, 8:24 p.m.