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

Bug#889596: marked as done (libpinyin: FTBFS on sparc64: bus error in gen_binary_files)

Your message dated Thu, 30 Oct 2025 19:19:45 +0000
with message-id <E1vEYBV-006eee-0D@fasolo.debian.org>
and subject line Bug#889596: fixed in libpinyin 2.10.3-1
has caused the Debian Bug report #889596,
regarding libpinyin: FTBFS on sparc64: bus error in gen_binary_files
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.)


-- 
889596: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889596
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Source: libpinyin
Version: 2.1.91-1
Severity: normal
Tags: upstream
User: debian-sparc@lists.debian.org
Usertags: sparc64

Builds of libpinyin for sparc64 (admittedly not a release architecture)
have been failing:

  ../utils/storage/gen_binary_files --table-dir ../data
  Makefile:539: recipe for target 'bigram.db' failed
  make[3]: *** [bigram.db] Bus error

This error most likely indicates an unaligned memory access attempt, to
which sparc64 is particularly sensitive.  Could you please take a look?

Thanks!

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?amu@monk.mit.edu

--- End Message ---
--- Begin Message --- 
Source: libpinyin
Source-Version: 2.10.3-1
Done: Boyuan Yang <byang@debian.org>

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

Debian distribution maintenance software
pp.
Boyuan Yang <byang@debian.org> (supplier of updated libpinyin 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: Thu, 30 Oct 2025 14:52:21 -0400
Source: libpinyin
Architecture: source
Version: 2.10.3-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Input Method Team <debian-input-method@lists.debian.org>
Changed-By: Boyuan Yang <byang@debian.org>
Closes: 889596
Changes:
 libpinyin (2.10.3-1) unstable; urgency=medium
 .
   * Team upload.
   * Upload to unstable. (Closes: #889596)
Checksums-Sha1:
 b0611f32d8e81a9783a576c4a870dd302cc87109 2534 libpinyin_2.10.3-1.dsc
 a60e2b44b97cb061ca8b6b14c21b6aa5c6d089fa 20624870 libpinyin_2.10.3.orig.tar.gz
 44c9642ee84a599d1f78cf2c51dc67e3ae3b2d5f 6612 libpinyin_2.10.3-1.debian.tar.xz
 3945f08a852512fef876346e8278105b7abf47c1 9500 libpinyin_2.10.3-1_amd64.buildinfo
Checksums-Sha256:
 05e5bab3ce3c6a68c9a9a63f3d57bfc84c4b45eacb68dabd0db15bda9abadac0 2534 libpinyin_2.10.3-1.dsc
 3fe786ff2c2059bdbdf9d8d752db691a516a941a977521955fe0af3f0b4db299 20624870 libpinyin_2.10.3.orig.tar.gz
 6e8ab56e924d93721d0c0cab0ec4d2229a7de5aeca5d5562e473285b63a8a671 6612 libpinyin_2.10.3-1.debian.tar.xz
 b1c434570e4c24913f37659757ca6758ebb4b742d3724393f4c485df3165a72e 9500 libpinyin_2.10.3-1_amd64.buildinfo
Files:
 6a124af9bf566f3f21651f2de483cd6e 2534 libs optional libpinyin_2.10.3-1.dsc
 3ec265036485e0c7ff69e3007bffa550 20624870 libs optional libpinyin_2.10.3.orig.tar.gz
 1eaabcc6aaed6a842245d307d4664017 6612 libs optional libpinyin_2.10.3-1.debian.tar.xz
 d982a89dd14e87c76816e1d739c7d65d 9500 libs optional libpinyin_2.10.3-1_amd64.buildinfo

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

iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAmkDtTQACgkQwpPntGGC
Ws5GjQ/+OraE4289osiV3MaPUK7esT9jvh/UK94cvQxFSTdTAL9R1WR4xDcncIZp
CGamW2Tuf3UguY3yD4N01moyuKm9cR2j4L2wtt6u7K31RXk7UnTkHfSngUc5n7Im
GPZjKVE52C4+v+ATKRMwbwtsZiHTIVrKSv+dwhSzgGnFUqaeKkgA/j87x2l7RFzB
8PQlWU5QG0DyzPEAR4u+Gg2QWEpIvqf9mLVW1fz4IfyZE4WLBDUSSZmsgVtSPpDC
LKzSjG8t3vIRtsp0jWE8aGoo3biLlKKQNsoORlz4k6CNXMb84G8Kh0iwZAgjHbqq
D07lk1Z8jGVXqi44FgVpqUDMYZs7+JVLkRW4YWYaJOKfr2oXBOLkqeeeWzT7u4ea
9f0sS/RAM+uLwdB0pOryyJLQJPK8fqfGnSTWdWpokKP2c+KKZTqHE7PqHYjfkDTI
amU5YppajGjGHy4I7jqYr7Jw3hj5OlvXInl4mSbCiHsmhTJZUyieNXLJVfS4ld3n
S5dUTgCmq/cW1aBQ5Us0HyJI5Zy6dfyqSs/u6cjihbTm0vJWbKpLulnzEBIuitOE
G1KOrhY+bD2uIBq9TsWIsb0XXodetN2ImU6rh5GS7GZ1WhyW/uZkDf3a1ByD+7Fu
/7B5eOC+9nJxMrjWdn8pdqEIeJ0KsZWjLNbxb8ElfGEnGL9lqGw=
=VFoV
-----END PGP SIGNATURE-----

Attachment: pgpZkPwkRZ6Mo.pgp
Description: PGP signature


--- End Message ---
Reply to: