From: "Debian Bug Tracking System" <owner@bugs.debian.org>
To: Giovanni Mascellani <gio@debian.org>
Cc: linux-xfs@vger.kernel.org, team+boost@tracker.debian.org
Subject: Processed (with 1 error): Re: Bug#1000974: copy_move_algo.hpp:1083:10: error: ‘__fallthrough__’ was not declared in this scope; did you mean ‘fallthrough’?
Date: Sun, 05 Dec 2021 15:57:07 +0000 [thread overview]
Message-ID: <handler.s.C.16387197672501.transcript@bugs.debian.org> (raw)
In-Reply-To: c7ccff50-c177-7f96-2d99-2077f77374ad@debian.org
Processing commands for control@bugs.debian.org:
> reassign 1000974 xfslibs-dev
Bug #1000974 [libboost1.74-dev] copy_move_algo.hpp:1083:10: error: ‘__fallthrough__’ was not declared in this scope; did you mean ‘fallthrough’?
Bug reassigned from package 'libboost1.74-dev' to 'xfslibs-dev'.
No longer marked as found in versions boost1.74/1.74.0-13.
Ignoring request to alter fixed versions of bug #1000974 to the same values previously set
> severity 1000974 important
Bug #1000974 [xfslibs-dev] copy_move_algo.hpp:1083:10: error: ‘__fallthrough__’ was not declared in this scope; did you mean ‘fallthrough’?
Ignoring request to change severity of Bug 1000974 to the same value.
> retitle 1000974 xfs/linux.h defines common word "fallthrough" breaking
Bug #1000974 [xfslibs-dev] copy_move_algo.hpp:1083:10: error: ‘__fallthrough__’ was not declared in this scope; did you mean ‘fallthrough’?
Changed Bug title to 'xfs/linux.h defines common word "fallthrough" breaking' from 'copy_move_algo.hpp:1083:10: error: ‘__fallthrough__’ was not declared in this scope; did you mean ‘fallthrough’?'.
> unrelated headers
Unknown command or malformed arguments to command.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1000974: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000974
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
next parent reply other threads:[~2021-12-05 15:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <9b9bda73-9554-0c75-824d-f8d1b9b98e19@debian.org>
[not found] ` <7686ac7e-0df1-a98c-27ce-51dc5e46c55e@debian.org>
[not found] ` <163839370805.58768.6385074074873965943.reportbug@zbuz.infomaniak.ch>
[not found] ` <c7ccff50-c177-7f96-2d99-2077f77374ad@debian.org>
2021-12-05 15:57 ` Debian Bug Tracking System [this message]
2021-12-05 17:33 ` Bug#1000974: copy_move_algo.hpp:1083:10: error: ‘__fallthrough__’ was not declared in this scope; did you mean ‘fallthrough’? Thomas Goirand
2021-12-05 17:45 ` Darrick J. Wong
2021-12-05 17:49 ` [PATCH xfsprogs-5.14.2 URGENT] libxfs: hide the drainbamaged fallthrough macro from xfslibs Darrick J. Wong
2021-12-05 17:49 ` Bug#1000974: " Darrick J. Wong
2021-12-05 21:10 ` Dave Chinner
2021-12-05 21:10 ` Dave Chinner
2021-12-06 14:26 ` Eric Sandeen
2021-12-06 14:26 ` Bug#1000974: " Eric Sandeen
2021-12-06 20:15 ` Kees Cook
2021-12-06 20:15 ` Bug#1000974: " Kees Cook
[not found] ` <handler.1000974.B1000974.163872562421581.ackinfo@bugs.debian.org>
2021-12-05 19:00 ` Bug#1000974: Info received (Bug#1000974: copy_move_algo.hpp:1083:10: error: ‘__fallthrough__’ was not declared in this scope; did you mean ‘fallthrough’?) Thomas Goirand
2021-12-07 12:36 ` Bug#1000974: marked as done (xfs/linux.h defines common word "fallthrough" breaking unrelated headers) Debian Bug Tracking System
2021-12-07 12:54 ` Debian Bug Tracking System
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.16387197672501.transcript@bugs.debian.org \
--to=owner@bugs.debian.org \
--cc=gio@debian.org \
--cc=linux-xfs@vger.kernel.org \
--cc=team+boost@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 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.