chore: update changelog for version 2.0.64

[18202781743]

1. Added new changelog entry for version 2.0.64
2. Included release date and maintainer information
3. Follows standard Debian changelog format
4. Maintains chronological order of releases

chore: 更新版本 2.0.64 的变更日志

1. 添加了版本 2.0.64 的新变更日志条目
2. 包含发布日期和维护者信息
3. 遵循标准的 Debian 变更日志格式
4. 保持版本发布的先后顺序

Summary by Sourcery

Update the Debian changelog to include the new 2.0.64 release entry

Chores:

• Add changelog entry for version 2.0.64 with release date and maintainer information
• Ensure the entry follows the standard Debian changelog format and chronological order

[github-actions]

TAG Bot

TAG: 2.0.64
EXISTED: no
DISTRIBUTION: unstable

[sourcery-ai]

Hey @18202781743 - 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.}

[sourcery-ai]

Reviewer's Guide

This PR appends a new Debian-formatted changelog entry for version 2.0.64, including release date, maintainer info, and ensures chronological order.

File-Level Changes

Change	Details	Files
Added new changelog entry for version 2.0.64	Added version and urgency header Included release date and maintainer information Followed standard Debian changelog entry format Maintained chronological ordering of entries	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.

[deepin-ci-robot]

deepin pr auto review

这个提交的改动主要是更新了 debian/changelog 文件，添加了一个新的版本发布记录。从代码审查的角度来看，这个改动是合理的，但可以提出以下几点建议：

1. 版本号格式：确保版本号格式符合项目的版本控制规范。通常，版本号应该遵循语义化版本控制（Semantic Versioning），即 主版本号.次版本号.修订号。例如，2.0.64 是一个合理的版本号。

2. 提交信息：提交信息应该简洁明了，并且能够清晰地描述这次提交的内容。在这个例子中，提交信息 "Release 2.0.64" 是不够具体的，建议添加更多的细节，比如这次发布包含哪些主要改动或者修复了哪些问题。

3. 日期格式：日期格式应该统一，并且使用 UTC 时间。在这个例子中，日期格式是正确的，但建议检查整个项目的日期格式是否一致。

4. 签名：提交信息中应该包含签名，以确保提交的可追溯性和安全性。在这个例子中，签名是正确的。

5. 版本号更新：在 debian/changelog 文件中，应该按照 Debian 的规范更新版本号。通常，新的版本号应该比上一个版本号大，并且按照语义化版本控制规则进行更新。

6. 翻译：如果项目是多语言的，确保提交信息中的描述是翻译过的，并且翻译是准确的。

综上所述，这个提交的改动是合理的，但可以进一步改进提交信息，确保版本号格式和日期格式的一致性，并且添加更多的细节来描述这次发布的内容。

[deepin-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: 18202781743, robertkill

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