Your message dated Tue, 13 Aug 2024 14:00:34 +0200
with message-id <65286045-53d9-4d46-a214-46d147976...@thykier.net>
and subject line Re: metadata
has caused the Debian Bug report #1076924,
regarding sendip: FTBFS: sendip.c:282:46: error: ‘SENDIP_LIBS’ undeclared
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.)
--
1076924: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1076924
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:sendip
Version: 2.6-1
Severity: serious
Tags: ftbfs
Dear maintainer:
During a rebuild of all packages in unstable, your package failed to build:
--------------------------------------------------------------------------------
[...]
debian/rules binary
dh binary
dh_update_autotools_config
dh_autoreconf
dh_auto_configure
dh_auto_build
make -j2 "INSTALL=install --strip-program=true"
make[1]: Entering directory '/<<PKGBUILDDIR>>'
gcc -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<<PKGBUILDDIR>>=.
-fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection
-fPIC -fsigned-char -pipe -Wall -Wpointer-arith -Wwrite-strings -Wstrict-prototypes -Wnested-externs
-Winline -Werror -g -Wcast-align -DSENDIP_LIBS=\"/usr/lib/x86_64-linux-gnu/sendip\"
-Wdate-time -D_FORTIFY_SOURCE=2 -c -o csum.o csum.c
gcc -g -O2 -Werror=implicit-function-declaration
-ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time
-D_FORTIFY_SOURCE=2 -c -o compact.o compact.c
gcc -g -O2 -Werror=implicit-function-declaration
-ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time
-D_FORTIFY_SOURCE=2 -c -o sendip.o sendip.c
gcc -g -O2 -Werror=implicit-function-declaration
-ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time
-D_FORTIFY_SOURCE=2 -c -o gnugetopt.o gnugetopt.c
sendip.c: In function ‘load_module’:
sendip.c:282:46: error: ‘SENDIP_LIBS’ undeclared (first use in this function)
282 |
newmod->name=malloc(strlen(modname)+strlen(SENDIP_LIBS)+strlen(".so")+2);
| ^~~~~~~~~~~
sendip.c:282:46: note: each undeclared identifier is reported only once for
each function it appears in
make[1]: *** [<builtin>: sendip.o] Error 1
make[1]: *** Waiting for unfinished jobs....
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
dh_auto_build: error: make -j2 "INSTALL=install --strip-program=true" returned
exit code 2
make: *** [debian/rules:8: binary] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
--------------------------------------------------------------------------------
The above is just how the build ends and not necessarily the most relevant part.
If required, the full build log is available here:
https://people.debian.org/~sanvila/build-logs/202407/
About the archive rebuild: The build was made on virtual machines
of type m6a.large and r6a.large from AWS, using sbuild and a
reduced chroot with only build-essential packages.
If you could not reproduce the bug please contact me privately, as I
am willing to provide ssh access to a virtual machine where the bug is
fully reproducible.
If this is really a bug in one of the build-depends, please use
reassign and affects, so that this is still visible in the BTS web
page for this package.
Thanks.
--- End Message ---
--- Begin Message ---
On Thu, 8 Aug 2024 15:38:58 +0200 Santiago Vila <sanv...@debian.org> wrote:
# this one based on the build log
found 1076924 1.22.8
# and this one based on the fact that it does not happen anymore
fixed 1076924 1.22.11
thanks
Adding a `fixed` version does not also `close` the bug. Since the bug
appear to be fixed, I have now closed it as well (to get it of the list
of open RC bugs).
If there are still minor details to sort out, please consider either
filing a separate (non-RC) bugs for those or reopen and downgrade the
severity of this bug (note, reopen might clear the fixed version).
Best regards,
Niels
--- End Message ---
