Bug#1004625: marked as done (libextractor: FTBFS with ffmpeg 5.0)
Your message dated Thu, 23 Jun 2022 05:50:02 + with message-id and subject line Bug#1004625: fixed in libextractor 1:1.11-6 has caused the Debian Bug report #1004625, regarding libextractor: FTBFS with ffmpeg 5.0 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.) -- 1004625: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004625 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libextractor Version: 1:1.11-5 Severity: important X-Debbugs-Cc: sramac...@debian.org Tags: sid bookworm ftbfs Usertags: ffmpeg5.0 libextractor FTBFS with ffmpeg 5.0 (available in experimental) | libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -I../../src/include -I../../src/common -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 -I/usr/include/x86_64-linux-gnu -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c thumbnailgtk_extractor.c -fPIC -DPIC -o .libs/libextractor_thumbnailgtk_la-thumbnailgtk_extractor.o | libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -I../../src/include -I../../src/common -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c gif_extractor.c -o gif_extractor.o >/dev/null 2>&1 | thumbnailffmpeg_extractor.c: In function ‘create_thumbnail’: | thumbnailffmpeg_extractor.c:193:3: warning: ‘av_init_packet’ is deprecated [-Wdeprecated-declarations] | 193 | av_init_packet (); | | ^~ | In file included from /usr/include/x86_64-linux-gnu/libavformat/avformat.h:316, | from thumbnailffmpeg_extractor.c:43: | /usr/include/x86_64-linux-gnu/libavcodec/packet.h:506:6: note: declared here | 506 | void av_init_packet(AVPacket *pkt); | | ^~ | thumbnailffmpeg_extractor.c:198:30: warning: assignment discards ‘const’ qualifier from pointer target type [-Wdiscarded-qualifiers] | 198 | if (NULL == (encoder_codec = avcodec_find_encoder (AV_CODEC_ID_MJPEG))) | | ^ | thumbnailffmpeg_extractor.c:335:9: warning: implicit declaration of function ‘avcodec_encode_video2’; did you mean ‘avcodec_encode_subtitle’? [-Wimplicit-function-declaration] | 335 | err = avcodec_encode_video2 (encoder_codec_ctx, | | ^ | | avcodec_encode_subtitle | thumbnailffmpeg_extractor.c: In function ‘extract_image’: | thumbnailffmpeg_extractor.c:432:22: warning: assignment discards ‘const’ qualifier from pointer target type [-Wdiscarded-qualifiers] | 432 | if (NULL == (codec = avcodec_find_decoder (image_codec_id))) | | ^ | thumbnailffmpeg_extractor.c:480:5: warning: ‘av_init_packet’ is deprecated [-Wdeprecated-declarations] | 480 | av_init_packet (); | | ^~ | In file included from /usr/include/x86_64-linux-gnu/libavformat/avformat.h:316, | from thumbnailffmpeg_extractor.c:43: | /usr/include/x86_64-linux-gnu/libavcodec/packet.h:506:6: note: declared here | 506 | void av_init_packet(AVPacket *pkt); | | ^~ | thumbnailffmpeg_extractor.c:483:5: warning: implicit declaration of function ‘avcodec_decode_video2’; did you mean ‘avcodec_decode_subtitle2’? [-Wimplicit-function-declaration] | 483 | avcodec_decode_video2 (codec_ctx, frame, _finished, ); | | ^ | | avcodec_decode_subtitle2 | thumbnailffmpeg_extractor.c: In function ‘extract_video’: | thumbnailffmpeg_extractor.c:610:39: error: ‘AVStream’ has no member named ‘codec’ | 610 | codec_ctx = format_ctx->streams[i]->codec; | | ^~ | thumbnailffmpeg_extractor.c:613:24: warning: assignment discards ‘const’ qualifier from pointer target type [-Wdiscarded-qualifiers] | 613 | if (NULL == (codec = avcodec_find_decoder (codecpar->codec_id))) | |^ | make[5]: *** [Makefile:2273: thumbnailffmpeg_extractor.lo] Error 1 | make[5]: *** Waiting for unfinished jobs | libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -I../../src/include -I../../src/common -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c flac_extractor.c -o flac_extractor.o >/dev/null 2>&1 | libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -I../../src/include -I../../src/common
Bug#1002237: Any chance of re-introduction?
Dear maintainer Is there a chance of re-introduction in bullseye? The package "package-update-indicator" recommends "gnome-packagekit". For this, i created the bug #1010802: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010802 Best regards and thank you Bernhard
Bug#1012600: marked as done (zfs-dkms: Compilation fails. ZFS completely non-functional after latest kernel upgrade.)
Your message dated Thu, 23 Jun 2022 04:06:10 + with message-id and subject line Bug#1012600: fixed in zfs-linux 2.1.5-1 has caused the Debian Bug report #1012600, regarding zfs-dkms: Compilation fails. ZFS completely non-functional after latest kernel upgrade. 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.) -- 1012600: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012600 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: zfs-dkms Version: 2.1.4-1 Severity: grave Tags: ftbfs Justification: renders package unusable X-Debbugs-Cc: mc5...@mclink.it Dear Maintainer, zfs system is completely non-functional due to zfs-dkms kernel module compilation terminating in error. My `/home/` is on zfs and thus I'm restricted to use `root` who has a usable `$HOME`. * What led up to the situation? Routine "apt update && apt upgrade", most likely due to kernel upgrade. After installation system asked for a reboot to complete kernel update. After reboot I got the normal `lightdm` login screen, but I was unable to login. I went to a text console to analyze situation and I found /home/ completely wiped. Also dmesg shows system does not find suitable ZFS moduled and thus is unable to mount pool. * What exactly did you do (or not do) that was effective (or ineffective)? I tried to reinstall the failing package, but there are evident errors visible in `/var/lib/dkms/zfs/2.1.4/build/make.log` I am unsure how I can attach the file here. If I don't manage it I will try to comment on the bug from another machine. System is currently completely unusable. -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.18.0-1-amd64 (SMP w/12 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE 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 zfs-dkms depends on: ii debconf [debconf-2.0] 1.5.79 ii dkms 3.0.3-2 ii file 1:5.41-4 ii libc6-dev [libc-dev] 2.33-7 ii libpython3-stdlib 3.10.4-1+b1 ii lsb-release11.2 ii perl 5.34.0-4 ii python3-distutils 3.10.5-1 Versions of packages zfs-dkms recommends: ii linux-libc-dev 5.18.2-1 ii zfs-zed 2.1.4-1+b1 ii zfsutils-linux 2.1.4-1+b1 Versions of packages zfs-dkms suggests: pn debhelper -- debconf information: zfs-dkms/stop-build-for-32bit-kernel: true zfs-dkms/stop-build-for-unknown-kernel: true * zfs-dkms/note-incompatible-licenses: DKMS make.log for zfs-2.1.4 for kernel 5.18.0-1-amd64 (x86_64) Fri Jun 10 12:50:47 AM CEST 2022 make all-recursive make[1]: Entering directory '/var/lib/dkms/zfs/2.1.4/build' Making all in module make[2]: Entering directory '/var/lib/dkms/zfs/2.1.4/build/module' list='icp lua zstd'; for td in $list; do make -C $td; done make[3]: Entering directory '/var/lib/dkms/zfs/2.1.4/build/module/icp' mkdir -p api core spi io os algs algs/aes algs/edonr algs/modes algs/sha1 algs/sha2 algs/skein asm-x86_64 asm-x86_64/aes asm-x86_64/modes asm-x86_64/sha1 asm-x86_64/sha2 asm-i386 asm-generic make[3]: Leaving directory '/var/lib/dkms/zfs/2.1.4/build/module/icp' make[3]: Entering directory '/var/lib/dkms/zfs/2.1.4/build/module/lua' mkdir -p setjmp make[3]: Leaving directory '/var/lib/dkms/zfs/2.1.4/build/module/lua' make[3]: Entering directory '/var/lib/dkms/zfs/2.1.4/build/module/zstd' mkdir -p lib make[3]: Leaving directory '/var/lib/dkms/zfs/2.1.4/build/module/zstd' make -C /lib/modules/5.18.0-1-amd64/build \ \ M="$PWD" O=/lib/modules/5.18.0-1-amd64/build CONFIG_ZFS=m modules make[3]: Entering directory '/usr/src/linux-headers-5.18.0-1-amd64' CC [M] /var/lib/dkms/zfs/2.1.4/build/module/nvpair/nvpair.o CC [M] /var/lib/dkms/zfs/2.1.4/build/module/lua/lapi.o CC [M] /var/lib/dkms/zfs/2.1.4/build/module/unicode/u8_textprep.o CC [M] /var/lib/dkms/zfs/2.1.4/build/module/unicode/uconv.o CC [M] /var/lib/dkms/zfs/2.1.4/build/module/nvpair/fnvpair.o CC [M] /var/lib/dkms/zfs/2.1.4/build/module/avl/avl.o CC [M] /var/lib/dkms/zfs/2.1.4/build/module/spl/../os/linux/spl/spl-atomic.o CC [M] /var/lib/dkms/zfs/2.1.4/build/module/lua/lauxlib.o CC [M] /var/lib/dkms/zfs/2.1.4/build/module/icp/illumos-crypto.o CC [M] /var/lib/dkms/zfs/2.1.4/build/module/zcommon/cityhash.o CC [M]
Bug#998953: marked as done (scim-skk: missing required debian/rules targets build-arch and/or build-indep)
Your message dated Thu, 23 Jun 2022 01:21:42 + with message-id and subject line Bug#998953: fixed in scim-skk 0.5.2-7.3 has caused the Debian Bug report #998953, regarding scim-skk: missing required debian/rules targets build-arch and/or build-indep 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.) -- 998953: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998953 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: scim-skk Version: 0.5.2-7.2 Severity: important Justification: Debian Policy section 4.9 Tags: bookworm sid User: debian...@lists.debian.org Usertags: missing-build-arch-indep Dear maintainer, Your package does not include build-arch and/or build-indep targets in debian/rules. This is required by Debian Policy section 4.9, since 2012. https://www.debian.org/doc/debian-policy/ch-source.html#main-building-script-debian-rules Please note that this is also a sign that the packaging of this software could benefit from a refresh. For example, packages using 'dh' cannot be affected by this issue. This mass bug filing was discussed on debian-devel@ in https://lists.debian.org/debian-devel/2021/11/msg00052.html . The severity of this bug will be changed to 'serious' after a month. Best, Lucas --- End Message --- --- Begin Message --- Source: scim-skk Source-Version: 0.5.2-7.3 Done: Boyuan Yang We believe that the bug you reported is fixed in the latest version of scim-skk, 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 998...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Boyuan Yang (supplier of updated scim-skk 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: Sun, 12 Jun 2022 20:23:35 -0400 Source: scim-skk Architecture: source Version: 0.5.2-7.3 Distribution: unstable Urgency: high Maintainer: Ikuya Awashiro Changed-By: Boyuan Yang Closes: 998953 1005985 Changes: scim-skk (0.5.2-7.3) unstable; urgency=high . * Non-maintainer upload. * Migrate from dpatch to dh. (Closes: #1005985, #998953) * Refresh packaging: + Bump debhelper compat to v13. + Bump Standards-Version to 4.6.1. + Migrate to "3.0 (quilt)" source format. * debian/patches: Add patch to fix LIBTOOL_EXPORT_OPTIONS. Checksums-Sha1: 228a01c54f7141817f02b6a146a3834d2e35f8b2 1819 scim-skk_0.5.2-7.3.dsc 0ddcad937bbed9d94a0076fded26e197e7d24d21 534157 scim-skk_0.5.2.orig.tar.gz a8e25ad248bc68dcb5f968d1a06037bb10364106 8496 scim-skk_0.5.2-7.3.debian.tar.xz 71abb7d9db3e35fc483c53fa8a598dbf5ddda62b 13951 scim-skk_0.5.2-7.3_amd64.buildinfo Checksums-Sha256: 918dcbb08df7e092715082634e16269d9a38efad6db6cccfd07e02cd80ec1785 1819 scim-skk_0.5.2-7.3.dsc 17e755db22cd135a47381eae6f924f68f2c8d2991cec1a4b635ad294653d7b2d 534157 scim-skk_0.5.2.orig.tar.gz 72bb34645c1a2a7ea2885e56005005e63f26797edc0e42a31bf927971eeaf64b 8496 scim-skk_0.5.2-7.3.debian.tar.xz 242f70b62e32f70654a6de266a12d2861255b3605a879b238e3cc2137637fff6 13951 scim-skk_0.5.2-7.3_amd64.buildinfo Files: f7c791c323f4e034b5c2337208790902 1819 utils optional scim-skk_0.5.2-7.3.dsc 69d789660439c248e507da63c90ad70a 534157 utils optional scim-skk_0.5.2.orig.tar.gz e455be0bf7f55be47bcae9076df225d1 8496 utils optional scim-skk_0.5.2-7.3.debian.tar.xz 4a7b7217c2671c6233579b0bd75496fa 13951 utils optional scim-skk_0.5.2-7.3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAmKmg+sACgkQwpPntGGC Ws4i6g//ZapyDOMEhUhFZecJQ/VX7hu6Wot6EDQ6CsMwCbrrIOJy96rVvn1CyZDC uwCgz2sVeNQcSWqCJJ27RthnUOLFY44onCheNDo217NypNX2vPqJ2IGMGP2wVrfO t3vDFeOHCvJChuc/0ljiAaE+FoOC26wIdoLpTkS2mtv7kRPYvL50Na0lLZgVRhNO GkFIWe8cBA8AP1TxVSuXEWBlRzPo4zqzU6o/BNjHAfTYIIUpxgn1tx2xg2cbn1EH jAv+6gIwJy9y5nCyXwM0ipI+1fruMjyE3fJicHJA+C+BSD+AyzNshVfIR9uAKiTR hb6D6n7RUUlBPEVQ0RIuBVVyH8mXguf83MMyTh5Rq2IT28mK4xSCOPdIB1mnvyUB n5PYbUov+XLLVxye8XGCCl2EXIWsHMzL52xuZVKB29dv3fZDv+m25H4suYC3NpBB wefKiMPuy8nJsU1VvUNuvjy9FkYjCY8m3/Gx8DS2Q2BjykvtCWO84o+B0Ky5P6mR sgAddHKkylFbK5+wA8r+YEX6aOTu+O9esTjXHIZF6MOn/Y4NA53A1nP1cSmGGLYG VY3bBpNoc8NBejc8oGboCOB4ZrrLvWwbovew1hrs1ABovG2P/JYX/LFH/C59RWs8 6JRUMs/d0RY0UzNAdTP67hegTwCuUuUogsDp2x1PF9VRi8+ozM4=
Bug#1005985: marked as done (Please migrate away from dpatch)
Your message dated Thu, 23 Jun 2022 01:21:42 + with message-id and subject line Bug#1005985: fixed in scim-skk 0.5.2-7.3 has caused the Debian Bug report #1005985, regarding Please migrate away from dpatch 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.) -- 1005985: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005985 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: scim-skk Version: 0.5.2-7.2 Severity: serious dpatch is deprecated and will be removed before the bookworm release. Please migrate to source format 3.0 (quilt) instead. --- End Message --- --- Begin Message --- Source: scim-skk Source-Version: 0.5.2-7.3 Done: Boyuan Yang We believe that the bug you reported is fixed in the latest version of scim-skk, 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 1005...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Boyuan Yang (supplier of updated scim-skk 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: Sun, 12 Jun 2022 20:23:35 -0400 Source: scim-skk Architecture: source Version: 0.5.2-7.3 Distribution: unstable Urgency: high Maintainer: Ikuya Awashiro Changed-By: Boyuan Yang Closes: 998953 1005985 Changes: scim-skk (0.5.2-7.3) unstable; urgency=high . * Non-maintainer upload. * Migrate from dpatch to dh. (Closes: #1005985, #998953) * Refresh packaging: + Bump debhelper compat to v13. + Bump Standards-Version to 4.6.1. + Migrate to "3.0 (quilt)" source format. * debian/patches: Add patch to fix LIBTOOL_EXPORT_OPTIONS. Checksums-Sha1: 228a01c54f7141817f02b6a146a3834d2e35f8b2 1819 scim-skk_0.5.2-7.3.dsc 0ddcad937bbed9d94a0076fded26e197e7d24d21 534157 scim-skk_0.5.2.orig.tar.gz a8e25ad248bc68dcb5f968d1a06037bb10364106 8496 scim-skk_0.5.2-7.3.debian.tar.xz 71abb7d9db3e35fc483c53fa8a598dbf5ddda62b 13951 scim-skk_0.5.2-7.3_amd64.buildinfo Checksums-Sha256: 918dcbb08df7e092715082634e16269d9a38efad6db6cccfd07e02cd80ec1785 1819 scim-skk_0.5.2-7.3.dsc 17e755db22cd135a47381eae6f924f68f2c8d2991cec1a4b635ad294653d7b2d 534157 scim-skk_0.5.2.orig.tar.gz 72bb34645c1a2a7ea2885e56005005e63f26797edc0e42a31bf927971eeaf64b 8496 scim-skk_0.5.2-7.3.debian.tar.xz 242f70b62e32f70654a6de266a12d2861255b3605a879b238e3cc2137637fff6 13951 scim-skk_0.5.2-7.3_amd64.buildinfo Files: f7c791c323f4e034b5c2337208790902 1819 utils optional scim-skk_0.5.2-7.3.dsc 69d789660439c248e507da63c90ad70a 534157 utils optional scim-skk_0.5.2.orig.tar.gz e455be0bf7f55be47bcae9076df225d1 8496 utils optional scim-skk_0.5.2-7.3.debian.tar.xz 4a7b7217c2671c6233579b0bd75496fa 13951 utils optional scim-skk_0.5.2-7.3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAmKmg+sACgkQwpPntGGC Ws4i6g//ZapyDOMEhUhFZecJQ/VX7hu6Wot6EDQ6CsMwCbrrIOJy96rVvn1CyZDC uwCgz2sVeNQcSWqCJJ27RthnUOLFY44onCheNDo217NypNX2vPqJ2IGMGP2wVrfO t3vDFeOHCvJChuc/0ljiAaE+FoOC26wIdoLpTkS2mtv7kRPYvL50Na0lLZgVRhNO GkFIWe8cBA8AP1TxVSuXEWBlRzPo4zqzU6o/BNjHAfTYIIUpxgn1tx2xg2cbn1EH jAv+6gIwJy9y5nCyXwM0ipI+1fruMjyE3fJicHJA+C+BSD+AyzNshVfIR9uAKiTR hb6D6n7RUUlBPEVQ0RIuBVVyH8mXguf83MMyTh5Rq2IT28mK4xSCOPdIB1mnvyUB n5PYbUov+XLLVxye8XGCCl2EXIWsHMzL52xuZVKB29dv3fZDv+m25H4suYC3NpBB wefKiMPuy8nJsU1VvUNuvjy9FkYjCY8m3/Gx8DS2Q2BjykvtCWO84o+B0Ky5P6mR sgAddHKkylFbK5+wA8r+YEX6aOTu+O9esTjXHIZF6MOn/Y4NA53A1nP1cSmGGLYG VY3bBpNoc8NBejc8oGboCOB4ZrrLvWwbovew1hrs1ABovG2P/JYX/LFH/C59RWs8 6JRUMs/d0RY0UzNAdTP67hegTwCuUuUogsDp2x1PF9VRi8+ozM4= =jemj -END PGP SIGNATURE End Message ---
Processed: Correct bug closing info
Processing commands for cont...@bugs.debian.org:
> notfixed 1012596 timeshift/22.06.1-0.1
Bug #1012596 {Done: Boyuan Yang } [cron-daemon-common]
cron-daemon-common: missing versioned Breaks+Replaces against bcron,
systemd-cron
The source timeshift and version 22.06.1-0.1 do not appear to match any binary
packages
No longer marked as fixed in versions timeshift/22.06.1-0.1.
> fixed 1012596 cron/3.0pl1-144
Bug #1012596 {Done: Boyuan Yang } [cron-daemon-common]
cron-daemon-common: missing versioned Breaks+Replaces against bcron,
systemd-cron
Marked as fixed in versions cron/3.0pl1-144; no longer marked as fixed in
versions cron/3.0pl1-144.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1012596: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012596
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1012596: marked as done (cron-daemon-common: missing versioned Breaks+Replaces against bcron, systemd-cron)
Your message dated Thu, 23 Jun 2022 00:51:25 + with message-id and subject line Bug#1012596: fixed in timeshift 22.06.1-0.1 has caused the Debian Bug report #1012596, regarding cron-daemon-common: missing versioned Breaks+Replaces against bcron, systemd-cron 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.) -- 1012596: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012596 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: cron-daemon-common Version: 3.0pl1-143 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Selecting previously unselected package cron-daemon-common. Preparing to unpack .../cron-daemon-common_3.0pl1-143_all.deb ... Unpacking cron-daemon-common (3.0pl1-143) ... dpkg: error processing archive /var/cache/apt/archives/cron-daemon-common_3.0pl1-143_all.deb (--unpack): trying to overwrite '/etc/crontab', which is also in package bcron 0.11-9 Errors were encountered while processing: /var/cache/apt/archives/cron-daemon-common_3.0pl1-143_all.deb Selecting previously unselected package cron-daemon-common. Preparing to unpack .../cron-daemon-common_3.0pl1-143_all.deb ... Unpacking cron-daemon-common (3.0pl1-143) ... dpkg: error processing archive /var/cache/apt/archives/cron-daemon-common_3.0pl1-143_all.deb (--unpack): trying to overwrite '/etc/cron.d/.placeholder', which is also in package systemd-cron 1.15.18-1 Errors were encountered while processing: /var/cache/apt/archives/cron-daemon-common_3.0pl1-143_all.deb For bcron the conflicting file is only /etc/crontab For systemd-cron the conflicting files are /etc/cron.d/.placeholder /etc/cron.daily/.placeholder /etc/cron.hourly/.placeholder /etc/cron.monthly/.placeholder /etc/cron.weekly/.placeholder /etc/crontab These two alternative cron implementations need to start using cron-daemon-common for these shared files first before you can add the corresponding Breaks+Replaces against them. cheers, Andreas --- End Message --- --- Begin Message --- Source: timeshift Source-Version: 22.06.1-0.1 Done: Boyuan Yang We believe that the bug you reported is fixed in the latest version of timeshift, 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 1012...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Boyuan Yang (supplier of updated timeshift 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: Sun, 12 Jun 2022 19:46:42 -0400 Source: timeshift Architecture: source Version: 22.06.1-0.1 Distribution: unstable Urgency: medium Maintainer: Yanhao Mo Changed-By: Boyuan Yang Closes: 1012265 1012596 Changes: timeshift (22.06.1-0.1) unstable; urgency=medium . * Non-maintainer upload. * Switch to linuxmint upstream. (Closes: #1012265) (LP: #1976627) * d/control,d/rules,d/u/metadata: Switch upstream info. * New upstream version 22.06.1. * debian/: Apply wrap-and-sort -abst. * debian/control: Bump Standards-Version to 4.6.1. * debian/control: Add new dependency cron-daemon. (Closes: #1012596) * Add new build-dep libxapp-dev. Checksums-Sha1: 6de5497bfb48039e06dca9a04edf305bf42792ba 1988 timeshift_22.06.1-0.1.dsc 96fb9e7a679d0eba9e7d18eb7fb9fc5a8b7f3945 1429399 timeshift_22.06.1.orig.tar.gz 2f89e243b226797d20647c96de6a76f796b1c869 12336 timeshift_22.06.1-0.1.debian.tar.xz bd0e27f99e4320f550a6d35d648e8991b926d8dc 15171 timeshift_22.06.1-0.1_amd64.buildinfo Checksums-Sha256: ff8897abca76eaabcb16a6d625fa7005c1f0abc362a17513e5adf97b939169ab 1988 timeshift_22.06.1-0.1.dsc 8db5a0fa8e8b76f0ecd5490d1d4def31500f44c3efd88af34d498f40bfbbfe95 1429399 timeshift_22.06.1.orig.tar.gz 285b61f42d7339cc1cce5f4fa2fe0de3cf168974f31f7a973577fe5cf3164e55 12336 timeshift_22.06.1-0.1.debian.tar.xz
Bug#1013364: dicomnifti: autopkgtest failure: number of repetitions is less than two
Puzzling, this package has not changed since November 2017. Not sure what I'm supposed to do next. Thanks, On 6/22/22 4:15 PM, Paul Gevers wrote: Source: dicomnifti Version: 2.33.1-4 Severity: serious User: debian...@lists.debian.org Usertags: fails-always Dear maintainer(s), You recently added an autopkgtest to your package dicomnifti, great. However, it fails on i386 and s390x. Currently this failure is blocking the migration to testing [1]. Can you please investigate the situation and fix it? I copied some of the output at the bottom of this report. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=dicomnifti https://ci.debian.net/data/autopkgtest/testing/i386/d/dicomnifti/22218046/log.gz CreateNIfTIHeader: WARNING: number of repetitions is less than two time between volumes is set to zero output.nii: FAILED md5sum: WARNING: 1 computed checksum did NOT match autopkgtest [15:10:43]: test run-unit-test -- Valerio Luccio High Performance Computing 10 Astor Place, Room 416D New York University New York, NY 10003 "In an open world, who needs windows or gates ?"
Bug#1011714: marked as done (python-pygit2: import fails if /usr/lib/ssl/certs does not exist)
Your message dated Wed, 22 Jun 2022 21:37:45 + with message-id and subject line Bug#1011714: fixed in python-pygit2 1.8.0-3 has caused the Debian Bug report #1011714, regarding python-pygit2: import fails if /usr/lib/ssl/certs does not exist 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.) -- 1011714: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011714 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gitless Version: 0.8.8-4 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220525 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > '/<>/debian/run-simple-test.sh' > Using directory /tmp/gitless-test.jVerea > + [ 1 -ne 1 ] > + dir=/tmp/gitless-test.jVerea > + : python3.10 > + : git > + pwd > + : /<>/gl.py > + gl=python3.10 /<>/gl.py > + [ -d /tmp/gitless-test.jVerea ] > + cd /tmp/gitless-test.jVerea > + python3.10 /<>/gl.py init > Traceback (most recent call last): > File "/<>/gl.py", line 10, in > from gitless.cli import gl > File "/<>/gitless/cli/gl.py", line 13, in > import pygit2 > File "/usr/lib/python3/dist-packages/pygit2/__init__.py", line 230, in > > settings = Settings() > File "/usr/lib/python3/dist-packages/pygit2/settings.py", line 55, in > __init__ > self._initialize_tls_certificate_locations() > File "/usr/lib/python3/dist-packages/pygit2/settings.py", line 61, in > _initialize_tls_certificate_locations > self.set_ssl_cert_locations( > File "/usr/lib/python3/dist-packages/pygit2/settings.py", line 191, in > set_ssl_cert_locations > option(_pygit2.GIT_OPT_SET_SSL_CERT_LOCATIONS, cert_file, cert_dir) > ValueError: invalid argument: 'file || path' > make[1]: *** [debian/rules:9: override_dh_auto_test] Error 1 The full build log is available from: http://qa-logs.debian.net/2022/05/25/gitless_0.8.8-4_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220525;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220525=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 marking 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: python-pygit2 Source-Version: 1.8.0-3 Done: Timo Röhling We believe that the bug you reported is fixed in the latest version of python-pygit2, 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 1011...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Timo Röhling (supplier of updated python-pygit2 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, 22 Jun 2022 23:10:20 +0200 Source: python-pygit2 Architecture: source Version: 1.8.0-3 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Timo Röhling Closes: 1011714 Changes: python-pygit2 (1.8.0-3) unstable; urgency=medium . * Team upload. * Depend on openssl (Closes: #1011714) * Bump Standards-Version to 4.6.1 Checksums-Sha1: 8cf9b5cd202c89c41ecb9fe1b7863547d0e04b5d 2218 python-pygit2_1.8.0-3.dsc 0fc240a56f971e9208bab40d4778da2a077cf719 6912 python-pygit2_1.8.0-3.debian.tar.xz 4bcb2335bc7a2fa4b1f0bdf6ff204bc5b2c24a8b 9558 python-pygit2_1.8.0-3_amd64.buildinfo Checksums-Sha256: dbadbe8d6caf66dd92d61cb6fa8ffb6f67c3ad608b969548c73aa4720a256d32 2218 python-pygit2_1.8.0-3.dsc 8fbdfcd35ee5e58f86ecdada6c0283c8a512719ca34d2d4f8d44f8116f8d7d4c 6912 python-pygit2_1.8.0-3.debian.tar.xz 157d26532d2d58389faad172e87e28d601d009266fc438cf86fd0f3fffa6ccdd 9558 python-pygit2_1.8.0-3_amd64.buildinfo Files:
Bug#1001001: linux-image-5.10.0-9-arm64: kernel BUG at include/linux/swapops.h:204!
On Wednesday, 22 June 2022 23:15:46 CEST Diederik de Haas wrote: > Via sources.list.erb I found that "<%= node['debian_release'] %>-backports" > gets enabled, which I assume results in Stable-backports. > It appears that various tools get installed (but I don't see qemu mentioned > (explicitly)), but I do see 'virt-what' and the package description seems to > indicate it may be useful to figure out detail of the VM. Forgot to add: Backports seems available but it needs to be explicitly specified to install packages from it, which _I_ didn't see, but I'm not familiar with your (build) systems. I don't know if it's an option, but stable-bpo has 1:7.0+dfsg-2~bpo11+2 signature.asc Description: This is a digitally signed message part.
Bug#1011714: marked as pending in python-pygit2
Control: tag -1 pending Hello, Bug #1011714 in python-pygit2 reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/packages/python-pygit2/-/commit/8c027a625b4e04e6d7344d299dca415dc5538e6b Depend on openssl Closes: #1011714 (this message was generated automatically) -- Greetings https://bugs.debian.org/1011714
Processed: Bug#1011714 marked as pending in python-pygit2
Processing control commands: > tag -1 pending Bug #1011714 [src:python-pygit2] python-pygit2: import fails if /usr/lib/ssl/certs does not exist Added tag(s) pending. -- 1011714: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011714 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1001001: linux-image-5.10.0-9-arm64: kernel BUG at include/linux/swapops.h:204!
Hi Paul, On Wednesday, 22 June 2022 21:57:06 CEST Paul Gevers wrote: > On 21-06-2022 23:19, Diederik de Haas wrote: > > > I think that the install logs aren't that important (anymore) as the > > issue/symptoms appear to be the same: > > - some swap action resulting in some failure > > - CPU gets stuck > > - watchdog triggers a reboot > > If the reboot would actually happen/finish, I wouldn't have problems of > the hanging host. The issues I spotted required a manual reboot (and > that's why I spotted them). Hmm ...interesting. AFAIK that is a watchdog's task. And I was certain I saw sth about it as I've seen (a yet to be reported) an issue related to watchdog myself, hence why I remembered it. On Saturday, 4 December 2021 22:44:38 CEST Paul Gevers wrote: > I noticed in the logs that *after* the reported kernel bug but before > the actual hang, I see multiple instances of: > watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [apt-get:2204621] > and > watchdog: BUG: soft lockup - CPU#2 stuck for 22s! [kcompactd0:40] > on ci-worker-arm64-07. And here is where I saw it. (My watchdog issue doesn't cause a hang btw) > > How is swap configured on these devices? > > https://salsa.debian.org/ci-team/debian-ci-config/-/blob/master/cookbooks/ba > sics/default.rb#L3 until line 11 Not familiar with Ruby, but IIUC a swap file get created half the size of RAM. I _think_ the swapon command isn't technically needed as it will be done on bootup through fstab, but shouldn't hurt either. Seems fine :) > > I *assumed* it was running on arm64 (native) hardware and was about to > > ask specifics about it and then I noticed this: > > Host bridge [0600]: Red Hat, Inc. QEMU PCIe Host bridge [1b36:0008] > > > > Qemu. Quite likely unrelated, but a while back I had an issue with qemu > > in building arm64 images: https://bugs.debian.org/988174 > > hmm, OK, right (I forgot that I knew this). > > > I think it would be useful to know which qemu version(s) were used. > > Is there any way to know from inside the VM? If you have access to the host, APT should be able to tell you. Via sources.list.erb I found that "<%= node['debian_release'] %>-backports" gets enabled, which I assume results in Stable-backports. It appears that various tools get installed (but I don't see qemu mentioned (explicitly), but I do see 'virt-what' and the package description seems to indicate it may be useful to figure out detail of the VM. @mjt, I have two questions for you: 1) do you know if/how the qemu version can be queried from within the VM? 2) Are you aware of potential issues wrt hangs in arm64 VM created with Qemu? Or IOW, could you take a look at this bug and can you give tips which could help in tracking down the cause and subsequently the solution? TIA, Diederik signature.asc Description: This is a digitally signed message part.
Bug#1013365: python-aiortc: autopkgtest regression on armhf: [Errno 542398533] Generic error in an external library
Source: python-aiortc
Version: 1.3.2-1
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Dear maintainer(s),
With a recent upload of python-aiortc the autopkgtest of python-aiortc
fails in testing on armhf when that autopkgtest is run with the binary
packages of python-aiortc from unstable. It passes when run with only
packages from testing. In tabular form:
passfail
python-aiortc from testing1.3.2-1
all others from testingfrom testing
I copied some of the output at the bottom of this report.
Currently this regression is blocking the migration to testing [1]. Can
you please investigate the situation and fix it?
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[1] https://qa.debian.org/excuses.php?package=python-aiortc
https://ci.debian.net/data/autopkgtest/testing/armhf/p/python-aiortc/22926423/log.gz
=== FAILURES
===
_ MediaRecorderTest.test_video_mp4_uhd
_
self = testMethod=test_video_mp4_uhd>
@asynctest
async def test_video_mp4_uhd(self):
path = self.temporary_path("test.mp4")
recorder = MediaRecorder(path)
recorder.addTrack(VideoStreamTrackUhd())
await recorder.start()
await asyncio.sleep(2)
await recorder.stop()
tests/test_contrib_media.py:651: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
/usr/lib/python3/dist-packages/aiortc/contrib/media.py:383: in stop
for packet in context.stream.encode(None):
av/stream.pyx:164: in av.stream.Stream.encode
???
av/codec/context.pyx:492: in av.codec.context.CodecContext.encode
???
av/codec/context.pyx:411: in
av.codec.context.CodecContext._send_frame_and_recv
???
av/codec/context.pyx:469: in av.codec.context.CodecContext._recv_packet
???
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _
???
E av.error.ExternalError: [Errno 542398533] Generic error in an
external library
av/error.pyx:336: ExternalError
- Captured stderr call
-
[libx264 @ 0x1425410] using cpu capabilities: ARMv6 NEON
[libx264 @ 0x1425410] profile High, level 5.1, 4:2:0, 8-bit
[libx264 @ 0x1425410] 264 - core 164 r3095 baee400 - H.264/MPEG-4 AVC
codec - Copyleft 2003-2022 - http://www.videolan.org/x264.html -
options: cabac=1 ref=3 deblock=1:0:0 analyse=0x3:0x113 me=hex subme=7
psy=1 psy_rd=1.00:0.00 mixed_ref=1 me_range=16 chroma_me=1 trellis=1
8x8dct=1 cqm=0 deadzone=21,11 fast_pskip=1 chroma_qp_offset=-2
threads=33 lookahead_threads=16 sliced_threads=1 slices=33 nr=0
decimate=1 interlaced=0 bluray_compat=0 constrained_intra=0 bframes=3
b_pyramid=2 b_adapt=1 b_bias=0 direct=1 weightb=1 open_gop=0 weightp=2
keyint=250 keyint_min=25 scenecut=40 intra_refresh=0 rc_lookahead=40
rc=abr mbtree=1 bitrate=1024 ratetol=1.0 qcomp=0.60 qpmin=0 qpmax=69
qpstep=4 ip_ratio=1.40 aq=1:1.00
x264 [error]: malloc of size 26198688 failed
x264 [error]: malloc of size 43687792 failed
H264Test.test_encoder
_
self =
frame =
force_keyframe = False
def _encode_frame(
self, frame: av.VideoFrame, force_keyframe: bool
) -> Iterator[bytes]:
if self.codec and (
frame.width != self.codec.width
or frame.height != self.codec.height
# we only adjust bitrate if it changes by over 10%
or abs(self.target_bitrate - self.codec.bit_rate) /
self.codec.bit_rate
> 0.1
):
self.buffer_data = b""
self.buffer_pts = None
self.codec = None
# reset the picture type, otherwise no B-frames are produced
frame.pict_type = av.video.frame.PictureType.NONE
if self.codec is None:
try:
self.codec, self.codec_buffering = create_encoder_context(
"h264_omx", frame.width, frame.height,
bitrate=self.target_bitrate
)
/usr/lib/python3/dist-packages/aiortc/codecs/h264.py:285: _ _ _ _ _ _ _
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
codec_name = 'h264_omx', width = 640, height = 480, bitrate = 100
def create_encoder_context(
codec_name: str, width: int, height: int, bitrate: int
) -> Tuple[av.CodecContext, bool]:
codec = av.CodecContext.create(codec_name, "w")
codec.width = width
codec.height = height
codec.bit_rate = bitrate
codec.pix_fmt = "yuv420p"
codec.framerate = fractions.Fraction(MAX_FRAME_RATE, 1)
codec.time_base = fractions.Fraction(1, MAX_FRAME_RATE)
codec.options = {
"profile": "baseline",
"level": "31",
Processed: severity of 1004579 is serious, severity of 1004594 is serious, severity of 1004596 is serious ...
Processing commands for cont...@bugs.debian.org: > severity 1004579 serious Bug #1004579 [src:mplayer] mplayer: FTBFS with ffmpeg 5.0 Severity set to 'serious' from 'important' > severity 1004594 serious Bug #1004594 [src:qtwebengine-opensource-src] qtwebengine-opensource-src: FTBFS with ffmpeg 5.0 Severity set to 'serious' from 'important' > severity 1004596 serious Bug #1004596 [src:kino] kino: FTBFS with ffmpeg 5.0 Severity set to 'serious' from 'important' > severity 1004597 serious Bug #1004597 [src:amide] amide: FTBFS with ffmpeg 5.0 Severity set to 'serious' from 'important' > severity 1004598 serious Bug #1004598 [src:audacity] audacity: FTBFS with ffmpeg 5.0 Severity set to 'serious' from 'important' > severity 1004612 serious Bug #1004612 [src:kodi] kodi: FTBFS with ffmpeg 5.0 Severity set to 'serious' from 'important' > severity 1004613 serious Bug #1004613 [src:nordlicht] nordlicht: FTBFS with ffmpeg 5.0 Severity set to 'serious' from 'important' > severity 1004616 serious Bug #1004616 [src:performous] performous: FTBFS with ffmpeg 5.0 Severity set to 'serious' from 'important' > severity 1004620 serious Bug #1004620 [src:olive-editor] olive-editor: FTBFS with ffmpeg 5.0 Severity set to 'serious' from 'important' > severity 1004622 serious Bug #1004622 [src:dvbcut] dvbcut: FTBFS with ffmpeg 5.0 Severity set to 'serious' from 'important' > severity 1004625 serious Bug #1004625 [src:libextractor] libextractor: FTBFS with ffmpeg 5.0 Severity set to 'serious' from 'important' > severity 1004626 serious Bug #1004626 [src:forked-daapd] forked-daapd: FTBFS with ffmpeg 5.0 Severity set to 'serious' from 'important' > severity 1004628 serious Bug #1004628 [src:qtav] qtav: FTBFS with ffmpeg 5.0 Severity set to 'serious' from 'important' > severity 1004630 serious Bug #1004630 [src:guvcview] guvcview: FTBFS with ffmpeg 5.0 Severity set to 'serious' from 'important' > severity 1004632 serious Bug #1004632 [src:wxsvg] wxsvg: FTBFS with ffmpeg 5.0 Severity set to 'serious' from 'important' > severity 1004637 serious Bug #1004637 [src:libquicktime] libquicktime: FTBFS with ffmpeg 5.0 Severity set to 'serious' from 'important' > severity 1004638 serious Bug #1004638 [src:openjfx] openjfx: FTBFS with ffmpeg 5.0 Severity set to 'serious' from 'important' > severity 1004642 serious Bug #1004642 [src:moviepy] moviepy: FTBFS with ffmpeg 5.0 Severity set to 'serious' from 'important' > severity 1004719 serious Bug #1004719 [src:shotdetect] shotdetect: FTBFS with ffmpeg 5.0 Severity set to 'serious' from 'important' > severity 1004763 serious Bug #1004763 [src:libopenshot] libopenshot: FTBFS with ffmpeg 5.0 Severity set to 'serious' from 'important' > severity 1004770 serious Bug #1004770 [src:octave-video] octave-video: FTBFS with ffmpeg 5.0 Severity set to 'serious' from 'important' > severity 1004783 serious Bug #1004783 [src:kodi-inputstream-ffmpegdirect] kodi-inputstream-ffmpegdirect: FTBFS in ffmpeg 5.0 Severity set to 'serious' from 'important' > severity 1004784 serious Bug #1004784 [src:aiscm] aiscm: FTBFS with ffmpeg 5.0 Severity set to 'serious' from 'important' > severity 1004794 serious Bug #1004794 [src:bs1770gain] bs1770gain: FTBFS with ffmpeg 5.0 Severity set to 'serious' from 'important' > severity 1004800 serious Bug #1004800 [src:ignition-common3] ignition-common3: FTBFS with ffmpeg 5.0 Severity set to 'serious' from 'important' > severity 1004805 serious Bug #1004805 [src:xmms2] xmms2: FTBFS with ffmpeg 5.0 Severity set to 'serious' from 'important' > severity 1004806 serious Bug #1004806 [src:dolphin-emu] dolphin-emu: FTBFS with ffmpeg 5.0 Severity set to 'serious' from 'important' > severity 1004808 serious Bug #1004808 [src:deepin-music] deepin-music: FTBFS with ffmpeg 5.0 Severity set to 'serious' from 'important' > severity 1004809 serious Bug #1004809 [src:deepin-voice-recorder] deepin-voice-recorder: FTBFS with ffmpeg 5.0 Severity set to 'serious' from 'important' > severity 1004816 serious Bug #1004816 [src:performous-composer] performous-composer: FTBFS with ffmpeg 5.0 Severity set to 'serious' from 'important' > severity 1004817 serious Bug #1004817 [src:paraview] paraview: FTBFS with ffmpeg 5.0 Severity set to 'serious' from 'important' > severity 1004819 serious Bug #1004819 [src:mediastreamer2] mediastreamer2: FTBFS with ffmpeg 5.0 Severity set to 'serious' from 'important' > severity 1004821 serious Bug #1004821 [src:libam7xxx] libam7xxx: FTBFS with ffmpeg 5.0 Severity set to 'serious' from 'important' > severity 1004822 serious Bug #1004822 [src:k3b] k3b: FTBFS with ffmpeg 5.0 Severity set to 'serious' from 'important' > severity 1004823 serious Bug #1004823 [src:info-beamer] info-beamer: FTBFS with ffmpeg 5.0 Severity set to 'serious' from 'important' > severity 1004828 serious Bug #1004828 [src:handbrake] handbrake: FTBFS with ffmpeg 5.0 Severity set to 'serious' from 'important' > severity 1004830 serious Bug #1004830 [src:gerbera] gerbera: FTBFS with ffmpeg 5.0 Severity
Bug#1013364: dicomnifti: autopkgtest failure: number of repetitions is less than two
Source: dicomnifti Version: 2.33.1-4 Severity: serious User: debian...@lists.debian.org Usertags: fails-always Dear maintainer(s), You recently added an autopkgtest to your package dicomnifti, great. However, it fails on i386 and s390x. Currently this failure is blocking the migration to testing [1]. Can you please investigate the situation and fix it? I copied some of the output at the bottom of this report. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=dicomnifti https://ci.debian.net/data/autopkgtest/testing/i386/d/dicomnifti/22218046/log.gz CreateNIfTIHeader: WARNING: number of repetitions is less than two time between volumes is set to zero output.nii: FAILED md5sum: WARNING: 1 computed checksum did NOT match autopkgtest [15:10:43]: test run-unit-test OpenPGP_signature Description: OpenPGP digital signature
Bug#1013363: fonttools breaks glyphslib autopkgtest: AssertionError: *.designspace file is different from expected
Source: fonttools, glyphslib
Control: found -1 fonttools/4.33.3-1
Control: found -1 glyphslib/5.3.2+ds1-1
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: breaks needs-update
Dear maintainer(s),
With a recent upload of fonttools the autopkgtest of glyphslib fails in
testing when that autopkgtest is run with the binary packages of
fonttools from unstable. It passes when run with only packages from
testing. In tabular form:
passfail
fonttools from testing4.33.3-1
glyphslib from testing5.3.2+ds1-1
all others from testingfrom testing
I copied some of the output at the bottom of this report.
Currently this regression is blocking the migration of fonttools to
testing [1]. Due to the nature of this issue, I filed this bug report
against both packages. Can you please investigate the situation and
reassign the bug to the right package?
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[1] https://qa.debian.org/excuses.php?package=fonttools
https://ci.debian.net/data/autopkgtest/testing/amd64/g/glyphslib/22951714/log.gz
=== FAILURES
===
_ test_designspace_generation_regular_same_family_name[defcon]
_
tmpdir =
local('/tmp/pytest-of-debci/pytest-0/test_designspace_generation_re0')
ufo_module = '/usr/lib/python3/dist-packages/defcon/__init__.py'>
def test_designspace_generation_regular_same_family_name(tmpdir,
ufo_module):
ufo_Lt = ufo_module.Font()
ufo_Lt.info.familyName = "CoolFoundry Examplary Serif"
ufo_Lt.info.styleName = "Light"
ufo_Lt.info.openTypeOS2WeightClass = 300
ufo_Rg = ufo_module.Font()
ufo_Rg.info.familyName = "CoolFoundry Examplary Serif"
ufo_Rg.info.styleName = "Regular"
ufo_Rg.info.openTypeOS2WeightClass = 400
ufo_Md = ufo_module.Font()
ufo_Md.info.familyName = "CoolFoundry Examplary Serif"
ufo_Md.info.styleName = "Medium"
ufo_Md.info.openTypeOS2WeightClass = 500
ufo_Bd = ufo_module.Font()
ufo_Bd.info.familyName = "CoolFoundry Examplary Serif"
ufo_Bd.info.styleName = "Bold"
ufo_Bd.info.openTypeOS2WeightClass = 700
ufo_ExBd = ufo_module.Font()
ufo_ExBd.info.familyName = "CoolFoundry Examplary Serif"
ufo_ExBd.info.styleName = "XBold"
ufo_ExBd.info.openTypeOS2WeightClass = 800
font = to_glyphs([ufo_Lt, ufo_Rg, ufo_Md, ufo_Bd, ufo_ExBd])
designspace = to_designspace(font, ufo_module=ufo_module)
path = os.path.join(str(tmpdir), "actual.designspace")
designspace.write(path)
expected_path = os.path.join(
os.path.dirname(__file__), "..", "data",
"DesignspaceGenTestRegular.designspace"
)
> assert (
len(main.diff_files(path, expected_path,
formatter=formatting.DiffFormatter()))
== 0
)
E assert 50 == 0
E+ where 50 = len('[update-attribute, /designspace[1], format,
"4.1"]')
E+where '[update-attribute, /designspace[1], format, "4.1"]'
= 0x7f6942f867a0>('/tmp/pytest-of-debci/pytest-0/test_designspace_generation_re0/actual.designspace',
'/tmp/autopkgtest-lxc.p3l2ko5z/downtmp/build.Bjv/src/tests/builder/../data/DesignspaceGenTestRegular.designspace',
formatter=)
E+ where =
main.diff_files
E+ and 0x7f69422765f0> = ()
E+where =
formatting.DiffFormatter
tests/builder/designspace_gen_test.py:69: AssertionError
_ test_designspace_generation_italic_same_family_name[defcon]
__
tmpdir =
local('/tmp/pytest-of-debci/pytest-0/test_designspace_generation_it0')
ufo_module = '/usr/lib/python3/dist-packages/defcon/__init__.py'>
def test_designspace_generation_italic_same_family_name(tmpdir,
ufo_module):
ufo_Lt = ufo_module.Font()
ufo_Lt.info.familyName = "CoolFoundry Examplary Serif"
ufo_Lt.info.styleName = "Light Italic"
ufo_Lt.info.openTypeOS2WeightClass = 300
ufo_Lt.info.italicAngle = -11
ufo_Rg = ufo_module.Font()
ufo_Rg.info.familyName = "CoolFoundry Examplary Serif"
ufo_Rg.info.styleName = "Regular Italic"
ufo_Rg.info.openTypeOS2WeightClass = 400
ufo_Rg.info.italicAngle = -11
ufo_Md = ufo_module.Font()
ufo_Md.info.familyName = "CoolFoundry Examplary Serif"
ufo_Md.info.styleName = "Medium Italic"
ufo_Md.info.openTypeOS2WeightClass = 500
ufo_Md.info.italicAngle = -11
ufo_Bd = ufo_module.Font()
ufo_Bd.info.familyName = "CoolFoundry Examplary Serif"
ufo_Bd.info.styleName = "Bold Italic"
ufo_Bd.info.openTypeOS2WeightClass = 700
Processed: fonttools breaks glyphslib autopkgtest: AssertionError: *.designspace file is different from expected
Processing control commands: > found -1 fonttools/4.33.3-1 Bug #1013363 [src:fonttools, src:glyphslib] fonttools breaks glyphslib autopkgtest: AssertionError: *.designspace file is different from expected Marked as found in versions fonttools/4.33.3-1. > found -1 glyphslib/5.3.2+ds1-1 Bug #1013363 [src:fonttools, src:glyphslib] fonttools breaks glyphslib autopkgtest: AssertionError: *.designspace file is different from expected Marked as found in versions glyphslib/5.3.2+ds1-1. -- 1013363: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013363 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1013362: src:alt-ergo: fails to migrate to testing for too long: FTBFS on armel, mips64el and mipsel
Source: alt-ergo Version: 2.0.0-8 Severity: serious Tags: sid bookworm ftbfs User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing [1]. Your package src:alt-ergo has been trying to migrate for 61 days [2]. Hence, I am filing this bug. The latest uploads of your package failed to build on armel, mips64el and mipsel [3]. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bookworm, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=alt-ergo [3] https://buildd.debian.org/status/package.php?p=alt-ergo OpenPGP_signature Description: OpenPGP digital signature
Processed: src:ruby3.0: fails to migrate to testing for too long: causes autopkgtest failure on ppc64el
Processing control commands: > close -1 3.0.4-7 Bug #1013360 [src:ruby3.0] src:ruby3.0: fails to migrate to testing for too long: causes autopkgtest failure on ppc64el Marked as fixed in versions ruby3.0/3.0.4-7. Bug #1013360 [src:ruby3.0] src:ruby3.0: fails to migrate to testing for too long: causes autopkgtest failure on ppc64el Marked Bug as done -- 1013360: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013360 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1013360: src:ruby3.0: fails to migrate to testing for too long: causes autopkgtest failure on ppc64el
Source: ruby3.0 Version: 3.0.3-1 Severity: serious Control: close -1 3.0.4-7 Tags: sid bookworm User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), I know you know, but to track it, I'm still filing this bug. The Release Team considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing [1]. Your package src:ruby3.0 has been trying to migrate for 61 days [2]. Hence, I am filing this bug. 3.0.4 triggers two autopkgtest regressions: "Compaction isn't available on this platform". If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bookworm, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=ruby3.0 OpenPGP_signature Description: OpenPGP digital signature
Bug#1001001: linux-image-5.10.0-9-arm64: kernel BUG at include/linux/swapops.h:204!
Hi Diederik, On 21-06-2022 23:19, Diederik de Haas wrote: I think that the install logs aren't that important (anymore) as the issue/ symptoms appear to be the same: - some swap action resulting in some failure - CPU gets stuck - watchdog triggers a reboot If the reboot would actually happen/finish, I wouldn't have problems of the hanging host. The issues I spotted required a manual reboot (and that's why I spotted them). How is swap configured on these devices? https://salsa.debian.org/ci-team/debian-ci-config/-/blob/master/cookbooks/basics/default.rb#L3 until line 11 Yeah, I _assumed_ as such, but assumptions can be dangerous ;-) Total ACK. Normally I scroll (hard) by the hardware listings as that rarely says anything to me. And I did that before too, but just now I made an important discovery. I *assumed* it was running on arm64 (native) hardware and was about to ask specifics about it and then I noticed this: Host bridge [0600]: Red Hat, Inc. QEMU PCIe Host bridge [1b36:0008] Qemu. Quite likely unrelated, but a while back I had an issue with qemu in building arm64 images: https://bugs.debian.org/988174 hmm, OK, right (I forgot that I knew this). I think it would be useful to know which qemu version(s) were used. Is there any way to know from inside the VM? If the issue does occur again, I think it would be useful to bring 'upstream' into the conversation. They likely can bring much more useful input into this then (f.e.) I could. Also, if upstream is made aware there is an issue (even infrequent), then they can make the most informed choice what to do with it. Ack. Paul OpenPGP_signature Description: OpenPGP digital signature
Processed: raise severity of deal.ii FTBFS bugs again
Processing commands for cont...@bugs.debian.org: > severity 1011655 serious Bug #1011655 [src:deal.ii] deal.ii ftbfs against libtbb-dev/experimental, cmake could not find tbb Bug #1012126 [src:deal.ii] deal.ii: FTBFS with onetbb/2021.5.0-9 in experimental Severity set to 'serious' from 'important' Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 1011655: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011655 1012126: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012126 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: forcemerge deal.ii FTBFS bugs
Processing commands for cont...@bugs.debian.org: > forcemerge 1011655 1012126 Bug #1011655 [src:deal.ii] deal.ii ftbfs against libtbb-dev/experimental, cmake could not find tbb Bug #1012126 [src:deal.ii] deal.ii: FTBFS with onetbb/2021.5.0-9 in experimental Severity set to 'important' from 'serious' Bug #1011655 [src:deal.ii] deal.ii ftbfs against libtbb-dev/experimental, cmake could not find tbb Added tag(s) ftbfs. Merged 1011655 1012126 > thanks Stopping processing here. Please contact me if you need assistance. -- 1011655: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011655 1012126: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012126 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1012544: marked as done (libworkflow1: Broken shared library packaging)
Your message dated Wed, 22 Jun 2022 19:00:15 + with message-id and subject line Bug#1012544: fixed in workflow 0.10.1-1 has caused the Debian Bug report #1012544, regarding libworkflow1: Broken shared library packaging 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.) -- 1012544: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012544 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libworkflow1 Version: 0.9.10-1 Severity: serious Hi! This package has several problems: - It contains a shared library without a SOVERSION ,--- $ objdump -p /usr/lib/x86_64-linux-gnu/libworkflow.so | grep SONAME SONAME libworkflow.so `--- This means any binary package linked against this shared library misses relevant ABI information and can break on any ABI change. The SONAME should contain the SOVERSION, in this case I'd assume that to be 1, from the binary package name, but given the version used in the fully versioned shared library filename, perhaps that should have been libworkflow0, and then SONAME should be libworkflow.so.0. - The shared library object should be the one with the full version, say libworkflow.so.0.9.10, the SONAME should be the symlink, so say libworkflow.so.0 → libworkflow.so.0.9.10, and the unversioned .so symlink for build-time linking should also be a symlink (or in some cases a linker script), libworkflow.so → libworkflow.so.0.9.10. - The versioned shared library filenames should go into the versioned shared library package. - The unversioned shared and static library filenames should go into the -dev package. Please refer to debian-policy section §8 for further information. I think in this case lintian would have flagged these as errors. Thanks, Guillem --- End Message --- --- Begin Message --- Source: workflow Source-Version: 0.10.1-1 Done: Lance Lin We believe that the bug you reported is fixed in the latest version of workflow, 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 1012...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Lance Lin (supplier of updated workflow 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, 17 Jun 2022 20:09:07 +0700 Source: workflow Binary: libworkflow-dev libworkflow0 Architecture: source amd64 Version: 0.10.1-1 Distribution: unstable Urgency: medium Maintainer: Lance Lin Changed-By: Lance Lin Description: libworkflow-dev - Parallel computing and asynchronous web server engine libworkflow0 - Parallel computing and asynchronous web server engine Closes: 1012544 Changes: workflow (0.10.1-1) unstable; urgency=medium . * Update to version 0.10.1 * d/control: Bump standards to 4.6.1 * d/copyright: Update years to 2022 * Fixed SONAME/SOVERSION issues. Closes: #1012544 Checksums-Sha1: e3f1b67ba3a15781f221da69904f67f419d46699 1769 workflow_0.10.1-1.dsc 53f981c9adee302af4bc5ab35627d81724377ab5 378725 workflow_0.10.1.orig.tar.gz ae462be15f6952ddd0304a067debd864816206e3 4012 workflow_0.10.1-1.debian.tar.xz 538b1865054600edf4f717422af516ca9e0bbe82 285060 libworkflow-dev_0.10.1-1_amd64.deb d46e021641a77e5015d01773ab1a1bb50be6559b 12188 libworkflow0_0.10.1-1_amd64.deb 53273d57a4b0396ec42aebbebcfda803cc6849fc 6697 workflow_0.10.1-1_amd64.buildinfo Checksums-Sha256: c32d785bc2453717fc862928597a1db3653f66d1b2a4e8ecb7c4551947ba70a1 1769 workflow_0.10.1-1.dsc 69135be742649160fdf548939b788845e155456a28ebc5466e555bf8a444bccc 378725 workflow_0.10.1.orig.tar.gz 9b993014c19eac5195a21ea0eb02602134dd4531c9e1775e0b48d9fba35ced98 4012 workflow_0.10.1-1.debian.tar.xz 0286116b297ae92a6f9f7b3b47216573d23fdff2a725159525ef397aeb05523c 285060 libworkflow-dev_0.10.1-1_amd64.deb e41f95b58bed0da7d0c5d8440cb4d600fa782c5221f8a94a177af142a22f5423 12188 libworkflow0_0.10.1-1_amd64.deb b70a20b05585425ace49171ded25cd7f44df010547cd9a0eaa332ccb26d9d86a 6697 workflow_0.10.1-1_amd64.buildinfo Files: bfcfde90f0bcd4adcc2bb610cd52cbb9 1769 libs optional workflow_0.10.1-1.dsc 6e0787e1a23439e154cd51d87d0644cd 378725 libs optional workflow_0.10.1.orig.tar.gz
Bug#1011755: marked as done (gdb-doc: FTBFS: configure: error: GMP is missing or unusable)
Your message dated Wed, 22 Jun 2022 17:04:16 + with message-id and subject line Bug#1011755: fixed in gdb-doc 12.1-1 has caused the Debian Bug report #1011755, regarding gdb-doc: FTBFS: configure: error: GMP is missing or unusable 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.) -- 1011755: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011755 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gdb-doc Version: 11.2-1 Severity: serious Tags: ftbfs Justification: fails to build from source Hi, the latest upload of gdb-doc FTBFS in a minimal buildd chroot: [...] checking for library containing dlopen... none required checking whether to use expat... no configure: WARNING: expat support disabled; some features may be unavailable. checking for libgmp... no configure: error: GMP is missing or unusable make[1]: *** [Makefile:7482: configure-gdb] Error 1 [...] Andreas gdb-doc_11.2-1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: gdb-doc Source-Version: 12.1-1 Done: Héctor Orón Martínez We believe that the bug you reported is fixed in the latest version of gdb-doc, 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 1011...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Héctor Orón Martínez (supplier of updated gdb-doc 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, 22 Jun 2022 18:17:13 +0200 Source: gdb-doc Binary: gdb-doc Architecture: source all Version: 12.1-1 Distribution: unstable Urgency: medium Maintainer: Héctor Orón Martínez Changed-By: Héctor Orón Martínez Description: gdb-doc- The GNU Debugger Documentation Closes: 883815 1001569 1011755 Changes: gdb-doc (12.1-1) unstable; urgency=medium . * Remove and thank Riku Voipio for past contributions (Closes: #1001569, #883815) * Bump standards version, no changes * New upstream version 12.1 * debian/control: build depend on libgmp-dev. (Closes: #1011755) Checksums-Sha1: c4ee4743f3713ad65d9320a4eafc1fae0dccdd5d 1965 gdb-doc_12.1-1.dsc 30a3076508a8f2aff0e8da6090bfa35012b037cb 24037132 gdb-doc_12.1.orig.tar.xz 3a39d2fc5ea1981ba81340569792f8f42ee900e4 13308 gdb-doc_12.1-1.debian.tar.xz 0522418d0a890a6d9f8c03bdabf06719342b0515 4992276 gdb-doc_12.1-1_all.deb 9724089e361718746fa98305cdc9c7f17928e6dd 8130 gdb-doc_12.1-1_amd64.buildinfo Checksums-Sha256: 07f070952d19114733659327f6e020b51f7ebc28828f973569b22415f1f2ced2 1965 gdb-doc_12.1-1.dsc aed3fd381f025e1101675e5b45f1d2420bbd03e84d483cab4881f0800d4e6993 24037132 gdb-doc_12.1.orig.tar.xz f2f8d686e54a44f74f38df3bc31f0a22e136982a588e646fb0d2d4a6ca452e9b 13308 gdb-doc_12.1-1.debian.tar.xz 8049b4dd5e79c7015c8439d3917d4f37f55a75b41559e1b23079c78c9ceb0992 4992276 gdb-doc_12.1-1_all.deb 4d9876100b8d4730a3c9bc614c8e961e0354a00e5b6c2ea3de4fbe1eaa74ee51 8130 gdb-doc_12.1-1_amd64.buildinfo Files: 97de6bf5c97b393b5b6ee1573639faf1 1965 non-free/devel optional gdb-doc_12.1-1.dsc 9ccaeb08b04253582d3bd765554a9bac 24037132 non-free/devel optional gdb-doc_12.1.orig.tar.xz 6e7dfcdea3c23cdca4b0e495876b9161 13308 non-free/devel optional gdb-doc_12.1-1.debian.tar.xz 3c6940558a1af50ad23834f20db90319 4992276 non-free/doc optional gdb-doc_12.1-1_all.deb b6701b616e3d9f2ffeb73c0b4451f06a 8130 non-free/devel optional gdb-doc_12.1-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE6Q8IiVReeMgqnedOryKDqnbirHsFAmKzR6gACgkQryKDqnbi rHvxyQ//a5BGv4BISVxjsjQTGuIUXSGtL86h5fo0ILsc9paxUsEaVvL0uFTo94B8 juT37Jwv2SGkEBSFg88AGnjq//XaTm4RJDujYjdRp+DJp4EmzkrmngKazB8ZBA3T qHooZfQT1523qt0x0HH6tkzbREc2vqhL5cZQtApcVfrF7SZsahRr7bfNQuBoutG/ q4kQjU4AHVXC7qdURvUesRe6vflp6x1RaojLhRcWyR02jzFiV9N2EGUrUAWYzMG/ CRtHrqGj408O9ser/vofI5U452pN6A/hzC6HibTxUx7xoTlf+LmN3RMxLkK7cUwL Fwke266g55KNwwWIFVES4+UivIlPooNXZpA1V1CjWSWH/6kZydgbc84KShr4BiS2 t4nIaxIiC1AxmsNUoGPj0UgrDBvm/vNMGzmbw72pQRkVIFz3tAA/xrRkQNQmbSNx fnpvBc5cVL/Px3aaGUvc/tGYRxB2FJMzxvB/ebX+z2jK1uHdlIHfW4JGv4HI48Ze Dnol2tgXCtCwLdBQ4yEjAc9vHcrzaaaFw1xSFHZCGCU5YD+ww6Z4jIBJCyO3HoVh xO07jtKwCAv9ht9OvAiaLCFy3fE9rCvMDGSjKIpWQHtMEjHbDggjORZVtVEhqmN0
Processed: severity of 1013191 is wishlist
Processing commands for cont...@bugs.debian.org: > severity 1013191 wishlist Bug #1013191 [src:mdurl] mdurl: FTBFS with flit < 3.2 Severity set to 'wishlist' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 1013191: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013191 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1012494: marked as done (gdb: FTBFS on ppc family: No rule to make target 'info' in build/default/sim/ppc)
Your message dated Wed, 22 Jun 2022 16:34:01 + with message-id and subject line Bug#1012494: fixed in gdb 12.1-1 has caused the Debian Bug report #1012494, regarding gdb: FTBFS on ppc family: No rule to make target 'info' in build/default/sim/ppc 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.) -- 1012494: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012494 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gdb Version: 11.2-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: debian-powe...@lists.debian.org User: debian-powe...@lists.debian.org Usertags: ppc64el powerpc ppc64 gdb 11 is not migrating to testing because the ppc64el build is missing: > make[3]: Leaving directory '/<>/build/default/gnulib' > Doing info in sim > make[3]: Entering directory '/<>/build/default/sim' > Making info in ppc > make[4]: Entering directory '/<>/build/default/sim/ppc' > make[4]: *** No rule to make target 'info'. Stop. > make[4]: Leaving directory '/<>/build/default/sim/ppc' > make[3]: *** [Makefile:1271: info-recursive] Error 1 > make[3]: Leaving directory '/<>/build/default/sim' > make[2]: *** [Makefile:8088: info-sim] Error 1 > make[2]: Leaving directory '/<>/build/default' > make[1]: *** [Makefile:984: do-info] Error 2 > make[1]: Leaving directory '/<>/build/default' > make: *** [debian/rules:233: stamps/build-default] Error 2 — https://buildd.debian.org/status/fetch.php?pkg=gdb=ppc64el=11.2-1=1651406483=0 The non-release architectures powerpc and ppc64 seem to have the same bug. If there's no obvious nice solution, it might be possible to mitigate this by only enabling the texinfo documentation when asked to build Architecture: all packages, which in practice get built on an x86 buildd? smcv --- End Message --- --- Begin Message --- Source: gdb Source-Version: 12.1-1 Done: Héctor Orón Martínez We believe that the bug you reported is fixed in the latest version of gdb, 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 1012...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Héctor Orón Martínez (supplier of updated gdb 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, 22 Jun 2022 18:10:19 +0200 Source: gdb Architecture: source Version: 12.1-1 Distribution: unstable Urgency: medium Maintainer: Héctor Orón Martínez Changed-By: Héctor Orón Martínez Closes: 1001561 1012494 Changes: gdb (12.1-1) unstable; urgency=medium . * Remove and thank Riku Voipio for past contributions (Closes: #1001561) * Bump standards version, no changes * New upstream release. (Closes: #1012494) * debian/patches: refresh, merged upstream gdb_bsd support Checksums-Sha1: e30f1872598e87999abb22c1a842f8f40594fd9a 2855 gdb_12.1-1.dsc 0bde03844c88fce5c8d3000fa419f53076a019cb 22940352 gdb_12.1.orig.tar.xz bc9f4dc85fce7a25f4e43b51758200f580d983ec 195 gdb_12.1.orig.tar.xz.asc bc861e20a667aca081e0ddc13eb966e7a1097905 286420 gdb_12.1-1.debian.tar.xz 3fcee6747e28b3334f6ea4ed78b52750465671b1 10001 gdb_12.1-1_source.buildinfo Checksums-Sha256: f5d6d76793a7e2678c8a02d7c51983408e58acac8d4f724e9e17c1faf1da3010 2855 gdb_12.1-1.dsc 8e439ae59180f07b8408c55af7762aadf3832d644808fc2ce31ad5caa30dc98a 22940352 gdb_12.1.orig.tar.xz 94a6fd40d0875155a1ce904071f6c23d4e33a77d10a6640821ae14df1b2495a7 195 gdb_12.1.orig.tar.xz.asc 4bbcc98c93a910910fa775a32a4947f2add0df31545bc372c4f1adf9ddcc191f 286420 gdb_12.1-1.debian.tar.xz 15893ab95b42088ddc188d7ff940d487936395c0430f609c2456ad2cf189fb1a 10001 gdb_12.1-1_source.buildinfo Files: 7d0c04d451282bb639454a7213f04e87 2855 devel optional gdb_12.1-1.dsc 2ba8d242d5556328902e7468294c062e 22940352 devel optional gdb_12.1.orig.tar.xz 14ee505e98d0fe830594f7ac51051375 195 devel optional gdb_12.1.orig.tar.xz.asc 9f913d93fcc70d2294b043b825738ec1 286420 devel optional gdb_12.1-1.debian.tar.xz 036c8030859dcf3c003cfeaacafffd65 10001 devel optional gdb_12.1-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE6Q8IiVReeMgqnedOryKDqnbirHsFAmKzP18ACgkQryKDqnbi
Bug#1013355: groovy: FTBFS with jansi 2.4.0-1
Forgot to CC the bug report Am Mittwoch, dem 22.06.2022 um 18:14 +0200 schrieb Emmanuel Bourg: > Le 2022-06-22 17:54, Markus Koschany a écrit : > > > groovy FTBFS with jansi 2.4.0. I intend to either prepare a patch or > > upgrade to a newer upstream release in the future. > > Please hold the upload, this is going to blow up Maven and Gradle. I've > introduced > jansi1 to try to work around the issue but I haven't completed the > transition yet. Could you share your plans with jansi1 and why we just can't upgrade to a newer version of it? I am still working on a major gradle upgrade in the background and I hope we don't need the current version any longer. jansi 2.4.0 was also required to upgrade maven-shared-utils. Besides from gradle and groovy no other r-dep failed to build from source, at least that was the outcome of a ratt rebuild. signature.asc Description: This is a digitally signed message part
Bug#1013355: groovy: FTBFS with jansi 2.4.0-1
Le 2022-06-22 17:54, Markus Koschany a écrit : groovy FTBFS with jansi 2.4.0. I intend to either prepare a patch or upgrade to a newer upstream release in the future. Please hold the upload, this is going to blow up Maven and Gradle. I've introduced jansi1 to try to work around the issue but I haven't completed the transition yet. Emmanuel Bourg
Bug#1013355: groovy: FTBFS with jansi 2.4.0-1
Package: groovy Version: 2.4.21-1 Severity: serious X-Debbugs-Cc: a...@debian.org groovy FTBFS with jansi 2.4.0. I intend to either prepare a patch or upgrade to a newer upstream release in the future. Markus
Bug#1011714: gitless: FTBFS: ValueError: invalid argument: 'file || path'
Control: reassign -1 src:python-pygit2 Control: retitle -1 python-pygit2: import fails if /usr/lib/ssl/certs does not exist Looks like python-pygit2 needs the OpenSSL certificate paths set up properly to function. The problem disappears if the openssl package is installed. On Thu, 26 May 2022 08:12:19 +0200 Lucas Nussbaum wrote: Source: gitless Version: 0.8.8-4 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220525 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > '/<>/debian/run-simple-test.sh' > Using directory /tmp/gitless-test.jVerea > + [ 1 -ne 1 ] > + dir=/tmp/gitless-test.jVerea > + : python3.10 > + : git > + pwd > + : /<>/gl.py > + gl=python3.10 /<>/gl.py > + [ -d /tmp/gitless-test.jVerea ] > + cd /tmp/gitless-test.jVerea > + python3.10 /<>/gl.py init > Traceback (most recent call last): > File "/<>/gl.py", line 10, in > from gitless.cli import gl > File "/<>/gitless/cli/gl.py", line 13, in > import pygit2 > File "/usr/lib/python3/dist-packages/pygit2/__init__.py", line 230, in > settings = Settings() > File "/usr/lib/python3/dist-packages/pygit2/settings.py", line 55, in __init__ > self._initialize_tls_certificate_locations() > File "/usr/lib/python3/dist-packages/pygit2/settings.py", line 61, in _initialize_tls_certificate_locations > self.set_ssl_cert_locations( > File "/usr/lib/python3/dist-packages/pygit2/settings.py", line 191, in set_ssl_cert_locations > option(_pygit2.GIT_OPT_SET_SSL_CERT_LOCATIONS, cert_file, cert_dir) > ValueError: invalid argument: 'file || path' > make[1]: *** [debian/rules:9: override_dh_auto_test] Error 1 The full build log is available from: http://qa-logs.debian.net/2022/05/25/gitless_0.8.8-4_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220525;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220525=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 marking 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 -- ⢀⣴⠾⠻⢶⣦⠀ ╭╮ ⣾⠁⢠⠒⠀⣿⡁ │ Timo Röhling │ ⢿⡄⠘⠷⠚⠋⠀ │ 9B03 EBB9 8300 DF97 C2B1 23BF CC8C 6BDD 1403 F4CA │ ⠈⠳⣄ ╰╯ signature.asc Description: PGP signature
Processed: Re: gitless: FTBFS: ValueError: invalid argument: 'file || path'
Processing control commands: > reassign -1 src:python-pygit2 Bug #1011714 [src:gitless] gitless: FTBFS: ValueError: invalid argument: 'file || path' Bug reassigned from package 'src:gitless' to 'src:python-pygit2'. No longer marked as found in versions gitless/0.8.8-4. Ignoring request to alter fixed versions of bug #1011714 to the same values previously set > retitle -1 python-pygit2: import fails if /usr/lib/ssl/certs does not exist Bug #1011714 [src:python-pygit2] gitless: FTBFS: ValueError: invalid argument: 'file || path' Changed Bug title to 'python-pygit2: import fails if /usr/lib/ssl/certs does not exist' from 'gitless: FTBFS: ValueError: invalid argument: 'file || path''. -- 1011714: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011714 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1013348: test_elf.py fails with binutils in unstable
tags 1013348 + pending thanks > the test_elf.py test fails with binutils from the trunk: Thanks for the report. I've fixed this earlier today with this commit: https://salsa.debian.org/reproducible-builds/diffoscope/commit/280ff40115af104685932b96e83ccb79f78afabb It fixes it in our Salsa CI pipeline, and I'll upload it tomorrow. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Processed: Re: test_elf.py fails with binutils in unstable
Processing commands for cont...@bugs.debian.org: > tags 1013348 + pending Bug #1013348 [src:diffoscope] test_elf.py fails with binutils in unstable Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1013348: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013348 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: markdown-it-py: FTBFS with flit < 3.4 (<3.3?)
Processing control commands: > severity -1 wishlist Bug #1013204 [src:markdown-it-py] markdown-it-py: FTBFS with flit < 3.4 (<3.3?) Severity set to 'wishlist' from 'serious' > retitle -1 markdown-it-py: backport for bullseye Bug #1013204 [src:markdown-it-py] markdown-it-py: FTBFS with flit < 3.4 (<3.3?) Changed Bug title to 'markdown-it-py: backport for bullseye' from 'markdown-it-py: FTBFS with flit < 3.4 (<3.3?)'. -- 1013204: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013204 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1013204: markdown-it-py: FTBFS with flit < 3.4 (<3.3?)
Control: severity -1 wishlist Control: retitle -1 markdown-it-py: backport for bullseye On Sat, 18 Jun 2022 17:58:24 -0500 "David (Plasma) Paul" wrote: markdown-it-py fails to build from source with versions of flit earlier than 3.4 according to the package's pyproject.toml.[0] Attached is a patch to fix the declared build dependency on flit in the debian/control file to match the supported versions listed in the package's pyproject.toml file. [0] However, I was able to get markdown-it-py to build with flit 3.3.0-1~bpo11+1, so maybe the value in the pyproject.toml file is higher than it strictly needs to be. Regardless of what the actual exact minimum value is, I can confirm that flit 3.0.0 is insufficient. Please do not file RC bugs when a bookworm/sid only package does not build for bullseye-backports. If you want a backport please express that intend otherwise this is invalid.
Bug#1013348: test_elf.py fails with binutils in unstable
Package: src:diffoscope Version: 216 Severity: serious the test_elf.py test fails with binutils from the trunk: [...] FAILED tests/comparators/test_elf.py::test_diff - AssertionError FAILED tests/comparators/test_elf.py::test_lib_differences - AssertionError
Processed (with 2 errors): Re: Bug#1010747 closed by Debian FTP Masters
Processing control commands:
> reopen -1
Bug #1010747 {Done: Georges Khaznadar } [shiboken2]
Unusable with current python version
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions pyacidobasic/2.11.1-2 and
pymecavideo/7.2.1-3.
> notfixed pyacidobasic/2.11.1-2
Unknown command or malformed arguments to command.
> notfixed pymecavideo/7.2.1-3
Unknown command or malformed arguments to command.
--
1010747: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010747
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1010747: closed by Debian FTP Masters
Control: reopen -1 Control: notfixed pyacidobasic/2.11.1-2 Control: notfixed pymecavideo/7.2.1-3 On Wed, 08 Jun 2022 15:03:50 +0200 Yuri D'Elia wrote: This bug was against shiboken2, but was fixed pyacidobasic? I just verified nothing has been fixed in shiboken2 yet. Georges, please pay attention to what bugs you are closing. Your packages might be influenced (autoremoved) because of this bug but it does not really help to close it via your packages' changelogs.
Bug#1011698: marked as done (voms-api-java: FTBFS: dh_auto_test: error: /usr/lib/jvm/default-java/bin/java -noverify -cp /usr/share/maven/boot/plexus-classworlds-2.x.jar -Dmaven.home=/usr/share/maven
Your message dated Wed, 22 Jun 2022 10:55:09 + with message-id and subject line Bug#1011698: fixed in voms-api-java 3.3.2-2 has caused the Debian Bug report #1011698, regarding voms-api-java: FTBFS: dh_auto_test: error: /usr/lib/jvm/default-java/bin/java -noverify -cp /usr/share/maven/boot/plexus-classworlds-2.x.jar -Dmaven.home=/usr/share/maven -Dmaven.multiModuleProjectDirectory=/<> -Dclassworlds.conf=/etc/maven/m2-debian.conf org.codehaus.plexus.classworlds.launcher.Launcher -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian -Dmaven.repo.local=/<>/debian/maven-repo --batch-mode test returned exit code 1 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.) -- 1011698: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011698 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: voms-api-java Version: 3.3.2-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220525 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules build > dh build --buildsystem=maven >dh_update_autotools_config -O--buildsystem=maven >dh_autoreconf -O--buildsystem=maven >dh_auto_configure -O--buildsystem=maven > mh_patchpoms -plibvoms-api-java-java --debian-build --keep-pom-version > --maven-repo=/<>/debian/maven-repo >dh_auto_build -O--buildsystem=maven > /usr/lib/jvm/default-java/bin/java -noverify -cp > /usr/share/maven/boot/plexus-classworlds-2.x.jar > -Dmaven.home=/usr/share/maven > -Dmaven.multiModuleProjectDirectory=/<> > -Dclassworlds.conf=/etc/maven/m2-debian.conf > org.codehaus.plexus.classworlds.launcher.Launcher > -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian > -Dmaven.repo.local=/<>/debian/maven-repo --batch-mode package > javadoc:jar javadoc:aggregate -DskipTests -Dnotimestamp=true -Dlocale=en_US > [INFO] Scanning for projects... > [INFO] > [INFO] ---< org.italiangrid:voms-api-java > > > [INFO] Building voms-api-java 3.3.2 > [INFO] [ jar > ]- > [INFO] > [INFO] --- maven-resources-plugin:3.1.0:resources (default-resources) @ > voms-api-java --- > [INFO] Using 'UTF-8' encoding to copy filtered resources. > [INFO] Copying 1 resource > [INFO] > [INFO] --- maven-compiler-plugin:3.8.1:compile (default-compile) @ > voms-api-java --- > [INFO] Changes detected - recompiling the module! > [INFO] Compiling 115 source files to /<>/target/classes > [WARNING] bootstrap class path not set in conjunction with -source 8 > [WARNING] > /<>/src/main/java/org/italiangrid/voms/request/SSLSocketFactoryProvider.java:[33,39] > eu.emi.security.authn.x509.impl.SocketFactoryCreator in > eu.emi.security.authn.x509.impl has been deprecated > [WARNING] > /<>/src/main/java/org/italiangrid/voms/request/impl/LegacyProtocol.java:[39,39] > eu.emi.security.authn.x509.impl.HostnameMismatchCallback in > eu.emi.security.authn.x509.impl has been deprecated > [WARNING] > /<>/src/main/java/org/italiangrid/voms/request/impl/LegacyProtocol.java:[40,39] > eu.emi.security.authn.x509.impl.SocketFactoryCreator in > eu.emi.security.authn.x509.impl has been deprecated > [WARNING] > /<>/src/main/java/org/italiangrid/voms/request/SSLSocketFactoryProvider.java:[81,37] > eu.emi.security.authn.x509.impl.SocketFactoryCreator in > eu.emi.security.authn.x509.impl has been deprecated > [WARNING] > /<>/src/main/java/org/italiangrid/voms/request/impl/LegacyProtocol.java:[48,17] > eu.emi.security.authn.x509.impl.HostnameMismatchCallback in > eu.emi.security.authn.x509.impl has been deprecated > [WARNING] > /<>/src/main/java/org/italiangrid/voms/request/impl/LegacyProtocol.java:[74,9] > eu.emi.security.authn.x509.impl.SocketFactoryCreator in > eu.emi.security.authn.x509.impl has been deprecated > [INFO] > [INFO] --- maven-resources-plugin:3.1.0:testResources (default-testResources) > @ voms-api-java --- > [INFO] Using 'UTF-8' encoding to copy filtered resources. > [INFO] Copying 85 resources > [INFO] > [INFO] --- maven-compiler-plugin:3.8.1:testCompile (default-testCompile) @ > voms-api-java --- > [INFO] Changes detected - recompiling the module! > [INFO] Compiling 30 source files to /<>/target/test-classes > [WARNING] bootstrap class path not set in conjunction with -source 8 > [WARNING] > /<>/src/test/java/org/italiangrid/voms/test/TestVOMSESLineParser.java:[71,7] > assertThat(T,org.hamcrest.Matcher) in org.junit.Assert has >
Bug#1013341: /usr/bin/ld.bfd: warning: /usr/lib/crt0-efi-x86_64.o: missing .note.GNU-stack section implies executable stack
Am 22.06.22 um 11:49 schrieb Julien Cristau: On Wed, Jun 22, 2022 at 10:50:48AM +0200, Michael Biebl wrote: Marking as RC, as it causes a FTBFS Not using -Wl,--fatal-warnings might be a workaround for systemd until gnu-efi fixes this? Yeah, I'll probably add a workaround like diff --git a/src/boot/efi/meson.build b/src/boot/efi/meson.build index 52e2a71a7c..18311ede25 100644 --- a/src/boot/efi/meson.build +++ b/src/boot/efi/meson.build @@ -251,6 +251,8 @@ efi_ldflags = [ '-L', efi_libdir, '-nostdlib', '-T', efi_lds, +'-Wl,--no-warn-execstack', +'-Wl,--no-warn-rwx-segments', '-Wl,--build-id=sha1', '-Wl,--fatal-warnings', '-Wl,--no-undefined', to systemd for the time being. OpenPGP_signature Description: OpenPGP digital signature
Bug#1013341: /usr/bin/ld.bfd: warning: /usr/lib/crt0-efi-x86_64.o: missing .note.GNU-stack section implies executable stack
On Wed, Jun 22, 2022 at 10:50:48AM +0200, Michael Biebl wrote: > Package: gnu-efi > Version: 3.0.13+git20210716.269ef9d-2 > Severity: serious > Forwarded: https://sourceforge.net/p/gnu-efi/bugs/28/ > > Hi, > > since the latest update of binutils to 2.38.50.20220615, > the systemd source package fails to build: > > ``` > $ ninja -C build/ > ninja: Entering directory `build/' > [72/2108] Generating src/boot/efi/linuxx64.elf.stub with a custom command > FAILED: src/boot/efi/linuxx64.elf.stub > /usr/bin/cc -o src/boot/efi/linuxx64.elf.stub -DGNU_EFI_USE_MS_ABI -DSD_BOOT > -ffreestanding -fshort-wchar -fvisibility=hidden -I > /home/michael/git/systemd/src/fundamental -I > /home/michael/git/systemd/src/boot/efi -include src/boot/efi/efi_config.h > -include version.h -isystem /usr/include/efi/x86_64 -isystem /usr/include/efi > -std=gnu11 -Wall -Wextra -Wno-format-signedness > -Wno-missing-field-initializers -Wno-unused-parameter -Wdate-time > -Wendif-labels -Werror=format=2 -Werror=implicit-function-declaration > -Werror=incompatible-pointer-types -Werror=int-conversion -Werror=overflow > -Werror=override-init -Werror=return-type -Werror=shift-count-overflow > -Werror=shift-overflow=2 -Werror=undef -Wfloat-equal -Wimplicit-fallthrough=5 > -Winit-self -Wlogical-op -Wmissing-include-dirs -Wmissing-noreturn > -Wnested-externs -Wold-style-definition -Wpointer-arith -Wredundant-decls > -Wshadow -Wstrict-aliasing=2 -Wstrict-prototypes -Wsuggest-attribute=noreturn > -Wunused-function -Wwrite-strings -Wno-unused-result -fno-stack-protector > -fno-strict-aliasing -fpic -fwide-exec-charset=UCS2 -mno-red-zone -mno-sse > -mno-mmx -ggdb -DEFI_DEBUG -fuse-ld=bfd -L /usr/lib -nostdlib -T > /usr/lib/elf_x86_64_efi.lds -Wl,--build-id=sha1 -Wl,--fatal-warnings > -Wl,--no-undefined -Wl,--warn-common -Wl,-Bsymbolic -z nocombreloc > /usr/lib/crt0-efi-x86_64.o -pie -Wl,--no-dynamic-linker > src/boot/efi/bootspec-fundamental.c.o src/boot/efi/efivars-fundamental.c.o > src/boot/efi/sha256.c.o src/boot/efi/string-util-fundamental.c.o > src/boot/efi/assert.c.o src/boot/efi/devicetree.c.o src/boot/efi/disk.c.o > src/boot/efi/efi-string.c.o src/boot/efi/graphics.c.o src/boot/efi/initrd.c.o > src/boot/efi/measure.c.o src/boot/efi/pe.c.o src/boot/efi/secure-boot.c.o > src/boot/efi/ticks.c.o src/boot/efi/util.c.o src/boot/efi/cpio.c.o > src/boot/efi/splash.c.o src/boot/efi/stub.c.o src/boot/efi/linux_x86.c.o > -lefi -lgnuefi -lgcc > /usr/bin/ld.bfd: warning: /usr/lib/crt0-efi-x86_64.o: missing .note.GNU-stack > section implies executable stack > /usr/bin/ld.bfd: NOTE: This behaviour is deprecated and will be removed in a > future version of the linker > collect2: error: ld returned 1 exit status > [77/2108] Generating catalog/systemd.ru.catalog with a custom command > (wrapped by meson to capture output) > ninja: build stopped: subcommand failed. > ``` > > I originally raised this at systemd upstream [1], but it was mentioned > there, that this might actually be a gnu-efi issue. > [1] also contains links to the relevant changes in binutils which now > trigger this warning. > > Marking as RC, as it causes a FTBFS > Not using -Wl,--fatal-warnings might be a workaround for systemd until gnu-efi fixes this? Cheers, Julien
Bug#1013299: linux-image-4.19.0-20-amd64: NULL pointer deref in qdisc_put() due to missing backport
On Tuesday, 21 June 2022 16:11:42 CEST Diederik de Haas wrote:
> > So yes, this needs to also be fixed upstream (hence me including that tag
> > when reporbugging), but perhaps Debian can quickfix.
>
> What I have observed so far is that a commit needs to be accepted upstream
> (but doesn't have to have gone through the whole 'chain of command') before
> a temporary patch is accepted to quickly fix it in Debian.
I made an initial attempt at a patch, see attachment.
https://kernel-team.pages.debian.net/kernel-handbook/ch-common-tasks.html#s4.2.2
describes a way to test whether this patch fixes the issue.
(Just in case. I'm reasonably sure you already know this)>From 38cc721ef0c6745d808718d212968a173b6732b5 Mon Sep 17 00:00:00 2001
From: Diederik de Haas
Date: Wed, 22 Jun 2022 11:44:05 +0200
Subject: [PATCH] [linux-4.19.y] net_sched: let qdisc_put() accept NULL pointer
In commit 92833e8b5db6c209e9311ac8c6a44d3bf1856659 titled
"net: sched: rename qdisc_destroy() to qdisc_put()" part of the
functionality of qdisc_destroy() was moved into a (for linux-4.19.y)
new function qdisk_put(), and the previous calls to qdisc_destroy()
were changed to qdisk_put().
This made it similar to f.e. 5.10.y and current master.
There was one part of qdisc_destroy() not moved over to qdisc_put() and
that was the check for a NULL value, causing oopses.
(See upstream commit: 6efb971ba8edfbd80b666f29de12882852f095ae)
This patch fixes that.
Fixes: 92833e8b5db6c209e9311ac8c6a44d3bf1856659
Reported-by: Thorsten Glaser
Link: https://bugs.debian.org/1013299
---
net/sched/sch_generic.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/net/sched/sch_generic.c b/net/sched/sch_generic.c
index 7c1b1eff84f4..cad2586c3473 100644
--- a/net/sched/sch_generic.c
+++ b/net/sched/sch_generic.c
@@ -970,8 +970,6 @@ static void qdisc_destroy(struct Qdisc *qdisc)
const struct Qdisc_ops *ops;
struct sk_buff *skb, *tmp;
- if (!qdisc)
- return;
ops = qdisc->ops;
#ifdef CONFIG_NET_SCHED
@@ -1003,6 +1001,9 @@ static void qdisc_destroy(struct Qdisc *qdisc)
void qdisc_put(struct Qdisc *qdisc)
{
+ if (!qdisc)
+ return;
+
if (qdisc->flags & TCQ_F_BUILTIN ||
!refcount_dec_and_test(>refcnt))
return;
--
2.36.1
signature.asc
Description: This is a digitally signed message part.
Bug#1013341: /usr/bin/ld.bfd: warning: /usr/lib/crt0-efi-x86_64.o: missing .note.GNU-stack section implies executable stack
Package: gnu-efi Version: 3.0.13+git20210716.269ef9d-2 Severity: serious Forwarded: https://sourceforge.net/p/gnu-efi/bugs/28/ Hi, since the latest update of binutils to 2.38.50.20220615, the systemd source package fails to build: ``` $ ninja -C build/ ninja: Entering directory `build/' [72/2108] Generating src/boot/efi/linuxx64.elf.stub with a custom command FAILED: src/boot/efi/linuxx64.elf.stub /usr/bin/cc -o src/boot/efi/linuxx64.elf.stub -DGNU_EFI_USE_MS_ABI -DSD_BOOT -ffreestanding -fshort-wchar -fvisibility=hidden -I /home/michael/git/systemd/src/fundamental -I /home/michael/git/systemd/src/boot/efi -include src/boot/efi/efi_config.h -include version.h -isystem /usr/include/efi/x86_64 -isystem /usr/include/efi -std=gnu11 -Wall -Wextra -Wno-format-signedness -Wno-missing-field-initializers -Wno-unused-parameter -Wdate-time -Wendif-labels -Werror=format=2 -Werror=implicit-function-declaration -Werror=incompatible-pointer-types -Werror=int-conversion -Werror=overflow -Werror=override-init -Werror=return-type -Werror=shift-count-overflow -Werror=shift-overflow=2 -Werror=undef -Wfloat-equal -Wimplicit-fallthrough=5 -Winit-self -Wlogical-op -Wmissing-include-dirs -Wmissing-noreturn -Wnested-externs -Wold-style-definition -Wpointer-arith -Wredundant-decls -Wshadow -Wstrict-aliasing=2 -Wstrict-prototypes -Wsuggest-attribute=noreturn -Wunused-function -Wwrite-strings -Wno-unused-result -fno-stack-protector -fno-strict-aliasing -fpic -fwide-exec-charset=UCS2 -mno-red-zone -mno-sse -mno-mmx -ggdb -DEFI_DEBUG -fuse-ld=bfd -L /usr/lib -nostdlib -T /usr/lib/elf_x86_64_efi.lds -Wl,--build-id=sha1 -Wl,--fatal-warnings -Wl,--no-undefined -Wl,--warn-common -Wl,-Bsymbolic -z nocombreloc /usr/lib/crt0-efi-x86_64.o -pie -Wl,--no-dynamic-linker src/boot/efi/bootspec-fundamental.c.o src/boot/efi/efivars-fundamental.c.o src/boot/efi/sha256.c.o src/boot/efi/string-util-fundamental.c.o src/boot/efi/assert.c.o src/boot/efi/devicetree.c.o src/boot/efi/disk.c.o src/boot/efi/efi-string.c.o src/boot/efi/graphics.c.o src/boot/efi/initrd.c.o src/boot/efi/measure.c.o src/boot/efi/pe.c.o src/boot/efi/secure-boot.c.o src/boot/efi/ticks.c.o src/boot/efi/util.c.o src/boot/efi/cpio.c.o src/boot/efi/splash.c.o src/boot/efi/stub.c.o src/boot/efi/linux_x86.c.o -lefi -lgnuefi -lgcc /usr/bin/ld.bfd: warning: /usr/lib/crt0-efi-x86_64.o: missing .note.GNU-stack section implies executable stack /usr/bin/ld.bfd: NOTE: This behaviour is deprecated and will be removed in a future version of the linker collect2: error: ld returned 1 exit status [77/2108] Generating catalog/systemd.ru.catalog with a custom command (wrapped by meson to capture output) ninja: build stopped: subcommand failed. ``` I originally raised this at systemd upstream [1], but it was mentioned there, that this might actually be a gnu-efi issue. [1] also contains links to the relevant changes in binutils which now trigger this warning. Marking as RC, as it causes a FTBFS Regards, Michael [1] https://github.com/systemd/systemd/issues/23789 -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.18.0-2-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled -- no debconf information
Bug#1013335: rust-hyper: impossible to install
Source: rust-hyper Version: 0.12.35-1 Severity: grave Justification: renders package unusable -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Main binary package, librust-hyper-dev, declares impossible to satisfy dependencies, and consequently all binary packages are impossible to install. -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmKyxAkACgkQLHwxRsGg ASEWvxAAg/41BCtW/E72FWw0FZ6aC0A9Ef/YQeUQaU6Hx7XXFs/r6YWwgq+Mh4y0 1J4iDGK7UX0EWbvwqPOMcYmn2XyQVAUCMxiF1Qm5QMzuegq1cCc1LVjnOQMsExX+ qpk2DmK6RbQzoQS81XkG/yYPz//Kspe3IfKmh3mXD5ESeqnyMlbenyHzJstflShd gquqOTpyxl8eNgmPZSnlARYHnzPhIYFFRcx1j0h/Yedcxq6ok8S7TPsWdbq54m9P XeR6sJ8hiz4wpCjAqQgQDf5nGmVcTpc8VnEyQSpCAyyYZXXvTnpXrzzY6l7az/GD cv510SXDRhnsQVrtd0G1p4Rh+c/6T/mw9o3l9MRRzJQvvptlKa2+cC4TGyDiP8kU YybPT3YcVuPjrJ6dL7x3B9smjDMSES8Q44Z9U+4+bv9HaWav6mLSb6Ugx7tjtVgL GIdVmBPsMEGHXODM/s74UnKdyBuVpnk6sCAwRLlfscWwgcDvCax/i5osHy6LP/6S Y3O+bcyzrrwv3wBcWyUI2TYxShTC9zC9KAgoSVUcSdJZ3H0E9mArSB7t3djHuz3t tsZhaZ1setSN5CDB30Og+tlqst1NNcSdlb24Y4stDUi9C2E79KP41k2WobHGtjq0 vNfUUhD+sknAC2rLiCtwDEOXSIyX8M/J2xac4kyk5zYrRmof2SA= =qmay -END PGP SIGNATURE-
