From: "Debian Bug Tracking System" <owner@bugs.debian.org>
To: Andreas Beckmann <anbe@debian.org>
Cc: debian-on-mobile-maintainers@alioth-lists.debian.net,
linux-xfs@vger.kernel.org, jfs@debian.org, agx@sigxcpu.org,
bernat@debian.org, debian-med-packaging@lists.alioth.debian.org,
debian-multimedia@lists.debian.org, dr@jones.dk,
pkg-privacy-maintainers@lists.alioth.debian.org,
debian-xml-sgml-pkgs@lists.alioth.debian.org,
team+pkg-security@tracker.debian.org
Subject: Processed: tagging 1071837, tagging 1071931, tagging 1071934, tagging 1071838, tagging 1071832, tagging 1071860 ...
Date: Thu, 20 Jun 2024 05:33:09 +0000 [thread overview]
Message-ID: <handler.s.C.17188615123053551.transcript@bugs.debian.org> (raw)
In-Reply-To: 1718861509-739-bts-anbe@debian.org
Processing commands for control@bugs.debian.org:
> tags 1071837 + sid trixie
Bug #1071837 [src:chntpw] chntpw: Please use pkg-config instead of libgcrypt-config to locate libgcrypt
Added tag(s) sid and trixie.
> tags 1071931 + sid trixie
Bug #1071931 [src:libaacs] libaacs: FTBFS against libgcrypt 1.11
Added tag(s) trixie and sid.
> tags 1071934 + sid trixie
Bug #1071934 [src:libpam-ccreds] libpam-ccreds: FTBFS against libgcrypt 1.11
Added tag(s) sid and trixie.
> tags 1071838 + sid trixie
Bug #1071838 [src:clamz] clamz: FTBFS against libgcrypt 1.11
Added tag(s) sid and trixie.
> tags 1071832 + sid trixie
Bug #1071832 [src:aircrack-ng] aircrack-ng: FTBFS against libgcrypt 1.11
Added tag(s) sid and trixie.
> tags 1071860 + sid trixie
Bug #1071860 [src:fis-gtm] fis-gtm: Searches for libgcrypt with libgcrypt-config
Added tag(s) trixie and sid.
> tags 1071932 + sid trixie
Bug #1071932 [src:libbdplus] libbdplus: FTBFS against libgcrypt 1.11
Added tag(s) sid and trixie.
> tags 1071937 + sid trixie experimental
Bug #1071937 [src:libxslt] libxslt: FTBFS against libgcrypt 1.11
Added tag(s) trixie, experimental, and sid.
> tags 1070892 + sid trixie
Bug #1070892 [src:abiword] abiword: Please use pkg-config instead of libgcrypt-config to locate libgcrypt
Added tag(s) sid and trixie.
> tags 1070903 + sid trixie
Bug #1070903 [src:axc] axc: Please use pkg-config instead of libgcrypt-config to locate libgcrypt
Added tag(s) trixie and sid.
> notfound 1073831 xfslibs-dev/6.8.0-2.1
Bug #1073831 [xfslibs-dev] xfsdump:FATAL ERROR: could not find a current XFS handle library
The source xfslibs-dev and version 6.8.0-2.1 do not appear to match any binary packages
No longer marked as found in versions xfslibs-dev/6.8.0-2.1.
> found 1073831 6.8.0-2.1
Bug #1073831 [xfslibs-dev] xfsdump:FATAL ERROR: could not find a current XFS handle library
Marked as found in versions xfsprogs/6.8.0-2.1.
> tags 1071941 + sid trixie experimental
Bug #1071941 [src:monkeysphere] monkeysphere: FTBFS against libgcrypt 1.11 (and next libassuan)
Added tag(s) experimental, sid, and trixie.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1070892: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070892
1070903: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070903
1071832: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071832
1071837: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071837
1071838: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071838
1071860: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071860
1071931: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071931
1071932: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071932
1071934: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071934
1071937: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071937
1071941: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071941
1073831: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073831
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
parent reply other threads:[~2024-06-20 5:33 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1718861509-739-bts-anbe@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.17188615123053551.transcript@bugs.debian.org \
--to=owner@bugs.debian.org \
--cc=agx@sigxcpu.org \
--cc=anbe@debian.org \
--cc=bernat@debian.org \
--cc=debian-med-packaging@lists.alioth.debian.org \
--cc=debian-multimedia@lists.debian.org \
--cc=debian-on-mobile-maintainers@alioth-lists.debian.net \
--cc=debian-xml-sgml-pkgs@lists.alioth.debian.org \
--cc=dr@jones.dk \
--cc=jfs@debian.org \
--cc=linux-xfs@vger.kernel.org \
--cc=pkg-privacy-maintainers@lists.alioth.debian.org \
--cc=team+pkg-security@tracker.debian.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