Bug#1001657: Ball fails its autopkgtest - how to properly deal with sip files?
Hi Étienne, Am Wed, Dec 15, 2021 at 11:23:17PM +0100 schrieb Étienne Mollier: > > I pushed my changes leading to these errors, but getting the > other bugs affecting ball fixed before Christmas might involve > undoing the setting of SIP_LIBRARIES in d/rules. Thanks a lot for your investigations. I do not think we have a real time limit for ball - but this is a good time to do some polishing in BTW and if we delay the solution it might become forgotten again. That's why I'm asking whether the effort to solve the issue is worth doing compared to simply droping the Python3 package which I consider a valid solution of the problem. Kind regards Andreas. -- http://fam-tille.de
Bug#1001681: marked as done (sight: FTBFS in unstable)
Your message dated Thu, 16 Dec 2021 06:18:37 + with message-id and subject line Bug#1001681: fixed in sight 21.0.0-3 has caused the Debian Bug report #1001681, regarding sight: FTBFS in unstable 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.) -- 1001681: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001681 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: sight Version: 21.0.0-2 Severity: serious User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu jammy Hi Flavien, sight is failing to build in unstable right now with the following error: cd /tmp/sight-21.0.0/obj-x86_64-linux-gnu/libs/io/dimse && /usr/bin/c++ -DBOOST_ALL_DYN_LINK -DBOOST_ALL_NO_LIB -DBOOST_ATOMIC_DYN_LINK -DBOOST_CHRONO_DYN_LINK -DBOOST_DATE_TIME_DYN_LINK -DBOOST_FILESYSTEM_DYN_LINK -DBOOST_IOSTREAMS_DYN_LINK -DBOOST_LOG_DYN_LINK -DBOOST_LOG_SETUP_DYN_LINK -DBOOST_REGEX_DYN_LINK -DBOOST_SPIRIT_USE_PHOENIX_V3 -DBOOST_THREAD_DONT_PROVIDE_DEPRECATED_FEATURES_SINCE_V3_0_0 -DBOOST_THREAD_DYN_LINK -DBOOST_THREAD_PROVIDES_FUTURE -DBOOST_THREAD_VERSION=2 -DIO_DIMSE_EXPORTS -Dio_dimse_EXPORTS -I/tmp/sight-21.0.0/obj-x86_64-linux-gnu/libs/io/dimse/include -I/tmp/sight-21.0.0/libs -I/tmp/sight-21.0.0/libs/core -I/tmp/sight-21.0.0/obj-x86_64-linux-gnu/libs/core/pch/pchData/include/pchData -I/tmp/sight-21.0.0/obj-x86_64-linux-gnu/libs/core/core/include -I/usr/include/libxml2 -I/tmp/sight-21.0.0/obj-x86_64-linux-gnu/libs/core/data/include -g -O2 -ffile-prefix-map=/tmp/sight-21.0.0=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -O3 -DNDEBUG -fPIC -fvisibility=hidden -fvisibility-inlines-hidden -march=sandybridge -mtune=generic -mfpmath=sse -fvisibility=hidden -fvisibility-inlines-hidden -Wall -Wextra -Wconversion -Wno-unused-parameter -Wno-ignored-qualifiers -std=gnu++17 -include "pch.hpp" -Winvalid-pch -MD -MT libs/io/dimse/CMakeFiles/io_dimse.dir/SeriesEnquirer.cpp.o -MF CMakeFiles/io_dimse.dir/SeriesEnquirer.cpp.o.d -o CMakeFiles/io_dimse.dir/SeriesEnquirer.cpp.o -c /tmp/sight-21.0.0/libs/io/dimse/SeriesEnquirer.cpp /tmp/sight-21.0.0/libs/io/dimse/SeriesEnquirer.cpp: In member function 'std::string sight::io::dimse::SeriesEnquirer::findSOPInstanceUID(const string&, unsigned int)': /tmp/sight-21.0.0/libs/io/dimse/SeriesEnquirer.cpp:748:5: error: 'OFIterator' was not declared in this scope; did you mean 'OF_error'? 748 | OFIterator it= responses.begin(); | ^~ | OF_error /tmp/sight-21.0.0/libs/io/dimse/SeriesEnquirer.cpp:748:26: error: expected primary-expression before '*' token 748 | OFIterator it= responses.begin(); | ^ /tmp/sight-21.0.0/libs/io/dimse/SeriesEnquirer.cpp:748:27: error: expected primary-expression before '>' token 748 | OFIterator it= responses.begin(); | ^ /tmp/sight-21.0.0/libs/io/dimse/SeriesEnquirer.cpp:748:29: error: 'it' was not declared in this scope; did you mean 'io'? 748 | OFIterator it= responses.begin(); | ^~ | io I don't know where OFIterator is supposed to come from, but clearly something has changed. Cheers, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer https://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: sight Source-Version: 21.0.0-3 Done: Pierre Gruet We believe that the bug you reported is fixed in the latest version of sight, 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 1001...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Pierre Gruet (supplier of updated sight 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, 15 Dec 2021 23:03:15 +0100 Source: sight Architecture: source Version: 21.0.0-3 Distribution:
Bug#1001289: marked as done (colorclass: needs update for python3.10: 'Mapping' from 'collections' is removed)
Your message dated Thu, 16 Dec 2021 05:33:30 + with message-id and subject line Bug#1001289: fixed in colorclass 2.2.0-2.2 has caused the Debian Bug report #1001289, regarding colorclass: needs update for python3.10: 'Mapping' from 'collections' is removed 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.) -- 1001289: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001289 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: colorclass Version: 2.2.0-2.1 Severity: serious X-Debbugs-CC: debian...@lists.debian.org Tags: sid bookworm User: debian...@lists.debian.org Usertags: needs-update Control: affects -1 src:python3-defaults Dear maintainer(s), With a recent upload of python3-defaults the autopkgtest of colorclass fails in testing when that autopkgtest is run with the binary packages of python3-defaults from unstable. It passes when run with only packages from testing. In tabular form: passfail python3-defaults from testing3.9.8-1 colorclass from testing2.2.0-2.1 all others from testingfrom testing I copied some of the output at the bottom of this report. https://docs.python.org/3.9/library/collections.html says: """ Deprecated since version 3.3, will be removed in version 3.10: Moved Collections Abstract Base Classes to the collections.abc module. For backwards compatibility, they continue to be visible in this module through Python 3.9. """ Time to move on. Currently this regression is blocking the migration of python3-defaults to testing [1]. Of course, python3-defaults shouldn't just break your autopkgtest (or even worse, your package), but it seems to me that the change in python3-defaults was intended and your package needs to update to the new situation. If this is a real problem in your package (and not only in your autopkgtest), the right binary package(s) from python3-defaults should really add a versioned Breaks on the unfixed version of (one of your) package(s). Note: the Breaks is nice even if the issue is only in the autopkgtest as it helps the migration software to figure out the right versions to combine in the tests. 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=python3-defaults https://ci.debian.net/data/autopkgtest/testing/amd64/c/colorclass/17344288/log.gz Testing with python3.10: Traceback (most recent call last): File "", line 1, in File "/usr/lib/python3/dist-packages/colorclass/__init__.py", line 11, in from colorclass.codes import list_tags # noqa File "/usr/lib/python3/dist-packages/colorclass/codes.py", line 4, in from collections import Mapping ImportError: cannot import name 'Mapping' from 'collections' (/usr/lib/python3.10/collections/__init__.py) autopkgtest [20:13:20]: test autodep8-python3 OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: colorclass Source-Version: 2.2.0-2.2 Done: Daniel Baumann We believe that the bug you reported is fixed in the latest version of colorclass, 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 1001...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Daniel Baumann (supplier of updated colorclass 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: Thu, 16 Dec 2021 05:16:44 +0200 Source: colorclass Architecture: source Version: 2.2.0-2.2 Distribution: unstable Urgency: medium Maintainer: Debian Python Modules Team Changed-By: Daniel Baumann Closes: 1001289 Changes: colorclass (2.2.0-2.2) unstable; urgency=medium . * Non-maintainer upload. * Applying patch from Steve Langasek for Python 3.10 (Closes: #1001289). Checksums-Sha1: 1a7301a08c7c4f49b30e7a06a8496e53c39e2496 2109 colorclass_2.2.0-2.2.dsc eb21f80182e6fe12502fad56c79770fbe28eb53e 3016 colorclass_2.2.0-2.2.debian.tar.xz 3e4a33565178fc6980735327f8c5420b75194e2d 7006 colorclass_2.2.0-2.2_amd64.buildinfo
Processed: severity of 1000744 is important
Processing commands for cont...@bugs.debian.org: > severity 1000744 important Bug #1000744 [src:emacs] emacs: FTBFS on mipsel: Ran 3873 tests, 3786 results as expected, 1 unexpected, 86 skipped Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 1000744: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000744 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#999109: marked as done (fortunes-fr: missing required debian/rules targets build-arch and/or build-indep)
Your message dated Thu, 16 Dec 2021 03:04:29 + with message-id and subject line Bug#1001723: Removed package(s) from unstable has caused the Debian Bug report #999109, regarding fortunes-fr: missing required debian/rules targets build-arch and/or build-indep to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 999109: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999109 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: fortunes-fr Version: 0.65+nmu3 Severity: important Justification: Debian Policy section 4.9 Tags: bookworm sid User: debian...@lists.debian.org Usertags: missing-build-arch-indep Dear maintainer, Your package does not include build-arch and/or build-indep targets in debian/rules. This is required by Debian Policy section 4.9, since 2012. https://www.debian.org/doc/debian-policy/ch-source.html#main-building-script-debian-rules Please note that this is also a sign that the packaging of this software could benefit from a refresh. For example, packages using 'dh' cannot be affected by this issue. This mass bug filing was discussed on debian-devel@ in https://lists.debian.org/debian-devel/2021/11/msg00052.html . The severity of this bug will be changed to 'serious' after a month. Best, Lucas --- End Message --- --- Begin Message --- Version: 0.65+nmu3+rm Dear submitter, as the package fortunes-fr has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1001723 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#1001773: dcontainers: FTBFS on s390x in sid
Source: dcontainers Version: 0.8.0~alpha.16-1 Severity: serious User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu jammy Hi Matthias, While rebuilding packages in Ubuntu for the libphobos2-ldc ABI change, I found that dcontainers fails to build from source on s390x: [...] [44/44] gdc -o test_looptest test_looptest.p/test_looptest.d.o -Wl,--allow-shlib-undefined -shared-libphobos -Wl,-z,relro -g -O2 '-ffile-prefix-map=/root/dcontainers-0.8.0~alpha.16=.' -fstack-protector-strong -frelease '-Wl,-rpath,$ORIGIN/' '-Wl,-rpath-link,/root/dcontainers-0.8.0~alpha.16/obj-s390x-linux-gnu/' -Wl,libdcontainers.so.0.8.0 -lstdx-allocator -lmir-core FAILED: test_looptest gdc -o test_looptest test_looptest.p/test_looptest.d.o -Wl,--allow-shlib-undefined -shared-libphobos -Wl,-z,relro -g -O2 '-ffile-prefix-map=/root/dcontainers-0.8.0~alpha.16=.' -fstack-protector-strong -frelease '-Wl,-rpath,$ORIGIN/' '-Wl,-rpath-link,/root/dcontainers-0.8.0~alpha.16/obj-s390x-linux-gnu/' -Wl,libdcontainers.so.0.8.0 -lstdx-allocator -lmir-core /usr/bin/ld: test_looptest.p/test_looptest.d.o: in function `_D4stdx9allocator__T4makeTS10containers5ttree__T5TTreeTiTSQCeQCc10mallocator10MallocatorVbi0VAyaa5_61203c2062Vbi0Vmi64ZQCt4NodeTQCtZQEiFNbNiNfQDhZPQEr': /usr/include/d/stdx-allocator/stdx/allocator/package.d:671: undefined reference to `_D3mir7utility__T3maxTmTmZQjFNaNbNiNfmmZm' collect2: error: ld returned 1 exit status ninja: build stopped: subcommand failed. [...] (https://launchpad.net/ubuntu/+source/dcontainers/0.8.0~alpha.16-1build6/+build/22612941) This build failure is also reproducible in Debian unstable. While the s390x binaries don't need to be rebuilt for the libphobos2-ldc ABI change (because ldc is not available on s390x and s390x uses gdc instead), it is nevertheless a serious bug. It also prevents updating the package in Ubuntu, because unlike Debian, Ubuntu does not have binNMUs. There is a similar build failure on armhf, where gdc appears to be the default D compiler despite ldc being available for this arch. Cheers, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer https://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: PGP signature
Bug#1001765: [Pkg-rust-maintainers] Bug#1001765: src:rust-futures: fails to migrate to testing for too long: makes reverse dependencies uninstallable in testing
I know we expect this for some time in the rust ecosystem, but 60 days ought to be enough for that. I appreciate your efforts to keep testing moving forwards. All the crates that are used by applications in testing that had dependencies on rust-futures have been dealt with (generally by disabling cargo features). That leaves a bunch of crates from an old version of tokio which no longer exist as separate crates in current tokio. The main tokio crate itself (which has an updated version in unstable),and a couple of other miscellaneous crates. These will all be autoremoved in a few days time as a result of bugs 998570 and 998611 If you want to speed things up a bit and avoid rust-tokio cycling out and back in to testing, then you could set removal hints on the following packages. rust-tokio-executor rust-tokio-current-thread rust-tokio-fs rust-tokio-reactor rust-tokio-tcp rust-tokio-threadpool rust-tokio-timer rust-tokio-udp rust-tokio-uds rust-tokio-io rust-bufstream rust-lewton rust-ogg rust-tokio-async-await rust-tokio-codec
Bug#1001770: libgmsh4 needs Breaks+Replaces: libgmsh4 (>= 4.8.4+ds1-1~)
Package: libgmsh4 Version: 4.8.4+ds2-1 Severity: serious Unpacking libgmsh4.8:amd64 (4.8.4+ds2-1) ... dpkg: error processing archive /tmp/apt-dpkg-install-g8oaD4/13-libgmsh4.8_4.8.4+ds2-1_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libgmsh.so.4.8.4', which is also in package libgmsh4:amd64 4.8.4+ds1-1 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
Processed: Re: [pkg-gnupg-maint] Bug#993578: 90gpg-agent generator: `gpgconf --check-programs` can hang
Processing control commands: > tags 993578 pending Bug #993578 [gpg-agent] 90gpg-agent generator: `gpgconf --check-programs` can hang Added tag(s) pending. -- 993578: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993578 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#993578: [pkg-gnupg-maint] Bug#993578: 90gpg-agent generator: `gpgconf --check-programs` can hang
Control: tags 993578 pending Raphael Hertzog wrote... > With the patch in https://salsa.debian.org/debian/gnupg2/-/merge_requests/9 > I no longer have this issue. Thanks for preparing this. > But I'm not sure if the patch is fully correct, the manual page is not > clear whether --check-options foo is a subset of --check-programs. However > the output format of both command is exactly the same. Okay, so I mill do a close check of all components involved. Still it seems your suggestion does more good than harm. > BTW I believe this issue needs to be fixed in bullseye too. ACK Christoph, wading through the loong backlog. signature.asc Description: PGP signature
Bug#984388: marked as done (vdr-plugin-live: ftbfs with GCC-11)
Your message dated Wed, 15 Dec 2021 22:09:05 + with message-id and subject line Bug#984388: fixed in vdr-plugin-live 3.1.3-1 has caused the Debian Bug report #984388, regarding vdr-plugin-live: ftbfs with GCC-11 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.) -- 984388: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984388 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:vdr-plugin-live Version: 2.3.1-5 Severity: normal Tags: sid bookworm User: debian-...@lists.debian.org Usertags: ftbfs-gcc-11 [This bug is not targeted to the upcoming bullseye release] Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-11/g++-11, but succeeds to build with gcc-10/g++-10. The severity of this report will be raised before the bookworm release, so nothing has to be done for the bullseye release. The full build log can be found at: http://people.debian.org/~doko/logs/20210228/filtered/gcc11/vdr-plugin-live_2.3.1-5_unstable_gcc11.log The last lines of the build log are at the end of this report. To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-11/porting_to.html GCC 11 defaults to the GNU++17 standard. If your package installs header files in /usr/include, please don't work around C++17 issues by choosing a lower C++ standard for the package build, but fix these issues to build with the C++17 standard. [...] ECPP pages/ epginfo.cpp ECPP pages/ timerconflicts.cpp ECPP pages/ recstream.cpp ECPP pages/ users.cpp ECPP pages/ edit_user.cpp ECPP pages/ edit_recording.cpp ECPP pages/ osd.cpp CC pages/ menu.o CC pages/ recordings.o CC pages/ schedule.o CC pages/ multischedule.o CC pages/ screenshot.o CC pages/ timers.o CC pages/ whats_on.o CC pages/ switch_channel.o CC pages/ keypress.o CC pages/ remote.o CC pages/ channels_widget.o CC pages/ edit_timer.o CC pages/ error.o CC pages/ pageelems.o CC pages/ tooltip.o CC pages/ vlc.o CC pages/ searchtimers.o CC pages/ edit_searchtimer.o CC pages/ searchresults.o CC pages/ searchepg.o CC pages/ login.o CC pages/ ibox.o CC pages/ xmlresponse.o CC pages/ play_recording.o CC pages/ pause_recording.o CC pages/ stop_recording.o CC pages/ ffw_recording.o CC pages/ rwd_recording.o CC pages/ setup.o CC pages/ content.o CC pages/ epginfo.o CC pages/ timerconflicts.o CC pages/ recstream.o CC pages/ users.o CC pages/ edit_user.o CC pages/ edit_recording.o CC pages/ osd.o AR pages/ libpages.a ECPP css/ styles.cpp CC css/ styles.o AR css/ libcss.a ECPP javascript/ treeview.cpp CC javascript/ treeview.o AR javascript/ libjavascript.a CC live.o CC thread.o CC tntconfig.o CC setup.o CC i18n.o CC timers.o CC tools.o CC recman.o CC tasks.o tasks.cpp: In member function ‘void vdrlive::TaskManager::DoScheduledTasks()’: tasks.cpp:248:83: error: call of overloaded ‘bind(void (vdrlive::Task::*)(), const std::_Placeholder<1>&)’ is ambiguous 248 | for_each( m_taskQueue.begin(), m_taskQueue.end(), bind( ::Action, _1 ) ); | ^ compilation terminated due to -Wfatal-errors. make[1]: *** [Makefile:116: tasks.o] Error 1 make[1]: Leaving directory '/<>' dh_auto_build: error: make -j1 returned exit code 2 make: *** [debian/rules:9: build] Error 25 dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2 --- End Message --- --- Begin Message --- Source: vdr-plugin-live Source-Version: 3.1.3-1 Done: Tobias Grimm We believe that the bug you reported is fixed in the latest version of vdr-plugin-live, 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 984...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Tobias Grimm (supplier of
Bug#999153: marked as done (jpeginfo: missing required debian/rules targets build-arch and/or build-indep)
Your message dated Wed, 15 Dec 2021 22:06:36 + with message-id and subject line Bug#999153: fixed in jpeginfo 1.6.1-1 has caused the Debian Bug report #999153, regarding jpeginfo: missing required debian/rules targets build-arch and/or build-indep to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 999153: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999153 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: jpeginfo Version: 1.6.0-6 Severity: important Justification: Debian Policy section 4.9 Tags: bookworm sid User: debian...@lists.debian.org Usertags: missing-build-arch-indep Dear maintainer, Your package does not include build-arch and/or build-indep targets in debian/rules. This is required by Debian Policy section 4.9, since 2012. https://www.debian.org/doc/debian-policy/ch-source.html#main-building-script-debian-rules Please note that this is also a sign that the packaging of this software could benefit from a refresh. For example, packages using 'dh' cannot be affected by this issue. This mass bug filing was discussed on debian-devel@ in https://lists.debian.org/debian-devel/2021/11/msg00052.html . The severity of this bug will be changed to 'serious' after a month. Best, Lucas --- End Message --- --- Begin Message --- Source: jpeginfo Source-Version: 1.6.1-1 Done: Andreas Tille We believe that the bug you reported is fixed in the latest version of jpeginfo, 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 999...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille (supplier of updated jpeginfo 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, 15 Dec 2021 22:38:17 +0100 Source: jpeginfo Architecture: source Version: 1.6.1-1 Distribution: unstable Urgency: medium Maintainer: Debian PhotoTools Maintainers Changed-By: Andreas Tille Closes: 695524 825498 901985 965606 999153 Changes: jpeginfo (1.6.1-1) unstable; urgency=medium . [ Andreas Tille ] * New upstream version Closes: #695524 * Move package to Debian PhotoTools Maintainers * d/control: Add Homepage * debian/source/format: quilt (3.0) * Add watch file * DEP5 * d/rules: short dh Closes: #999153 * debhelper-compat 13 Closes: #965606 * Standards-Version: 4.6.0 (routine-update) * Add salsa-ci file (routine-update) * Rules-Requires-Root: no (routine-update) . [ Mathieu Malaterre ] * Better long description clarifying limitations of the program Closes: #825498 . [ Helmut Grohne ] * Fix FTCBFS: Export a suitable CC for ./configure. Closes: #901985 Checksums-Sha1: 868dceee05a41e9ccd4cb1d4b024842977ac7d32 2021 jpeginfo_1.6.1-1.dsc 8fd998c3090908d1b100ed38d5d7fc2600e5742b 64856 jpeginfo_1.6.1.orig.tar.gz b9c1c0f56562a140d1e3bc796235b9ada72d736e 4076 jpeginfo_1.6.1-1.debian.tar.xz ac2a0108e1b466c38a69a229fc58c824751ef91d 6090 jpeginfo_1.6.1-1_amd64.buildinfo Checksums-Sha256: 67d2646df036581f1f88076e53fc6f21a38899495ed25116f12847ff79216d4a 2021 jpeginfo_1.6.1-1.dsc 629e31cf1da0fa1efe4a7cc54c67123a68f5024f3d8e864a30457aeaed1d7653 64856 jpeginfo_1.6.1.orig.tar.gz efb6f00ad18e7be088961859705f60578e7ddc4618ff09feb3dbd739a124c679 4076 jpeginfo_1.6.1-1.debian.tar.xz 87a571ba1894e2822a5be3c670c31ffb4881688cfabff49eff71308336e3b16a 6090 jpeginfo_1.6.1-1_amd64.buildinfo Files: c194e2ae7287e3c112d7968cd7e34e1d 2021 graphics optional jpeginfo_1.6.1-1.dsc 344be10d6b16ec559c5d8b7e3707241f 64856 graphics optional jpeginfo_1.6.1.orig.tar.gz 19c58a23b2969c3489c5df1b94b77412 4076 graphics optional jpeginfo_1.6.1-1.debian.tar.xz 26bd66b4508d7c73b0e18e202e92185f 6090 graphics optional jpeginfo_1.6.1-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmG6YRQRHHRpbGxlQGRl Ymlhbi5vcmcACgkQV4oElNHGRtFCnw/+LFHzEhbchee8D293XVpv0qnUatKwGaHh Rct6KqTtTEdq8fIhxFh0+tD+shW3NZ9t68nR75pXErTawL9NgZum18CiasyeXjEt ekb4ywpUWmiYELVgBkO2ODfDKC7ZPxxUY0zUvGz2TPhO+0q7ocG/PEsDIBwE9EyL EwZY2pTRcu0Zr6LNwq9h27HcdBnm73aGVZzD2+G2GW+5BeMYc8VuQX1OHvA+XCL0 CrX4IxSU1AsxXy1WcV7IQr79Ry3Wsoo9On9oeTFmPOxjrkkdMnwG7CsFvkxbAapD
Bug#999074: iec16022: missing required debian/rules targets build-arch and/or build-indep
I just had a look at this and so far it looks easy to convert to dh. I intend to prepare an NMU for this. Debdiff will follow. Jan: Is that ok with you? Also: Would you be interested in a co-maintainer for iec16022? I am sort of scratching my own itch here as iec16022 is a reverse dependency of glabels. Cheers, sur5r -- ceterum censeo microsoftem esse delendam. pgpRWgJjEQFT3.pgp Description: OpenPGP digital signature
Processed: bug 998294 is forwarded to https://github.com/KhronosGroup/Vulkan-ValidationLayers/issues/3607
Processing commands for cont...@bugs.debian.org: > forwarded 998294 > https://github.com/KhronosGroup/Vulkan-ValidationLayers/issues/3607 Bug #998294 [src:vulkan-validationlayers] src:vulkan-validationlayers: fails to migrate to testing for too long: FTBFS on mips*el Set Bug forwarded-to-address to 'https://github.com/KhronosGroup/Vulkan-ValidationLayers/issues/3607'. > thanks Stopping processing here. Please contact me if you need assistance. -- 998294: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998294 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1001657: Ball fails its autopkgtest - how to properly deal with sip files?
Hi Étienne, Am Wed, Dec 15, 2021 at 09:42:00PM +0100 schrieb Étienne Mollier: > > Pushed, Thanks for the nudge. (Sorry, I couldn't push yesterday > for dumb reasons.) Thanks. :-) > > The python package is probably available for the case if you want to use > > the library itself in the python code and use it programmatically. > > The upstream wiki page seems to concur: > > > > https://github.com/BALL-Project/ball/wiki/BALLPythonScripting > > This was my perception of the situation when I tried to make > use of ballview myself, to make sure the software was operating > properly without all the python3 bindings. So what do you think is the more promising strategy: Fixing python3-ball under the now better conditions or simply droping the package? > Have a nice day, :) Same to you and thanks again Andreas. -- http://fam-tille.de
Bug#953380: marked as done (rpmlint: Autopkgtest error (test failure))
Your message dated Wed, 15 Dec 2021 20:43:10 + with message-id and subject line Bug#953380: fixed in rpmlint 2.2.0+ds1-0.2 has caused the Debian Bug report #953380, regarding rpmlint: Autopkgtest error (test failure) 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.) -- 953380: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953380 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: rpmlint Version: 1.11-0.2 Severity: grave Tags: help Hi all, I am looking for help on the autopkgtest failure for new rpmlint with python3 enabled: https://ci.debian.net/packages/r/rpmlint/testing/amd64/ It could be a python2->python3 regression and someone need to look into it. -- Thanks, Boyuan Yang signature.asc Description: This is a digitally signed message part --- End Message --- --- Begin Message --- Source: rpmlint Source-Version: 2.2.0+ds1-0.2 Done: Boyuan Yang We believe that the bug you reported is fixed in the latest version of rpmlint, 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 953...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Boyuan Yang (supplier of updated rpmlint 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, 15 Dec 2021 14:25:08 -0500 Source: rpmlint Architecture: source Version: 2.2.0+ds1-0.2 Distribution: unstable Urgency: high Maintainer: RPM packaging team Changed-By: Boyuan Yang Closes: 953380 Changes: rpmlint (2.2.0+ds1-0.2) unstable; urgency=high . * Non-maintainer upload. * debian/tests/testsuite: Use correct testsuite where binary test files are not needed. (Closes: #953380) Checksums-Sha1: 3eec102cb556bfadba25d0d84eabfb1c0c6c1b24 2436 rpmlint_2.2.0+ds1-0.2.dsc 51b6d80d42c83608f48530451c3009f83b40df38 274427 rpmlint_2.2.0+ds1.orig.tar.gz 770b301ad0d2f6a212d6d1715c3f44049b2d577f 4572 rpmlint_2.2.0+ds1-0.2.debian.tar.xz 294f1c5087f21b38c28c7178f33f3a9a7b4bc529 8211 rpmlint_2.2.0+ds1-0.2_amd64.buildinfo Checksums-Sha256: 6fb345bc517a27ffe0a583fbbbe7f0357aee64e3e0d007149f8cf1863d1c5753 2436 rpmlint_2.2.0+ds1-0.2.dsc e0440e1ee745c45700d0cdc23555f7a29aa0aafd3bc66e76fda9d5de0932ebe3 274427 rpmlint_2.2.0+ds1.orig.tar.gz a172f8c2ca05fb733194140baaee4391bf386f7340198c5ab5aa722c7220e139 4572 rpmlint_2.2.0+ds1-0.2.debian.tar.xz d8aff2e59c6d881ecc2b20c0e7d4c8fd922dcdf666eedbccfb7fc20742c9e79c 8211 rpmlint_2.2.0+ds1-0.2_amd64.buildinfo Files: f435e9226498f92b22f57aca6b3308a1 2436 admin optional rpmlint_2.2.0+ds1-0.2.dsc 49752ee6552f64d52b2bd4c461dc1c86 274427 admin optional rpmlint_2.2.0+ds1.orig.tar.gz 0d7668c6bbacedd04281bc22496deb21 4572 admin optional rpmlint_2.2.0+ds1-0.2.debian.tar.xz 03d75495b7ec3e4d207c7129baba8c54 8211 admin optional rpmlint_2.2.0+ds1-0.2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAmG6RM0ACgkQwpPntGGC Ws6xjw/9FqNjrGWfplAvat0GeQ8q4BnhovSzbYwncLb0SjvAYQayKEE9Z55QoKRm nwsbj8iUhBuSMuzGsy3QU75nYTjRz7RFCVDPUWAfCAOzhpAcaHIttCYly2/0gyGG zNtDjBswLEgGA+kFeMdv+cJLWHlb/waHc5nvbNo7WEHUObDy55VQyJmdqhtWm63e CEd4aDhHnaPtWo6fufqr/f/AyqERDcHEoLmYtKnuODP3Qzrjp9C5YQ5WyCcQp54/ NHwmrFyEjN4T1hDdrB0smG7LmrPOnnopQdiKBipr7wh0CFJlT5e+lcS8El6IGnad 2ZrVpAZIeTypaOunHkrZZ236YsXTwEfiLMyW1OBxvWUwOdHuBBX7n10m+Oi2L1k9 z1yz+8H5OaWKTfeca4VORrtSD8zllAypSIl7gmwW6B8J5TDdSmzzcI2DEIWvTlpn gHcuOaYFd/gcC0QiFuepFG1NPf/XqHXTPVsf6MGX1dQnLHHlwuFe8/oRE+qjpXLl VvTaMBNCyt+FJ7Eb9g13hhUJ7ORTJ52bhX5i02dFAZA2N2elukmz21EiJGPspif0 L9mrbc3yH/BTl8ghZv/Wkk2Wjb4Qql/U768+pAfdVT+bvjzw8Ga7S3BEtUKe6hFD IonLqIp4Xcx8CxR9Th3re42JE0UMtXIudp2o9yatQ/YPKK4dP20= =0G3Y -END PGP SIGNATURE End Message ---
Processed: Re: silx: autopkgtests failures
Processing commands for cont...@bugs.debian.org: > block 1001665 by 1001545 Bug #1001665 [src:silx] silx: autopkgtests failures 1001665 was not blocked by any bugs. 1001665 was not blocking any bugs. Added blocking bug(s) of 1001665: 1001545 > thanks Stopping processing here. Please contact me if you need assistance. -- 1001665: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001665 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1001545: silx: autopkgtests failures
block 1001665 by 1001545 thanks Hi all, On Mon, 13 Dec 2021 22:42:13 +0100 Sebastian Ramacher wrote: The autopkgtests of silx fail with: | [7 8 9]] | Abscissa Ordinate1 ['%d', '%.2f'] 2 [1 2 3] [4 5 6] | Abscissa Ordinate2 ['%d', '%.2f'] 2 [1 2 3] [7 8 9] | Abscissa Ordinate1 ['%d', '%.2f'] 2 [1 2 3] [4 5 6] | x y ['%d', '%.2f'] 2 [1] [1.1] | x y ['%d', '%.2f'] 2 [1] [1.1] | ./usr/lib/python3/dist-packages/silx/math/fit/test/test_fit.py:54: RuntimeWarning: invalid value encountered in multiply | return numpy.exp(x*numpy.less(abs(x), 250)) - \ | sss...WARNING:silx.opencl.common:Last chance to get an OpenCL device ... probably not the one requested | Segmentation fault See https://ci.debian.net/data/autopkgtest/testing/arm64/s/silx/17544040/log.gz The failure seems to be independet of the packages that trigger the autopkgtest run. The test doesn't seem to be really flaky, it just always fails with unstable added to the suite set that apt can use to install packages from. It turns out that python3-silx depends on python3-pyopencl and the later has an alternative Depends on pocl-opencl-icd. pocl-opencl-icd is no longer in testing as it has an RC bug. It seems that the segfault is only occurring with the binaries from pocl. Unfortunately for silx, python3-pyopencl currently has an RC bug (in CC) related to the same issue, but then in the Build-Depends. I assume when that bug is fixed (assuming it can be), the binary package will also drop the Depends and the issue for silx is fixed. In the mean time, if silx can work around the python3-pyopencl dependency it could consider doing so. Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#1001766: oomd: ships both ./lib/systemd/system/oomd.service & ./usr/lib/systemd/system/oomd.service
Further information from IRC: The issue was not part of the 0.5.0-1 package from snapshot, but only appeared in the rebuild 0.5.0-1+b1. In building 0.5.0-1 in a clean sid chroot (with usrmerge), I get the same issue of the service file being put in both /lib and /usr/lib. It seems to me the bug could be in the debian build chain. jaimos
Processed: libexpect-perl: diff for NMU version 1.21-1.2
Processing control commands: > tags 999021 + patch Bug #999021 [src:libexpect-perl] libexpect-perl: missing required debian/rules targets build-arch and/or build-indep Added tag(s) patch. > tags 999021 + pending Bug #999021 [src:libexpect-perl] libexpect-perl: missing required debian/rules targets build-arch and/or build-indep Added tag(s) pending. -- 999021: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999021 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#999021: libexpect-perl: diff for NMU version 1.21-1.2
Control: tags 999021 + patch Control: tags 999021 + pending Dear maintainer, I've prepared an NMU for libexpect-perl (versioned as 1.21-1.2) and uploaded it to DELAYED/7. Please feel free to tell me if I should delay it longer. Regards, dam diff -u libexpect-perl-1.21/debian/changelog libexpect-perl-1.21/debian/changelog --- libexpect-perl-1.21/debian/changelog +++ libexpect-perl-1.21/debian/changelog @@ -1,3 +1,11 @@ +libexpect-perl (1.21-1.2) unstable; urgency=medium + + * Non-maintainer upload + * Provide 'build-arch' and 'build-indep' targets in debian/rules +Closes: #999021 + + -- Damyan Ivanov Wed, 15 Dec 2021 19:58:42 + + libexpect-perl (1.21-1.1) unstable; urgency=medium * Non maintainer upload by the Reproducible Builds team. diff -u libexpect-perl-1.21/debian/rules libexpect-perl-1.21/debian/rules --- libexpect-perl-1.21/debian/rules +++ libexpect-perl-1.21/debian/rules @@ -7,21 +7,26 @@ TMP =`pwd`/debian/$(PACKAGE) -build: build-stamp -build-stamp: +build: build-arch build-indep + +build-indep: build-indep-stamp +build-indep-stamp: dh_testdir perl Makefile.PL INSTALLDIRS=vendor $(MAKE) OPTIMIZE="-O2 -g -Wall" - touch build-stamp + touch $@ + +build-arch: + # nothing to do here realclean: clean clean: dh_testdir dh_testroot - rm -f build-stamp + rm -f build-indep-stamp [ ! -f Makefile ] || $(MAKE) distclean @@ -60,4 +65,4 @@ dh_builddeb binary: binary-indep binary-arch -.PHONY: build clean binary-indep binary-arch binary install +.PHONY: build build-arch build-indep clean binary-indep binary-arch binary install
Bug#995212: ungoogled-chromium? [was: Re: Bug#995212: chromium: Update to version 94.0.4606.61 (security-fixes)]
Hi Jeff, On Tue, 14 Dec 2021 09:13:42 +, Jeff Blake wrote: [...] > Inspector and convertutf are the worst offenders in terms of being > unnecessary and complex. The disable/catapult.patch could also be dropped, > since profiling might be desirable to some users. convertutf at least is required for licensing reasons — it replaces code which is stripped from the upstream tarball because it’s not DFSG-free. See https://lintian.debian.org/tags/license-problem-convert-utf-code for details. Regards, Stephen pgpjqbqVKwhVK.pgp Description: OpenPGP digital signature
Bug#999320: marked as done (libwww-indexparser-perl: missing required debian/rules targets build-arch and/or build-indep)
Your message dated Wed, 15 Dec 2021 19:18:34 + with message-id and subject line Bug#999320: fixed in libwww-indexparser-perl 0.91-2 has caused the Debian Bug report #999320, regarding libwww-indexparser-perl: missing required debian/rules targets build-arch and/or build-indep to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 999320: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999320 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libwww-indexparser-perl Version: 0.91-1.1 Severity: important Justification: Debian Policy section 4.9 Tags: bookworm sid User: debian...@lists.debian.org Usertags: missing-build-arch-indep Dear maintainer, Your package does not include build-arch and/or build-indep targets in debian/rules. This is required by Debian Policy section 4.9, since 2012. https://www.debian.org/doc/debian-policy/ch-source.html#main-building-script-debian-rules Please note that this is also a sign that the packaging of this software could benefit from a refresh. For example, packages using 'dh' cannot be affected by this issue. This mass bug filing was discussed on debian-devel@ in https://lists.debian.org/debian-devel/2021/11/msg00052.html . The severity of this bug will be changed to 'serious' after a month. Best, Lucas --- End Message --- --- Begin Message --- Source: libwww-indexparser-perl Source-Version: 0.91-2 Done: Christoph Biedl We believe that the bug you reported is fixed in the latest version of libwww-indexparser-perl, 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 999...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Christoph Biedl (supplier of updated libwww-indexparser-perl 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, 15 Dec 2021 23:07:40 +0100 Source: libwww-indexparser-perl Architecture: source Version: 0.91-2 Distribution: unstable Urgency: medium Maintainer: Christoph Biedl Changed-By: Christoph Biedl Closes: 999320 Changes: libwww-indexparser-perl (0.91-2) unstable; urgency=medium . * Take over maintainership. Thanks James Bromberger for all the past work on WWW::IndexParser * Modernize packaging. Closes: #999320 Checksums-Sha1: 58df34a9dc699c95becd6ae54cdc390c03a5f2a9 1948 libwww-indexparser-perl_0.91-2.dsc 1847587e36b64734662f826c10c468ca354c0a13 2444 libwww-indexparser-perl_0.91-2.debian.tar.xz 1f80ecb6350d18ef7c61bccaef56360521cb4924 7733 libwww-indexparser-perl_0.91-2_powerpc.buildinfo Checksums-Sha256: 900c92a7cecafc41c7125fe333a2f078abb099e43b577b998b72a89c1b537504 1948 libwww-indexparser-perl_0.91-2.dsc 2fcd5ed3749c63fa8b21d1d4db63d462f36923b22a048fde8e3d1ed7044fc974 2444 libwww-indexparser-perl_0.91-2.debian.tar.xz ea16407a97990b2f793d13979fcb490e70bf147a3d2152c9a14b39dccddc4d73 7733 libwww-indexparser-perl_0.91-2_powerpc.buildinfo Files: 74bb381a69c9dab190ed7c212e7ef462 1948 perl optional libwww-indexparser-perl_0.91-2.dsc c52fb61f4f6e2b47649d948f7d9e51d1 2444 perl optional libwww-indexparser-perl_0.91-2.debian.tar.xz 5838136f565248b1d0b7bea9cb17be57 7733 perl optional libwww-indexparser-perl_0.91-2_powerpc.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEWXMI+726A12MfJXdxCxY61kUkv0FAmG6OwwACgkQxCxY61kU kv3WWg//cw1+7YaAqkka4fKt27zcHqrTGvKB00d+jotE4ZrK+wYMImBZ5xwZkgQn INcjWmif8h4VWJW2+u2p9SqYLedcOwyABpWRi+xZ7gnxtkSyUjzABQDv9CcIuB22 CBhzfXkUqTEFUpg4qFMjQBFWA4NGM4FgrULrc72v/13r/jSPMwByPJ5Z4ApOAwqP 9GmcxIpW9T5HC4xeuRWMzUmP4oKwjmPV0KZO9Nd4cjlD7eMtGaFwQ0+rToj8AfTX 4H8GzOVWMi3LSyPN5piSSWViXqtKxqDC3mVgrS5zyn4SzIVUqftwvdhdvDBFzy1s X0EFibpDUr209GlQvPN1eHZK1yQ48dKpmLyPb4Mfj/1ENBnx57zJUjLpWundeCxb 9faMHvY3PUgrMXRly5TXfTeGmr4cRh7Up9HpzgBPHbLPQM4kHiW7NOABmVof8L4E 5hkwypiXRK8qqN+JTl3hd9Fc6SzdGo01dNKWzUyuu1wth3mElM/FLVwmzIaDsuZM 0fdAVvifC0o/7x+OR9S+0pXcg+TCPWwH3ABYtobK1LtB9UBkKuSG+ZTFEuHNn0AH i1HJNOYsBiC4kHFUGghA0sRsbr+kAwVCtuNbBlp135t1u3+v0Omd/Ygk8Y4/iGVe 3IgsYUAz6lIKTgZAzYCXuVMLH2CP8Rf3W2Dl3p6TK4zJLIHoK0M= =E2R1 -END PGP SIGNATURE End Message ---
Bug#997845: Your mail
i can happily report that the FTPmasters accepted notcurses 3.0.0 into experimental today, and thus the transition bringing it into unstable ought begin. once that hits, i'll be landing on this with both feet. signature.asc Description: PGP signature
Bug#1001766: oomd: ships both ./lib/systemd/system/oomd.service & ./usr/lib/systemd/system/oomd.service
Package: oomd Version: 0.5.0-1+b1 Severity: grave oomd ships the same file with different content under / and /usr: +--- | dpkg-deb -c oomd_0.5.0-1+b1_amd64.deb|grep service | -rw-r--r-- root/root 369 2021-08-31 16:24 ./lib/systemd/system/oomd.service | -rw-r--r-- root/root 241 2021-12-11 20:27 ./usr/lib/systemd/system/oomd.service +--- This violates the following requirement from Debian Policy: +--- | To support merged-/usr systems, packages must not install files in | both /path and /usr/path. For example, a package must not install | both /bin/example and /usr/bin/example. +---[ Debian Policy, Section 10.1. Binaries ] And someone reported on IRC (#debian-next) to encounter this issue. Ansgar
Bug#1001765: src:rust-futures: fails to migrate to testing for too long: makes reverse dependencies uninstallable in testing
Source: rust-futures Version: 0.1.29-3 Severity: serious Control: close -1 0.3.17-2 Tags: sid bookworm User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing [1]. Your package src:rust-futures has been trying to migrate for 61 days [2]. Hence, I am filing this bug. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. I know we expect this for some time in the rust ecosystem, but 60 days ought to be enough for that. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bookworm, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=rust-futures OpenPGP_signature Description: OpenPGP digital signature
Processed: src:rust-futures: fails to migrate to testing for too long: makes reverse dependencies uninstallable in testing
Processing control commands: > close -1 0.3.17-2 Bug #1001765 [src:rust-futures] src:rust-futures: fails to migrate to testing for too long: makes reverse dependencies uninstallable in testing Marked as fixed in versions rust-futures/0.3.17-2. Bug #1001765 [src:rust-futures] src:rust-futures: fails to migrate to testing for too long: makes reverse dependencies uninstallable in testing Marked Bug as done -- 1001765: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001765 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#984232: marked as done (meshlab: ftbfs with GCC-11)
Your message dated Wed, 15 Dec 2021 19:03:27 + with message-id and subject line Bug#984232: fixed in meshlab 2020.09+dfsg1-2 has caused the Debian Bug report #984232, regarding meshlab: ftbfs with GCC-11 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.) -- 984232: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984232 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:meshlab Version: 2020.09+dfsg1-1 Severity: normal Tags: sid bookworm User: debian-...@lists.debian.org Usertags: ftbfs-gcc-11 [This bug is not targeted to the upcoming bullseye release] Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-11/g++-11, but succeeds to build with gcc-10/g++-10. The severity of this report will be raised before the bookworm release, so nothing has to be done for the bullseye release. The full build log can be found at: http://people.debian.org/~doko/logs/20210228/filtered/gcc11/meshlab_2020.09+dfsg1-1_unstable_gcc11.log The last lines of the build log are at the end of this report. To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-11/porting_to.html GCC 11 defaults to the GNU++17 standard. If your package installs header files in /usr/include, please don't work around C++17 issues by choosing a lower C++ standard for the package build, but fix these issues to build with the C++17 standard. [...] 27 | i->setBackgroundColor(QColor(255,2,0)); | ^ In file included from /usr/include/x86_64-linux-gnu/qt5/QtWidgets/QListWidget:1, from /<>/src/external/structuresynth-1.5/ssynth/SyntopiaCore/Logging/ListWidgetLogger.h:5, from /<>/src/external/structuresynth-1.5/ssynth/SyntopiaCore/Logging/ListWidgetLogger.cpp:1: /usr/include/x86_64-linux-gnu/qt5/QtWidgets/qlistwidget.h:124:18: note: declared here 124 | virtual void setBackgroundColor(const QColor ) | ^~ /<>/src/external/structuresynth-1.5/ssynth/SyntopiaCore/Logging/ListWidgetLogger.cpp:30:71: warning: ‘virtual void QListWidgetItem::setBackgroundColor(const QColor&)’ is deprecated: Use QListWidgetItem::setBackground() instead [-Wdeprecated-declarations] 30 | i->setBackgroundColor(QColor(25,255,0)); | ^ In file included from /usr/include/x86_64-linux-gnu/qt5/QtWidgets/QListWidget:1, from /<>/src/external/structuresynth-1.5/ssynth/SyntopiaCore/Logging/ListWidgetLogger.h:5, from /<>/src/external/structuresynth-1.5/ssynth/SyntopiaCore/Logging/ListWidgetLogger.cpp:1: /usr/include/x86_64-linux-gnu/qt5/QtWidgets/qlistwidget.h:124:18: note: declared here 124 | virtual void setBackgroundColor(const QColor ) | ^~ /<>/src/external/structuresynth-1.5/ssynth/SyntopiaCore/Logging/ListWidgetLogger.cpp:32:74: warning: ‘virtual void QListWidgetItem::setBackgroundColor(const QColor&)’ is deprecated: Use QListWidgetItem::setBackground() instead [-Wdeprecated-declarations] 32 | i->setBackgroundColor(QColor(220,220,220)); | ^ In file included from /usr/include/x86_64-linux-gnu/qt5/QtWidgets/QListWidget:1, from /<>/src/external/structuresynth-1.5/ssynth/SyntopiaCore/Logging/ListWidgetLogger.h:5, from /<>/src/external/structuresynth-1.5/ssynth/SyntopiaCore/Logging/ListWidgetLogger.cpp:1: /usr/include/x86_64-linux-gnu/qt5/QtWidgets/qlistwidget.h:124:18: note: declared here 124 | virtual void setBackgroundColor(const QColor ) | ^~ [ 16%] Building CXX object
Bug#995769: marked as done (dbab: v1.5.7 package fail to upgrade from bullseye (1.5.01-1))
Your message dated Wed, 15 Dec 2021 19:00:09 + with message-id and subject line Bug#995769: fixed in dbab 1.5.7-2 has caused the Debian Bug report #995769, regarding dbab: v1.5.7 package fail to upgrade from bullseye (1.5.01-1) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 995769: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995769 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: dbab Version: 1.5.7-1 Severity: grave X-Debbugs-CC: suntong...@users.sourceforge.net Dear Debian dbab maintainer, Package dbab/1.5.7-1 has broken maintscript and cannot be properly upgraded from dbab/1.5.01-1 to dbab/1.5.7-1: % sudo apt dist-upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done The following packages will be upgraded: dbab 1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/20.3 kB of archives. After this operation, 6144 B disk space will be freed. Do you want to continue? [Y/n] y Retrieving bug reports... Done Parsing Found/Fixed information... Done Reading changelogs... Done (Reading database ... 377073 files and directories currently installed.) Preparing to unpack .../archives/dbab_1.5.7-1_all.deb ... md5sum: /etc/dbab: Is a directory Unpacking dbab (1.5.7-1) over (1.5.01-1) ... Setting up dbab (1.5.7-1) ... grep: /etc/dbab/dbab.list-: No such file or directory cat: /etc/dbab/dbab.addr: No such file or directory curl 'https://pgl.yoyo.org/adservers/serverlist.php?hostformat=dnsmasq =0=plaintext' -o /tmp/dbab-map.adblock.conf % Total% Received % Xferd Average Speed TimeTime Time Current Dload Upload Total SpentLeft Speed 100 127k0 127k0 0 204k 0 --:--:-- --:--:-- --:--:-- 204k grep: /etc/dbab/dbab.list-: No such file or directory File /etc/dnsmasq.d/dbab-map.adblock.conf updated. cat: /etc/dbab/dbab.addr: No such file or directory sed: can't read /etc/dbab/dbab.list+: No such file or directory File /etc/dnsmasq.d/dbab-map.trashsites.conf updated. Removing obsolete conffile /etc/dbab ... rm: cannot remove '/etc/dbab.dpkg-remove': Is a directory dpkg: error processing package dbab (--configure): installed dbab package post-installation script subprocess returned error exit status 1 Processing triggers for man-db (2.9.4-2) ... Errors were encountered while processing: dbab E: Sub-process /usr/bin/dpkg returned an error code (1) Thanks, Boyuan Yang signature.asc Description: This is a digitally signed message part --- End Message --- --- Begin Message --- Source: dbab Source-Version: 1.5.7-2 Done: Tong Sun We believe that the bug you reported is fixed in the latest version of dbab, 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 995...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Tong Sun (supplier of updated dbab package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 11 Dec 2021 19:14:48 + Source: dbab Binary: dbab Architecture: source all Version: 1.5.7-2 Distribution: unstable Urgency: medium Maintainer: Tong Sun Changed-By: Tong Sun Description: dbab - dnsmasq-based ad-blocking using pixelserv Closes: 995769 1001009 Changes: dbab (1.5.7-2) unstable; urgency=medium . * properly remove auto-generated files instead * add ca-certificates to depend list; moved to contrib; closes: #1001009 * delete debian/dbab.maintscript; closes: #995769 * fix: missing-explanation-for-contrib-or-non-free-package * fix: out-of-date-standards-version * try to take care of the case of upgrading from buster * explain reasons for moving to contrib in d/README.Debian Checksums-Sha1: 48354bad1aef5dfe1e997a684b3e2a962dc69d11 1898 dbab_1.5.7-2.dsc cde3a3c454b7bcfd8afa2097022edae71c2ae4f0 14252 dbab_1.5.7.orig.tar.gz b38a47f1d1c10cd44763025fa8a634066785da8d 6396 dbab_1.5.7-2.debian.tar.xz 8c9c24145a759d14314763e7d8365cfa0241f697 21192 dbab_1.5.7-2_all.deb e263edd13f211a30f66885f50ee7a5012487ec75 6795 dbab_1.5.7-2_amd64.buildinfo Checksums-Sha256:
Bug#995424: marked as done (libgmsh4: SONAME bump without package rename)
Your message dated Wed, 15 Dec 2021 19:00:11 + with message-id and subject line Bug#995424: fixed in gmsh 4.8.4+ds2-1 has caused the Debian Bug report #995424, regarding libgmsh4: SONAME bump without package rename 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.) -- 995424: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995424 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libgmsh4 Version: 4.8.4+ds1-1 Severity: serious X-Debbugs-Cc: sramac...@debian.org, elb...@debian.org The package name of shared libraries is supposed to follow the SONAME of the library. In the case of libgmsh, the SONAME in testing is libgmsh.so.4.7 and the package should have been named libgmsh4.7. But now, the SONAME changed to libgmsh.so.4.8 and the package name should have been changed accorindgly. This broke every user outside of the gmsh source package of libgmsh4. See for example https://ci.debian.net/data/autopkgtest/testing/amd64/d/deal.ii/15628998/log.gz Cheers -- Sebastian Ramacher signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: gmsh Source-Version: 4.8.4+ds2-1 Done: Anton Gladky We believe that the bug you reported is fixed in the latest version of gmsh, 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 995...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Anton Gladky (supplier of updated gmsh 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, 07 Nov 2021 20:54:27 +0100 Source: gmsh Binary: gmsh gmsh-dbgsym gmsh-doc libgmsh-dev libgmsh-private-headers-dev libgmsh4.8 libgmsh4.8-dbgsym python3-gmsh Architecture: source amd64 all Version: 4.8.4+ds2-1 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Anton Gladky Description: gmsh - Three-dimensional finite element mesh generator gmsh-doc - Three-dimensional finite element mesh generator documentation libgmsh-dev - Three-dimensional finite element mesh generator development files libgmsh-private-headers-dev - Three-dimensional finite element mesh generator development files libgmsh4.8 - Three-dimensional finite element mesh generator shared library python3-gmsh - Three-dimensional finite element mesh generator Python 3 wrapper Closes: 948773 995424 Changes: gmsh (4.8.4+ds2-1) unstable; urgency=medium . * [67d9673] Update d/copyright. (Thanks, Thorsten!) * [6a27104] New upstream version 4.8.4+ds2 * [fc0b62a] Rename libmgsh4 to libgmsh4.8. (Closes: #995424) * [f1f4bc0] Provide private api headers. (Closes: #948773) * [9befa85] Set Standards-Version to 4.6.0 Checksums-Sha1: 025044e53b6d75832ee0b2364856fd2a3a8d6ada 2860 gmsh_4.8.4+ds2-1.dsc aff462326ecf22d5d6e65c767d3ebb3666791290 15583004 gmsh_4.8.4+ds2.orig.tar.xz c0fd09ff51a3101031db5e6732a4a2d5078f9240 24280 gmsh_4.8.4+ds2-1.debian.tar.xz 070b94ca1e1915780114bfac720d88015b0679e0 8804 gmsh-dbgsym_4.8.4+ds2-1_amd64.deb fb35f371ba03a8f898624491e66fbb7a2923ad07 4458080 gmsh-doc_4.8.4+ds2-1_all.deb 86be714425fbe5a0e4c6b8813992a67955f56338 16289 gmsh_4.8.4+ds2-1_amd64.buildinfo e13cde2fd1d52ed370ec0283390a78c181b9782b 46888 gmsh_4.8.4+ds2-1_amd64.deb 6934a46468da82e252107514a319f187d6c4d9cc 72444 libgmsh-dev_4.8.4+ds2-1_amd64.deb fe04997c2c5d6fa065d3e52d8ddf430868e0d7a4 326252 libgmsh-private-headers-dev_4.8.4+ds2-1_amd64.deb c2b4936aa84d0f857a11ae12c49cec9168c7a62e 108837020 libgmsh4.8-dbgsym_4.8.4+ds2-1_amd64.deb 15012c28127074d1529feaef08954ace2ac5f66f 4968084 libgmsh4.8_4.8.4+ds2-1_amd64.deb 44b477df50e2de17b514159ea4de40ea10489030 70068 python3-gmsh_4.8.4+ds2-1_all.deb Checksums-Sha256: 304a1cc03c9487a997458a9c6a0fde075cc6f6b32ecfd8c9d612b33de7faaf6f 2860 gmsh_4.8.4+ds2-1.dsc cd2689205ee2c77e862a5742b08139e7d2efd0843f405c8930ef1f7a1b35078b 15583004 gmsh_4.8.4+ds2.orig.tar.xz 827ca80ff04b57b1386ecc9935f21fcfab5930d3550a3a30ce7749456f4372e1 24280 gmsh_4.8.4+ds2-1.debian.tar.xz f26ec526705dcd528b2caeb4e888455f9f4cc03ff2d6943c55f980d0409060ac 8804 gmsh-dbgsym_4.8.4+ds2-1_amd64.deb 9ce51d8c5408065c2ce554b6632c7d00b2adfd8abe79a01860b334baae040192 4458080
Bug#984396: marked as done (vdr-plugin-xine: ftbfs with GCC-11)
Your message dated Wed, 15 Dec 2021 19:00:25 + with message-id and subject line Bug#984393: fixed in vdr-plugin-xineliboutput 2.2.0+git20211212-1 has caused the Debian Bug report #984393, regarding vdr-plugin-xine: ftbfs with GCC-11 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.) -- 984393: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984393 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:vdr-plugin-xine Version: 0.9.4-17 Severity: normal Tags: sid bookworm User: debian-...@lists.debian.org Usertags: ftbfs-gcc-11 [This bug is not targeted to the upcoming bullseye release] Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-11/g++-11, but succeeds to build with gcc-10/g++-10. The severity of this report will be raised before the bookworm release, so nothing has to be done for the bullseye release. The full build log can be found at: http://people.debian.org/~doko/logs/20210228/filtered/gcc11/vdr-plugin-xine_0.9.4-17_unstable_gcc11.log The last lines of the build log are at the end of this report. To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-11/porting_to.html GCC 11 defaults to the GNU++17 standard. If your package installs header files in /usr/include, please don't work around C++17 issues by choosing a lower C++ standard for the package build, but fix these issues to build with the C++17 standard. [...] g++ -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -g -O2 -fdebug-prefix-map=/build/vdr-J3eFss/vdr-2.4.1=. -fstack-protector-strong -Wformat -Werror=format-security -fPIC -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -c -D_GNU_SOURCE -DPLUGIN_NAME_I18N='"xine"' -DFIFO_DIR=\"/tmp/vdr-xine\" -DVERIFY_BITMAP_DIRTY=0 -DSET_VIDEO_WINDOW `pkg-config --cflags libxine` -I/usr/include/vdr/include vdr172h264parser.c xgettext -C -cTRANSLATORS --no-wrap --no-location -k -ktr -ktrNOOP --package-name=vdr-xine --package-version=0.9.4 --msgid-bugs-address='Reinhard Nissl ' -o po/xine.pot vdr172h264parser.c vdr172remux.c xine.c xineDevice.c xineExternal.c xineLib.c xineOsd.c xineRemote.c xineSettings.c xineSetupPage.c xineplayer.c g++ -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -g -O2 -fdebug-prefix-map=/build/vdr-J3eFss/vdr-2.4.1=. -fstack-protector-strong -Wformat -Werror=format-security -fPIC -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -c -D_GNU_SOURCE -DPLUGIN_NAME_I18N='"xine"' -DFIFO_DIR=\"/tmp/vdr-xine\" -DVERIFY_BITMAP_DIRTY=0 -DSET_VIDEO_WINDOW `pkg-config --cflags libxine` -I/usr/include/vdr/include xineplayer.c vdr172remux.c: In member function ‘void vdr172::cTsToPes::PutTs(const uchar*, int)’: vdr172remux.c:3370:13: error: ‘max’ was not declared in this scope; did you mean ‘std::max’? 3370 | size = max(KILOBYTE(2), length + Length); | ^~~ | std::max In file included from /usr/include/c++/11/bits/specfun.h:45, from /usr/include/c++/11/cmath:1927, from /usr/include/c++/11/math.h:36, from /usr/include/vdr/tools.h:18, from /usr/include/vdr/i18n.h:14, from /usr/include/vdr/config.h:19, from vdr172remux.c:2: /usr/include/c++/11/bits/stl_algobase.h:300:5: note: ‘std::max’ declared here 300 | max(const _Tp& __a, const _Tp& __b, _Compare __comp) | ^~~ vdr172remux.c: In member function ‘const uchar* vdr172::cTsToPes::GetPes(int&)’: vdr172remux.c:3390:17: error: ‘min’ was not declared in this scope; did you mean ‘std::min’? 3390 | int l = min(length - offset, MAXPESLENGTH); | ^~~ | std::min In file included from /usr/include/c++/11/bits/specfun.h:45, from /usr/include/c++/11/cmath:1927, from
Bug#984395: marked as done (vdr-plugin-vcd: ftbfs with GCC-11)
Your message dated Wed, 15 Dec 2021 19:00:25 + with message-id and subject line Bug#984393: fixed in vdr-plugin-xineliboutput 2.2.0+git20211212-1 has caused the Debian Bug report #984393, regarding vdr-plugin-vcd: ftbfs with GCC-11 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.) -- 984393: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984393 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:vdr-plugin-vcd Version: 0.9-28 Severity: normal Tags: sid bookworm User: debian-...@lists.debian.org Usertags: ftbfs-gcc-11 [This bug is not targeted to the upcoming bullseye release] Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-11/g++-11, but succeeds to build with gcc-10/g++-10. The severity of this report will be raised before the bookworm release, so nothing has to be done for the bullseye release. The full build log can be found at: http://people.debian.org/~doko/logs/20210228/filtered/gcc11/vdr-plugin-vcd_0.9-28_unstable_gcc11.log The last lines of the build log are at the end of this report. To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-11/porting_to.html GCC 11 defaults to the GNU++17 standard. If your package installs header files in /usr/include, please don't work around C++17 issues by choosing a lower C++ standard for the package build, but fix these issues to build with the C++17 standard. [...] dh clean --with vdrplugin dh: warning: Compatibility levels before 10 are deprecated (level 9 in use) debian/rules override_dh_auto_clean make[1]: Entering directory '/<>' /usr/bin/make -o .dependencies clean VDRDIR=/usr/include/vdr LIBDIR=. LOCALEDIR=locale make[2]: Entering directory '/<>' make[2]: Leaving directory '/<>' rm -rf locale libvdr-*.so.* make[1]: Leaving directory '/<>' dh_clean dh_clean: warning: Compatibility levels before 10 are deprecated (level 9 in use) debian/rules build dh build --with vdrplugin dh: warning: Compatibility levels before 10 are deprecated (level 9 in use) dh_update_autotools_config dh_auto_configure dh_auto_configure: warning: Compatibility levels before 10 are deprecated (level 9 in use) debian/rules override_dh_auto_build make[1]: Entering directory '/<>' dh_auto_build -- all VDRDIR=/usr/include/vdr LIBDIR=. LOCALEDIR=locale dh_auto_build: warning: Compatibility levels before 10 are deprecated (level 9 in use) make -j1 all VDRDIR=/usr/include/vdr LIBDIR=. LOCALEDIR=locale make[2]: Entering directory '/<>' g++ -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -fPIC -Wl,-z,relro -Wdate-time -D_FORTIFY_SOURCE=2 -c -DPLUGIN_NAME_I18N='"vcd"' -D_GNU_SOURCE -I/usr/include/vdr/include vcd.c vcd.c: In member function ‘virtual cOsdMenu* cPluginVcd::MainMenuAction()’: vcd.c:139:20: error: ‘max’ was not declared in this scope; did you mean ‘std::max’? 139 | psd_size = max((int)U32_TO_LE(vcd->vcdInfo.psd_size), PSD_VCD_MAX_SIZE*CD_XA21_DATASIZE); |^~~ |std::max In file included from /usr/include/c++/11/bits/specfun.h:45, from /usr/include/c++/11/cmath:1927, from /usr/include/c++/11/math.h:36, from /usr/include/vdr/tools.h:18, from /usr/include/vdr/i18n.h:14, from /usr/include/vdr/config.h:19, from /usr/include/vdr/interface.h:13, from vcd.c:25: /usr/include/c++/11/bits/stl_algobase.h:300:5: note: ‘std::max’ declared here 300 | max(const _Tp& __a, const _Tp& __b, _Compare __comp) | ^~~ vcd.c:143:20: error: ‘max’ was not declared in this scope; did you mean ‘std::max’? 143 | psd_size = max((int)U32_TO_LE(vcd->vcdInfo.psd_size), PSD_VCD_MAX_SIZE*CD_XA21_DATASIZE); |^~~ |std::max In file included from /usr/include/c++/11/bits/specfun.h:45,
Bug#984392: marked as done (vdr-plugin-streamdev: ftbfs with GCC-11)
Your message dated Wed, 15 Dec 2021 19:00:25 + with message-id and subject line Bug#984393: fixed in vdr-plugin-xineliboutput 2.2.0+git20211212-1 has caused the Debian Bug report #984393, regarding vdr-plugin-streamdev: ftbfs with GCC-11 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.) -- 984393: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984393 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:vdr-plugin-streamdev Version: 0.6.1+git20180514-3 Severity: normal Tags: sid bookworm User: debian-...@lists.debian.org Usertags: ftbfs-gcc-11 [This bug is not targeted to the upcoming bullseye release] Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-11/g++-11, but succeeds to build with gcc-10/g++-10. The severity of this report will be raised before the bookworm release, so nothing has to be done for the bullseye release. The full build log can be found at: http://people.debian.org/~doko/logs/20210228/filtered/gcc11/vdr-plugin-streamdev_0.6.1+git20180514-3_unstable_gcc11.log The last lines of the build log are at the end of this report. To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-11/porting_to.html GCC 11 defaults to the GNU++17 standard. If your package installs header files in /usr/include, please don't work around C++17 issues by choosing a lower C++ standard for the package build, but fix these issues to build with the C++17 standard. [...] msgfmt -c -o po/fr_FR.mo po/fr_FR.po msgmerge -U --no-wrap --no-location --backup=none -q -N po/it_IT.po po/streamdev-client.pot msgfmt -c -o po/it_IT.mo po/it_IT.po msgmerge -U --no-wrap --no-location --backup=none -q -N po/lt_LT.po po/streamdev-client.pot msgfmt -c -o po/lt_LT.mo po/lt_LT.po msgmerge -U --no-wrap --no-location --backup=none -q -N po/pl_PL.po po/streamdev-client.pot msgfmt -c -o po/pl_PL.mo po/pl_PL.po msgmerge -U --no-wrap --no-location --backup=none -q -N po/ru_RU.po po/streamdev-client.pot msgfmt -c -o po/ru_RU.mo po/ru_RU.po msgmerge -U --no-wrap --no-location --backup=none -q -N po/sk_SK.po po/streamdev-client.pot msgfmt -c -o po/sk_SK.mo po/sk_SK.po make[2]: Leaving directory '/<>/client' make -C ./tools make[2]: Entering directory '/<>/tools' make[2]: 'sockettools.a' is up to date. make[2]: Leaving directory '/<>/tools' make -C ./libdvbmpeg make[2]: Entering directory '/<>/libdvbmpeg' cc -g -O2 -fdebug-prefix-map=/build/vdr-J3eFss/vdr-2.4.1=. -fstack-protector-strong -Wformat -Werror=format-security -fPIC -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -c -D_GNU_SOURCE -U_FORTIFY_SOURCE -I/include -I.. -o ctools.o ctools.c cc -g -O2 -fdebug-prefix-map=/build/vdr-J3eFss/vdr-2.4.1=. -fstack-protector-strong -Wformat -Werror=format-security -fPIC -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -c -D_GNU_SOURCE -U_FORTIFY_SOURCE -I/include -I.. -o remux.o remux.c cc -g -O2 -fdebug-prefix-map=/build/vdr-J3eFss/vdr-2.4.1=. -fstack-protector-strong -Wformat -Werror=format-security -fPIC -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -c -D_GNU_SOURCE -U_FORTIFY_SOURCE -I/include -I.. -o ringbuffy.o ringbuffy.c cc -g -O2 -fdebug-prefix-map=/build/vdr-J3eFss/vdr-2.4.1=. -fstack-protector-strong -Wformat -Werror=format-security -fPIC -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -c -D_GNU_SOURCE -U_FORTIFY_SOURCE -I/include -I.. -o transform.o transform.c ar -rcs libdvbmpegtools.a ctools.o remux.o ringbuffy.o transform.o make[2]: Leaving directory '/<>/libdvbmpeg' make -C ./remux make[2]: Entering directory '/<>/remux' g++ -g -O2 -fdebug-prefix-map=/build/vdr-J3eFss/vdr-2.4.1=. -fstack-protector-strong -Wformat -Werror=format-security -fPIC -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -c -D_GNU_SOURCE -I/include -I.. -o tsremux.o tsremux.c g++ -g -O2
Bug#984391: marked as done (vdr-plugin-remote: ftbfs with GCC-11)
Your message dated Wed, 15 Dec 2021 19:00:25 + with message-id and subject line Bug#984393: fixed in vdr-plugin-xineliboutput 2.2.0+git20211212-1 has caused the Debian Bug report #984393, regarding vdr-plugin-remote: ftbfs with GCC-11 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.) -- 984393: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984393 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:vdr-plugin-remote Version: 0.7.0-4 Severity: normal Tags: sid bookworm User: debian-...@lists.debian.org Usertags: ftbfs-gcc-11 [This bug is not targeted to the upcoming bullseye release] Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-11/g++-11, but succeeds to build with gcc-10/g++-10. The severity of this report will be raised before the bookworm release, so nothing has to be done for the bullseye release. The full build log can be found at: http://people.debian.org/~doko/logs/20210228/filtered/gcc11/vdr-plugin-remote_0.7.0-4_unstable_gcc11.log The last lines of the build log are at the end of this report. To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-11/porting_to.html GCC 11 defaults to the GNU++17 standard. If your package installs header files in /usr/include, please don't work around C++17 issues by choosing a lower C++ standard for the package build, but fix these issues to build with the C++17 standard. [...] dh clean --with vdrplugin dh: warning: Compatibility levels before 10 are deprecated (level 9 in use) dh_auto_clean dh_auto_clean: warning: Compatibility levels before 10 are deprecated (level 9 in use) make -j1 clean make[1]: Entering directory '/<>' make[1]: Leaving directory '/<>' dh_clean dh_clean: warning: Compatibility levels before 10 are deprecated (level 9 in use) debian/rules build dh build --with vdrplugin dh: warning: Compatibility levels before 10 are deprecated (level 9 in use) dh_update_autotools_config dh_auto_configure dh_auto_configure: warning: Compatibility levels before 10 are deprecated (level 9 in use) dh_auto_build dh_auto_build: warning: Compatibility levels before 10 are deprecated (level 9 in use) make -j1 make[1]: Entering directory '/<>' g++ -g -O2 -fdebug-prefix-map=/build/vdr-J3eFss/vdr-2.4.1=. -fstack-protector-strong -Wformat -Werror=format-security -fPIC -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -c -DPLUGIN_NAME_I18N='"remote"' -DREMOTE_FEATURE_LIRC -DREMOTE_FEATURE_TCPIP remote.c g++ -g -O2 -fdebug-prefix-map=/build/vdr-J3eFss/vdr-2.4.1=. -fstack-protector-strong -Wformat -Werror=format-security -fPIC -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -c -DPLUGIN_NAME_I18N='"remote"' -DREMOTE_FEATURE_LIRC -DREMOTE_FEATURE_TCPIP ttystatus.c ttystatus.c: In member function ‘virtual void cTtyStatus::display(const char*, bool, int)’: ttystatus.c:114:13: error: ‘min’ was not declared in this scope; did you mean ‘std::min’? 114 | n = min(limit-pos, (int)sizeof(blanks)-1); | ^~~ | std::min In file included from /usr/include/c++/11/bits/specfun.h:45, from /usr/include/c++/11/cmath:1927, from /usr/include/c++/11/math.h:36, from /usr/include/vdr/tools.h:18, from /usr/include/vdr/i18n.h:14, from /usr/include/vdr/plugin.h:13, from ttystatus.c:25: /usr/include/c++/11/bits/stl_algobase.h:278:5: note: ‘std::min’ declared here 278 | min(const _Tp& __a, const _Tp& __b, _Compare __comp) | ^~~ ttystatus.c: In member function ‘virtual void cTtyStatus::OsdCurrentItem(const char*)’: ttystatus.c:361:17: error: ‘min’ was not declared in this scope; did you mean ‘std::min’? 361 | first = min(currIndex-10,lastIndex-20); | ^~~ | std::min In file included from
Bug#984390: marked as done (vdr-plugin-satip: ftbfs with GCC-11)
Your message dated Wed, 15 Dec 2021 19:00:25 + with message-id and subject line Bug#984393: fixed in vdr-plugin-xineliboutput 2.2.0+git20211212-1 has caused the Debian Bug report #984393, regarding vdr-plugin-satip: ftbfs with GCC-11 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.) -- 984393: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984393 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:vdr-plugin-satip Version: 2.4.0-4 Severity: normal Tags: sid bookworm User: debian-...@lists.debian.org Usertags: ftbfs-gcc-11 [This bug is not targeted to the upcoming bullseye release] Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-11/g++-11, but succeeds to build with gcc-10/g++-10. The severity of this report will be raised before the bookworm release, so nothing has to be done for the bullseye release. The full build log can be found at: http://people.debian.org/~doko/logs/20210228/filtered/gcc11/vdr-plugin-satip_2.4.0-4_unstable_gcc11.log The last lines of the build log are at the end of this report. To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-11/porting_to.html GCC 11 defaults to the GNU++17 standard. If your package installs header files in /usr/include, please don't work around C++17 issues by choosing a lower C++ standard for the package build, but fix these issues to build with the C++17 standard. [...] Command: dpkg-buildpackage -us -uc -b -rfakeroot dpkg-buildpackage: info: source package vdr-plugin-satip dpkg-buildpackage: info: source version 2.4.0-4 dpkg-buildpackage: info: source distribution unstable dpkg-buildpackage: info: source changed by Tobias Grimm dpkg-source --before-build . dpkg-buildpackage: info: host architecture amd64 fakeroot debian/rules clean dh clean --with vdrplugin dh: warning: Compatibility levels before 10 are deprecated (level 9 in use) dh_auto_clean dh_auto_clean: warning: Compatibility levels before 10 are deprecated (level 9 in use) make -j1 clean make[1]: Entering directory '/<>' make[1]: Leaving directory '/<>' dh_clean dh_clean: warning: Compatibility levels before 10 are deprecated (level 9 in use) debian/rules build dh build --with vdrplugin dh: warning: Compatibility levels before 10 are deprecated (level 9 in use) dh_update_autotools_config dh_auto_configure dh_auto_configure: warning: Compatibility levels before 10 are deprecated (level 9 in use) debian/rules override_dh_auto_build make[1]: Entering directory '/<>' dh_auto_build -- STRIP=/bin/true dh_auto_build: warning: Compatibility levels before 10 are deprecated (level 9 in use) make -j1 STRIP=/bin/true make[2]: Entering directory '/<>' g++ -MM -MG -g -O2 -fdebug-prefix-map=/build/vdr-J3eFss/vdr-2.4.1=. -fstack-protector-strong -Wformat -Werror=format-security -fPIC -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -DPLUGIN_NAME_I18N='"satip"' satip.c common.c config.c device.c discover.c msearch.c param.c poller.c rtp.c rtcp.c rtsp.c sectionfilter.c server.c setup.c socket.c statistics.c tuner.c > .dependencies CC satip.o g++ -g -O2 -fdebug-prefix-map=/build/vdr-J3eFss/vdr-2.4.1=. -fstack-protector-strong -Wformat -Werror=format-security -fPIC -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -c -DPLUGIN_NAME_I18N='"satip"' -o satip.o satip.c CC common.o g++ -g -O2 -fdebug-prefix-map=/build/vdr-J3eFss/vdr-2.4.1=. -fstack-protector-strong -Wformat -Werror=format-security -fPIC -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -c -DPLUGIN_NAME_I18N='"satip"' -o common.o common.c CC config.o g++ -g -O2 -fdebug-prefix-map=/build/vdr-J3eFss/vdr-2.4.1=. -fstack-protector-strong -Wformat -Werror=format-security -fPIC -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -c -DPLUGIN_NAME_I18N='"satip"' -o config.o config.c CC device.o g++ -g
Bug#984383: marked as done (vdr-plugin-dvbhddevice: ftbfs with GCC-11)
Your message dated Wed, 15 Dec 2021 19:00:25 + with message-id and subject line Bug#984393: fixed in vdr-plugin-xineliboutput 2.2.0+git20211212-1 has caused the Debian Bug report #984393, regarding vdr-plugin-dvbhddevice: ftbfs with GCC-11 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.) -- 984393: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984393 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:vdr-plugin-dvbhddevice Version: 2.2.0-13 Severity: normal Tags: sid bookworm User: debian-...@lists.debian.org Usertags: ftbfs-gcc-11 [This bug is not targeted to the upcoming bullseye release] Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-11/g++-11, but succeeds to build with gcc-10/g++-10. The severity of this report will be raised before the bookworm release, so nothing has to be done for the bullseye release. The full build log can be found at: http://people.debian.org/~doko/logs/20210228/filtered/gcc11/vdr-plugin-dvbhddevice_2.2.0-13_unstable_gcc11.log The last lines of the build log are at the end of this report. To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-11/porting_to.html GCC 11 defaults to the GNU++17 standard. If your package installs header files in /usr/include, please don't work around C++17 issues by choosing a lower C++ standard for the package build, but fix these issues to build with the C++17 standard. [...] Command: dpkg-buildpackage -us -uc -b -rfakeroot dpkg-buildpackage: info: source package vdr-plugin-dvbhddevice dpkg-buildpackage: info: source version 2.2.0-13 dpkg-buildpackage: info: source distribution unstable dpkg-buildpackage: info: source changed by Tobias Grimm dpkg-source --before-build . dpkg-buildpackage: info: host architecture amd64 fakeroot debian/rules clean dh clean --with vdrplugin dh: warning: Compatibility levels before 10 are deprecated (level 9 in use) dh_auto_clean dh_auto_clean: warning: Compatibility levels before 10 are deprecated (level 9 in use) make -j1 clean make[1]: Entering directory '/<>' make[1]: Leaving directory '/<>' dh_clean dh_clean: warning: Compatibility levels before 10 are deprecated (level 9 in use) debian/rules build dh build --with vdrplugin dh: warning: Compatibility levels before 10 are deprecated (level 9 in use) dh_update_autotools_config dh_auto_configure dh_auto_configure: warning: Compatibility levels before 10 are deprecated (level 9 in use) dh_auto_build dh_auto_build: warning: Compatibility levels before 10 are deprecated (level 9 in use) make -j1 make[1]: Entering directory '/<>' g++ -g -O2 -fdebug-prefix-map=/build/vdr-J3eFss/vdr-2.4.1=. -fstack-protector-strong -Wformat -Werror=format-security -fPIC -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -c -DPLUGIN_NAME_I18N='"dvbhddevice"' -o dvbhddevice.o dvbhddevice.c g++ -g -O2 -fdebug-prefix-map=/build/vdr-J3eFss/vdr-2.4.1=. -fstack-protector-strong -Wformat -Werror=format-security -fPIC -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -c -DPLUGIN_NAME_I18N='"dvbhddevice"' -o dvbhdffdevice.o dvbhdffdevice.c g++ -g -O2 -fdebug-prefix-map=/build/vdr-J3eFss/vdr-2.4.1=. -fstack-protector-strong -Wformat -Werror=format-security -fPIC -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -c -DPLUGIN_NAME_I18N='"dvbhddevice"' -o hdffcmd.o hdffcmd.c g++ -g -O2 -fdebug-prefix-map=/build/vdr-J3eFss/vdr-2.4.1=. -fstack-protector-strong -Wformat -Werror=format-security -fPIC -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -c -DPLUGIN_NAME_I18N='"dvbhddevice"' -o hdffosd.o hdffosd.c hdffosd.c: In member function ‘virtual void cHdffOsd::DrawText(int, int, const char*, tColor, tColor, const cFont*, int, int, int)’: hdffosd.c:352:26: error: ‘max’ was not declared in this scope; did you mean ‘std::max’? 352 |
Bug#984385: marked as done (vdr-plugin-dvd: ftbfs with GCC-11)
Your message dated Wed, 15 Dec 2021 19:00:25 +
with message-id
and subject line Bug#984393: fixed in vdr-plugin-xineliboutput
2.2.0+git20211212-1
has caused the Debian Bug report #984393,
regarding vdr-plugin-dvd: ftbfs with GCC-11
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.)
--
984393: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984393
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:vdr-plugin-dvd
Version: 0.3.6~b03+cvs20090426.0013-28
Severity: normal
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-11
[This bug is not targeted to the upcoming bullseye release]
Please keep this issue open in the bug tracker for the package it
was filed for. If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.
The package fails to build in a test rebuild on at least amd64 with
gcc-11/g++-11, but succeeds to build with gcc-10/g++-10. The
severity of this report will be raised before the bookworm release,
so nothing has to be done for the bullseye release.
The full build log can be found at:
http://people.debian.org/~doko/logs/20210228/filtered/gcc11/vdr-plugin-dvd_0.3.6~b03+cvs20090426.0013-28_unstable_gcc11.log
The last lines of the build log are at the end of this report.
To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.
apt-get -t=experimental install g++
Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-11/porting_to.html
GCC 11 defaults to the GNU++17 standard. If your package installs
header files in /usr/include, please don't work around C++17 issues
by choosing a lower C++ standard for the package build, but fix these
issues to build with the C++17 standard.
[...]
player-dvd.c:417:30: warning: format ‘%lld’ expects argument of type ‘long long
int’, but argument 5 has type ‘int64_t’ {aka ‘long int’} [-Wformat=]
417 | fprintf(f, "%d:%d:%lld:%s\n", re->title, re->chapter,
re->second, re->key);
| ~~~^~~
| ||
| long long int
int64_t {aka long int}
| %ld
player-dvd.c: In member function ‘void cDvdPlayer::GetAudioLanguageStr(const
char**) const’:
player-dvd.c:3066:30: warning: ISO C++ forbids converting a string constant to
‘char*’ [-Wwrite-strings]
3066 | audioTypeDescr = "ac3";
| ^
player-dvd.c:3069:30: warning: ISO C++ forbids converting a string constant to
‘char*’ [-Wwrite-strings]
3069 | audioTypeDescr = "dts";
| ^
player-dvd.c:3072:30: warning: ISO C++ forbids converting a string constant to
‘char*’ [-Wwrite-strings]
3072 | audioTypeDescr = "pcm";
| ^
player-dvd.c:3075:30: warning: ISO C++ forbids converting a string constant to
‘char*’ [-Wwrite-strings]
3075 | audioTypeDescr = "mp2";
| ^
player-dvd.c:3078:30: warning: ISO C++ forbids converting a string constant to
‘char*’ [-Wwrite-strings]
3078 | audioTypeDescr = "non";
| ^
player-dvd.c:3083:33: warning: narrowing conversion of
‘audioStreamLanguageCode’ from ‘uint16_t’ {aka ‘short unsigned int’} to ‘char’
[-Wnarrowing]
3083 | char audioLanguageStr[3] = {audioStreamLanguageCode,
audioStreamLanguageCode >> 8, 0};
| ^~~
player-dvd.c:3083:82: warning: narrowing conversion of
‘(int)(audioStreamLanguageCode >> 8)’ from ‘int’ to ‘char’ [-Wnarrowing]
3083 | char audioLanguageStr[3] = {audioStreamLanguageCode,
audioStreamLanguageCode >> 8, 0};
|
^~~~
player-dvd.c: In member function ‘void cDvdPlayer::GetSubtitleLanguageStr(const
char**) const’:
player-dvd.c:3101:36: warning: narrowing conversion of
‘subtitleStreamLanguageCode’ from ‘int’ to ‘char’ [-Wnarrowing]
3101 | char subtitleLanguageStr[3] =
Bug#984382: marked as done (vdr: ftbfs with GCC-11)
Your message dated Wed, 15 Dec 2021 19:00:25 + with message-id and subject line Bug#984393: fixed in vdr-plugin-xineliboutput 2.2.0+git20211212-1 has caused the Debian Bug report #984393, regarding vdr: ftbfs with GCC-11 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.) -- 984393: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984393 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:vdr Version: 2.4.1-4.1 Severity: normal Tags: sid bookworm User: debian-...@lists.debian.org Usertags: ftbfs-gcc-11 [This bug is not targeted to the upcoming bullseye release] Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-11/g++-11, but succeeds to build with gcc-10/g++-10. The severity of this report will be raised before the bookworm release, so nothing has to be done for the bullseye release. The full build log can be found at: http://people.debian.org/~doko/logs/20210228/filtered/gcc11/vdr_2.4.1-4.1_unstable_gcc11.log The last lines of the build log are at the end of this report. To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-11/porting_to.html GCC 11 defaults to the GNU++17 standard. If your package installs header files in /usr/include, please don't work around C++17 issues by choosing a lower C++ standard for the package build, but fix these issues to build with the C++17 standard. [...] In file included from /usr/include/c++/11/bits/specfun.h:45, from /usr/include/c++/11/cmath:1927, from /usr/include/c++/11/math.h:36, from tools.h:18, from i18n.h:14, from config.h:19, from channels.h:13, from channels.c:10: /usr/include/c++/11/bits/stl_algobase.h:300:5: note: ‘std::max’ declared here 300 | max(const _Tp& __a, const _Tp& __b, _Compare __comp) | ^~~ channels.c: In static member function ‘static int cChannels::MaxShortChannelNameLength()’: channels.c:1061:41: error: ‘max’ was not declared in this scope; did you mean ‘std::max’? 1061 | maxShortChannelNameLength = max(Utf8StrLen(Channel->ShortName(true)), maxShortChannelNameLength); | ^~~ | std::max In file included from /usr/include/c++/11/bits/specfun.h:45, from /usr/include/c++/11/cmath:1927, from /usr/include/c++/11/math.h:36, from tools.h:18, from i18n.h:14, from config.h:19, from channels.h:13, from channels.c:10: /usr/include/c++/11/bits/stl_algobase.h:300:5: note: ‘std::max’ declared here 300 | max(const _Tp& __a, const _Tp& __b, _Compare __comp) | ^~~ ci.c: In member function ‘virtual void cCaPidReceiver::Receive(const uchar*, int)’: ci.c:216:17: error: ‘min’ was not declared in this scope; did you mean ‘std::min’? 216 | int n = min(length, TS_SIZE - 4); | ^~~ | std::min In file included from /usr/include/c++/11/bits/specfun.h:45, from /usr/include/c++/11/cmath:1927, from /usr/include/c++/11/math.h:36, from tools.h:18, from i18n.h:14, from config.h:19, from channels.h:13, from ci.h:15, from ci.c:10: /usr/include/c++/11/bits/stl_algobase.h:278:5: note: ‘std::min’ declared here 278 | min(const _Tp& __a, const _Tp& __b, _Compare __comp) | ^~~ ci.c: In member function ‘bool cCiMMI::SendAnswer(const char*)’: ci.c:1596:12: error: ‘min’ was not declared in this scope; did you mean ‘std::min’? 1596 | len = min(sizeof(answer.text), strlen(Text)); |^~~ |std::min In file included from /usr/include/c++/11/bits/specfun.h:45, from
Bug#984248: marked as done (mygui: ftbfs with GCC-11)
Your message dated Wed, 15 Dec 2021 19:00:22 + with message-id and subject line Bug#984248: fixed in mygui 3.4.1+dfsg-1 has caused the Debian Bug report #984248, regarding mygui: ftbfs with GCC-11 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.) -- 984248: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984248 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:mygui Version: 3.2.2+dfsg-2.1 Severity: normal Tags: sid bookworm User: debian-...@lists.debian.org Usertags: ftbfs-gcc-11 [This bug is not targeted to the upcoming bullseye release] Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-11/g++-11, but succeeds to build with gcc-10/g++-10. The severity of this report will be raised before the bookworm release, so nothing has to be done for the bullseye release. The full build log can be found at: http://people.debian.org/~doko/logs/20210228/filtered/gcc11/mygui_3.2.2+dfsg-2.1_unstable_gcc11.log The last lines of the build log are at the end of this report. To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-11/porting_to.html GCC 11 defaults to the GNU++17 standard. If your package installs header files in /usr/include, please don't work around C++17 issues by choosing a lower C++ standard for the package build, but fix these issues to build with the C++17 standard. [...] from /usr/include/c++/11/sstream:38, from /<>/MyGUIEngine/include/MyGUI_LogStream.h:12, from /<>/MyGUIEngine/include/MyGUI_LogManager.h:11, from /<>/MyGUIEngine/include/MyGUI_Diagnostic.h:12, from /<>/MyGUIEngine/include/MyGUI_Common.h:36, from /<>/MyGUIEngine/include/MyGUI_Precompiled.h:11, from /<>/MyGUIEngine/src/MyGUI_ActionController.cpp:7: /usr/include/c++/11/ostream:250:7: error: ‘std::basic_ostream<_CharT, _Traits>::__ostream_type& std::basic_ostream<_CharT, _Traits>::operator<<(std::nullptr_t)’ cannot be overloaded with ‘std::basic_ostream<_CharT, _Traits>::__ostream_type& std::basic_ostream<_CharT, _Traits>::operator<<(int)’ 250 | operator<<(nullptr_t) | ^~~~ /usr/include/c++/11/ostream:189:7: note: previous declaration ‘std::basic_ostream<_CharT, _Traits>::__ostream_type& std::basic_ostream<_CharT, _Traits>::operator<<(int)’ 189 | operator<<(int __n); | ^~~~ In file included from /usr/include/c++/11/istream:39, from /usr/include/c++/11/sstream:38, from /<>/MyGUIEngine/include/MyGUI_LogStream.h:12, from /<>/MyGUIEngine/include/MyGUI_LogManager.h:11, from /<>/MyGUIEngine/include/MyGUI_Diagnostic.h:12, from /<>/MyGUIEngine/include/MyGUI_Common.h:36, from /<>/MyGUIEngine/include/MyGUI_Precompiled.h:11, from /<>/MyGUIEngine/src/MyGUI_BackwardCompatibility.cpp:7: /usr/include/c++/11/ostream:250:7: error: ‘std::basic_ostream<_CharT, _Traits>::__ostream_type& std::basic_ostream<_CharT, _Traits>::operator<<(std::nullptr_t)’ cannot be overloaded with ‘std::basic_ostream<_CharT, _Traits>::__ostream_type& std::basic_ostream<_CharT, _Traits>::operator<<(int)’ 250 | operator<<(nullptr_t) | ^~~~ /usr/include/c++/11/ostream:189:7: note: previous declaration ‘std::basic_ostream<_CharT, _Traits>::__ostream_type& std::basic_ostream<_CharT, _Traits>::operator<<(int)’ 189 | operator<<(int __n); | ^~~~ In file included from /usr/include/c++/11/istream:39, from /usr/include/c++/11/sstream:38, from /<>/MyGUIEngine/include/MyGUI_LogStream.h:12, from /<>/MyGUIEngine/include/MyGUI_LogManager.h:11, from /<>/MyGUIEngine/include/MyGUI_Diagnostic.h:12, from /<>/MyGUIEngine/include/MyGUI_Common.h:36, from
Bug#984393: marked as done (vdr-plugin-xineliboutput: ftbfs with GCC-11)
Your message dated Wed, 15 Dec 2021 19:00:25 + with message-id and subject line Bug#984393: fixed in vdr-plugin-xineliboutput 2.2.0+git20211212-1 has caused the Debian Bug report #984393, regarding vdr-plugin-xineliboutput: ftbfs with GCC-11 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.) -- 984393: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984393 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:vdr-plugin-xineliboutput Version: 2.1.0+git20191101-1.1 Severity: normal Tags: sid bookworm User: debian-...@lists.debian.org Usertags: ftbfs-gcc-11 [This bug is not targeted to the upcoming bullseye release] Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-11/g++-11, but succeeds to build with gcc-10/g++-10. The severity of this report will be raised before the bookworm release, so nothing has to be done for the bullseye release. The full build log can be found at: http://people.debian.org/~doko/logs/20210228/filtered/gcc11/vdr-plugin-xineliboutput_2.1.0+git20191101-1.1_unstable_gcc11.log The last lines of the build log are at the end of this report. To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-11/porting_to.html GCC 11 defaults to the GNU++17 standard. If your package installs header files in /usr/include, please don't work around C++17 issues by choosing a lower C++ standard for the package build, but fix these issues to build with the C++17 standard. [...] device.c:1370:16: error: ‘min’ was not declared in this scope; did you mean ‘std::min’? 1370 | result = min(result, m_local->Poll(Poller, TimeoutMs)); |^~~ |std::min In file included from /usr/include/c++/11/bits/specfun.h:45, from /usr/include/c++/11/cmath:1927, from /usr/include/c++/11/math.h:36, from /usr/include/vdr/tools.h:18, from /usr/include/vdr/i18n.h:14, from /usr/include/vdr/config.h:19, from device.c:15: /usr/include/c++/11/bits/stl_algobase.h:278:5: note: ‘std::min’ declared here 278 | min(const _Tp& __a, const _Tp& __b, _Compare __comp) | ^~~ device.c:1372:16: error: ‘min’ was not declared in this scope; did you mean ‘std::min’? 1372 | result = min(result, m_server->Poll(Poller, TimeoutMs)); |^~~ |std::min In file included from /usr/include/c++/11/bits/specfun.h:45, from /usr/include/c++/11/cmath:1927, from /usr/include/c++/11/math.h:36, from /usr/include/vdr/tools.h:18, from /usr/include/vdr/i18n.h:14, from /usr/include/vdr/config.h:19, from device.c:15: /usr/include/c++/11/bits/stl_algobase.h:278:5: note: ‘std::min’ declared here 278 | min(const _Tp& __a, const _Tp& __b, _Compare __comp) | ^~~ device.c:1374:18: error: ‘max’ was not declared in this scope; did you mean ‘std::max’? 1374 | m_FreeBufs = max(result, 0); | ^~~ | std::max In file included from /usr/include/c++/11/bits/specfun.h:45, from /usr/include/c++/11/cmath:1927, from /usr/include/c++/11/math.h:36, from /usr/include/vdr/tools.h:18, from /usr/include/vdr/i18n.h:14, from /usr/include/vdr/config.h:19, from device.c:15: /usr/include/c++/11/bits/stl_algobase.h:300:5: note: ‘std::max’ declared here 300 | max(const _Tp& __a, const _Tp& __b, _Compare __comp) | ^~~ device.c: In member function ‘virtual void cXinelibDevice::GetOsdSize(int&, int&, double&)’: device.c:1526:18: error: ‘max’ was not declared in this scope; did you mean ‘std::max’? 1526 | Width = max(m_VideoSize->width, 512); | ^~~ | std::max In file
Bug#1001009: marked as done (Downloads external files on install)
Your message dated Wed, 15 Dec 2021 19:00:09 + with message-id and subject line Bug#1001009: fixed in dbab 1.5.7-2 has caused the Debian Bug report #1001009, regarding Downloads external files on install 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.) -- 1001009: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001009 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: dbab Version: 1.3.2-1 Severity: serious The package runs `dbab-get-list` in postinst, which downloads http://pgl.yoyo.org/adservers/serverlist.php?hostformat=dnsmasq=0=plaintext If the package cannot function without this or similar unpackaged file, it should be moved to contrib. If it can, the downloading should be done by the user/administrator. -- System Information: Debian Release: bookworm/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable'), (500, 'testing'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.15.0-1-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages dbab depends on: ii bind9-dnsutils [dnsutils] 1:9.17.20-3 ii curl 7.79.1-2 pn dnsmasq ii perl 5.32.1-6 dbab recommends no packages. dbab suggests no packages. --- End Message --- --- Begin Message --- Source: dbab Source-Version: 1.5.7-2 Done: Tong Sun We believe that the bug you reported is fixed in the latest version of dbab, 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 1001...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Tong Sun (supplier of updated dbab package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 11 Dec 2021 19:14:48 + Source: dbab Binary: dbab Architecture: source all Version: 1.5.7-2 Distribution: unstable Urgency: medium Maintainer: Tong Sun Changed-By: Tong Sun Description: dbab - dnsmasq-based ad-blocking using pixelserv Closes: 995769 1001009 Changes: dbab (1.5.7-2) unstable; urgency=medium . * properly remove auto-generated files instead * add ca-certificates to depend list; moved to contrib; closes: #1001009 * delete debian/dbab.maintscript; closes: #995769 * fix: missing-explanation-for-contrib-or-non-free-package * fix: out-of-date-standards-version * try to take care of the case of upgrading from buster * explain reasons for moving to contrib in d/README.Debian Checksums-Sha1: 48354bad1aef5dfe1e997a684b3e2a962dc69d11 1898 dbab_1.5.7-2.dsc cde3a3c454b7bcfd8afa2097022edae71c2ae4f0 14252 dbab_1.5.7.orig.tar.gz b38a47f1d1c10cd44763025fa8a634066785da8d 6396 dbab_1.5.7-2.debian.tar.xz 8c9c24145a759d14314763e7d8365cfa0241f697 21192 dbab_1.5.7-2_all.deb e263edd13f211a30f66885f50ee7a5012487ec75 6795 dbab_1.5.7-2_amd64.buildinfo Checksums-Sha256: f2cc8693f4ae26c0aff8deba85673e4b90b2b2d5ff5d108b55a64c3e7567ef8e 1898 dbab_1.5.7-2.dsc 4b9c3c453abf155ded33cd39bda5f8ece0543043f73342f456c1e3e07f1c2ae0 14252 dbab_1.5.7.orig.tar.gz 674c6c65280b12cab264f927deb16f3970a83a752a887fad88ae7546cb560695 6396 dbab_1.5.7-2.debian.tar.xz 0ba39eb852e1a7b13e694b6d2e1c62a49ec267cb3ed8e9fafd24736ee692031d 21192 dbab_1.5.7-2_all.deb 4aef79e40b7c0fcf1ec6776700cbabc48760719137d06e8d31e092b987302152 6795 dbab_1.5.7-2_amd64.buildinfo Files: 92c1370ad529076fa77ab11f6c021164 1898 contrib/net optional dbab_1.5.7-2.dsc dc808d4716d5d6e062cb242948827df9 14252 contrib/net optional dbab_1.5.7.orig.tar.gz 0952dcb73fd3bf96feea9dd00841282e 6396 contrib/net optional dbab_1.5.7-2.debian.tar.xz 8d1e2b413e47ee9895b215c58270f1d1 21192 contrib/net optional dbab_1.5.7-2_all.deb 8981ff3204cdc9e78bff041eb5f6ed18 6795 contrib/net optional dbab_1.5.7-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCgAwFiEEPpmlJvXcwMu/HO6mALrnSzQzafEFAmG1BEwSHG5pbGVzaEBk
Bug#1001764: mrgingham: autopkgtest failure with python3.10 as a supported version
Source: mrgingham Version: 1.20-3 Severity: serious X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: needs-update User: debian-pyt...@lists.debian.org Usertags: python3.10 python3-all-dev Control: affects -1 src:python3-defaults Hi Maintainer mrgingham's autopkgtests fail with python3.10 as a supported version [1]. This currently prevents the migration of python3-defaults to testing. I've copied what I hope is the relevant part of the log below. I believe the problem is due to the use of 'Testsuite: autopkgtest-pkg-python' and autodep8 always tests for all supported python versions, see #904999. Please either remove 'Testsuite: autopkgtest-pkg-python' from debian/control, or better yet, please adjust mrgingham so that it builds the extension for all supported python versions. Regards Graham [1] https://ci.debian.net/packages/m/mrgingham/testing/amd64/ autopkgtest [06:11:20]: test autodep8-python3: set -e ; for py in $(py3versions -r 2>/dev/null) ; do cd "$AUTOPKGTEST_TMP" ; echo "Testing with $py:" ; $py -c "import mrgingham; print(mrgingham)" ; done autopkgtest [06:11:20]: test autodep8-python3: [--- Testing with python3.10: Traceback (most recent call last): File "", line 1, in ModuleNotFoundError: No module named 'mrgingham' autopkgtest [06:11:20]: test autodep8-python3: ---] autopkgtest [06:11:20]: test autodep8-python3: - - - - - - - - - - results - - - - - - - - - - autodep8-python3 FAIL non-zero exit status 1
Processed: mrgingham: autopkgtest failure with python3.10 as a supported version
Processing control commands: > affects -1 src:python3-defaults Bug #1001764 [src:mrgingham] mrgingham: autopkgtest failure with python3.10 as a supported version Added indication that 1001764 affects src:python3-defaults -- 1001764: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001764 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#999041: marked as done (libimage-base-bundle-perl: missing required debian/rules targets build-arch and/or build-indep)
Your message dated Wed, 15 Dec 2021 16:34:03 + with message-id and subject line Bug#999041: fixed in libimage-base-bundle-perl 1.0.7-3.4 has caused the Debian Bug report #999041, regarding libimage-base-bundle-perl: missing required debian/rules targets build-arch and/or build-indep to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 999041: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999041 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libimage-base-bundle-perl Version: 1.0.7-3.3 Severity: important Justification: Debian Policy section 4.9 Tags: bookworm sid User: debian...@lists.debian.org Usertags: missing-build-arch-indep Dear maintainer, Your package does not include build-arch and/or build-indep targets in debian/rules. This is required by Debian Policy section 4.9, since 2012. https://www.debian.org/doc/debian-policy/ch-source.html#main-building-script-debian-rules Please note that this is also a sign that the packaging of this software could benefit from a refresh. For example, packages using 'dh' cannot be affected by this issue. This mass bug filing was discussed on debian-devel@ in https://lists.debian.org/debian-devel/2021/11/msg00052.html . The severity of this bug will be changed to 'serious' after a month. Best, Lucas --- End Message --- --- Begin Message --- Source: libimage-base-bundle-perl Source-Version: 1.0.7-3.4 Done: gregor herrmann We believe that the bug you reported is fixed in the latest version of libimage-base-bundle-perl, 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 999...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. gregor herrmann (supplier of updated libimage-base-bundle-perl 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, 15 Dec 2021 17:18:18 CET Source: libimage-base-bundle-perl Binary: Architecture: source Version: 1.0.7-3.4 Distribution: unstable Urgency: medium Maintainer: Don Armstrong Changed-By: gregor herrmann Description: Closes: 999041 Changes: libimage-base-bundle-perl (1.0.7-3.4) unstable; urgency=medium . * Non-maintainer upload. * Fix "missing required debian/rules targets build-arch and/or build- indep": add targets in debian/rules. (Closes: #999041) Checksums-Sha256: 53a06dbcf4bfd1793f94b9e6f49ac0d6e3d8f9983f19e8b28078b23e57707e45 1960 libimage-base-bundle-perl_1.0.7-3.4.dsc c59d55282f3441b1b6b0e2f21ec845b9447589fc9d2d71eb66bb647f6ef6c3d7 2537 libimage-base-bundle-perl_1.0.7-3.4.diff.gz 91bbb3e8e9dcd3a8f495af6eda5b256b415ce6dd4739bb94041dde46e0fffa19 5965 libimage-base-bundle-perl_1.0.7-3.4_sourceonly.buildinfo Checksums-Sha1: ce5872ebb385d51110721a34d70bc4276ff3f218 1960 libimage-base-bundle-perl_1.0.7-3.4.dsc 5377b5dd910a6bd20589f4180eba1850a3f7e6be 2537 libimage-base-bundle-perl_1.0.7-3.4.diff.gz eef5d07f8faba8570eac3e949042ffc2e9fe11ce 5965 libimage-base-bundle-perl_1.0.7-3.4_sourceonly.buildinfo Files: 4e0685acbf55e72072647e47e96c0564 1960 perl optional libimage-base-bundle-perl_1.0.7-3.4.dsc 36a477a4078881dbc3b1acea5ff2d74e 2537 perl optional libimage-base-bundle-perl_1.0.7-3.4.diff.gz 437c574ebb8dc7f96a1f26e4086deb58 5965 - - libimage-base-bundle-perl_1.0.7-3.4_sourceonly.buildinfo -BEGIN PGP SIGNATURE- iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAmG6FUpfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ qgZgXg//eDEXAFIcfJHSpc1w/IMB1az3FR8UCDzd9X3mddQ9HO649Aso5/OnCio8 JORCbLOpf4glp965jaVQgcUQGETlEvbzn3bT2v0lIuSLdCHjEz5dYdlKHENtH/2T Nu6cLQkajVAEc71jQyWJlg+A9XZupMslEA8vspTkPl7jmcsG6BwJqmCwabtdScsV kpIRa2z2smDA4yVfStZzsfodxNH1/VOZvVqiZzIZvczXNDcbIR8fLy3WgooXhOhq PTTWN0LQu9QVPfWzjKc1ajsQTWG1AUBXAFURGnbCKSbYduKQ1Mf+kCU7E0HidOUu GCsR9Afd2awcBMp9Wv0EmIZ1Dfk/Jfh301CcpAszyyVmu79Qj2STXFIr9NID4Pgh UldathgrSxIhYSgif1HuE6u9rEvEfXseWTWZV8Axy+PYFRTrC10Uns7Oo18nRdaM pf+l0TcQuvaiO85xYsLUP99NE0PNd+VwaxRJwMSWgSsMMVgWFo/uaRj4JS9lxrfL grkH9slUAYx76j9GyWX+vjUMReKQlPV2c+KjDUli9Nfv/QXyg9Em8Cy5LnA2x+zW IlgwFmyYZVGasoiQHmSQln48bUHGoUYO4ot2Q/m8Ujb6/g5wPbFWbiFgczGsL+uj
Bug#999083: gkrellm-leds: missing required debian/rules targets build-arch and/or build-indep
On Wed, Dec 15, 2021 at 09:28:39AM +0100, Christoph Biedl wrote: > > The severity of this bug will be changed to 'serious' after a month. > > In coordination with the maintainer, I will take over and do an > upload to resolve the issue soon. Current maintainer acknowledging. Thanks, Christoph. -- Mike Markley
Bug#1001760: FTBFS: 'placeholders' is ambiguous
Package: dart
Version: 6.9.5-4
Severity: serious
Tags: patch
Justification: ftbfs
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu jammy ubuntu-patch
Hi José Luís,
In rebuilding packages in Ubuntu for the liburdfdom-model package rename, I
found that dart currently fails to build from source:
/tmp/dart-6.9.5/unittests/unit/test_Signal.cpp: In member function 'virtual void
Signal_NonStaticMemberFunction_Test::TestBody()':
/tmp/dart-6.9.5/unittests/unit/test_Signal.cpp:118:9: error: reference to
'placeholders' is ambiguous
118 | using placeholders::_1;
| ^~~~
In file included from /usr/include/eigen3/Eigen/Core:265,
from /tmp/dart-6.9.5/obj-x86_64-linux-gnu/dart/config.hpp:5,
from /tmp/dart-6.9.5/dart/dart.hpp:33,
from /tmp/dart-6.9.5/unittests/unit/test_Signal.cpp:36:
/usr/include/eigen3/Eigen/src/Core/util/IndexedViewHelper.h:174:11: note:
candidates are: 'namespace Eigen::placeholders { }'
174 | namespace placeholders {
| ^~~~
In file included from /usr/include/c++/11/pstl/glue_algorithm_defs.h:13,
from /usr/include/c++/11/algorithm:74,
from
/tmp/dart-6.9.5/unittests/gtest/include/gtest/internal/gtest-port.h:284,
from
/tmp/dart-6.9.5/unittests/gtest/include/gtest/internal/gtest-internal.h:40,
from /tmp/dart-6.9.5/unittests/gtest/include/gtest/gtest.h:59,
from /tmp/dart-6.9.5/unittests/unit/test_Signal.cpp:34:
/usr/include/c++/11/functional:219:13: note: 'namespace
std::placeholders { }'
219 | namespace placeholders
| ^~~~
Please find attached a patch that disambiguates and lets the package build.
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru dart-6.9.5/debian/patches/series dart-6.9.5/debian/patches/series
--- dart-6.9.5/debian/patches/series2021-10-08 07:07:34.0 -0700
+++ dart-6.9.5/debian/patches/series2021-12-14 21:44:11.0 -0800
@@ -5,3 +5,4 @@
0007-fix-soversion.patch
0006-Reduce-test-result-accuracy-to-fix-i386.patch
0008-fix-cmake-example.patch
+stdc++.patch
diff -Nru dart-6.9.5/debian/patches/stdc++.patch
dart-6.9.5/debian/patches/stdc++.patch
--- dart-6.9.5/debian/patches/stdc++.patch 1969-12-31 16:00:00.0
-0800
+++ dart-6.9.5/debian/patches/stdc++.patch 2021-12-15 07:49:05.0
-0800
@@ -0,0 +1,22 @@
+Description: disambiguate 'placeholders' namespace
+ Eigen now has a 'placeholders' namespace, so specify that we're after
+ std::placeholders
+Author: Steve Langasek
+Last-Update: 2021-12-15
+Forwarded: no
+
+Index: dart-6.9.5/unittests/unit/test_Signal.cpp
+===
+--- dart-6.9.5.orig/unittests/unit/test_Signal.cpp
dart-6.9.5/unittests/unit/test_Signal.cpp
+@@ -115,8 +115,8 @@
+ signal2.connect(::onSignal2Static);
+
+ // Connect non-static member function
+- using placeholders::_1;
+- using placeholders::_2;
++ using std::placeholders::_1;
++ using std::placeholders::_2;
+ signal1.connect(bind(::onSignal1, , _1));
+ signal2.connect(bind(::onSignal2, , _1, _2));
+
Bug#999282: marked as done (spell: missing required debian/rules targets build-arch and/or build-indep)
Your message dated Wed, 15 Dec 2021 16:03:38 + with message-id and subject line Bug#999282: fixed in spell 1.0-24.1 has caused the Debian Bug report #999282, regarding spell: missing required debian/rules targets build-arch and/or build-indep to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 999282: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999282 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: spell Version: 1.0-24 Severity: important Justification: Debian Policy section 4.9 Tags: bookworm sid User: debian...@lists.debian.org Usertags: missing-build-arch-indep Dear maintainer, Your package does not include build-arch and/or build-indep targets in debian/rules. This is required by Debian Policy section 4.9, since 2012. https://www.debian.org/doc/debian-policy/ch-source.html#main-building-script-debian-rules Please note that this is also a sign that the packaging of this software could benefit from a refresh. For example, packages using 'dh' cannot be affected by this issue. This mass bug filing was discussed on debian-devel@ in https://lists.debian.org/debian-devel/2021/11/msg00052.html . The severity of this bug will be changed to 'serious' after a month. Best, Lucas --- End Message --- --- Begin Message --- Source: spell Source-Version: 1.0-24.1 Done: gregor herrmann We believe that the bug you reported is fixed in the latest version of spell, 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 999...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. gregor herrmann (supplier of updated spell 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: Tue, 14 Dec 2021 19:13:00 CET Source: spell Binary: Architecture: source Version: 1.0-24.1 Distribution: unstable Urgency: medium Maintainer: Giacomo Catenazzi Changed-By: gregor herrmann Description: Closes: 999282 Changes: spell (1.0-24.1) unstable; urgency=medium . * Non-maintainer upload. * Fix "missing required debian/rules targets build-arch and/or build- indep": add targets to debian/rules. (Closes: #999282) Checksums-Sha256: 6a0ab937673b344b7454aaa8228055caa64533fc2cf45044ac521e3bc391f384 1802 spell_1.0-24.1.dsc a874962a01d0ce22a2ab9c85898b056ea687fcd990847f97976418037ddd9cd8 9077 spell_1.0-24.1.diff.gz a4da168a4182e7ff9da5801812c77d86a8298dfb13ef2c45dc99ac84a3b48d65 6318 spell_1.0-24.1_sourceonly.buildinfo Checksums-Sha1: 350601f391b1fbdf0310c56f0ac69e3e0e832743 1802 spell_1.0-24.1.dsc 65f523fab09856556493f171b93266936e2c5891 9077 spell_1.0-24.1.diff.gz 16513131a0cc66206760224872b7480d4ed6bafd 6318 spell_1.0-24.1_sourceonly.buildinfo Files: fe4a76dee31a26b83dc232f8b21ecd5a 1802 text optional spell_1.0-24.1.dsc 5f4c567a2208bb3d0c8569664d5a906f 9077 text optional spell_1.0-24.1.diff.gz aafe33168f76bd853e06444bf030f392 6318 - - spell_1.0-24.1_sourceonly.buildinfo -BEGIN PGP SIGNATURE- iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAmG43qxfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ qgbRug//VXhOBYdV3yNXKbLZbGszGbc39zkjPTQYJrcHEUEmaVBet7+c/bNfWeJj vBRSuXSKmFgOwgWLAP2/JodnKpvhLJh+rZ2BpJoITERonqE6Sqgqn2Q6ucgl3ENY 3B9cn0PIhkRfbEgpCiP0Bhi3OkyV4ogFS9tAQtzxZsahM6ZM9pL9/raP4JA28ZmH Oaa4UQz74zfZQnVTKuEy0tfVRukIuPKbGlNXj8a2hI07m6HTkMfTbp/XMe1iav43 nAfMth6iinppVt82zzNr6wPO6D1qjRL6OvtkT2uWwN4M47iiu7/L/rx7+VUy1rBa jHagAJt4TcC/K1T1pz13bCfcVL/2AcKQYvu1AlqH/dqbUqCny7msrbTo9Qt8LQkQ /d3Gs8lLkDa/7c0AWJNiyHnuP7MgmeTUVRQgbjcQxPNc74xeBTz8VwFLsODVaPfI i1e3HxJmV2gt/169Ql8eq80JG7R6wL3hJ1+9wdIN/GE93eztfowA/LvdOESRthI4 ijHF+Pfa1b3ly37uX1oPMblh2fDq/kgjnNAzl53HPAjOGVCWJS68QMOiDqjzd4Az JD1RqdDc82GZnZKtCb0i6+YYYm0BgGOCeJGuaiM3FbjikjKFiC0n5F1+XwaBhb9b NxzQm0rC27OM0U0h2Q+X4GlC7TKWnoO9Q+QGE9TrAf8sHTJouIw= =ei5T -END PGP SIGNATURE End Message ---
Bug#999041: libimage-base-bundle-perl: diff for NMU version 1.0.7-3.3
On Tue, 14 Dec 2021 16:55:58 -0800, Don Armstrong wrote: > On Mon, 13 Dec 2021, gregor herrmann wrote: > > I've prepared an NMU for libimage-base-bundle-perl (versioned as 1.0.7-3.3) > > and > > uploaded it to DELAYED/5. Please feel free to tell me if I > > should delay it longer. > Feel free to upload right away; thanks for fixing it. Thanks! Rescheduled to DELAYED/0. > [I'm also happy if > the perl team takes over that package too.] Thanks for the offer. I'll see if I find the time to do it. [Normally I would just invest the few needed minutes but this package is a bit, hm, untypical :)] Cheers, gregor -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe `- NP: Nick Cave And The Bad Seeds: Cannibal's Hymn signature.asc Description: Digital Signature
Bug#998413: marked as done (gap-float: failed to build on i386 arch: object must be an MPFR, not a integer)
Your message dated Wed, 15 Dec 2021 16:08:53 +0100 with message-id and subject line Re: gap-float: autopkgtest regression: object must be an MPFR, not a integer has caused the Debian Bug report #998413, regarding gap-float: failed to build on i386 arch: object must be an MPFR, not a integer 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.) -- 998413: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998413 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gap-float Version: 0.9.9+ds-1 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of gap-float the autopkgtest of gap-float fails in testing when that autopkgtest is run with the binary packages of gap-float from unstable. It passes when run with only packages from testing. In tabular form: passfail gap-float from testing0.9.9+ds-1 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration to testing [1]. Can you please investigate the situation and fix it? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=gap-float https://ci.debian.net/data/autopkgtest/testing/i386/g/gap-float/16389623/log.gz Error, GET_MPFR: object must be an MPFR, not a integer Error, was not in any namespace Error, was not in any namespace autopkgtest [01:09:07]: test command2 OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Fixed in package version 1.0.2+ds-1. -- Jerome BENOIT | calculus+at-rezozer^dot*net https://qa.debian.org/developer.php?login=calcu...@rezozer.net AE28 AE15 710D FF1D 87E5 A762 3F92 19A6 7F36 C68B OpenPGP_signature Description: OpenPGP digital signature --- End Message ---
Bug#998413: gap-float: autopkgtest regression: object must be an MPFR, not a integer
Fixed in package version 1.0.2+ds-1. -- Jerome BENOIT | calculus+at-rezozer^dot*net https://qa.debian.org/developer.php?login=calcu...@rezozer.net AE28 AE15 710D FF1D 87E5 A762 3F92 19A6 7F36 C68B OpenPGP_signature Description: OpenPGP digital signature
Bug#996946: marked as done (freeipa-server: Server setup can fail due to some race in configuring pki-tomcatd)
Your message dated Wed, 15 Dec 2021 15:03:33 + with message-id and subject line Bug#996946: fixed in freeipa 4.9.8-1 has caused the Debian Bug report #996946, regarding freeipa-server: Server setup can fail due to some race in configuring pki-tomcatd 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.) -- 996946: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996946 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: freeipa-server Version: 4.9.7-1 Severity: serious Justification: RT This is a placeholder bug preventing migration to testing, until the root cause of server setup failing randomly is found. Seems to be related to slapd and pki-tomcatd; in some cases it doesn't trust it's own certificate or something. -- System Information: Debian Release: 11.0 APT prefers impish-updates APT policy: (500, 'impish-updates'), (500, 'impish-security'), (500, 'impish') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.13.0-19-generic (SMP w/8 CPU threads) Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8), LANGUAGE=fi:en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled --- End Message --- --- Begin Message --- Source: freeipa Source-Version: 4.9.8-1 Done: Timo Aaltonen We believe that the bug you reported is fixed in the latest version of freeipa, 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 996...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Timo Aaltonen (supplier of updated freeipa 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, 15 Dec 2021 16:41:25 +0200 Source: freeipa Built-For-Profiles: noudeb Architecture: source Version: 4.9.8-1 Distribution: unstable Urgency: medium Maintainer: Debian FreeIPA Team Changed-By: Timo Aaltonen Closes: 996946 Changes: freeipa (4.9.8-1) unstable; urgency=medium . * New upstream release. * patches: Drop upstreamed patch. * server.install: Updated. * Build only the client in order to be able to backport to bullseye. (Closes: #996946) * control: Depend on librpm9 instead of librpm8. * tests: Disabled for a client-only build. Checksums-Sha1: c8a4798d474508a11ed33cc004692386a440f9c3 3024 freeipa_4.9.8-1.dsc 38641a7f95779ba35089fcc10e25ec82a9b0248e 13272761 freeipa_4.9.8.orig.tar.gz 76f7dca9ca14f99f9676c9856f512494b422a0b0 282204 freeipa_4.9.8-1.debian.tar.xz 2496d26311941aab9a5d63fdbb821cb596e7803b 7884 freeipa_4.9.8-1_source.buildinfo Checksums-Sha256: dfa67f340f29ad9f3daad6a9a018fb0d2f194917f8df2a3828b7282640c11c3c 3024 freeipa_4.9.8-1.dsc 2fddaf6de41dfe244e25a3211f756491ffa8e657595b74388249d2287a601782 13272761 freeipa_4.9.8.orig.tar.gz ca8202fe4bb4654418e12dc5dbb2ddbc64fc65cab6818367ff9dea83f0f6e83c 282204 freeipa_4.9.8-1.debian.tar.xz 4885ab982dea153982d3bf5ff17087e7c50a8e08413578fb7f01522f0399bcb3 7884 freeipa_4.9.8-1_source.buildinfo Files: 90d7885af644ea8ab98c6eba8d140acb 3024 net optional freeipa_4.9.8-1.dsc 9f29f390a29500f0152a88e5513aa150 13272761 net optional freeipa_4.9.8.orig.tar.gz f633e6649ec4050c763941c9de0dcea8 282204 net optional freeipa_4.9.8-1.debian.tar.xz 222ee4811d736fc22bd2aa6fe76f6e50 7884 net optional freeipa_4.9.8-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEdS3ifE3rFwGbS2Yjy3AxZaiJhNwFAmG5/1kACgkQy3AxZaiJ hNxrFg/+LP1qQOo/BZ96vZqbBVxL3D1oXWbl+Ykmg5/29rWJJMVvAq4eOL1Wk5D8 1iXYJxqrITWJiqno83OMRqRMyGyGvi80+71a/341l33xaIPO/8QH1+h7cRwSLhTa Bh4YLsZrSu+s/kEXv2sdT7815aHKuTQ0oFEHB0Tts5785KQHBF3TyFiBMW/iF/e7 zg7qBRM/UBPK9wtoQECVDC+J+09aeDYJbFzGYdHZkzFejAZzpsSaTQiKyEvh6bVC cyPZpVpeqkTVpRvGfb3gmgJ6kFUns5Llx1TbV7mR3nJnzQBPlv70b4SNmnpH18R3 GhP6jxR6JjX15hKdbfheC1SRczmMoFhCXbTBxVHoSxdPwhTbmHiGqZgRrb2MM2ZQ nsDoiyKPtNG6QR4k3+yaUWIYPzRDej7vgsmYyGQmmi7DrUU0wUGVZCLoAwVVhsZb oNq5ztE5FcGzpNNsTH6heDwCeh79XTgccq7yvg68X7FaK6c1S9eGJXRVmyEapGCx Iw2WJuPoIh4enNO5bf2mQ/vTN2TL6XnzoaCDPUG4yeBh7p+nG6nI3RqTi+6qPVIA 1cWqy4J/peVYv+NeQ3L2yryZVAxBaueiQEym0dWmPyD/+v1JBZrBALpV1mPsUPLY 2ZSVpCgUAtXsls6aW8OCy86to4pe5wfXo8lOHK3Nn7q/lFIq1Eg= =zEhJ -END PGP SIGNATURE End Message ---
Bug#1001667: flam3: flaky autopkgtest on ppc64el
Thanks for reporting the problem. flam3-genome has a random element which probably explains the flakiness. However, I have run it thousands of times on my x64 desktop with no segfaults, and the issue does seem to be totally specific to ppc64el. Maybe it is a problem with the compiler or the kernel? I'm attaching a script that runs flam3-genome continuously until it crashes. It would be very helpful if someone with easy access to ppc64el could install flam3, run the script, and report a seed number that triggers a segfault. The problem should then be easily reproducible. Cheers, Peter genome.sh Description: application/shellscript
Bug#987816: marked as pending in dask.distributed
Dear Maintainer, On Sun, 28 Nov 2021 07:39:16 + Diane Trout wrote: > Control: tag -1 pending > > Hello, > > Bug #987816 in dask.distributed reported by you has been fixed in the > Git repository and is awaiting an upload. You can see the commit > message below and you can check the diff of the fix at: > > https://salsa.debian.org/python-team/packages/dask.distributed/-/commit/82fc3a8274972ec9c1c4619a2b1291f09fcdf0c0 > > > Import Debian changes 2021.01.0+ds.1-2.1 > > dask.distributed (2021.01.0+ds.1-2.1) unstable; urgency=medium > . > * Non-maintainer upload. > * Backport upstream fix removing tests that fail under some > circumstances. (Closes: #987816) > * python-distributed-doc: Fix broken symlink to html5shiv.min.js, > dh_link needs absolute paths. (Closes: #988675) > I tested with this version 2021.01.0+ds.1-2.1 (https://packages.debian.org/source/stable/dask.distributed) and it fails with the error, distributed/tests/test_core.py::test_server_listen FAILED Do we need to raise a different bug report for this ? Regards, Vignesh
Processed: tagging 1000435
Processing commands for cont...@bugs.debian.org: > tags 1000435 + ftbfs Bug #1000435 [src:matplotlib] Matplotlib crashes on mips64el in lines.py Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 1000435: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000435 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: xdelta: diff for NMU version 1.1.3-9.4
Processing control commands: > tags 999238 patch pending Bug #999238 [src:xdelta] xdelta: missing required debian/rules targets build-arch and/or build-indep Added tag(s) pending and patch. -- 999238: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999238 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#999238: xdelta: diff for NMU version 1.1.3-9.4
Control: tags 999238 patch pending
Hi LaMont,
I've prepared an NMU for xdelta (versioned as 1.1.3-9.4) and uploaded it
to DELAYED/5. Please feel free to tell me if I should delay it longer.
Regards,
--
Colin Watson [cjwat...@debian.org]
diff -u xdelta-1.1.3/debian/changelog xdelta-1.1.3/debian/changelog
--- xdelta-1.1.3/debian/changelog
+++ xdelta-1.1.3/debian/changelog
@@ -1,3 +1,10 @@
+xdelta (1.1.3-9.4) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * debian/rules: Add build-arch and build-indep targets (closes: #999238).
+
+ -- Colin Watson Wed, 15 Dec 2021 12:15:05 +
+
xdelta (1.1.3-9.3) unstable; urgency=medium
* Non-maintainer upload.
diff -u xdelta-1.1.3/debian/rules xdelta-1.1.3/debian/rules
--- xdelta-1.1.3/debian/rules
+++ xdelta-1.1.3/debian/rules
@@ -24,13 +24,15 @@
CPPFLAGS=`glib-config --cflags` CFLAGS="${CFLAGS}" \
dh_auto_configure
-build: build-stamp
+build build-arch: build-stamp
build-stamp: config.status
dh_testdir
$(MAKE)
touch $@
+build-indep:
+
autofiles:
#libtoolize --automake --copy --force
#aclocal
@@ -57,12 +59,12 @@
dh_install --sourcedir=debian/tmp --list-missing
-binary-indep: build install
+binary-indep: build-indep
# There are no architecture-independent files to be uploaded
# generated by this package. If there were any they would be
# made here.
-binary-arch: build install
+binary-arch: build-arch install
dh_testdir -a
dh_testroot -a
dh_installchangelogs -a
@@ -81,4 +83,4 @@
dh_builddeb -a
binary: binary-indep binary-arch
-.PHONY: build clean binary-arch binary-indep binary install
+.PHONY: build-arch build-indep build clean binary-arch binary-indep binary install
Bug#999282: spell: diff for NMU version 1.0-24.1
Thank you for the patch. No need to have a longer queue. ciao cate On 14.12.2021 19:13, gregor herrmann wrote: Control: tags 999282 + patch Control: tags 999282 + pending Dear maintainer, I've prepared an NMU for spell (versioned as 1.0-24.1) and uploaded it to DELAYED/5. Please feel free to tell me if I should delay it longer. Regards.
Processed: update bts with metadata
Processing commands for cont...@bugs.debian.org:
> reassign 1001718 src:ccdproc 2.2.0-1
Bug #1001718 {Done: Ole Streicher } [src:astroscrappy,
src:ccdproc] astroscrappy breaks ccdproc autopkgtest: detect_cosmics() got an
unexpected keyword argument 'pssl'
Bug reassigned from package 'src:astroscrappy, src:ccdproc' to 'src:ccdproc'.
No longer marked as found in versions astroscrappy/1.1.0-1 and ccdproc/2.2.0-1.
No longer marked as fixed in versions ccdproc/2.2.0-2.
Bug #1001718 {Done: Ole Streicher } [src:ccdproc]
astroscrappy breaks ccdproc autopkgtest: detect_cosmics() got an unexpected
keyword argument 'pssl'
Marked as found in versions ccdproc/2.2.0-1.
> fixed 1001718 2.2.0-2
Bug #1001718 {Done: Ole Streicher } [src:ccdproc]
astroscrappy breaks ccdproc autopkgtest: detect_cosmics() got an unexpected
keyword argument 'pssl'
Marked as fixed in versions ccdproc/2.2.0-2.
> affects 1001718 src:astroscrappy
Bug #1001718 {Done: Ole Streicher } [src:ccdproc]
astroscrappy breaks ccdproc autopkgtest: detect_cosmics() got an unexpected
keyword argument 'pssl'
Added indication that 1001718 affects src:astroscrappy
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1001718: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001718
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#984232: status
On Mon, Nov 15, 2021 at 02:53:40PM -0600, Ryan Pavlik wrote: > Upstream has fixed this, and I have a package with the latest upstream > sources in progress, happy to accept help to put it over the edge. Any progress on this? If necessary, I could NMU with the minimal fix of adding export DEB_CXXFLAGS_MAINT_APPEND += -std=gnu++14 to debian/rules. > Ryan cu Adrian
Bug#999319: popularity-contest: missing required debian/rules targets build-arch and/or build-indep
On Tue, Nov 09, 2021 at 10:28:20PM +0100, Lucas Nussbaum wrote: > Source: popularity-contest > Version: 1.73 > Severity: important > Justification: Debian Policy section 4.9 > Tags: bookworm sid > User: debian...@lists.debian.org > Usertags: missing-build-arch-indep > > Dear maintainer, > > Your package does not include build-arch and/or build-indep targets in > debian/rules. This is required by Debian Policy section 4.9, since 2012. > https://www.debian.org/doc/debian-policy/ch-source.html#main-building-script-debian-rules > > Please note that this is also a sign that the packaging of this software > could benefit from a refresh. For example, packages using 'dh' cannot be > affected by this issue. > > This mass bug filing was discussed on debian-devel@ in > https://lists.debian.org/debian-devel/2021/11/msg00052.html . > The severity of this bug will be changed to 'serious' after a month. Hello Lucas, I will need a bit more time because testing popcon is slow... Cheers, -- Bill. Imagine a large red swirl here.
Processed: severity of 999319 is important
Processing commands for cont...@bugs.debian.org: > severity 999319 important Bug #999319 [src:popularity-contest] popularity-contest: missing required debian/rules targets build-arch and/or build-indep Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 999319: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999319 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1001657: Ball fails its autopkgtest - how to properly deal with sip files?
On 15 December 2021 2:36:14 pm IST, Andreas Tille wrote: >Hi Étienne, > >Am Tue, Dec 14, 2021 at 11:13:21PM +0100 schrieb Étienne Mollier: >> Étienne Mollier, on 2021-12-14: >> > However, once the sip file is caught, the package fails to build >> > from source due to various errors in the generated code. The >> > patch also addresses one of them in its second hunk. I think I >> > was stuck on some "overrides" related errors, but they were >> > interleaved within sip output, I can send a proper log later >> > this week after an overnight build if needed. >> >> I forgot I had one other patch to address PyString issues, part >> of the ftbfs. And also forgot to mention that I had to enforce >> -DSIP_LIBRARIES=/usr/lib/python3/dist-packages from the cmake >> call in d/rules. >> >> In hope this helps, > >May be you can simply push your patches to make sure everything is >stored visibly. > >What I'm currently wondering is the following: According to popcon[1] >python3-ball has 2 votes and its only dependency ballview has 10 votes. >This makes no real sense if ballview would really need python3-ball. Based on the package description, python3-ball has the "python bindings" for the library packages. ballview does not seem to use the python bindings at all (as you'd normally expect). The python package is probably available for the case if you want to use the library itself in the python code and use it programmatically. The upstream wiki page seems to concur: https://github.com/BALL-Project/ball/wiki/BALLPythonScripting But I have no idea if these bindings are of any use. We can only know when someone who knows the software well can tell. So I'll echo the same thing you wrote below. Steffen to clarify :- >Upstream does not seem to be active any more but may be Steffen (in >CC) can clarify this.
Bug#1001657: Ball fails its autopkgtest - how to properly deal with sip files?
Hi Étienne, Am Tue, Dec 14, 2021 at 11:13:21PM +0100 schrieb Étienne Mollier: > Étienne Mollier, on 2021-12-14: > > However, once the sip file is caught, the package fails to build > > from source due to various errors in the generated code. The > > patch also addresses one of them in its second hunk. I think I > > was stuck on some "overrides" related errors, but they were > > interleaved within sip output, I can send a proper log later > > this week after an overnight build if needed. > > I forgot I had one other patch to address PyString issues, part > of the ftbfs. And also forgot to mention that I had to enforce > -DSIP_LIBRARIES=/usr/lib/python3/dist-packages from the cmake > call in d/rules. > > In hope this helps, May be you can simply push your patches to make sure everything is stored visibly. What I'm currently wondering is the following: According to popcon[1] python3-ball has 2 votes and its only dependency ballview has 10 votes. This makes no real sense if ballview would really need python3-ball. I'm wondering how we can find out whether ballview really depends the Python3 package or whether we can simply drop it. Upstream does not seem to be active any more but may be Steffen (in CC) can clarify this. Kind regards Andreas. [1] https://qa.debian.org/popcon.php?package=ball -- http://fam-tille.de
Processed: Re: Bug#999083: gkrellm-leds: missing required debian/rules targets build-arch and/or build-indep
Processing control commands: > tags 999083 pending Bug #999083 [src:gkrellm-leds] gkrellm-leds: missing required debian/rules targets build-arch and/or build-indep Added tag(s) pending. -- 999083: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999083 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#999083: gkrellm-leds: missing required debian/rules targets build-arch and/or build-indep
Control: tags 999083 pending Lucas Nussbaum wrote... > The severity of this bug will be changed to 'serious' after a month. In coordination with the maintainer, I will take over and do an upload to resolve the issue soon. Christoph signature.asc Description: PGP signature
Processed: severity of 1001744 is important
Processing commands for cont...@bugs.debian.org: > severity 1001744 important Bug #1001744 [cura] cura: Cura does not start Severity set to 'important' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. -- 1001744: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001744 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
