chore: update changelog to 1:6.1.19

[mhduiy]

更新说明

自动更新 changelog 到版本 1:6.1.19

变更内容

• 更新 debian/changelog

版本信息

• 新版本: 1:6.1.19
• 目标分支: master

Summary by Sourcery

Chores:

• Bump Debian changelog entry to version 1:6.1.19 targeting master.

[github-actions]

TAG Bot

TAG: 6.1.19
EXISTED: no
DISTRIBUTION: unstable

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Updates the Debian packaging changelog to bump the package version to 1:6.1.19 on the master branch.

File-Level Changes

Change	Details	Files
Bump Debian package version and metadata in the changelog for release 1:6.1.19.	Add a new changelog entry for version 1:6.1.19 with appropriate metadata (maintainer, date, urgency, and summary). Ensure the new version entry is prepended so it becomes the latest release note. Align entry format with existing Debian changelog conventions to keep packaging tooling working correctly.	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

我来对这份 git diff 进行审查：

1. 格式规范：

• changelog 的格式符合 Debian 标准格式
• 版本号格式正确 (1:6.1.19)
• 维护者信息和日期格式规范
• 缩进使用两个空格，符合规范

2. 内容质量：

• 变更描述简洁明了："Fix issue where copying is not possible after clearing"
• 修复了一个重要的功能性 bug
• 版本号从 6.1.18 升级到 6.1.19，符合版本递增规则
• urgency 设置为 medium 是合理的，因为这是一个功能性修复

3. 建议改进：

• 建议在变更描述中提供更多细节，比如具体在什么场景下会出现复制失败的问题
• 可以考虑添加相关的 bug 编号（如果有）
• 日期显示为 2026 年，这可能是错误，应该修正为当前年份

4. 安全性：

• 从 changelog 无法直接评估安全性，但从描述来看是一个功能性修复，应该不涉及安全问题

5. 其他建议：

• 如果这个修复与特定的系统环境或配置相关，建议在描述中说明
• 如果有相关的测试用例，建议在描述中提及

总结：
这是一个格式规范的 changelog 条目，主要是一个功能性修复。建议补充更多细节信息，并修正日期错误。整体来说符合 Debian 包维护的标准要求。

[sourcery-ai]

Hey - 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]

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

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