国产统信uos操作系统无法安装社区版软件(deb）

[wulidi]

Chat2DB Edition

Chat2DB Community

Chat2DB Version

Chat2DB-Community-5.3.0-arm64.deb

Deployment

Desktop

Operating System

Linux

Operating System Version

统信桌面操作系统UOS专业版1070 （arm64内核，D2000处理器）

Database and Version

No response

Problem Summary

Steps to Reproduce

从官网直接下载社区版，deb安装包时出现的错误

Expected Behavior

应该要能正常安装才对

Actual Behavior

安装过程中提示依赖关系不满足

Logs

Screenshots or Additional Context

No response

Impact

Data loss

Workaround

No known workaround

Submission Checklist

• I reproduced this on the selected Chat2DB edition.
• I searched existing issues for duplicates.
• I removed credentials and private data.

[github-actions]

已了解:在统信桌面操作系统 UOS 专业版 1070(arm64,D2000)上安装 Chat2DB-Community-5.3.0-arm64.deb 时,安装过程提示依赖关系不满足。

当前必填的 Problem Summary 实际为空(两张图片均上传失败)。请补充:

• 一两句话的问题摘要;
• 安装命令的完整终端输出,尤其是具体缺少或版本不满足的依赖包名称。请先移除其中的隐私信息。

有了准确的依赖错误后,维护者即可判断是安装包依赖声明还是 UOS 软件源兼容性问题。

``

Warning

Firewall blocked 1 domain

The following domain was blocked by the firewall during workflow execution:

• awmgmcpg

To allow these domains, add them to the network.allowed list in your workflow frontmatter:

network:
  allowed:
    - defaults
    - "awmgmcpg"

See Network Configuration for more information.

Generated by AI Issue Assistant for #1929 · 9.22 AIC · ⌖ 2.65 AIC · ⊞ 16.8K · ◷

[wulidi]

补充：出现问题的操作系统为统信UOS桌面操作系统，内核为arm64，处理器为D2000。
问题：在安装社区5.3.0-1版本时出现错误提示：依赖关系不满足：libnettle8

[wulidi]

已了解:在统信桌面操作系统 UOS 专业版 1070(arm64,D2000)上安装 Chat2DB-Community-5.3.0-arm64.deb 时,安装过程提示依赖关系不满足。

当前必填的 Problem Summary 实际为空(两张图片均上传失败)。请补充:

• 一两句话的问题摘要;
• 安装命令的完整终端输出,尤其是具体缺少或版本不满足的依赖包名称。请先移除其中的隐私信息。

有了准确的依赖错误后,维护者即可判断是安装包依赖声明还是 UOS 软件源兼容性问题。

``

Warning

Firewall blocked 1 domain

Generated by AI Issue Assistant for #1929 · 9.22 AIC · ⌖ 2.65 AIC · ⊞ 16.8K · ◷

[openai0229]

Triage result: Backlog, P1. The added evidence identifies libnettle8 as the blocking dependency on UOS 1070 arm64. The next step is to trace whether that dependency is introduced by jpackage, the bundled JCEF/runtime, or the UOS package resolver, then record whether the arm64 AppImage is a valid workaround. Release-owner approval is required before changing package dependencies.