From: "Debian Bug Tracking System" <owner@bugs.debian.org>
To: Adrian Bunk <bunk@debian.org>
Cc: linux-xfs@vger.kernel.org, debian-release@lists.debian.org
Subject: Processed: unarchiving 1116595, fixed 1116595 in 6.19.0-1, tagging 1128511
Date: Thu, 02 Jul 2026 20:35:03 +0000 [thread overview]
Message-ID: <handler.s.C.17830243713682752.transcript@bugs.debian.org> (raw)
In-Reply-To: 1783024369-277-bts-bunk@debian.org
Processing commands for control@bugs.debian.org:
> unarchive 1116595
Bug #1116595 {Done: Bastian Germann <bage@debian.org>} [xfsprogs] Packaging issue: xfs_scrub_all_fail.service NoNewPrivileges breaks emailing reports
Bug #1128087 {Done: Bastian Germann <bage@debian.org>} [xfsprogs] xfs_scrub_all_fail.service: fails to email report (might be similar to bug #1116595)
Unarchived Bug 1116595
Unarchived Bug 1128087
> fixed 1116595 6.19.0-1
Bug #1116595 {Done: Bastian Germann <bage@debian.org>} [xfsprogs] Packaging issue: xfs_scrub_all_fail.service NoNewPrivileges breaks emailing reports
Bug #1128087 {Done: Bastian Germann <bage@debian.org>} [xfsprogs] xfs_scrub_all_fail.service: fails to email report (might be similar to bug #1116595)
Marked as fixed in versions xfsprogs/6.19.0-1.
Marked as fixed in versions xfsprogs/6.19.0-1.
> tags 1128511 - moreinfo
Bug #1128511 [release.debian.org] trixie-pu: package xfsprogs/6.13.0-2+deb13u1
Removed tag(s) moreinfo.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1116595: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1116595
1128087: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1128087
1128511: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1128511
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
parent reply other threads:[~2026-07-02 20:44 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1783024369-277-bts-bunk@debian.org>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=handler.s.C.17830243713682752.transcript@bugs.debian.org \
--to=owner@bugs.debian.org \
--cc=bunk@debian.org \
--cc=debian-release@lists.debian.org \
--cc=linux-xfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.