Your message dated Wed, 2 Sep 2020 08:43:40 +0200
with message-id <82cc63fa-decc-1f00-e783-3b77a0e44...@gmail.com>
and subject line Re: findent: FTBFS: parser.cpp:104:10: fatal error:
parser.hpp: No such file or directory
has caused the Debian Bug report #966897,
regarding findent: FTBFS: parser.cpp:104:10: fatal error: parser.hpp: No such
file or directory
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
966897: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966897
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: findent
Version: 3.1.1-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200802 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> g++ -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -g -O2
> -fdebug-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat
> -Werror=format-security -c -o myparser.o myparser.cpp
> In file included from myparser.cpp:1:
> parser.cpp:104:10: fatal error: parser.hpp: No such file or directory
> 104 | #include "parser.hpp"
> | ^~~~~~~~~~~~
> compilation terminated.
> make[4]: *** [Makefile:488: myparser.o] Error 1
The full build log is available from:
http://qa-logs.debian.net/2020/08/02/findent_3.1.1-1_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Fixed in version 3.1.7-1 (available in sid)
On Mon, 3 Aug 2020 10:01:39 +0200 Lucas Nussbaum <lu...@debian.org> wrote:
Source: findent
Version: 3.1.1-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200802 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> g++ -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -g -O2
-fdebug-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat
-Werror=format-security -c -o myparser.o myparser.cpp
> In file included from myparser.cpp:1:
> parser.cpp:104:10: fatal error: parser.hpp: No such file or directory
> 104 | #include "parser.hpp"
> | ^~~~~~~~~~~~
> compilation terminated.
> make[4]: *** [Makefile:488: myparser.o] Error 1
The full build log is available from:
http://qa-logs.debian.net/2020/08/02/findent_3.1.1-1_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
