feat: add Qt5 and Qt6 dual version support

[Kakueeen]

Added support for both Qt5 and Qt6 frameworks to ensure compatibility
across different system environments. This change allows the application
to work seamlessly with either Qt version, providing flexibility for
users and developers while maintaining backward compatibility.

Log: Added dual Qt version support for better compatibility

Influence:

1. Test application functionality with Qt5 installation
2. Test application functionality with Qt6 installation
3. Verify no regression in existing features
4. Check UI rendering consistency across both Qt versions
5. Test application startup and basic operations
6. Verify plugin loading and dependency resolution

feat: 添加 Qt5 和 Qt6 双版本支持

添加了对 Qt5 和 Qt6 框架的双重支持，确保在不同系统环境下的兼容性。此更改
使应用程序能够与任一 Qt 版本无缝协作，为用户和开发人员提供灵活性，同时保
持向后兼容性。

Log: 新增双 Qt 版本支持以提升兼容性

Influence:

1. 在 Qt5 环境下测试应用程序功能
2. 在 Qt6 环境下测试应用程序功能
3. 验证现有功能无回归问题
4. 检查两个 Qt 版本下的 UI 渲染一致性
5. 测试应用程序启动和基本操作
6. 验证插件加载和依赖项解析

Summary by Sourcery

Build:

• Record Qt5 and Qt6 dual-version support in the Debian changelog for packaging distribution.

[github-actions]

TAG Bot

TAG: 1.5.10
EXISTED: no
DISTRIBUTION: unstable

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

This pull request prepares for Qt5/Qt6 dual-version support by updating Debian packaging metadata, but the provided diff only shows that debian/changelog is touched without exposing its content, so reviewers should focus on confirming that the changelog entry correctly documents the new dual Qt support and follows Debian conventions.

File-Level Changes

Change	Details	Files
Update Debian changelog to document Qt5/Qt6 dual-version support	Add a new changelog entry describing the addition of dual Qt5/Qt6 framework support Ensure the entry includes an appropriate version, distribution target, and maintainer signature per Debian policy Document potential impact areas such as runtime compatibility, UI rendering, and plugin loading so downstream users know what changed	debian/changelog

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey there - I've reviewed your changes - here's some feedback:

• The PR description talks about adding dual Qt5/Qt6 support, but the current diff only touches debian/changelog; if there are code or packaging changes required for the new Qt support, they appear to be missing from this PR.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- The PR description talks about adding dual Qt5/Qt6 support, but the current diff only touches `debian/changelog`; if there are code or packaging changes required for the new Qt support, they appear to be missing from this PR.

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[deepin-ci-robot]

deepin pr auto review

我来帮你审查这个 changelog 文件的变更：

1. 语法逻辑：

• 格式符合 Debian changelog 的标准格式，包含版本号、发行版和紧急程度
• 变更条目使用了规范的缩进和项目符号格式
• 维护者信息和日期格式正确

2. 代码质量：

• 变更描述简洁明了，准确反映了功能变更
• 使用了标准的变更类型标记 "feat" 表示新功能
• 版本号递增合理（1.5.9 -> 1.5.10）

3. 改进建议：

• 建议在变更描述中提供更多细节，比如：
  • Qt5 和 Qt6 双版本支持的具体实现方式
  • 是否涉及 API 变更
  • 对现有功能的影响
• 可以考虑添加相关的 bug 编号或任务编号，便于追踪
• 建议在变更描述中说明这个变更的动机和带来的好处

4. 安全性考虑：

• 由于涉及 Qt 版本支持，建议确认：
  • 是否需要额外的安全补丁
  • 是否有版本兼容性相关的安全考虑
  • 新版本 Qt 的安全特性是否得到充分利用

示例改进版本：

dde-device-formatter (1.5.10) unstable; urgency=medium

  * feat: add Qt5 and Qt6 dual version support
    - Implement compatibility layer for both Qt5 and Qt6
    - Update build system to support conditional compilation
    - Ensure all existing features work with both Qt versions
    - (Closes: #bug-number)

 -- Liu Zhangjian <[email protected]>  Wed, 17 Dec 2025 14:43:16 +0800

这样的改进可以让变更记录更加完整和有用，便于其他开发者理解和维护。

[deepin-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: Kakueeen, lzwind

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• debian/deepin/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment