From: "Debian Bug Tracking System" <owner@bugs.debian.org>
To: 1066832@bugs.debian.org, 1066832-submitter@bugs.debian.org,
linux-fscrypt@vger.kernel.org
Subject: Bug#1066832: Info received (Debian #1066832: [fsverity-utils] hard Build-Depends on unportable package pandoc)
Date: Thu, 14 Mar 2024 03:33:04 +0000 [thread overview]
Message-ID: <handler.1066832.B1066832.17103869452234129.ackinfo@bugs.debian.org> (raw)
In-Reply-To: Pine.BSM.4.64L.2403140311320.10945@herc.mirbsd.org
Thank you for the additional information you have supplied regarding
this Bug report.
This is an automatically generated reply to let you know your message
has been received.
Your message is being forwarded to the package maintainers and other
interested parties for their attention; they will reply in due course.
Your message has been sent to the package maintainer(s):
Romain Perier <romain.perier@gmail.com>
If you wish to submit further information on this problem, please
send it to 1066832@bugs.debian.org.
Please do not send mail to owner@bugs.debian.org unless you wish
to report a problem with the Bug-tracking system.
--
1066832: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066832
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
next prev parent reply other threads:[~2024-03-14 4:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.BSM.4.64L.2403140237160.10945@herc.mirbsd.org>
2024-03-14 3:20 ` Debian #1066832: [fsverity-utils] hard Build-Depends on unportable package pandoc Thorsten Glaser
2024-03-14 3:33 ` Debian Bug Tracking System [this message]
2024-03-20 22:37 ` Eric Biggers
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.1066832.B1066832.17103869452234129.ackinfo@bugs.debian.org \
--to=owner@bugs.debian.org \
--cc=1066832-submitter@bugs.debian.org \
--cc=1066832@bugs.debian.org \
--cc=linux-fscrypt@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox