Your message dated Wed, 11 Oct 2017 08:50:07 +0000
with message-id <[email protected]>
and subject line Bug#869588: fixed in libcap2 1:2.25-1.1
has caused the Debian Bug report #869588,
regarding libcap2 FTBFS: error: conflicting types for '__cap_lookup_name'
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 [email protected]
immediately.)


-- 
869588: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869588
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: libcap2
Version: 1:2.25-1
Severity: serious
User: [email protected]
Usertags: rebootstrap

libcap2 fails to build from source in sid.

| cc -g -O2 -fdebug-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong 
-Wformat -Werror=format-security -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 
-Dlinux -Wall -Wwrite-strings -Wpointer-arith -Wcast-qual -Wcast-align 
-Wstrict-prototypes -Wmissing-prototypes -Wnested-externs -Winline -Wshadow -g 
-D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -Dlinux -Wall -Wwrite-strings 
-Wpointer-arith -Wcast-qual -Wcast-align -Wstrict-prototypes 
-Wmissing-prototypes -Wnested-externs -Winline -Wshadow -g -Wdate-time 
-D_FORTIFY_SOURCE=2 -fPIC -I/<<PKGBUILDDIR>>/libcap/../libcap/include/uapi 
-I/<<PKGBUILDDIR>>/libcap/../libcap/include -include _caps_output.gperf -c 
cap_text.c -o cap_text.o
| In file included from <command-line>:0:0:
| ./_caps_output.gperf:86:15: error: unknown type name 'size_t'
|       register size_t n)
|                ^~~~~~
| ./_caps_output.gperf:109:52: error: unknown type name 'size_t'
|  __cap_hash_name(register const char *str, register size_t len)
|                                                     ^~~~~~
| ./_caps_output.gperf:208:21: error: unknown type name 'size_t'
|             register size_t len)
|                      ^~~~~~
| ./_caps_output.gperf:207:29: error: conflicting types for '__cap_lookup_name'
|  const struct __cap_token_s *__cap_lookup_name(register const char *str,
|                              ^~~~~~~~~~~~~~~~~
| ./_caps_output.gperf:33:36: note: previous declaration of '__cap_lookup_name' 
was here
|  static const struct __cap_token_s *__cap_lookup_name(const char *,
|                                     ^~~~~~~~~~~~~~~~~
| cap_text.c: In function 'cap_to_name':
| cap_text.c:291:2: warning: ignoring return value of 'asprintf', declared with 
attribute warn_unused_result [-Wunused-result]
|   asprintf(&tmp, "%u", cap);
|   ^~~~~~~~~~~~~~~~~~~~~~~~~
| Makefile:66: recipe for target 'cap_text.o' failed
| make[3]: *** [cap_text.o] Error 1
| make[3]: Leaving directory '/<<PKGBUILDDIR>>/libcap'
| Makefile:12: recipe for target 'all' failed
| make[2]: *** [all] Error 2
| make[2]: Leaving directory '/<<PKGBUILDDIR>>'
| dh_auto_build: make -j1 CC=cc BUILD_CC=cc returned exit code 2
| 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:25: recipe for target 'build-arch' failed
| make: *** [build-arch] Error 2
| dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2

Looks like the gperf upload is the immediate cause.

Helmut

--- End Message ---
--- Begin Message ---
Source: libcap2
Source-Version: 1:2.25-1.1

We believe that the bug you reported is fixed in the latest version of
libcap2, 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 [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Matthias Klose <[email protected]> (supplier of updated libcap2 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 [email protected])


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

Format: 1.8
Date: Wed, 11 Oct 2017 10:26:50 +0200
Source: libcap2
Binary: libcap2-bin libcap2 libcap-dev libpam-cap libcap2-udeb
Architecture: source
Version: 1:2.25-1.1
Distribution: unstable
Urgency: medium
Maintainer: Christian Kastner <[email protected]>
Changed-By: Matthias Klose <[email protected]>
Description:
 libcap-dev - POSIX 1003.1e capabilities (development)
 libcap2    - POSIX 1003.1e capabilities (library)
 libcap2-bin - POSIX 1003.1e capabilities (utilities)
 libcap2-udeb - POSIX 1003.1e capabilities (library) (udeb)
 libpam-cap - POSIX 1003.1e capabilities (PAM module)
Closes: 869588
Changes:
 libcap2 (1:2.25-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix FTBFS with gperf 3.1 (Helmut Grohne). Closes: #869588.
Checksums-Sha1:
 a4c37b57e313c37b92b5ea28fe7f57c236b7b4a4 2191 libcap2_2.25-1.1.dsc
 af89b9c18d283e15ade11dae5f49735e35b43e62 20804 libcap2_2.25-1.1.debian.tar.xz
 58dfc55483fd4298a68bc98588a1d0e09d8cba65 4820 libcap2_2.25-1.1_source.buildinfo
Checksums-Sha256:
 298ee63187b0406bad5d08d2edf19c9155a3061eb99884bc3ebc94b20d37e229 2191 
libcap2_2.25-1.1.dsc
 65e3b8e70aa782a58d611911b01d555dabf871fde35d48cbaeaff734bcf1faf6 20804 
libcap2_2.25-1.1.debian.tar.xz
 bf0779ae7ac9e3679ac9297b5f07f6a4252a604c43c81996a2236c10e51253b7 4820 
libcap2_2.25-1.1_source.buildinfo
Files:
 e2907cab9927aa6d91ae9c6cf7ebf6d6 2191 libs optional libcap2_2.25-1.1.dsc
 0e30e5ae324572ae2fa51d2395003f9b 20804 libs optional 
libcap2_2.25-1.1.debian.tar.xz
 42f529f797e467eae51ce90042f67992 4820 libs optional 
libcap2_2.25-1.1_source.buildinfo

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBCAAGBQJZ3dYmAAoJEL1+qmB3j6b11QYP/3nUZDrfYKBAWjv/t6vFgxzs
Z6gGKXoSzMkXEIItkteth/Ry2O+uNzYyGU9wd88XmGQVU9dJtC6qCCZn72zBntIq
G8x2l+0vhRP0ndA2hTpbU30g9BPETxFLNFtTKXuC0LfcTq9GT9qHPZNTB8XSR+P1
Zdd8mObAkGvws/QkZkQbw3hQ+or3sdL11EkYk6alXtCyAeanNQ1Zh//z/8Ox5WsL
0VEC00aAyzwKpiO5b6S7lWJFlxw1Obk5N07tQ8XozkKYdlhCBrjGLeD756twVZ9U
9ZGwg6qon54N/ZQd2Yxd1xlUkmuQOakOjbhWoLSJ3xxXmft6hFlwyV9ozQwY4XWO
/lOShvE9J2NwjOOP0itREvi27YC/AJlK2tBVz0oMMq6RwSthpJ26U8HQ4IMRolga
hM2rcflYIjI6Y3Z7dCsj1J++Ps7yUusqWahd03fb8ocNXS+76BT5VKJC5AUldGUP
x1o2mXuqmEKMe4o/nrXEUr3xYcxaepRGK3KFKaO+6/7T11TJo9XKwXbqxyaOs/nn
UrThZIt7+Jb/PO4n7U88aMwP94Wq2U40feW0Ew4y/Fwk6iPZsqB32RjmXXXhpjWt
ArzUbBZvNrE/1zua3N9lSb5Ij7rZc2Bcta51lfqwF81ICGFgSk7gtfWcbGQ1YoBX
kYXFOvVhYz252cCqYtDP
=279o
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to