Your message dated Thu, 12 Sep 2024 15:08:11 +0000
with message-id <e1solqz-00cjyz...@fasolo.debian.org>
and subject line Bug#1078408: fixed in autofs 5.1.9-1.2
has caused the Debian Bug report #1078408,
regarding autofs: FTBFS: cyrus-sasl.c:112:25: error: initialization of ‘int 
(*)(void)’ from incompatible pointer type ‘int (*)(void *, int,  const char **, 
unsigned int *)’ [-Wincompatible-pointer-types]
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.)


-- 
1078408: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1078408
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: autofs
Version: 5.1.9-1.1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240809 ftbfs-trixie

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
> 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 -D_REENTRANT -D_FILE_OFFSET_BITS=64 
> -I/usr/include/tirpc  -D_REENTRANT -D_FILE_OFFSET_BITS=64 
> -I/usr/include/tirpc  
> -DSSS_LIB_DIR=\"/usr/lib/x86_64-linux-gnu/sssd/modules\" -I../include 
> -I../lib -fPIC -D_GNU_SOURCE 
> -DAUTOFS_LIB_DIR=\"/usr/lib/x86_64-linux-gnu/autofs\" 
> -DAUTOFS_MAP_DIR=\"/etc\" -c amd_tok.c
> cyrus-sasl.c:112:25: error: initialization of ‘int (*)(void)’ from 
> incompatible pointer type ‘int (*)(void *, int,  const char **, unsigned int 
> *)’ [-Wincompatible-pointer-types]
>   112 |         { SASL_CB_USER, &getuser_func, NULL },
>       |                         ^
> cyrus-sasl.c:112:25: note: (near initialization for ‘callbacks[0].proc’)
> cyrus-sasl.c:113:29: error: initialization of ‘int (*)(void)’ from 
> incompatible pointer type ‘int (*)(void *, int,  const char **, unsigned int 
> *)’ [-Wincompatible-pointer-types]
>   113 |         { SASL_CB_AUTHNAME, &getuser_func, NULL },
>       |                             ^
> cyrus-sasl.c:113:29: note: (near initialization for ‘callbacks[1].proc’)
> cyrus-sasl.c:114:25: error: initialization of ‘int (*)(void)’ from 
> incompatible pointer type ‘int (*)(sasl_conn_t *, void *, int,  sasl_secret_t 
> **)’ {aka ‘int (*)(struct sasl_conn *, void *, int,  struct sasl_secret **)’} 
> [-Wincompatible-pointer-types]
>   114 |         { SASL_CB_PASS, &getpass_func, NULL },
>       |                         ^
> cyrus-sasl.c:114:25: note: (near initialization for ‘callbacks[2].proc’)
> cyrus-sasl.c:119:24: error: initialization of ‘int (*)(void)’ from 
> incompatible pointer type ‘int (*)(void *, int,  const char *)’ 
> [-Wincompatible-pointer-types]
>   119 |         { SASL_CB_LOG, &sasl_log_func, NULL },
>       |                        ^
> cyrus-sasl.c:119:24: note: (near initialization for ‘debug_callbacks[0].proc’)
> cyrus-sasl.c:120:25: error: initialization of ‘int (*)(void)’ from 
> incompatible pointer type ‘int (*)(void *, int,  const char **, unsigned int 
> *)’ [-Wincompatible-pointer-types]
>   120 |         { SASL_CB_USER, &getuser_func, NULL },
>       |                         ^
> cyrus-sasl.c:120:25: note: (near initialization for ‘debug_callbacks[1].proc’)
> cyrus-sasl.c:121:29: error: initialization of ‘int (*)(void)’ from 
> incompatible pointer type ‘int (*)(void *, int,  const char **, unsigned int 
> *)’ [-Wincompatible-pointer-types]
>   121 |         { SASL_CB_AUTHNAME, &getuser_func, NULL },
>       |                             ^
> cyrus-sasl.c:121:29: note: (near initialization for ‘debug_callbacks[2].proc’)
> cyrus-sasl.c:122:25: error: initialization of ‘int (*)(void)’ from 
> incompatible pointer type ‘int (*)(sasl_conn_t *, void *, int,  sasl_secret_t 
> **)’ {aka ‘int (*)(struct sasl_conn *, void *, int,  struct sasl_secret **)’} 
> [-Wincompatible-pointer-types]
>   122 |         { SASL_CB_PASS, &getpass_func, NULL },
>       |                         ^
> cyrus-sasl.c:122:25: note: (near initialization for ‘debug_callbacks[3].proc’)
> make[3]: *** [Makefile:137: cyrus-sasl.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2024/08/09/autofs_5.1.9-1.1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240809;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20240809&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results

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!

If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.

--- End Message ---
--- Begin Message ---
Source: autofs
Source-Version: 5.1.9-1.2
Done: Salvatore Bonaccorso <car...@debian.org>

We believe that the bug you reported is fixed in the latest version of
autofs, 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 1078...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Salvatore Bonaccorso <car...@debian.org> (supplier of updated autofs 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: SHA512

Format: 1.8
Date: Wed, 11 Sep 2024 20:56:38 +0200
Source: autofs
Architecture: source
Version: 5.1.9-1.2
Distribution: unstable
Urgency: medium
Maintainer: Mike Gabriel <sunwea...@debian.org>
Changed-By: Salvatore Bonaccorso <car...@debian.org>
Closes: 1078408
Changes:
 autofs (5.1.9-1.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix incompatible function pointer types in cyrus-sasl module (Closes:
     #1078408)
Checksums-Sha1:
 c6a93975e3b618dbedb63410ff4ce70463894862 2479 autofs_5.1.9-1.2.dsc
 bcded547c0f8ea837c756005271cf69390b76d2b 23916 autofs_5.1.9-1.2.debian.tar.xz
 a72170017ff763068c5f80c23e5f23b726e23c6b 7329 autofs_5.1.9-1.2_source.buildinfo
Checksums-Sha256:
 ab4881c92c640482cfe3ec73c6a8e827757f151d6b059ae21de816598576d5f7 2479 
autofs_5.1.9-1.2.dsc
 f98ca8a8f695c66532e9870c7b9192adaa6497415f6b1ee3d7ebcf82674c6c9f 23916 
autofs_5.1.9-1.2.debian.tar.xz
 04f103a7a8a142bf4aa269e85449a99f00b42b87675f5cdef62ada6882c3a088 7329 
autofs_5.1.9-1.2_source.buildinfo
Files:
 30e93f4a2a109575f047df844bccc2b6 2479 utils optional autofs_5.1.9-1.2.dsc
 8b66012f16d53997dbbe033f308709b0 23916 utils optional 
autofs_5.1.9-1.2.debian.tar.xz
 fb5865aa0f26b5f8b0338c15d7b86013 7329 utils optional 
autofs_5.1.9-1.2_source.buildinfo
-----BEGIN PGP SIGNATURE-----

iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAmbh6sJfFIAAAAAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2
NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk
ZWJpYW4ub3JnAAoJEAVMuPMTQ89EjG0P/2PvdLyWns+Tuid/eeQUlPLB7FEfK+Ti
25hH1MzBqoyUep+56hjQvi8GcxAtot2e03T6AggJATLWEsYOtE/3MpuQK1FQNrJR
Yig8uwE3EU4kn3v/a6k1uGB/g9YGPmSlz4y/UCJ0CZJPiavakd+zUkmCTF2M83UB
rQVCeIaxQ/FNT4IZa5T5gToTKRYZPRTUmSfHU9WrhMZz+rbulWEKL3vFA9LF+Rzp
DOJ9uppMAN2lWUWhdrF0XqMZilvMRa2UbemPPYAwUYX5HpziP9dAAFaYSQaVe6C6
2ENp/XzpX4nn+7iYrNIuvZ9teGz+Dd2e0h+tR6eXQV3f1JmEcuiwZDCPhhb1g6rg
iHK3uhnMRk/YqXv1pFOUJ8ojN/8680qaU59EKa+yaKOof9kD/nK+c1d9/Vg9/s+h
bAlKf+dRbR5j5MhJm3v2HMWdZTCmbWAtdlzU4QrcviwSFL5P/KbbAwRx3cxNtfGX
3FNOgYQW7eAXF3JD742DQG8CZEj88vv09m1k/p34JorB9Fa2Hx2exNhx8cSppcwq
jj9w+J418vmHDHce4OBPjNevdsBFpUW9+RXBHg9hIM9XIif5E91xYVqE4nJz7WOO
AxmcdQ0FxoS4T0zEFa/PahCUupigfM+pXoeO4loBeNXU7y7W5BfG3A5rxdaGzeHV
pACWHqcOWJxu
=bTfh
-----END PGP SIGNATURE-----

Attachment: pgpnb9il9KqgO.pgp
Description: PGP signature


--- End Message ---

Reply via email to