Your message dated Wed, 08 Apr 2020 18:34:41 +0000
with message-id <e1jmfx7-000bbn...@fasolo.debian.org>
and subject line Bug#955815: fixed in intel-opencl-clang 10.0.0-2
has caused the Debian Bug report #955815,
regarding intel-opencl-clang: requires a source-only upload
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.)


-- 
955815: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955815
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: intel-opencl-clang
Version: 9.0.0-1
Severity: serious

intel-opencl-clang currently cannot migrate:

Not built on buildd: arch all binaries uploaded by tjaal...@ubuntu.com, a new 
source-only upload is needed to allow migration
Not built on buildd: arch amd64 binaries uploaded by tjaal...@ubuntu.com

Since this is includes an Arch: all binary package, a binNMU won't help
in this case. Please perform an source-only upload to fix this issue.

I also wonder why libopencl-clang-dev is an Arch: all binary in the
first place. It contains an architecture specific interface -- the
symlink to the shared library provided by libopencl-clang9.

Cheers
-- 
Sebastian Ramacher

Attachment: signature.asc
Description: PGP signature


--- End Message ---
--- Begin Message ---
Source: intel-opencl-clang
Source-Version: 10.0.0-2
Done: Timo Aaltonen <tjaal...@debian.org>

We believe that the bug you reported is fixed in the latest version of
intel-opencl-clang, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 955...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Timo Aaltonen <tjaal...@debian.org> (supplier of updated intel-opencl-clang 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Wed, 08 Apr 2020 21:11:04 +0300
Source: intel-opencl-clang
Architecture: source
Version: 10.0.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian OpenCL team <pkg-opencl-de...@lists.alioth.debian.org>
Changed-By: Timo Aaltonen <tjaal...@debian.org>
Closes: 955815
Changes:
 intel-opencl-clang (10.0.0-2) unstable; urgency=medium
 .
   * control: Build -dev on amd64/i386 like the lib. (Closes: #955815)
Checksums-Sha1:
 382ed2adbb44d6652f99e75162acbf686b0a8a05 2228 intel-opencl-clang_10.0.0-2.dsc
 244fa91a38db4818f81edf4306bebcc411ed4162 4248 
intel-opencl-clang_10.0.0-2.debian.tar.xz
 5c07068331b22f01897d5ba6e1cfb042dec9fca9 7892 
intel-opencl-clang_10.0.0-2_source.buildinfo
Checksums-Sha256:
 9b68891e51d466d86e7d09dd201d9854d83fd521328d4a214d53bad0bb6d3915 2228 
intel-opencl-clang_10.0.0-2.dsc
 f48086783d9d3122c377a074f6fc6889246a3862f5b4cde3bb984dc549bb3672 4248 
intel-opencl-clang_10.0.0-2.debian.tar.xz
 d188d7d8f4444306a440c546c924a0786092a7caaa0a6468786c71619e569621 7892 
intel-opencl-clang_10.0.0-2_source.buildinfo
Files:
 e2cc083f1025dd2160df7bb4a4de88d9 2228 libs optional 
intel-opencl-clang_10.0.0-2.dsc
 d35ddcf6459a2efda0aa7232ee468da4 4248 libs optional 
intel-opencl-clang_10.0.0-2.debian.tar.xz
 c26f6d1a3a17dc7c934ffe334ac048df 7892 libs optional 
intel-opencl-clang_10.0.0-2_source.buildinfo

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEdS3ifE3rFwGbS2Yjy3AxZaiJhNwFAl6OE8cACgkQy3AxZaiJ
hNyOWA/+LkSKGR7gv3eJFDgy+hbucemnQV3mkfw2i6dShznUxRTvSqFLyIIvTdPr
ZBHTbqhB+RTgvRFRjYnnJ7Cas2x61CX8K3Jr05abFosucJZw5V8JNBc+T3T5MxSp
zmf/knUHcCVRmzjnru7AY8AUzbEHwbORWh+r8KXCLw1ESKbVU4fU/CDpDIrEd7Lv
P93luR8wlB/vuVNSLqOoQnl4SO2J3/J2T58WS0VpSHBrnX4MS3Ck594I8vn/IkJW
/eFp/lrCEbgpSmD6nenHvr7bht7cslrtN3XWZpuukT42VReFzmzHhP0jZiph4t2i
QdGvi5nJ4gSiE6jT9Naa1JQ2Uc3FAyKFjemkGVX7SH1fSdz5M25/ytexmjcHkZkc
zBK+OMsI4egk/AmQp13b6R3YJHa3FwPkVjQxJGs18/pkNnLwtcDlogi/kLDPJMHn
SIyIGu2sFvmnh8Z8y5fWSu+UbIsZTz1T1ogPdXM8m6iz0p5rme9dOChKb+wIDV/Y
12So9hI4H9Ujfn79fjIGuKYUsosxhc2S4/ad8EhEbjIAr3OVMLv2aAISkw4EJVpC
NhxbED8yifqPEYdz5dP/06NaYduCWFYcay30LhSwEIM2EKKAeELnOyX95/VNXFHd
/FakdOV3pdG6YhB7L5e2pPcfnUMClrhO8V4v2Oj3GNc2jZiCzVM=
=pzgr
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to