[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1118633: marked as done (rocr-runtime ftbfs on arm64 and ppc64el, where it built before)



Your message dated Sat, 25 Oct 2025 09:50:01 +0000
with message-id <E1vCauP-00DznN-1x@fasolo.debian.org>
and subject line Bug#1118633: fixed in rocr-runtime 6.4.3+dfsg-2
has caused the Debian Bug report #1118633,
regarding rocr-runtime ftbfs on arm64 and ppc64el, where it built before
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 owner@bugs.debian.org
immediately.)


-- 
1118633: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1118633
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: src:rocr-runtime
Version: 6.4.3+dfsg-1
Severity: serious
Tags: sid forky

rocr-runtime ftbfs on arm64 and ppc64el, where it built before. 6/7 version mismatch?
--- End Message ---
--- Begin Message ---
Source: rocr-runtime
Source-Version: 6.4.3+dfsg-2
Done: Cordell Bloor <cgmb@debian.org>

We believe that the bug you reported is fixed in the latest version of
rocr-runtime, 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 1118633@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Cordell Bloor <cgmb@debian.org> (supplier of updated rocr-runtime 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 ftpmaster@ftp-master.debian.org)


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

Format: 1.8
Date: Sat, 25 Oct 2025 03:21:31 -0600
Source: rocr-runtime
Architecture: source
Version: 6.4.3+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian ROCm Team <debian-ai@lists.debian.org>
Changed-By: Cordell Bloor <cgmb@debian.org>
Closes: 1118633
Changes:
 rocr-runtime (6.4.3+dfsg-2) unstable; urgency=medium
 .
   * Add d/p/0012-strip-x86-intrinsics-from-xdna-support.patch and
     d/p/0013-add-arm-and-ppc-memory-barriers.patch to fix FTBFS on
     arm64 and ppc64el (Closes: #1118633)
   * Add Breaks libamdhip64-5 and rocm-opencl-icd annotations to
     libhsa-runtime64-1 as the introduction of support for generic
     ISAs has broken key assumptions in the ROCm Common Language Runtime.
Checksums-Sha1:
 4e5b59a7a568e58ab1ed3bd91c1a0685e4dcccd4 2739 rocr-runtime_6.4.3+dfsg-2.dsc
 c161705ea2bca5347bf69c7acc2825cc4a33dd12 19956 rocr-runtime_6.4.3+dfsg-2.debian.tar.xz
 c92d99c7e6015f9bb7fc3f0fabe811a383d512e9 8195 rocr-runtime_6.4.3+dfsg-2_source.buildinfo
Checksums-Sha256:
 048afd23bc284bca6590c0baa5667b57d461263f00c0275f5be5d4167847e417 2739 rocr-runtime_6.4.3+dfsg-2.dsc
 c097e69198a27cde6c787ab48d44f9ec41f64a71aadcbd27dc783f7010a152ea 19956 rocr-runtime_6.4.3+dfsg-2.debian.tar.xz
 aebe818c41051e22d807bceae375332b74c939e8d5a0c26456aa25f79584ba32 8195 rocr-runtime_6.4.3+dfsg-2_source.buildinfo
Files:
 94fd8b83d9195086461290260c1cbda9 2739 video optional rocr-runtime_6.4.3+dfsg-2.dsc
 e0c7429e855a5ca0153acd7383ad6048 19956 video optional rocr-runtime_6.4.3+dfsg-2.debian.tar.xz
 bb851c80949eaaa1ff6b5e48e7d43ddb 8195 video optional rocr-runtime_6.4.3+dfsg-2_source.buildinfo

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

wsG7BAEBCgBvBYJo/JdOCRD5747gwCFjD0cUAAAAAAAeACBzYWx0QG5vdGF0aW9u
cy5zZXF1b2lhLXBncC5vcmcrSDp6g01W2lpMYDZ+WZX58SOo2NDOadFEAIRC/+Ve
2RYhBAzgb+OSqkj40i5EcfnvjuDAIWMPAACnpA//bKzIiXrpIE3TNR9AWPEzEEji
lGQydpNTUiij3LCfs/dp1Ku1cCiWY8ljIV5BD6Ngq1Tal52MdvsukANU9Jcvxa1j
QE9gi+uHXxYgNzeBQIvtzP+2uea7hRtcbPxnpYYPZTLTb1KIWNPpdH/HCMgSbRlQ
gYrGi+AzFKf4lkSu1iEnGFPpDImq8dFD919PxDqkU4FpS6vBCdx20PT+x3AB/KLZ
aPhzzvzFQBgeFX9XyehlbUft0XE9E5Uua6XbsLJNRIIOSCGl4C0Al6igXGufkjZo
W6OxynXgIEI0vaq8oQZrWooRmJAKqqSVL2V9kdy9vGGpIWVeib+Vxg6eh+RYuS1q
24G1K6vQqylrCTT4LtLgJhM/D9E6/YGXM2JnlQrTEk7TiHxbPIa/0joWXYtGUQkx
EwSQlR/P9f4cMNnvAozkzRekRTNv23xFhpLi9m3ZrrwAfgHwl3PIoQfHmIk5AgoF
kcO212+Y486zINQ3YCMjHkAYfXVMO2UCNdWFsdc2pqj9WzbkeGE8okprnhID1wZm
xC/KohtIeIe/m7kOffURuDN0zlNlL8RhTMFJclckADX/8GazXDr2FmtdUJzfexih
yMPwX3H7aoR3DMhSH68aHyL4nJce5jt9W4dHrN0i9SxCxs0Vh93ax/zpdl0cR0qi
keGlW5VfbXQsAymEYHw=
=Z1BW
-----END PGP SIGNATURE-----

Attachment: pgpug5Dw9tEzl.pgp
Description: PGP signature


--- End Message ---

Reply to: