Your message dated Tue, 18 Jun 2024 09:35:17 +0000 with message-id <E1sJVFF-003lzp-8J@fasolo.debian.org> and subject line Bug#1073317: fixed in pd-lyonpotpourri 3.0.1-5 has caused the Debian Bug report #1073317, regarding pd-lyonpotpourri: FTBFS: m_pd.h:85:26: error: static assertion failed: "field must be t_float!" 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 owner@bugs.debian.org immediately.) -- 1073317: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073317 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: pd-lyonpotpourri: FTBFS: m_pd.h:85:26: error: static assertion failed: "field must be t_float!"
- From: Lucas Nussbaum <lucas@debian.org>
- Date: Sun, 16 Jun 2024 14:54:53 +0200
- Message-id: <[🔎] Zm7gnVRM51daH23_@grub.nussbaum.fr>
Source: pd-lyonpotpourri Version: 3.0.1-4 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lucas@debian.org Usertags: ftbfs-20240615 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > cc -DPD -I "/usr/include/pd" -DPD_FLOATSIZE=64 -DUNIX -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -o distortion~.linux-amd64-64.so.o -c distortion~.c > ++++ info: making rtrig~.linux-amd64-64.so.o in lib lyonpotpourri > In file included from MSPd.h:31, > from distortion~.c:1: > distortion~.c: In function ‘distortion_tilde_setup’: > /usr/include/pd/m_pd.h:85:26: error: static assertion failed: "field must be t_float!" > 85 | #define PD_STATIC_ASSERT _Static_assert > | ^~~~~~~~~~~~~~ > /usr/include/pd/m_pd.h:575:5: note: in expansion of macro ‘PD_STATIC_ASSERT’ > 575 | PD_STATIC_ASSERT(sizeof(((type *)NULL)->field) == sizeof(t_float), "field must be t_float!"); \ > | ^~~~~~~~~~~~~~~~ > distortion~.c:35:3: note: in expansion of macro ‘CLASS_MAINSIGNALIN’ > 35 | CLASS_MAINSIGNALIN(distortion_class, t_distortion, x_f); > | ^~~~~~~~~~~~~~~~~~ > distortion~.c: In function ‘distortion1_perform’: > distortion~.c:72:15: warning: initialization of ‘float *’ from incompatible pointer type ‘t_float *’ {aka ‘double *’} [-Wincompatible-pointer-types] > 72 | float *in = (t_float *)(w[2]); > | ^ > distortion~.c:73:16: warning: initialization of ‘float *’ from incompatible pointer type ‘t_float *’ {aka ‘double *’} [-Wincompatible-pointer-types] > 73 | float *out = (t_float *)(w[5]); > | ^ > distortion~.c: In function ‘distortion2_perform’: > distortion~.c:113:15: warning: initialization of ‘float *’ from incompatible pointer type ‘t_float *’ {aka ‘double *’} [-Wincompatible-pointer-types] > 113 | float *in = (t_float *)(w[2]); > | ^ > distortion~.c:114:18: warning: initialization of ‘float *’ from incompatible pointer type ‘t_float *’ {aka ‘double *’} [-Wincompatible-pointer-types] > 114 | float *data1 = (t_float *)(w[3]); > | ^ > distortion~.c:115:18: warning: initialization of ‘float *’ from incompatible pointer type ‘t_float *’ {aka ‘double *’} [-Wincompatible-pointer-types] > 115 | float *data2 = (t_float *)(w[4]); > | ^ > distortion~.c:116:16: warning: initialization of ‘float *’ from incompatible pointer type ‘t_float *’ {aka ‘double *’} [-Wincompatible-pointer-types] > 116 | float *out = (t_float *)(w[5]); > | ^ > distortion~.c: In function ‘distortion3_perform’: > distortion~.c:165:15: warning: initialization of ‘float *’ from incompatible pointer type ‘t_float *’ {aka ‘double *’} [-Wincompatible-pointer-types] > 165 | float *in = (t_float *)(w[2]); > | ^ > distortion~.c:166:18: warning: initialization of ‘float *’ from incompatible pointer type ‘t_float *’ {aka ‘double *’} [-Wincompatible-pointer-types] > 166 | float *data1 = (t_float *)(w[3]); > | ^ > distortion~.c:167:18: warning: initialization of ‘float *’ from incompatible pointer type ‘t_float *’ {aka ‘double *’} [-Wincompatible-pointer-types] > 167 | float *data2 = (t_float *)(w[4]); > | ^ > distortion~.c:168:16: warning: initialization of ‘float *’ from incompatible pointer type ‘t_float *’ {aka ‘double *’} [-Wincompatible-pointer-types] > 168 | float *out = (t_float *)(w[5]); > | ^ > make[1]: *** [/usr/share/pd-lib-builder//Makefile.pdlibbuilder:987: distortion~.linux-amd64-64.so.o] Error 1 The full build log is available from: http://qa-logs.debian.net/2024/06/15/pd-lyonpotpourri_3.0.1-4_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240615;users=lucas@debian.org or: https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20240615&fusertaguser=lucas@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 ---
- To: 1073317-close@bugs.debian.org
- Subject: Bug#1073317: fixed in pd-lyonpotpourri 3.0.1-5
- From: Debian FTP Masters <ftpmaster@ftp-master.debian.org>
- Date: Tue, 18 Jun 2024 09:35:17 +0000
- Message-id: <E1sJVFF-003lzp-8J@fasolo.debian.org>
- Reply-to: IOhannes m zmölnig (Debian/GNU) <umlaeute@debian.org>
Source: pd-lyonpotpourri Source-Version: 3.0.1-5 Done: IOhannes m zmölnig (Debian/GNU) <umlaeute@debian.org> We believe that the bug you reported is fixed in the latest version of pd-lyonpotpourri, 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 1073317@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. IOhannes m zmölnig (Debian/GNU) <umlaeute@debian.org> (supplier of updated pd-lyonpotpourri 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 ftpmaster@ftp-master.debian.org) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Format: 1.8 Date: Tue, 18 Jun 2024 11:12:42 +0200 Source: pd-lyonpotpourri Architecture: source Version: 3.0.1-5 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers <debian-multimedia@lists.debian.org> Changed-By: IOhannes m zmölnig (Debian/GNU) <umlaeute@debian.org> Closes: 1073317 Changes: pd-lyonpotpourri (3.0.1-5) unstable; urgency=medium . * Add patch to build against Pd64 (Closes: #1073317) + Replace all 'float' occurences with 't_float' * Add patch to fix some more compiler warnings * B-D on pkgconf rather than pkg-config * Switch to dh-sequence-puredata * Add Provides-stanza * Bump standards version to 4.7.0 Checksums-Sha1: 9eebd2e59f6138e3e3600ba8d3057541161c6273 2223 pd-lyonpotpourri_3.0.1-5.dsc c451404ee6bb7539caaac6da6535327055b256e5 55468 pd-lyonpotpourri_3.0.1-5.debian.tar.xz Checksums-Sha256: 2b08753a0fe74b22bde9aff952e98a4c8afd861910a36a6c52153f71093e7c3e 2223 pd-lyonpotpourri_3.0.1-5.dsc a6cd318719fe0d2a438e13fb13af5474e5915d05bb0fc6f77ee9bd47131322d5 55468 pd-lyonpotpourri_3.0.1-5.debian.tar.xz Files: 0b507f6feb302910d012ac954f76f239 2223 sound optional pd-lyonpotpourri_3.0.1-5.dsc 28106b7e45e86e10aa39815f425a2503 55468 sound optional pd-lyonpotpourri_3.0.1-5.debian.tar.xz -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEdAXnRVdICXNIABVttlAZxH96NvgFAmZxUYMACgkQtlAZxH96 NviqdA/9HRMr5IeGFTvdfnZpNyJxMo5I/B5XLhdWckxA8e8+rHnhSGOKETfqT2og fiCvV12X9Ji4z648ym5c+/ZqTquOY5mflr9hjtw3mHJ/q9Oieasg4qx+Pfqg2fN1 RcOEYxyeTtnbsK97ceZ6H8xN1koaiZ7RcvB+O5sGWzp1hOyDUHTCMRC30luZkM+P OSkg/NfNXRhQEwv9vxUhuV+bcINBhaEg5eQD/zOnVWsd3BVB2S0DDAz/72RLeTfU fSDIA63aYXFDl7WcekDU6Xb04a+smaJQV+ApXjki4QPBW/YmY6VFTbGTrdGDTngs G3t8Yla0ruTbHhslw4Xd+ylWSJGbjhb50UkYK2JrPpUvhwKyn342nLQq37H1zIFV U/MFcw4pBq9WH+MpUfoNVObFYnOT919akvN3pT4f3k9hPJBY06ezBex1w15idxVE 4CgNnArw+Mu1q1E+HZ81b62wskjwSJe645atIIr++SeUBKTkDtt4u1i/jEt0Xmb/ N8KdgdKBmYofVHjHIf4Y+xOlcpcwlpBQxurKS9nlirxifFzJgpH2Hoytw5EPaHTE YNj4loCYUVgjbIFrN+Bk2vg40+6j5ok9imK+M1WzQfAU8sKiVQFJy2edkl6dRDX9 EmWOUXixCIInCj5YGzQTzqqLFzfqxWIFy6UDYubZvMWU5MXtrDY= =v5hh -----END PGP SIGNATURE-----Attachment: pgpMuf7dM0GV7.pgp
Description: PGP signature
--- End Message ---