Your message dated Mon, 05 Jan 2026 07:35:14 +0000
with message-id <[email protected]>
and subject line Bug#1124644: fixed in ggml 0.9.5-2
has caused the Debian Bug report #1124644,
regarding ggml FTBFS on riscv64
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 [email protected]
immediately.)


-- 
1124644: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1124644
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: ggml
Version: 0.9.5-1
Severity: serious
Tags: ftbfs sid

ggml FTBFS on riscv64, here the relevant part of the log:

In file included from 
/build/reproducible-path/ggml-0.9.5/src/ggml-cpu/ggml-cpu.c:14:
/build/reproducible-path/ggml-0.9.5/src/ggml-cpu/vec.h: In function 
‘ggml_vec_dot_f16_unroll’:
/build/reproducible-path/ggml-0.9.5/src/ggml-cpu/vec.h:293:31: error: 
‘GGML_F16_STEP’ undeclared (first use in this function); did you mean 
‘GGML_F32_STEP’?
  293 |         const int np = (n & ~(GGML_F16_STEP - 1));
      |                               ^~~~~~~~~~~~~
      |                               GGML_F32_STEP
/build/reproducible-path/ggml-0.9.5/src/ggml-cpu/vec.h:293:31: note: each 
undeclared identifier is reported only once for each function it appears in
/build/reproducible-path/ggml-0.9.5/src/ggml-cpu/vec.h:295:9: error: unknown 
type name ‘GGML_F16_VEC’; did you mean ‘GGML_F32_VEC’?
  295 |         GGML_F16_VEC sum[GGML_VEC_DOT_UNROLL][GGML_F16_ARR] = { { 
GGML_F16_VEC_ZERO } };
      |         ^~~~~~~~~~~~
      |         GGML_F32_VEC

--- End Message ---
--- Begin Message ---
Source: ggml
Source-Version: 0.9.5-2
Done: Christian Kastner <[email protected]>

We believe that the bug you reported is fixed in the latest version of
ggml, 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 [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Christian Kastner <[email protected]> (supplier of updated ggml 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 [email protected])


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

Format: 1.8
Date: Mon, 05 Jan 2026 08:28:48 +0100
Source: ggml
Architecture: source
Version: 0.9.5-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Deep Learning Team <[email protected]>
Changed-By: Christian Kastner <[email protected]>
Closes: 1124644
Changes:
 ggml (0.9.5-2) unstable; urgency=medium
 .
   * Temporarily revert riscv64 to minimal feature flags (Closes: #1124644)
Checksums-Sha1:
 8d4e3e8292f7d0d87d8d451a6318181a3d629f1e 2792 ggml_0.9.5-2.dsc
 f96e16816dcf2612b15dec020d7ff3e98a1ac856 15020 ggml_0.9.5-2.debian.tar.xz
 aabc7a85b77a756b09a28d91629fa12f1bf92673 6529 ggml_0.9.5-2_source.buildinfo
Checksums-Sha256:
 c199a2216a630594430d6aafb04245d3ee8a41b6387ea48f644e4daa4decd4fa 2792 
ggml_0.9.5-2.dsc
 643831b3646e07cecdfb5ef22cfab7aadaec25db182485594fb7d6b228eae9d8 15020 
ggml_0.9.5-2.debian.tar.xz
 922d4cf681de4f4c47894d6c31b9e9984882be36df980076eaa4be137af3bcdb 6529 
ggml_0.9.5-2_source.buildinfo
Files:
 336f437f180d3089f92651298042756f 2792 libs optional ggml_0.9.5-2.dsc
 84b66412be6864392d3ca955ffdf3c95 15020 libs optional ggml_0.9.5-2.debian.tar.xz
 ccddf043fc428da2398da1cf2bdc3451 6529 libs optional 
ggml_0.9.5-2_source.buildinfo

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

iQIzBAEBCgAdFiEEQZ9+mkfDq5UZ8bCjOZU6N95Os2sFAmlbaK4ACgkQOZU6N95O
s2vrCQ/+M94jRlEEGD9PtzNv7jvGCJaaIF2v/EQURMdrQLiKdyRDv9xnFZVcf1Jq
b6RwCUxXHw4+SULMHY7byvcD/C3iE1darBXVN26qOFw54CTeKl6XAfn2aAjTyA0Y
ANSs2FRC7fEt7vcKlABuqWOj4iov3znpDRw3u9YdAJqlSa6wNQL1megMitQ/T18S
wDCktO9xKsQshBIQ07BdEO86F3R2DmzjeF8M45F31MD6QHGmq6t8eHK+UrAA72rK
DRmgMgN6D/JEDWoowktNthJlv3FZy1a9Ige+AIEcbSQxILPi2L3MVXOqTZktPCLc
gITrQ/BLIKJN+0RXClBp942+vtK33Lg9Pe9qLyhOau4pLJTNeexdhkjV7qXlSCbF
PJ8iAXq1EQ84YRljDWzW0PoJZ9FnO7y00+EVd42bwDmxRYT64Tpul9FFXQet+m1E
iEsTkeyxX6kav+rP9Tjj87hhv6APXgSoMu2BX4Lk6n2UgW8hXuSbyh/ES+dkruVC
slEHVXGD+oKT3zSkiVL+kECVIrLutcdzeBNPioMgyZGKo6p8EXxEPwdeyCgK2/ne
JQ1XoeWiCpBpQuGIzlM00XFNBvx9Vtdgv5+B0bnD0UgH2q9EWW3kExhJgvS/QeeF
v67M6kKxpuWE/2rIvXhkybRLVlBNNbgRUcapRgDZ1W6EHQTHGd4=
=u6g+
-----END PGP SIGNATURE-----

Attachment: pgpomd2wO2MEa.pgp
Description: PGP signature


--- End Message ---

Reply via email to