Processed: severity of 1066501 is important
Processing commands for cont...@bugs.debian.org:
> severity 1066501 important
Bug #1066501 {Done: IOhannes m zmölnig (Debian/GNU) }
[src:pd-wiimote] pd-wiimote: FTBFS: wiimote.c:736:7: error: implicit
declaration of function ‘error’; did you mean ‘perror’?
[-Werror=implicit-function-declaration]
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1066501: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066501
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1037357: marked as done (flowblade: windows always open off-center)
Your message dated Sat, 06 Apr 2024 04:49:10 + with message-id and subject line Bug#1037357: fixed in flowblade 2.14.0.1-2 has caused the Debian Bug report #1037357, regarding flowblade: windows always open off-center 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.) -- 1037357: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037357 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: flowblade Version: 2.8.0.3-3 Severity: important The first time that Flowblade is run and asks for one's preferred editing mode, the window is maximized. The next time that Flowblade is run, the window is the same size, except that it's partially off-screen, so it has to be dragged back to the top edge of the desktop environment. The window should always open maximized and remain completely within the visible screen area. Martin-Éric -- System Information: Debian Release: 12.0 APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'stable-debug'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-9-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8), LANGUAGE=fi:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages flowblade depends on: ii frei0r-plugins1.8.0-1+b1 ii gir1.2-gdkpixbuf-2.0 2.42.10+dfsg-1+b1 ii gir1.2-glib-2.0 1.74.0-3 ii gir1.2-gtk-3.03.24.37-2 ii gir1.2-pango-1.0 1.50.12+ds-1 ii gmic 2.9.4-4+b4 ii libmlt-data 7.12.0-1 ii librsvg2-common 2.54.5+dfsg-1 ii python3 3.11.2-1+b1 ii python3-cairo 1.20.1-5+b1 ii python3-dbus 1.3.2-4+b1 ii python3-distutils 3.11.2-3 ii python3-gi3.42.2-3+b1 ii python3-gi-cairo 3.42.2-3+b1 ii python3-mlt 7.12.0-1+b1 ii python3-numpy 1:1.24.2-1 ii python3-opencv4.6.0+dfsg-12 ii python3-pil 9.4.0-1.1+b1 ii swh-plugins 0.4.17-2 flowblade recommends no packages. flowblade suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: flowblade Source-Version: 2.14.0.1-2 Done: Gürkan Myczko We believe that the bug you reported is fixed in the latest version of flowblade, 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 1037...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Gürkan Myczko (supplier of updated flowblade 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: Sat, 06 Apr 2024 06:20:07 +0200 Source: flowblade Architecture: source Version: 2.14.0.1-2 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers Changed-By: Gürkan Myczko Closes: 1037357 1068293 Changes: flowblade (2.14.0.1-2) unstable; urgency=medium . * d/control: add missing build-depends. (Closes: #1068293) * Bump standards version to 4.6.2. * This version also fixes bug off-center windows. (Closes: #1037357) Checksums-Sha1: 35b32ad08bece159d2046172c44aecff0ea454d3 2162 flowblade_2.14.0.1-2.dsc 47b3e1397b170d8d5a46c17b51404c9d17d99e54 25220 flowblade_2.14.0.1-2.debian.tar.xz 9db23bde57023f6d74d9c0347fd3df4936fd6121 9508 flowblade_2.14.0.1-2_source.buildinfo Checksums-Sha256: df77431536a49aa6cd73097f90c7592ceaca84f53da6a746b419c475d940533e 2162 flowblade_2.14.0.1-2.dsc bcb5420d5e1ae0244a3068f597732783bc091a40c368d55cb935ae417ac707c2 25220 flowblade_2.14.0.1-2.debian.tar.xz e42b3b66d86b2888d8c3e2650becae31c3697d442b164eac35a4ad8a18987f8d 9508 flowblade_2.14.0.1-2_source.buildinfo Files: 35ec858e4878ae52448a84ae1933c92c 2162 video optional flowblade_2.14.0.1-2.dsc d3c2e38273d87858dd4ba52c5983283a 25220 video optional flowblade_2.14.0.1-2.debian.tar.xz 1e71853d31c4eb3d7343821961ec775a 9508 video optional flowblade_2.14.0.1-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEtgob82PcExn/Co6JEWhSvN91FcAFAmYQz5MACgkQEWhSvN91 FcBjxxAAg43D1n00FqSLY1ROQ5adXeXQuuwITVmzn4ZMYcMQG2TD/FTBIJB6aJt/ q7X5s4i93gae0OU8N8C78c5E51eQXdSut1kF8Xl8yoq2czli8oF4y18zgtdC0GnU
Bug#1068293: marked as done (flowblade: 2.14 missing Depends on python3-libusb1)
Your message dated Sat, 06 Apr 2024 04:49:10 + with message-id and subject line Bug#1068293: fixed in flowblade 2.14.0.1-2 has caused the Debian Bug report #1068293, regarding flowblade: 2.14 missing Depends on python3-libusb1 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.) -- 1068293: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068293 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: flowblade Version: 2.14.0.1-1 Severity: important $ flowblade FLOWBLADE MOVIE EDITOR 2.14.0.1 --- Launch script dir: /usr/bin Running from installation... modules path: /usr/share/flowblade/Flowblade MLT found, version: 7.12.0 Failed to import module app.py to launch Flowblade! ERROR: No module named 'usb1' Installation was assumed to be at: /usr/share/flowblade/Flowblade -- System Information: Debian Release: 12.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable-debug'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-18-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8), LANGUAGE=fi:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages flowblade depends on: ii ffmpeg7:5.1.4-0+deb12u1 ii frei0r-plugins1.8.0-1+b1 ii gir1.2-gdkpixbuf-2.0 2.42.10+dfsg-1+b1 ii gir1.2-glib-2.0 1.74.0-3 ii gir1.2-gtk-3.03.24.38-2~deb12u1 ii gir1.2-pango-1.0 1.50.12+ds-1 ii gmic 2.9.4-4+b4 ii libmlt-data 7.12.0-1 ii librsvg2-common 2.54.7+dfsg-1~deb12u1 ii python3 3.11.2-1+b1 ii python3-cairo 1.20.1-5+b1 ii python3-dbus 1.3.2-4+b1 ii python3-distutils 3.11.2-3 ii python3-gi3.42.2-3+b1 ii python3-gi-cairo 3.42.2-3+b1 ii python3-mlt 7.12.0-1+b1 ii python3-numpy 1:1.24.2-1 ii python3-opencv4.6.0+dfsg-12 ii python3-pil 9.4.0-1.1+b1 ii swh-plugins 0.4.17-2 flowblade recommends no packages. flowblade suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: flowblade Source-Version: 2.14.0.1-2 Done: Gürkan Myczko We believe that the bug you reported is fixed in the latest version of flowblade, 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 1068...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Gürkan Myczko (supplier of updated flowblade 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: Sat, 06 Apr 2024 06:20:07 +0200 Source: flowblade Architecture: source Version: 2.14.0.1-2 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers Changed-By: Gürkan Myczko Closes: 1037357 1068293 Changes: flowblade (2.14.0.1-2) unstable; urgency=medium . * d/control: add missing build-depends. (Closes: #1068293) * Bump standards version to 4.6.2. * This version also fixes bug off-center windows. (Closes: #1037357) Checksums-Sha1: 35b32ad08bece159d2046172c44aecff0ea454d3 2162 flowblade_2.14.0.1-2.dsc 47b3e1397b170d8d5a46c17b51404c9d17d99e54 25220 flowblade_2.14.0.1-2.debian.tar.xz 9db23bde57023f6d74d9c0347fd3df4936fd6121 9508 flowblade_2.14.0.1-2_source.buildinfo Checksums-Sha256: df77431536a49aa6cd73097f90c7592ceaca84f53da6a746b419c475d940533e 2162 flowblade_2.14.0.1-2.dsc bcb5420d5e1ae0244a3068f597732783bc091a40c368d55cb935ae417ac707c2 25220 flowblade_2.14.0.1-2.debian.tar.xz e42b3b66d86b2888d8c3e2650becae31c3697d442b164eac35a4ad8a18987f8d 9508 flowblade_2.14.0.1-2_source.buildinfo Files: 35ec858e4878ae52448a84ae1933c92c 2162 video optional flowblade_2.14.0.1-2.dsc d3c2e38273d87858dd4ba52c5983283a 25220 video optional flowblade_2.14.0.1-2.debian.tar.xz 1e71853d31c4eb3d7343821961ec775a 9508 video optional flowblade_2.14.0.1-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEtgob82PcExn/Co6JEWhSvN91FcAFAmYQz5MACgkQEWhSvN91 FcBjxxAAg43D1n00FqSLY1ROQ5adXeXQuuwITVmzn4ZMYcMQG2TD/FTBIJB6aJt
Processed: Re: Bug#1068155: lmms: FTBFS on i386: dh_install: warning: Cannot find (any matches for) "usr/lib/*/lmms/libvestige.so" (tried in ., debian/tmp)
Processing control commands: > reassign -1 libwine-dev 9.0~repack-4 Bug #1068155 [src:lmms] lmms: FTBFS on i386: dh_install: warning: Cannot find (any matches for) "usr/lib/*/lmms/libvestige.so" (tried in ., debian/tmp) Bug reassigned from package 'src:lmms' to 'libwine-dev'. No longer marked as found in versions lmms/1.2.2+dfsg1-6. Ignoring request to alter fixed versions of bug #1068155 to the same values previously set Bug #1068155 [libwine-dev] lmms: FTBFS on i386: dh_install: warning: Cannot find (any matches for) "usr/lib/*/lmms/libvestige.so" (tried in ., debian/tmp) Marked as found in versions wine/9.0~repack-4. > affects -1 + src:lmms Bug #1068155 [libwine-dev] lmms: FTBFS on i386: dh_install: warning: Cannot find (any matches for) "usr/lib/*/lmms/libvestige.so" (tried in ., debian/tmp) Added indication that 1068155 affects src:lmms -- 1068155: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068155 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1063140: marked as done (mpg123: NMU diff for 64-bit time_t transition)
Your message dated Fri, 05 Apr 2024 18:00:21 +
with message-id
and subject line Bug#1063140: fixed in mpg123 1.32.6-1
has caused the Debian Bug report #1063140,
regarding mpg123: NMU diff for 64-bit time_t transition
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.)
--
1063140: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063140
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mpg123
Version: 1.32.4-1
Severity: serious
Tags: patch pending sid trixie
Justification: library ABI skew on upgrade
User: debian-...@lists.debian.org
Usertags: time-t
NOTICE: these changes must not be uploaded to unstable yet!
Dear maintainer,
As part of the 64-bit time_t transition required to support 32-bit
architectures in 2038 and beyond
(https://wiki.debian.org/ReleaseGoals/64bit-time), we have identified
mpg123 as a source package shipping runtime libraries whose ABI
either is affected by the change in size of time_t, or could not be
analyzed via abi-compliance-checker (and therefore to be on the safe
side we assume is affected).
To ensure that inconsistent combinations of libraries with their
reverse-dependencies are never installed together, it is necessary to
have a library transition, which is most easily done by renaming the
runtime library package.
Since turning on 64-bit time_t is being handled centrally through a change
to the default dpkg-buildflags (https://bugs.debian.org/1037136), it is
important that libraries affected by this ABI change all be uploaded close
together in time. Therefore I have prepared a 0-day NMU for mpg123
which will initially be uploaded to experimental if possible, then to
unstable after packages have cleared binary NEW.
Please find the patch for this NMU attached.
If you have any concerns about this patch, please reach out ASAP. Although
this package will be uploaded to experimental immediately, there will be a
period of several days before we begin uploads to unstable; so if information
becomes available that your package should not be included in the transition,
there is time for us to amend the planned uploads.
-- System Information:
Debian Release: trixie/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 6.5.0-14-generic (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru mpg123-1.32.4/debian/changelog mpg123-1.32.4/debian/changelog
--- mpg123-1.32.4/debian/changelog 2024-01-21 16:52:21.0 +
+++ mpg123-1.32.4/debian/changelog 2024-02-05 08:33:38.0 +
@@ -1,3 +1,10 @@
+mpg123 (1.32.4-1.1) experimental; urgency=medium
+
+ * Non-maintainer upload.
+ * Rename libraries for 64-bit time_t transition.
+
+ -- Steve Langasek Mon, 05 Feb 2024 08:33:38 +
+
mpg123 (1.32.4-1) unstable; urgency=medium
* New upstream version 1.32.4
diff -Nru mpg123-1.32.4/debian/control mpg123-1.32.4/debian/control
--- mpg123-1.32.4/debian/control2023-10-01 13:44:05.0 +
+++ mpg123-1.32.4/debian/control2024-02-05 08:33:37.0 +
@@ -42,7 +42,10 @@
OSS4, the Advanced Linux Sound Architecture (ALSA), JACK, PortAudio,
PulseAudio, OpenAL and the Network Audio System (NAS).
-Package: libmpg123-0
+Package: libmpg123-0t64
+Provides: ${t64:Provides}
+Replaces: libmpg123-0
+Breaks: libmpg123-0 (<< ${source:Version})
Multi-Arch: same
Architecture: any
Section: libs
@@ -56,7 +59,10 @@
This package contains the C libraries needed to run executables that use
the mpg123 library.
-Package: libout123-0
+Package: libout123-0t64
+Provides: ${t64:Provides}
+Replaces: libout123-0
+Breaks: libout123-0 (<< ${source:Version})
Multi-Arch: same
Architecture: any
Section: libs
@@ -69,7 +75,10 @@
.
This package contains the shared out123 library.
-Package: libsyn123-0
+Package: libsyn123-0t64
+Provides: ${t64:Provides}
+Replaces: libsyn123-0
+Breaks: libsyn123-0 (<< ${source:Version})
Multi-Arch: same
Architecture: any
Section: libs
@@ -87,9 +96,9 @@
Architecture: any
Section: libdevel
Depends:
- libmpg123-0 (= ${binary:Version}),
- libout123-0 (= ${binary:Version}),
- libsyn123-0 (= ${binary:Version}),
+ libmpg123-0t64 (= ${binary:Version}),
+ libout123-0t64 (= ${binary:Version}),
+ libsyn123-0t64 (= ${binary:Version}),
${misc:Depends}
Description: MPEG layer 1/2/3 audio decoder (development files)
mpg123 is a real tim
Bug#1067562: marked as done (FTBFS: missing symbols on 32-bit architectures)
Your message dated Fri, 05 Apr 2024 18:00:21 + with message-id and subject line Bug#1067562: fixed in mpg123 1.32.6-1 has caused the Debian Bug report #1067562, regarding FTBFS: missing symbols on 32-bit architectures 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.) -- 1067562: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067562 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mpg123 Version: 1.32.5-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=mpg123=armel=1.32.5-1%2Bb1=1711185338=0 Symbols marked (arch-bits=32|arch=!x32) disappeared on armel/armhf/powerpc, probably because of time_t changes? -- System Information: Debian Release: trixie/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable'), (500, 'testing'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.7.9-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled --- End Message --- --- Begin Message --- Source: mpg123 Source-Version: 1.32.6-1 Done: Sebastian Ramacher We believe that the bug you reported is fixed in the latest version of mpg123, 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 1067...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sebastian Ramacher (supplier of updated mpg123 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: Fri, 05 Apr 2024 13:31:38 +0200 Binary: libmpg123-0t64 libmpg123-0t64-dbgsym libmpg123-dev libout123-0t64 libout123-0t64-dbgsym libsyn123-0t64 libsyn123-0t64-dbgsym mpg123 mpg123-dbgsym Source: mpg123 Architecture: amd64 source Version: 1.32.6-1 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers Changed-By: Sebastian Ramacher Closes: 1063140 1067562 Description: libmpg123-0t64 - MPEG layer 1/2/3 audio decoder (shared library) libmpg123-dev - MPEG layer 1/2/3 audio decoder (development files) libout123-0t64 - MPEG layer 1/2/3 audio decoder (libout123 shared library) libsyn123-0t64 - MPEG layer 1/2/3 audio decoder (libsyn123 shared library) mpg123 - MPEG layer 1/2/3 audio player Changes: mpg123 (1.32.6-1) unstable; urgency=medium . [ Sebastian Ramacher ] * New upstream version 1.32.6 . [ Steve Langasek ] * Rename libraries for 64-bit time_t transition. (Closes: #1063140) . [ Simon Chopin ] * Only include 32bit compat symbols on i386 arches (Closes: #1067562) Checksums-Sha1: cf952d21a664e4352773151ee6484eab5d93d0b2 2062 mpg123_1.32.6-1.dsc 886c8c5f100caccfb4fefabc1c75ff6e2a834128 1116813 mpg123_1.32.6.orig.tar.bz2 4bf67a67ecd91c99eca92dbc46174df8a5669f36 833 mpg123_1.32.6.orig.tar.bz2.asc d3c318b4947c0c3c58c650af2c8ff8290ea78642 25216 mpg123_1.32.6-1.debian.tar.xz faa687634a1c1abad86d66be8b86da3ad455128a 268556 libmpg123-0t64-dbgsym_1.32.6-1_amd64.deb 10977a79ccbe3cbee755c0a78655621622c81cda 147912 libmpg123-0t64_1.32.6-1_amd64.deb f201b578b4fc5328a18666fcf8aec9d81151e284 61456 libmpg123-dev_1.32.6-1_amd64.deb c9f02db9b774e5569d55405b5ff472391a84884b 77380 libout123-0t64-dbgsym_1.32.6-1_amd64.deb 7736c71c2b1ae923fd9ac83291113ba15b54f519 29780 libout123-0t64_1.32.6-1_amd64.deb 7664ae837cf9b52a015f9a26cfd58936f568c885 185100 libsyn123-0t64-dbgsym_1.32.6-1_amd64.deb 0c3530561a258873340fe07980dce5fbc5d1 88084 libsyn123-0t64_1.32.6-1_amd64.deb 29a42931679c0c7775a346afe69c6010a7ede847 329344 mpg123-dbgsym_1.32.6-1_amd64.deb 7ec3865c9e68ea2a6d8773bfb1bc1c077a1d9745 10244 mpg123_1.32.6-1_amd64.buildinfo 4fa455e471f643544a98f062c1e4fefe13a49640 206660 mpg123_1.32.6-1_amd64.deb Checksums-Sha256: fd6fd2bc386554657ae970e0a12941c2fa2c84f3077d09cbbaaef64064677843 2062 mpg123_1.32.6-1.dsc ccdd1d0abc31d73d8b435fc658c79049d0a905b30669b6a42a03ad169dc609e6 1116813 mpg123_1.32.6.orig.tar.bz2
Processed: Re: FTBFS: missing symbols on 32-bit architectures
Processing control commands: > tags -1 ftbfs patch Bug #1067562 [src:mpg123] FTBFS: missing symbols on 32-bit architectures Added tag(s) patch. -- 1067562: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067562 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: retitle 1068293 to flowblade: 2.14 missing Depends on python3-libusb1
Processing commands for cont...@bugs.debian.org: > retitle 1068293 flowblade: 2.14 missing Depends on python3-libusb1 Bug #1068293 [flowblade] flowblade: 2.14 fails to launch due to missing app.py Changed Bug title to 'flowblade: 2.14 missing Depends on python3-libusb1' from 'flowblade: 2.14 fails to launch due to missing app.py'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1068293: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068293 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 1066599 is important
Processing commands for cont...@bugs.debian.org:
> severity 1066599 important
Bug #1066599 {Done: Sebastian Ramacher }
[src:libquicktime] libquicktime: FTBFS: qtpng.c:74:5: error: implicit
declaration of function ‘memcpy’ [-Werror=implicit-function-declaration]
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1066599: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066599
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1065859: marked as done (flowblade: Please drop dependencies on python3-distutils)
Your message dated Wed, 03 Apr 2024 03:49:24 + with message-id and subject line Bug#1065859: fixed in flowblade 2.14.0.1-1 has caused the Debian Bug report #1065859, regarding flowblade: Please drop dependencies on python3-distutils 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.) -- 1065859: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065859 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: flowblade Version: 2.12.0.2-1 Severity: important Tags: ftbfs User: debian-pyt...@lists.debian.org Usertags: python3.12 Hi Maintainer This package has dependencies, build-dependencies and/or autopkgtest dependencies on python3-distutils. The python3-distutils binary package will soon be dropped from python3-stdlib-extensions. In fact, there is no module for Python 3.12 in python3-distutils, so these dependencies may already be unnecessary. Regards Graham --- End Message --- --- Begin Message --- Source: flowblade Source-Version: 2.14.0.1-1 Done: Gürkan Myczko We believe that the bug you reported is fixed in the latest version of flowblade, 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 1065...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Gürkan Myczko (supplier of updated flowblade 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, 03 Apr 2024 05:12:09 +0200 Source: flowblade Architecture: source Version: 2.14.0.1-1 Distribution: experimental Urgency: medium Maintainer: Debian Multimedia Maintainers Changed-By: Gürkan Myczko Closes: 1065859 Changes: flowblade (2.14.0.1-1) experimental; urgency=medium . * New upstream version. * d/control: drop dependency python3-distutils. (Closes: #1065859) Checksums-Sha1: 30df31ffdeb2032759da633c7c73471bc744b35a 2162 flowblade_2.14.0.1-1.dsc 4afa7a63c4e578c1124621240d44566284d5b701 18464464 flowblade_2.14.0.1.orig.tar.gz 1351173273749fff0b17da899879d3b529274a7e 25160 flowblade_2.14.0.1-1.debian.tar.xz 83991147345ef4edf96006875e44152297ec58ff 9480 flowblade_2.14.0.1-1_source.buildinfo Checksums-Sha256: 918aa9ad8e677fffa5bc6da0c2f367099e2bb6bea6c7be6e9d7b808be3c8f8d4 2162 flowblade_2.14.0.1-1.dsc 78686715ebeda758add019032a0eb70d85e77f63f5d2aa479663f0a5a68c8e44 18464464 flowblade_2.14.0.1.orig.tar.gz 8aeac1603fcafd39f9467d988f18adbabb94317326143630022e908073af6c64 25160 flowblade_2.14.0.1-1.debian.tar.xz c840d0db967752b1237605d3dfca2d6d0257a81e93907d2a27d1eaad049320c8 9480 flowblade_2.14.0.1-1_source.buildinfo Files: 2bde69dc9901e863588ec40b657bfad3 2162 video optional flowblade_2.14.0.1-1.dsc 947be592328cfb1d7d74c3c60421a8ce 18464464 video optional flowblade_2.14.0.1.orig.tar.gz 13b9f8e746b64911dd8010d381727591 25160 video optional flowblade_2.14.0.1-1.debian.tar.xz 7dcd7cf67bcdcba18c2de56634479a0e 9480 video optional flowblade_2.14.0.1-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEtgob82PcExn/Co6JEWhSvN91FcAFAmYMzOoACgkQEWhSvN91 FcA/Lg/+Le0zmqmOjKOxVU3b4Sl/XXr4R2pQikGEOiq2RdmehiLrT4OXTBueeygi ThMMQ81z5x/GNSOGwWjq8q8spyVIcP+DvHZF5YmRB6ZkpJTnzKbsuz5HHCocHIwD u+9unesZsngjSOZA3uyCSgvqA/8cC8eJ3LKewozhxYE+9PF6z63tBYbb6D8WE2bX j7BcuLSWzWNruuY0FdIfTTB5BeCSxTI627+u203r7wLKBPApzaZxhQGlmb2J9ED7 Qz0Pv0QUR/75rEJJ9VsU3MYY9vVpjO+6KmWEtQXK+3Ks4fHfWajdyx/gWUshTlK9 aCeZJcLhH3zRSUY3NWxPmMAmZToTms+9eiSCz5a5VvAhMHCtLzE9YlYbi1Cv/sBR cOJswghcX3BtSpL/nPKNSqvshwjUY0dHV5c/OFEl1pPwRilCHlSGs7OWLDKLsCxD 1dODkyhUHfG6y4t89+dgDLdMzVB3cl+z7T1cz1B0lcE2is4ykV5K0TYp4pPR1Wqf qONzoMxB7oqKJW923T0WMwO4Ro/0KjcVwHTh1GgQD7ZWSsJtggQkn6qnakJ0XB9y 4zAua4Uvwj5fe8cCrygE+IsMGU/KPwd88IoBR1YqYqTByk9lpic54zN2O6zNUcsF ELGdtUZlWIi/HFTFafNnbNq5TFYBCYMUmG1a42n4JOMbBSnQ/p0= =b39i -END PGP SIGNATURE- pgp3doGsx93rY.pgp Description: PGP signature --- End Message ---
Processed: tagging 1068224, tagging 1068222, found 1067391 in 1.2.2-2, tagging 1067391, tagging 1068216 ...
Processing commands for cont...@bugs.debian.org:
> tags 1068224 + sid trixie
Bug #1068224 [deepin-movie] deepin-movie, dependencies unsatisfiable on 32-bit
non-i386 architectures.
Added tag(s) trixie and sid.
> tags 1068222 + sid trixie
Bug #1068222 [libappmenu-gtk3-parser0] libappmenu-gtk3-parser0, dependencies
unsatisfiable on 32-bit non-i386 architectures.
Added tag(s) trixie and sid.
> found 1067391 1.2.2-2
Bug #1067391 [bitlbee-facebook] bitlbee-facebook: redundant dependency on
libglib2.0-0
There is no source info for the package 'bitlbee-facebook' at version '1.2.2-2'
with architecture ''
Unable to make a source version for version '1.2.2-2'
Marked as found in versions 1.2.2-2.
> tags 1067391 + sid trixie
Bug #1067391 [bitlbee-facebook] bitlbee-facebook: redundant dependency on
libglib2.0-0
Added tag(s) trixie and sid.
> tags 1068216 + sid trixie
Bug #1068216 [aqemu] aqemu, dependencies unsatisfiable on 32-bit non-i386
architectures.
Added tag(s) sid and trixie.
> tags 1068149 + sid trixie
Bug #1068149 [src:porg] FTBFS: Error: symbol `open64' is already defined
Added tag(s) sid and trixie.
> forwarded 1041803 https://github.com/hyperspy/hyperspy/issues/3217
Bug #1041803 [hyperspy] hyperspy: FTBFS test_image fails
Set Bug forwarded-to-address to
'https://github.com/hyperspy/hyperspy/issues/3217'.
> tags 1041803 + sid trixie
Bug #1041803 [hyperspy] hyperspy: FTBFS test_image fails
Added tag(s) trixie and sid.
> tags 1068040 + sid trixie
Bug #1068040 [src:deepin-deb-installer] Update Build-Depends for the time64
library renames
Added tag(s) sid and trixie.
> tags 1068202 + sid trixie
Bug #1068202 [src:bazel-bootstrap] bazel-bootstrap: FTBFS:
/usr/include/absl/base/policy_checks.h:79:2: error: #error "C++ versions less
than C++14 are not supported."
Added tag(s) sid and trixie.
> found 1068230 0.36.0-1
Bug #1068230 [gnome-settings-daemon,phosh] automatic suspend regression with
gnome-settings-daemon 46
There is no source info for the package 'gnome-settings-daemon' at version
'0.36.0-1' with architecture ''
Marked as found in versions phosh/0.36.0-1.
> found 1068230 46~beta-1
Bug #1068230 [gnome-settings-daemon,phosh] automatic suspend regression with
gnome-settings-daemon 46
There is no source info for the package 'phosh' at version '46~beta-1' with
architecture ''
Marked as found in versions gnome-settings-daemon/46~beta-1.
> tags 1068180 + sid trixie
Bug #1068180 {Done: Sebastian Ramacher } [src:libgav1]
FTBFS: C++ versions less than C++14 are not supported.
Added tag(s) trixie and sid.
> tags 1068194 + sid trixie
Bug #1068194 [src:pcsx2] pcsx2: FTBFS:
/<>/plugins/cdvdGigaherz/src/CDVD.cpp:143:19: error:
‘system_error’ in namespace ‘std’ does not name a type
Added tag(s) trixie and sid.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1041803: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041803
1067391: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067391
1068040: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068040
1068149: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068149
1068180: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068180
1068194: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068194
1068202: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068202
1068216: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068216
1068222: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068222
1068224: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068224
1068230: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068230
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: Re: lmms: FTBFS on i386: dh_install: warning: Cannot find (any matches for) "usr/lib/*/lmms/libvestige.so" (tried in ., debian/tmp)
Processing control commands: > tag -1 sid trixie Bug #1068155 [src:lmms] lmms: FTBFS on i386: dh_install: warning: Cannot find (any matches for) "usr/lib/*/lmms/libvestige.so" (tried in ., debian/tmp) Added tag(s) trixie and sid. -- 1068155: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068155 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1068180: marked as done (FTBFS: C++ versions less than C++14 are not supported.)
Your message dated Mon, 01 Apr 2024 13:51:15 +
with message-id
and subject line Bug#1068180: fixed in libgav1 0.19.0-2
has caused the Debian Bug report #1068180,
regarding FTBFS: C++ versions less than C++14 are not supported.
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.)
--
1068180: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068180
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libgav1
Version: 0.18.0-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/fetch.php?pkg=libgav1=armel=0.18.0-1%2Bb2=1711940873=0
In file included from /usr/include/absl/base/config.h:86,
from /usr/include/absl/base/attributes.h:37,
from /usr/include/absl/base/thread_annotations.h:37,
from /<>/src/utils/threadpool.h:42,
from /<>/src/threading_strategy.h:24,
from /<>/src/frame_scratch_buffer.h:31,
from /<>/src/decoder_impl.h:30,
from /<>/src/decoder_impl.cc:15:
/usr/include/absl/base/policy_checks.h:79:2: error: #error "C++ versions less
than C++14 are not supported."
79 | #error "C++ versions less than C++14 are not supported."
| ^
/usr/bin/c++ -DLIBGAV1_CMAKE=1 -DLIBGAV1_ENABLE_AVX2=0 -DLIBGAV1_ENABLE_NEON=0
-DLIBGAV1_ENABLE_SSE4_1=0 -DLIBGAV1_FLAGS_SRCDIR=\"/<>\"
-DLIBGAV1_FLAGS_TMPDIR=\"/tmp\" -DLIBGAV1_MAX_BITDEPTH=10 -I/<>
-I/<>/src -I/<>/obj-arm-linux-gnueabi
-I/<>/third_party/abseil-cpp
-I/<>/third_party/googletest/googlemock/include
-I/<>/third_party/googletest/googletest/include
-I/<>/third_party/googletest/googletest -g -O2 -ffile-prefix-
map=/<>=. -flto=auto -ffat-lto-objects -fstack-protector-strong
-fstack-clash-protection -Wformat -Werror=format-security -D_LARGEFILE_SOURCE
-D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2
-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time
-D_FORTIFY_SOURCE=2 -std=gnu++11 -fPIC -Wall -Wextra -Wmissing-declarations
-Wno-sign-compare -fvisibility=hidden -fvisibility-inlines-hidden -Wno-format-
truncation -MD -MT CMakeFiles/libgav1_utils.dir/src/utils/segmentation.cc.o -MF
CMakeFiles/libgav1_utils.dir/src/utils/segmentation.cc.o.d -o
CMakeFiles/libgav1_utils.dir/src/utils/segmentation.cc.o -c
/<>/src/utils/segmentation.cc
In file included from /usr/include/absl/time/time.h:89,
from /usr/include/absl/time/clock.h:26,
from
/usr/include/absl/synchronization/internal/kernel_timeout.h:30,
from /usr/include/absl/synchronization/mutex.h:74,
from /<>/src/utils/threadpool.h:43:
/usr/include/absl/strings/string_view.h: In member function ‘constexpr void
absl::debian5::string_view::remove_prefix(size_type) const’:
/usr/include/absl/strings/string_view.h:340:10: error: assignment of member
‘absl::debian5::string_view::ptr_’ in read-only object
340 | ptr_ += n;
| ~^~~~
/usr/include/absl/strings/string_view.h:341:13: error: assignment of member
‘absl::debian5::string_view::length_’ in read-only object
341 | length_ -= n;
| ^~~~
/usr/include/absl/strings/string_view.h: In member function ‘constexpr void
absl::debian5::string_view::remove_suffix(size_type) const’:
/usr/include/absl/strings/string_view.h:350:13: error: assignment of member
‘absl::debian5::string_view::length_’ in read-only object
350 | length_ -= n;
| ^~~~
/usr/include/absl/strings/string_view.h: In member function ‘constexpr void
absl::debian5::string_view::swap(absl::debian5::string_view&) const’:
/usr/include/absl/strings/string_view.h:358:13: error: passing ‘const
absl::debian5::string_view’ as ‘this’ argument discards qualifiers
[-fpermissive]
358 | *this = s;
| ^
/usr/include/absl/strings/string_view.h:161:7: note: in call to
‘absl::debian5::string_view& absl::debian5::string_view::operator=(const
absl::debian5::string_view&)’
161 | class string_view {
| ^~~
make[3]: Leaving directory '/<>/obj-arm-linux-gnueabi'
[ 15%] Built target libgav1_file_writer
/usr/include/absl/time/time.h: In constructor
‘absl::debian5::Duration::HiRep::HiRep(int64_t)’:
/usr/include/absl/time/time.h:256:5: error: ‘constexpr’ constructor does not
have empty body
256 | }
| ^
/usr/include/absl/time/time.h: In member function ‘constexpr int64_t
absl::debian5::Duration::Hi
Bug#1067494: marked as done (obs-studio: FTBFS on time64_t archs)
Your message dated Sun, 31 Mar 2024 13:39:07 +
with message-id
and subject line Bug#1067494: fixed in obs-studio 30.0.2+dfsg-3
has caused the Debian Bug report #1067494,
regarding obs-studio: FTBFS on time64_t archs
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.)
--
1067494: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067494
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: obs-studio
Version: 30.0.2+dfsg-2.1
Severity: serious
Hello, looks like we got a failure due to time64_t transition.
/usr/bin/cc -DENABLE_HEVC -DHAVE_OBSCONFIG_H -DHAVE_UDEV -Dlinux_v4l2_EXPORTS -I/<>/libobs
-I/<>/obj-arm-linux-gnueabihf/config -g -O2 -Werror=implicit-function-declaration
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -fno-stack-clash-protection
-fdebug-prefix-map=/<>=/usr/src/obs-studio-30.0.2+dfsg-2.1build2 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64
-Wdate-time -D_FORTIFY_SOURCE=3 -DFFMPEG_MUX_FIXED=\"/usr/lib/arm-linux-gnueabihf/obs-plugins/obs-ffmpeg/obs-ffmpeg-mux\"
-DSIMDE_ENABLE_OPENMP -fopenmp-simd -O3 -fvisibility=hidden -Wno-error=deprecated-declarations -std=gnu17 -fPIC -Werror -Wextra -Wvla -Wno-error=vla
-Wswitch -Wno-error=switch -Wformat -Wformat-security -Wunused-parameter -Wno-unused-function -Wno-missing-field-initializers -fno-strict-aliasing
-Werror-implicit-function-declaration -Wno-missing-braces -Wno-error=maybe-uninitialized -DSIMDE_ENABLE_OPENMP -fopenmp-simd -MD -MT
plugins/linux-v4l2/CMakeFiles/linux-v4l2.dir/v4l2-input.c.o -MF plugins/linux-v4l2/CMakeFiles/linux-v4l2.dir/v4l2-input.c.o.d -o
plugins/linux-v4l2/CMakeFiles/linux-v4l2.dir/v4l2-input.c.o -c /<>/plugins/linux-v4l2/v4l2-input.c
/<>/plugins/linux-v4l2/v4l2-input.c: In function ‘v4l2_thread’:
/<>/plugins/linux-v4l2/v4l2-input.c:66:43: error: format ‘%ld’
expects argument of type ‘long int’, but argument 4 has type ‘__suseconds64_t’ {aka ‘long
long int’} [-Werror=format=]
66 | #define blog(level, msg, ...) blog(level, "v4l2-input: " msg,
##__VA_ARGS__)
| ^~
/<>/plugins/linux-v4l2/v4l2-input.c:262:17: note: in expansion of
macro ‘blog’
262 | blog(LOG_DEBUG,
| ^~~~
cc1: all warnings being treated as errors
[137/484] /usr/bin/cc -DENABLE_HEVC -DHAVE_OBSCONFIG_H -Dlinux_jack_EXPORTS -I/<>/libobs
-I/<>/obj-arm-linux-gnueabihf/config -g -O2 -Werror=implicit-function-declaration
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -fno-stack-clash-protection
-fdebug-prefix-map=/<>=/usr/src/obs-studio-30.0.2+dfsg-2.1build2 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64
-Wdate-time -D_FORTIFY_SOURCE=3 -DFFMPEG_MUX_FIXED=\"/usr/lib/arm-linux-gnueabihf/obs-plugins/obs-ffmpeg/obs-ffmpeg-mux\"
-DSIMDE_ENABLE_OPENMP -fopenmp-simd -O3 -fvisibility=hidden -Wno-error=deprecated-declarations -std=gnu17 -fPIC -Werror -Wextra -Wvla -Wno-error=vla
-Wswitch -Wno-error=switch -Wformat -Wformat-security -Wunused-parameter -Wno-unused-function -Wno-missing-field-initializers -fno-strict-aliasing
-Werror-implicit-function-declaration -Wno-missing-braces -Wno-error=maybe-uninitialized -DSIMDE_ENABLE_OPENMP -fopenmp-simd -MD -MT
plugins/linux-jack/CMakeFiles/linux-jack.dir/linux-jack.c.o -MF plugins/linux-jack/CMakeFiles/linux-jack.dir/linux-jack.c.o.d -o
plugins/linux-jack/CMakeFiles/linux-jack.dir/linux-jack.c.o -c /<>/plugins/linux-jack/linux-jack.c
I did "fix" with an ugly hacky patch, just for armhf platform, but I don't know
how to properly solve it.
diff -Nru obs-studio-30.0.2+dfsg/debian/patches/time64.patch
obs-studio-30.0.2+dfsg/debian/patches/time64.patch
--- obs-studio-30.0.2+dfsg/debian/patches/time64.patch 1970-01-01
01:00:00.0 +0100
+++ obs-studio-30.0.2+dfsg/debian/patches/time64.patch 2024-03-22
13:31:40.0 +0100
@@ -0,0 +1,18 @@
+Description: Use time64_t everywhere
+Author: Gianfranco Costamagna
+Last-Update: 2024-03-21
+
+--- obs-studio-30.0.2+dfsg.orig/plugins/linux-v4l2/v4l2-input.c
obs-studio-30.0.2+dfsg/plugins/linux-v4l2/v4l2-input.c
+@@ -260,7 +260,11 @@ static void *v4l2_thread(void *vptr)
+ }
+
+ blog(LOG_DEBUG,
++#ifndef __arm__
+"%s: ts: %06ld buf id #%d, flags 0x%08X, seq #%d, len %d, used
%d",
++#else
++ "%s: ts: %06lld
Processed: Bug#1067494 marked as pending in obs-studio
Processing control commands: > tag -1 pending Bug #1067494 [obs-studio] obs-studio: FTBFS on time64_t archs Added tag(s) pending. -- 1067494: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067494 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1068114: marked as done (libfluidsynth-dev: package depends on libsystemd-dev)
Your message dated Sun, 31 Mar 2024 00:33:32 +0100 with message-id and subject line Re: Bug#1068114: libfluidsynth-dev: package depends on libsystemd-dev has caused the Debian Bug report #1068114, regarding libfluidsynth-dev: package depends on libsystemd-dev 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.) -- 1068114: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068114 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libfluidsynth-dev Version: 2.3.4-1+b3 Severity: important X-Debbugs-Cc: noreply+debian.reportbug.photofilmst...@adaptivetime.com Dear Maintainer, I have libfluidsynth3 installed and it correctly does not depend on libsystemd. However, when trying to install libfluidsynth-dev insists it must install libsystemd- dev. This hard dependency should be removed as it is clearly unnecessary and is preventing me from being able to install libfluidsynth-dev. -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'oldstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.5.0-4-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: sysvinit (via /sbin/init) LSM: AppArmor: enabled Versions of packages libfluidsynth-dev depends on: ii libasound2-dev 1.2.11-1+b1 ii libdbus-1-dev1.14.10-4+b1 pn libfluidsynth2 ii libfluidsynth3 2.3.4-1+b3 pn libinstpatch-dev ii libjack-dev 1:0.126.0-2+b2 ii libpipewire-0.3-dev 1.0.4-3 ii libpulse-dev 16.1+dfsg1-3+b1 ii libreadline-dev 8.2-4 ii libsdl2-dev 2.30.1+dfsg-4 pn libsndfile-dev pn libsystemd-dev libfluidsynth-dev recommends no packages. libfluidsynth-dev suggests no packages. --- End Message --- --- Begin Message --- On 2024-03-30 19:04:13 -0400, Gravis wrote: > Package: libfluidsynth-dev > Version: 2.3.4-1+b3 > Severity: important > X-Debbugs-Cc: noreply+debian.reportbug.photofilmst...@adaptivetime.com > > Dear Maintainer, > > I have libfluidsynth3 installed and it correctly does not depend on > libsystemd. > However, > when trying to install libfluidsynth-dev insists it must install libsystemd- > dev. This > hard dependency should be removed as it is clearly unnecessary and is > preventing me from > being able to install libfluidsynth-dev. The pkg-config file included in libfluidsynth-dev lists libsystemd in Requires.privat so the dependency on libsystem-dev is correct and required. Closing Cheers > > > -- System Information: > Debian Release: trixie/sid > APT prefers unstable > APT policy: (500, 'unstable'), (500, 'testing'), (500, 'oldstable') > Architecture: amd64 (x86_64) > Foreign Architectures: i386 > > Kernel: Linux 6.5.0-4-amd64 (SMP w/8 CPU threads; PREEMPT) > Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not > set > Shell: /bin/sh linked to /usr/bin/dash > Init: sysvinit (via /sbin/init) > LSM: AppArmor: enabled > > Versions of packages libfluidsynth-dev depends on: > ii libasound2-dev 1.2.11-1+b1 > ii libdbus-1-dev1.14.10-4+b1 > pn libfluidsynth2 > ii libfluidsynth3 2.3.4-1+b3 > pn libinstpatch-dev > ii libjack-dev 1:0.126.0-2+b2 > ii libpipewire-0.3-dev 1.0.4-3 > ii libpulse-dev 16.1+dfsg1-3+b1 > ii libreadline-dev 8.2-4 > ii libsdl2-dev 2.30.1+dfsg-4 > pn libsndfile-dev > pn libsystemd-dev > > libfluidsynth-dev recommends no packages. > > libfluidsynth-dev suggests no packages. > -- Sebastian Ramacher--- End Message ---
Processed: block 1036884 with 1067272 1067494 1067829 1067561
Processing commands for cont...@bugs.debian.org: > block 1036884 with 1067272 1067494 1067829 1067561 Bug #1036884 [release.debian.org] transition: time64_t 1036884 was blocked by: 1067193 1067171 1065787 1055530 1067190 1067509 1067189 1067458 1067069 1062847 1067288 1067677 1055352 1065973 1065816 1067192 1066049 1067676 1066794 1066328 1067170 1067508 1067175 1036884 was not blocking any bugs. Added blocking bug(s) of 1036884: 1067272, 1067829, 1067494, and 1067561 > thanks Stopping processing here. Please contact me if you need assistance. -- 1036884: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036884 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1067883: marked as done (terminatorx: Depends on dead-upstream mpg321 instead of mpg123)
Your message dated Fri, 29 Mar 2024 20:14:07 + with message-id and subject line Bug#1067883: fixed in terminatorx 4.2.0-2 has caused the Debian Bug report #1067883, regarding terminatorx: Depends on dead-upstream mpg321 instead of mpg123 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.) -- 1067883: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067883 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: terminatorx Version: 4.2.0-1 Severity: normal X-Debbugs-Cc: ametz...@bebt.de User: ametz...@debian.org Usertags: mpg321-removal Hello, this package depends on mpg321. mpg321 is dead upstream (last change 2012, about 12 years ago), it was initially created because of license issues with mpg123, however mpg123 moved to Debian main in 2006. Please consider moving to another player, e.g. mpg123. mpg123 license nowadays is LGPL-2.1, while mpg321 uses GPL-2+. Since LGPL-2.1 can be relicensed to GPL-2+ there should not be any problemds on that side. cu Andreas --- End Message --- --- Begin Message --- Source: terminatorx Source-Version: 4.2.0-2 Done: Dennis Braun We believe that the bug you reported is fixed in the latest version of terminatorx, 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 1067...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Dennis Braun (supplier of updated terminatorx 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: Fri, 29 Mar 2024 20:14:05 +0100 Source: terminatorx Architecture: source Version: 4.2.0-2 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers Changed-By: Dennis Braun Closes: 1067883 Changes: terminatorx (4.2.0-2) unstable; urgency=medium . * Change B-D mpg321 -> mpg123 (Closes: #1067883) * Prefer libjack-dev over libjack-jackd2-dev * Bump Standards-Version to 4.6.2 * Use the default CI/CD configuration from salsa * Change my email address Checksums-Sha1: 56915baaa3bfd6ce97097c4a3d84d528680373f1 2326 terminatorx_4.2.0-2.dsc 3edf0db49cd99c13df806a711e0d02bcc133c3ee 16956 terminatorx_4.2.0-2.debian.tar.xz 0788dd1c86a2521ef385cef87a2421e8bc02989d 7159 terminatorx_4.2.0-2_source.buildinfo Checksums-Sha256: 3db10b2b12446c855b0c9d449bb67a4da696083a1377514c58e57736cdea9bc2 2326 terminatorx_4.2.0-2.dsc 612fbdc645600c0a206e18922bc453cc87d291a340c6fb190e62abfcac3c77cf 16956 terminatorx_4.2.0-2.debian.tar.xz 56e68ea1624bcf82278cfdabe1a4e267c9926d0faaa2b1053bcd92ae6af179ae 7159 terminatorx_4.2.0-2_source.buildinfo Files: 75fd6ed9bb190b8d182a244b4ffb2264 2326 sound optional terminatorx_4.2.0-2.dsc ec4af57661ecd7e13d847c879fbcd693 16956 sound optional terminatorx_4.2.0-2.debian.tar.xz f89bbbe28dceadd4a1145f0129a2794b 7159 sound optional terminatorx_4.2.0-2_source.buildinfo -BEGIN PGP SIGNATURE- iQJDBAEBCgAtFiEEPLfDAq+1fmGoxhfdY06lXZArmDYFAmYHE/oPHHNuZEBkZWJp YW4ub3JnAAoJEGNOpV2QK5g24IQP/jAEEClaoZWPGTVkzVqpTtBNxkb7aqMuSkrG CR/BKkWrtFTyKJAQNLmksOani/fIQ26Cyk3o0wFsiJOeY00kuclS7JdRwLl+SN7N C1zxemmW7q4IMao7PqcuhDQ2VCWZp1iwjbDotiaoWnk/RCyFT5SOfg5GQfSOc5XC /wj4qIDIYU+dF7s7Kg34Rmq7mc8kRAOwViqvor1XdCjMBQhXs6oXdMpgVMnnBqXf S+e5duwVoacnf6osqVw593soLAqULon5Xvz+rq+XZvyLamg08TfO/OfVkH2FzCTt c6/rrg3H9Iwdy700d+jKww16SbK1V1mWp/Su5YW2b07kCQ5PbwetuKNhIXA7fblk HtYBDrG6DBNJdtQEfNyFsPyNPCRlysGgvPt7QWf98MqUZ0S3OFJkcRBrfebWsHII QsZCheBjqL9T2JRhjzXyKa4w9z8Qf3xw5A6kQ6gNF6798udDiFULjSBy9ptftPnx XbzRp66vP3PqxZe7p/+ctrbJYOSboLbnMmCjhuQQJ9aCcfdRuXudy9j1vVWv5FOr TpWtWGnY6F/wJCP/VDxAkZ4QWPniT007c61NYQJOTkqTA4n1xhmlAtyTtPLc36ac ZK2MqkqkGmpVaV/hHKioidPmnzfwIlJQmJCqRo6vKI/w5rvyWu3+jeuOb8CuX3kB DJGrciuU =lJS7 -END PGP SIGNATURE- pgpqj8RxkwGxx.pgp Description: PGP signature --- End Message ---
Bug#1062831: marked as done (guitarix: segfaults, when creating a preset bank)
Your message dated Fri, 29 Mar 2024 19:43:48 + with message-id and subject line Bug#1062831: fixed in guitarix 0.46.0+dfsg-1 has caused the Debian Bug report #1062831, regarding guitarix: segfaults, when creating a preset bank 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.) -- 1062831: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062831 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: guitarix Version: 0.44.1+dfsg1-3+b1 Severity: normal X-Debbugs-Cc: invernom...@paranoici.org Hello and thanks for maintaining Guitarix in Debian! I would like to save some presets. I click on the "Preset:" button and then on "New Bank": a new field appears, where I should enter the name of the new bank. If, instead, I just click on this field, guitarix segfaults. Please investigate, reproduce the bug and fix it and/or forward my bug report upstream, as appropriate. Thanks for your time! -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (800, 'testing'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 6.5.0-5-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages guitarix depends on: ii fonts-roboto 2:0~20170802-3 ii guitarix-common 0.44.1+dfsg1-3 ii guitarix-ladspa 0.44.1+dfsg1-3+b1 ii guitarix-lv2 0.44.1+dfsg1-3+b1 ii libatkmm-1.6-1v5 2.28.3-2+b1 ii libavahi-common3 0.8-13+b1 ii libavahi-gobject0 0.8-13+b1 ii libbluetooth3 5.71-1 ii libboost-iostreams1.83.0 1.83.0-2+b2 ii libc6 2.37-15~deb13u1 ii libcairomm-1.0-1v51.14.5-1 ii libcurl3-gnutls 8.5.0-2 ii libfftw3-single3 3.3.10-1 ii libgcc-s1 13.2.0-10 ii libglib2.0-0 2.78.3-2 ii libglibmm-2.4-1v5 2.66.6-2 ii libgtk-3-03.24.40-2 ii libgtkmm-3.0-1v5 3.24.8-2 ii libgxw0 0.44.1+dfsg1-3+b1 ii libgxwmm0 0.44.1+dfsg1-3+b1 ii libjack-jackd2-0 [libjack-0.125] 1.9.21~dfsg-3 ii liblilv-0-0 0.24.22-1 ii liblrdf0 0.6.1-4 ii libpangomm-1.4-1v52.46.3-1 ii libsigc++-2.0-0v5 2.12.1-1 ii libsndfile1 1.2.2-1 ii libstdc++613.2.0-10 ii libzita-convolver44.0.3-2 ii libzita-resampler11.11.2-1 Versions of packages guitarix recommends: pn gvfs-backends ii jack-capture 0.9.73-4 pn lame ii vorbis-tools 1.4.2-1+b1 guitarix suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: guitarix Source-Version: 0.46.0+dfsg-1 Done: Dennis Braun We believe that the bug you reported is fixed in the latest version of guitarix, 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 1062...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Dennis Braun (supplier of updated guitarix 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: Fri, 29 Mar 2024 17:15:09 +0100 Source: guitarix Architecture: source Version: 0.46.0+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers Changed-By: Dennis Braun Closes: 1062831 Changes: guitarix (0.46.0+dfsg-1) unstable; urgency=medium . * New upstream version 0.46.0+dfsg + Fix segfaults, when creating a preset bank (Closes: #1062831) * Development switched to github, update d/copyright and d/watch * LADSPA support is dropped, remove ladspa package * Drop patches applied by upstream * Add libfftw3-dev to B-Ds * Bump d/copyright years * Refresh *.lintian.overrides, add d/source/lintian-over
Processed: Bug#1067883 marked as pending in terminatorx
Processing control commands: > tag -1 pending Bug #1067883 [src:terminatorx] terminatorx: Depends on dead-upstream mpg321 instead of mpg123 Added tag(s) pending. -- 1067883: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067883 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 1067494
Processing commands for cont...@bugs.debian.org: > tags 1067494 + ftbfs Bug #1067494 [obs-studio] obs-studio: FTBFS on time64_t archs Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 1067494: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067494 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1056141: marked as done (nvenc encoder not available after installing libnvidia-encode1 and enabling ffnvcodec)
Your message dated Thu, 28 Mar 2024 16:55:25 +0100 with message-id and subject line Re: Bug#1056141: nvenc encoder not available after installing libnvidia-encode1 and enabling ffnvcodec has caused the Debian Bug report #1056141, regarding nvenc encoder not available after installing libnvidia-encode1 and enabling ffnvcodec 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.) -- 1056141: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056141 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ffmpeg Version: 7:6.1-2 Hi in Trixie, using nvidia-driver 525.125.06-2, libnvidia-encode1 525.125.06-2, and ffmpeg 7:6.1-2, I can't seem to get the nvenc codec built into ffmpeg. $ ffmpeg -codecs | grep 264 H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10 (decoders: h264 h264_v4l2m2m h264_qsv h264_cuvid ) (encoders: libx264 libx264rgb h264_omx h264_qsv h264_v4l2m2m h264_vaapi ) These are the additional enable flags I added to the debian/rules file: --enable-nonfree \ --enable-cuda-llvm \ --enable-ffnvcodec Full build configuration: configuration: --prefix=/usr --extra-version=9 --toolchain=hardened --libdir=/usr/lib/x86_64-linux-gnu --incdir=/usr/include/x86_64-linux-gnu --arch=amd64 --enable-gpl --disable-stripping --enable-gnutls --enable-ladspa --enable-libaom --enable-libass --enable-libbluray --enable-libbs2b --enable-libcaca --enable-libcdio --enable-libcodec2 --enable-libdav1d --enable-libflite --enable-libfontconfig --enable-libfreetype --enable-libfribidi --enable-libglslang --enable-libgme --enable-libgsm --enable-libjack --enable-libmp3lame --enable-libmysofa --enable-libopenjpeg --enable-libopenmpt --enable-libopus --enable-libpulse --enable-librabbitmq --enable-librist --enable-librubberband --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libsrt --enable-libssh --enable-libtheora --enable-libtwolame --enable-libvidstab --enable-libvorbis --enable-libvpx --enable-libwebp --enable-libx265 --enable-libxml2 --enable-libxvid --enable-libzimg --enable-libzmq --enable-libzvbi --enable-lv2 --enable-omx --enable-openal --enable-opencl --enable-opengl --enable-sdl2 --enable-nonfree --enable-cuda-llvm --enable-ffnvcodec --disable-sndio --enable-libjxl --enable-pocketsphinx --enable-librsvg --enable-libvpl --disable-libmfx --enable-libdc1394 --enable-libdrm --enable-libiec61883 --enable-chromaprint --enable-frei0r --enable-libsvtav1 --enable-libx264 --enable-libplacebo --enable-librav1e --enable-shared After being built I just installed the ffmpeg and libavcodec debs. $ dpkg -i': sudo dpkg -i ffmpeg_6.0-9_amd64.deb libavcodec60_6.0-9_amd64.deb libavcodec-extra* I originally had the proprietary driver installed via the vendor's script, but it has since been removed. My goal is to have nvenc appear as an option in OBS, which depends on ffmpeg to have the codec available. --- End Message --- --- Begin Message --- On 2023-11-17 11:20:11 -0500, Brian Bostwick wrote: > Package: ffmpeg > Version: 7:6.1-2 > > Hi in Trixie, using nvidia-driver 525.125.06-2, libnvidia-encode1 > 525.125.06-2, and ffmpeg 7:6.1-2, I can't seem to get the nvenc codec > built into ffmpeg. This was probably a driver version mismatch. 535.x is now available in unstable fixing this issues. Cheers > > $ ffmpeg -codecs | grep 264 > H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10 (decoders: h264 h264_v4l2m2m > h264_qsv h264_cuvid ) (encoders: libx264 libx264rgb h264_omx h264_qsv > h264_v4l2m2m h264_vaapi ) > > These are the additional enable flags I added to the debian/rules file: > > --enable-nonfree \ > --enable-cuda-llvm \ > --enable-ffnvcodec > > Full build configuration: > > configuration: > --prefix=/usr > --extra-version=9 > --toolchain=hardened > --libdir=/usr/lib/x86_64-linux-gnu > --incdir=/usr/include/x86_64-linux-gnu > --arch=amd64 > --enable-gpl > --disable-stripping > --enable-gnutls > --enable-ladspa > --enable-libaom > --enable-libass > --enable-libbluray > --enable-libbs2b > --enable-libcaca > --enable-libcdio > --enable-libcodec2 > --enable-libdav1d > --enable-libflite &g
Bug#1066683: marked as done (vorbis-tools: FTBFS: codec_skeleton.c:119:9: error: implicit declaration of function ‘utf8_decode’ [-Werror=implicit-function-declaration])
Your message dated Wed, 27 Mar 2024 11:29:28 +
with message-id
and subject line Bug#1066683: fixed in vorbis-tools 1.4.2-2
has caused the Debian Bug report #1066683,
regarding vorbis-tools: FTBFS: codec_skeleton.c:119:9: error: implicit
declaration of function ‘utf8_decode’ [-Werror=implicit-function-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.)
--
1066683: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066683
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: vorbis-tools
Version: 1.4.2-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
This is most likely caused by a change in dpkg 1.22.6, that enabled
-Werror=implicit-function-declaration. For more information, see
https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration
Relevant part (hopefully):
> gcc -DLOCALEDIR=\"/usr/share/locale\" -DHAVE_CONFIG_H -I. -I.. -I../include
> -I../intl -Wdate-time -D_FORTIFY_SOURCE=2 -O2 -Wall -ffast-math
> -fsigned-char -g -O2 -Werror=implicit-function-declaration
> -ffile-prefix-map=/<>=. -fstack-protector-strong
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -c
> -o codec_invalid.o codec_invalid.c
> codec_skeleton.c: In function ‘skeleton_process_fisbone_message_header’:
> codec_skeleton.c:119:9: error: implicit declaration of function ‘utf8_decode’
> [-Werror=implicit-function-declaration]
> 119 | if (utf8_decode(header, ) < 0) {
> | ^~~
> codec_skeleton.c: In function ‘skeleton_end’:
> codec_skeleton.c:254:25: warning: unused variable ‘self’ [-Wunused-variable]
> 254 | misc_skeleton_info *self = stream->data;
> | ^~~~
> cc1: some warnings being treated as errors
> make[3]: *** [Makefile:578: codec_skeleton.o] Error 1
The full build log is available from:
http://qa-logs.debian.net/2024/03/13/vorbis-tools_1.4.2-1_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240313;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240313=lu...@debian.org=1=1=1=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: vorbis-tools
Source-Version: 1.4.2-2
Done: Sebastian Ramacher
We believe that the bug you reported is fixed in the latest version of
vorbis-tools, 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 1066...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Sebastian Ramacher (supplier of updated vorbis-tools
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, 27 Mar 2024 11:08:53 +0100
Source: vorbis-tools
Architecture: source
Version: 1.4.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers
Changed-By: Sebastian Ramacher
Closes: 1066683
Changes:
vorbis-tools (1.4.2-2) unstable; urgency=medium
.
* Team upload
.
[ Debian Janitor ]
* Remove constraints unnecessary since buster
* Trim trailing whitespace.
* Drop transition for old debug package migration.
.
[ Dennis Braun ]
* Update rules, no need to override dh_strip anymore
.
[ Sebastian Ramacher ]
* Add missing include (Closes: #1066683)
Checksums-Sha1:
96401075d234d91c2e63ec3741e87cb8cceb9e2a 1673 vorbis-tools_1.4.2-2.dsc
4bb9776c40f6c0e987f5318adf9b4d418777eb63 39624
vorbis-tools_1.4.2-2.debian.tar.xz
Processed: Bug#1066683 marked as pending in vorbis-tools
Processing control commands: > tag -1 pending Bug #1066683 [src:vorbis-tools] vorbis-tools: FTBFS: codec_skeleton.c:119:9: error: implicit declaration of function ‘utf8_decode’ [-Werror=implicit-function-declaration] Added tag(s) pending. -- 1066683: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066683 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: reassign 1067662 to a2jmidid, tagging 1067662 ..., reassign 1060734 to src:sail
Processing commands for cont...@bugs.debian.org: > reassign 1067662 a2jmidid 9-3 Bug #1067662 [aj2midid] a2jmidid doesn't handle midi interfaces with two or more identical port names correctly and fails to expose them Warning: Unknown package 'aj2midid' Bug reassigned from package 'aj2midid' to 'a2jmidid'. No longer marked as found in versions 9-3. Ignoring request to alter fixed versions of bug #1067662 to the same values previously set Bug #1067662 [a2jmidid] a2jmidid doesn't handle midi interfaces with two or more identical port names correctly and fails to expose them Marked as found in versions a2jmidid/9-3. > tags 1067662 + fixed-upstream Bug #1067662 [a2jmidid] a2jmidid doesn't handle midi interfaces with two or more identical port names correctly and fails to expose them Added tag(s) fixed-upstream. > forwarded 1067662 https://github.com/jackaudio/a2jmidid/pull/5 Bug #1067662 [a2jmidid] a2jmidid doesn't handle midi interfaces with two or more identical port names correctly and fails to expose them Set Bug forwarded-to-address to 'https://github.com/jackaudio/a2jmidid/pull/5'. > reassign 1060734 src:sail 0.9.0+repack-2 Bug #1060734 [libsail0] Add more dev dependencies Warning: Unknown package 'libsail0' Bug reassigned from package 'libsail0' to 'src:sail'. No longer marked as found in versions sail/0.9.0+repack-2. Ignoring request to alter fixed versions of bug #1060734 to the same values previously set Bug #1060734 [src:sail] Add more dev dependencies Marked as found in versions sail/0.9.0+repack-2. > thanks Stopping processing here. Please contact me if you need assistance. -- 1060734: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060734 1067662: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067662 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: let these show up on buildd.d.o overview page
Processing commands for cont...@bugs.debian.org:
> tags 883308 + ftbfs
Bug #883308 [libseccomp2] libseccomp2 is missing support for ia64, alpha, sh4,
sparc64, m68k
Added tag(s) ftbfs.
> tags 1067055 + ftbfs
Bug #1067055 [src:openmpi] openmpi: error: implicit declaration of function
'OPAL_THREAD_ADD_FETCH64'
Ignoring request to alter tags of bug #1067055 to the same tags previously set
> tags 1067207 + ftbfs
Bug #1067207 [src:mesa] mesa: switch statement too large, might need
-mlong-jump-table-offsets
Ignoring request to alter tags of bug #1067207 to the same tags previously set
> tags 1067447 + ftbfs
Bug #1067447 [src:jackd2] jackd2: patch to fix ftbfs on m68k; jack{1,2}:
unneeded libffado-dev B-D on some arches
Added tag(s) ftbfs.
> tags 1067577 + ftbfs
Bug #1067577 [src:sysprof] sysprof: B-D on libunwind-dev which is not generally
available
Added tag(s) ftbfs.
> tags 1067582 + ftbfs
Bug #1067582 [src:gnuplot] gnuplot: please provide a profile to break B-D cycle
Added tag(s) ftbfs.
> tags 1067613 + ftbfs
Bug #1067613 [src:openjdk-11] openjdk-11: FTBFS on alpha: d/rules references
deleted patch (trivial fix)
Added tag(s) ftbfs.
> tags 1067643 + ftbfs
Bug #1067643 [src:webkit2gtk] webkit2gtk: please use architecture whitelist for
libseccomp-dev B-D
Added tag(s) ftbfs.
> tags 1067644 + ftbfs
Bug #1067644 [src:gcc-12] gcc-12: BD-Uninstallable on m68k due to gnat-11 vs
gnat-12
Added tag(s) ftbfs.
> tags 1067646 + ftbfs
Bug #1067646 [src:llvm-toolchain-17] llvm-toolchain-17: please enable m68k build
Added tag(s) ftbfs.
> tags 1067647 + ftbfs
Bug #1067647 [src:google-perftools] google-perftools: FTBFS: #error Could not
determine cache line length - unknown architecture
Added tag(s) ftbfs.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1067055: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067055
1067207: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067207
1067447: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067447
1067577: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067577
1067582: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067582
1067613: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067613
1067643: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067643
1067644: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067644
1067646: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067646
1067647: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067647
883308: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883308
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: tagging 1067618, tagging 1067624, tagging 1067596, tagging 1067623, tagging 1067609, tagging 1067547 ...
y-gnome/3.4.3-2.
> fixed 1038298 3.4.3-4
Bug #1038298 {Done: Jeremy Bícha } [src:ruby-gnome] please
drop transitional package ruby-gnome2-dev from src:ruby-gnome
Marked as fixed in versions ruby-gnome/3.4.3-4.
> reassign 1038297 src:ruby-gnome 3.4.3-2
Bug #1038297 {Done: Jeremy Bícha } [ruby-gnome2] please drop
transitional package ruby-gnome2 from src:ruby-gnome
Bug reassigned from package 'ruby-gnome2' to 'src:ruby-gnome'.
No longer marked as found in versions ruby-gnome/3.4.3-2.
No longer marked as fixed in versions ruby-gnome/3.4.3-4.
Bug #1038297 {Done: Jeremy Bícha } [src:ruby-gnome] please
drop transitional package ruby-gnome2 from src:ruby-gnome
Marked as found in versions ruby-gnome/3.4.3-2.
> fixed 1038297 3.4.3-4
Bug #1038297 {Done: Jeremy Bícha } [src:ruby-gnome] please
drop transitional package ruby-gnome2 from src:ruby-gnome
Marked as fixed in versions ruby-gnome/3.4.3-4.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1016379: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016379
1032715: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032715
1032716: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032716
1032755: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032755
1032788: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032788
1038226: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038226
1038297: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038297
1038298: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038298
1038301: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038301
1038304: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038304
1050523: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050523
1065915: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065915
1066102: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066102
1067139: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067139
1067219: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067219
1067221: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067221
1067223: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067223
1067224: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067224
1067304: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067304
1067367: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067367
1067547: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067547
1067596: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067596
1067609: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067609
1067618: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067618
1067623: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067623
1067624: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067624
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1067323: marked as done (liblc3: FTBFS: attdet_py.c:20:10: fatal error: numpy/ndarrayobject.h: No such file or directory)
Your message dated Sat, 23 Mar 2024 22:24:17 + with message-id and subject line Bug#1067323: fixed in liblc3 1.0.4-3 has caused the Debian Bug report #1067323, regarding liblc3: FTBFS: attdet_py.c:20:10: fatal error: numpy/ndarrayobject.h: No such file or directory 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.) -- 1067323: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067323 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: liblc3 Version: 1.0.4-2 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240319 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > x86_64-linux-gnu-gcc -Wsign-compare -DNDEBUG -g -fwrapv -O2 -Wall -g > -fstack-protector-strong -fstack-clash-protection -Wformat > -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -g > -O2 -Werror=implicit-function-declaration > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection > -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC > -DNPY_NO_DEPRECATED_API=NPY_1_7_API_VERSION -I../src -I../include > -I/usr/include/python3.11 -c attdet_py.c -o > build/temp.linux-x86_64-cpython-311/attdet_py.o -std=c11 -ffast-math > attdet_py.c:20:10: fatal error: numpy/ndarrayobject.h: No such file or > directory >20 | #include > | ^~~ > compilation terminated. > error: command '/usr/bin/x86_64-linux-gnu-gcc' failed with exit code 1 > make[2]: *** [test/makefile.mk:18: test_py] Error 1 The full build log is available from: http://qa-logs.debian.net/2024/03/19/liblc3_1.0.4-2_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240319;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240319=lu...@debian.org=1=1=1=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: liblc3 Source-Version: 1.0.4-3 Done: Dylan Aïssi We believe that the bug you reported is fixed in the latest version of liblc3, 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 1067...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Dylan Aïssi (supplier of updated liblc3 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: Sat, 23 Mar 2024 22:22:25 +0100 Source: liblc3 Architecture: source Version: 1.0.4-3 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers Changed-By: Dylan Aïssi Closes: 1067323 Changes: liblc3 (1.0.4-3) unstable; urgency=medium . * Cherry-pick upstream patch adding numpy include path (Closes: #1067323) * Refresh debian/copyright * Add debian/upstream/metadata Checksums-Sha1: 0fe69fac6d49dbbeef3bb942c620c980333007a8 2208 liblc3_1.0.4-3.dsc d14544e706167c90257a1f77e22dd0fb345c2653 3360 liblc3_1.0.4-3.debian.tar.xz e3f042448b7786982c53f86658ee0cf4f95296ac 8187 liblc3_1.0.4-3_amd64.buildinfo Checksums-Sha256: e78394373d99cc6bd68ac2bc7474682e297395b71d8e16e2e9a85278a1b97120 2208 liblc3_1.0.4-3.dsc 8a931d7d987e94a1522f2ed1d65de892dae01e635222c0456aaf733fbef00e55 3360 liblc3_1.0.4-3.debian.tar.xz 23c3daa429e97d4e86d9233bab60666ab8364acc4f9a6d34ff8acf08b2f2e5d1 8187 liblc3_1.0.4-3_amd64.buildinfo Files: 600eb7055da6e3ecd67d3ad77a8593ea 2208 sound optional liblc3_1.0.4-3.dsc 5bd5ff942715f1b81b23234cda3a7b28 3360 sound optional liblc3_1.0.4-3.debian.tar.xz 98b087c93e239119138e02ddc7412a2a 8187 sound optional
Processed: Bug#1067323 marked as pending in liblc3
Processing control commands: > tag -1 pending Bug #1067323 [src:liblc3] liblc3: FTBFS: attdet_py.c:20:10: fatal error: numpy/ndarrayobject.h: No such file or directory Added tag(s) pending. -- 1067323: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067323 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1059068: marked as done (apt: fails to resolve dependencies)
Your message dated Sat, 23 Mar 2024 19:00:32 + with message-id and subject line Bug#1059068: fixed in svt-av1 2.0.0+dfsg-1 has caused the Debian Bug report #1059068, regarding apt: fails to resolve dependencies 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.) -- 1059068: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059068 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: apt Version: 2.7.7 Severity: normal I'm currently upgrading a stable machine to unstable (except some buggy packages), which is mostly done, but apt fails to resolve dependencies in order to upgrade vlc (aptitude is worse): qaa:~> apt install -s vlc [...] The following packages have unmet dependencies: vlc-plugin-base : Depends: libavcodec60 (>= 7:6.0) Depends: libavformat60 (>= 7:6.0) vlc-plugin-video-output : Depends: libavcodec60 (>= 7:6.0) E: Unable to correct problems, you have held broken packages. Why doesn't it try to install these packages, then? For instance, just adding libavcodec60 works: qaa:~> apt install -s vlc libavcodec60 [...] The following packages were automatically installed and are no longer required: libavutil57 libcodec2-1.0 libdav1d6 libixml10 libnfs13 libplacebo208 libpostproc56 libsdl-image1.2 libsdl1.2debian libswscale6 libupnp13 libvpx7 Use 'apt autoremove' to remove them. The following additional packages will be installed: cmus cmus-plugin-ffmpeg gir1.2-javascriptcoregtk-4.1 gir1.2-webkit2-4.1 gstreamer1.0-libav libasound2-plugins libavfilter9 libavformat60 libavif16 libchromaprint1 libcodec2-1.2 libfreerdp-server2-2 libfreerdp2-2 libgd3 libixml11 libjavascriptcoregtk-4.0-18 libjavascriptcoregtk-4.1-0 libjavascriptcoregtk-6.0-1 libplacebo338 libpostproc57 libsvtav1enc1d1 libswscale7 libupnp17 libvlc-bin libvlc5 libvlccore9 libwebkit2gtk-4.0-37 libwebkit2gtk-4.1-0 libwebkitgtk-6.0-4 libwinpr2-2 vlc-bin vlc-data vlc-l10n vlc-plugin-access-extra vlc-plugin-base vlc-plugin-notify vlc-plugin-qt vlc-plugin-samba vlc-plugin-skins2 vlc-plugin-video-output vlc-plugin-video-splitter vlc-plugin-visualization Suggested packages: libcuda1 libnvcuvid1 libnvidia-encode1 freerdp2-x11 libgd-tools gstreamer1.0-alsa vlc-plugin-fluidsynth vlc-plugin-jack vlc-plugin-pipewire vlc-plugin-svg libdvdcss2 The following packages will be REMOVED: libavcodec59 libavfilter8 libavformat59 libavif15 libsvtav1enc1 The following NEW packages will be installed: libavcodec60 libavfilter9 libavformat60 libavif16 libcodec2-1.2 libixml11 libplacebo338 libpostproc57 libsvtav1enc1d1 libswscale7 libupnp17 The following packages will be upgraded: cmus cmus-plugin-ffmpeg gir1.2-javascriptcoregtk-4.1 gir1.2-webkit2-4.1 gstreamer1.0-libav libasound2-plugins libchromaprint1 libfreerdp-server2-2 libfreerdp2-2 libgd3 libjavascriptcoregtk-4.0-18 libjavascriptcoregtk-4.1-0 libjavascriptcoregtk-6.0-1 libvlc-bin libvlc5 libvlccore9 libwebkit2gtk-4.0-37 libwebkit2gtk-4.1-0 libwebkitgtk-6.0-4 libwinpr2-2 vlc vlc-bin vlc-data vlc-l10n vlc-plugin-access-extra vlc-plugin-base vlc-plugin-notify vlc-plugin-qt vlc-plugin-samba vlc-plugin-skins2 vlc-plugin-video-output vlc-plugin-video-splitter vlc-plugin-visualization 33 upgraded, 11 newly installed, 5 to remove and 61 not upgraded. [...] -- Package-specific info: -- apt-config dump -- APT ""; APT::Architecture "amd64"; APT::Build-Essential ""; APT::Build-Essential:: "build-essential"; APT::Install-Recommends "1"; APT::Install-Suggests "0"; APT::Sandbox ""; APT::Sandbox::User "_apt"; APT::Authentication ""; APT::Authentication::TrustCDROM "true"; APT::NeverAutoRemove ""; APT::NeverAutoRemove:: "^firmware-linux.*"; APT::NeverAutoRemove:: "^linux-firmware$"; APT::NeverAutoRemove:: "^linux-image-[a-z0-9]*$"; APT::NeverAutoRemove:: "^linux-image-[a-z0-9]*-[a-z0-9]*$"; APT::VersionedKernelPackages ""; APT::VersionedKernelPackages:: "linux-.*"; APT::VersionedKernelPackages:: "kfreebsd-.*"; APT::VersionedKernelPackages:: "gnumach-.*"; APT::VersionedKernelPackages:: ".*-modules"; APT::VersionedKernelPackages:: ".*-kernel"; APT::Never-MarkAuto-Sections ""; APT::Never-MarkAuto-Sections:: "metapackages"; APT::Never-MarkAuto-Sections:: "tasks"; APT::Move-Autobit-Sections ""; APT::Move-Autobit-Sections:: "oldlibs"; APT::AutoRemove ""; A
Bug#1066644: marked as done (pd-hexloader: FTBFS: hexloader.c:608:5: error: implicit declaration of function ‘error’; did you mean ‘perror’? [-Werror=implicit-function-declaration])
Your message dated Sat, 23 Mar 2024 15:51:13 +0100
with message-id
and subject line pd-hexloader: FTBFS: hexloader.c:608:5: error: implicit
declaration of function ‘error’;
has caused the Debian Bug report #1066644,
regarding pd-hexloader: FTBFS: hexloader.c:608:5: error: implicit declaration
of function ‘error’; did you mean ‘perror’?
[-Werror=implicit-function-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.)
--
1066644: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066644
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pd-hexloader
Version: 1.7-6
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
This is most likely caused by a change in dpkg 1.22.6, that enabled
-Werror=implicit-function-declaration. For more information, see
https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration
Relevant part (hopefully):
> cc -I"/usr/include/pd" -DPD -DVERSION='"v1.7"' -fPIC -Wdate-time
> -D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration
> -ffile-prefix-map=/<>=. -fstack-protector-strong
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection
> -O6 -funroll-loops -fomit-frame-pointer -o "hexloader.o" -c "hexloader.c"
> hexloader.c: In function ‘hexloader_normalize’:
> hexloader.c:427:11: warning: return discards ‘const’ qualifier from pointer
> target type [-Wdiscarded-qualifiers]
> 427 | return s->s_name;
> | ~^~~~
> hexloader.c: In function ‘hexloader_fsnormalize’:
> hexloader.c:478:11: warning: return discards ‘const’ qualifier from pointer
> target type [-Wdiscarded-qualifiers]
> 478 | return s->s_name;
> | ~^~~~
> hexloader.c: In function ‘hexloader_deslashify’:
> hexloader.c:492:32: warning: passing argument 2 of ‘filelist_add’ discards
> ‘const’ qualifier from pointer target type [-Wdiscarded-qualifiers]
> 492 | result=filelist_add(result, s->s_name, 0);
> | ~^~~~
> hexloader.c:320:55: note: expected ‘char *’ but argument is of type ‘const
> char *’
> 320 | static filelist_t*filelist_add(filelist_t*files, char*name,
> namelist_t*setupfun) {
> | ~^~~~
> hexloader.c: In function ‘hexloader_getaltsetups’:
> hexloader.c:534:30: warning: passing argument 2 of ‘namelist_add’ discards
> ‘const’ qualifier from pointer target type [-Wdiscarded-qualifiers]
> 534 | names=namelist_add(names, s->s_name);
> | ~^~~~
> hexloader.c:243:55: note: expected ‘char *’ but argument is of type ‘const
> char *’
> 243 | static namelist_t*namelist_add(namelist_t*names, char*name) {
> | ~^~~~
> hexloader.c:537:30: warning: passing argument 2 of ‘namelist_add’ discards
> ‘const’ qualifier from pointer target type [-Wdiscarded-qualifiers]
> 537 | names=namelist_add(names, s->s_name);
> | ~^~~~
> hexloader.c:243:55: note: expected ‘char *’ but argument is of type ‘const
> char *’
> 243 | static namelist_t*namelist_add(namelist_t*names, char*name) {
> | ~^~~~
> hexloader.c: In function ‘hexloader_doload’:
> hexloader.c:608:5: error: implicit declaration of function ‘error’; did you
> mean ‘perror’? [-Werror=implicit-function-declaration]
> 608 | error("alas! somebody (you?) has compiled [hexloader] without
> support for loading externals...how should i load?");
> | ^
> | perror
> hexloader.c: In function ‘hexloader_setup’:
> hexloader.c:915:24: warning: macro "__DATE__" might prevent reproducible
> builds [-Wdate-time]
> 915 | post("\tcompiled on "__DATE__" at "__TIME__ " ");
> |^~~~
> hexloader.c:915:38: warning: macro "__TIME__" might prevent reproducible
> builds [-Wdate-time]
> 915 | post("\tcompiled on "__DATE__" at "__TIME__ " ");
> | ^~~~
Bug#1065781: marked as done (libmpeg3: FTBFS on arm{el,hf}: audio/synthesizers.c:36:9: error: implicit declaration of function ‘mpeg3audio_dct64’; did you mean ‘mpeg3audio_dopcm’? [-Werror=implicit-fu
Your message dated Sat, 23 Mar 2024 00:58:04 +
with message-id
and subject line Bug#1065781: fixed in libmpeg3 1.8.dfsg-6
has caused the Debian Bug report #1065781,
regarding libmpeg3: FTBFS on arm{el,hf}: audio/synthesizers.c:36:9: error:
implicit declaration of function ‘mpeg3audio_dct64’; did you mean
‘mpeg3audio_dopcm’? [-Werror=implicit-function-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.)
--
1065781: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065781
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libmpeg3
Version: 1.8.dfsg-5
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org
https://buildd.debian.org/status/fetch.php?pkg=libmpeg3=armhf=1.8.dfsg-5=1709535029=0
cc -c -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time
-D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration
-ffile-prefix-map=/<>=. -fstack-protector-strong
-fstack-clash-protection -Wformat -Werror=format-security -Wall -Wextra
-Wno-unused-function -W -O2 -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE
-D_LARGEFILE64_SOURCE -I. -I/usr/include/a52dec -g -fPIC -D_REENTRANT
audio/tables.c -o armv8l/audio/tables.o
audio/synthesizers.c: In function ‘mpeg3audio_synth_stereo’:
audio/synthesizers.c:36:9: error: implicit declaration of function
‘mpeg3audio_dct64’; did you mean ‘mpeg3audio_dopcm’?
[-Werror=implicit-function-declaration]
36 | mpeg3audio_dct64(buf[1] + ((audio->bo + 1) & 0xf), buf[0] +
audio->bo, bandPtr);
| ^~~~
| mpeg3audio_dopcm
Cheers
--
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: libmpeg3
Source-Version: 1.8.dfsg-6
Done: IOhannes m zmölnig (Debian/GNU)
We believe that the bug you reported is fixed in the latest version of
libmpeg3, 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 1065...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
IOhannes m zmölnig (Debian/GNU) (supplier of updated
libmpeg3 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: Fri, 22 Mar 2024 23:03:43 +0100
Source: libmpeg3
Architecture: source
Version: 1.8.dfsg-6
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers
Changed-By: IOhannes m zmölnig (Debian/GNU)
Closes: 1065781
Changes:
libmpeg3 (1.8.dfsg-6) unstable; urgency=medium
.
* Add more missing prototypes (Closes: #1065781)
* Apply 'wrap-and-sort -ast'
Checksums-Sha1:
6c719450f50b8178ce0b039b5a26b1e3bd687315 2319 libmpeg3_1.8.dfsg-6.dsc
09b0b6319787f0c60666e2926652c2af998a51ce 18096
libmpeg3_1.8.dfsg-6.debian.tar.xz
Checksums-Sha256:
8251324e8349c4e19a0d9de002556d01a68a9e2a6cfb9da6c4d540c97d208c75 2319
libmpeg3_1.8.dfsg-6.dsc
42b846b27fe97ba7b1ea84754d097da5526b8ff4705c7c87984e5d33f8642703 18096
libmpeg3_1.8.dfsg-6.debian.tar.xz
Files:
6504a3dc28033413119d338a35f7cb3a 2319 libs optional libmpeg3_1.8.dfsg-6.dsc
286efb8ef00919c17eaaa3804304caee 18096 libs optional
libmpeg3_1.8.dfsg-6.debian.tar.xz
-BEGIN PGP SIGNATURE-
iQJKBAEBCAA0FiEEdAXnRVdICXNIABVttlAZxH96NvgFAmX+BOwWHGZvcnVtQHVt
bGFldXRlLm11ci5hdAAKCRC2UBnEf3o2+DqKD/9BWDZXUPDOcLenY9axpWTPLugu
pOkW7iW4HWR03Lo6v0JxuoqzGGWGjGUzypsxdjDX2tmZHuD5+nq2Q7SnO9HFSpDr
B5TtZUjskJ7wAx3CYzDqfSV3dOA+TURY5kfnCw/Bu6WjXFZ9YKPsSAiwmKCirDfu
ELMBrKeuBWsmQ+e35aFQ2bs893VXm6Aj1r+VuRNXa+LetizAb9x2pF7lNZFq8cZv
710Vqd3KBUBC4FGBabY7ul7Bc4/mzxbHRSabVYc1hIKmrBtkliKiwpwUecAIkT50
+QyvIqrMjBfNjDGjH/SMv9o/5LkS6UjyeqVycW91Z9pk+ZwtzDpjFJpjCUpnLTbF
Q7pw05cRyGpwpnmfjE/Qo1RLcL2ju/YVnII2qZVvO+tChLjfpf5hQEd97ASLzOEP
0TRPyEP8huFNf8hft+2kfn+MyLmte/p5USOodfxoDr3XH1PuhVl0u3xpwToqBWiO
C6YqA2+EgojGzwApZQbzLdNuaixFAz+KAFcU+YldRgQKk+mGWNVUea7/xiueDVE+
VeB0tanoHGTRr1eSn6FsIwjL0gJR80HfZKyYNuLyD0Z9Jm+8bN5E7LDbqaPs4Isq
mIRUyCuacqy+77f72/NZkHjhcTOqRKluQ4Nyzpa+RczFhyZ1ceuSwNDPdXJB+3kj
FtAy3Z4YPl5KXS9ZAg==
=pTuZ
-END PGP SIGNATURE-
pgprhs86zT7AL.pgp
Description: PGP signature
--- End Message ---
Bug#1066233: marked as done (libmpeg3: FTBFS: audio/synthesizers.c:36:9: error: implicit declaration of function ‘mpeg3audio_dct64’; did you mean ‘mpeg3audio_dopcm’? [-Werror=implicit-function-declara
Your message dated Sat, 23 Mar 2024 00:58:04 + with message-id and subject line Bug#1065781: fixed in libmpeg3 1.8.dfsg-6 has caused the Debian Bug report #1065781, regarding libmpeg3: FTBFS: audio/synthesizers.c:36:9: error: implicit declaration of function ‘mpeg3audio_dct64’; did you mean ‘mpeg3audio_dopcm’? [-Werror=implicit-function-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.) -- 1065781: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065781 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libmpeg3 Version: 1.8.dfsg-5 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This is most likely caused by a change in dpkg 1.22.6, that enabled -Werror=implicit-function-declaration. For more information, see https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration Relevant part (hopefully): > cc -c -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 > -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. > -fstack-protector-strong -fstack-clash-protection -Wformat > -Werror=format-security -fcf-protection -Wall -Wextra -Wno-unused-function -W > -O2 -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -I. > -I/usr/include/a52dec -g -fPIC -D_REENTRANT audio/tables.c -o > x86_64/audio/tables.o > audio/synthesizers.c: In function ‘mpeg3audio_synth_stereo’: > audio/synthesizers.c:36:9: error: implicit declaration of function > ‘mpeg3audio_dct64’; did you mean ‘mpeg3audio_dopcm’? > [-Werror=implicit-function-declaration] >36 | mpeg3audio_dct64(buf[1] + ((audio->bo + 1) & 0xf), buf[0] + > audio->bo, bandPtr); > | ^~~~ > | mpeg3audio_dopcm > audio/layer2.c: In function ‘step_two’: > audio/layer2.c:283:20: warning: suggest parentheses around assignment used as > truth value [-Wparentheses] > 283 | if(ba = *bita++) > |^~ > audio/layer2.c:369:5: warning: this ‘for’ clause does not guard... > [-Wmisleading-indentation] > 369 | for(i = sblimit; i < SBLIMIT; i++) > | ^~~ > audio/layer2.c:373:9: note: ...this statement, but the latter is misleadingly > indented as if it were guarded by the ‘for’ > 373 | return result; > | ^~ > audio/layer2.c:276:19: warning: unused variable ‘test’ [-Wunused-variable] > 276 | int d1, step, test; > | ^~~~ > audio/layer2.c: In function ‘mpeg3audio_dolayer2’: > audio/layer2.c:393:42: warning: pointer targets in passing argument 2 of > ‘mpeg3bits_use_ptr’ differ in signedness [-Wpointer-sign] > 393 | mpeg3bits_use_ptr(audio->stream, frame); > | ^ > | | > | char * > In file included from audio/layer2.c:8: > ./mpeg3protos.h:482:60: note: expected ‘unsigned char *’ but argument is of > type ‘char *’ > 482 | int mpeg3bits_use_ptr(mpeg3_bits_t* stream, unsigned char *buffer); > | ~~~^~ > audio/layer2.c:378:13: warning: unused parameter ‘frame_size’ > [-Wunused-parameter] > 378 | int frame_size, > | ^~ > audio/pcm.c: In function ‘mpeg3audio_dopcm’: > audio/pcm.c:71:64: warning: pointer targets in initialization of ‘unsigned > char *’ from ‘char *’ differ in signedness [-Wpointer-sign] >71 | unsigned char *input = frame + > |^ > audio/layer3.c: In function ‘get_scale_factors_1’: > audio/layer3.c:53:21: warning: unused parameter ‘ch’ [-Wunused-parameter] >53 | int ch, > | ^~ > audio/layer3.c:54:21: warning: unused parameter ‘gr’ [-Wunused-parameter] >54 | int gr) > | ^~ > audio/layer3.c: In function ‘dequantize_sample’: > audio/layer3.c:226:19: warning: comparison of integer expressions of > different signedness: ‘int’ and ‘long unsigned int’ [-W
Bug#1066566: marked as done (elektroid: FTBFS: editor.c:1166:3: error: implicit declaration of function ‘g_unlink’; did you mean ‘unlink’? [-Werror=implicit-function-declaration])
Your message dated Fri, 22 Mar 2024 23:13:07 + with message-id and subject line Bug#1066566: fixed in elektroid 3.0.1-2 has caused the Debian Bug report #1066566, regarding elektroid: FTBFS: editor.c:1166:3: error: implicit declaration of function ‘g_unlink’; did you mean ‘unlink’? [-Werror=implicit-function-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.) -- 1066566: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066566 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: elektroid Version: 3.0.1-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This is most likely caused by a change in dpkg 1.22.6, that enabled -Werror=implicit-function-declaration. For more information, see https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration Relevant part (hopefully): > gcc -DHAVE_CONFIG_H -I. -I.. -Wall -O3 -DDATADIR='"/usr/share/elektroid"' > -DLOCALEDIR='"/usr/share/locale"' -Wdate-time -D_FORTIFY_SOURCE=2 -I../src > `/usr/bin/pkg-config --cflags alsa glib-2.0 zlib json-glib-1.0 libzip` > -I/usr/include/opus -I/usr/include/x86_64-linux-gnu -D_GNU_SOURCE -g -O2 > -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. > -fstack-protector-strong -fstack-clash-protection -Wformat > -Werror=format-security -fcf-protection -c -o elektroid_cli-connector.o `test > -f 'connector.c' || echo './'`connector.c > editor.c: In function ‘editor_save_to_remote’: > editor.c:1166:3: error: implicit declaration of function ‘g_unlink’; did you > mean ‘unlink’? [-Werror=implicit-function-declaration] > 1166 | g_unlink (tmp_file); > | ^~~~ > | unlink > gcc -DHAVE_CONFIG_H -I. -I.. -Wall -O3 -DDATADIR='"/usr/share/elektroid"' > -DLOCALEDIR='"/usr/share/locale"' -Wdate-time -D_FORTIFY_SOURCE=2 -I../src > `/usr/bin/pkg-config --cflags alsa glib-2.0 zlib json-glib-1.0 libzip` > -I/usr/include/opus -I/usr/include/x86_64-linux-gnu -D_GNU_SOURCE -g -O2 > -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. > -fstack-protector-strong -fstack-clash-protection -Wformat > -Werror=format-security -fcf-protection -c -o elektroid_cli-sample.o `test -f > 'sample.c' || echo './'`sample.c > gcc -DHAVE_CONFIG_H -I. -I.. -Wall -O3 -DDATADIR='"/usr/share/elektroid"' > -DLOCALEDIR='"/usr/share/locale"' -Wdate-time -D_FORTIFY_SOURCE=2 -I../src > `/usr/bin/pkg-config --cflags alsa glib-2.0 zlib json-glib-1.0 libzip` > -I/usr/include/opus -I/usr/include/x86_64-linux-gnu -D_GNU_SOURCE -g -O2 > -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. > -fstack-protector-strong -fstack-clash-protection -Wformat > -Werror=format-security -fcf-protection -c -o elektroid_cli-utils.o `test -f > 'utils.c' || echo './'`utils.c > gcc -DHAVE_CONFIG_H -I. -I.. -Wall -O3 -DDATADIR='"/usr/share/elektroid"' > -DLOCALEDIR='"/usr/share/locale"' -Wdate-time -D_FORTIFY_SOURCE=2 -I../src > `/usr/bin/pkg-config --cflags alsa glib-2.0 zlib json-glib-1.0 libzip` > -I/usr/include/opus -I/usr/include/x86_64-linux-gnu -D_GNU_SOURCE -g -O2 > -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. > -fstack-protector-strong -fstack-clash-protection -Wformat > -Werror=format-security -fcf-protection -c -o elektroid_cli-backend.o `test > -f 'backend.c' || echo './'`backend.c > gcc -DHAVE_CONFIG_H -I. -I.. -Wall -O3 -DDATADIR='"/usr/share/elektroid"' > -DLOCALEDIR='"/usr/share/locale"' -Wdate-time -D_FORTIFY_SOURCE=2 -I../src > `/usr/bin/pkg-config --cflags alsa glib-2.0 zlib json-glib-1.0 libzip` > -I/usr/include/opus -I/usr/include/x86_64-linux-gnu -D_GNU_SOURCE -g -O2 > -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. > -fstack-protector-strong -fstack-clash-protection -Wformat > -Werror=format-security -fcf-protection -c -o elektroid_cli-backend_alsa.o > `test -f 'backend_alsa.c' || echo './'`backend_alsa.c > gcc -DHAVE_CONFIG_H -I. -I.. -Wall -O3 -DDATADIR='"/usr/share/elektroid"' > -DLOCALEDIR='"/usr/share/locale"' -Wdate-time -D_FORTIFY_SOURCE=2 -I../src > `/usr/bin/pkg-config --cflags alsa glib-2.0 zlib json-g
Processed: unarchiving 1061899, severity of 1061899 is important, user release.debian....@packages.debian.org ...
ux]
zfs-linux: NMU diff for 64-bit time_t transition
Unarchived Bug 1063888
> severity 1063888 important
Bug #1063888 {Done: Steve Langasek } [src:zfs-linux]
zfs-linux: NMU diff for 64-bit time_t transition
Severity set to 'important' from 'serious'
> usertags 1063888 time-t-downgrade
Usertags were: time-t-downgrade.
Usertags are now: time-t-downgrade.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1061899: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061899
1061928: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061928
1062051: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062051
1062184: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062184
1062277: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062277
1062291: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062291
1062333: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062333
1062632: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062632
1062865: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062865
1063105: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063105
1063140: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063140
1063888: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063888
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: jackd2: patch to fix ftbfs on m68k; jack{1,2}: unneeded libffado-dev B-D on some arches
Processing control commands:
> affects -1 src:jack-audio-connection-kit
Bug #1067447 [src:jackd2] jackd2: patch to fix ftbfs on m68k; jack{1,2}:
unneeded libffado-dev B-D on some arches
Added indication that 1067447 affects src:jack-audio-connection-kit
--
1067447: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067447
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1065957: marked as done (sndobj: Please drop dependencies on python3-distutils)
Your message dated Wed, 20 Mar 2024 13:22:44 + with message-id and subject line Bug#1065957: fixed in sndobj 2.6.7+ds1-4 has caused the Debian Bug report #1065957, regarding sndobj: Please drop dependencies on python3-distutils 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.) -- 1065957: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065957 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: sndobj Version: 2.6.7+ds1-3 Severity: important Tags: ftbfs User: debian-pyt...@lists.debian.org Usertags: python3.12 Hi Maintainer This package has dependencies, build-dependencies and/or autopkgtest dependencies on python3-distutils. The python3-distutils binary package will soon be dropped from python3-stdlib-extensions. In fact, there is no module for Python 3.12 in python3-distutils, so these dependencies may already be unnecessary. Regards Graham --- End Message --- --- Begin Message --- Source: sndobj Source-Version: 2.6.7+ds1-4 Done: Benjamin Drung We believe that the bug you reported is fixed in the latest version of sndobj, 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 1065...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Benjamin Drung (supplier of updated sndobj 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, 20 Mar 2024 13:27:03 +0100 Source: sndobj Built-For-Profiles: noudeb Architecture: source Version: 2.6.7+ds1-4 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers Changed-By: Benjamin Drung Closes: 1065957 Changes: sndobj (2.6.7+ds1-4) unstable; urgency=medium . * Team upload. * Replace deprecated distutils Python module (Closes: #1065957) Checksums-Sha1: 84f0d9e872627dabad4bc1998841457df3b6bcfb 2102 sndobj_2.6.7+ds1-4.dsc 0df1964371a4b09b550cb29e78647b712bf06c6c 12820 sndobj_2.6.7+ds1-4.debian.tar.xz 1ea4954b7de3b350928d9d56287a7760314948bb 7515 sndobj_2.6.7+ds1-4_source.buildinfo Checksums-Sha256: 01e869eef59a20a283f8da12e6253d6fe0431e0617558fb86b18908692d9d05c 2102 sndobj_2.6.7+ds1-4.dsc 6e92b9aed99258716adcd2df58a1592181d6724377b644a21ea8d62035995566 12820 sndobj_2.6.7+ds1-4.debian.tar.xz c010214483ab53371809621e307f98b6388249e4a12e8ba5177ba77cf8303ead 7515 sndobj_2.6.7+ds1-4_source.buildinfo Files: a372e975bb5f679c80ecef71c0991beb 2102 sound optional sndobj_2.6.7+ds1-4.dsc ebdf0b24dbd41ba669e4965c3896ddcb 12820 sound optional sndobj_2.6.7+ds1-4.debian.tar.xz 09a4b3ddee7d0d7e36d556982692d496 7515 sound optional sndobj_2.6.7+ds1-4_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEpi0s+9ULm1vzYNVLFZ61xO/Id0wFAmX61kwACgkQFZ61xO/I d0wPaxAAjvnKVVdrBmA8kp/vtbzqZaSSOhKXUbx8QGVeRWWd88pNwOA1r7p/ah1U FTpEC5blYjWIRpEOIVgXcSRsYDH9FZIPSK3J75TBcfT3s6YvBZE0UAoTsOiTnKFL RyQos/K1hKhVIMQtE7gXXFmafnwsaJ3RV+AwyDAWkym1NwsNmHHVTM7CLwVoquvj eKm+NxZPnBP/I68wEU4hMAs1wP2fNXim67K06ACdUkh4/Mtq+ZK12z6j56jNkrsc ZmRxCJ8ZAZTKsmS0XfTZFRoQOdY1K7jwtjUtYoP9wqz89COCpCbmLoW9cXrdf0Aq Z/t6wDeFbwmK/5xznA4v2jcnLRmmBGz0Oh8eA5/9xb22v2BEzaowxm98kfarw7Tj C+MRDkZ2CbQK8p7igxAYfHPqOtZdv/m/XKnjONmkxexFVqpfCDbA+dNwVcN0ed1c zvcVB8IdK4/UP9biMD4BY4VuTi+GEsQVpnTjAwqhwlquA5j5V2IR/tTDF1SuQ/RU rdujirpFR0FFIojyH7H8dqnvGMTg7Vx1kBLMdWj0LdTKW4ZEfg49zxJuKxXqWQoZ 8mMRHt3VTqROTyHmgFEdQkQWhfU12LO3FOGKEVNH0VzvOG2QrmvWNHTqUrQFIaxk iicDUsM6Hhmo4iUeDX+By+HhbwpsUd1D75Yp5AERoICZ+iwRt+4= =ldmc -END PGP SIGNATURE- pgpz8mDFi9Ct0.pgp Description: PGP signature --- End Message ---
Processed: Bug#1065957 marked as pending in sndobj
Processing control commands: > tag -1 pending Bug #1065957 [src:sndobj] sndobj: Please drop dependencies on python3-distutils Added tag(s) pending. -- 1065957: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065957 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1056989: marked as done (libaacs: build aacs_info)
Your message dated Tue, 19 Mar 2024 19:00:14 + with message-id and subject line Bug#1056989: fixed in libaacs 0.11.1-3 has caused the Debian Bug report #1056989, regarding libaacs: build aacs_info 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.) -- 1056989: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056989 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libaacs Version: 0.11.1-2 Severity: wishlist Hey. Upstream contains the aacs_info program at: src/examples/aacs_info.c would it be possible to build and package that (e.g. as libaacs-tools or so), too? Thanks, Chris. --- End Message --- --- Begin Message --- Source: libaacs Source-Version: 0.11.1-3 Done: Christoph Anton Mitterer We believe that the bug you reported is fixed in the latest version of libaacs, 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 1056...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Christoph Anton Mitterer (supplier of updated libaacs 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, 17 Jan 2024 05:45:47 +0100 Source: libaacs Binary: libaacs-bin libaacs-bin-dbgsym libaacs-dev libaacs0 libaacs0-dbgsym Architecture: source amd64 Version: 0.11.1-3 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers Changed-By: Christoph Anton Mitterer Description: libaacs-bin - free-and-libre implementation of AACS (tools) libaacs-dev - free-and-libre implementation of AACS (development files) libaacs0 - free-and-libre implementation of AACS Closes: 1056989 Changes: libaacs (0.11.1-3) unstable; urgency=medium . * Team upload. * Package aacs_info in a new libaacs-bin package. (Closes: #1056989) Checksums-Sha1: 24d5a16f1f538ddb7646b5c1bcdf1298a9244604 2105 libaacs_0.11.1-3.dsc a1790329647d56ae7f3db1bc2f6e488f3426d591 4780 libaacs_0.11.1-3.debian.tar.xz faf943c6e7495692a127e797dd22a6dcf9fd0fef 7380 libaacs-bin-dbgsym_0.11.1-3_amd64.deb 6f78f996c17faf0d6e6f32e632cd03fbda129abc 7912 libaacs-bin_0.11.1-3_amd64.deb 785ea19aa0f20c3c79df6b01f4b3fdb295ebde6d 7328 libaacs-dev_0.11.1-3_amd64.deb 02ebaa2670c90f1eaef193c6c41aa0698731c11d 156156 libaacs0-dbgsym_0.11.1-3_amd64.deb 79d4d8b97816d41b695333bfb4e349f351b5051c 57656 libaacs0_0.11.1-3_amd64.deb 43470ebc3767c47b5fb98e6ef20bddefcde7d139 7350 libaacs_0.11.1-3_amd64.buildinfo Checksums-Sha256: 55c9db83d75a8511eb06e30a3d418a7ab1faf6b013c263519a64f70be14ab84c 2105 libaacs_0.11.1-3.dsc 063d81ba9206dc08f5035ba3b3753cd1976932139556da5ad08dedab5778ff27 4780 libaacs_0.11.1-3.debian.tar.xz 6474ca2e0282879a7ff56ad06aada591464c30ad0eaf9db2dfa0537218a2f439 7380 libaacs-bin-dbgsym_0.11.1-3_amd64.deb 2646c49c813e4d2fc6e4643ef43b67a42c2c8559cda8d7636ba290a2c956e2ea 7912 libaacs-bin_0.11.1-3_amd64.deb b1863177ae07b1f91ea05b1775d78ad38538639438d06a990728e5ec392bc6e5 7328 libaacs-dev_0.11.1-3_amd64.deb b16c8c50276f40e3200b7afe2af02a9d900372459d7c13e992dd97ab2b9534dd 156156 libaacs0-dbgsym_0.11.1-3_amd64.deb 905b06233f0e4ed472462241607e6e8d1a94b7f82e055951a7f3b1f62de54190 57656 libaacs0_0.11.1-3_amd64.deb 538e05b2f8bd3277cebf5fb2227e0e5f3bd3e37d3b2de5060ce11580fb362f85 7350 libaacs_0.11.1-3_amd64.buildinfo Files: 6358eba1e971eea890ec228bc3b33289 2105 video optional libaacs_0.11.1-3.dsc e8c72f4625e482947081baac1b4512bf 4780 video optional libaacs_0.11.1-3.debian.tar.xz 995d7b9d041385c5f8285be4a077d45f 7380 debug optional libaacs-bin-dbgsym_0.11.1-3_amd64.deb da3b385497c26d1cbd4aec892b65efe5 7912 utils optional libaacs-bin_0.11.1-3_amd64.deb 1f9450396f641f0b805d7e7b36f2aa60 7328 libdevel optional libaacs-dev_0.11.1-3_amd64.deb c11da2d001629e53bb66517196d74576 156156 debug optional libaacs0-dbgsym_0.11.1-3_amd64.deb 082709b0199c129316f72c60518d122f 57656 libs optional libaacs0_0.11.1-3_amd64.deb d279497309e0112b0870d871756bcf70 7350 video optional libaacs_0.11.1-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEmjwHvQbeL0FugTpdYS7xYT4FD1QFAmWqcjUACgkQYS7xYT4F D1Qkdg/8DxDBNPFToG1NReirTK4taTrtrwP3B90WTBaHxaW3oZ3m/j+FWHtACiCb X1Nh2uTViqbaxIFawNezvzBBkcJfbd2Do1u420Ux6BVmxRD42gsy4tKrSOglin6F
Bug#1066577: marked as done (nanovg: FTBFS: ../src/nanovg_gl.h:341:17: error: implicit declaration of function ‘glBlendFuncSeparate’; did you mean ‘glnvg__blendFuncSeparate’? [-Werror=implicit-functio
Your message dated Tue, 19 Mar 2024 06:49:47 + with message-id and subject line Bug#1066577: fixed in nanovg 0.0~git20230826.f93799c+dfsg-2 has caused the Debian Bug report #1066577, regarding nanovg: FTBFS: ../src/nanovg_gl.h:341:17: error: implicit declaration of function ‘glBlendFuncSeparate’; did you mean ‘glnvg__blendFuncSeparate’? [-Werror=implicit-function-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.) -- 1066577: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066577 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: nanovg Version: 0.0~git20230826.f93799c+dfsg-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This is most likely caused by a change in dpkg 1.22.6, that enabled -Werror=implicit-function-declaration. For more information, see https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration Relevant part (hopefully): > make[1]: Entering directory '/<>/build' > Building nanovg (debug) > Creating obj/Debug/nanovg > nanovg.c > Linking nanovg > Building example_gl2 (debug) > Building example_gl3 (debug) > Building example_gl2_msaa (debug) > Building example_gl3_msaa (debug) > Building example_fbo (debug) > Building example_gles2 (debug) > Building example_gles3 (debug) > Creating obj/Debug/example_gl2 > Creating obj/Debug/example_gl3 > example_gl2.c > Creating obj/Debug/example_gl2_msaa > Creating obj/Debug/example_gl3_msaa > example_gl3.c > Creating obj/Debug/example_gles3 > Creating obj/Debug/example_fbo > Creating obj/Debug/example_gles2 > demo.c > example_gl2.c > example_gl3.c > example_gles3.c > example_gles2.c > example_fbo.c > In file included from ../example/example_fbo.c:29: > ../src/nanovg_gl.h: In function ‘glnvg__blendFuncSeparate’: > ../src/nanovg_gl.h:341:17: error: implicit declaration of function > ‘glBlendFuncSeparate’; did you mean ‘glnvg__blendFuncSeparate’? > [-Werror=implicit-function-declaration] > 341 | glBlendFuncSeparate(blend->srcRGB, blend->dstRGB, > blend->srcAlpha,blend->dstAlpha); > | ^~~ > | glnvg__blendFuncSeparate > ../src/nanovg_gl.h: In function ‘glnvg__dumpShaderError’: > ../src/nanovg_gl.h:404:9: error: implicit declaration of function > ‘glGetShaderInfoLog’ [-Werror=implicit-function-declaration] > 404 | glGetShaderInfoLog(shader, 512, , str); > | ^~ > ../example/demo.c: In function ‘drawParagraph’: > ../example/demo.c:874:21: warning: unused variable ‘boxText’ > [-Wunused-variable] > 874 | const char* boxText = "Testing\nsome multiline\ntext."; > | ^~~ > ../src/nanovg_gl.h: In function ‘glnvg__dumpProgramError’: > ../src/nanovg_gl.h:414:9: error: implicit declaration of function > ‘glGetProgramInfoLog’ [-Werror=implicit-function-declaration] > 414 | glGetProgramInfoLog(prog, 512, , str); > | ^~~ > ../src/nanovg_gl.h: In function ‘glnvg__createShader’: > ../src/nanovg_gl.h:441:16: error: implicit declaration of function > ‘glCreateProgram’ [-Werror=implicit-function-declaration] > 441 | prog = glCreateProgram(); > |^~~ > ../src/nanovg_gl.h:442:16: error: implicit declaration of function > ‘glCreateShader’; did you mean ‘glnvg__createShader’? > [-Werror=implicit-function-declaration] > 442 | vert = glCreateShader(GL_VERTEX_SHADER); > |^~ > |glnvg__createShader > ../src/nanovg_gl.h:445:9: error: implicit declaration of function > ‘glShaderSource’ [-Werror=implicit-function-declaration] > 445 | glShaderSource(vert, 3, str, 0); > | ^~ > ../src/nanovg_gl.h:449:9: error: implicit declaration of function > ‘glCompileShader’ [-Werror=implicit-function-declaration] > 449 | glCompileShader(vert); > | ^~~ > ../src/nanovg_gl.h:450:9: error: implicit declaration of function > ‘glGetShaderiv’; did you mean ‘
Bug#1066676: marked as done (pd-ext13: FTBFS: openpatch.c:61:5: error: implicit declaration of function ‘glob_evalfile’; did you mean ‘binbuf_evalfile’? [-Werror=implicit-function-declaration])
Your message dated Mon, 18 Mar 2024 17:38:22 +
with message-id
and subject line Bug#1066676: fixed in pd-ext13 0.17.1-9
has caused the Debian Bug report #1066676,
regarding pd-ext13: FTBFS: openpatch.c:61:5: error: implicit declaration of
function ‘glob_evalfile’; did you mean ‘binbuf_evalfile’?
[-Werror=implicit-function-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.)
--
1066676: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066676
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pd-ext13
Version: 0.17.1-8
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
This is most likely caused by a change in dpkg 1.22.6, that enabled
-Werror=implicit-function-declaration. For more information, see
https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration
Relevant part (hopefully):
> cc -DPD -I "/usr/include/pd" -DUNIX -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC
> -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration
> -ffile-prefix-map=/<>=. -fstack-protector-strong
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -o
> filesize.pd_linux.o -c filesize.c
> info: making send13.pd_linux.o in lib ext13
> openpatch.c: In function ‘openpatch_symbol’:
> openpatch.c:61:5: error: implicit declaration of function ‘glob_evalfile’;
> did you mean ‘binbuf_evalfile’? [-Werror=implicit-function-declaration]
>61 | glob_evalfile(0,gensym(filename),gensym(path));
> | ^
> | binbuf_evalfile
> cc -DPD -I "/usr/include/pd" -DUNIX -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC
> -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration
> -ffile-prefix-map=/<>=. -fstack-protector-strong
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -o
> send13.pd_linux.o -c send13.c
> info: making scramble~.pd_linux.o in lib ext13
> promiscous~.c: In function ‘promiscous_tilde_new’:
> promiscous~.c:147:50: warning: passing argument 1 of ‘setnic_promisc’
> discards ‘const’ qualifier from pointer target type [-Wdiscarded-qualifiers]
> 147 | if((x->sock = setnic_promisc(x->interface->s_name))<0){
> | ^~~~
> promiscous~.c:41:33: note: expected ‘char *’ but argument is of type ‘const
> char *’
>41 | static int setnic_promisc(char *nic_name){
> | ~~^~~~
> sfwrite13~.c: In function ‘sfwrite13_close’:
> sfwrite13~.c:142:11: warning: ignoring return value of ‘write’ declared with
> attribute ‘warn_unused_result’ [-Wunused-result]
> 142 | write(x->x_file,,sizeof(w));
> | ^
> cc1: some warnings being treated as errors
> make[1]: *** [/usr/share/pd-lib-builder//Makefile.pdlibbuilder:987:
> openpatch.pd_linux.o] Error 1
The full build log is available from:
http://qa-logs.debian.net/2024/03/13/pd-ext13_0.17.1-8_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240313;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240313=lu...@debian.org=1=1=1=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: pd-ext13
Source-Version: 0.17.1-9
Done: IOhannes m zmölnig (Debian/GNU)
We believe that the bug you reported is fixed in the latest version of
pd-ext13, 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 1066...@bugs.debian.org,
and the maintainer will reopen the bug report if appropri
Bug#1066607: marked as done (pd-pmpd: FTBFS: mass3D.c:465:17: error: implicit declaration of function ‘error’; did you mean ‘perror’? [-Werror=implicit-function-declaration])
Your message dated Mon, 18 Mar 2024 16:50:42 +
with message-id
and subject line Bug#1066607: fixed in pd-pmpd 0.13.1-1
has caused the Debian Bug report #1066607,
regarding pd-pmpd: FTBFS: mass3D.c:465:17: error: implicit declaration of
function ‘error’; did you mean ‘perror’? [-Werror=implicit-function-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.)
--
1066607: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066607
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pd-pmpd
Version: 0.9-9
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
This is most likely caused by a change in dpkg 1.22.6, that enabled
-Werror=implicit-function-declaration. For more information, see
https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration
Relevant part (hopefully):
> cc -DPD -I "/usr/include/pd" -DUNIX -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC
> -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration
> -ffile-prefix-map=/<>=. -fstack-protector-strong
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -o
> mass2D.pd_linux.o -c mass2D.c
> info: making tSphere3D.pd_linux.o in lib pmpd
> mass3D.c: In function ‘mass3D_inter_ambient’:
> mass3D.c:465:17: error: implicit declaration of function ‘error’; did you
> mean ‘perror’? [-Werror=implicit-function-declaration]
> 465 | error("bad ambient interraction message");
> | ^
> | perror
> mass2D.c: In function ‘mass2D_inter_ambient’:
> mass2D.c:342:17: error: implicit declaration of function ‘error’; did you
> mean ‘perror’? [-Werror=implicit-function-declaration]
> 342 | error("bad ambient interraction message");
> | ^
> | perror
> pmpd~.c: In function ‘pmpd_tilde_mass’:
> pmpd~.c:273:40: error: implicit declaration of function ‘error’; did you mean
> ‘perror’? [-Werror=implicit-function-declaration]
> 273 | if (x->nb_mass == nb_max_mass) error("to many mass");
> |^
> |perror
> cc -DPD -I "/usr/include/pd" -DUNIX -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC
> -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration
> -ffile-prefix-map=/<>=. -fstack-protector-strong
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -o
> tSphere3D.pd_linux.o -c tSphere3D.c
> info: making tCircle2D.pd_linux.o in lib pmpd
> cc -DPD -I "/usr/include/pd" -DUNIX -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC
> -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration
> -ffile-prefix-map=/<>=. -fstack-protector-strong
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -o
> tCircle2D.pd_linux.o -c tCircle2D.c
> info: making iCylinder3D.pd_linux.o in lib pmpd
> cc -DPD -I "/usr/include/pd" -DUNIX -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC
> -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration
> -ffile-prefix-map=/<>=. -fstack-protector-strong
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -o
> iCylinder3D.pd_linux.o -c iCylinder3D.c
> info: making tSquare2D.pd_linux.o in lib pmpd
> cc -DPD -I "/usr/include/pd" -DUNIX -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC
> -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration
> -ffile-prefix-map=/<>=. -fstack-protector-strong
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -o
> tSquare2D.pd_linux.o -c tSquare2D.c
> info: making tPlane3D.pd_linux.o in lib pmpd
> cc -DPD -I "/usr/include/pd" -DUNIX -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC
> -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration
> -ffile-prefix-map=/<>=. -fstack-protector-strong
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -o
> tPlane3D.pd_linux.o -c tPlane3D.c
> info: making iSeg2D.pd_linux.o in lib pmp
Bug#1060212: marked as done (pd-pmpd: Update to current version 0.12 and remove recommendation of package puredata-import)
Your message dated Mon, 18 Mar 2024 16:50:42 + with message-id and subject line Bug#1060212: fixed in pd-pmpd 0.13.1-1 has caused the Debian Bug report #1060212, regarding pd-pmpd: Update to current version 0.12 and remove recommendation of package puredata-import 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.) -- 1060212: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060212 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: pd-pmpd Version: 0.9-7 Severity: normal X-Debbugs-Cc: peterpar...@fastmail.com Dear Maintainer, * What led up to the situation? The current version of the pd-pmpd package on Debian stable is 0.9-7 while the upstream software is already at 0.12. pd-pmpd furthermore recommends puredata-import, which is deprectated, see discussion at https://lists.puredata.info/pipermail/pd-list//2024-01/132865.html -- System Information: Debian Release: 12.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable'), (500, 'oldstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.1.0-17-rt-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages pd-pmpd depends on: ii libc6 2.36-9+deb12u3 pn pd-libdir ii puredata-core [pd] 0.54.1+ds-2~bpo12+1 Versions of packages pd-pmpd recommends: pn pd-import pd-pmpd suggests no packages. --- End Message --- --- Begin Message --- Source: pd-pmpd Source-Version: 0.13.1-1 Done: IOhannes m zmölnig (Debian/GNU) We believe that the bug you reported is fixed in the latest version of pd-pmpd, 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 1060...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. IOhannes m zmölnig (Debian/GNU) (supplier of updated pd-pmpd 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: Mon, 18 Mar 2024 17:36:43 +0100 Source: pd-pmpd Architecture: source Version: 0.13.1-1 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers Changed-By: IOhannes m zmölnig (Debian/GNU) Closes: 1060212 1066607 Changes: pd-pmpd (0.13.1-1) unstable; urgency=medium . * New upstream version 0.13.1 (Closes: #1066607, #1060212) * Switch buildsystem to CMake + Drop pd-lib-builder patch + single/double-flavoured CMake builds * No longer Recommend "pd-import" (Closes: #1060212) * Add patch to fix typos * Add patch to honour dpkg-buildflags * Fix manual installation of renamed files * Add lintian-overrides for new-style 32bit externals * Add lintian-override about false-positive source-missing * Update upstream URLs + Update d/watch * Update copyright information + Update d/copyright + Exclude binary files from licensecheck + Re-generate d/copyright_hints Checksums-Sha1: 83cc683ed7d92b3fe7555d538b58169800dc4358 2164 pd-pmpd_0.13.1-1.dsc 662ed77663342bbee9c0b2e5b0ae8a7861274b5f 8315181 pd-pmpd_0.13.1.orig.tar.gz bbe38fd2de8dfb3ca85c440627f20f247ca4796f 6224 pd-pmpd_0.13.1-1.debian.tar.xz Checksums-Sha256: 6c5acfa43a019209dde7ad510493dda07655ef00fe9d7a9e8ba1f50c07c21b26 2164 pd-pmpd_0.13.1-1.dsc ec1a5123e3d263da4be02f16f1aa9890fab5b4b1fdb0432e57cb2694e01c543b 8315181 pd-pmpd_0.13.1.orig.tar.gz 604445f70ef02d5367a03b5c544c2d3c49daf189c5ef9a5eeb73393443cc5ccc 6224 pd-pmpd_0.13.1-1.debian.tar.xz Files: aa823fb1020b1bcf6c46995b4538069f 2164 sound optional pd-pmpd_0.13.1-1.dsc b14329665326f55025a6766a3173b5d8 8315181 sound optional pd-pmpd_0.13.1.orig.tar.gz 48944d8ee9d5af1352f3c091fcd01600 6224 sound optional pd-pmpd_0.13.1-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQJKBAEBCAA0FiEEdAXnRVdICXNIABVttlAZxH96NvgFAmX4bgYWHGZvcnVtQHVt bGFldXRlLm11ci5hdAAKCRC2UBnEf3o2+OkKD/0Wj6NiY4co9WdCZU9y4NaAgY1A nk0JbB2+PHDVYoQqs2k8SuLpAcpObDtqSoPPxsf1R6oi5B6A35VsK+LFe9frh9Ls FIztvKzsWUb+yWjXDKIFVkpjrOVQScNPZg46VyJS9xmU1kETAU3tq6
Bug#1066493: marked as done (pd-csound: FTBFS: csoundapi_tilde.c:774:7: error: implicit declaration of function ‘error’; did you mean ‘perror’? [-Werror=implicit-function-declaration])
Your message dated Mon, 18 Mar 2024 16:11:33 +
with message-id
and subject line Bug#1066493: fixed in pd-csound 2:1.01.0-6
has caused the Debian Bug report #1066493,
regarding pd-csound: FTBFS: csoundapi_tilde.c:774:7: error: implicit
declaration of function ‘error’; did you mean ‘perror’?
[-Werror=implicit-function-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.)
--
1066493: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066493
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pd-csound
Version: 2:1.01.0-5
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
This is most likely caused by a change in dpkg 1.22.6, that enabled
-Werror=implicit-function-declaration. For more information, see
https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration
Relevant part (hopefully):
> /usr/bin/cc -Dpdcsound_EXPORTS -I/usr/include/csound -g -O2
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=.
> -fstack-protector-strong -fstack-clash-protection -Wformat
> -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC
> -MD -MT CMakeFiles/pdcsound.dir/src/csoundapi_tilde.c.o -MF
> CMakeFiles/pdcsound.dir/src/csoundapi_tilde.c.o.d -o
> CMakeFiles/pdcsound.dir/src/csoundapi_tilde.c.o -c
> /<>/src/csoundapi_tilde.c
> /<>/src/csoundapi_tilde.c: In function ‘open_midi_callback’:
> /<>/src/csoundapi_tilde.c:774:7: error: implicit declaration of
> function ‘error’; did you mean ‘perror’?
> [-Werror=implicit-function-declaration]
> 774 | error("unable to allocate memory for midi queue");
> | ^
> | perror
> cc1: some warnings being treated as errors
> make[3]: *** [CMakeFiles/pdcsound.dir/build.make:79:
> CMakeFiles/pdcsound.dir/src/csoundapi_tilde.c.o] Error 1
The full build log is available from:
http://qa-logs.debian.net/2024/03/13/pd-csound_1.01.0-5_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240313;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240313=lu...@debian.org=1=1=1=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: pd-csound
Source-Version: 2:1.01.0-6
Done: IOhannes m zmölnig (Debian/GNU)
We believe that the bug you reported is fixed in the latest version of
pd-csound, 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 1066...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
IOhannes m zmölnig (Debian/GNU) (supplier of updated
pd-csound 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: Mon, 18 Mar 2024 16:46:16 +0100
Source: pd-csound
Architecture: source
Version: 2:1.01.0-6
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers
Changed-By: IOhannes m zmölnig (Debian/GNU)
Closes: 1066493
Changes:
pd-csound (2:1.01.0-6) unstable; urgency=medium
.
* Patch to replace error() with pd_error() (Closes: #1066493)
* Bump standards version to 4.6.2
Checksums-Sha1:
bcebc61829ebdfb49aadb7cf39a74668bb38a7c7 2139 pd-csound_1.01.0-6.dsc
5dbb29026e3c8f220324e55f3409fc1cf2f0136e 4228 pd-csound_1.01.0-6.debian.tar.xz
Checksums-Sha256:
3356384bc51ea8213de20afd5b678923e336d198057ef22b41f01d44f7797470 2139
pd-csound_1.01.0-6.dsc
dddf0ff9e17955e4d44659992885d65b67e58af1fa95a11f07de3cde0d2d5689 4228
pd-csoun
Processed: Bug#1066493 marked as pending in pd-csound
Processing control commands: > tag -1 pending Bug #1066493 [src:pd-csound] pd-csound: FTBFS: csoundapi_tilde.c:774:7: error: implicit declaration of function ‘error’; did you mean ‘perror’? [-Werror=implicit-function-declaration] Added tag(s) pending. -- 1066493: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066493 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1066192: marked as done (qm-dsp: FTBFS: hmm/hmm.c:703:15: error: implicit declaration of function ‘dgetrf_’ [-Werror=implicit-function-declaration])
Your message dated Mon, 18 Mar 2024 14:52:50 + with message-id and subject line Bug#1066192: fixed in qm-dsp 1.7.1-8 has caused the Debian Bug report #1066192, regarding qm-dsp: FTBFS: hmm/hmm.c:703:15: error: implicit declaration of function ‘dgetrf_’ [-Werror=implicit-function-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.) -- 1066192: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066192 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: qm-dsp Version: 1.7.1-7.1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This is most likely caused by a change in dpkg 1.22.6, that enabled -Werror=implicit-function-declaration. For more information, see https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration Relevant part (hopefully): > cc -g -O2 -Werror=implicit-function-declaration > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection > -DNDEBUG -O3 -fPIC -ffast-math -ftree-vectorize -DUSE_PTHREADS -I. > -Iext/kissfft -Iext/kissfft/tools -Dkiss_fft_scalar=double -Wdate-time > -D_FORTIFY_SOURCE=2 -c -o hmm/hmm.o hmm/hmm.c > hmm/hmm.c: In function ‘invert’: > hmm/hmm.c:703:15: error: implicit declaration of function ‘dgetrf_’ > [-Werror=implicit-function-declaration] > 703 | ret = dgetrf_(, , a, , ipiv, ); /* ret should > be zero, negative if cov is singular */ > | ^~~ > hmm/hmm.c:730:9: error: implicit declaration of function ‘dgetri_’ > [-Werror=implicit-function-declaration] > 730 | dgetri_(, a, , ipiv, , , ); > | ^~~ > g++ -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection > -fPIC -Wall -g -O2 -Werror=implicit-function-declaration > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection > -DNDEBUG -O3 -fPIC -ffast-math -ftree-vectorize -DUSE_PTHREADS -I. > -Iext/kissfft -Iext/kissfft/tools -Dkiss_fft_scalar=double -I. -Iext/kissfft > -Iext/kissfft/tools -Dkiss_fft_scalar=double -Wdate-time -D_FORTIFY_SOURCE=2 > -c -o maths/Correlation.o maths/Correlation.cpp > cc1plus: warning: ‘-Werror=’ argument ‘-Werror=implicit-function-declaration’ > is not valid for C++ > g++ -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection > -fPIC -Wall -g -O2 -Werror=implicit-function-declaration > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection > -DNDEBUG -O3 -fPIC -ffast-math -ftree-vectorize -DUSE_PTHREADS -I. > -Iext/kissfft -Iext/kissfft/tools -Dkiss_fft_scalar=double -I. -Iext/kissfft > -Iext/kissfft/tools -Dkiss_fft_scalar=double -Wdate-time -D_FORTIFY_SOURCE=2 > -c -o maths/CosineDistance.o maths/CosineDistance.cpp > cc1plus: warning: ‘-Werror=’ argument ‘-Werror=implicit-function-declaration’ > is not valid for C++ > g++ -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection > -fPIC -Wall -g -O2 -Werror=implicit-function-declaration > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection > -DNDEBUG -O3 -fPIC -ffast-math -ftree-vectorize -DUSE_PTHREADS -I. > -Iext/kissfft -Iext/kissfft/tools -Dkiss_fft_scalar=double -I. -Iext/kissfft > -Iext/kissfft/tools -Dkiss_fft_scalar=double -Wdate-time -D_FORTIFY_SOURCE=2 > -c -o maths/KLDivergence.o maths/KLDivergence.cpp > cc1plus: warning: ‘-Werror=’ argument ‘-Werror=implicit-function-declaration’ > is not valid for C++ > g++ -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection > -fPIC -Wall -g -O2 -Werror=implicit-function-declaration > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection > -DNDEBUG -O3 -fPIC -ffas
Bug#1066007: marked as done (qm-dsp: FTBFS on arm{el,hf}: hmm/hmm.c:703:15: error: implicit declaration of function ‘dgetrf_’ [-Werror=implicit-function-declaration])
Your message dated Mon, 18 Mar 2024 14:52:50 +
with message-id
and subject line Bug#1066007: fixed in qm-dsp 1.7.1-8
has caused the Debian Bug report #1066007,
regarding qm-dsp: FTBFS on arm{el,hf}: hmm/hmm.c:703:15: error: implicit
declaration of function ‘dgetrf_’ [-Werror=implicit-function-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.)
--
1066007: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066007
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: qm-dsp
Version: 1.7.1-7.1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org
https://buildd.debian.org/status/fetch.php?pkg=qm-dsp=armhf=1.7.1-7.1=1709536479=0
hmm/hmm.c: In function ‘invert’:
hmm/hmm.c:703:15: error: implicit declaration of function ‘dgetrf_’
[-Werror=implicit-function-declaration]
703 | ret = dgetrf_(, , a, , ipiv, ); /* ret should
be zero, negative if cov is singular */
| ^~~
hmm/hmm.c:730:9: error: implicit declaration of function ‘dgetri_’
[-Werror=implicit-function-declaration]
730 | dgetri_(, a, , ipiv, , , );
| ^~~
Cheers
--
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: qm-dsp
Source-Version: 1.7.1-8
Done: IOhannes m zmölnig (Debian/GNU)
We believe that the bug you reported is fixed in the latest version of
qm-dsp, 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 1066...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
IOhannes m zmölnig (Debian/GNU) (supplier of updated
qm-dsp 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: Mon, 18 Mar 2024 15:02:10 +0100
Source: qm-dsp
Architecture: source
Version: 1.7.1-8
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers
Changed-By: IOhannes m zmölnig (Debian/GNU)
Closes: 1066007 1066192
Changes:
qm-dsp (1.7.1-8) unstable; urgency=medium
.
* Update lapack patch to declare dgetr[fi]_()
(Closes: #1066007, #1066192)
* B-D on pkgconf (but fallback to pkg-config)
* Build and run upstream tests via autopktest
* Apply 'wrap-and-sort -ast'
Checksums-Sha1:
ec11fba62386e366e40009130bd028248fe3d8cf 2373 qm-dsp_1.7.1-8.dsc
743ffbb8e22ad4af181c53ae99c20d401535eb6c 7860 qm-dsp_1.7.1-8.debian.tar.xz
Checksums-Sha256:
fa2a7e0102217c2a63754315d31fe8461b2409efb5a4e94979eff01b4375adff 2373
qm-dsp_1.7.1-8.dsc
68cf17e37976fe32b06e2e69a2213a0b0c902b7c822941441ad2472b2061e6bd 7860
qm-dsp_1.7.1-8.debian.tar.xz
Files:
e4dc6f64e905280af736bce182039b62 2373 sound optional qm-dsp_1.7.1-8.dsc
205e54e474a98ec76eb49d59850554d7 7860 sound optional
qm-dsp_1.7.1-8.debian.tar.xz
-BEGIN PGP SIGNATURE-
iQJKBAEBCAA0FiEEdAXnRVdICXNIABVttlAZxH96NvgFAmX4SssWHGZvcnVtQHVt
bGFldXRlLm11ci5hdAAKCRC2UBnEf3o2+Ad4D/0UQpzEbYvjlWizHEJZmORMMbSH
vXymW22SAIsWACJlzu5c1labxA6nHc8bQ08PCTf3ashn+Hou2t6Qe4r9CeEHU6Oy
nsEDnqPjrdGnJlnu+A3tHugkBMSPw1DNd7sGzDpDRO76l4PRm+3FxF8dtAB4sd42
8On2AQZVMZJz9S9Uoxvx8kC/K1pdxiZ9lB8XKSjQl8+NMjdE6xXHveYObnJH7M+f
iA3d08PHWxnqGPpYDm8hd1AwVGbOLLFDjDHM0oDLDlrNMNA8mCv+dXkX422mcIuU
ABu4tKaX+HkcWbAHX/BtYfkNcTjVtMVlGR5Psi/7yi3WEQYHCygPd9DHH37NVNUB
g7BaRneSiyHw/sAu5Wqwb3d3mGHXdr1s4afoqQSKjthKERj6NP02c0lEGzKRB+sf
pBBcjIXxlCywkK01+mS9k25hj2fTCDaRCnXG6YdRwjB5sNAz0a//pG2gk+Xyi3BY
Gyzq3EMjFEafoxNNhFU7UgjAkw0oKNRV18dhGnk3IGO6lWGlUMyIuoDMTIVFDryG
NeBdHPy7Sm/nnaJ/aZG/NF55v3KrvRwADdX7T23h1viiC4pYrPMyOxlcCOtBe9W2
DaVJXICPOg4Joo8PpcWcxG0R1mQu2Ox+nTDvzD/p4E9TLjaw1VwZACT2bCzlgJHk
DwUI/Ll6YbhzlZM7TA==
=17H6
-END PGP SIGNATURE-
pgpZmBUOmf9vC.pgp
Description: PGP signature
--- End Message ---
Processed: Bug#1066192 marked as pending in qm-dsp
Processing control commands: > tag -1 pending Bug #1066192 [src:qm-dsp] qm-dsp: FTBFS: hmm/hmm.c:703:15: error: implicit declaration of function ‘dgetrf_’ [-Werror=implicit-function-declaration] Added tag(s) pending. -- 1066192: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066192 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#1066007 marked as pending in qm-dsp
Processing control commands:
> tag -1 pending
Bug #1066007 [src:qm-dsp] qm-dsp: FTBFS on arm{el,hf}: hmm/hmm.c:703:15: error:
implicit declaration of function ‘dgetrf_’
[-Werror=implicit-function-declaration]
Added tag(s) pending.
--
1066007: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066007
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1066591: marked as done (pd-mrpeach: FTBFS: slipenc/slipenc.c:92:9: error: implicit declaration of function ‘error’; did you mean ‘perror’? [-Werror=implicit-function-declaration])
Your message dated Mon, 18 Mar 2024 12:50:31 +
with message-id
and subject line Bug#1066591: fixed in pd-mrpeach 0.1~svn17672-5
has caused the Debian Bug report #1066591,
regarding pd-mrpeach: FTBFS: slipenc/slipenc.c:92:9: error: implicit
declaration of function ‘error’; did you mean ‘perror’?
[-Werror=implicit-function-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.)
--
1066591: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066591
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pd-mrpeach
Version: 0.1~svn17672-4
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
This is most likely caused by a change in dpkg 1.22.6, that enabled
-Werror=implicit-function-declaration. For more information, see
https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration
Relevant part (hopefully):
> cc -DPD -I "/usr/include/pd" -DUNIX -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC
> -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration
> -ffile-prefix-map=/<>=. -fstack-protector-strong
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -o
> life2x/life2x.pd_linux.o -c life2x/life2x.c
> info: making net/tcpserver.pd_linux.o in lib mrpeach
> slipenc/slipenc.c: In function ‘slipenc_new’:
> slipenc/slipenc.c:92:9: error: implicit declaration of function ‘error’; did
> you mean ‘perror’? [-Werror=implicit-function-declaration]
>92 | error("slipenc: unable to allocate %lu bytes for x_slip_buf",
> (long)sizeof(t_atom)*x->x_slip_max_length);
> | ^
> | perror
> net/tcpsend.c: In function ‘tcpsend_connect’:
> net/tcpsend.c:64:9: error: implicit declaration of function ‘error’; did you
> mean ‘herror’? [-Werror=implicit-function-declaration]
>64 | error("tcpsend: already connected");
> | ^
> | herror
> life2x/life2x.c: In function ‘life2x_rule’:
> life2x/life2x.c:375:13: error: implicit declaration of function ‘error’; did
> you mean ‘perror’? [-Werror=implicit-function-declaration]
> 375 | error("life2x_rule: bad character in rule: %c",
> s->s_name[i]);
> | ^
> | perror
> cc1: some warnings being treated as errors
> make[1]: *** [/usr/share/pd-lib-builder//Makefile.pdlibbuilder:987:
> slipenc/slipenc.pd_linux.o] Error 1
The full build log is available from:
http://qa-logs.debian.net/2024/03/13/pd-mrpeach_0.1~svn17672-4_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240313;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240313=lu...@debian.org=1=1=1=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: pd-mrpeach
Source-Version: 0.1~svn17672-5
Done: IOhannes m zmölnig (Debian/GNU)
We believe that the bug you reported is fixed in the latest version of
pd-mrpeach, 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 1066...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
IOhannes m zmölnig (Debian/GNU) (supplier of updated
pd-mrpeach 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: Mon, 18 Mar 2024 13:26:44 +0100
Source: pd-mrpeach
Architecture: source
Version: 0.1~svn17672-5
Distributio
Processed: Bug#1066591 marked as pending in pd-mrpeach
Processing control commands: > tag -1 pending Bug #1066591 [src:pd-mrpeach] pd-mrpeach: FTBFS: slipenc/slipenc.c:92:9: error: implicit declaration of function ‘error’; did you mean ‘perror’? [-Werror=implicit-function-declaration] Added tag(s) pending. -- 1066591: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066591 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1066642: marked as done (pd-pdogg: FTBFS: oggwrite~.c:156:25: error: implicit declaration of function ‘error’; did you mean ‘herror’? [-Werror=implicit-function-declaration])
Your message dated Mon, 18 Mar 2024 12:09:44 +
with message-id
and subject line Bug#1066642: fixed in pd-pdogg 0.25.1-9
has caused the Debian Bug report #1066642,
regarding pd-pdogg: FTBFS: oggwrite~.c:156:25: error: implicit declaration of
function ‘error’; did you mean ‘herror’? [-Werror=implicit-function-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.)
--
1066642: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066642
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pd-pdogg
Version: 0.25.1-8
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
This is most likely caused by a change in dpkg 1.22.6, that enabled
-Werror=implicit-function-declaration. For more information, see
https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration
Relevant part (hopefully):
> cc -DPD -I "/usr/include/pd" -DUNIX -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC
> -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration
> -ffile-prefix-map=/<>=. -fstack-protector-strong
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -o
> oggwrite~.pd_linux.o -c oggwrite~.c
> oggwrite~.c: In function ‘oggwrite_write’:
> oggwrite~.c:156:25: error: implicit declaration of function ‘error’; did you
> mean ‘herror’? [-Werror=implicit-function-declaration]
> 156 | error("oggwrite~: could not send ogg header
> to server (%d)", err);
> | ^
> | herror
> oggamp~.c: In function ‘oggamp_vorbis_init’:
> oggamp~.c:252:17: error: implicit declaration of function ‘error’; did you
> mean ‘herror’? [-Werror=implicit-function-declaration]
> 252 | error("oggamp~: input does not appear to be an ogg
> bitstream (error %d)", result);
> | ^
> | herror
> oggwrite~.c: In function ‘oggwrite_comment’:
> oggwrite~.c:555:17: warning: assignment discards ‘const’ qualifier from
> pointer target type [-Wdiscarded-qualifiers]
> 555 | comment = atom_gensym(argv)->s_name;
> | ^
> oggamp~.c: In function ‘oggamp_child_main’:
> oggamp~.c:826:41: warning: format ‘%d’ expects argument of type ‘int’, but
> argument 3 has type ‘t_int’ {aka ‘long int’} [-Wformat=]
> 826 | sprintf(boo, "fifosize %d\n",
> |~^
> | |
> | int
> |%ld
> 827 | x->x_fifosize);
> | ~
> | |
> | t_int {aka long int}
> oggamp~.c:843:53: warning: format ‘%d’ expects argument of type ‘int’, but
> argument 3 has type ‘t_int’ {aka ‘long int’} [-Wformat=]
> 843 | sprintf(boo, "head %d, tail %d\n",
> x->x_fifohead, x->x_fifotail);
> |~^
> ~
> | | |
> | int
> t_int {aka long int}
> |%ld
> oggamp~.c:843:62: warning: format ‘%d’ expects argument of type ‘int’, but
> argument 4 has type ‘t_int’ {aka ‘long int’} [-Wformat=]
> 843 | sprintf(boo, "head %d, tail %d\n",
> x->x_fifohead, x->x_fifotail);
> | ~^
> ~
> | |
> |
> | int
> t_int {aka long int}
> |
Bug#1066568: marked as done (pd-iemlib: FTBFS: src/FIR~.c:120:7: error: implicit declaration of function ‘error’; did you mean ‘perror’? [-Werror=implicit-function-declaration])
Your message dated Mon, 18 Mar 2024 12:09:37 +
with message-id
and subject line Bug#1066568: fixed in pd-iemlib 1.22.3-2
has caused the Debian Bug report #1066568,
regarding pd-iemlib: FTBFS: src/FIR~.c:120:7: error: implicit declaration of
function ‘error’; did you mean ‘perror’? [-Werror=implicit-function-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.)
--
1066568: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066568
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pd-iemlib
Version: 1.22.3-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
This is most likely caused by a change in dpkg 1.22.6, that enabled
-Werror=implicit-function-declaration. For more information, see
https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration
Relevant part (hopefully):
> cc -DPD -I "/usr/include/pd" -DUNIX -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC
> -Iinclude -DHAVE_G_CANVAS_H=1 -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=.
> -fstack-protector-strong -fstack-clash-protection -Wformat
> -Werror=format-security -fcf-protection -o src/dollarg.pd_linux.o -c
> src/dollarg.c
> info: making src/exp_inc.pd_linux.o in lib iemlib
> src/FIR~.c: In function ‘FIR_tilde_set’:
> src/FIR~.c:120:7: error: implicit declaration of function ‘error’; did you
> mean ‘perror’? [-Werror=implicit-function-declaration]
> 120 | error("FIR~: %s: no such table~", x->x_table_name->s_name);
> | ^
> | perror
> cc -DPD -I "/usr/include/pd" -DUNIX -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC
> -Iinclude -DHAVE_G_CANVAS_H=1 -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=.
> -fstack-protector-strong -fstack-clash-protection -Wformat
> -Werror=format-security -fcf-protection -o src/exp_inc.pd_linux.o -c
> src/exp_inc.c
> info: making src/f2note.pd_linux.o in lib iemlib
> cc -DPD -I "/usr/include/pd" -DUNIX -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC
> -Iinclude -DHAVE_G_CANVAS_H=1 -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=.
> -fstack-protector-strong -fstack-clash-protection -Wformat
> -Werror=format-security -fcf-protection -o src/f2note.pd_linux.o -c
> src/f2note.c
> info: making src/fade~.pd_linux.o in lib iemlib
> cc -DPD -I "/usr/include/pd" -DUNIX -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC
> -Iinclude -DHAVE_G_CANVAS_H=1 -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=.
> -fstack-protector-strong -fstack-clash-protection -Wformat
> -Werror=format-security -fcf-protection -o src/fade~.pd_linux.o -c src/fade~.c
> info: making src/filter~.pd_linux.o in lib iemlib
> cc -DPD -I "/usr/include/pd" -DUNIX -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC
> -Iinclude -DHAVE_G_CANVAS_H=1 -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=.
> -fstack-protector-strong -fstack-clash-protection -Wformat
> -Werror=format-security -fcf-protection -o src/filter~.pd_linux.o -c
> src/filter~.c
> info: making src/float24.pd_linux.o in lib iemlib
> cc -DPD -I "/usr/include/pd" -DUNIX -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC
> -Iinclude -DHAVE_G_CANVAS_H=1 -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=.
> -fstack-protector-strong -fstack-clash-protection -Wformat
> -Werror=format-security -fcf-protection -o src/float24.pd_linux.o -c
> src/float24.c
> info: making src/for++.pd_linux.o in lib iemlib
> cc -DPD -I "/usr/include/pd" -DUNIX -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC
> -Iinclude -DHAVE_G_CANVAS_H=1 -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=.
> -fstack-protector-strong -fstack-clash-protection -Wformat
> -Werror=format-security -fcf-protection -o src/for++.pd_linux.o -c src/for++.c
> info: making src/gate.pd_linux.o in lib iemlib
> cc -DPD -I "/usr/include/pd&
Bug#1066615: marked as done (pd-markex: FTBFS: counter.c:83:25: error: implicit declaration of function ‘error’; did you mean ‘perror’? [-Werror=implicit-function-declaration])
Your message dated Mon, 18 Mar 2024 11:50:04 +
with message-id
and subject line Bug#1066615: fixed in pd-markex 0.85-8
has caused the Debian Bug report #1066615,
regarding pd-markex: FTBFS: counter.c:83:25: error: implicit declaration of
function ‘error’; did you mean ‘perror’? [-Werror=implicit-function-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.)
--
1066615: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066615
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pd-markex
Version: 0.85-7
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
This is most likely caused by a change in dpkg 1.22.6, that enabled
-Werror=implicit-function-declaration. For more information, see
https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration
Relevant part (hopefully):
> cc -DPD -I "/usr/include/pd" -DUNIX -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC
> -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration
> -ffile-prefix-map=/<>=. -fstack-protector-strong
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -o
> randomF.pd_linux.o -c randomF.c
> info: making reson~.pd_linux.o in lib markex
> counter.c: In function ‘counter_bang’:
> counter.c:83:25: error: implicit declaration of function ‘error’; did you
> mean ‘perror’? [-Werror=implicit-function-declaration]
>83 | error("up/down wrong");
> | ^
> | perror
> tripleLine.c: In function ‘setLineParameters’:
> tripleLine.c:66:17: error: implicit declaration of function ‘error’; did you
> mean ‘perror’? [-Werror=implicit-function-declaration]
>66 | error("tripleLine: requires 3 or 4 args");
> | ^
> | perror
> cc -DPD -I "/usr/include/pd" -DUNIX -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC
> -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration
> -ffile-prefix-map=/<>=. -fstack-protector-strong
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -o
> reson~.pd_linux.o -c reson~.c
> info: making alternate.pd_linux.o in lib markex
> cc -DPD -I "/usr/include/pd" -DUNIX -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC
> -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration
> -ffile-prefix-map=/<>=. -fstack-protector-strong
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -o
> alternate.pd_linux.o -c alternate.c
> info: making average.pd_linux.o in lib markex
> cc -DPD -I "/usr/include/pd" -DUNIX -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC
> -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration
> -ffile-prefix-map=/<>=. -fstack-protector-strong
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -o
> average.pd_linux.o -c average.c
> info: making tripleRand.pd_linux.o in lib markex
> cc -DPD -I "/usr/include/pd" -DUNIX -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC
> -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration
> -ffile-prefix-map=/<>=. -fstack-protector-strong
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -o
> tripleRand.pd_linux.o -c tripleRand.c
> info: making vector0x2f.pd_linux.o in lib markex
> cc -DPD -I "/usr/include/pd" -DUNIX -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC
> -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration
> -ffile-prefix-map=/<>=. -fstack-protector-strong
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -o
> vector0x2f.pd_linux.o -c vector0x2f.c
> info: making vectorpack.pd_linux.o in lib markex
> cc1: some warnings being treated as errors
> make[1]: *** [/usr/share/pd-lib-builder//Makefile.pdlibbuilder:987:
> tripleLine.pd_linux.o] Error 1
The full build log is available from:
http://qa-logs.debian.net/2024/03/13/pd-markex_0.85-7_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag
Bug#1066590: marked as done (pd-creb: FTBFS: modules/statwav~.c:116:13: error: implicit declaration of function ‘error’; did you mean ‘perror’? [-Werror=implicit-function-declaration])
Your message dated Mon, 18 Mar 2024 11:49:47 +
with message-id
and subject line Bug#1066590: fixed in pd-creb 0.10.0-2
has caused the Debian Bug report #1066590,
regarding pd-creb: FTBFS: modules/statwav~.c:116:13: error: implicit
declaration of function ‘error’; did you mean ‘perror’?
[-Werror=implicit-function-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.)
--
1066590: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066590
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pd-creb
Version: 0.10.0-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
This is most likely caused by a change in dpkg 1.22.6, that enabled
-Werror=implicit-function-declaration. For more information, see
https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration
Relevant part (hopefully):
> cc -DPD -I "/usr/include/pd" -DUNIX -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC
> -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration
> -ffile-prefix-map=/<>=. -fstack-protector-strong
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -o
> modules/ibfft~.pd_linux.o -c modules/ibfft~.c
> info: making modules/cheby~.pd_linux.o in lib creb
> modules/statwav~.c: In function ‘statwav_tilde_set’:
> modules/statwav~.c:116:13: error: implicit declaration of function ‘error’;
> did you mean ‘perror’? [-Werror=implicit-function-declaration]
> 116 | error("statwav~: %s: no such array",
> x->x_arrayname->s_name);
> | ^
> | perror
> cc1: some warnings being treated as errors
> make[1]: *** [/usr/share/pd-lib-builder//Makefile.pdlibbuilder:987:
> modules/statwav~.pd_linux.o] Error 1
The full build log is available from:
http://qa-logs.debian.net/2024/03/13/pd-creb_0.10.0-1_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240313;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240313=lu...@debian.org=1=1=1=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: pd-creb
Source-Version: 0.10.0-2
Done: IOhannes m zmölnig (Debian/GNU)
We believe that the bug you reported is fixed in the latest version of
pd-creb, 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 1066...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
IOhannes m zmölnig (Debian/GNU) (supplier of updated
pd-creb 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: Sat, 16 Mar 2024 21:54:00 +0100
Source: pd-creb
Architecture: source
Version: 0.10.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers
Changed-By: IOhannes m zmölnig (Debian/GNU)
Closes: 1066590
Changes:
pd-creb (0.10.0-2) unstable; urgency=medium
.
* Patch to use pd_error() instead of error() (Closes: #1066590)
Checksums-Sha1:
2e178b3b53966eeb77613b376468383c1bc74c84 2122 pd-creb_0.10.0-2.dsc
d53b7489dad8db325c9a4ce06c767903d6a869bf 11832 pd-creb_0.10.0-2.debian.tar.xz
Checksums-Sha256:
68aa3c17c006d6ce41283fe18394219c4a92e318a6824e6ebb744fdb822ab2d5 2122
pd-creb_0.10.0-2.dsc
9fa5e6d35c239353906342f6f1f86dd5f1c914dd0beb580e289df7f17fbce284 11832
pd-creb_0.10.0-2.debian.tar.xz
Files:
67d513241c993b1fe3bde3af36859925 2122 sound optional pd-creb_0.10.0-2.dsc
0ac37321aa14f2da464860d0bf344b8
Bug#1066588: marked as done (pd-nusmuk: FTBFS: pbank.c:159:9: error: implicit declaration of function ‘error’; did you mean ‘perror’? [-Werror=implicit-function-declaration])
Your message dated Mon, 18 Mar 2024 11:50:11 +
with message-id
and subject line Bug#1066588: fixed in pd-nusmuk 20151113+repack-9
has caused the Debian Bug report #1066588,
regarding pd-nusmuk: FTBFS: pbank.c:159:9: error: implicit declaration of
function ‘error’; did you mean ‘perror’? [-Werror=implicit-function-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.)
--
1066588: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066588
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pd-nusmuk
Version: 20151113+repack-8
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
This is most likely caused by a change in dpkg 1.22.6, that enabled
-Werror=implicit-function-declaration. For more information, see
https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration
Relevant part (hopefully):
> cc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=.
> -fstack-protector-strong -fstack-clash-protection -Wformat
> -Werror=format-security -fcf-protection -fPIC -o "tab_upsample.o" -c
> "tab_upsample.c"
> pbank.c: In function ‘pbank_set’:
> pbank.c:159:9: error: implicit declaration of function ‘error’; did you mean
> ‘perror’? [-Werror=implicit-function-declaration]
> 159 | error("pbank_set: takes at least 3 arguments: column row
> item(s)");
> | ^
> | perror
> pbank.c: In function ‘pbank_read’:
> pbank.c:907:27: warning: passing argument 2 of ‘pbank_fromfile’ discards
> ‘const’ qualifier from pointer target type [-Wdiscarded-qualifiers]
> 907 | pbank_fromfile(x,fname->s_name,TEXT,0);
> | ~^~~~
> pbank.c:869:38: note: expected ‘char *’ but argument is of type ‘const char *’
> 869 | void pbank_fromfile(t_pbank *x,char *name, int type, int silentFlag)
> // filename with or without path
> |~~^~~~
> pbank.c: In function ‘pbank_new’:
> mtx_preset.c: In function ‘mtx_preset_matrix’:
> pbank.c:1194:14: warning: assignment discards ‘const’ qualifier from pointer
> target type [-Wdiscarded-qualifiers]
> 1194 | shit = (argv+2)->a_w.w_symbol->s_name;
> | ^
> mtx_preset.c:120:9: error: implicit declaration of function ‘error’; did you
> mean ‘perror’? [-Werror=implicit-function-declaration]
> 120 | error("bad matrix");
> | ^
> | perror
> pbank.c:1217:14: warning: assignment discards ‘const’ qualifier from pointer
> target type [-Wdiscarded-qualifiers]
> 1217 | shit = (argv+3)->a_w.w_symbol->s_name;
> | ^
> pbank.c:1257:43: warning: passing argument 2 of ‘pbank_fromfile’ discards
> ‘const’ qualifier from pointer target type [-Wdiscarded-qualifiers]
> 1257 | pbank_fromfile(x,x->p_name->s_name, TEXT,1);
> | ~^~~~
> pbank.c:869:38: note: expected ‘char *’ but argument is of type ‘const char *’
> 869 | void pbank_fromfile(t_pbank *x,char *name, int type, int silentFlag)
> // filename with or without path
> |~~^~~~
> cc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=.
> -fstack-protector-strong -fstack-clash-protection -Wformat
> -Werror=format-security -fcf-protection -fPIC -o "tab_upsample_copy.o" -c
> "tab_upsample_copy.c"
> cc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=.
> -fstack-protector-strong -fstack-clash-protection -Wformat
> -Werror=format-security -fcf-protection -fPIC -o "tab_max.o" -c "tab_max.c"
> cc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=.
> -fstack-protector-strong -fstack-clash-protection -Wformat
> -Werror=format-security -fcf-protection -fPIC -o "tab_min.o" -c "tab_min.c"
> cc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2
> -Werror=implicit-function-declaration -ffile-prefix-map=/
Bug#1066517: marked as done (pd-hcs: FTBFS: stat.c:123:17: error: implicit declaration of function ‘error’; did you mean ‘perror’? [-Werror=implicit-function-declaration])
Your message dated Mon, 18 Mar 2024 11:49:57 +
with message-id
and subject line Bug#1066517: fixed in pd-hcs 0.2.1-4
has caused the Debian Bug report #1066517,
regarding pd-hcs: FTBFS: stat.c:123:17: error: implicit declaration of function
‘error’; did you mean ‘perror’? [-Werror=implicit-function-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.)
--
1066517: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066517
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pd-hcs
Version: 0.2.1-3
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
This is most likely caused by a change in dpkg 1.22.6, that enabled
-Werror=implicit-function-declaration. For more information, see
https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration
Relevant part (hopefully):
> cc -DPD -I "/usr/include/pd" -DUNIX -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC
> -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration
> -ffile-prefix-map=/<>=. -fstack-protector-strong
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -o
> canvas_name.pd_linux.o -c canvas_name.c
> info: making folder_list.pd_linux.o in lib hcs
> classpath.c: In function ‘classpath_setup’:
> classpath.c:138:38: warning: macro "__DATE__" might prevent reproducible
> builds [-Wdate-time]
> 138 | logpost(NULL, 4, "\tcompiled on "__DATE__" at "__TIME__ " ");
> | ^~~~
> classpath.c:138:52: warning: macro "__TIME__" might prevent reproducible
> builds [-Wdate-time]
> 138 | logpost(NULL, 4, "\tcompiled on "__DATE__" at "__TIME__ " ");
> |^~~~
> stat.c: In function ‘stat_output_error’:
> stat.c:123:17: error: implicit declaration of function ‘error’; did you mean
> ‘perror’? [-Werror=implicit-function-declaration]
> 123 | error("[stat]: access denied: %s",
> x->x_filename->s_name);
> | ^
> | perror
> stat.c: In function ‘stat_setup’:
> stat.c:302:38: warning: macro "__DATE__" might prevent reproducible builds
> [-Wdate-time]
> 302 | logpost(NULL, 4, "\tcompiled on "__DATE__" at "__TIME__ " ");
> | ^~~~
> stat.c:302:52: warning: macro "__TIME__" might prevent reproducible builds
> [-Wdate-time]
> 302 | logpost(NULL, 4, "\tcompiled on "__DATE__" at "__TIME__ " ");
> |^~~~
> passwd.c: In function ‘get_uid_from_arguments’:
> passwd.c:118:25: error: implicit declaration of function ‘error’; did you
> mean ‘perror’? [-Werror=implicit-function-declaration]
> 118 | error("[passwd]: UID less than zero not
> allowed (%d)", (int)uid);
> | ^
> | perror
> passwd.c: In function ‘passwd_setup’:
> passwd.c:205:38: warning: macro "__DATE__" might prevent reproducible builds
> [-Wdate-time]
> 205 | logpost(NULL, 4, "\tcompiled on "__DATE__" at "__TIME__ " ");
> | ^~~~
> passwd.c:205:52: warning: macro "__TIME__" might prevent reproducible builds
> [-Wdate-time]
> 205 | logpost(NULL, 4, "\tcompiled on "__DATE__" at "__TIME__ " ");
> |^~~~
> cc -DPD -I "/usr/include/pd" -DUNIX -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC
> -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration
> -ffile-prefix-map=/<>=. -fstack-protector-strong
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -o
> folder_list.pd_linux.o -c folder_list.c
> info: making unsetenv.pd_linux.o in lib hcs
> cc -DPD -I "/usr/include/pd" -DUNIX -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC
> -Wda
Processed: Bug#1066642 marked as pending in pd-pdogg
Processing control commands: > tag -1 pending Bug #1066642 [src:pd-pdogg] pd-pdogg: FTBFS: oggwrite~.c:156:25: error: implicit declaration of function ‘error’; did you mean ‘herror’? [-Werror=implicit-function-declaration] Added tag(s) pending. -- 1066642: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066642 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#1066588 marked as pending in pd-nusmuk
Processing control commands: > tag -1 pending Bug #1066588 [src:pd-nusmuk] pd-nusmuk: FTBFS: pbank.c:159:9: error: implicit declaration of function ‘error’; did you mean ‘perror’? [-Werror=implicit-function-declaration] Added tag(s) pending. -- 1066588: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066588 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#1066615 marked as pending in pd-markex
Processing control commands: > tag -1 pending Bug #1066615 [src:pd-markex] pd-markex: FTBFS: counter.c:83:25: error: implicit declaration of function ‘error’; did you mean ‘perror’? [-Werror=implicit-function-declaration] Added tag(s) pending. -- 1066615: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066615 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#1066568 marked as pending in pd-iemlib
Processing control commands: > tag -1 pending Bug #1066568 [src:pd-iemlib] pd-iemlib: FTBFS: src/FIR~.c:120:7: error: implicit declaration of function ‘error’; did you mean ‘perror’? [-Werror=implicit-function-declaration] Added tag(s) pending. -- 1066568: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066568 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#1066590 marked as pending in pd-creb
Processing control commands: > tag -1 pending Bug #1066590 [src:pd-creb] pd-creb: FTBFS: modules/statwav~.c:116:13: error: implicit declaration of function ‘error’; did you mean ‘perror’? [-Werror=implicit-function-declaration] Added tag(s) pending. -- 1066590: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066590 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#1066517 marked as pending in pd-hcs
Processing control commands: > tag -1 pending Bug #1066517 [src:pd-hcs] pd-hcs: FTBFS: stat.c:123:17: error: implicit declaration of function ‘error’; did you mean ‘perror’? [-Werror=implicit-function-declaration] Added tag(s) pending. -- 1066517: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066517 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1066530: marked as done (pd-tclpd: FTBFS: tcl_class.c:108:9: error: implicit declaration of function ‘error’; did you mean ‘perror’? [-Werror=implicit-function-declaration])
Your message dated Sat, 16 Mar 2024 23:10:36 +
with message-id
and subject line Bug#1066530: fixed in pd-tclpd 0.3.1-3
has caused the Debian Bug report #1066530,
regarding pd-tclpd: FTBFS: tcl_class.c:108:9: error: implicit declaration of
function ‘error’; did you mean ‘perror’? [-Werror=implicit-function-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.)
--
1066530: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066530
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pd-tclpd
Version: 0.3.1-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
This is most likely caused by a change in dpkg 1.22.6, that enabled
-Werror=implicit-function-declaration. For more information, see
https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration
Relevant part (hopefully):
> cc -DPD -I "/usr/include/pd" -DUNIX -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC
> -std=c99 -DHASHTABLE_COPY_KEYS -I/usr/include/tcl8.6 -Wdate-time
> -D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration
> -ffile-prefix-map=/<>=. -fstack-protector-strong
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -o
> tcl_widgetbehavior.pd_linux.o -c tcl_widgetbehavior.c
> swig -v -tcl -o tcl_wrap.c -I/usr/include/pd tclpd.i
> In file included from
> /usr/include/x86_64-linux-gnu/bits/libc-header-start.h:33,
> from /usr/include/stdint.h:26,
> from /usr/lib/gcc/x86_64-linux-gnu/13/include/stdint.h:9,
> from hashtable.h:7,
> from hashtable.c:1:
> /usr/include/features.h:195:3: warning: #warning "_BSD_SOURCE and
> _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp]
> 195 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use
> _DEFAULT_SOURCE"
> | ^~~
> hashtable.c: In function ‘list_remove’:
> hashtable.c:37:17: warning: passing argument 1 of ‘free’ discards ‘const’
> qualifier from pointer target type [-Wdiscarded-qualifiers]
>37 | free(tmp->k);
> | ~~~^~~
> In file included from hashtable.h:8:
> /usr/include/stdlib.h:568:25: note: expected ‘void *’ but argument is of type
> ‘const char *’
> 568 | extern void free (void *__ptr) __THROW;
> | ~~^
> hashtable.c:51:21: warning: passing argument 1 of ‘free’ discards ‘const’
> qualifier from pointer target type [-Wdiscarded-qualifiers]
>51 | free(tmp->k);
> | ~~~^~~
> /usr/include/stdlib.h:568:25: note: expected ‘void *’ but argument is of type
> ‘const char *’
> 568 | extern void free (void *__ptr) __THROW;
> | ~~^
> tcl_class.c: In function ‘tclpd_new’:
> tcl_class.c:108:9: error: implicit declaration of function ‘error’; did you
> mean ‘perror’? [-Werror=implicit-function-declaration]
> 108 | error("tclpd: class not found: %s", name);
> | ^
> | perror
> tcl_widgetbehavior.c: In function ‘tclpd_guiclass_vis’:
> tcl_widgetbehavior.c:297:28: warning: format ‘%lx’ expects argument of type
> ‘long unsigned int’, but argument 4 has type ‘struct _glist *’ [-Wformat=]
> 297 | snprintf(buf, 32, ".x%lx.c", glist_getcanvas(glist));
> | ~~^ ~~
> || |
> || struct _glist *
> |long unsigned int
> tclpd.c: In function ‘tclpd_setup’:
> tclpd.c:32:9: error: implicit declaration of function ‘error’; did you mean
> ‘perror’? [-Werror=implicit-function-declaration]
>32 | error("tclpd: error loading %s", buf);
> | ^
> | perror
> tcl_loader.c: In function ‘tclpd_do_load_lib’:
> tcl_loader.c:80:9: error: implicit declaration of function ‘error’; did you
> mean ‘perror’? [-Werror=implicit-function-declaration]
>80 | error("tclpd loader: error trying to load %s", filename);
> | ^
> | perror
> tcl_proxyinlet.c: In function ‘proxyinlet_anything’:
&g
Bug#1066501: marked as done (pd-wiimote: FTBFS: wiimote.c:736:7: error: implicit declaration of function ‘error’; did you mean ‘perror’? [-Werror=implicit-function-declaration])
Your message dated Sat, 16 Mar 2024 23:10:50 +
with message-id
and subject line Bug#1066501: fixed in pd-wiimote 0.3.2-9
has caused the Debian Bug report #1066501,
regarding pd-wiimote: FTBFS: wiimote.c:736:7: error: implicit declaration of
function ‘error’; did you mean ‘perror’? [-Werror=implicit-function-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.)
--
1066501: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066501
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pd-wiimote
Version: 0.3.2-8
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
This is most likely caused by a change in dpkg 1.22.6, that enabled
-Werror=implicit-function-declaration. For more information, see
https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration
Relevant part (hopefully):
> cc -DPD -I "/usr/include/pd" -DUNIX -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC
> -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration
> -ffile-prefix-map=/<>=. -fstack-protector-strong
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -o
> wiimote.pd_linux.o -c wiimote.c
> wiimote.c:405:2: warning: #warning Balance ignores calibration data [-Wcpp]
> 405 | #warning Balance ignores calibration data
> | ^~~
> wiimote.c: In function ‘cwiid_error_callback’:
> wiimote.c:736:7: error: implicit declaration of function ‘error’; did you
> mean ‘perror’? [-Werror=implicit-function-declaration]
> 736 | error("wiimote: %s", err);
> | ^
> | perror
> cc1: some warnings being treated as errors
> make[1]: *** [/usr/share/pd-lib-builder//Makefile.pdlibbuilder:987:
> wiimote.pd_linux.o] Error 1
The full build log is available from:
http://qa-logs.debian.net/2024/03/13/pd-wiimote_0.3.2-8_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240313;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240313=lu...@debian.org=1=1=1=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: pd-wiimote
Source-Version: 0.3.2-9
Done: IOhannes m zmölnig (Debian/GNU)
We believe that the bug you reported is fixed in the latest version of
pd-wiimote, 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 1066...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
IOhannes m zmölnig (Debian/GNU) (supplier of updated
pd-wiimote 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: Sat, 16 Mar 2024 23:47:00 +0100
Source: pd-wiimote
Architecture: source
Version: 0.3.2-9
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers
Changed-By: IOhannes m zmölnig (Debian/GNU)
Closes: 1066501
Changes:
pd-wiimote (0.3.2-9) unstable; urgency=medium
.
* Patch to use pd_error() instead of error() (Closes: #1066501)
* Refresh patches
Checksums-Sha1:
96eabce4c9ee7031cc0fa357aa824e52e6e4d490 2196 pd-wiimote_0.3.2-9.dsc
155c8495a8935edae69937787cdb5941bea4e9b6 4436 pd-wiimote_0.3.2-9.debian.tar.xz
Checksums-Sha256:
c2ebb10193cc627011eee2aa2099360d14cd67158a95d19335a3c965b60c95f3 2196
pd-wiimote_0.3.2-9.dsc
6d696c8b4ec56ee77a6b0af5d2af0eb9dc35a88f030d24d9aaedd576c9484381 4436
pd-wiimote_0.3.2-9.debian.tar.xz
Files:
14a36b11dec68575416b8878ea3dd094 2196 sound optional pd-wiimote_0.3.2-9.
Processed: Bug#1066530 marked as pending in pd-tclpd
Processing control commands: > tag -1 pending Bug #1066530 [src:pd-tclpd] pd-tclpd: FTBFS: tcl_class.c:108:9: error: implicit declaration of function ‘error’; did you mean ‘perror’? [-Werror=implicit-function-declaration] Added tag(s) pending. -- 1066530: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066530 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#1066501 marked as pending in pd-wiimote
Processing control commands: > tag -1 pending Bug #1066501 [src:pd-wiimote] pd-wiimote: FTBFS: wiimote.c:736:7: error: implicit declaration of function ‘error’; did you mean ‘perror’? [-Werror=implicit-function-declaration] Added tag(s) pending. -- 1066501: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066501 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1066699: marked as done (pd-unauthorized: FTBFS: blinkenlights.c:770:9: error: implicit declaration of function ‘error’; did you mean ‘perror’? [-Werror=implicit-function-declaration])
Your message dated Sat, 16 Mar 2024 22:42:55 +
with message-id
and subject line Bug#1066699: fixed in pd-unauthorized 0.1-8
has caused the Debian Bug report #1066699,
regarding pd-unauthorized: FTBFS: blinkenlights.c:770:9: error: implicit
declaration of function ‘error’; did you mean ‘perror’?
[-Werror=implicit-function-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.)
--
1066699: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066699
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pd-unauthorized
Version: 0.1-7
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
This is most likely caused by a change in dpkg 1.22.6, that enabled
-Werror=implicit-function-declaration. For more information, see
https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration
Relevant part (hopefully):
> cc -I"/usr/include/pd" -DPD -DVERSION='"0.1"' -fPIC -Wdate-time
> -D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration
> -ffile-prefix-map=/<>=. -fstack-protector-strong
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -O6
> -funroll-loops -fomit-frame-pointer -o "exciter.o" -c "exciter.c"
> blinkenlights.c: In function ‘blinkenlights_open’:
> blinkenlights.c:770:9: error: implicit declaration of function ‘error’; did
> you mean ‘perror’? [-Werror=implicit-function-declaration]
> 770 | error( "blinkenlights : cannot open >%s<", sfile->s_name);
> | ^
> | perror
> blinkenlights.c: In function ‘blinkenlights_findframes’:
> blinkenlights.c:629:9: warning: ignoring return value of ‘fgets’ declared
> with attribute ‘warn_unused_result’ [-Wunused-result]
> 629 | fgets( lineread, BL_MAX_LENGTH, x->x_filed );
> | ^~~~
> audience~.c: In function ‘audience_properties’:
> audience~.c:389:45: warning: format ‘%d’ expects argument of type ‘int’, but
> argument 3 has type ‘t_int’ {aka ‘long int’} [-Wformat=]
> 389 | sprintf(buf, "pdtk_audience_dialog %%s %d %d %d\n",
> |~^
> | |
> | int
> |%ld
> 390 | x->x_width, x->x_height, x->x_nboutputs
> | ~~
> | |
> | t_int {aka long int}
> audience~.c:389:48: warning: format ‘%d’ expects argument of type ‘int’, but
> argument 4 has type ‘t_int’ {aka ‘long int’} [-Wformat=]
> 389 | sprintf(buf, "pdtk_audience_dialog %%s %d %d %d\n",
> | ~^
> ||
> |int
> | %ld
> 390 | x->x_width, x->x_height, x->x_nboutputs
> | ~~~
> | |
> | t_int {aka long int}
> audience~.c:389:51: warning: format ‘%d’ expects argument of type ‘int’, but
> argument 5 has type ‘t_int’ {aka ‘long int’} [-Wformat=]
> 389 | sprintf(buf, "pdtk_audience_dialog %%s %d %d %d\n",
> | ~^
> | |
> | int
> | %ld
> 390 | x->x_width, x->x_height, x->x_nboutputs
> | ~~
> | |
> | t_int {aka long int}
> audience~.c: In function ‘audience_dialog’:
> audience~.c:516:13: error: implicit declaration of function ‘error’; did you
> mean ‘perror’? [-Werror=implicit-function-declaration]
> 516 | error( "audience~ : fatal : could no
Processed: Bug#1066699 marked as pending in pd-unauthorized
Processing control commands: > tag -1 pending Bug #1066699 [src:pd-unauthorized] pd-unauthorized: FTBFS: blinkenlights.c:770:9: error: implicit declaration of function ‘error’; did you mean ‘perror’? [-Werror=implicit-function-declaration] Added tag(s) pending. -- 1066699: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066699 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1066650: marked as done (pd-fftease: FTBFS: fftease_utilities.c:56:9: error: implicit declaration of function ‘error’; did you mean ‘perror’? [-Werror=implicit-function-declaration])
Your message dated Sat, 16 Mar 2024 22:13:49 +
with message-id
and subject line Bug#1066650: fixed in pd-fftease 3.0.1-6
has caused the Debian Bug report #1066650,
regarding pd-fftease: FTBFS: fftease_utilities.c:56:9: error: implicit
declaration of function ‘error’; did you mean ‘perror’?
[-Werror=implicit-function-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.)
--
1066650: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066650
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pd-fftease
Version: 3.0.1-5
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
This is most likely caused by a change in dpkg 1.22.6, that enabled
-Werror=implicit-function-declaration. For more information, see
https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration
Relevant part (hopefully):
> cc -DPD -I "/usr/include/pd" -DUNIX -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC
> -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration
> -ffile-prefix-map=/<>=. -fstack-protector-strong
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -o
> leanunconvert.pd_linux.o -c leanunconvert.c
> info: making limit_fftsize.pd_linux.o in lib fftease
> fftease_utilities.c: In function ‘fftease_overlap’:
> fftease_utilities.c:56:9: error: implicit declaration of function ‘error’;
> did you mean ‘perror’? [-Werror=implicit-function-declaration]
>56 | error("fftease_overlap: %d is not a legal overlap
> factor",overlap);
> | ^
> | perror
> cc -DPD -I "/usr/include/pd" -DUNIX -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC
> -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration
> -ffile-prefix-map=/<>=. -fstack-protector-strong
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -o
> limit_fftsize.pd_linux.o -c limit_fftsize.c
> info: making limited_oscbank.pd_linux.o in lib fftease
> cc -DPD -I "/usr/include/pd" -DUNIX -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC
> -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration
> -ffile-prefix-map=/<>=. -fstack-protector-strong
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -o
> limited_oscbank.pd_linux.o -c limited_oscbank.c
> info: making makewindows.pd_linux.o in lib fftease
> cc -DPD -I "/usr/include/pd" -DUNIX -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC
> -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration
> -ffile-prefix-map=/<>=. -fstack-protector-strong
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -o
> makewindows.pd_linux.o -c makewindows.c
> info: making oscbank.pd_linux.o in lib fftease
> cc -DPD -I "/usr/include/pd" -DUNIX -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC
> -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration
> -ffile-prefix-map=/<>=. -fstack-protector-strong
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -o
> oscbank.pd_linux.o -c oscbank.c
> info: making overlapadd.pd_linux.o in lib fftease
> cc -DPD -I "/usr/include/pd" -DUNIX -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC
> -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration
> -ffile-prefix-map=/<>=. -fstack-protector-strong
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -o
> overlapadd.pd_linux.o -c overlapadd.c
> info: making PenroseOscil.pd_linux.o in lib fftease
> cc -DPD -I "/usr/include/pd" -DUNIX -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC
> -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration
> -ffile-prefix-map=/<>=. -fstack-protector-strong
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -o
> PenroseOscil.pd_linux.o -c PenroseOscil.c
> info: making PenroseRand.pd_linux.o in lib fftease
> cc -DPD -I "/usr/include/pd" -DUNIX -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC
> -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration
> -ffile-prefix-map
Bug#1066665: marked as done (pd-ggee: FTBFS: control/unwonk.c:59:31: error: implicit declaration of function ‘error’; did you mean ‘perror’? [-Werror=implicit-function-declaration])
Your message dated Sat, 16 Mar 2024 22:13:56 +
with message-id
and subject line Bug#105: fixed in pd-ggee 0.28-5
has caused the Debian Bug report #105,
regarding pd-ggee: FTBFS: control/unwonk.c:59:31: error: implicit declaration
of function ‘error’; did you mean ‘perror’?
[-Werror=implicit-function-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.)
--
105: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=105
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pd-ggee
Version: 0.28-4
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
This is most likely caused by a change in dpkg 1.22.6, that enabled
-Werror=implicit-function-declaration. For more information, see
https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration
Relevant part (hopefully):
> cc -DPD -I "/usr/include/pd" -DUNIX -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC
> -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration
> -ffile-prefix-map=/<>=. -fstack-protector-strong
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -o
> filters/equalizer.pd_linux.o -c filters/equalizer.c
> info: making gui/state.pd_linux.o in lib ggee
> control/unwonk.c: In function ‘unwonk_new’:
> control/unwonk.c:59:31: error: implicit declaration of function ‘error’; did
> you mean ‘perror’? [-Werror=implicit-function-declaration]
>59 | if (c != 'f') error("unwonk: %s: bad type",
> | ^
> | perror
> control/qread.c: In function ‘qread_open’:
> control/qread.c:48:11: error: implicit declaration of function ‘error’; did
> you mean ‘perror’? [-Werror=implicit-function-declaration]
>48 | error("can't open %s",fname);
> | ^
> | perror
> control/qread.c: In function ‘qread_next’:
> control/qread.c:66:6: warning: ignoring return value of ‘fscanf’ declared
> with attribute ‘warn_unused_result’ [-Wunused-result]
>66 | fscanf(x->x_file,"%f",);
> | ^
> control/qread.c:72:6: warning: ignoring return value of ‘fscanf’ declared
> with attribute ‘warn_unused_result’ [-Wunused-result]
>72 | fscanf(x->x_file,"%s",name);
> | ^~~
> control/qread.c:78:11: warning: ignoring return value of ‘fscanf’ declared
> with attribute ‘warn_unused_result’ [-Wunused-result]
>78 | fscanf(x->x_file,"%f",);
> | ^~
> control/qread.c:82:6: warning: ignoring return value of ‘fscanf’ declared
> with attribute ‘warn_unused_result’ [-Wunused-result]
>82 | fscanf(x->x_file,";");
> | ^
> experimental/fofsynth~.c: In function ‘fofsynth_usearray’:
> experimental/fofsynth~.c:261:11: error: implicit declaration of function
> ‘error’; did you mean ‘perror’? [-Werror=implicit-function-declaration]
> 261 | error("%s: no such array", s->s_name);
> | ^
> | perror
> cc1: some warnings being treated as errors
> make[1]: *** [/usr/share/pd-lib-builder//Makefile.pdlibbuilder:987:
> control/unwonk.pd_linux.o] Error 1
The full build log is available from:
http://qa-logs.debian.net/2024/03/13/pd-ggee_0.28-4_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240313;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240313=lu...@debian.org=1=1=1=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: pd-ggee
Source-Version: 0.28-5
Done: IOha
Processed: Bug#1066650 marked as pending in pd-fftease
Processing control commands: > tag -1 pending Bug #1066650 [src:pd-fftease] pd-fftease: FTBFS: fftease_utilities.c:56:9: error: implicit declaration of function ‘error’; did you mean ‘perror’? [-Werror=implicit-function-declaration] Added tag(s) pending. -- 1066650: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066650 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1066627: marked as done (pd-cxc: FTBFS: reson~.c:131:17: error: implicit declaration of function ‘error’; did you mean ‘perror’? [-Werror=implicit-function-declaration])
Your message dated Sat, 16 Mar 2024 21:45:12 +
with message-id
and subject line Bug#1066627: fixed in pd-cxc 0.5.2-8
has caused the Debian Bug report #1066627,
regarding pd-cxc: FTBFS: reson~.c:131:17: error: implicit declaration of
function ‘error’; did you mean ‘perror’? [-Werror=implicit-function-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.)
--
1066627: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066627
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pd-cxc
Version: 0.5.2-7
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
This is most likely caused by a change in dpkg 1.22.6, that enabled
-Werror=implicit-function-declaration. For more information, see
https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration
Relevant part (hopefully):
> cc -DPD -I "/usr/include/pd" -DUNIX -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC
> -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration
> -ffile-prefix-map=/<>=. -fstack-protector-strong
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -o
> bfilt.pd_linux.o -c bfilt.c
> info: making random_fl.pd_linux.o in lib cxc
> reson~.c: In function ‘sigreson_new’:
> reson~.c:131:17: error: implicit declaration of function ‘error’; did you
> mean ‘perror’? [-Werror=implicit-function-declaration]
> 131 | error("buffer alloc failed");
> | ^
> | perror
> random1.c: In function ‘random1_bang’:
> random1.c:90:19: warning: integer overflow in expression of type ‘int’
> results in ‘-2’ [-Woverflow]
>90 | m = (RAND_MAX * 2);
> | ^
> mean~.c: In function ‘cxmean_set’:
> mean~.c:49:9: error: implicit declaration of function ‘error’; did you mean
> ‘perror’? [-Werror=implicit-function-declaration]
>49 | error("%s: bad template for mean~", x->x_arrayname->s_name);
> | ^
> | perror
> cc -DPD -I "/usr/include/pd" -DUNIX -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC
> -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration
> -ffile-prefix-map=/<>=. -fstack-protector-strong
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -o
> random_fl.pd_linux.o -c random_fl.c
> info: making cxc_split.pd_linux.o in lib cxc
> cc -DPD -I "/usr/include/pd" -DUNIX -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC
> -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration
> -ffile-prefix-map=/<>=. -fstack-protector-strong
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -o
> cxc_split.pd_linux.o -c cxc_split.c
> info: making bfilt2.pd_linux.o in lib cxc
> cc -DPD -I "/usr/include/pd" -DUNIX -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC
> -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration
> -ffile-prefix-map=/<>=. -fstack-protector-strong
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -o
> bfilt2.pd_linux.o -c bfilt2.c
> info: making ixprint.pd_linux.o in lib cxc
> cc1: some warnings being treated as errors
> make[1]: *** [/usr/share/pd-lib-builder//Makefile.pdlibbuilder:987:
> reson~.pd_linux.o] Error 1
The full build log is available from:
http://qa-logs.debian.net/2024/03/13/pd-cxc_0.5.2-7_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240313;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240313=lu...@debian.org=1=1=1=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: pd-cxc
Source-Version: 0.5.2-8
Bug#1066542: marked as done (pd-boids: FTBFS: boids2d.c:472:9: error: implicit declaration of function ‘error’; did you mean ‘perror’? [-Werror=implicit-function-declaration])
Your message dated Sat, 16 Mar 2024 21:45:04 +
with message-id
and subject line Bug#1066542: fixed in pd-boids 1.1.1-10
has caused the Debian Bug report #1066542,
regarding pd-boids: FTBFS: boids2d.c:472:9: error: implicit declaration of
function ‘error’; did you mean ‘perror’? [-Werror=implicit-function-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.)
--
1066542: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066542
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pd-boids
Version: 1.1.1-9
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
This is most likely caused by a change in dpkg 1.22.6, that enabled
-Werror=implicit-function-declaration. For more information, see
https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration
Relevant part (hopefully):
> cc -DPD -I "/usr/include/pd" -DUNIX -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC
> -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration
> -ffile-prefix-map=/<>=. -fstack-protector-strong
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -o
> boids2d.pd_linux.o -c boids2d.c
> boids3d.c: In function ‘boids3d_setup’:
> boids3d.c:178:80: warning: macro "__DATE__" might prevent reproducible builds
> [-Wdate-time]
> 178 | post("boids3d 2005-2006 a.sier / jasch ? 1995-2003 eric l.
> singer "__DATE__" "__TIME__);
> |
> ^~~~
> boids3d.c:178:91: warning: macro "__TIME__" might prevent reproducible builds
> [-Wdate-time]
> 178 | post("boids3d 2005-2006 a.sier / jasch ? 1995-2003 eric l.
> singer "__DATE__" "__TIME__);
> |
> ^~~~
> boids2d.c: In function ‘boids2d_setup’:
> boids2d.c:180:75: warning: macro "__DATE__" might prevent reproducible builds
> [-Wdate-time]
> 180 | post("boids2d 2005-2006 a.sier / jasch1995-2003 eric l.
> singer "__DATE__" "__TIME__);
> |
> ^~~~
> boids2d.c:180:86: warning: macro "__TIME__" might prevent reproducible builds
> [-Wdate-time]
> 180 | post("boids2d 2005-2006 a.sier / jasch1995-2003 eric l.
> singer "__DATE__" "__TIME__);
> |
>^~~~
> boids2d.c: In function ‘Flock_flyRect’:
> boids2d.c:472:9: error: implicit declaration of function ‘error’; did you
> mean ‘perror’? [-Werror=implicit-function-declaration]
> 472 | error("boids2d: flyrect needs four values");
> | ^
> | perror
> boids3d.c: In function ‘Flock_flyRect’:
> boids3d.c:468:17: error: implicit declaration of function ‘error’; did you
> mean ‘perror’? [-Werror=implicit-function-declaration]
> 468 | error("boids3d: flyrect needs 6 values");
> | ^
> | perror
> cc1: some warnings being treated as errors
> make[1]: *** [/usr/share/pd-lib-builder//Makefile.pdlibbuilder:987:
> boids2d.pd_linux.o] Error 1
The full build log is available from:
http://qa-logs.debian.net/2024/03/13/pd-boids_1.1.1-9_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240313;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240313=lu...@debian.org=1=1=1=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: pd-boids
Processed: Bug#1066665 marked as pending in pd-ggee
Processing control commands: > tag -1 pending Bug #105 [src:pd-ggee] pd-ggee: FTBFS: control/unwonk.c:59:31: error: implicit declaration of function ‘error’; did you mean ‘perror’? [-Werror=implicit-function-declaration] Added tag(s) pending. -- 105: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066665 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#1066627 marked as pending in pd-cxc
Processing control commands: > tag -1 pending Bug #1066627 [src:pd-cxc] pd-cxc: FTBFS: reson~.c:131:17: error: implicit declaration of function ‘error’; did you mean ‘perror’? [-Werror=implicit-function-declaration] Added tag(s) pending. -- 1066627: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066627 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#1066542 marked as pending in pd-boids
Processing control commands: > tag -1 pending Bug #1066542 [src:pd-boids] pd-boids: FTBFS: boids2d.c:472:9: error: implicit declaration of function ‘error’; did you mean ‘perror’? [-Werror=implicit-function-declaration] Added tag(s) pending. -- 1066542: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066542 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1051418: bad patch: debian/patches/0013-Fix-comparision-if-char-is-unsigned.patch
Processing control commands: > found -1 30.0.2+dfsg-2.1+b1 Bug #1051418 [obs-studio] obs-studio: clicking on an xcomposite window source makes obs segfault Marked as found in versions obs-studio/30.0.2+dfsg-2.1. -- 1051418: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051418 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1066836: marked as done (libcamera: ftbfs with 64-bit time_t)
Your message dated Thu, 14 Mar 2024 11:51:35 + with message-id and subject line Bug#1066836: fixed in libcamera 0.2.0-3 has caused the Debian Bug report #1066836, regarding libcamera: ftbfs with 64-bit time_t 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.) -- 1066836: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066836 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libcamera Version: 0.2.0-1 Severity: serious Tags: patch Justification: ftbfs User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu noble ubuntu-patch Dear maintainers, libcamera fails to build from source on 32-bit architectures under 64-bit time_t, because it has a module that legitimately un-sets _FILE_OFFSET_BITS for building but this is not allowed without also unsetting _TIME_BITS: [...] [267/430] c++ -Isrc/v4l2/v4l2-compat.so.p -Isrc/v4l2 -I../src/v4l2 -Iinclude -I../include -Iinclude/libcamera/ipa -Iinclude/libcamera -fdiagnostics-color=always -Wall -Winvalid-pch -Wextra -Werror -std=c++17 -Wno-redundant-move -Wno-psabi -Wshadow -include /<>/obj-arm-linux-gnueabihf/config.h -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -fno-stack-clash-protection -fdebug-prefix-map=/<>=/usr/src/libcamera-0.2.0-1ubuntu3 -Wno-error -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=3 -fPIC -DLIBCAMERA_BASE_PRIVATE -U_FILE_OFFSET_BITS -D_FILE_OFFSET_BITS=32 -D_LARGEFILE64_SOURCE -fvisibility=hidden -MD -MQ src/v4l2/v4l2-compat.so.p/v4l2_camera.cpp.o -MF src/v4l2/v4l2-compat.so.p/v4l2_camera.cpp.o.d -o src/v4l2/v4l2-compat.so.p/v4l2_camera.cpp.o -c ../src/v4l2/v4l2_camera.cpp FAILED: src/v4l2/v4l2-compat.so.p/v4l2_camera.cpp.o c++ -Isrc/v4l2/v4l2-compat.so.p -Isrc/v4l2 -I../src/v4l2 -Iinclude -I../include -Iinclude/libcamera/ipa -Iinclude/libcamera -fdiagnostics-color=always -Wall -Winvalid-pch -Wextra -Werror -std=c++17 -Wno-redundant-move -Wno-psabi -Wshadow -include /<>/obj-arm-linux-gnueabihf/config.h -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -fno-stack-clash-protection -fdebug-prefix-map=/<>=/usr/src/libcamera-0.2.0-1ubuntu3 -Wno-error -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=3 -fPIC -DLIBCAMERA_BASE_PRIVATE -U_FILE_OFFSET_BITS -D_FILE_OFFSET_BITS=32 -D_LARGEFILE64_SOURCE -fvisibility=hidden -MD -MQ src/v4l2/v4l2-compat.so.p/v4l2_camera.cpp.o -MF src/v4l2/v4l2-compat.so.p/v4l2_camera.cpp.o.d -o src/v4l2/v4l2-compat.so.p/v4l2_camera.cpp.o -c ../src/v4l2/v4l2_camera.cpp In file included from /usr/include/features.h:394, from /usr/include/arm-linux-gnueabihf/c++/13/bits/os_defines.h:39, from /usr/include/arm-linux-gnueabihf/c++/13/bits/c++config.h:679, from /usr/include/c++/13/bits/requires_hosted.h:31, from /usr/include/c++/13/deque:60, from ../src/v4l2/v4l2_camera.h:10, from ../src/v4l2/v4l2_camera.cpp:8: /usr/include/features-time64.h:26:5: error: #error "_TIME_BITS=64 is allowed only with _FILE_OFFSET_BITS=64" 26 | # error "_TIME_BITS=64 is allowed only with _FILE_OFFSET_BITS=64" | ^ [...] (https://launchpad.net/ubuntu/+source/libcamera/0.2.0-1ubuntu3/+build/27902670) Since this is a legitimate un-setting of _FILE_OFFSET_BITS in order to get access to the necessary libc6 prototypes and macros, and since the functions being intercepted are not sensitive to time_t, the simplest solution is to also unset _TIME_BITS. Please see the attached patch, which has been uploaded to Ubuntu to fix this build failure. Thanks for considering, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer https://www.debian.org/ slanga...@ubuntu.com vor...@debian.org diff -Nru libcamera-0.2.0/debian/control libcamera-0.2.0/debian/control --- libcamera-0.2.0/debian/control 2024-01-17 13:27:50.0 -0800 +++ libcamera-0.2.0/debian/control 2024-03-13 22:27:39.0 -0700 @@ -1,7 +1,6 @@ Source: libcamera Priority: optional -Maintainer: Ubuntu Developers -XSBC-Original-Maintainer: Debian Multimedia Maintainers +Maintainer: Debian Multimedia Maintainers Uploaders: Emmanuel Arias , IOhannes m zmölnig (Debian/GNU) , Andr
Processed: Bug#1066836 marked as pending in libcamera
Processing control commands: > tag -1 pending Bug #1066836 [libcamera] libcamera: ftbfs with 64-bit time_t Added tag(s) pending. -- 1066836: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066836 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1066599: marked as done (libquicktime: FTBFS: qtpng.c:74:5: error: implicit declaration of function ‘memcpy’ [-Werror=implicit-function-declaration])
Your message dated Wed, 13 Mar 2024 23:59:37 + with message-id and subject line Bug#1066599: fixed in libquicktime 2:1.2.4-16 has caused the Debian Bug report #1066599, regarding libquicktime: FTBFS: qtpng.c:74:5: error: implicit declaration of function ‘memcpy’ [-Werror=implicit-function-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.) -- 1066599: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066599 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libquicktime Version: 2:1.2.4-15 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This is most likely caused by a change in dpkg 1.22.6, that enabled -Werror=implicit-function-declaration. For more information, see https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration Relevant part (hopefully): > /bin/bash ../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. > -I../.. -I../../include -I../../include -Wdate-time -D_FORTIFY_SOURCE=2 > -I/usr/include/libpng16 -DLOCALE_DIR=\"/usr/share/locale\" -g -O2 > -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. > -fstack-protector-strong -fstack-clash-protection -Wformat > -Werror=format-security -fcf-protection -finline-functions -Wall -Winline > -Wmissing-declarations -Wdeclaration-after-statement -fvisibility=hidden -c > -o lqt_png.lo lqt_png.c > libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -I../../include > -I../../include -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/libpng16 > -DLOCALE_DIR=\"/usr/share/locale\" -g -O2 > -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. > -fstack-protector-strong -fstack-clash-protection -Wformat > -Werror=format-security -fcf-protection -finline-functions -Wall -Winline > -Wmissing-declarations -Wdeclaration-after-statement -fvisibility=hidden -c > lqt_png.c -fPIC -DPIC -o .libs/lqt_png.o > libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -I../../include > -I../../include -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/libpng16 > -DLOCALE_DIR=\"/usr/share/locale\" -g -O2 > -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. > -fstack-protector-strong -fstack-clash-protection -Wformat > -Werror=format-security -fcf-protection -finline-functions -Wall -Winline > -Wmissing-declarations -Wdeclaration-after-statement -fvisibility=hidden -c > qtpng.c -fPIC -DPIC -o .libs/qtpng.o > qtpng.c: In function ‘read_function’: > qtpng.c:74:5: error: implicit declaration of function ‘memcpy’ > [-Werror=implicit-function-declaration] >74 | memcpy(data, codec->buffer + codec->buffer_position, length); > | ^~ > qtpng.c:30:1: note: include ‘’ or provide a declaration of ‘memcpy’ >29 | #include "qtpng.h" > +++ |+#include >30 | > qtpng.c:74:5: warning: incompatible implicit declaration of built-in function > ‘memcpy’ [-Wbuiltin-declaration-mismatch] >74 | memcpy(data, codec->buffer + codec->buffer_position, length); > | ^~ > qtpng.c:74:5: note: include ‘’ or provide a declaration of ‘memcpy’ > qtpng.c: In function ‘write_function’: > qtpng.c:88:3: warning: incompatible implicit declaration of built-in function > ‘memcpy’ [-Wbuiltin-declaration-mismatch] >88 | memcpy(codec->buffer + codec->buffer_size, data, length); > | ^~ > qtpng.c:88:3: note: include ‘’ or provide a declaration of ‘memcpy’ > qtpng.c: In function ‘set_parameter’: > qtpng.c:213:7: error: implicit declaration of function ‘strcasecmp’ > [-Werror=implicit-function-declaration] > 213 | if(!strcasecmp(key, "png_compression_level")) > | ^~ > cc1: some warnings being treated as errors > make[5]: *** [Makefile:532: qtpng.lo] Error 1 The full build log is available from: http://qa-logs.debian.net/2024/03/13/libquicktime_1.2.4-15_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240313;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240313=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://w
Processed: forcibly merging 1066233 1065781
Processing commands for cont...@bugs.debian.org:
> forcemerge 1066233 1065781
Bug #1066233 [src:libmpeg3] libmpeg3: FTBFS: audio/synthesizers.c:36:9: error:
implicit declaration of function ‘mpeg3audio_dct64’; did you mean
‘mpeg3audio_dopcm’? [-Werror=implicit-function-declaration]
Bug #1065781 [src:libmpeg3] libmpeg3: FTBFS on arm{el,hf}:
audio/synthesizers.c:36:9: error: implicit declaration of function
‘mpeg3audio_dct64’; did you mean ‘mpeg3audio_dopcm’?
[-Werror=implicit-function-declaration]
Added tag(s) trixie and sid.
Merged 1065781 1066233
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1065781: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065781
1066233: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066233
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed:
Processing control commands: > severity -1 wishlist Bug #1020755 [src:rotter] rotter: reproducible-builds: Embedded build path in /usr/bin/rotter Severity set to 'wishlist' from 'normal' -- 1020755: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020755 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed:
Processing control commands: > severity -1 wishlist Bug #1039623 [src:shotcut] shotcut: reproducible-builds: build paths trigger differences, embedded date-based version Severity set to 'wishlist' from 'normal' -- 1039623: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039623 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: ffmpeg: reproducible builds: Embeds build path in binaries generated with cl2c
Processing control commands: > fixed -1 7:6.1-1 Bug #985187 [src:ffmpeg] ffmpeg: reproducible builds: Embeds build path in binaries generated with cl2c Marked as fixed in versions ffmpeg/7:6.1-1. > close -1 Bug #985187 [src:ffmpeg] ffmpeg: reproducible builds: Embeds build path in binaries generated with cl2c Marked Bug as done -- 985187: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985187 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1061501: marked as done (libvorbis: Please disable test-coupling-segfault autopkgtest on armhf)
Your message dated Sun, 10 Mar 2024 09:34:09 +0100 with message-id <4f5ebd02-daf6-446a-91d1-20abf4838...@debian.org> and subject line has caused the Debian Bug report #1061501, regarding libvorbis: Please disable test-coupling-segfault autopkgtest on armhf 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.) -- 1061501: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061501 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libvorbis Version: 1.3.7-1 Severity: serious User: debian-...@lists.debian.org Usertags: 32bit-stackclash Tags: patch Hi, the autopkgtest test-coupling-segfault currently fails on armhf due to valgrind bug https://bugs.debian.org/1061496. Please disable the test for now, it can be re-enabled once the valgrind issue is fixed. Patch attached. Thanks, Emanuele diff -Nru libvorbis-1.3.7/debian/changelog libvorbis-1.3.7/debian/changelog --- libvorbis-1.3.7/debian/changelog 2020-09-27 16:13:53.0 +0200 +++ libvorbis-1.3.7/debian/changelog 2024-01-25 16:25:09.0 +0100 @@ -1,3 +1,11 @@ +libvorbis (1.3.7-1.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Disable test-coupling-segfault on armhf due to valgrind bug #1061496. +(Closes: #XXX) + + -- Emanuele Rocca Thu, 25 Jan 2024 16:25:09 +0100 + libvorbis (1.3.7-1) unstable; urgency=medium * Team upload diff -Nru libvorbis-1.3.7/debian/tests/control libvorbis-1.3.7/debian/tests/control --- libvorbis-1.3.7/debian/tests/control 2020-09-27 16:05:13.0 +0200 +++ libvorbis-1.3.7/debian/tests/control 2024-01-25 16:24:06.0 +0100 @@ -1,2 +1,6 @@ -Depends: @, vorbis-tools, build-essential, sound-theme-freedesktop, sound-icons, valgrind -Tests: test-examples test-coupling-segfault +Depends: @, vorbis-tools, build-essential, sound-theme-freedesktop +Tests: test-examples + +Depends: @, vorbis-tools, sound-icons, valgrind +Tests: test-coupling-segfault +Architecture: !armhf --- End Message --- --- Begin Message --- Version: 1.3.7-2 OpenPGP_signature.asc Description: OpenPGP digital signature --- End Message ---
Processed: Bug#1042996 marked as pending in kodi
Processing control commands: > tag -1 pending Bug #1042996 [kodi] kodi: Kodi autoinstalls 77 unremovable language addons Ignoring request to alter tags of bug #1042996 to the same tags previously set -- 1042996: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042996 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: closing 1065423
Processing commands for cont...@bugs.debian.org:
> # no action from the maintainer required
> close 1065423
Bug #1065423 {Done: Sebastian Ramacher }
[vlc-plugin-pipewire] vlc-plugin-pipewire uninstallable in unstable after vlc
time_t transition
Bug 1065423 is already marked as done; not doing anything.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1065423: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065423
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: closing 1065423
Processing commands for cont...@bugs.debian.org: > close 1065423 Bug #1065423 [vlc-plugin-pipewire] vlc-plugin-pipewire uninstallable in unstable after vlc time_t transition Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1065423: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065423 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 1060467 is important, severity of 1060469 is important, severity of 1060471 is important ...
1060605 1060608: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060608 1060610: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060610 1060611: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060611 1060614: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060614 1060621: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060621 1060623: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060623 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1065318: marked as done (mplayer: Package is not installable due to dependency on libsmbclient)
Your message dated Sat, 2 Mar 2024 17:45:08 +0100 with message-id and subject line Re: Bug#1065318: mplayer: Package is not installable due to dependency on libsmbclient has caused the Debian Bug report #1065318, regarding mplayer: Package is not installable due to dependency on libsmbclient 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.) -- 1065318: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065318 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: mplayer Severity: grave Justification: renders package unusable X-Debbugs-Cc: benjamin.poir...@gmail.com Dear Maintainer, The mplayer package is currently not installable in Sid: root@vsid:/tmp# apt install mplayer Reading package lists... Done Building dependency tree... Done Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libsmbclient : Depends: samba-libs (= 2:4.19.5+dfsg-1) but 2:4.19.5+dfsg-3 is to be installed libsmbclient0 : Breaks: libsmbclient (< 2:4.19.5+dfsg-3) but 2:4.19.5+dfsg-1 is to be installed E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages. I guess this problem is related to this change noted in the samba changelog: samba (2:4.19.5+dfsg-2) unstable; urgency=medium * rename libsmbclient => libsmbclient0 for 64-bit time_t transition Closes: #1064337 I rebuilt the mplayer package from source (version 1.5+svn38446) without any change. The resulting .deb had a dependency on libsmbclient0 (>= 2:4.0.3+dfsg1) and I was able to install it without further effort. Thank you -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.6.15-amd64 (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_WARN Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages mplayer depends on: ii liba52-0.7.4 0.7.4-20+b1 ii libaa11.4p5-51 ii libasound2t64 [libasound2]1.2.11-1 ii libass9 1:0.17.1-2 ii libaudio2 1.9.4-7+b1 ii libavcodec60 7:6.1.1-2 ii libavformat60 7:6.1.1-2 ii libavutil58 7:6.1.1-2 ii libbluray21:1.3.4-1 ii libbs2b0 3.1.0+dfsg-7 ii libc6 2.37-15.1 ii libcaca0 0.99.beta20-4 ii libcdio-cdda2 10.2+2.0.1-1 ii libcdio-paranoia2 10.2+2.0.1-1 ii libcdio19 2.1.0-4 ii libdca0 0.0.7-2 ii libdv41.0.0-17 ii libdvdnav46.1.1-1 ii libdvdread8 6.1.3-1 ii libegl1 1.7.0-1 pn libenca0 ii libfaad2 2.11.1-1+b1 ii libfontconfig12.15.0-1 ii libfreetype6 2.13.2+dfsg-1+b1 ii libfribidi0 1.0.13-3+b1 ii libgif7 5.2.2-1 ii libgl11.7.0-1 ii libjack-jackd2-0 [libjack-0.125] 1.9.21~dfsg-3+b1 ii libjpeg62-turbo 1:2.1.5-2+b2 ii liblirc-client0t64 [liblirc-client0] 0.10.2-0.7 ii libmad0 0.15.1b-10.1+b1 ii libmng1 1.0.10+dfsg-3.1+b5 ii libmpeg2-40.5.1-9+b1 ii libmpg123-0 1.32.5-1 ii libogg0 1.3.5-3 ii libopenal11:1.23.1-4+b1 ii libpng16-16t64 [libpng16-16] 1.6.43-3 ii libpostproc57 7:6.1.1-2 ii libpulse0 16.1+dfsg1-3 pn libsdl1.2debian pn libsmbclient ii libsndio7.0 1.9.0-0.3+b3 ii
Bug#1063107: marked as done (openvdb: NMU diff for 64-bit time_t transition)
Your message dated Fri, 01 Mar 2024 19:35:13 +
with message-id
and subject line Bug#1063107: fixed in openvdb 10.0.1-2.1
has caused the Debian Bug report #1063107,
regarding openvdb: NMU diff for 64-bit time_t transition
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.)
--
1063107: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063107
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: openvdb
Version: 10.0.1-2
Severity: serious
Tags: patch pending sid trixie
Justification: library ABI skew on upgrade
User: debian-...@lists.debian.org
Usertags: time-t
NOTICE: these changes must not be uploaded to unstable yet!
Dear maintainer,
As part of the 64-bit time_t transition required to support 32-bit
architectures in 2038 and beyond
(https://wiki.debian.org/ReleaseGoals/64bit-time), we have identified
openvdb as a source package shipping runtime libraries whose ABI
either is affected by the change in size of time_t, or could not be
analyzed via abi-compliance-checker (and therefore to be on the safe
side we assume is affected).
To ensure that inconsistent combinations of libraries with their
reverse-dependencies are never installed together, it is necessary to
have a library transition, which is most easily done by renaming the
runtime library package.
Since turning on 64-bit time_t is being handled centrally through a change
to the default dpkg-buildflags (https://bugs.debian.org/1037136), it is
important that libraries affected by this ABI change all be uploaded close
together in time. Therefore I have prepared a 0-day NMU for openvdb
which will initially be uploaded to experimental if possible, then to
unstable after packages have cleared binary NEW.
Please find the patch for this NMU attached.
If you have any concerns about this patch, please reach out ASAP. Although
this package will be uploaded to experimental immediately, there will be a
period of several days before we begin uploads to unstable; so if information
becomes available that your package should not be included in the transition,
there is time for us to amend the planned uploads.
-- System Information:
Debian Release: trixie/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 6.2.0-39-generic (SMP w/32 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru openvdb-10.0.1/debian/changelog openvdb-10.0.1/debian/changelog
--- openvdb-10.0.1/debian/changelog 2023-05-04 18:14:05.0 -0300
+++ openvdb-10.0.1/debian/changelog 2024-02-05 01:07:41.0 -0300
@@ -1,3 +1,10 @@
+openvdb (10.0.1-2.1) experimental; urgency=medium
+
+ * Non-maintainer upload.
+ * Rename libraries for 64-bit time_t transition.
+
+ -- Lucas Kanashiro Mon, 05 Feb 2024 01:07:41 -0300
+
openvdb (10.0.1-2) unstable; urgency=medium
* debian/control: Fix dependency of libopenvdb-ax-dev on shared library
diff -Nru openvdb-10.0.1/debian/control openvdb-10.0.1/debian/control
--- openvdb-10.0.1/debian/control 2023-05-04 18:13:36.0 -0300
+++ openvdb-10.0.1/debian/control 2024-02-05 01:07:41.0 -0300
@@ -43,7 +43,10 @@
Standards-Version: 4.6.1
X-Python3-Version: >= 3.7
-Package: libopenvdb10.0
+Package: libopenvdb10.0t64
+Provides: ${t64:Provides}
+Replaces: libopenvdb10.0
+Breaks: libopenvdb10.0 (<< ${source:Version})
Multi-Arch: same
Architecture: any
Depends: ${misc:Depends}, ${shlibs:Depends}
@@ -57,7 +60,10 @@
.
This package contains the libraries needed to run OpenVDB applications
-Package: libopenvdb-ax10.0
+Package: libopenvdb-ax10.0t64
+Provides: ${t64:Provides}
+Replaces: libopenvdb-ax10.0
+Breaks: libopenvdb-ax10.0 (<< ${source:Version})
Multi-Arch: same
Architecture: amd64 arm64 armel armhf i386 mips64el ppc64el s390x arc
hurd-i386 ia64 kfreebsd-amd64 kfreebsd-i386 m68k powerpc ppc64 riscv64 sh4
sparc64 x32
Depends: ${misc:Depends}, ${shlibs:Depends}
@@ -76,7 +82,7 @@
Section: libdevel
Depends: libblosc-dev,
libimath-dev,
- libopenvdb10.0 (= ${binary:Version}),
+ libopenvdb10.0t64 (= ${binary:Version}),
libtbb-dev,
${misc:Depends}
Description: Sparse Volume Processing toolkit - dev
@@ -93,7 +99,7 @@
Section: libdevel
Depends: libblosc-dev,
libimath-dev,
- libopenvdb-ax10.0 (= ${binary:Version}),
+ libop
Bug#1063139: marked as done (mjpegtools: NMU diff for 64-bit time_t transition)
Your message dated Fri, 01 Mar 2024 12:52:37 +
with message-id
and subject line Bug#1063139: fixed in mjpegtools 1:2.1.0+debian-8.1
has caused the Debian Bug report #1063139,
regarding mjpegtools: NMU diff for 64-bit time_t transition
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.)
--
1063139: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063139
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mjpegtools
Version: 1:2.1.0+debian-8
Severity: serious
Tags: patch pending sid trixie
Justification: library ABI skew on upgrade
User: debian-...@lists.debian.org
Usertags: time-t
NOTICE: these changes must not be uploaded to unstable yet!
Dear maintainer,
As part of the 64-bit time_t transition required to support 32-bit
architectures in 2038 and beyond
(https://wiki.debian.org/ReleaseGoals/64bit-time), we have identified
mjpegtools as a source package shipping runtime libraries whose ABI
either is affected by the change in size of time_t, or could not be
analyzed via abi-compliance-checker (and therefore to be on the safe
side we assume is affected).
To ensure that inconsistent combinations of libraries with their
reverse-dependencies are never installed together, it is necessary to
have a library transition, which is most easily done by renaming the
runtime library package.
Since turning on 64-bit time_t is being handled centrally through a change
to the default dpkg-buildflags (https://bugs.debian.org/1037136), it is
important that libraries affected by this ABI change all be uploaded close
together in time. Therefore I have prepared a 0-day NMU for mjpegtools
which will initially be uploaded to experimental if possible, then to
unstable after packages have cleared binary NEW.
Please find the patch for this NMU attached.
If you have any concerns about this patch, please reach out ASAP. Although
this package will be uploaded to experimental immediately, there will be a
period of several days before we begin uploads to unstable; so if information
becomes available that your package should not be included in the transition,
there is time for us to amend the planned uploads.
-- System Information:
Debian Release: trixie/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 6.5.0-14-generic (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru mjpegtools-2.1.0+debian/debian/changelog
mjpegtools-2.1.0+debian/debian/changelog
--- mjpegtools-2.1.0+debian/debian/changelog2023-11-20 21:28:47.0
+
+++ mjpegtools-2.1.0+debian/debian/changelog2024-02-05 08:31:21.0
+
@@ -1,3 +1,10 @@
+mjpegtools (1:2.1.0+debian-8.1) experimental; urgency=medium
+
+ * Non-maintainer upload.
+ * Rename libraries for 64-bit time_t transition.
+
+ -- Steve Langasek Mon, 05 Feb 2024 08:31:21 +
+
mjpegtools (1:2.1.0+debian-8) unstable; urgency=medium
* Team upload
diff -Nru mjpegtools-2.1.0+debian/debian/control
mjpegtools-2.1.0+debian/debian/control
--- mjpegtools-2.1.0+debian/debian/control 2023-11-20 21:28:47.0
+
+++ mjpegtools-2.1.0+debian/debian/control 2024-02-05 08:31:14.0
+
@@ -33,12 +33,12 @@
Multi-Arch: same
Architecture: any
Depends:
- liblavfile-2.1-0 (= ${binary:Version}),
- liblavjpeg-2.1-0 (= ${binary:Version}),
- liblavplay-2.1-0 (= ${binary:Version}),
- libmjpegutils-2.1-0 (= ${binary:Version}),
- libmpeg2encpp-2.1-0 (= ${binary:Version}),
- libmplex2-2.1-0 (= ${binary:Version}),
+ liblavfile-2.1-0t64 (= ${binary:Version}),
+ liblavjpeg-2.1-0t64 (= ${binary:Version}),
+ liblavplay-2.1-0t64 (= ${binary:Version}),
+ libmjpegutils-2.1-0t64 (= ${binary:Version}),
+ libmpeg2encpp-2.1-0t64 (= ${binary:Version}),
+ libmplex2-2.1-0t64 (= ${binary:Version}),
${misc:Depends}
Description: MJPEG capture/editing/replay and MPEG encoding toolset
(development)
The mjpeg programs are a set of tools that can do recording of videos and
@@ -47,7 +47,10 @@
.
This package contains the development files.
-Package: liblavfile-2.1-0
+Package: liblavfile-2.1-0t64
+Provides: ${t64:Provides}
+Replaces: liblavfile-2.1-0
+Breaks: liblavfile-2.1-0 (<< ${source:Version})
Section: libs
Architecture: any
Multi-Arch: same
@@ -61,7 +64,10 @@
.
This package contains the shared lavfile library.
-Package: liblavjpeg-2.1-0
+Package: liblavjpeg-2.1-0t64
+Provides:
Bug#1063127: marked as done (libdvdread: NMU diff for 64-bit time_t transition)
Your message dated Fri, 01 Mar 2024 12:36:45 +
with message-id
and subject line Bug#1063127: fixed in libdvdread 6.1.3-1.1
has caused the Debian Bug report #1063127,
regarding libdvdread: NMU diff for 64-bit time_t transition
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.)
--
1063127: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063127
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libdvdread
Version: 6.1.3-1
Severity: serious
Tags: patch pending sid trixie
Justification: library ABI skew on upgrade
User: debian-...@lists.debian.org
Usertags: time-t
NOTICE: these changes must not be uploaded to unstable yet!
Dear maintainer,
As part of the 64-bit time_t transition required to support 32-bit
architectures in 2038 and beyond
(https://wiki.debian.org/ReleaseGoals/64bit-time), we have identified
libdvdread as a source package shipping runtime libraries whose ABI
either is affected by the change in size of time_t, or could not be
analyzed via abi-compliance-checker (and therefore to be on the safe
side we assume is affected).
To ensure that inconsistent combinations of libraries with their
reverse-dependencies are never installed together, it is necessary to
have a library transition, which is most easily done by renaming the
runtime library package.
Since turning on 64-bit time_t is being handled centrally through a change
to the default dpkg-buildflags (https://bugs.debian.org/1037136), it is
important that libraries affected by this ABI change all be uploaded close
together in time. Therefore I have prepared a 0-day NMU for libdvdread
which will initially be uploaded to experimental if possible, then to
unstable after packages have cleared binary NEW.
Please find the patch for this NMU attached.
If you have any concerns about this patch, please reach out ASAP. Although
this package will be uploaded to experimental immediately, there will be a
period of several days before we begin uploads to unstable; so if information
becomes available that your package should not be included in the transition,
there is time for us to amend the planned uploads.
-- System Information:
Debian Release: trixie/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 6.5.0-14-generic (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru libdvdread-6.1.3/debian/changelog libdvdread-6.1.3/debian/changelog
--- libdvdread-6.1.3/debian/changelog 2022-06-08 17:04:02.0 +
+++ libdvdread-6.1.3/debian/changelog 2024-02-05 07:53:51.0 +
@@ -1,3 +1,10 @@
+libdvdread (6.1.3-1.1) experimental; urgency=medium
+
+ * Non-maintainer upload.
+ * Rename libraries for 64-bit time_t transition.
+
+ -- Steve Langasek Mon, 05 Feb 2024 07:53:51 +
+
libdvdread (6.1.3-1) unstable; urgency=medium
* Team upload
diff -Nru libdvdread-6.1.3/debian/control libdvdread-6.1.3/debian/control
--- libdvdread-6.1.3/debian/control 2022-06-08 16:53:30.0 +
+++ libdvdread-6.1.3/debian/control 2024-02-05 07:53:51.0 +
@@ -11,7 +11,10 @@
Vcs-Git: https://salsa.debian.org/multimedia-team/libdvdread.git
Rules-Requires-Root: no
-Package: libdvdread8
+Package: libdvdread8t64
+Provides: ${t64:Provides}
+Replaces: libdvdread8
+Breaks: libdvdread8 (<< ${source:Version})
Section: libs
Architecture: any
Multi-Arch: same
@@ -30,7 +33,7 @@
Section: libdevel
Architecture: any
Multi-Arch: same
-Depends: libdvdread8 (= ${binary:Version}), pkg-config, ${misc:Depends}
+Depends: libdvdread8t64 (= ${binary:Version}), pkg-config, ${misc:Depends}
Suggests: libdvdcss-dev
Description: library for reading DVDs (development)
libdvdread provides the functionality that is required to access many DVDs. It
diff -Nru libdvdread-6.1.3/debian/libdvdread8.bug-control
libdvdread-6.1.3/debian/libdvdread8.bug-control
--- libdvdread-6.1.3/debian/libdvdread8.bug-control 2022-06-08
16:47:06.0 +
+++ libdvdread-6.1.3/debian/libdvdread8.bug-control 1970-01-01
00:00:00.0 +
@@ -1 +0,0 @@
-Report-With: libdvdnav4 libdvdcss2
diff -Nru libdvdread-6.1.3/debian/libdvdread8.docs
libdvdread-6.1.3/debian/libdvdread8.docs
--- libdvdread-6.1.3/debian/libdvdread8.docs2022-06-08 16:47:06.0
+
+++ libdvdread-6.1.3/debian/libdvdread8.docs1970-01-01 00:00:00.0
+
@@ -1 +0,0 @@
-debia
Bug#1063114: marked as done (flac: NMU diff for 64-bit time_t transition)
Your message dated Fri, 01 Mar 2024 12:20:47 +
with message-id
and subject line Bug#1063114: fixed in flac 1.4.3+ds-2.1
has caused the Debian Bug report #1063114,
regarding flac: NMU diff for 64-bit time_t transition
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.)
--
1063114: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063114
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: flac
Version: 1.4.3+ds-2
Severity: serious
Tags: patch pending sid trixie
Justification: library ABI skew on upgrade
User: debian-...@lists.debian.org
Usertags: time-t
NOTICE: these changes must not be uploaded to unstable yet!
Dear maintainer,
As part of the 64-bit time_t transition required to support 32-bit
architectures in 2038 and beyond
(https://wiki.debian.org/ReleaseGoals/64bit-time), we have identified
flac as a source package shipping runtime libraries whose ABI
either is affected by the change in size of time_t, or could not be
analyzed via abi-compliance-checker (and therefore to be on the safe
side we assume is affected).
To ensure that inconsistent combinations of libraries with their
reverse-dependencies are never installed together, it is necessary to
have a library transition, which is most easily done by renaming the
runtime library package.
Since turning on 64-bit time_t is being handled centrally through a change
to the default dpkg-buildflags (https://bugs.debian.org/1037136), it is
important that libraries affected by this ABI change all be uploaded close
together in time. Therefore I have prepared a 0-day NMU for flac
which will initially be uploaded to experimental if possible, then to
unstable after packages have cleared binary NEW.
Please find the patch for this NMU attached.
If you have any concerns about this patch, please reach out ASAP. Although
this package will be uploaded to experimental immediately, there will be a
period of several days before we begin uploads to unstable; so if information
becomes available that your package should not be included in the transition,
there is time for us to amend the planned uploads.
-- System Information:
Debian Release: trixie/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 6.5.0-14-generic (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru flac-1.4.3+ds/debian/changelog flac-1.4.3+ds/debian/changelog
--- flac-1.4.3+ds/debian/changelog 2023-07-03 06:43:49.0 +
+++ flac-1.4.3+ds/debian/changelog 2024-02-05 06:15:30.0 +
@@ -1,3 +1,10 @@
+flac (1.4.3+ds-2.1) experimental; urgency=medium
+
+ * Non-maintainer upload.
+ * Rename libraries for 64-bit time_t transition.
+
+ -- Steve Langasek Mon, 05 Feb 2024 06:15:30 +
+
flac (1.4.3+ds-2) unstable; urgency=medium
[ Adrian Bunk ]
diff -Nru flac-1.4.3+ds/debian/control flac-1.4.3+ds/debian/control
--- flac-1.4.3+ds/debian/control2023-07-03 06:38:51.0 +
+++ flac-1.4.3+ds/debian/control2024-02-05 06:15:30.0 +
@@ -37,7 +37,10 @@
This package contains the command-line tools flac (used for encoding and
decoding FLACs) and metaflac (used for manipulating FLAC metadata.)
-Package: libflac12
+Package: libflac12t64
+Provides: ${t64:Provides}
+Replaces: libflac12
+Breaks: libflac12 (<< ${source:Version})
Section: libs
Architecture: any
Multi-Arch: same
@@ -89,7 +92,7 @@
Architecture: any
Multi-Arch: same
Depends:
- libflac12 (= ${binary:Version}),
+ libflac12t64 (= ${binary:Version}),
libogg-dev,
${misc:Depends},
Description: Free Lossless Audio Codec - C development library
diff -Nru flac-1.4.3+ds/debian/libflac12.install
flac-1.4.3+ds/debian/libflac12.install
--- flac-1.4.3+ds/debian/libflac12.install 2022-10-26 05:37:11.0
+
+++ flac-1.4.3+ds/debian/libflac12.install 1970-01-01 00:00:00.0
+
@@ -1 +0,0 @@
-usr/lib/*/libFLAC.so.*
diff -Nru flac-1.4.3+ds/debian/libflac12.symbols
flac-1.4.3+ds/debian/libflac12.symbols
--- flac-1.4.3+ds/debian/libflac12.symbols 2023-06-27 10:04:07.0
+
+++ flac-1.4.3+ds/debian/libflac12.symbols 1970-01-01 00:00:00.0
+
@@ -1,298 +0,0 @@
-libFLAC.so.12 libflac12 #MINVER#
-* Build-Depends-Package: libflac-dev
- FLAC_API_SUPPORTS_OGG_FLAC@Base 1.3.0
- FLAC__ChannelAssignmentString@Base
Bug#1062718: marked as done (qm-dsp: NMU diff for 64-bit time_t transition)
Your message dated Thu, 29 Feb 2024 22:07:57 +
with message-id
and subject line Bug#1062718: fixed in qm-dsp 1.7.1-7.1
has caused the Debian Bug report #1062718,
regarding qm-dsp: NMU diff for 64-bit time_t transition
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.)
--
1062718: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062718
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: qm-dsp
Version: 1.7.1-7
Severity: serious
Tags: patch pending sid trixie
Justification: library ABI skew on upgrade
User: debian-...@lists.debian.org
Usertags: time-t
NOTICE: these changes must not be uploaded to unstable yet!
Dear maintainer,
As part of the 64-bit time_t transition required to support 32-bit
architectures in 2038 and beyond
(https://wiki.debian.org/ReleaseGoals/64bit-time), we have identified
qm-dsp as a source package shipping runtime libraries whose ABI
either is affected by the change in size of time_t, or could not be
analyzed via abi-compliance-checker (and therefore to be on the safe
side we assume is affected).
To ensure that inconsistent combinations of libraries with their
reverse-dependencies are never installed together, it is necessary to
have a library transition, which is most easily done by renaming the
runtime library package.
Since turning on 64-bit time_t is being handled centrally through a change
to the default dpkg-buildflags (https://bugs.debian.org/1037136), it is
important that libraries affected by this ABI change all be uploaded close
together in time. Therefore I have prepared a 0-day NMU for qm-dsp
which will initially be uploaded to experimental if possible, then to
unstable after packages have cleared binary NEW.
Please find the patch for this NMU attached.
If you have any concerns about this patch, please reach out ASAP. Although
this package will be uploaded to experimental immediately, there will be a
period of several days before we begin uploads to unstable; so if information
becomes available that your package should not be included in the transition,
there is time for us to amend the planned uploads.
-- System Information:
Debian Release: trixie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 6.5.0-5-amd64 (SMP w/32 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect
diff -Nru qm-dsp-1.7.1/debian/changelog qm-dsp-1.7.1/debian/changelog
--- qm-dsp-1.7.1/debian/changelog 2024-01-22 08:01:00.0 +
+++ qm-dsp-1.7.1/debian/changelog 2024-02-02 22:15:56.0 +
@@ -1,3 +1,10 @@
+qm-dsp (1.7.1-7.1) experimental; urgency=medium
+
+ * Non-maintainer upload.
+ * Rename libraries for 64-bit time_t transition.
+
+ -- Sergio Durigan Junior Fri, 02 Feb 2024 22:15:56
+
+
qm-dsp (1.7.1-7) unstable; urgency=medium
* B-D on liblapack-dev
diff -Nru qm-dsp-1.7.1/debian/control qm-dsp-1.7.1/debian/control
--- qm-dsp-1.7.1/debian/control 2024-01-22 08:01:00.0 +
+++ qm-dsp-1.7.1/debian/control 2024-02-02 22:15:56.0 +
@@ -16,7 +16,10 @@
Vcs-Git: https://salsa.debian.org/multimedia-team/qm-dsp.git
Vcs-Browser: https://salsa.debian.org/multimedia-team/qm-dsp
-Package: libqm-dsp0
+Package: libqm-dsp0t64
+Provides: ${t64:Provides}
+Replaces: libqm-dsp0
+Breaks: libqm-dsp0 (<< ${source:Version})
Section: libs
Architecture: any
Depends:
@@ -37,7 +40,7 @@
Section: libdevel
Architecture: any
Depends:
- libqm-dsp0 (= ${binary:Version}),
+ libqm-dsp0t64 (= ${binary:Version}),
${misc:Depends},
Multi-Arch: same
Description: Development files (headers) for libqm-dsp library
diff -Nru qm-dsp-1.7.1/debian/libqm-dsp0.install
qm-dsp-1.7.1/debian/libqm-dsp0.install
--- qm-dsp-1.7.1/debian/libqm-dsp0.install 2024-01-22 08:01:00.0
+
+++ qm-dsp-1.7.1/debian/libqm-dsp0.install 1970-01-01 00:00:00.0
+
@@ -1 +0,0 @@
-lib*.so.* /usr/lib/${DEB_HOST_MULTIARCH}
diff -Nru qm-dsp-1.7.1/debian/libqm-dsp0t64.install
qm-dsp-1.7.1/debian/libqm-dsp0t64.install
--- qm-dsp-1.7.1/debian/libqm-dsp0t64.install 1970-01-01 00:00:00.0
+
+++ qm-dsp-1.7.1/debian/libqm-dsp0t64.install 2024-01-22 08:01:00.0
+
@@ -0,0 +1 @@
+lib*.so.* /usr/lib/${DEB_HOST_MULTIARCH}
diff -Nru qm-dsp-1.7.1/debian/libqm-dsp0t64.lintian-overrides
qm-dsp-1.7.1/debian/libqm-dsp0t64.l
Bug#1063296: marked as done (pupnp: NMU diff for 64-bit time_t transition)
Your message dated Thu, 29 Feb 2024 22:06:17 +
with message-id
and subject line Bug#1063296: fixed in pupnp 1:1.14.18-1.1
has caused the Debian Bug report #1063296,
regarding pupnp: NMU diff for 64-bit time_t transition
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.)
--
1063296: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063296
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pupnp
Version: 1:1.14.18-1
Severity: serious
Tags: patch pending sid trixie
Justification: library ABI skew on upgrade
User: debian-...@lists.debian.org
Usertags: time-t
NOTICE: these changes must not be uploaded to unstable yet!
Dear maintainer,
As part of the 64-bit time_t transition required to support 32-bit
architectures in 2038 and beyond
(https://wiki.debian.org/ReleaseGoals/64bit-time), we have identified
pupnp as a source package shipping runtime libraries whose ABI
either is affected by the change in size of time_t, or could not be
analyzed via abi-compliance-checker (and therefore to be on the safe
side we assume is affected).
To ensure that inconsistent combinations of libraries with their
reverse-dependencies are never installed together, it is necessary to
have a library transition, which is most easily done by renaming the
runtime library package.
Since turning on 64-bit time_t is being handled centrally through a change
to the default dpkg-buildflags (https://bugs.debian.org/1037136), it is
important that libraries affected by this ABI change all be uploaded close
together in time. Therefore I have prepared a 0-day NMU for pupnp
which will initially be uploaded to experimental if possible, then to
unstable after packages have cleared binary NEW.
Please find the patch for this NMU attached.
If you have any concerns about this patch, please reach out ASAP. Although
this package will be uploaded to experimental immediately, there will be a
period of several days before we begin uploads to unstable; so if information
becomes available that your package should not be included in the transition,
there is time for us to amend the planned uploads.
-- System Information:
Debian Release: trixie/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 6.5.0-15-generic (SMP w/32 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru pupnp-1.14.18/debian/changelog pupnp-1.14.18/debian/changelog
--- pupnp-1.14.18/debian/changelog 2023-09-02 13:47:27.0 -0300
+++ pupnp-1.14.18/debian/changelog 2024-02-05 23:35:52.0 -0300
@@ -1,3 +1,10 @@
+pupnp (1:1.14.18-1.1) experimental; urgency=medium
+
+ * Non-maintainer upload.
+ * Rename libraries for 64-bit time_t transition.
+
+ -- Lucas Kanashiro Mon, 05 Feb 2024 23:35:52 -0300
+
pupnp (1:1.14.18-1) unstable; urgency=medium
* New upstream version 1.14.18
diff -Nru pupnp-1.14.18/debian/control pupnp-1.14.18/debian/control
--- pupnp-1.14.18/debian/control2023-06-10 09:37:40.0 -0300
+++ pupnp-1.14.18/debian/control2024-02-05 23:35:52.0 -0300
@@ -23,8 +23,8 @@
Architecture: any
Section: libdevel
Depends:
- libixml11 (= ${binary:Version}),
- libupnp17 (= ${binary:Version}),
+ libixml11t64 (= ${binary:Version}),
+ libupnp17t64 (= ${binary:Version}),
${misc:Depends}
Suggests: libupnp-doc
Description: Portable SDK for UPnP Devices, version 1.14 (development files)
@@ -38,7 +38,10 @@
debug versions of libraries needed for development of programs using
uPnP.
-Package: libupnp17
+Package: libupnp17t64
+Provides: ${t64:Provides}
+Replaces: libupnp17
+Breaks: libupnp17 (<< ${source:Version})
Multi-Arch: same
Architecture: any
Section: libs
@@ -51,9 +54,12 @@
Play Device Architecture Specification - see http://www.upnp.org/ for
specifications.
.
- The libupnp17 package contains the runtime library for uPnP.
+ The libupnp17t64 package contains the runtime library for uPnP.
-Package: libixml11
+Package: libixml11t64
+Provides: ${t64:Provides}
+Replaces: libixml11
+Breaks: libixml11 (<< ${source:Version})
Multi-Arch: same
Architecture: any
Section: libs
diff -Nru pupnp-1.14.18/debian/libixml11.install
pupnp-1.14.18/debian/libixml11.install
--- pupnp-1.14.18/debian/libixml11.install 2023-06-10 09:37:40.0
-0300
+++ pupnp-1.14.18/debian/libixml11.install 1969-12-31 21:00:00.
Bug#1063286: marked as done (portsmf: NMU diff for 64-bit time_t transition)
Your message dated Thu, 29 Feb 2024 22:04:54 +
with message-id
and subject line Bug#1063286: fixed in portsmf 0.1~svn20101010-6.1
has caused the Debian Bug report #1063286,
regarding portsmf: NMU diff for 64-bit time_t transition
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.)
--
1063286: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063286
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: portsmf
Version: 0.1~svn20101010-6
Severity: serious
Tags: patch pending sid trixie
Justification: library ABI skew on upgrade
User: debian-...@lists.debian.org
Usertags: time-t
NOTICE: these changes must not be uploaded to unstable yet!
Dear maintainer,
As part of the 64-bit time_t transition required to support 32-bit
architectures in 2038 and beyond
(https://wiki.debian.org/ReleaseGoals/64bit-time), we have identified
portsmf as a source package shipping runtime libraries whose ABI
either is affected by the change in size of time_t, or could not be
analyzed via abi-compliance-checker (and therefore to be on the safe
side we assume is affected).
To ensure that inconsistent combinations of libraries with their
reverse-dependencies are never installed together, it is necessary to
have a library transition, which is most easily done by renaming the
runtime library package.
Since turning on 64-bit time_t is being handled centrally through a change
to the default dpkg-buildflags (https://bugs.debian.org/1037136), it is
important that libraries affected by this ABI change all be uploaded close
together in time. Therefore I have prepared a 0-day NMU for portsmf
which will initially be uploaded to experimental if possible, then to
unstable after packages have cleared binary NEW.
Please find the patch for this NMU attached.
If you have any concerns about this patch, please reach out ASAP. Although
this package will be uploaded to experimental immediately, there will be a
period of several days before we begin uploads to unstable; so if information
becomes available that your package should not be included in the transition,
there is time for us to amend the planned uploads.
-- System Information:
Debian Release: trixie/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 6.5.0-15-generic (SMP w/32 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru portsmf-0.1~svn20101010/debian/changelog
portsmf-0.1~svn20101010/debian/changelog
--- portsmf-0.1~svn20101010/debian/changelog2021-08-15 12:14:13.0
-0300
+++ portsmf-0.1~svn20101010/debian/changelog2024-02-05 22:54:08.0
-0300
@@ -1,3 +1,10 @@
+portsmf (0.1~svn20101010-6.1) experimental; urgency=medium
+
+ * Non-maintainer upload.
+ * Rename libraries for 64-bit time_t transition.
+
+ -- Lucas Kanashiro Mon, 05 Feb 2024 22:54:08 -0300
+
portsmf (0.1~svn20101010-6) unstable; urgency=medium
* Team upload.
diff -Nru portsmf-0.1~svn20101010/debian/control
portsmf-0.1~svn20101010/debian/control
--- portsmf-0.1~svn20101010/debian/control 2021-08-15 12:10:27.0
-0300
+++ portsmf-0.1~svn20101010/debian/control 2024-02-05 22:54:08.0
-0300
@@ -9,7 +9,10 @@
Vcs-Browser: https://salsa.debian.org/multimedia-team/portsmf
Vcs-Git: https://salsa.debian.org/multimedia-team/portsmf.git
-Package: libportsmf0
+Package: libportsmf0t64
+Provides: ${t64:Provides}
+Replaces: libportsmf0
+Breaks: libportsmf0 (<< ${source:Version})
Architecture: any
Multi-Arch: same
Pre-Depends: ${misc:Pre-Depends}
@@ -35,7 +38,7 @@
Section: libdevel
Architecture: any
Multi-Arch: same
-Depends: libportsmf0 (= ${binary:Version}), ${misc:Depends}
+Depends: libportsmf0t64 (= ${binary:Version}), ${misc:Depends}
Description: Portable Standard Midi File Library (development files)
Portsmf is "Port Standard MIDI File", a cross-platform, C++ library for
reading
and writing Standard MIDI Files.
diff -Nru portsmf-0.1~svn20101010/debian/libportsmf0.install
portsmf-0.1~svn20101010/debian/libportsmf0.install
--- portsmf-0.1~svn20101010/debian/libportsmf0.install 2021-08-15
12:10:27.0 -0300
+++ portsmf-0.1~svn20101010/debian/libportsmf0.install 1969-12-31
21:00:00.0 -0300
@@ -1 +0,0 @@
-usr/lib/*/libportSMF.so.0*
diff -Nru portsmf-0.1~svn20101010/debian/libportsmf0t64.install
portsmf-0.1~svn20101010/debian/libpor
Bug#1062935: marked as done (swami: NMU diff for 64-bit time_t transition)
Your message dated Thu, 29 Feb 2024 18:45:04 +
with message-id
and subject line Bug#1062935: fixed in swami 2.2.2-2.1
has caused the Debian Bug report #1062935,
regarding swami: NMU diff for 64-bit time_t transition
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.)
--
1062935: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062935
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: swami
Version: 2.2.2-2
Severity: serious
Tags: patch pending sid trixie
Justification: library ABI skew on upgrade
User: debian-...@lists.debian.org
Usertags: time-t
NOTICE: these changes must not be uploaded to unstable yet!
Dear maintainer,
As part of the 64-bit time_t transition required to support 32-bit
architectures in 2038 and beyond
(https://wiki.debian.org/ReleaseGoals/64bit-time), we have identified
swami as a source package shipping runtime libraries whose ABI
either is affected by the change in size of time_t, or could not be
analyzed via abi-compliance-checker (and therefore to be on the safe
side we assume is affected).
To ensure that inconsistent combinations of libraries with their
reverse-dependencies are never installed together, it is necessary to
have a library transition, which is most easily done by renaming the
runtime library package.
Since turning on 64-bit time_t is being handled centrally through a change
to the default dpkg-buildflags (https://bugs.debian.org/1037136), it is
important that libraries affected by this ABI change all be uploaded close
together in time. Therefore I have prepared a 0-day NMU for swami
which will initially be uploaded to experimental if possible, then to
unstable after packages have cleared binary NEW.
Please find the patch for this NMU attached.
If you have any concerns about this patch, please reach out ASAP. Although
this package will be uploaded to experimental immediately, there will be a
period of several days before we begin uploads to unstable; so if information
becomes available that your package should not be included in the transition,
there is time for us to amend the planned uploads.
-- System Information:
Debian Release: trixie/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 6.5.0-14-generic (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru swami-2.2.2/debian/changelog swami-2.2.2/debian/changelog
--- swami-2.2.2/debian/changelog2023-10-20 21:29:32.0 +
+++ swami-2.2.2/debian/changelog2024-02-04 03:16:40.0 +
@@ -1,3 +1,10 @@
+swami (2.2.2-2.1) experimental; urgency=medium
+
+ * Non-maintainer upload.
+ * Rename libraries for 64-bit time_t transition.
+
+ -- Steve Langasek Sun, 04 Feb 2024 03:16:40 +
+
swami (2.2.2-2) unstable; urgency=medium
* Team upload
diff -Nru swami-2.2.2/debian/control swami-2.2.2/debian/control
--- swami-2.2.2/debian/control 2023-10-20 21:28:08.0 +
+++ swami-2.2.2/debian/control 2024-02-04 03:16:40.0 +
@@ -33,8 +33,8 @@
Package: swami
Architecture: any
Depends:
- libswami1 (= ${binary:Version}),
- libswamigui1 (= ${binary:Version}),
+ libswami1t64 (= ${binary:Version}),
+ libswamigui1t64 (= ${binary:Version}),
${misc:Depends},
${shlibs:Depends}
Recommends:
@@ -45,7 +45,10 @@
A programming API is also provided for integration with other
applications.
-Package: libswami1
+Package: libswami1t64
+Provides: ${t64:Provides}
+Replaces: libswami1
+Breaks: libswami1 (<< ${source:Version})
Section: libs
Architecture: any
Multi-Arch: same
@@ -60,7 +63,10 @@
.
This package provides the shared library.
-Package: libswamigui1
+Package: libswamigui1t64
+Provides: ${t64:Provides}
+Replaces: libswamigui1
+Breaks: libswamigui1 (<< ${source:Version})
Section: libs
Architecture: any
Multi-Arch: same
@@ -83,8 +89,8 @@
libgnomecanvas2-dev,
libgtk2.0-dev,
libinstpatch-dev,
- libswami1 (= ${binary:Version}),
- libswamigui1 (= ${binary:Version}),
+ libswami1t64 (= ${binary:Version}),
+ libswamigui1t64 (= ${binary:Version}),
${misc:Depends}
Description: MIDI instrument editor - development files
Swami (Sampled Waveforms And Musical Instruments) is an application
diff -Nru swami-2.2.2/debian/libswami1.install
swami-2.2.2/debian/libswami1.install
--- swami-2.2.2/debian/libswami1.install2023-10-20 21:26:05.0
+
+++ swami-
Bug#1062907: marked as done (sndobj: NMU diff for 64-bit time_t transition)
Your message dated Thu, 29 Feb 2024 17:48:54 +
with message-id
and subject line Bug#1062907: fixed in sndobj 2.6.7+ds1-3.1
has caused the Debian Bug report #1062907,
regarding sndobj: NMU diff for 64-bit time_t transition
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.)
--
1062907: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062907
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sndobj
Version: 2.6.7+ds1-3
Severity: serious
Tags: patch pending sid trixie
Justification: library ABI skew on upgrade
User: debian-...@lists.debian.org
Usertags: time-t
NOTICE: these changes must not be uploaded to unstable yet!
Dear maintainer,
As part of the 64-bit time_t transition required to support 32-bit
architectures in 2038 and beyond
(https://wiki.debian.org/ReleaseGoals/64bit-time), we have identified
sndobj as a source package shipping runtime libraries whose ABI
either is affected by the change in size of time_t, or could not be
analyzed via abi-compliance-checker (and therefore to be on the safe
side we assume is affected).
To ensure that inconsistent combinations of libraries with their
reverse-dependencies are never installed together, it is necessary to
have a library transition, which is most easily done by renaming the
runtime library package.
Since turning on 64-bit time_t is being handled centrally through a change
to the default dpkg-buildflags (https://bugs.debian.org/1037136), it is
important that libraries affected by this ABI change all be uploaded close
together in time. Therefore I have prepared a 0-day NMU for sndobj
which will initially be uploaded to experimental if possible, then to
unstable after packages have cleared binary NEW.
Please find the patch for this NMU attached.
If you have any concerns about this patch, please reach out ASAP. Although
this package will be uploaded to experimental immediately, there will be a
period of several days before we begin uploads to unstable; so if information
becomes available that your package should not be included in the transition,
there is time for us to amend the planned uploads.
-- System Information:
Debian Release: trixie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 6.5.0-5-amd64 (SMP w/32 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect
diff -Nru sndobj-2.6.7+ds1/debian/changelog sndobj-2.6.7+ds1/debian/changelog
--- sndobj-2.6.7+ds1/debian/changelog 2020-03-26 23:19:43.0 +
+++ sndobj-2.6.7+ds1/debian/changelog 2024-02-03 23:09:00.0 +
@@ -1,3 +1,10 @@
+sndobj (2.6.7+ds1-3.1) experimental; urgency=medium
+
+ * Non-maintainer upload.
+ * Rename libraries for 64-bit time_t transition.
+
+ -- Sergio Durigan Junior Sat, 03 Feb 2024 23:09:00
+
+
sndobj (2.6.7+ds1-3) unstable; urgency=medium
* Team upload.
diff -Nru sndobj-2.6.7+ds1/debian/control sndobj-2.6.7+ds1/debian/control
--- sndobj-2.6.7+ds1/debian/control 2020-03-26 23:19:43.0 +
+++ sndobj-2.6.7+ds1/debian/control 2024-02-03 23:09:00.0 +
@@ -23,7 +23,7 @@
Multi-Arch: same
Depends:
fftw-dev,
- libsndobj2v5 (= ${binary:Version}),
+ libsndobj2t64 (= ${binary:Version}),
${misc:Depends},
Description: Sound Object library (development files)
The Sound Object Library is an object-oriented audio processing library.
@@ -32,7 +32,10 @@
.
This package contains the development files.
-Package: libsndobj2v5
+Package: libsndobj2t64
+Provides: ${t64:Provides}
+X-Time64-Compat: libsndobj2v5
+Breaks: libsndobj2v5 (<< ${source:Version})
Section: libs
Architecture: any
Multi-Arch: same
@@ -40,7 +43,7 @@
Depends:
${misc:Depends},
${shlibs:Depends},
-Replaces:
+Replaces:libsndobj2v5,
libsndobj2,
libsndobj2c2,
Conflicts:
diff -Nru sndobj-2.6.7+ds1/debian/libsndobj2t64.lintian-overrides
sndobj-2.6.7+ds1/debian/libsndobj2t64.lintian-overrides
--- sndobj-2.6.7+ds1/debian/libsndobj2t64.lintian-overrides 1970-01-01
00:00:00.0 +
+++ sndobj-2.6.7+ds1/debian/libsndobj2t64.lintian-overrides 2024-02-03
23:09:00.0 +
@@ -0,0 +1 @@
+libsndobj2t64: package-name-doesnt-match-sonames libsndobj2v5
diff -Nru sndobj-2.6.7+ds1/debian/rules sndobj-2.6.7+ds1/debian/rules
--- sndobj-2.6.7+ds1/debian/rules 2020-03-26 23:19:43.0 +
+++ sndobj-2.6.7+ds1/debian/rules 2
