chore: release dde-network-core 2.0.60

[BLumia]

Changelog:

• chore: Modify compilation issues
• i18n: Update translations

Log:

Summary by Sourcery

Prepare and release dde-network-core version 2.0.60 with compilation fixes and updated translations.

Enhancements:

• Fix compilation issues
• Update i18n translations

Chores:

• Update Debian changelog for version 2.0.60

[deepin-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: BLumia

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

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

[sourcery-ai]

Reviewer's Guide

This PR prepares the Debian packaging for the 2.0.60 release by updating the changelog with the latest compilation fixes and translation updates.

File-Level Changes

Change	Details	Files
Debian changelog updated for new release	Bump package version to 2.0.60 Add entries for compilation issue fixes Add entries for translation updates Update release date and metadata	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 @BLumia - I've reviewed your changes and they look great!

---

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. 日志条目内容：虽然日志条目内容简洁明了，但可以进一步详细说明修改的具体内容，例如编译问题的具体修改点，以及翻译更新的具体内容。这有助于其他开发者理解这次提交的背景和影响。

2. 版本号管理：确保版本号的更新是符合语义化版本控制的规则的。如果只是小版本号的更新，应该只增加最后一位数字，而不是直接跳到2.0.60。

3. 提交信息格式：虽然提交信息格式基本正确，但建议使用更标准的格式，例如：

   dde-network-core (2.0.60) unstable; urgency=medium
   
     * chore: 修复编译问题
     * i18n: 更新翻译
   
   -- Wang Zichong <[email protected]>  Sat, 21 Jun 2025 13:42:00 +0800
   

   这样可以更清晰地表达提交的目的和内容。

4. 时间戳格式：时间戳格式看起来是正确的，但建议使用标准的日期格式，例如 YYYY-MM-DD HH:MM:SS。

5. 签名：确保提交信息中包含签名，以便其他开发者验证提交者的身份。

综上所述，虽然这个提交在语法和逻辑上没有问题，但可以通过改进日志条目的详细性和格式来提高代码质量和可维护性。

[github-actions]

TAG Bot

TAG: 2.0.60
EXISTED: no
DISTRIBUTION: unstable

[deepin-bot]

TAG Bot

New tag: 2.0.60
DISTRIBUTION: unstable
Suggest: synchronizing this PR through rebase #364