chore: update dde-control-center dependency version

[caixr23]

Updated the build dependency from dde-control-center-dev (> 6.1.70) to dde-control-center-dev (>= 6.1.71) to ensure compatibility with the latest version. This change allows the package to build with version 6.1.71 and above while maintaining backward compatibility. The version bump is necessary to incorporate new features or bug fixes provided in the updated control center development package.

Influence:

1. Verify that the package builds successfully with dde-control-center- dev version 6.1.71
2. Test backward compatibility with older versions (should fail with versions below 6.1.71)
3. Ensure all dependent functionality works correctly with the updated dependency

chore: 更新 dde-control-center 依赖版本

将构建依赖从 dde-control-center-dev (> 6.1.70) 更新为 dde-control- center-dev (>= 6.1.71)，以确保与最新版本的兼容性。此更改允许包在 6.1.71 及以上版本中构建，同时保持向后兼容性。版本更新是为了整合更新控制中心开发
包提供的新功能或错误修复。

Influence:

1. 验证包是否能在 dde-control-center-dev 6.1.71 版本下成功构建
2. 测试与旧版本的向后兼容性（6.1.71 以下版本应构建失败）
3. 确保所有依赖功能在更新依赖后正常工作

Summary by Sourcery

Build:

• Update debian packaging to depend on dde-control-center-dev (>= 6.1.71) instead of (> 6.1.70).

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Updates the Debian packaging build dependency on dde-control-center-dev to require version 6.1.71 or newer instead of > 6.1.70, tightening the minimum supported version for building while aligning with the latest control center dev package.

File-Level Changes

Change	Details	Files
Tighten the minimum required version of the dde-control-center-dev build dependency in Debian packaging.	Adjust the version constraint to require dde-control-center-dev (>= 6.1.71) instead of (> 6.1.70) in the Build-Depends field Align Debian control metadata with the expected minimum control center development package version for building	debian/control

---

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 - I've left some high level feedback:

• The new constraint >= 6.1.71 is functionally equivalent to the existing > 6.1.70, so if the intent is to enforce a stricter minimum or reflect new functionality, consider either adjusting the description (which currently suggests a behavioral change) or updating the version requirement to a truly new minimum.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- The new constraint `>= 6.1.71` is functionally equivalent to the existing `> 6.1.70`, so if the intent is to enforce a stricter minimum or reflect new functionality, consider either adjusting the description (which currently suggests a behavioral change) or updating the version requirement to a truly new minimum.

---

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

这段代码是 debian/control 文件的一部分，该文件用于定义 Debian 软件包的构建依赖关系和元数据。具体的修改是将对 dde-control-center-dev 包的版本约束从严格大于 (>) 6.1.70 修改为大于或等于 (>=) 6.1.71。

以下是针对该修改的详细审查意见：

1. 语法逻辑

• 语法正确性：Debian 控制文件的语法是正确的。版本号约束格式 package (>= version) 是标准的写法。
• 逻辑一致性：
  • 修改前：> 6.1.70 意味着依赖版本必须严格大于 6.1.70。由于版本号通常是整数递增的，这实际上排除了 6.1.70，但允许 6.1.71 及以上。
  • 修改后：>= 6.1.71 意味着依赖版本必须是 6.1.71 或更高。
  • 潜在问题：这两个条件在逻辑上并不完全等价。
    • 如果存在 6.1.70.1 这样的补丁版本，修改前的条件 > 6.1.70 会接受它，而修改后的条件 >= 6.1.71 会拒绝它。
    • 如果 6.1.71 是一个破坏性更新或引入了不兼容的 API，强制要求 >= 6.1.71 可能会导致旧版系统无法构建该包。
• 建议：请确认 6.1.71 是否是修复了特定 Bug 或引入了必须使用的 API 的最小版本。如果是为了兼容 6.1.70.1 这样的补丁版本，通常使用 >= 6.1.70.1 或保持 > 6.1.70 可能更合适。但如果确定 6.1.71 是基准版本，则当前修改是合理的。

2. 代码质量

• 规范性：符合 Debian 打包规范，格式排版整洁。
• 明确性：指定具体的版本号（6.1.71）使得构建环境更加明确，有助于避免因依赖库版本过低导致的编译错误或运行时错误。

3. 代码性能

• 不适用：这是一个配置文件，不涉及运行时代码，因此不直接涉及代码执行性能。

4. 代码安全

• 依赖安全性：通过提高最低依赖版本到 6.1.71，通常意味着引入了上游的安全补丁或 Bug 修复。从安全角度来看，强制使用包含修复的较新版本是积极的措施。
• 供应链安全：确保构建依赖的版本明确，有助于减少构建环境的不确定性，防止使用了包含已知漏洞的旧版本库。

总结与改进建议

这个修改的主要目的是将构建依赖 dde-control-center-dev 的基准版本提升到 6.1.71。

改进建议：

1. 确认版本逻辑：请再次确认是否存在 6.1.70.x 的版本。如果上游发布过 6.1.70.1 或 6.1.70.2 等包含必要修复的版本，直接跳到 >= 6.1.71 可能会导致这些中间版本无法被使用。如果确定 6.1.71 是第一个可用版本，则无需担心。
2. Changelog 更新：虽然不在本次 diff 中，但请确保在 debian/changelog 文件中添加了相应的条目，说明为什么要升级这个依赖（例如："Update build-dep on dde-control-center-dev to >= 6.1.71 for new API support"）。

总体而言，如果 6.1.71 确实是引入了必要功能或修复的版本，这是一个合理且规范的修改。

[deepin-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: caixr23, mhduiy

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