Your message dated Sun, 1 Sep 2024 09:51:16 +0800
with message-id <[email protected]>
and subject line Re: rust-cty: fails to build rust-cty on loong64
has caused the Debian Bug report #1060910,
regarding rust-cty: fails to build rust-cty on loong64
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.)
--
1060910: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060910
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: rust-cty
Version: 0.2.1-1
Severity: normal
Dear Maintainer,
I am the maintainer for the Rust LoongArch target, and I am reporting a build
failure issue with `rust-cty` on LoongArch64. I am seeking your assistance in
addressing this issue.
I am aware that the build failure is due to the lack of LoongArch support in
`cty`. Previously, I attempted to submit a pull request to the upstream `cty`
project to address the issue. However, the project is no longer maintained, so
I kindly request your help in incorporating a fix patch into the Debian project.
The fix is a single line of code.
PR: https://github.com/japaric/cty/pull/23
-- System Information:
Debian Release: trixie/sid
APT prefers unreleased
APT policy: (500, 'unreleased'), (500, 'unstable')
Architecture: loong64 (loongarch64)
Kernel: Linux 6.6.8 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect
--- End Message ---
--- Begin Message ---
As you can see in upstream issues [#14][#24], in the PR you mentioned, and
through lack of commits, this crate is practically deprecated. There's one
single rdep in Debian, also long unmaintained. Its functionality is replaceable
by the libc crate and, to a lesser extent, core::ffi. It can be concluded that
this is no longer necessary.
[#14]: https://github.com/japaric/cty/issues/14
[#24]: https://github.com/japaric/cty/issues/24
--
Sdrager,
Blair Noctis
pgpuF7c3iEl3J.pgp
Description: OpenPGP digital signature
--- End Message ---
