Bug#1006384: closed by Debian FTP Masters (reply to Olivier Sallou ) (Bug#1006384: fixed in logol 1.7.9+dfsg-2)
Hi Paul, Paul Gevers писал 2022-03-03 00:44: > On 01-03-2022 12:01, Paul Gevers wrote: >> This "fix" suggest there may be more breakage, normally the Release Team >> would schedule binNMU's. Can you please elaborate how ABI is normally >> maintained within swi-prolog, such that the rebuilds can be detected and >> requested? I fail to see how in the case of logol and swi-prolog the right >> versions are chosen. In other words, I think the "fixed" logol can migrate >> to testing even if swi-prolog does not and will be broken in testing until >> swi-prolog can migrate. Normally *versioned* dependencies should prevent >> this. > > I just read the backlog of the bug report (by default, submitters of > bug reports in Debian don't get notified of messages, I missed the > discussion). It seems my worry was already raised. The bug was > reassigned to logol, so the swi-prolog maintainers missed my message. > >> I checked, there are more reverse build dependencies of swi-prolog, I'm >> afraid there's more breakage that hasn't been detected yet. (eye seems to go >> in lockstep, so that package currently seems OK). > > Maybe swi-prolog maintainers can comment. Thanks for your input. Since the problem is resolved now, could you please unblock migration of swi-prolog, logol, and eye (another package depending on swi-prolog). swi-prolog package (namely, swi-prolog-core) provides an easy way to require some particular ABI since 8.2.0+dfsg-2 uploaded on Jun 9, 2020. Specifically, in this case logol requires version 67 of binary ABI (pre-compiled Prolog code), where the version of swi-prolog in unstable is at version 68. In case of logol, its fixed version needs to depend on swi-prolog-binary-68 (again, provided by swi-prolog-core). In this case it will be easier to track problems with ABI changes. There are more ABI stuff in swi-prolog which can be tracked the same way. It is documented in d/Debian.NEWS and d/README.Debian and there are references to SWI-Prolog upstream reference guide. More specifically, swi-prolog provides 5 virtual packages, each of them containing (a part) of some specific ABI version claimed by the current swi-prolog version. All these components are extensively documented in SWI-Prolog upstream reference guide. These virtual packages were introduced to prevent the same ABI-incompatibility problems with another Debian package, eye. Cheers! Lev
Bug#1006678: marked as done (ukui-settings-daemon: FTBFS against libkscreen 5.24.2)
Your message dated Thu, 03 Mar 2022 07:19:21 + with message-id and subject line Bug#1006678: fixed in ukui-settings-daemon 3.1.1.1-1 has caused the Debian Bug report #1006678, regarding ukui-settings-daemon: FTBFS against libkscreen 5.24.2 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.) -- 1006678: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006678 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ukui-settings-daemon Version: 3.1.1-1 Severity: serious Tags: ftbfs In current Debian unstable (and Ubuntu Jammy), ukui-settings-daemon FTBFS against the latest Plasma libkscreen 5.24.2. xrandr-output.cpp: In static member function ‘static void xrandrOutput::readInOutputs(KScreen::ConfigPtr, const QVariantList&)’: xrandr-output.cpp:368:21: error: ‘class KScreen::Output’ has no member named ‘setLogicalSize’ 368 | output->setLogicalSize(QSizeF()); | ^~ --- End Message --- --- Begin Message --- Source: ukui-settings-daemon Source-Version: 3.1.1.1-1 Done: handsome_feng We believe that the bug you reported is fixed in the latest version of ukui-settings-daemon, 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 1006...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. handsome_feng (supplier of updated ukui-settings-daemon package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 03 Mar 2022 14:25:48 +0800 Source: ukui-settings-daemon Architecture: source Version: 3.1.1.1-1 Distribution: unstable Urgency: medium Maintainer: Kylin Team Changed-By: handsome_feng Closes: 1006678 Changes: ukui-settings-daemon (3.1.1.1-1) unstable; urgency=medium . * New upstream bugfix release. (Closes: 1006678) Checksums-Sha1: 9bf8acd0b783e930b63f3114f3c93754bc7fbdd3 2802 ukui-settings-daemon_3.1.1.1-1.dsc a64214310eb3e4bd74871065d659522a77a62a7c 348889 ukui-settings-daemon_3.1.1.1.orig.tar.gz 015140715edf25b598f3828ac79c731454078b19 3952 ukui-settings-daemon_3.1.1.1-1.debian.tar.xz cf8cbacd0a81f41e91b5a97fe139cf7b9145c60b 20234 ukui-settings-daemon_3.1.1.1-1_source.buildinfo Checksums-Sha256: da7d074d29c85a1a66901c907e36e3f1c449f81434f2b3637c3ca57894e6536d 2802 ukui-settings-daemon_3.1.1.1-1.dsc 54cb776ca93272c8f872986390f9cb63a9ef85a3f4bcd4e37db49bdb1373bdd9 348889 ukui-settings-daemon_3.1.1.1.orig.tar.gz 83ca0f155107db95d7ebabf7ebd8be1f65b6d2ec65e1990f8e838342f0f8d54e 3952 ukui-settings-daemon_3.1.1.1-1.debian.tar.xz 3bc10fe8882bfedf156f847785ff26d06cecec80d5521b72878aa72423e4147b 20234 ukui-settings-daemon_3.1.1.1-1_source.buildinfo Files: 0db8b8182be93991675ec9b5fd98a668 2802 x11 optional ukui-settings-daemon_3.1.1.1-1.dsc e3043a73255c8cddf48a589096db93e8 348889 x11 optional ukui-settings-daemon_3.1.1.1.orig.tar.gz 8c38316645f9f47f74dc2d7cd8db5a27 3952 x11 optional ukui-settings-daemon_3.1.1.1-1.debian.tar.xz 24c1f080be90cd177034e50c75052262 20234 x11 optional ukui-settings-daemon_3.1.1.1-1_source.buildinfo -BEGIN PGP SIGNATURE- iQJPBAEBCAA5FiEEhsgAHpUwnacZWWSCm7hQwBMRHwwFAmIgaLUbHGppYW5mZW5n bGlAdWJ1bnR1a3lsaW4uY29tAAoJEJu4UMATER8MbmoP/2dalEQ67SBvPv7LoMRG VymB2D3w3YbUz0pbzYe5KKw4ZGuwXm+NI9YhPVyoLLWjsbbTDlfW5qeM13OTt5NV OaWs/JZke/x55CpyeMx99WeCteuGAw5MWRrpfMt+ozzXfl17DJtdD0lcmHrAGI8K l+Gdciu27sBcjaGk2cTA/fV4bF8qIKK364CHKcGVN8PydSyq+xgE1OVM6JQaJ0Xp Lv6ejP864RYUApdx6VrAwnQt7Ogjydfwvh38qEAuhS758YdqyFXD1LNkHOxUkamY YP4L26meoSSFE4NWVWPudxVzKHEJxewnSzUXwmsD6anFYATYQ5ereIVaReaX3RQ0 0eX/ht4UbCOexUODxR54+fpcuWOOhlrFafbOOLdtCFbuL8pFAviCRX0AuRlaMI+4 pw5Sw1xHhIBiNEwm6Fzhhf4Hk0bishhNR1UAAfRrtrFL0ak9hwYelNfiXyrsx8qE TqCwxsoyjXADag0ipHpBIC0KMHbW8jav/pZ9C9SGEMt9zqHOqLHTdVXnzQKET8Vm sdHbaZLi+IzIxmdO927mkM5uKizci5GJC1M/uEIdjEj2a2nqx72fE/r3iuQ5O/y2 JR0kvUHFeR71uBO41f0RV0tJwKt/0LCHE1FlZm7jygH02F5s5/RRnQq0coxSn66u jfkZ3G2S5/CAIKktan1elLib =xiGN -END PGP SIGNATURE End Message ---
Bug#1002242: marked as done (dh-php >= 4 causes multiple packages to FTBFS)
Your message dated Thu, 3 Mar 2022 05:22:03 +0100 with message-id <14026656-9f6e-4e4a-b906-34fd0df76...@sury.org> and subject line Re: Bug#1000637: dh-php >= 4 causes multiple packages to FTBFS has caused the Debian Bug report #1000637, regarding dh-php >= 4 causes multiple packages to FTBFS 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.) -- 1000637: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000637 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: sassphp Version: 0.7-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211220 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 '/<>' > sed: can't read debian/control.in: No such file or directory > debian/rules:9: CONFIGURE_TARGETS: configure-7.4-stamp > debian/rules:10: BUILD_TARGETS: build-7.4-stamp > debian/rules:11: INSTALL_TARGETS: install-7.4-stamp > dh_clean > dh_clean: warning: Compatibility levels before 10 are deprecated (level 9 in > use) > /usr/share/dh-php/gen-control > Package not converted to dh-php >= 4 > make[1]: *** [/usr/share/dh-php/pkg-pecl.mk:76: override_dh_clean] Error 1 The full build log is available from: http://qa-logs.debian.net/2021/12/20/sassphp_0.7-1_unstable.log 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 --- Most of the packages build now and those that does not need to be fixed individually. I’ll take care of php-facedetect and tideways; and I think sassphp is dead upstream, but there’s some activity in https://github.com/sensational/sassphp repository, so I’ll investigate this before filling RM bug. Ondrej -- Ondřej Surý (He/Him) ond...@sury.org--- End Message ---
Bug#1002218: marked as done (dh-php >= 4 causes multiple packages to FTBFS)
Your message dated Thu, 3 Mar 2022 05:22:03 +0100 with message-id <14026656-9f6e-4e4a-b906-34fd0df76...@sury.org> and subject line Re: Bug#1000637: dh-php >= 4 causes multiple packages to FTBFS has caused the Debian Bug report #1000637, regarding dh-php >= 4 causes multiple packages to FTBFS 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.) -- 1000637: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000637 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: php-memcached Version: 3.1.5+2.2.0-5+deb11u1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211220 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 '/<>' > sed: can't read debian/control.in: No such file or directory > sed: can't read debian/control.in: No such file or directory > sed: can't read debian/control.in: No such file or directory > dh_clean > /usr/share/dh-php/gen-control > Package not converted to dh-php >= 4 > make[1]: *** [/usr/share/dh-php/pkg-pecl.mk:76: override_dh_clean] Error 1 The full build log is available from: http://qa-logs.debian.net/2021/12/20/php-memcached_3.1.5+2.2.0-5+deb11u1_unstable.log 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 --- Most of the packages build now and those that does not need to be fixed individually. I’ll take care of php-facedetect and tideways; and I think sassphp is dead upstream, but there’s some activity in https://github.com/sensational/sassphp repository, so I’ll investigate this before filling RM bug. Ondrej -- Ondřej Surý (He/Him) ond...@sury.org--- End Message ---
Bug#1002232: marked as done (dh-php >= 4 causes multiple packages to FTBFS)
Your message dated Thu, 3 Mar 2022 05:22:03 +0100 with message-id <14026656-9f6e-4e4a-b906-34fd0df76...@sury.org> and subject line Re: Bug#1000637: dh-php >= 4 causes multiple packages to FTBFS has caused the Debian Bug report #1000637, regarding dh-php >= 4 causes multiple packages to FTBFS 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.) -- 1000637: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000637 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: tideways Version: 5.0.4-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211220 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 '/<>' > sed: can't read debian/control.in: No such file or directory > debian/rules:8: CONFIGURE_TARGETS: configure-7.4-stamp > debian/rules:9: BUILD_TARGETS: build-7.4-stamp > debian/rules:10: INSTALL_TARGETS: install-7.4-stamp > dh_clean > /usr/share/dh-php/gen-control > Package not converted to dh-php >= 4 > make[1]: *** [/usr/share/dh-php/pkg-pecl.mk:76: override_dh_clean] Error 1 The full build log is available from: http://qa-logs.debian.net/2021/12/20/tideways_5.0.4-2_unstable.log 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 --- Most of the packages build now and those that does not need to be fixed individually. I’ll take care of php-facedetect and tideways; and I think sassphp is dead upstream, but there’s some activity in https://github.com/sensational/sassphp repository, so I’ll investigate this before filling RM bug. Ondrej -- Ondřej Surý (He/Him) ond...@sury.org--- End Message ---
Bug#1002215: marked as done (dh-php >= 4 causes multiple packages to FTBFS)
Your message dated Thu, 3 Mar 2022 05:22:03 +0100 with message-id <14026656-9f6e-4e4a-b906-34fd0df76...@sury.org> and subject line Re: Bug#1000637: dh-php >= 4 causes multiple packages to FTBFS has caused the Debian Bug report #1000637, regarding dh-php >= 4 causes multiple packages to FTBFS 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.) -- 1000637: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000637 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: php-redis Version: 5.3.2+4.3.0-2+deb11u1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211220 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 '/<>' > sed: can't read debian/control.in: No such file or directory > sed: can't read debian/control.in: No such file or directory > sed: can't read debian/control.in: No such file or directory > dh_clean > /usr/share/dh-php/gen-control > Package not converted to dh-php >= 4 > make[1]: *** [/usr/share/dh-php/pkg-pecl.mk:76: override_dh_clean] Error 1 The full build log is available from: http://qa-logs.debian.net/2021/12/20/php-redis_5.3.2+4.3.0-2+deb11u1_unstable.log 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 --- Most of the packages build now and those that does not need to be fixed individually. I’ll take care of php-facedetect and tideways; and I think sassphp is dead upstream, but there’s some activity in https://github.com/sensational/sassphp repository, so I’ll investigate this before filling RM bug. Ondrej -- Ondřej Surý (He/Him) ond...@sury.org--- End Message ---
Bug#1000637: marked as done (dh-php >= 4 causes multiple packages to FTBFS)
Your message dated Thu, 3 Mar 2022 05:22:03 +0100 with message-id <14026656-9f6e-4e4a-b906-34fd0df76...@sury.org> and subject line Re: Bug#1000637: dh-php >= 4 causes multiple packages to FTBFS has caused the Debian Bug report #1000637, regarding dh-php >= 4 causes multiple packages to FTBFS 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.) -- 1000637: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000637 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: php-facedetect Version: 1.1.0-19-g135c72a-2 Severity: serious Tags: ftbfs bookworm sid https://buildd.debian.org/status/logs.php?pkg=php-facedetect=1.1.0-19-g135c72a-2%2Bb1 ... dh_clean /usr/share/dh-php/gen-control Package not converted to dh-php >= 4 make[1]: *** [/usr/share/dh-php/pkg-pecl.mk:72: override_dh_clean] Error 1 --- End Message --- --- Begin Message --- Most of the packages build now and those that does not need to be fixed individually. I’ll take care of php-facedetect and tideways; and I think sassphp is dead upstream, but there’s some activity in https://github.com/sensational/sassphp repository, so I’ll investigate this before filling RM bug. Ondrej -- Ondřej Surý (He/Him) ond...@sury.org--- End Message ---
Bug#1004096: marked as done (lua-cliargs: autopkgtest regression: module 'system' not found)
Your message dated Wed, 2 Mar 2022 20:16:11 -0500 with message-id <20220303011611.y2j6efs7teoy6plh@localhost> and subject line Re: Bug#1004099: lua-system: autopkgtest regression: module 'mediator' not found has caused the Debian Bug report #1004096, regarding lua-cliargs: autopkgtest regression: module 'system' not found 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.) -- 1004096: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004096 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: lua-cliargs Version: 3.0-2-4 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of lua-cliargs the autopkgtest of lua-cliargs fails in testing when that autopkgtest is run with the binary packages of lua-cliargs from unstable. It passes when run with only packages from testing. In tabular form: passfail lua-cliargsfrom testing3.0-2-4 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=lua-cliargs https://ci.debian.net/data/autopkgtest/testing/amd64/l/lua-cliargs/18493075/log.gz dh autopkgtest --buildsystem=lua --with lua dh_auto_test -O--buildsystem=lua make --no-print-directory -f /usr/share/dh-lua/make/dh-lua.Makefile.multiple autopkgtest Making target autopkgtest for debian/lua5.1.dh-lua.conf * lua dynamic custom (5.1, autopkgtest) ** +++ 175 successes / 0 failures / 0 errors / 0 pending : 0.099948 seconds * Target autopkgtest made Making target autopkgtest for debian/lua5.2.dh-lua.conf * lua dynamic custom (5.2, autopkgtest) ** +++ 175 successes / 0 failures / 0 errors / 0 pending : 0.101283 seconds * Target autopkgtest made Making target autopkgtest for debian/lua5.3.dh-lua.conf * lua dynamic custom (5.3, autopkgtest) ** +++ 175 successes / 0 failures / 0 errors / 0 pending : 0.323412 seconds * Target autopkgtest made Making target autopkgtest for debian/lua5.4.dh-lua.conf * lua dynamic custom (5.4, autopkgtest) ** lua5.4: /usr/share/lua/5.4/busted/core.lua:6: module 'system' not found: no field package.preload['system'] no file '/usr/local/share/lua/5.4/system.lua' no file '/usr/local/share/lua/5.4/system/init.lua' no file '/usr/local/lib/lua/5.4/system.lua' no file '/usr/local/lib/lua/5.4/system/init.lua' no file '/usr/share/lua/5.4/system.lua' no file '/usr/share/lua/5.4/system/init.lua' no file './system.lua' no file './system/init.lua' no file '/usr/local/lib/lua/5.4/system.so' no file '/usr/lib/x86_64-linux-gnu/lua/5.4/system.so' no file '/usr/lib/lua/5.4/system.so' no file '/usr/local/lib/lua/5.4/loadall.so' no file './system.so' stack traceback: [C]: in function 'require' /usr/share/lua/5.4/busted/core.lua:6: in main chunk [C]: in function 'require' /usr/share/lua/5.4/busted/runner.lua:18: in function 'busted.runner' /usr/bin/busted:3: in main chunk [C]: in ? make[2]: *** [/usr/share/dh-lua/make/dh-lua.Makefile.single:326: test-lua-dynamic-apkgt-real-custom] Error 1 make[1]: *** [/usr/share/dh-lua/make/dh-lua.Makefile.multiple:12: autopkgtest] Error 1 dh_auto_test: error: make --no-print-directory -f /usr/share/dh-lua/make/dh-lua.Makefile.multiple autopkgtest returned exit code 2 make: *** [debian/rules:4: autopkgtest] Error 25 autopkgtest [17:41:55]: test dh-lua-tests
Bug#1004099: marked as done (lua-system: autopkgtest regression: module 'mediator' not found)
Your message dated Wed, 2 Mar 2022 20:16:11 -0500 with message-id <20220303011611.y2j6efs7teoy6plh@localhost> and subject line Re: Bug#1004099: lua-system: autopkgtest regression: module 'mediator' not found has caused the Debian Bug report #1004099, regarding lua-system: autopkgtest regression: module 'mediator' not found 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.) -- 1004099: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004099 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: lua-system Version: 0.2.1-5 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of lua-system the autopkgtest of lua-system fails in testing when that autopkgtest is run with the binary packages of lua-system from unstable. It passes when run with only packages from testing. In tabular form: passfail lua-system from testing0.2.1-5 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=lua-system https://ci.debian.net/data/autopkgtest/testing/amd64/l/lua-system/18491945/log.gz dh autopkgtest --buildsystem=lua --with lua dh_auto_test -O--buildsystem=lua make --no-print-directory -f /usr/share/dh-lua/make/dh-lua.Makefile.multiple autopkgtest Making target autopkgtest for debian/lua5.1.dh-lua.conf * lua dynamic custom (5.1, autopkgtest) ** +++ 3 successes / 0 failures / 0 errors / 0 pending : 0.501591 seconds * Target autopkgtest made Making target autopkgtest for debian/lua5.2.dh-lua.conf * lua dynamic custom (5.2, autopkgtest) ** +++ 3 successes / 0 failures / 0 errors / 0 pending : 0.502037 seconds * Target autopkgtest made Making target autopkgtest for debian/lua5.3.dh-lua.conf * lua dynamic custom (5.3, autopkgtest) ** +++ 3 successes / 0 failures / 0 errors / 0 pending : 0.50354 seconds * Target autopkgtest made Making target autopkgtest for debian/lua5.4.dh-lua.conf * lua dynamic custom (5.4, autopkgtest) ** lua5.4: /usr/share/lua/5.4/busted/core.lua:45: module 'mediator' not found: no field package.preload['mediator'] no file '/usr/local/share/lua/5.4/mediator.lua' no file '/usr/local/share/lua/5.4/mediator/init.lua' no file '/usr/local/lib/lua/5.4/mediator.lua' no file '/usr/local/lib/lua/5.4/mediator/init.lua' no file '/usr/share/lua/5.4/mediator.lua' no file '/usr/share/lua/5.4/mediator/init.lua' no file './mediator.lua' no file './mediator/init.lua' no file '/usr/local/lib/lua/5.4/mediator.so' no file '/usr/lib/x86_64-linux-gnu/lua/5.4/mediator.so' no file '/usr/lib/lua/5.4/mediator.so' no file '/usr/local/lib/lua/5.4/loadall.so' no file './mediator.so' stack traceback: [C]: in function 'require' /usr/share/lua/5.4/busted/core.lua:45: in function 'busted.core' /usr/share/lua/5.4/busted/runner.lua:18: in function 'busted.runner' /usr/bin/busted:3: in main chunk [C]: in ? make[2]: *** [/usr/share/dh-lua/make/dh-lua.Makefile.single:326: test-lua-dynamic-apkgt-real-custom] Error 1 make[1]: *** [/usr/share/dh-lua/make/dh-lua.Makefile.multiple:12: autopkgtest] Error 1 dh_auto_test: error: make --no-print-directory -f /usr/share/dh-lua/make/dh-lua.Makefile.multiple autopkgtest returned exit code 2 make: *** [debian/rules:6: autopkgtest] Error 25 autopkgtest [17:40:57]: test dh-lua-tests OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- On Thu, Jan 20, 2022 at 09:11:17PM +0100, Paul Gevers wrote: > With a recent upload of lua-system the autopkgtest of lua-system fails in > testing when that autopkgtest is run with the binary packages of lua-system > from unstable. It passes when run with only packages from testing. In > tabular form: > ... > Making target autopkgtest for debian/lua5.3.dh-lua.conf > * lua dynamic custom (5.3, autopkgtest) ** >
Bug#1004098: marked as done (lua-say: autopkgtest regression: module 'system' not found)
Your message dated Wed, 2 Mar 2022 20:16:11 -0500 with message-id <20220303011611.y2j6efs7teoy6plh@localhost> and subject line Re: Bug#1004099: lua-system: autopkgtest regression: module 'mediator' not found has caused the Debian Bug report #1004098, regarding lua-say: autopkgtest regression: module 'system' not found 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.) -- 1004098: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004098 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: lua-say Version: 1.3-1-7 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of lua-say the autopkgtest of lua-say fails in testing when that autopkgtest is run with the binary packages of lua-say from unstable. It passes when run with only packages from testing. In tabular form: passfail lua-sayfrom testing1.3-1-7 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=lua-say https://ci.debian.net/data/autopkgtest/testing/amd64/l/lua-say/18500281/log.gz dh autopkgtest --buildsystem=lua --with lua dh_auto_test -O--buildsystem=lua make --no-print-directory -f /usr/share/dh-lua/make/dh-lua.Makefile.multiple autopkgtest Making target autopkgtest for debian/lua5.1.dh-lua.conf * lua dynamic custom (5.1, autopkgtest) ** + 5 successes / 0 failures / 0 errors / 0 pending : 0.002135 seconds * Target autopkgtest made Making target autopkgtest for debian/lua5.2.dh-lua.conf * lua dynamic custom (5.2, autopkgtest) ** + 5 successes / 0 failures / 0 errors / 0 pending : 0.003267 seconds * Target autopkgtest made Making target autopkgtest for debian/lua5.3.dh-lua.conf * lua dynamic custom (5.3, autopkgtest) ** + 5 successes / 0 failures / 0 errors / 0 pending : 0.007344 seconds * Target autopkgtest made Making target autopkgtest for debian/lua5.4.dh-lua.conf * lua dynamic custom (5.4, autopkgtest) ** lua5.4: /usr/share/lua/5.4/busted/core.lua:6: module 'system' not found: no field package.preload['system'] no file '/usr/local/share/lua/5.4/system.lua' no file '/usr/local/share/lua/5.4/system/init.lua' no file '/usr/local/lib/lua/5.4/system.lua' no file '/usr/local/lib/lua/5.4/system/init.lua' no file '/usr/share/lua/5.4/system.lua' no file '/usr/share/lua/5.4/system/init.lua' no file './system.lua' no file './system/init.lua' no file '/usr/local/lib/lua/5.4/system.so' no file '/usr/lib/x86_64-linux-gnu/lua/5.4/system.so' no file '/usr/lib/lua/5.4/system.so' no file '/usr/local/lib/lua/5.4/loadall.so' no file './system.so' stack traceback: [C]: in function 'require' /usr/share/lua/5.4/busted/core.lua:6: in main chunk [C]: in function 'require' /usr/share/lua/5.4/busted/runner.lua:18: in function 'busted.runner' /usr/bin/busted:3: in main chunk [C]: in ? make[2]: *** [/usr/share/dh-lua/make/dh-lua.Makefile.single:326: test-lua-dynamic-apkgt-real-custom] Error 1 make[1]: *** [/usr/share/dh-lua/make/dh-lua.Makefile.multiple:12: autopkgtest] Error 1 dh_auto_test: error: make --no-print-directory -f /usr/share/dh-lua/make/dh-lua.Makefile.multiple autopkgtest returned exit code 2 make: *** [debian/rules:4: autopkgtest] Error 25 autopkgtest [23:14:51]: test dh-lua-tests OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- On Thu, Jan 20, 2022 at 09:11:17PM +0100, Paul Gevers wrote: > With a recent upload of lua-system the autopkgtest of lua-system fails in > testing when that autopkgtest is run with the binary packages of lua-system > from unstable. It passes when run with only packages from testing. In > tabular form: > ... > Making target autopkgtest for debian/lua5.3.dh-lua.conf > * lua dynamic custom (5.3, autopkgtest) ** > +++ > 3 successes / 0
Bug#1004097: marked as done (lua-mediator: autopkgtest regression: module 'system' not found)
Your message dated Wed, 2 Mar 2022 20:16:11 -0500 with message-id <20220303011611.y2j6efs7teoy6plh@localhost> and subject line Re: Bug#1004099: lua-system: autopkgtest regression: module 'mediator' not found has caused the Debian Bug report #1004097, regarding lua-mediator: autopkgtest regression: module 'system' not found 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.) -- 1004097: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004097 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: lua-mediator Version: 1.1.2-0-6 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of lua-mediator the autopkgtest of lua-mediator fails in testing when that autopkgtest is run with the binary packages of lua-mediator from unstable. It passes when run with only packages from testing. In tabular form: passfail lua-mediator from testing1.1.2-0-6 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=lua-mediator https://ci.debian.net/data/autopkgtest/testing/amd64/l/lua-mediator/18493076/log.gz dh autopkgtest --buildsystem=lua --with lua dh_auto_test -O--buildsystem=lua make --no-print-directory -f /usr/share/dh-lua/make/dh-lua.Makefile.multiple autopkgtest Making target autopkgtest for debian/lua5.1.dh-lua.conf * lua dynamic custom (5.1, autopkgtest) ** ++ 26 successes / 0 failures / 0 errors / 0 pending : 0.008956 seconds * Target autopkgtest made Making target autopkgtest for debian/lua5.2.dh-lua.conf * lua dynamic custom (5.2, autopkgtest) ** ++ 26 successes / 0 failures / 0 errors / 0 pending : 0.00897 seconds * Target autopkgtest made Making target autopkgtest for debian/lua5.3.dh-lua.conf * lua dynamic custom (5.3, autopkgtest) ** ++ 26 successes / 0 failures / 0 errors / 0 pending : 0.02869 seconds * Target autopkgtest made Making target autopkgtest for debian/lua5.4.dh-lua.conf * lua dynamic custom (5.4, autopkgtest) ** lua5.4: /usr/share/lua/5.4/busted/core.lua:6: module 'system' not found: no field package.preload['system'] no file '/usr/local/share/lua/5.4/system.lua' no file '/usr/local/share/lua/5.4/system/init.lua' no file '/usr/local/lib/lua/5.4/system.lua' no file '/usr/local/lib/lua/5.4/system/init.lua' no file '/usr/share/lua/5.4/system.lua' no file '/usr/share/lua/5.4/system/init.lua' no file './system.lua' no file './system/init.lua' no file '/usr/local/lib/lua/5.4/system.so' no file '/usr/lib/x86_64-linux-gnu/lua/5.4/system.so' no file '/usr/lib/lua/5.4/system.so' no file '/usr/local/lib/lua/5.4/loadall.so' no file './system.so' stack traceback: [C]: in function 'require' /usr/share/lua/5.4/busted/core.lua:6: in main chunk [C]: in function 'require' /usr/share/lua/5.4/busted/runner.lua:18: in function 'busted.runner' /usr/bin/busted:3: in main chunk [C]: in ? make[2]: *** [/usr/share/dh-lua/make/dh-lua.Makefile.single:326: test-lua-dynamic-apkgt-real-custom] Error 1 make[1]: *** [/usr/share/dh-lua/make/dh-lua.Makefile.multiple:12: autopkgtest] Error 1 dh_auto_test: error: make --no-print-directory -f /usr/share/dh-lua/make/dh-lua.Makefile.multiple autopkgtest returned exit code 2 make: *** [debian/rules:4: autopkgtest] Error 25 autopkgtest [17:41:48]: test dh-lua-tests OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- On Thu, Jan 20, 2022 at 09:11:17PM +0100, Paul Gevers wrote: > With a recent upload of lua-system the autopkgtest of lua-system fails in > testing when that autopkgtest is run with the binary packages of lua-system > from unstable. It passes when run with only packages from testing. In > tabular form: > ... > Making target autopkgtest for
Bug#1000796: marked as pending in base-passwd
Control: tag -1 pending Hello, Bug #1000796 in base-passwd 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/debian/base-passwd/-/commit/06ed6f49253ff244dc9cbcadc840fdf611f11462 update-passwd.c: set walk to walk->next before removing update-passwd only removes once and exits even more than one items need to be removed. Root cause is walk is set to walk->next after remove_node(), in which the walk has been cleaned, so the while(walk) is terminated. Without the fix, the output of update-passwd $update-passwd --verbose Adding group "postgres" (120) Adding group "nova" (162) Adding group "barbican" (978) Adding group "keystone" (42424) Adding group "neutron" (164) Adding group "ceilometer" (166) Adding group "sysinv" (168) Adding group "snmpd" (169) Adding group "fm" (195) Adding group "libvirt" (991) Adding group "ironic" (1874) Adding group "www" (1877) Removing group "daemon" (1) Adding user "postgres" (120) Adding user "neutron" (164) Adding user "sysinv" (168) Adding user "snmpd" (169) Adding user "fm" (195) Adding user "barbican" (982) Adding user "ceilometer" (991) Adding user "keystone" (42424) Adding user "nova" (994) Adding user "ironic" (1874) Adding user "www" (1877) Removing user "daemon" (1) 25 changes have been made, rewriting files Writing passwd-file to /etc/passwd Writing shadow-file to /etc/shadow Writing group-file to /etc/group With the fix: $sudo update-passwd --verbose Adding group "postgres" (120) Adding group "nova" (162) Adding group "barbican" (978) Adding group "keystone" (42424) Adding group "neutron" (164) Adding group "ceilometer" (166) Adding group "sysinv" (168) Adding group "snmpd" (169) Adding group "fm" (195) Adding group "libvirt" (991) Adding group "ironic" (1874) Adding group "www" (1877) Removing group "daemon" (1) Removing group "bin" (2) Removing group "lp" (7) Removing group "man" (12) Removing group "audio" (29) Removing group "video" (44) Removing group "games" (60) Adding user "postgres" (120) Adding user "neutron" (164) Adding user "sysinv" (168) Adding user "snmpd" (169) Adding user "fm" (195) Adding user "barbican" (982) Adding user "ceilometer" (991) Adding user "keystone" (42424) Adding user "nova" (994) Adding user "ironic" (1874) Adding user "www" (1877) Removing user "daemon" (1) Removing user "bin" (2) Removing user "games" (5) Removing user "lp" (7) Removing user "mail" (8) 35 changes have been made, rewriting files Writing passwd-file to /etc/passwd Writing shadow-file to /etc/shadow Writing group-file to /etc/group Signed-off-by: Yue Tao Closes: #1000796 (this message was generated automatically) -- Greetings https://bugs.debian.org/1000796
Processed: Bug#1000796 marked as pending in base-passwd
Processing control commands: > tag -1 pending Bug #1000796 [base-passwd] update-passwd only remove item one time Added tag(s) pending. -- 1000796: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000796 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1004928: package upload will be done soon
A package fixing these bugs will be uploaded soon ... Thorsten
Bug#1004930: marked as done (build-depends on obsolete versioned lcl packages.)
Your message dated Wed, 02 Mar 2022 23:18:39 + with message-id and subject line Bug#1004930: fixed in astap-cli 2022.03.01-1 has caused the Debian Bug report #1004930, regarding build-depends on obsolete versioned lcl packages. 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.) -- 1004930: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004930 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: astap-cli Version: 0.9.588-3 Serverity: serious Tags: patch astap-cli build-depends on the lcl-2.0 lcl-utils-2.0 and lcl-nogui-2.0 packages which are no longer built by the lazarus source package. They are still present in unstable as cruft packages, but are completely gone from testing. I prepared a patch changing the package to use the unversioned lcl/lcl-utils/lcl-nogui packages and was able to get a succesful build in sid. diff -Nru astap-cli-0.9.588/debian/changelog astap-cli-0.9.588/debian/changelog --- astap-cli-0.9.588/debian/changelog 2021-11-02 20:30:51.0 + +++ astap-cli-0.9.588/debian/changelog 2022-02-03 18:40:02.0 + @@ -1,3 +1,10 @@ +astap-cli (0.9.588-3.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Build-depend on unversioned lcl packages. + + -- Peter Michael Green Thu, 03 Feb 2022 18:40:02 + + astap-cli (0.9.588-3) unstable; urgency=medium * debian/rules: set primary config file of lazarus to /etc/lazarus diff -Nru astap-cli-0.9.588/debian/control astap-cli-0.9.588/debian/control --- astap-cli-0.9.588/debian/control2021-11-02 01:31:06.0 + +++ astap-cli-0.9.588/debian/control2022-02-03 18:40:02.0 + @@ -7,9 +7,9 @@ , lazarus , fpc , fp-compiler - , lcl-2.0 - , lcl-utils-2.0 - , lcl-nogui-2.0 + , lcl + , lcl-utils + , lcl-nogui Standards-Version: 4.6.0 Homepage: http://www.hnsky.org/astap.htm Rules-Requires-Root: binary-targets --- End Message --- --- Begin Message --- Source: astap-cli Source-Version: 2022.03.01-1 Done: Thorsten Alteholz We believe that the bug you reported is fixed in the latest version of astap-cli, 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 1004...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thorsten Alteholz (supplier of updated astap-cli 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, 02 Mar 2022 22:30:51 +0100 Source: astap-cli Architecture: source Version: 2022.03.01-1 Distribution: unstable Urgency: medium Maintainer: Debian Astronomy Team Changed-By: Thorsten Alteholz Closes: 1004930 Changes: astap-cli (2022.03.01-1) unstable; urgency=medium . * new upstream version * debian/control: Build-depend on unversioned lcl packages. Closes: #1004930 thanks to Peter Green for the patch Checksums-Sha1: 29e27b370fcfe752ce9bb29359f88d17ce75546d 2190 astap-cli_2022.03.01-1.dsc ec65acc21657ef6c0681752b5192241c577c6535 642775 astap-cli_2022.03.01.orig.tar.gz 84036ffe9580ebaa46a3b1a22e7d2b1fa5bb7283 2828 astap-cli_2022.03.01-1.debian.tar.xz 0a0e5849adf6f50e9075cea11d3b6d2ec1ec01e5 12259 astap-cli_2022.03.01-1_amd64.buildinfo Checksums-Sha256: aa3ab77222cfca9d83e9cc21b37ffc91f34bbb7738c092c51d8e0f507e7f3922 2190 astap-cli_2022.03.01-1.dsc eaa6ed4ff7ff08b5029061e29b5b6f08a30167d7fb87813cbe4b40d03b4b5826 642775 astap-cli_2022.03.01.orig.tar.gz 8f2043f86bdb724f7176bca1419a7eb900860e8f218e68d3e8caf8eda980211b 2828 astap-cli_2022.03.01-1.debian.tar.xz 0c04829c3b65cf6ac1a4ea02b74e6a98576ebe158bb768ac0283b0131717e5e8 12259 astap-cli_2022.03.01-1_amd64.buildinfo Files: ab6a8001eb95a539b3639447fcd529f7 2190 science optional astap-cli_2022.03.01-1.dsc 1ed877515bf0e522907b14d1b17625da 642775 science optional astap-cli_2022.03.01.orig.tar.gz 0a4b929c960f55f3ac7e2fad56a95c2d 2828 science optional astap-cli_2022.03.01-1.debian.tar.xz 5920ba2461aa109e6a055f96040027b0 12259 science optional astap-cli_2022.03.01-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQKnBAEBCgCRFiEEYgH7/9u94Hgi6ruWlvysDTh7WEcFAmIf9l9fFIAALgAo
Bug#1005149: ansible: misbuilds with two supported Python versions
Control: tags -1 pending Hello all, Due to the severity of this issue, I have uploaded a NMU to the delayed queue, set to 10 days. The NMU is changing the build-dependency from python3-all to python3, so it builds for a single python release at a time. Debdiff attached. Lee, let me know if you need help with sponsors or maintenance of the package. For the record, this seems to be the same issue affecting ansible-core at #1001040 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001040 Thanks, -- Samuel Henrique ansible_2.10.7+merged+base+2.10.8+dfsg-1.1.debdiff Description: Binary data
Processed: ansible: misbuilds with two supported Python versions
Processing control commands: > tags -1 pending Bug #1005149 [src:ansible] ansible: misbuilds with two supported Python versions Added tag(s) pending. -- 1005149: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005149 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1001040: ansible-core: No such file or directory: '/usr/lib/python3.10/dist-packages/ansible/module_utils/ansible_release.py'
Control: tags -1 pending Hello all, Due to the severity of this issue, I have uploaded a NMU to the delayed queue, set to 10 days. The NMU is changing the build-dependency from python3-all to python3, so it builds for a single python release at a time. Debdiff attached. Lee, let me know if you need help with sponsors or maintenance of the package. For the record, this seems to be the same issue affecting ansible at #1005149 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005149 Thanks, -- Samuel Henrique ansible-core_2.12.0-1.1.debdiff Description: Binary data
Processed: ansible-core: No such file or directory: '/usr/lib/python3.10/dist-packages/ansible/module_utils/ansible_release.py'
Processing control commands: > tags -1 pending Bug #1001040 [src:ansible-core] ansible-core: No such file or directory: '/usr/lib/python3.10/dist-packages/ansible/module_utils/ansible_release.py' Added tag(s) pending. -- 1001040: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001040 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1006702: mariadb-10.6: Baseline violation on at least i386 via CXXFLAGS
Source: mariadb-10.6 Version: 1:10.6.7-2 Severity: serious Justification: baseline violation Hello! The file mysys/CMakeFiles.txt overrides the compiler machine flags [1] and causes mariadb-10.6 to be build with the CPU baseline of the buildd which results in binaries that will crash on the target platform such as i386. As can be seen in the build log for i386, the code is being built with "-msse4.2 -mpclmul" with at least SSE 4.2 which is not available before Intel Core i7, according to Wikipedia [3]. On ppc64, the code is being built with VSX, Crypto and POWER8 vector instructions which are all not available on the POWER5 baseline that the ppc64 port in Debian uses. I suggest patching out the whole section in mysys/CMakeFiles.txt which may also help fixing testsuite failures on some architectures. Thanks, Adrian > [1] > https://salsa.debian.org/mariadb-team/mariadb-server/-/blob/debian/latest/mysys/CMakeLists.txt#L62 > [2] > https://buildd.debian.org/status/fetch.php?pkg=mariadb-10.6=i386=1%3A10.6.7-2=1646205322=0 > [3] https://en.wikipedia.org/wiki/SSE4#SSE4.2 -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Bug#1006664: Revert?
On Thu, 3 Mar 2022 01:54:42 +0530 Nilesh Patra wrote: > > python3-unicodedata2 has disappeared from the NEW queue, has it been > > rejected? > > https://tracker.debian.org/pkg/python-unicodedata2 I must have caught it at just the wrong moment. Thanks. -- Neil Williams = http://www.linux.codehelp.co.uk/ pgpwQqIrLtq3Y.pgp Description: OpenPGP digital signature
Bug#1006664: Revert?
> python3-unicodedata2 has disappeared from the NEW queue, has it been > rejected? https://tracker.debian.org/pkg/python-unicodedata2 > Can we go back to 4.28.5-1 ? Not needed now, thanks to Sean for processing it in time Regards, Nilesh signature.asc Description: PGP signature
Bug#1006664: Revert?
python3-unicodedata2 has disappeared from the NEW queue, has it been rejected? Is it possible to revert python3-fonttools to a version which does NOT need python3-unicodedata2 ? This is starting to block a large number of changes to a large number of packages. Can we go back to 4.28.5-1 ? -- Neil Williams = http://www.linux.codehelp.co.uk/ pgpgzLa4qEMrK.pgp Description: OpenPGP digital signature
Bug#1005479: toil: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.10 3.9" returned exit code 13
Hi Paul, On 3/2/22 11:51 PM, Paul Gevers wrote: I tried re-triggering it to check once again but looks like runners are not up unfortunately. You mean the salsa ones, right? Yes And so if you could trigger a test suite for this package at your end once, and help debug it, that'd be really nice. What do you propose I look for? I'm not very good at debugging random software. Me neither, but I could propose to check for two things: a) As per Sascha's idea[1], if you can simply run the test once, and check there is nothing(no daemon/service) removing files in /tmp/.. dir b) If you could bypass the unlink (patch pasted below to do so) and check once, that would be great [1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005479#10 --- a/src/toil/jobStores/fileJobStore.py +++ b/src/toil/jobStores/fileJobStore.py @@ -489,13 +489,16 @@ return except OSError as e: if e.errno == errno.EEXIST: -# Overwrite existing file, emulating shutil.copyfile(). -os.unlink(localFilePath) -# It would be very unlikely to fail again for same reason but possible -# nonetheless in which case we should just give up. -os.link(jobStoreFilePath, localFilePath) -# Now we succeeded and don't need to copy -return +try: +# Overwrite existing file, emulating shutil.copyfile(). +os.unlink(localFilePath) +# It would be very unlikely to fail again for same reason but possible +# nonetheless in which case we should just give up. +os.link(jobStoreFilePath, localFilePath) +# Now we succeeded and don't need to copy +return +except: +pass elif e.errno == errno.EXDEV: # It's a cross-device link even though it didn't appear to be. # Just keep going and hit the file copy case. OpenPGP_signature Description: OpenPGP digital signature
Bug#1006384: closed by Debian FTP Masters (reply to Olivier Sallou ) (Bug#1006384: fixed in logol 1.7.9+dfsg-2)
Hi, On 01-03-2022 12:01, Paul Gevers wrote: This "fix" suggest there may be more breakage, normally the Release Team would schedule binNMU's. Can you please elaborate how ABI is normally maintained within swi-prolog, such that the rebuilds can be detected and requested? I fail to see how in the case of logol and swi-prolog the right versions are chosen. In other words, I think the "fixed" logol can migrate to testing even if swi-prolog does not and will be broken in testing until swi-prolog can migrate. Normally *versioned* dependencies should prevent this. I just read the backlog of the bug report (by default, submitters of bug reports in Debian don't get notified of messages, I missed the discussion). It seems my worry was already raised. The bug was reassigned to logol, so the swi-prolog maintainers missed my message. I checked, there are more reverse build dependencies of swi-prolog, I'm afraid there's more breakage that hasn't been detected yet. (eye seems to go in lockstep, so that package currently seems OK). Maybe swi-prolog maintainers can comment. Paul OpenPGP_signature Description: OpenPGP digital signature
Processed: your mail
Processing commands for cont...@bugs.debian.org: > severity #1006699 normal Bug #1006699 [kde-cli-tools] kde-cli-tools: kde-cli-toold installation blocked by another package already installed kde-runtime Severity set to 'normal' from 'grave' > End of message, stopping processing here. Please contact me if you need assistance. -- 1006699: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006699 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1005479: toil: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.10 3.9" returned exit code 13
Hi, On 02-03-2022 16:53, Nilesh Patra wrote: Sascha even pointed out that it goes fine on reproducible build machines, and this package runs same build time test as autopkgtest Yes, but normally not in lxc. The salsa pipeline was passing as well[1] which IIRC uses similar setup as debci. True, as far as I'm aware. I tried re-triggering it to check once again but looks like runners are not up unfortunately. You mean the salsa ones, right? ci.d.n runners should all be up. And so if you could trigger a test suite for this package at your end once, and help debug it, that'd be really nice. What do you propose I look for? I'm not very good at debugging random software. Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#1002166: marked as done (sdrangelove: FTBFS: gnuradiothread.cpp:139:23: error: no matching function for call to ‘gr::top_block::connect(osmosdr::source::sptr&, int, gr_adaptor_sptr&, int)’)
Your message dated Wed, 02 Mar 2022 16:18:03 +
with message-id
and subject line Bug#1006693: Removed package(s) from unstable
has caused the Debian Bug report #1002166,
regarding sdrangelove: FTBFS: gnuradiothread.cpp:139:23: error: no matching
function for call to ‘gr::top_block::connect(osmosdr::source::sptr&, int,
gr_adaptor_sptr&, int)’
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.)
--
1002166: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002166
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sdrangelove
Version: 0.0.1.20150707-5
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211220 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> cd /<>/obj-x86_64-linux-gnu/plugins/samplesource/gnuradio &&
> /usr/bin/c++ -DBOOST_ALL_NO_LIB -DBOOST_SYSTEM_DYN_LINK -DQT_CORE_LIB
> -DQT_GUI_LIB -DQT_MULTIMEDIA_LIB -DQT_NETWORK_LIB -DQT_NO_DEBUG
> -DQT_OPENGL_LIB -DQT_PLUGIN -DQT_SHARED -DQT_WIDGETS_LIB -DUSE_FFTW
> -DUSE_SIMD -Dinputgnuradio_EXPORTS
> -I/<>/obj-x86_64-linux-gnu/plugins/samplesource/gnuradio/inputgnuradio_autogen/include
> -I/<>/obj-x86_64-linux-gnu -I/<>/include
> -I/<>/include-gpl
> -I/<>/plugins/samplesource/gnuradio
> -I/<>/obj-x86_64-linux-gnu/plugins/samplesource/gnuradio
> -isystem /usr/include/x86_64-linux-gnu/qt5 -isystem
> /usr/include/x86_64-linux-gnu/qt5/QtCore -isystem
> /usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -isystem
> /usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem
> /usr/include/x86_64-linux-gnu/qt5/QtGui -isystem
> /usr/include/x86_64-linux-gnu/qt5/QtOpenGL -isystem
> /usr/include/x86_64-linux-gnu/qt5/QtMultimedia -isystem
> /usr/include/x86_64-linux-gnu/qt5/QtNetwork -g -O2
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -O3 -DNDEBUG -msse2
> -fPIC -fPIC -MD -MT
> plugins/samplesource/gnuradio/CMakeFiles/inputgnuradio.dir/gnuradiothread.cpp.o
> -MF CMakeFiles/inputgnuradio.dir/gnuradiothread.cpp.o.d -o
> CMakeFiles/inputgnuradio.dir/gnuradiothread.cpp.o -c
> /<>/plugins/samplesource/gnuradio/gnuradiothread.cpp
> /<>/plugins/samplesource/gnuradio/gnuradiothread.cpp: In member
> function ‘virtual void GnuradioThread::run()’:
> /<>/plugins/samplesource/gnuradio/gnuradiothread.cpp:139:23:
> error: no matching function for call to
> ‘gr::top_block::connect(osmosdr::source::sptr&, int, gr_adaptor_sptr&, int)’
> 139 | m_top->connect(m_src, 0, adaptor, 0);
> | ~~^~
> In file included from /usr/include/gnuradio/top_block.h:15,
> from
> /<>/plugins/samplesource/gnuradio/gnuradiothread.h:26,
> from
> /<>/plugins/samplesource/gnuradio/gnuradiothread.cpp:21:
> /usr/include/gnuradio/hier_block2.h:83:10: note: candidate: ‘void
> gr::hier_block2::connect(gr::basic_block_sptr)’
>83 | void connect(basic_block_sptr block);
> | ^~~
> /usr/include/gnuradio/hier_block2.h:83:10: note: candidate expects 1
> argument, 4 provided
> /usr/include/gnuradio/hier_block2.h:93:10: note: candidate: ‘void
> gr::hier_block2::connect(gr::basic_block_sptr, int, gr::basic_block_sptr,
> int)’
>93 | void connect(basic_block_sptr src, int src_port, basic_block_sptr
> dst, int dst_port);
> | ^~~
> /usr/include/gnuradio/hier_block2.h:93:71: note: no known conversion for
> argument 3 from ‘gr_adaptor_sptr’ {aka ‘boost::shared_ptr’} to
> ‘gr::basic_block_sptr’ {aka ‘std::shared_ptr’}
>93 | void connect(basic_block_sptr src, int src_port, basic_block_sptr
> dst, int dst_port);
> |
> ~^~~
> make[3]: ***
> [plugins/samplesource/gnuradio/CMakeFiles/inputgnuradio.dir/build.make:139:
> plugins/samplesource/gnuradio/CMakeFiles/inputgnuradio.dir/gnuradiothread.cpp.o]
> Error 1
The full build log is available from:
http://qa-logs.debian.net/2021/12/20/sdrangelove_0.0.1.20150707-5_unstable.log
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
Bug#1005479: toil: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.10 3.9" returned exit code 13
Hi Paul, On 3/2/22 9:09 PM, Paul Gevers wrote: On 02-03-2022 14:58, Nilesh Patra wrote: @Paul, could you please help reproduce this in the debci environment and help us with any clues as to what might be wrong? The autopkgtest command line is at the top of each log. I am aware, and I use something $similar, but that is not working for me and Sascha locally, hence asked for help :) Sascha even pointed out that it goes fine on reproducible build machines, and this package runs same build time test as autopkgtest The salsa pipeline was passing as well[1] which IIRC uses similar setup as debci. I tried re-triggering it to check once again but looks like runners are not up unfortunately. And so if you could trigger a test suite for this package at your end once, and help debug it, that'd be really nice. [1]: https://salsa.debian.org/med-team/toil/-/jobs/2396200 Regards, Nilesh OpenPGP_signature Description: OpenPGP digital signature
Bug#1005479: toil: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.10 3.9" returned exit code 13
Hi, On 02-03-2022 14:58, Nilesh Patra wrote: @Paul, could you please help reproduce this in the debci environment and help us with any clues as to what might be wrong? The autopkgtest command line is at the top of each log. | File "/usr/lib/python3/dist-packages/toil/jobStores/fileJobStore.py", line 498, in read_file |os.link(jobStoreFilePath, local_path) | OSError: [Errno 18] Invalid cross-device link: '/tmp/autopkgtest-lxc.rgt3f050/downtmp/build.YHo/src/jobstore-test-de9381ff-d8be-4b36-a691-be2c5fa759d2/files/no-job/file-d7145278c6b84845bd03cf5cff29e690/stream' -> '/home/debci/tmp/tmp1lgiu28c' > It looks (to me) that home and tmp are mounted on different partitions and os.link does not work with such a setting. I *think* the /tmp inside the lxc is mapped to /tmp of the host. /home is completely native to the container. (Not sure if all this matters). On *some* architectures /tmp and /var/lib/lxc of the host are on a separate partitions with respect to the rest. I'm pretty sure that for all our architectures all files inside the container are on the same partition. Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#971783: Any news ?
Hi Mike, there is a workarround to auto restart the mate-volume-control-status-icon when it suddenly stops: $ systemctl --user edit app-mate\\x2dvolume\\x2dcontrol\\x2dstatus\\x2dicon-autostart.service Add between commented lines: [Service] Restart=always $ systemctl --user daemon-reload $ systemctl --user restart app-mate\\x2dvolume\\x2dcontrol\\x2dstatus\\x2dicon-autostart.service Max. 15 février 2022 22:01 "Mike Gabriel" a écrit: > On So 13 Feb 2022 10:37:22 CET, Maxime G. wrote: > >> Hello. >> >> In Debian stable we try to have stable packages. But >> volume-control-applet is not stable and crashes. >> Despite the logs I sent earlier, here is a way to reproduce the problem: >> - Connect a bluetooth speaker. >> - Switch the main output of pulseaudio to the speaker. >> - Play a media (web browser or player) >> - Turn off the bluetooth speaker. >> -> volume-control-applet crash >> >> Thank you. > > This will surely help finding the issue. I haven't had time for this, > yet. But with a fool proof way of reproducing this, chances to get > this fixes are getting bigger. > > Thanks, > Mike > > -- > > DAS-NETZWERKTEAM > c\o Technik- und Ökologiezentrum Eckernförde > Mike Gabriel, Marienthaler Str. 17, 24340 Eckernförde > mobile: +49 (1520) 1976 148 > landline: +49 (4351) 850 8940 > > GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22 0782 9AF4 6B30 2577 1B31 > mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de
Bug#1002872: marked as done (libgl1-mesa-dri: crashes on pre-SSE2 CPUs due to movsd)
Your message dated Wed, 02 Mar 2022 14:42:32 + with message-id and subject line Bug#1002872: fixed in mesa 21.3.7-1 has caused the Debian Bug report #1002872, regarding libgl1-mesa-dri: crashes on pre-SSE2 CPUs due to movsd 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.) -- 1002872: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002872 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libgl1-mesa-dri Version: 21.3.0~rc5-1 Severity: critical Justification: breaks the whole system X-Debbugs-Cc: karogyoker2+deb...@gmail.com Dear Maintainer, When I start GNOME Web (epiphany-browser) and open certain pages (almost any page, but for example gmail.com), the tab crashes with a white background and a very sad face in a gray rounded rectangle saying that something wrong happened and that I have to contact my system administrator. The same screen is being shown if I choose gdm3 as the default desktop manager, making the system unbootable as I cannot log in or do anything. I can boot into Debian if I set the desktop manager to lightdm by selecting the rescue option from GRUB and then changing the desktop manager via dpkg-reconfigure lightdm. Then the same crash screen shows for a few seconds but then it disappears and lightdm's login screen shows up. After logging in via lightdm, it is using the MATE desktop environment and I receive multiple "Cinnamon just crashed" error messages, do I want to restart it or not, I can just close the dialog and then it works seemingly fine. I cannot open any web pages with firefox-esr at all. The tabs are crashing due to illegal instruction. Here is a report about it: https://crash- stats.mozilla.org/report/index/bp-04d2a015-e8bf-463f-a9da-a3ad40211221 I cannot play any videos with smplayer, mplayer or with vlc. I've tried the same image (debian-testing-i386-netinst.iso) in a virtual machine on a computer with SSE2 and everything just worked fine. I was able to open any web page in GNOME Web or firefox-esr and log in via gdm3 without any issues. "Cinnamon just crashed" error messages were not present at all. I didn't see any sad faces in a gray rounded rectangle on a white background. I was able to play videos in smplayer, mplayer and vlc. I suggest that https://wiki.debian.org/SIMDEverywhere might be helpful in developing a patch, if it isn't just a compiler flag fix. If this issue/bug is unfixable, the package should depend on package sse2-support (i386 only). Back to GNOME Web: I have attached gdb to the WebKitWebProcess and tried to open gmail.com to see what happens. This happens: Thread 8 "eadedCompositor" received signal SIGILL, Illegal instruction. [Switching to Thread 0xa9263ac0 (LWP 13336)] 0xa6ca3a2e in ?? () from target:/usr/lib/i386-linux-gnu/dri/swrast_dri.so (gdb) bt full #0 0xa6ca3a2e in ?? () from target:/usr/lib/i386-linux-gnu/dri/swrast_dri.so No symbol table info available. #1 0xa72653fa in ?? () from target:/usr/lib/i386-linux-gnu/dri/swrast_dri.so No symbol table info available. #2 0xa7266629 in ?? () from target:/usr/lib/i386-linux-gnu/dri/swrast_dri.so No symbol table info available. #3 0xa6d6d998 in ?? () from target:/usr/lib/i386-linux-gnu/dri/swrast_dri.so No symbol table info available. #4 0xa677bc43 in ?? () from target:/usr/lib/i386-linux-gnu/dri/swrast_dri.so No symbol table info available. #5 0xa6717676 in ?? () from target:/usr/lib/i386-linux-gnu/dri/swrast_dri.so No symbol table info available. #6 0xa6c53370 in ?? () from target:/usr/lib/i386-linux-gnu/dri/swrast_dri.so No symbol table info available. #7 0xa838bebe in ?? () from target:/lib/i386-linux-gnu/libGLX_mesa.so.0 No symbol table info available. #8 0xa8389a25 in ?? () from target:/lib/i386-linux-gnu/libGLX_mesa.so.0 No symbol table info available. #9 0xb08e5e04 in ?? () from target:/lib/i386-linux-gnu/libGLX.so.0 No symbol table info available. #10 0xb6389e59 in ?? () from target:/lib/i386-linux-gnu/libwebkit2gtk-4.0.so.37 No symbol table info available. #11 0xb638a534 in ?? () from target:/lib/i386-linux-gnu/libwebkit2gtk-4.0.so.37 --Type for more, q to quit, c to continue without paging--c No symbol table info available. #12 0xb638c70e in ?? () from target:/lib/i386-linux-gnu/libwebkit2gtk-4.0.so.37 No symbol table info available. #13 0xb6349fb9 in ?? () from target:/lib/i386-linux-gnu/libwebkit2gtk-4.0.so.37 No symbol table info available. #14 0xb634ab8e in ?? () from target:/lib/i386-linux-gnu/libwebkit2gtk-4.0.so.37 No symbol table info available. #15 0xb638c5cc in ?? () from target:/lib/i386-linux-gnu/libwebkit2gtk-4.0.so.37 No
Processed: RM: sdrangelove -- RoM; dead upstream
Processing control commands: > clone -1 -2 Bug #1002166 [src:sdrangelove] sdrangelove: FTBFS: gnuradiothread.cpp:139:23: error: no matching function for call to ‘gr::top_block::connect(osmosdr::source::sptr&, int, gr_adaptor_sptr&, int)’ Bug 1002166 cloned as bug 1006693 > retitle -2 RM: sdrangelove -- RoM; dead upstream Bug #1006693 [src:sdrangelove] sdrangelove: FTBFS: gnuradiothread.cpp:139:23: error: no matching function for call to ‘gr::top_block::connect(osmosdr::source::sptr&, int, gr_adaptor_sptr&, int)’ Changed Bug title to 'RM: sdrangelove -- RoM; dead upstream' from 'sdrangelove: FTBFS: gnuradiothread.cpp:139:23: error: no matching function for call to ‘gr::top_block::connect(osmosdr::source::sptr&, int, gr_adaptor_sptr&, int)’'. > severity -2 normal Bug #1006693 [src:sdrangelove] RM: sdrangelove -- RoM; dead upstream Severity set to 'normal' from 'serious' > reassign -2 ftp.debian.org Bug #1006693 [src:sdrangelove] RM: sdrangelove -- RoM; dead upstream Bug reassigned from package 'src:sdrangelove' to 'ftp.debian.org'. No longer marked as found in versions sdrangelove/0.0.1.20150707-5. Ignoring request to alter fixed versions of bug #1006693 to the same values previously set -- 1002166: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002166 1006693: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006693 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1002166: RM: sdrangelove -- RoM; dead upstream
Control: clone -1 -2 Control: retitle -2 RM: sdrangelove -- RoM; dead upstream Control: severity -2 normal Control: reassign -2 ftp.debian.org > > Source: sdrangelove > > Version: 0.0.1.20150707-5 > > Severity: serious > > Justification: FTBFS > > Tags: bookworm sid ftbfs > > User: lu...@debian.org > > Usertags: ftbfs-20211220 ftbfs-bookworm > > > > Hi, > > > > During a rebuild of all packages in sid, your package failed to build > > on amd64. > > sdrangelove hasn't really been touched upstream since 2015 (except 3 > more or less boring git commits), so I propose we remove it. Doing that now: Please remove sdrangelove from unstable. Christoph
Processed: Re: toil: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.10 3.9" returned exit code 13
Processing control commands:
> severity -1 serious
Bug #1005479 [src:toil] toil: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p "3.10 3.9" returned exit code 13
Severity set to 'serious' from 'normal'
> tags -1 moreinfo
Bug #1005479 [src:toil] toil: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p "3.10 3.9" returned exit code 13
Added tag(s) moreinfo.
--
1005479: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005479
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1006690: silx autopkg tests fail (missing test dependency)
Package: src:silx Version: 1.0.0+dfsg-2 Severity: serious Tags: sid bookworm silx autopkg tests fail (missing test dependency): [...] autopkgtest [21:49:30]: test command1: [--- Testing with python3.10: Traceback (most recent call last): File "", line 1, in File "/usr/lib/python3/dist-packages/silx/test/__init__.py", line 32, in import pytest ModuleNotFoundError: No module named 'pytest' autopkgtest [21:49:30]: test command1: ---] autopkgtest [21:49:31]: test command1: - - - - - - - - - - results - - - -
Bug#1006557: marked as done (toybox: Causes initramfs-tools trigger to fail without giving a reason)
Your message dated Wed, 02 Mar 2022 13:21:31 + with message-id and subject line Bug#1006557: fixed in toybox 0.8.6+dfsg-3 has caused the Debian Bug report #1006557, regarding toybox: Causes initramfs-tools trigger to fail without giving a reason 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.) -- 1006557: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006557 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: toybox Version: 0.8.6+dfsg-2 Severity: serious Hi, since I upgraded toybox to 0.8.6+dfsg-2, the initramfs-tools trigger fails on my machine: Processing triggers for initramfs-tools (0.140) ... update-initramfs: Generating /boot/initrd.img-5.16.0-3-amd64 E: /usr/share/initramfs-tools/hooks/zy-toybox failed with return 1. update-initramfs: failed for /boot/initrd.img-5.16.0-3-amd64 with 1. dpkg: error processing package initramfs-tools (--configure): installed initramfs-tools package post-installation script subprocess returned error exit status 1 Unfortunately /usr/share/initramfs-tools/hooks/zy-toybox doesn't note what exactly went wrong. I've added a "set -x" to /usr/share/initramfs-tools/hooks/zy-toybox and it fails as follows: ~ # dpkg --configure -a Setting up initramfs-tools (0.140) ... update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools (0.140) ... update-initramfs: Generating /boot/initrd.img-5.16.0-3-amd64 + echo + exit 0 + TB_BIN=/usr/bin/toybox + [ n = ] + [ -r /usr/share/initramfs-tools/hook-functions ] + . /usr/share/initramfs-tools/hook-functions + [ -f /var/tmp/mkinitramfs_Z7BaTH/bin/sh ] + rm -f /var/tmp/mkinitramfs_Z7BaTH/bin/toybox + copy_exec /usr/bin/toybox /bin/toybox + local src target x nonoptlib ret + src=/usr/bin/toybox + target=/bin/toybox + copy_file binary /usr/bin/toybox /bin/toybox + local type src target link_target + type=binary + src=/usr/bin/toybox + target=/bin/toybox + [ -f /usr/bin/toybox ] + return 2 + return 1 E: /usr/share/initramfs-tools/hooks/zy-toybox failed with return 1. update-initramfs: failed for /boot/initrd.img-5.16.0-3-amd64 with 1. dpkg: error processing package initramfs-tools (--configure): installed initramfs-tools package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: initramfs-tools dpkg --configure -a 5.13s user 2.38s system 96% cpu 7.800 total Changing TB_BIN=/usr/bin/toybox to TB_BIN=/bin/toybox fixes this. -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (990, 'unstable'), (600, 'testing'), (500, 'unstable-debug'), (500, 'buildd-unstable'), (110, 'experimental'), (1, 'experimental-debug'), (1, 'buildd-experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.16.0-1-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_CPU_OUT_OF_SPEC, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) LSM: AppArmor: enabled Versions of packages toybox depends on: ii libc6 2.33-7 ii libcrypt1 1:4.4.27-1.1 toybox recommends no packages. toybox suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: toybox Source-Version: 0.8.6+dfsg-3 Done: Antoni Villalonga We believe that the bug you reported is fixed in the latest version of toybox, 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 1006...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Antoni Villalonga (supplier of updated toybox 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, 27 Feb 2022 23:39:07 + Source: toybox Architecture: source Version: 0.8.6+dfsg-3 Distribution: unstable Urgency: medium Maintainer: Antoni Villalonga Changed-By: Antoni Villalonga Closes: 1006557 Changes: toybox (0.8.6+dfsg-3) unstable; urgency=medium . * Fix binary path on initramfs hook. Thanks to Axel Beckert for reporting and patch (Closes: #1006557) Checksums-Sha1:
Bug#1005616: marked as done (almanah: FTBFS: ../data/meson.build:2:5: ERROR: Function does not take positional arguments.)
Your message dated Wed, 02 Mar 2022 12:03:32 + with message-id and subject line Bug#1005616: fixed in almanah 0.12.3-2 has caused the Debian Bug report #1005616, regarding almanah: FTBFS: ../data/meson.build:2:5: ERROR: Function does not take positional arguments. 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.) -- 1005616: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005616 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: almanah Version: 0.12.3-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220212 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules binary > dh binary >dh_update_autotools_config >dh_autoreconf >dh_auto_configure > cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. > --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc > --localstatedir=/var --libdir=lib/x86_64-linux-gnu > The Meson build system > Version: 0.61.1 > Source dir: /<> > Build dir: /<>/obj-x86_64-linux-gnu > Build type: native build > Project name: almanah > Project version: 0.12.3 > C compiler for the host machine: cc (gcc 11.2.0 "cc (Debian 11.2.0-16) > 11.2.0") > C linker for the host machine: cc ld.bfd 2.38 > Host machine cpu family: x86_64 > Host machine cpu: x86_64 > Program python3 found: YES (/usr/bin/python3) > Found pkg-config: /usr/bin/pkg-config (0.29.2) > Run-time dependency glib-2.0 found: YES 2.70.3 > Run-time dependency gtk+-3.0 found: YES 3.24.31 > Run-time dependency gmodule-2.0 found: YES 2.70.3 > Run-time dependency gthread-2.0 found: YES 2.70.3 > Run-time dependency gio-2.0 found: YES 2.70.3 > Run-time dependency gtksourceview-3.0 found: YES 3.24.11 > Run-time dependency sqlite3 found: YES 3.37.2 > Run-time dependency cairo found: YES 1.16.0 > Run-time dependency atk found: YES 2.36.0 > Run-time dependency gcr-base-3 found: YES 3.40.0 > Run-time dependency cryptui-0.0 found: YES 3.12.2 > Run-time dependency gpgme found: YES 1.16.0-unknown > Run-time dependency libecal-2.0 found: YES 3.42.4 > Run-time dependency libedataserver-1.2 found: YES 3.42.4 > Run-time dependency gtkspell3-3.0 found: YES 3.0.10 > Program appstream-util found: YES (/usr/bin/appstream-util) > Program desktop-file-validate found: YES (/usr/bin/desktop-file-validate) > Configuring config.h.in using configuration > > ../data/meson.build:2:5: ERROR: Function does not take positional arguments. > > A full log can be found at > /<>/obj-x86_64-linux-gnu/meson-logs/meson-log.txt > cd obj-x86_64-linux-gnu && tail -v -n \+0 meson-logs/meson-log.txt > ==> meson-logs/meson-log.txt <== > Build started at 2022-02-12T22:46:34.789142 > Main binary: /usr/bin/python3 > Build Options: -Dprefix=/usr -Dlibdir=lib/x86_64-linux-gnu > -Dlocalstatedir=/var -Dsysconfdir=/etc -Dbuildtype=plain > -Dwrap_mode=nodownload > Python system: Linux > The Meson build system > Version: 0.61.1 > Source dir: /<> > Build dir: /<>/obj-x86_64-linux-gnu > Build type: native build > Project name: almanah > Project version: 0.12.3 > Sanity testing C compiler: cc > Is cross compiler: False. > Sanity check compiler command line: cc sanitycheckc.c -o sanitycheckc.exe -g > -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 > -D_FILE_OFFSET_BITS=64 -Wl,-z,relro -Wl,-z,now > Sanity check compile stdout: > > - > Sanity check compile stderr: > > - > Running test binary command: > /<>/obj-x86_64-linux-gnu/meson-private/sanitycheckc.exe > C compiler for the host machine: cc (gcc 11.2.0 "cc (Debian 11.2.0-16) > 11.2.0") > C linker for the host machine: cc ld.bfd 2.38 > Sanity testing C compiler: cc > Is cross compiler: False. > Sanity check compiler command line: cc sanitycheckc.c -o sanitycheckc.exe -g > -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 > -D_FILE_OFFSET_BITS=64 -Wl,-z,relro -Wl,-z,now > Sanity check compile stdout: > > - > Sanity check compile stderr: > > - > Running test binary command: > /<>/obj-x86_64-linux-gnu/meson-private/sanitycheckc.exe > C compiler for the build machine: cc (gcc 11.2.0 "cc (Debian 11.2.0-16) > 11.2.0") > C linker for the build machine: cc ld.bfd 2.38 > Build machine cpu family: x86_64 > Build machine cpu: x86_64 > Host machine cpu family: x86_64 > Host machine cpu: x86_64 > Target machine cpu family: x86_64 > Target machine cpu: x86_64 >
Bug#1005946: marked as done (nvidia-graphics-drivers-tesla-510: incompatible with xorg-server video ABI 25)
Your message dated Wed, 02 Mar 2022 10:34:18 + with message-id and subject line Bug#1005946: fixed in nvidia-graphics-drivers-tesla-510 510.47.03-2 has caused the Debian Bug report #1005946, regarding nvidia-graphics-drivers-tesla-510: incompatible with xorg-server video ABI 25 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.) -- 1005946: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005946 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: nvidia-graphics-drivers-tesla-418 Version: 418.226.00-1 Severity: serious xorg-server's video ABI was recently bumped, and nvidia-graphics-drivers-tesla-418 only declares compatibility for up to v24. Cheers, Julien --- End Message --- --- Begin Message --- Source: nvidia-graphics-drivers-tesla-510 Source-Version: 510.47.03-2 Done: Andreas Beckmann We believe that the bug you reported is fixed in the latest version of nvidia-graphics-drivers-tesla-510, 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. Andreas Beckmann (supplier of updated nvidia-graphics-drivers-tesla-510 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 02 Mar 2022 10:59:19 +0100 Source: nvidia-graphics-drivers-tesla-510 Architecture: source Version: 510.47.03-2 Distribution: unstable Urgency: medium Maintainer: Debian NVIDIA Maintainers Changed-By: Andreas Beckmann Closes: 1005946 Changes: nvidia-graphics-drivers-tesla-510 (510.47.03-2) unstable; urgency=medium . * Add xorg-video-abi-25 (Xorg Xserver 21) as alternative dependency. (Closes: #1005946) Checksums-Sha1: 924f7dd9a8f32d3c1fae962ee5f074e0d5010bd6 7386 nvidia-graphics-drivers-tesla-510_510.47.03-2.dsc 740e550242e9205bb063e8e6f1e1a9438bebdf85 209652 nvidia-graphics-drivers-tesla-510_510.47.03-2.debian.tar.xz b0ddf593d5d0041c75d55778f60804881b47f192 5612 nvidia-graphics-drivers-tesla-510_510.47.03-2_source.buildinfo Checksums-Sha256: 30f8a387280475f4963aa8522e21ce6da485503c167a10cee0c1142b279e442d 7386 nvidia-graphics-drivers-tesla-510_510.47.03-2.dsc b7f72b826e26ade35567b17d8de5dfb7a684dcac0980b324de3e773c2af78223 209652 nvidia-graphics-drivers-tesla-510_510.47.03-2.debian.tar.xz a015aded6cbe494a4f54f03503a01b686df51924a5713887671d2f8193a92124 5612 nvidia-graphics-drivers-tesla-510_510.47.03-2_source.buildinfo Files: f29a6d0a1f4ca601aaf663d6252c8e95 7386 non-free/libs optional nvidia-graphics-drivers-tesla-510_510.47.03-2.dsc a310b0293d391bd72a393c102005c6ce 209652 non-free/libs optional nvidia-graphics-drivers-tesla-510_510.47.03-2.debian.tar.xz 546cfa88ed2c55d0c5cec860041060b6 5612 non-free/libs optional nvidia-graphics-drivers-tesla-510_510.47.03-2_source.buildinfo -BEGIN PGP SIGNATURE- iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAmIfQ8MQHGFuYmVAZGVi aWFuLm9yZwAKCRBfsz+TWentCCybEACwPyNb2okjIHbzSIU8x6s40J47H9Yl9uOd C8GyUayJXX3Z34kzlc6Z+yIVmQQHpcbB8iNGJy8DJiluhdFE8R29k+Z4g7cYCnnu IkQq4FVx1NW7P34r0nAooPTau7ckITRCIqA2tWYUGDcmBzkw2Zh+LF22MTobW8p2 ULmga+U2vTh8WHqCbBwL5wWs3l8+2Nza4urf81ver26ECnQIqSBw11+RYQxGkwRl eQwwkg5JZ6h9UiANmnd5NVJi1bfE1GT/RvVX/QG5wf0vg1E4KFzoXmwrOWhoKObM 0uNi22nEbDk7v0m4Y+oCRpEhP3B1sE8GQC54DziHiOKYIydu4B74J1+JmdwWshi4 HwEjOFGDb/+QhhVMNGaRhkeg/j/Zw2GVm4ff9MycXqaxc4MsxGR8ZMFLiRkB1g5T 2zQXIYVsZxrqLXzan/f0H+cv5Wl9SypRUsEaUBIMqL/5g17WEOJCrxGNm+4G/w39 SXwbqn15vqLFb2fygT3yn99MYbGzUiHVQbx9TZlB8zEPpma9329jtdaZhI/PYi/C gYwBtMguwxHzdIIa0P4RncV8bYoarLrTT63DymSiiEDM59i5QmnH5V2zIMp7xJIY KEvXIDJEWn+ga08r4hy41BRG1/enIQLvqRCSpKO9FWUrA2gtE2m0cKbZBQUdyz3p vSh7fLNGPQ== =wp9H -END PGP SIGNATURE End Message ---
Processed: Re: Bug#1006664: python3-fonttools has unmet dependencies
Processing control commands: > affects 1006664 python3-matplotlib Bug #1006664 [python3-fonttools] python3-fonttools has unmet dependencies Added indication that 1006664 affects python3-matplotlib > severity 1006664 grave Bug #1006664 [python3-fonttools] python3-fonttools has unmet dependencies Severity set to 'grave' from 'serious' -- 1006664: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006664 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1006664: python3-fonttools has unmet dependencies
Control: affects 1006664 python3-matplotlib Control: severity 1006664 grave Raising the severity to Grave since it makes the package unusable (uninstallable). Could argue for Severity: Critical, since it breaks unrelated software (it breaks any package that depends on python3-matplotlib, and there are a lot of them).
Processed: fixed 982766 in 5.58.2+~cs5.11.7-1
Processing commands for cont...@bugs.debian.org: > fixed 982766 5.58.2+~cs5.11.7-1 Bug #982766 [src:node-webpack] node-webpack: remove dependency on node-uglifyjs-webpack-plugin Marked as fixed in versions node-webpack/5.58.2+~cs5.11.7-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 982766: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982766 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: fix affects
Processing commands for cont...@bugs.debian.org: > affects 1006664 - cctbx Bug #1006664 [python3-fonttools] python3-fonttools has unmet dependencies Removed indication that 1006664 affects cctbx > affects 1006664 + src:cctbx Bug #1006664 [python3-fonttools] python3-fonttools has unmet dependencies Added indication that 1006664 affects src:cctbx > affects 1006664 - wxmplot Bug #1006664 [python3-fonttools] python3-fonttools has unmet dependencies Removed indication that 1006664 affects wxmplot > affects 1006664 + src:wxmplot Bug #1006664 [python3-fonttools] python3-fonttools has unmet dependencies Added indication that 1006664 affects src:wxmplot > affects 910436 - cctbx Bug #910436 [wnpp] RFP: python3-unicodedata2 -- Provides access via Pyhton to the Unicode database. Bug #902029 [wnpp] RFP: python3-unicodedata2 -- Provides access via Pyhton to the Unicode database. Removed indication that 910436 affects cctbx Removed indication that 902029 affects cctbx > affects 910436 + src:cctbx Bug #910436 [wnpp] RFP: python3-unicodedata2 -- Provides access via Pyhton to the Unicode database. Bug #902029 [wnpp] RFP: python3-unicodedata2 -- Provides access via Pyhton to the Unicode database. Added indication that 910436 affects src:cctbx Added indication that 902029 affects src:cctbx > affects 910436 - wxmplot Bug #910436 [wnpp] RFP: python3-unicodedata2 -- Provides access via Pyhton to the Unicode database. Bug #902029 [wnpp] RFP: python3-unicodedata2 -- Provides access via Pyhton to the Unicode database. Removed indication that 910436 affects wxmplot Removed indication that 902029 affects wxmplot > affects 910436 + src:wxmplot Bug #910436 [wnpp] RFP: python3-unicodedata2 -- Provides access via Pyhton to the Unicode database. Bug #902029 [wnpp] RFP: python3-unicodedata2 -- Provides access via Pyhton to the Unicode database. Added indication that 910436 affects src:wxmplot Added indication that 902029 affects src:wxmplot > thanks Stopping processing here. Please contact me if you need assistance. -- 1006664: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006664 902029: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902029 910436: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910436 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Blocked
Processing commands for cont...@bugs.debian.org: > block 1006252 by 1006664 Bug #1006252 [src:cctbx] cctbx: reproducible builds: Timestamps embedded in boost_python_meta_ext.so.0.0.1 1006252 was not blocked by any bugs. 1006252 was not blocking any bugs. Added blocking bug(s) of 1006252: 1006664 > affects 1006664 + cctbx Bug #1006664 [python3-fonttools] python3-fonttools has unmet dependencies Added indication that 1006664 affects cctbx > affects 1006664 + wxmplot Bug #1006664 [python3-fonttools] python3-fonttools has unmet dependencies Added indication that 1006664 affects wxmplot > block 1006664 by 902029 Bug #1006664 [python3-fonttools] python3-fonttools has unmet dependencies 1006664 was not blocked by any bugs. 1006664 was blocking: 1006252 Added blocking bug(s) of 1006664: 910436 and 902029 > affects 902029 + cctbx Bug #902029 [wnpp] RFP: python3-unicodedata2 -- Provides access via Pyhton to the Unicode database. Bug #910436 [wnpp] RFP: python3-unicodedata2 -- Provides access via Pyhton to the Unicode database. Added indication that 902029 affects cctbx Added indication that 910436 affects cctbx > tag 1006252 - pending Bug #1006252 [src:cctbx] cctbx: reproducible builds: Timestamps embedded in boost_python_meta_ext.so.0.0.1 Removed tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1006252: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006252 1006664: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006664 902029: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902029 910436: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910436 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1006678: ukui-settings-daemon: FTBFS against libkscreen 5.24.2
Package: ukui-settings-daemon Version: 3.1.1-1 Severity: serious Tags: ftbfs In current Debian unstable (and Ubuntu Jammy), ukui-settings-daemon FTBFS against the latest Plasma libkscreen 5.24.2. xrandr-output.cpp: In static member function ‘static void xrandrOutput::readInOutputs(KScreen::ConfigPtr, const QVariantList&)’: xrandr-output.cpp:368:21: error: ‘class KScreen::Output’ has no member named ‘setLogicalSize’ 368 | output->setLogicalSize(QSizeF()); | ^~
Processed: bug #1002356 forwarded to upstream fix
Processing commands for cont...@bugs.debian.org:
> forwarded 1002356 https://github.com/joblib/joblib/commit/69f2b0
Bug #1002356 [src:joblib] joblib: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p "3.10 3.9" returned exit code 13
Set Bug forwarded-to-address to
'https://github.com/joblib/joblib/commit/69f2b0'.
> --
Stopping processing here.
Please contact me if you need assistance.
--
1002356: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002356
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
