Your message dated Thu, 22 Mar 2018 15:16:47 +0000
with message-id <e1ez1xp-000984...@fasolo.debian.org>
and subject line Bug#891293: fixed in trinity 1.8-3
has caused the Debian Bug report #891293,
regarding trinity: FTBFS with glibc 2.27: error: static declaration of 
'memfd_create' follows non-static declaration
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.)


-- 
891293: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891293
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: trinity
Version: 1.8-2
Severity: important
User: debian-gl...@lists.debian.org
Usertags: 2.27

trinity 1.8-2 fails to build with glibc 2.27 (2.27-0experimental0 from
experimental):

| cc -g -O2 -fdebug-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wall -Wextra -I. -Iinclude/ -include config.h 
-Wimplicit -D_GNU_SOURCE -D__linux__ -std=gnu11 -Wdeclaration-after-statement 
-Wformat=2 -Winit-self -Wnested-externs -Wpacked -Wshadow -Wswitch-enum -Wundef 
-Wwrite-strings -Wno-format-nonliteral -Wstrict-prototypes -Wmissing-prototypes 
-fsigned-char -Wlogical-op -Wstrict-aliasing=3 -Wno-maybe-uninitialized -o 
fds/inotify.o -c fds/inotify.c
| cc -g -O2 -fdebug-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wall -Wextra -I. -Iinclude/ -include config.h 
-Wimplicit -D_GNU_SOURCE -D__linux__ -std=gnu11 -Wdeclaration-after-statement 
-Wformat=2 -Winit-self -Wnested-externs -Wpacked -Wshadow -Wswitch-enum -Wundef 
-Wwrite-strings -Wno-format-nonliteral -Wstrict-prototypes -Wmissing-prototypes 
-fsigned-char -Wlogical-op -Wstrict-aliasing=3 -Wno-maybe-uninitialized -o 
fds/memfd.o -c fds/memfd.c
| fds/memfd.c:19:12: error: static declaration of 'memfd_create' follows 
non-static declaration
|  static int memfd_create(__unused__ const char *uname, __unused__ unsigned 
int flag)
|             ^~~~~~~~~~~~
| In file included from /usr/include/x86_64-linux-gnu/bits/mman-linux.h:115:0,
|                  from /usr/include/x86_64-linux-gnu/bits/mman.h:45,
|                  from /usr/include/x86_64-linux-gnu/sys/mman.h:41,
|                  from include/utils.h:4,
|                  from include/syscall.h:7,
|                  from include/child.h:7,
|                  from include/fd.h:3,
|                  from fds/memfd.c:9:
| /usr/include/x86_64-linux-gnu/bits/mman-shared.h:46:5: note: previous 
declaration of 'memfd_create' was here
|  int memfd_create (const char *__name, unsigned int __flags) __THROW;
|      ^~~~~~~~~~~~
| Makefile:130: recipe for target 'fds/memfd.o' failed
| make[2]: *** [fds/memfd.o] Error 1
| make[2]: Leaving directory '/<<PKGBUILDDIR>>'
| debian/rules:29: recipe for target 'override_dh_auto_build' failed
| make[1]: *** [override_dh_auto_build] Error 2
| make[1]: Leaving directory '/<<PKGBUILDDIR>>'
| debian/rules:32: recipe for target 'build-arch' failed
| make: *** [build-arch] Error 2
| dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status

A full build log is available there:
http://aws-logs.debian.net/2018/02/07/glibc-exp/trinity_1.8-2_unstable_glibc-exp.log

glibc 2.27 added support for memfd_create. Unfortunately trinity
also have such a function to wrap the corresponding syscall, and they
end up conflicting.

--- End Message ---
--- Begin Message ---
Source: trinity
Source-Version: 1.8-3

We believe that the bug you reported is fixed in the latest version of
trinity, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 891...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
gustavo panizzo <g...@zumbi.com.ar> (supplier of updated trinity package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Wed, 21 Mar 2018 15:13:33 +0000
Source: trinity
Binary: trinity
Architecture: source
Version: 1.8-3
Distribution: unstable
Urgency: medium
Maintainer: gustavo panizzo <g...@zumbi.com.ar>
Changed-By: gustavo panizzo <g...@zumbi.com.ar>
Description:
 trinity    - system call fuzz tester
Closes: 891293
Changes:
 trinity (1.8-3) unstable; urgency=medium
 .
   * Backport an upstream patch to build against glibc 2.27 (Closes: #891293)
   * Bumped standards version to 4.1.3, no changes were needed
   * Add minimal autopkg tests
Checksums-Sha1:
 5a256d9822d6efcd07cb79268ef52b0134882697 1892 trinity_1.8-3.dsc
 d5e06bb835d9d8276871628803ab357248c9402a 280620 trinity_1.8-3.debian.tar.xz
 e6afcdfc0c951aaf58e0c17646cd3c9a2cbff6ac 5578 trinity_1.8-3_amd64.buildinfo
Checksums-Sha256:
 fd8d5e8289138fe127104aadbec8f2f53a13bfbea168fcf2f648c7cb6ebd9f6a 1892 
trinity_1.8-3.dsc
 7a9a6664657a092eb29106042902931cfaf4774d57dd157aab1361bf93fe17ac 280620 
trinity_1.8-3.debian.tar.xz
 cccff2ca8a79ba2afac6ad795a8d926f2591f72fce81d820fd19ab6a1cdb119f 5578 
trinity_1.8-3_amd64.buildinfo
Files:
 0b7731be19bb26aa02abc45f87ef78a8 1892 utils optional trinity_1.8-3.dsc
 3d775e34360c0b6a1126a679301b4eb0 280620 utils optional 
trinity_1.8-3.debian.tar.xz
 e7574e230532f69c7decd4a19b42f0e1 5578 utils optional 
trinity_1.8-3_amd64.buildinfo

-----BEGIN PGP SIGNATURE-----

iQJFBAEBCAAvFiEEDixTvDtPMx04S0bghpRR/E7siM4FAlqzunARHGdmYUB6dW1i
aS5jb20uYXIACgkQhpRR/E7siM5Emw//c5B3Qic0KtynEwFPbKYHSoRlR5fKQi0U
70gG//5v+zJQl2l7MNEm+CthNgK/lcTLclwRApRWMXUyYOyytydqwH++0K0O9+mE
qkEdaPyrDUnO0AFdYr4YgQXZybeVYHPsIpJCbCXJtEmUQ+GseJN2Z7fd75HdLhfX
DzzDTUchGlrLeUmg8zc4fUDC2ksUQjFBRu46/4dSqQ0BcmzsvzT9adSzXL4NLi2J
yhv92NSG4KdhirV1jrwymwRQrCX+Xb5Ryf14QtEeedtsbj/sM/8Psj+37zINuQwl
+km8JdE9hcgxc+s3IJ9XkuUuX482iTC2ZdbLAkFylvlMMB0ghx590tA2iB7150KP
l/85RQtKaz2I167qN/AQGkToaLAb+vTpf72lMhhRFvz6bNc9E/4YOujIYJHhUNRL
gyQL7trwFH/+v2wPJ4NiQZHGYRckTOorMr4NV/rBqOPK4fanRB/4vK9FuqRruNVu
jvrZRmysomQH1nUI59oLbMaaJsFcHJh+ZaXQeXuKiaoCOLhNTHWNuqdKfzMMHCNz
itlm1qNjp74C5Yb90a/ULAR7ZpVL2ydyZeA6SvvUR6PZvLOU54uqk4Vx5ORzPMdA
i5fRytuQ1VJi95i5yiAQ/00bqErP20FA2aWW8QCDrWPTRIbSUU37F/iHvu81GDdB
2Iau27sCbLY=
=h1Ke
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to