Bug#1027826: marked as done (python-skbio: don't Build Depend on python-matplotlib-doc (it no longer exist in bookworm))
Your message dated Thu, 05 Jan 2023 07:39:11 + with message-id and subject line Bug#1027826: fixed in python-skbio 0.5.8-1 has caused the Debian Bug report #1027826, regarding python-skbio: don't Build Depend on python-matplotlib-doc (it no longer exist in bookworm) 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.) -- 1027826: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027826 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-skbio Version: 0.5.6-7 Severity: serious Tag: ftbfs User: debian...@lists.debian.org Usertag: edos-uninstallable Dear maintainer(s), Dose [1] is reporting issues with your packages. Normally your build dependencies shouldn't be removed from testing without removal all reverse build dependencies too, nor should a package be allowed to migrate unless all build dependencies are candidate for migration too. However, somehow we ended up in the current state and your source package is missing a Build-Depends now. Not being able to build from source in a suite is an RC bug in that suite. matplotlib stopped building python-matplotlib-doc. Paul [1] https://qa.debian.org/dose/debcheck/src_testing_main/index.html OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: python-skbio Source-Version: 0.5.8-1 Done: Andreas Tille We believe that the bug you reported is fixed in the latest version of python-skbio, 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 1027...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille (supplier of updated python-skbio 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, 05 Jan 2023 07:57:37 +0100 Source: python-skbio Architecture: source Version: 0.5.8-1 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Andreas Tille Closes: 1027826 Changes: python-skbio (0.5.8-1) unstable; urgency=medium . [ Étienne Mollier ] * simde patch: remove; implemented upstream. * soften_test patch: remove; implemented upstream. * pandas1.1-ordination-fix.patch: remove; applied upstream. * pandas1.1-valueerror.patch: remove; applied upstream. * local_inventory patch: unfuzz. * sphinx_add_javascript.patch: remove; fixed upstream. * fix-dtype-precision-warnings.patch: remove; applied upstream. * d/rules: include build root in CPPFLAGS; allow source code to find the simde-sse2.h wrapper. . [ Nilesh Patra ] * d/watch: Use tags instead of releases as the latter is hard to maintain * New upstream version 0.5.8 * Drop precision_bug.patch, which has been accounted for upstream * Re-diff patches * Add patch to build with older scipy * Add B-D and Depends on python3-h5py * Add patch to work-around a test * Remove override_dh_python3 which is not needed now * Remove B-D on python-matplotlib-doc, update patch to not reference it in intersphinx docs (Closes: #1027826) * Disable i386 in salsa-ci.yml . [ Andreas Tille ] * Standards-Version: 4.6.2 (routine-update) * Automated changes by lintian-brush * Update lintian override info format in d/python3-skbio.lintian-overrides on line 5. Checksums-Sha1: 9c63f5070a520a1cdc47ffe6dbe5b26672a801f7 2770 python-skbio_0.5.8-1.dsc aad4079b41b248383842f964af42c68861121b2e 3579407 python-skbio_0.5.8.orig.tar.gz a493e5bef9f122dc44cdffaa99c7acb7873f2c24 9512 python-skbio_0.5.8-1.debian.tar.xz 27e8b5ab422cb7aedcb071cf5463c4f432c59563 13367 python-skbio_0.5.8-1_amd64.buildinfo Checksums-Sha256: d7281b96b94e0c335fd04a7b3b8b783c4c99534033412a0a3e611aff1b4ddfd6 2770 python-skbio_0.5.8-1.dsc 950dca0ce454cb1732a8d32655af825711ac01acbd596607560994f6991b129d 3579407 python-skbio_0.5.8.orig.tar.gz 0218d7ce685fb7697f44e8ff712869578f1a2eb4fca0068dbdcf804fa3494a4f 9512 python-skbio_0.5.8-1.debian.tar.xz 5c49391ccb5839922071bbb089263ee036ac2a5c6e767e8e1c2550153399d5d9 13367 python-skbio_0.5.8-1_amd64.buildinfo Files: 02a35eadcba2e6ba4909afd1db8fcbe7 2770 python optional python-skbio_0.5.8-1.dsc 52cf1e2a241b04fb6e1de76dbdbcc163
Bug#1027395: marked as done (astropy breaks imexam autopkgtest: AssertionError)
Your message dated Thu, 05 Jan 2023 07:37:51 + with message-id and subject line Bug#1027395: fixed in imexam 0.9.1-3 has caused the Debian Bug report #1027395, regarding astropy breaks imexam autopkgtest: AssertionError 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.) -- 1027395: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027395 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: astropy, imexam Control: found -1 astropy/5.2-1 Control: found -1 imexam/0.9.1-2 Severity: serious Tags: sid bookworm User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a recent upload of astropy the autopkgtest of imexam fails in testing when that autopkgtest is run with the binary packages of astropy from unstable. It passes when run with only packages from testing. In tabular form: passfail astropyfrom testing5.2-1 imexam from testing0.9.1-2 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration of astropy to testing [1]. Due to the nature of this issue, I filed this bug report against both packages. Can you please investigate the situation and reassign the bug to the right package? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=astropy https://ci.debian.net/data/autopkgtest/testing/amd64/i/imexam/29791506/log.gz === FAILURES === __ test_gauss_center ___ def test_gauss_center(): """Check the gaussian center fitting.""" from astropy.convolution import Gaussian2DKernel # This creates a 2D normalized gaussian kernal with # a set amplitude. Guess off-center amp = 0.0015915494309189533 size = 81.0 sigma = 10.0 gaussian_2D_kernel = Gaussian2DKernel(sigma, x_size=size, y_size=size) plots = Imexamine() plots.set_data(gaussian_2D_kernel.array) a, xx, yy, xs, ys = plots.gauss_center(37, 37) > assert_allclose(amp, a, 1e-6) E AssertionError: E Not equal to tolerance rtol=1e-06, atol=0 E E Mismatched elements: 1 / 1 (100%) E Max absolute difference: 1.61872075e-07 E Max relative difference: 0.0001017 Ex: array(0.001592) Ey: array(0.001592) /usr/lib/python3/dist-packages/imexam/tests/test_imexamine.py:128: AssertionError - Captured stdout call - xc=40. yc=40. -- Captured log call --- INFO imexam.util:imexamine.py:1015 xc=40. yc=40. OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: imexam Source-Version: 0.9.1-3 Done: Ole Streicher We believe that the bug you reported is fixed in the latest version of imexam, 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 1027...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ole Streicher (supplier of updated imexam 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, 05 Jan 2023 08:11:41 +0100 Source: imexam Architecture: source Version: 0.9.1-3 Distribution: unstable Urgency: medium Maintainer: Debian Astronomy Team Changed-By: Ole Streicher Closes: 1027395 Changes: imexam (0.9.1-3) unstable; urgency=medium . * Mark test failing with astropy 5.2 as xfail (Closes: #1027395) * Push Standards-Version to 4.6.2, no changes needed * Add Rules-Requires-Root: no to d/control Checksums-Sha1: bef943577248a934297030bf88b29f5205055dfd 2361 imexam_0.9.1-3.dsc 5fdeeda6c27eb0a77145bb72f9a3c9d6793ecee7 5928 imexam_0.9.1-3.debian.tar.xz Checksums-Sha256:
Processed: reassign 1027602 to src:pdm-pep517, forcibly merging 1027496 1027602, affects 1027602
Processing commands for cont...@bugs.debian.org:
> reassign 1027602 src:pdm-pep517
Bug #1027602 [src:rope] rope: FTBFS: ImportError: cannot import name
'LegacyVersion' from 'packaging.version'
(/usr/lib/python3/dist-packages/packaging/version.py)
Bug reassigned from package 'src:rope' to 'src:pdm-pep517'.
No longer marked as found in versions rope/1.6.0-1.
Ignoring request to alter fixed versions of bug #1027602 to the same values
previously set
> forcemerge 1027496 1027602
Bug #1027496 {Done: Boyuan Yang } [src:pdm-pep517]
pdm-pep517: FTBFS: ImportError: cannot import name 'LegacyVersion' from
'packaging.version' (/usr/lib/python3/dist-packages/packaging/version.py)
Bug #1027602 [src:pdm-pep517] rope: FTBFS: ImportError: cannot import name
'LegacyVersion' from 'packaging.version'
(/usr/lib/python3/dist-packages/packaging/version.py)
Marked Bug as done
Marked as fixed in versions pdm-pep517/1.0.6+ds1-2.
Marked as found in versions pdm-pep517/1.0.6+ds1-1.
Merged 1027496 1027602
> affects 1027602 rope
Bug #1027602 {Done: Boyuan Yang } [src:pdm-pep517] rope:
FTBFS: ImportError: cannot import name 'LegacyVersion' from 'packaging.version'
(/usr/lib/python3/dist-packages/packaging/version.py)
Bug #1027496 {Done: Boyuan Yang } [src:pdm-pep517]
pdm-pep517: FTBFS: ImportError: cannot import name 'LegacyVersion' from
'packaging.version' (/usr/lib/python3/dist-packages/packaging/version.py)
Added indication that 1027602 affects rope
Added indication that 1027496 affects rope
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1027496: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027496
1027602: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027602
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1003473: marked as pending in php-horde-lz4
Control: tag -1 pending Hello, Bug #1003473 in php-horde-lz4 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/horde-team/php-horde-lz4/-/commit/17094c5f099ecf0d5ccbb89da690a759b185e559 d/patches: fix compilation against php8.1. (Closes: #1003473) (this message was generated automatically) -- Greetings https://bugs.debian.org/1003473
Processed: Bug#1003473 marked as pending in php-horde-lz4
Processing control commands: > tag -1 pending Bug #1003473 [src:php-horde-lz4] php-horde-lz4: fails to build with php8.1 Added tag(s) pending. -- 1003473: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003473 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1027565: kiwix-tools: FTBFS: ld: /usr/lib/x86_64-linux-gnu/libkiwix.so: undefined reference to `zim::Item::getPath[abi:cxx11]() const'
Hi, On 1/1/23 06:31, Lucas Nussbaum wrote: /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libkiwix.so: undefined reference to `zim::Item::getPath[abi:cxx11]() const' collect2: error: ld returned 1 exit status My upload of src:zimlib 8.1.0 accidentally contained a breaking change, but this should be fixed when the libkiwix transition completes, see #1027959. Thanks, -- Kunal / Legoktm
Processed: src:gtksourceview4: fails to migrate to testing for too long: autpkgtest regression and uploader built arch:all binaries
Processing control commands:
> close -1 4.8.4-1
Bug #1027958 [src:gtksourceview4] src:gtksourceview4: fails to migrate to
testing for too long: autpkgtest regression and uploader built arch:all binaries
Marked as fixed in versions gtksourceview4/4.8.4-1.
Bug #1027958 [src:gtksourceview4] src:gtksourceview4: fails to migrate to
testing for too long: autpkgtest regression and uploader built arch:all binaries
Marked Bug as done
> block -1 by 1024011
Bug #1027958 {Done: Paul Gevers } [src:gtksourceview4]
src:gtksourceview4: fails to migrate to testing for too long: autpkgtest
regression and uploader built arch:all binaries
1027958 was not blocked by any bugs.
1027958 was not blocking any bugs.
Added blocking bug(s) of 1027958: 1024011
--
1027958: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027958
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1027958: src:gtksourceview4: fails to migrate to testing for too long: autpkgtest regression and uploader built arch:all binaries
Source: gtksourceview4 Version: 4.8.3-1 Severity: serious Control: close -1 4.8.4-1 Tags: sid bookworm User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 1024011 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:gtksourceview4 has been trying to migrate for 61 days [2]. Hence, I am filing this bug. Your package fails its own autopkgtest, which was reported in bug #1024011. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bookworm, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=gtksourceview4 OpenPGP_signature Description: OpenPGP digital signature
Bug#1023365: marked as done (Compatibility problems with wxwidgets3.2)
Your message dated Thu, 05 Jan 2023 06:12:07 + with message-id and subject line Bug#1023365: fixed in slic3r-prusa 2.5.0+dfsg-4 has caused the Debian Bug report #1023365, regarding Compatibility problems with wxwidgets3.2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1023365: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023365 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: prusa-slicer Version: 2.5.0+dfsg-2 Severity: grave Justification: renders package unusable X-Debbugs-Cc: t...@beamnet.de, t...@debian.org, onit...@gmail.com The wrong wxWidgets Version is linked during the build. Normally debian/rules specifies WX_STABLE=1 which should result in the usage of wxWidgets 3.0 which is in stable. However, wx-config always returns wx3.2 which is then used by CMake even if CMakeLists.txt is changed to especially require wxWidgets 3.0 and wx-config options set to --version=3.0. As already stated in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022234 and https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020702 upstream does not have wxWidgets 3.2 support yet. I verified, the package is usable if linked against wxWidgets 3.0 by setting my wx-config alternative to 3.0 (update-alternatives). BR Jan -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (500, 'testing'), (100, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.0.0-2-amd64 (SMP w/24 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages prusa-slicer depends on: ii fonts-noto-hinted 20201225-1 ii libboost-chrono1.74.0 1.74.0-17 ii libboost-filesystem1.74.0 1.74.0-17 ii libboost-iostreams1.74.0 1.74.0-17 ii libboost-locale1.74.0 1.74.0-17 ii libboost-log1.74.0 1.74.0-17 ii libboost-regex1.74.0 [libboost-regex1.74.0-icu71] 1.74.0-17 ii libboost-thread1.74.0 1.74.0-17 ii libc6 2.35-4 ii libcurl3-gnutls 7.85.0-1 ii libdbus-1-3 1.14.4-1 ii libexpat1 2.5.0-1 ii libgcc-s1 12.2.0-3 ii libgl1 1.5.0-1 ii libglew2.2 2.2.0-4+b1 ii libglib2.0-0 2.74.1-1 ii libgmp10 2:6.2.1+dfsg1-1.1 ii libgtk-3-0 3.24.34-3 ii libimath-3-1-29 3.1.5-1+b1 ii libjpeg62-turbo 1:2.1.2-1+b1 ii libmpfr6 4.1.0-3 ii libnlopt0 2.7.1-4+b2 ii libocct-data-exchange-7.6 7.6.3+dfsg1-5 ii libocct-foundation-7.6 7.6.3+dfsg1-5 ii libocct-modeling-algorithms-7.6 7.6.3+dfsg1-5 ii libocct-modeling-data-7.6 7.6.3+dfsg1-5 ii libocct-ocaf-7.6 7.6.3+dfsg1-5 ii libopenvdb9.1 9.1.0-7+b1 ii libpng16-16 1.6.38-2 ii libstdc++6 12.2.0-3 ii libtbb12 2021.5.0-15 ii libwxbase3.2-0 3.2.1+dfsg-1 ii libwxgtk3.2-0 3.2.1+dfsg-1 prusa-slicer recommends no packages. prusa-slicer suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: slic3r-prusa Source-Version: 2.5.0+dfsg-4 Done: Chow Loong Jin We believe that the bug you reported is fixed in the latest version of slic3r-prusa, 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 1023...@bugs.debian.org, and the maintainer will reopen the bug
Bug#1025827: marked as done (slic3r-prusa: FTBFS on armel mipsel powerpc riscv64 sh4 m68k)
Your message dated Thu, 05 Jan 2023 06:12:08 + with message-id and subject line Bug#1025827: fixed in slic3r-prusa 2.5.0+dfsg-4 has caused the Debian Bug report #1025827, regarding slic3r-prusa: FTBFS on armel mipsel powerpc riscv64 sh4 m68k 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.) -- 1025827: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025827 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: slic3r-prusa Version: 2.5.0+dfsg-3 Severity: important Tags: ftbfs, patch User: debian-ri...@lists.debian.org Usertags: riscv64 X-Debbugs-Cc: debian-ri...@lists.debian.org Dear Maintainer, The MR[0] has been submitted by bunk one month ago, I'm assuming you haven't noticed it because gitlab will not send notifications from a MR IIRC. Due to fail build on armel & mipsel, this will block the package to testing I think. So please consider to merge the MR on next upload, thanks. [0]: https://salsa.debian.org/3dprinting-team/slic3r-prusa/-/merge_requests/3 -- Regards, -- Bo YU signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: slic3r-prusa Source-Version: 2.5.0+dfsg-4 Done: Chow Loong Jin We believe that the bug you reported is fixed in the latest version of slic3r-prusa, 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 1025...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Chow Loong Jin (supplier of updated slic3r-prusa 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, 05 Jan 2023 13:42:45 +0800 Source: slic3r-prusa Built-For-Profiles: noudeb Architecture: source Version: 2.5.0+dfsg-4 Distribution: unstable Urgency: medium Maintainer: Debian 3-D Printing Packages <3dprinter-gene...@lists.alioth.debian.org> Changed-By: Chow Loong Jin Closes: 1023365 1025827 Changes: slic3r-prusa (2.5.0+dfsg-4) unstable; urgency=medium . [ Adrian Bunk ] * [b4f4711] Link with libatomic on architectures that need it (Closes: #1025827) . [ Chow Loong Jin ] * Rebuild against updated wxgtk3.2 for GLEW fixes (Closes: #1023365) Checksums-Sha1: 1553a57c8f3abca3e248662608bf29f119e59e20 2573 slic3r-prusa_2.5.0+dfsg-4.dsc 82848437e29bba1e77e55563cb842a3d8fe321aa 47676 slic3r-prusa_2.5.0+dfsg-4.debian.tar.xz df15287441452f915aa1edf87e663c0a2b220ad1 17539 slic3r-prusa_2.5.0+dfsg-4_source.buildinfo Checksums-Sha256: 572f4bd399bc7b3400fd690547861ce427e9bc8fbd57ccbb8bc44e58b2de0688 2573 slic3r-prusa_2.5.0+dfsg-4.dsc fa089896fb3845515e1a075b163274344375283d2cbde800a8e857b7b35cc4c8 47676 slic3r-prusa_2.5.0+dfsg-4.debian.tar.xz dac33e8672e2cf6ab79d34885098c64c945a68d5f22adb791407474a2dac90da 17539 slic3r-prusa_2.5.0+dfsg-4_source.buildinfo Files: e2d88af3e148b346226ed6c70e233d8b 2573 misc optional slic3r-prusa_2.5.0+dfsg-4.dsc 5e7684b0324fc243fcb0c628bb3ed3fb 47676 misc optional slic3r-prusa_2.5.0+dfsg-4.debian.tar.xz 2d77e144c5a959178cd9a58da767923b 17539 misc optional slic3r-prusa_2.5.0+dfsg-4_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEEuDQnfs/9/dZ027Q+9UiW1iHUqEFAmO2Y6AACgkQ+9UiW1iH UqEKmg//apvi/R6VAKh2ErtBE1uxIF2OyI23gnfABcDez/yewD8qiqdLObcEXYza HOzFWXaKfN7GfDxchy20vUfyZhdsMKI+n3Je3N8UFbf5xBiv4kTh5zuOsg8OGKWe u/t7guF2wAsjgp8s7qca0PB7EP5Na1Y4Obq+YamAzwL4OCKnuh2KpEty57BNVOLH kRvYU+WhMB5t6uAjxe+C4DBwSR+PwN69vhjA/ADxDGPHzo3njJsvVsrq2ZF9NlYV 2L3SQTQZb4C92Ppq/LSPldI04FwAmbOQaXeajzY6rwFrXQ2a5IkawlV6NbBZQ2EF pKfk9mafhXEQRT0L/ckwZAxr4RYGGF6KuXmBxi1v0KUyqzNlNDUKCJiRKsqW2ZGu JS2tsA+gJE2ir00juq+77Nd2ZcGzZBaIXymaAU/lCIi0Zc32yN4DjYsfmp6e2iJi fW2eFN6d1DlXSKXYt67w52nICJDyIsCvU213kzMl41aOpptYgQGjt6PA7979COGe 868+ojqPr7ov2a9yaZMigc1cc1AXzmsAOzj8I9ypMbpLi0ui4wiF1rvZg+ocRC9w fyOqgmM8PR1LgwvoBpx8GeCaaOH74XtgPLsNYmDofBufiZ20NlhHldwOjUg2q2Jt gUk5hVrWeDE/2l4z5MKRaLq1D6xJkJQRSciJHJS1M+EDEcngti0= =fAG8 -END PGP SIGNATURE End Message ---
Bug#1027759: marked as done (pylint: Missing dependency on python3-tomli for python3 < 3.11)
Your message dated Thu, 5 Jan 2023 00:18:13 -0500 with message-id and subject line Re: Bug#1027759: pylint: Missing dependency on python3-tomli for python3 < 3.11 has caused the Debian Bug report #1027759, regarding pylint: Missing dependency on python3-tomli for python3 < 3.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.) -- 1027759: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027759 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: pylint Version: 2.15.9-1 Severity: serious Hi! It looks like the recent release is missing a dependency on python3-tomli when the python used is not at least 3.11. Seen on test suite failures locally and on the devscripts CI pipelines: https://salsa.debian.org/guillem/devscripts/-/jobs/3733272#L2644 Thanks, Guillem --- End Message --- --- Begin Message --- > Package: pylint > Version: 2.15.9-1 > Severity: serious > > Hi! > > It looks like the recent release is missing a dependency on > python3-tomli when the python used is not at least 3.11. Seen on > test suite failures locally and on the devscripts CI pipelines: > > https://salsa.debian.org/guillem/devscripts/-/jobs/3733272#L2644 this bug is invalid; pylint is a cli tool, not a module, so running it as /usr/bin/python3.10 -m pylint (https://salsa.debian.org/guillem/devscripts/-/jobs/3733272#L2619) in incorrect. call /usr/bin/pylint Regards, -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi Twitter: https://twitter.com/sandrotosi--- End Message ---
Bug#1027954: cppad: binary-all FTBFS
Source: cppad Version: 2023.00.00.0-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=cppad=all=2023.00.00.0-1=1672887350=0 ... dh_installdocs -i -O--buildsystem=cmake dh_installdocs: error: Cannot find (any matches for) "doc.omh" (tried in ., debian/tmp) make: *** [debian/rules:6: binary-indep] Error 25
Bug#1027628: marked as done (snapper: FTBFS: regex_compiler.tcc:179:19: error: expected unqualified-id before ‘=’ token)
Your message dated Thu, 05 Jan 2023 03:35:49 + with message-id and subject line Bug#1027628: fixed in btrfs-progs 6.1.1-1 has caused the Debian Bug report #1027628, regarding snapper: FTBFS: regex_compiler.tcc:179:19: error: expected unqualified-id before ‘=’ token 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.) -- 1027628: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027628 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: snapper Version: 0.10.4-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230101 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /bin/sh ../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I. -I.. > -I/usr/include/libxml2 -Wdate-time -D_FORTIFY_SOURCE=2 > -DCONF_DIR='"/etc/default"' -D_FILE_OFFSET_BITS=64 -g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -std=c++11 -Wall -Wextra -Wformat -Wnon-virtual-dtor > -Wno-unused-parameter -Wsuggest-override -c -o libsnapper_la-MntTable.lo > `test -f 'MntTable.cc' || echo './'`MntTable.cc > libtool: compile: g++ -DHAVE_CONFIG_H -I. -I.. -I/usr/include/libxml2 > -Wdate-time -D_FORTIFY_SOURCE=2 -DCONF_DIR=\"/etc/default\" > -D_FILE_OFFSET_BITS=64 -g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -std=c++11 -Wall > -Wextra -Wformat -Wnon-virtual-dtor -Wno-unused-parameter -Wsuggest-override > -c MntTable.cc -fPIC -DPIC -o .libs/libsnapper_la-MntTable.o > In file included from /usr/include/c++/12/bits/regex_compiler.h:571, > from /usr/include/c++/12/regex:65, > from Btrfs.cc:47: > /usr/include/c++/12/bits/regex_compiler.tcc: In member function ‘bool > std::__detail::_Compiler<_TraitsT>::_M_quantifier()’: > /usr/include/c++/12/bits/regex_compiler.tcc:179:19: error: expected > unqualified-id before ‘=’ token > 179 | auto __init = [this, &__neg]() > | ^ > /usr/include/c++/12/bits/regex_compiler.tcc:187:18: error: expected > primary-expression before ‘)’ token > 187 | __init(); > | ^ > /usr/include/c++/12/bits/regex_compiler.tcc:197:18: error: expected > primary-expression before ‘)’ token > 197 | __init(); > | ^ > /usr/include/c++/12/bits/regex_compiler.tcc:205:18: error: expected > primary-expression before ‘)’ token > 205 | __init(); > | ^ > make[3]: *** [Makefile:768: libsnapper_la-Btrfs.lo] Error 1 The full build log is available from: http://qa-logs.debian.net/2023/01/01/snapper_0.10.4-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230101;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230101=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: btrfs-progs Source-Version: 6.1.1-1 Done: Adam Borowski We believe that the bug you reported is fixed in the latest version of btrfs-progs, 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 1027...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Adam Borowski (supplier of updated btrfs-progs 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, 05 Jan 2023 03:44:03 +0100 Source: btrfs-progs Architecture: source Version: 6.1.1-1 Distribution: unstable Urgency: medium Maintainer: Adam Borowski Changed-By: Adam Borowski Closes: 1027628 1027785 Changes: btrfs-progs
Processed: Re: Bug#1027824: FTBFS: hanging testsuite: build killed after time of inactivity on buildds
Processing control commands: > forwarded -1 https://github.com/vim/vim/issues/11782 Bug #1027824 [src:vim] vim FTBFS on IPV6-only buildds Set Bug forwarded-to-address to 'https://github.com/vim/vim/issues/11782'. -- 1027824: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027824 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1027824: FTBFS: hanging testsuite: build killed after time of inactivity on buildds
Control: forwarded -1 https://github.com/vim/vim/issues/11782 On Tue, Jan 03, 2023 at 10:39:02PM +0200, Adrian Bunk wrote: > On Tue, Jan 03, 2023 at 09:15:03PM +0100, Salvatore Bonaccorso wrote: > > Looking at the older build failures from > > https://buildd.debian.org/status/logs.php?pkg=vim=amd64 it looks > > it was always on x86-conova-01 when it failed. > > The test seems to fail on IPV6-only buildds, I suspect something might > go wrong with the usage of "localhost" in this test without IPV4? Thanks for the hints. That allowed me to debug the issue. I've submitted a bug upstream and sent a PR which resolves the issue in my testing. https://github.com/vim/vim/pull/11783 Cheers, -- James GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
Bug#1027733: libc6: new libc6 breaks GNU Screen handling of some Unicode characters
Hi Aurelien, Axel Beckert wrote: > Aurelien Jarno wrote: > > An alternative is to not try to support all systems and reinvent the > > wheel, and instead assume a POSIX system. > > I'd say on Debian — independent of the actually used kernel — we can > do assume this at least. > > > That way the attached patch can be used. > > Nice patch! Thanks! Hrm, with that patch, autopkgtest fails the test case for #600246, i.e. it seems to reopen the infamous and seemingly non-trivial https://bugs.debian.org/600246 — not sure why though. (Wonder if Thorsten's patch works better for #600246 than the current one. Or maybe my way of testing is borked?) At least no more upload this night. Need to dig deeper. Regards, Axel -- ,''`. | Axel Beckert , https://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
Bug#1023284: libevent: FTBFS with glibc 2.36
Hello all, I'm forwarding my questions and thoughts about this patch. Le 2023-01-04 à 11 h 39, Shengjing Zhu a écrit : So Just make evutil_secure_rng_add_bytes noop with glibc's implemtation of arc4random. Please see following patch. In the libevent repo, azat mentions that nooping evutil_secure_rng_add_bytes is not a good thing to do [1] but on the other hand, other implementation have applied this kind of patch, like oracle mentioned above. I'm not pretending I know more, but I'd like to make sure this patch won't silently remove a core functionality in some packages, leading to random number generator being less random. Also, the libevent transition with glibc made by ubuntu in october went fine apparently, just a couple of build had an error [2] Again, I'm not trying to force one solution or another, but I question what solution is the best considering the little time we have until freeze. /Nicolas [1] https://github.com/libevent/libevent/issues/615#issuecomment-421182890 [2] https://bugs.launchpad.net/ubuntu/+source/libevent/+bug/1990941
Bug#1022372: marked as done (python-cattrs: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.10 returned exit code 13)
Your message dated Wed, 4 Jan 2023 20:32:30 -0500
with message-id
and subject line Re: python-cattrs: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p 3.10 returned exit code 13
has caused the Debian Bug report #1022372,
regarding python-cattrs: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p 3.10 returned exit code 13
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.)
--
1022372: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022372
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-cattrs
Version: 1.10.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221023 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> cd docs && \
> PYTHONPATH=/<>/.pybuild/cpython3_3.10_cattr/build
> http_proxy='http://127.0.0.1:9/' https_proxy='https://127.0.0.1:9/' \
> sphinx-build -N -E -T -b html . /<>/.pybuild/docs/html/
> Running Sphinx v4.5.0
> making output directory... done
> WARNING: html_static_path entry '_static' does not exist
> building [mo]: targets for 0 po files that are out of date
> building [html]: targets for 16 source files that are out of date
> updating environment: [new config] 16 added, 0 changed, 0 removed
> reading sources... [ 6%] benchmarking
> reading sources... [ 12%] cattr
> reading sources... [ 18%] cattr.preconf
> reading sources... [ 25%] contributing
> reading sources... [ 31%] converters
> reading sources... [ 37%] customizing
> reading sources... [ 43%] history
> reading sources... [ 50%] index
> reading sources... [ 56%] installation
> reading sources... [ 62%] modules
> reading sources... [ 68%] preconf
> reading sources... [ 75%] readme
> reading sources... [ 81%] structuring
> reading sources... [ 87%] unions
> reading sources... [ 93%] unstructuring
> reading sources... [100%] usage
>
> /<>/docs/cattr.preconf.rst:5: WARNING: duplicate label
> submodules, other instance in /<>/docs/cattr.rst
> /<>/docs/cattr.preconf.rst:64: WARNING: duplicate label module
> contents, other instance in /<>/docs/cattr.rst
> /<>/docs/unstructuring.rst:94: WARNING: duplicate label
> ``typing.annotated``, other instance in /<>/docs/structuring.rst
> /<>/docs/unstructuring.rst:100: WARNING: duplicate label
> ``attrs`` classes and dataclasses, other instance in
> /<>/docs/structuring.rst
> looking for now-outdated files... none found
> pickling environment... done
> checking consistency... /<>/docs/modules.rst: WARNING: document
> isn't included in any toctree
> done
> preparing documents... done
> writing output... [ 6%] benchmarking
> writing output... [ 12%] cattr
> writing output... [ 18%] cattr.preconf
> writing output... [ 25%] contributing
> writing output... [ 31%] converters
> writing output... [ 37%] customizing
> writing output... [ 43%] history
> writing output... [ 50%] index
> writing output... [ 56%] installation
> writing output... [ 62%] modules
> writing output... [ 68%] preconf
> writing output... [ 75%] readme
> writing output... [ 81%] structuring
> writing output... [ 87%] unions
> writing output... [ 93%] unstructuring
> writing output... [100%] usage
>
> /<>/src/cattr/gen.py:docstring of
> cattr.gen.make_dict_structure_fn:: WARNING: more than one target found for
> cross-reference 'Converter': cattr.converters.Converter, cattr.Converter
> /<>/docs/unstructuring.rst:14: WARNING: more than one target
> found for cross-reference 'Converter.unstructure':
> cattr.converters.Converter.unstructure, cattr.Converter.unstructure
> /<>/docs/unstructuring.rst:102: WARNING: more than one target
> found for cross-reference 'Converter': cattr.converters.Converter,
> cattr.Converter
> /<>/docs/unstructuring.rst:125: WARNING: more than one target
> found for cross-reference 'Converter.unstructure_attrs_asdict':
> cattr.converters.Converter.unstructure_attrs_asdict,
> cattr.Converter.unstructure_attrs_asdict
> /<>/docs/unstructuring.rst:125: WARNING: more than one target
> found for cross-reference 'Converter.unstructure_attrs_astuple':
> cattr.converters.Converter.unstructure_attrs_astuple,
> cattr.Converter.unstructure_attrs_astuple
> /<>/docs/usage.rst:29: WARNING: more than one target found for
> cross-reference 'Converter': cattr.converters.Converter, cattr.Converter
> generating indices... genindex py-modindex done
> highlighting module code... [ 7%] cattr.converters
> highlighting module code... [ 15%]
Bug#1027952: pcre2 causes crashes in link-grammar
Package: libpcre2-8-0 Version: 10.42-1 Severity: serious Tags: ftbfs Control: affects -1 src:link-grammar https://tracker.debian.org/pkg/pcre2 Issues preventing migration: ∙ ∙ autopkgtest for link-grammar/5.11.0~dfsg-1: amd64: Pass, arm64: Regression ♻ (reference ♻), armel: Regression ♻ (reference ♻), armhf: Regression ♻ (reference ♻), i386: Pass, ppc64el: Regression ♻ (reference ♻), s390x: Pass https://buildd.debian.org/status/logs.php?pkg=link-grammar=5.11.0~dfsg-1%2Bb1 ... make check-TESTS make[4]: Entering directory '/<>/tests' make[5]: Entering directory '/<>/tests' PASS: mem-leak PASS: multi-java ../test-driver: line 112: 3264343 Segmentation fault "$@" >> "$log_file" 2>&1 FAIL: multi-thread PASS: multi-dict PASS: dict-reopen === link-grammar 5.11.0: tests/test-suite.log === # TOTAL: 5 # PASS: 4 # SKIP: 0 # XFAIL: 0 # FAIL: 1 # XPASS: 0 # ERROR: 0 .. contents:: :depth: 2 FAIL: multi-thread == FAIL multi-thread (exit status: 139) Testsuite summary for link-grammar 5.11.0 # TOTAL: 5 # PASS: 4 # SKIP: 0 # XFAIL: 0 # FAIL: 1 # XPASS: 0 # ERROR: 0 See tests/test-suite.log Please report to https://github.com/opencog/link-grammar make[5]: *** [Makefile:806: test-suite.log] Error 1 A backtrace from a coredump of a local build of link-grammar also suggests that pcre might be the problem: Core was generated by `/tmp/link-grammar-5.11.0~dfsg/tests/.libs/multi-thread'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x7f46a39011b1 in ?? () from /lib/x86_64-linux-gnu/libpcre2-8.so.0 [Current thread is 1 (Thread 0x7f469e5546c0 (LWP 17344))] (gdb) bt #0 0x7f46a39011b1 in ?? () from /lib/x86_64-linux-gnu/libpcre2-8.so.0 #1 0x7f46a38ebb85 in ?? () from /lib/x86_64-linux-gnu/libpcre2-8.so.0 #2 0x7f46a38fa10f in pcre2_match_8 () from /lib/x86_64-linux-gnu/libpcre2-8.so.0 #3 0x7f46a3da9a86 in reg_match (rn=0x562bf27ace00, s=0x7f467b5b2100 "Bill") at dict-common/regex-morph.c:219 #4 match_regex (rn=0x562bf27ace00, s=s@entry=0x7f467b5b2100 "Bill") at dict-common/regex-morph.c:405 #5 0x7f46a3ddff63 in regex_guess (gword=0x7f467b59b3b0, word=, dict=0x562bf27a8a00) at tokenize/tokenize.c:413 #6 separate_word (sent=sent@entry=0x7f467b5b59e0, unsplit_word=unsplit_word@entry=0x7f467b59b3b0, opts=opts@entry=0x562bf547ae60) at tokenize/tokenize.c:2709 #7 0x7f46a3de155a in separate_sentence (sent=sent@entry=0x7f467b5b59e0, opts=opts@entry=0x562bf547ae60) at tokenize/tokenize.c:3116 #8 0x7f46a3d9b1ec in sentence_split (sent=0x7f467b5b59e0, opts=0x562bf547ae60) at ./link-grammar/api.c:494 #9 0x562bf0419670 in parse_one_sent (dict=, opts=0x562bf547ae60, sent_str=) at ./tests/multi-thread.cc:34 #10 0x562bf04199aa in parse_sents (dict=0x562bf27a8a00, opts=0x562bf547ae60, thread_id=, niter=500) at ./tests/multi-thread.cc:119 #11 0x7f46a3c044a3 in ?? () from /lib/x86_64-linux-gnu/libstdc++.so.6 #12 0x7f46a39b7fd4 in start_thread (arg=) at ./nptl/pthread_create.c:442 #13 0x7f46a3a378d0 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:100 (gdb)
Processed: pcre2 causes crashes in link-grammar
Processing control commands: > affects -1 src:link-grammar Bug #1027952 [libpcre2-8-0] pcre2 causes crashes in link-grammar Added indication that 1027952 affects src:link-grammar -- 1027952: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027952 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1027733: libc6: new libc6 breaks GNU Screen handling of some Unicode characters
Hi Aurelien, Aurelien Jarno wrote: > An alternative is to not try to support all systems and reinvent the > wheel, and instead assume a POSIX system. I'd say on Debian — independent of the actually used kernel — we can do assume this at least. > That way the attached patch can be used. Nice patch! Thanks! Regards, Axel -- ,''`. | Axel Beckert , https://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
Processed: affects 1027951
Processing commands for cont...@bugs.debian.org: > # Lintian build-devs currently can't be satisfied either due to this > affects 1027951 + src:lintian Bug #1027951 [python-dev-is-python3] python-dev-is-python3: Uninstallable as it depends on python-is-python3 which "Breaks: python-dev-is-python3 (<< 12)" Added indication that 1027951 affects src:lintian > thanks Stopping processing here. Please contact me if you need assistance. -- 1027951: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027951 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1026741: marked as done (python-xsdata: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.11 3.10" returned exit code 13)
Your message dated Thu, 05 Jan 2023 00:38:22 +
with message-id
and subject line Bug#1026741: fixed in python-xsdata 22.12-1
has caused the Debian Bug report #1026741,
regarding python-xsdata: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p "3.11 3.10" returned exit code 13
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.)
--
1026741: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026741
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-xsdata
Version: 22.11-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221220 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_test
> I: pybuild base:240: cd /<>/.pybuild/cpython3_3.11_xsdata/build;
> python3.11 -m pytest tests
> [1m= test session starts
> ==[0m
> platform linux -- Python 3.11.1, pytest-7.2.0, pluggy-1.0.0+repack
> benchmark: 3.2.2 (defaults: timer=time.perf_counter disable_gc=False
> min_rounds=5 min_time=0.05 max_time=1.0 calibration_precision=10
> warmup=False warmup_iterations=10)
> rootdir: /<>/.pybuild/cpython3_3.11_xsdata/build, configfile:
> setup.cfg
> plugins: benchmark-3.2.2
> collected 911 items
>
> tests/test_cli.py
> [32m.[0m[32m.[0m[32m.[0m[32m.[0m[32m.[0m[32m.[0m[32m.[0m[32m.[0m[32m.[0m[32m
> [ 0%][0m
> tests/codegen/test_analyzer.py [32m.[0m[32m.[0m[32m.[0m[32m
>[ 1%][0m
> tests/codegen/test_container.py
> [32m.[0m[32m.[0m[32m.[0m[32m.[0m[32m.[0m[32m.[0m[32m.[0m[32m
>[ 2%][0m
> tests/codegen/test_resolver.py
> [32m.[0m[32m.[0m[32m.[0m[32m.[0m[32m.[0m[32m.[0m[32m.[0m[32m.[0m[32m.[0m[32m.[0m[32m.[0m[32m.[0m[32m
> [ 3%][0m
> tests/codegen/test_transformer.py
> [32m.[0m[32m.[0m[32m.[0m[32m.[0m[32m.[0m[32m.[0m[32m.[0m[32m.[0m[32m.[0m[32m.[0m[32m.[0m[32m.[0m[32m.[0m[32m.[0m[32m.[0m[32m.[0m[32m.[0m[32m.[0m[32m.[0m[32m.[0m[32m.[0m[32m
> [ 5%][0m
> tests/codegen/test_utils.py
> [32m.[0m[32m.[0m[32m.[0m[32m.[0m[32m.[0m[32m.[0m[32m.[0m[32m.[0m[32m.[0m[32m.[0m[32m.[0m[32m.[0m[32m.[0m[32m.[0m[32m.[0m[32m.[0m[32m.[0m[32m.[0m[32m.[0m[32m
> [ 7%][0m
> tests/codegen/test_validator.py
> [32m.[0m[32m.[0m[32m.[0m[32m.[0m[32m.[0m[32m.[0m[32m.[0m[32m.[0m[32m
> [ 8%][0m
> tests/codegen/test_writer.py [32m.[0m[32m.[0m[32m.[0m[32m
>[ 9%][0m
> tests/codegen/handlers/test_add_attribute_substitutions.py
> [32m.[0m[32m.[0m[32m.[0m[32m.[0m[32m [ 9%][0m
> tests/codegen/handlers/test_create_compound_fields.py
> [32m.[0m[32m.[0m[32m.[0m[32m.[0m[32m.[0m[32m.[0m[32m
> [ 10%][0m
> tests/codegen/handlers/test_designate_class_packages.py
> [32m.[0m[32m.[0m[32m.[0m[32m.[0m[32m.[0m[32m.[0m[32m.[0m[32m
>[ 10%][0m
> tests/codegen/handlers/test_filter_classes.py
> [32m.[0m[32m.[0m[32m.[0m[32m.[0m[32m [ 11%][0m
> tests/codegen/handlers/test_flatten_attribute_groups.py
> [32m.[0m[32m.[0m[32m.[0m[32m.[0m[32m.[0m[32m[ 11%][0m
> tests/codegen/handlers/test_flatten_class_extensions.py
> [32m.[0m[32m.[0m[32m.[0m[32m.[0m[32m.[0m[32m.[0m[32m.[0m[32m.[0m[32m.[0m[32m.[0m[32m.[0m[32m.[0m[32m.[0m[32m.[0m[32m.[0m[32m.[0m[32m
> [ 13%]
> [0m[32m.[0m[32m.[0m[32m.[0m[32m.[0m[32m.[0m[32m.[0m[32m.[0m[32m.[0m[32m.[0m[32m.[0m[32m.[0m[32m
> [ 14%][0m
> tests/codegen/handlers/test_merge_attributes.py [32m.[0m[32m
> [ 14%][0m
> tests/codegen/handlers/test_process_attributes_types.py
> [32m.[0m[32m.[0m[32m.[0m[32m.[0m[32m.[0m[32m.[0m[32m.[0m[32m.[0m[32m.[0m[32m.[0m[32m.[0m[32m.[0m[32m.[0m[32m.[0m[32m.[0m[32m.[0m[32m
> [ 16%]
> [0m[32m.[0m[32m.[0m[32m.[0m[32m.[0m[32m.[0m[32m.[0m[32m.[0m[32m.[0m[32m
> [ 17%][0m
>
Bug#1027951: python-dev-is-python3: Uninstallable as it depends on python-is-python3 which "Breaks: python-dev-is-python3 (<< 12)"
Package: python-dev-is-python3 Version: 3.11.1-2 Severity: serious Hi, python-dev-is-python3 is uninstallable because of these never satisfiable package relations: Package: python-dev-is-python3 Source: what-is-python (12) Version: 3.11.1-2 Depends: python-is-python3 (= 3.11.1-2), […] ^^ Package: python-is-python3 Source: what-is-python (12) Version: 3.11.1-2 Installed-Size: 15 Maintainer: Matthias Klose Architecture: all Replaces: […], python-dev-is-python3 (<< 12), […] Breaks: […], python-dev-is-python3 (<< 12), […] ^^ See also https://qa.debian.org/dose/debcheck/unstable_main/latest/packages/python-dev-is-python3.html#ff0c7854f66c25b67d96e10ba73b0ca9 https://piuparts.debian.org/sid/fail/python-dev-is-python3_3.11.1-2.log Reason is probably that for the << relation in Breaks and Replaces of python-is-python3 the source package version is used despite the (different) binary package version should have been used. -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (990, 'unstable'), (600, 'testing'), (500, 'unstable-debug'), (500, 'buildd-unstable'), (110, 'experimental'), (1, 'experimental-debug'), (1, 'buildd-experimental') merged-usr: no Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.18.0-4-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_WARN Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) LSM: AppArmor: enabled
Processed: fixed 1027130 in clamav/1.0.0+dfsg-1
Processing commands for cont...@bugs.debian.org:
> fixed 1027130 clamav/1.0.0+dfsg-1
Bug #1027130 {Done: Scott Kitterman } [libclamav9]
libclamav9: LibClamAV Error: Can't verify database integrity
Marked as fixed in versions clamav/1.0.0+dfsg-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1027130: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027130
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: raising severity
Processing commands for cont...@bugs.debian.org: > severity 1027401 serious Bug #1027401 [src:shaarli] shaarli: Re-building package results in frontend missing icons Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 1027401: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027401 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1027950: pyside2 FTBFS with Python 3.11 as default version
Source: pyside2
Version: 5.15.2-2.3
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/fetch.php?pkg=pyside2=amd64=5.15.2-2.3%2Bb4=1672846001=0
...
debian/rules clean
dh clean --with python3,sphinxdoc --buildsystem=pybuild
dh_auto_clean -O--buildsystem=pybuild
I: pybuild base:240: python3.11 setup.py clean
Unsupported python version detected. Only these python versions are supported:
[(2, 7), (3, 5), (3, 6), (3, 7), (3, 8), (3, 9), (3, 10)]
E: pybuild pybuild:388: clean: plugin distutils failed with: exit code=1:
python3.11 setup.py clean
dh_auto_clean: error: pybuild --clean -i python{version} -p 3.11 returned exit
code 13
make: *** [debian/rules:30: clean] Error 25
Processed: Bug#1026741 marked as pending in python-xsdata
Processing control commands:
> tag -1 pending
Bug #1026741 [src:python-xsdata] python-xsdata: FTBFS: dh_auto_test: error:
pybuild --test --test-pytest -i python{version} -p "3.11 3.10" returned exit
code 13
Added tag(s) pending.
--
1026741: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026741
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1026741: marked as pending in python-xsdata
Control: tag -1 pending Hello, Bug #1026741 in python-xsdata reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/packages/python-xsdata/-/commit/4005e64c1632fa9ddcf61b1c2e4c288e96e2f3ff New upstream release (Closes: #1026741). (this message was generated automatically) -- Greetings https://bugs.debian.org/1026741
Bug#1027948: marked as done (clamav: Cannot fulfill the build build dependencies on mipsel/mips64el)
Your message dated Thu, 05 Jan 2023 00:05:26 + with message-id and subject line Bug#1027948: fixed in clamav 1.0.0+dfsg-4 has caused the Debian Bug report #1027948, regarding clamav: Cannot fulfill the build build dependencies on mipsel/mips64el 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.) -- 1027948: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027948 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: clamav Version: 1.0.0+dfsg-2 Severity: serious Tags: ftbfs https://buildd.debian.org/status/package.php?p=clamav=sid Dependency installability problem for clamav on mips64el: clamav build-depends on: - rust-lldb:mips64el rust-lldb depends on missing: - lldb-14:mips64el Dependency installability problem for clamav on mipsel: clamav build-depends on: - rust-lldb:mipsel rust-lldb depends on missing: - lldb-14:mipsel Is there actually a reason why the build dependency on rust-lldb is required at all? CMakeLists.txt calls find_package(Rust REQUIRED), which is implemented in the generic cmake/FindRust.cmake (not written for clamav). cmake/FindRust.cmake does check for tools like rust-lldb, but rust-lldb does not seem to be used anywhere. Test builds without rust-lldb succeeded for me on amd64 and mipsel, with no code changes detected in the amd64 build by diffoscope. --- End Message --- --- Begin Message --- Source: clamav Source-Version: 1.0.0+dfsg-4 Done: Scott Kitterman We believe that the bug you reported is fixed in the latest version of clamav, 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 1027...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Scott Kitterman (supplier of updated clamav 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, 04 Jan 2023 18:32:47 -0500 Source: clamav Architecture: source Version: 1.0.0+dfsg-4 Distribution: unstable Urgency: medium Maintainer: ClamAV Team Changed-By: Scott Kitterman Closes: 1027948 Changes: clamav (1.0.0+dfsg-4) unstable; urgency=medium . * Drop unneeded build-depends on rust-lldb (Closes: #1027948). Checksums-Sha1: eeccf2fa88dce6b5b4cbd8a28596879b1db35ff0 3003 clamav_1.0.0+dfsg-4.dsc e01269cf4cbeb85b15ab18b7b2c6247499870dff 223492 clamav_1.0.0+dfsg-4.debian.tar.xz f4e0730d1d9cb2942c413f1ea4eb820e0fe97395 7643 clamav_1.0.0+dfsg-4_source.buildinfo Checksums-Sha256: e0c6eee4153f7bb6f8d5f425f45ab8d2fdcace56e41517b7772d50948ffcf40c 3003 clamav_1.0.0+dfsg-4.dsc 3279b05609c730f8f9a0c696ed24d8326471e5ecc44f2ef978a6cb6d4c3c15fc 223492 clamav_1.0.0+dfsg-4.debian.tar.xz 0d6b8358e090108a2b2da168e3890e406729918423627c8b898965fc2113305b 7643 clamav_1.0.0+dfsg-4_source.buildinfo Files: 80d4c085698fa3d0a72e9a27d4c5c9db 3003 utils optional clamav_1.0.0+dfsg-4.dsc 30d7502b928a1c4d7d84ef2db21eadcd 223492 utils optional clamav_1.0.0+dfsg-4.debian.tar.xz 98a963a9d238c4823ce64ba81691ed45 7643 utils optional clamav_1.0.0+dfsg-4_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE53Kb/76FQA/u7iOxeNfe+5rVmvEFAmO2EVIACgkQeNfe+5rV mvFDbw/8DFhM+IMdDA8FaVTI/lhqCZ7u3kgsEDDZwwGSvRKej+bhs/Zd9Uje/9ND p0wKBFcMfPryoAakZeicI4lrQ0Q0sLdFKDy+4tAiJralyuIyGYV6WCxOuN8bZIcm oGzDlW+nXo9UCbFRLkRCQ2Q1nZgb46cZm+nXI1WSNmjO5y98XUd9/h7wpdfUTbv8 JTeD2eB4zV4EWRjMXHc3PRuuH57aq3C2uDvz4k8MsloANnvuuq3VhBW5RdrZrYf2 hXwtJgL37MA7Q1j9bReZgYPiVIvE1cFDb8eRzBhsflyZ/YdbM2soS3H1ChMIBvkt U5VbqZR8pBMJmgH69NiicFF5YJ/hRTIH4Sx6CwCgvHAwzcu+oF5nnD3vaE64mwoB +xat91laoeGh2IFoBQ/nQt+ZnyL4yoBzQQfINZfiYiCeNDbMHxOXX+t9dZKEV9E5 AAGOgwonyOG/mzLVhS9X6AiQejHuWaXQ2hjYZ4Tw2cG+O/Cr5vZBafWeKqqMzb9L jH9HpXtqzUHoCoblXQ4rwqFMIq1E7Uv07Q+O7oASv76p1Xbb6fs5BRa3vVljSJEk 7isr67UCNy2FzkvjQWmiLEH3imYd/EZpx3rpGGTXxu6OxOY58tYlkvxXq8BmIZzT JM4zltORvqXYhBXnwSdbbihovV55bjSqpbvkHxR86h+t6jE1u10= =zhem -END PGP SIGNATURE End Message ---
Bug#1027948: [Pkg-clamav-devel] Bug#1027948: clamav: Cannot fulfill the build build dependencies on mipsel/mips64el
On Wednesday, January 4, 2023 6:35:52 PM EST Adrian Bunk wrote: > Source: clamav > Version: 1.0.0+dfsg-2 > Severity: serious > Tags: ftbfs > > https://buildd.debian.org/status/package.php?p=clamav=sid > > Dependency installability problem for clamav on mips64el: > clamav build-depends on: > - rust-lldb:mips64el > rust-lldb depends on missing: > - lldb-14:mips64el > > Dependency installability problem for clamav on mipsel: > > clamav build-depends on: > - rust-lldb:mipsel > rust-lldb depends on missing: > - lldb-14:mipsel > > > Is there actually a reason why the build dependency on rust-lldb > is required at all? > > CMakeLists.txt calls find_package(Rust REQUIRED), which is implemented > in the generic cmake/FindRust.cmake (not written for clamav). > > cmake/FindRust.cmake does check for tools like rust-lldb, > but rust-lldb does not seem to be used anywhere. > > Test builds without rust-lldb succeeded for me on amd64 and mipsel, > with no code changes detected in the amd64 build by diffoscope. Same here. I was about to upload a change to drop it when I say the bug. Scott K signature.asc Description: This is a digitally signed message part.
Bug#1026678: marked as done (flit: FTBFS: mv: cannot stat '/<>/.pybuild/cpython3_3.10/build/scripts-3.10': No such file or directory)
Your message dated Wed, 04 Jan 2023 23:35:30 +
with message-id
and subject line Bug#1026678: fixed in flit 3.8.0-3
has caused the Debian Bug report #1026678,
regarding flit: FTBFS: mv: cannot stat
'/<>/.pybuild/cpython3_3.10/build/scripts-3.10': No such file or
directory
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1026678: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026678
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: flit
Version: 3.8.0-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221220 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> # Workaround #1018952: pybuild doesn't make it easy to built multiple packages
> PYBUILD_BEFORE_BUILD="mv {build_dir}/scripts-{version}
> {build_dir}/flit-scripts-{version} && rm {build_dir}/../*.whl" \
> PYBUILD_AFTER_BUILD="mv {build_dir}/flit-scripts-{version}
> {build_dir}/scripts-{version}" \
> pybuild --build -d flit_core
> I: pybuild pybuild:307: mv
> /<>/.pybuild/cpython3_3.11/build/scripts-3.11
> /<>/.pybuild/cpython3_3.11/build/flit-scripts-3.11 && rm
> /<>/.pybuild/cpython3_3.11/build/../*.whl
> mv: cannot stat '/<>/.pybuild/cpython3_3.11/build/scripts-3.11':
> No such file or directory
> E: pybuild pybuild:386: build: plugin pyproject failed with: exit code=1: mv
> /<>/.pybuild/cpython3_3.11/build/scripts-3.11
> /<>/.pybuild/cpython3_3.11/build/flit-scripts-3.11 && rm
> /<>/.pybuild/cpython3_3.11/build/../*.whl
> I: pybuild pybuild:307: mv
> /<>/.pybuild/cpython3_3.10/build/scripts-3.10
> /<>/.pybuild/cpython3_3.10/build/flit-scripts-3.10 && rm
> /<>/.pybuild/cpython3_3.10/build/../*.whl
> mv: cannot stat '/<>/.pybuild/cpython3_3.10/build/scripts-3.10':
> No such file or directory
> E: pybuild pybuild:386: build: plugin pyproject failed with: exit code=1: mv
> /<>/.pybuild/cpython3_3.10/build/scripts-3.10
> /<>/.pybuild/cpython3_3.10/build/flit-scripts-3.10 && rm
> /<>/.pybuild/cpython3_3.10/build/../*.whl
> make[1]: *** [debian/rules:30: execute_after_dh_auto_build] Error 13
The full build log is available from:
http://qa-logs.debian.net/2022/12/20/flit_3.8.0-2_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20221220;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20221220=lu...@debian.org=1=1=1=1#results
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: flit
Source-Version: 3.8.0-3
Done: Scott Kitterman
We believe that the bug you reported is fixed in the latest version of
flit, 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 1026...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Scott Kitterman (supplier of updated flit 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, 04 Jan 2023 18:12:03 -0500
Source: flit
Architecture: source
Version: 3.8.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team
Changed-By: Scott Kitterman
Closes: 1026678
Changes:
flit (3.8.0-3) unstable; urgency=medium
.
[ Stefano Rivera ]
* Replace the hacks in debian/rules to support multiple wheels with --name.
(Closes: #1026678)
.
[ Scott Kitterman ]
* Bump standards-version to 4.6.2 without further change
Checksums-Sha1:
2eecd6cb01f395d679b0fc92f9dcd96f87fb8892 2224 flit_3.8.0-3.dsc
ec58cd7af35ed24ac18862dc25b099c8592e26ff 12648 flit_3.8.0-3.debian.tar.xz
94e3a653472b77c50ace6d0820e7b4f86367738f 6389 flit_3.8.0-3_source.buildinfo
Bug#1027948: clamav: Cannot fulfill the build build dependencies on mipsel/mips64el
Source: clamav Version: 1.0.0+dfsg-2 Severity: serious Tags: ftbfs https://buildd.debian.org/status/package.php?p=clamav=sid Dependency installability problem for clamav on mips64el: clamav build-depends on: - rust-lldb:mips64el rust-lldb depends on missing: - lldb-14:mips64el Dependency installability problem for clamav on mipsel: clamav build-depends on: - rust-lldb:mipsel rust-lldb depends on missing: - lldb-14:mipsel Is there actually a reason why the build dependency on rust-lldb is required at all? CMakeLists.txt calls find_package(Rust REQUIRED), which is implemented in the generic cmake/FindRust.cmake (not written for clamav). cmake/FindRust.cmake does check for tools like rust-lldb, but rust-lldb does not seem to be used anywhere. Test builds without rust-lldb succeeded for me on amd64 and mipsel, with no code changes detected in the amd64 build by diffoscope.
Bug#1027734: prometheus-blackbox-exporter: FTBFS: inconsistent test failures
I think I just found the smoking gun, so to speak.
In the reproducible builds log, I spotted this:
=== RUN TestDNSProtocol
dns_test.go:490: "localhost" doesn't resolve to ::1.
--- SKIP: TestDNSProtocol (0.00s)
This is due to this check in TestDNSProtocol:
_, err := net.ResolveIPAddr("ip6", "localhost")
if err != nil {
t.Skip("\"localhost\" doesn't resolve to ::1.")
}
The failure of "localhost" resolving to ::1 (as well as 127.0.0.1)
suggests that the reproducible builds environment does not conform to a
typical Debian environment (where localhost resolves to both 127.0.0.1
_and_ ::1), and will cause the GRPC tests to fail, since the upstream
developer sets "IPProtocolFallback: false", and blackbox_exporter's
resolver defaults to ip6[1].
I will prepare a patch to set "IPProtocolFallback: true" in the GRPC
tests, as it is in all other tests in the repo (and as per the
documented runtime config defaults).
[1]:
https://github.com/prometheus/blackbox_exporter/issues/969#issuecomment-1370452161
OpenPGP_signature
Description: OpenPGP digital signature
Bug#1027936: marked as done (brian FTBFS with Python 3.11 as default version)
Your message dated Wed, 04 Jan 2023 23:20:19 + with message-id and subject line Bug#1027936: fixed in brian 2.5.1-2 has caused the Debian Bug report #1027936, regarding brian FTBFS with Python 3.11 as default version 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.) -- 1027936: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027936 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: brian Version: 2.5.1-1 Severity: serious https://buildd.debian.org/status/fetch.php?pkg=brian=amd64=2.5.1-1%2Bb1=1672837036=0 ... Configuration error: There is a programmable error in your configuration file: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/sphinx/config.py", line 350, in eval_config_file exec(code, namespace) File "/<>/docs_sphinx/conf.py", line 71, in generate_examples.main(root_dir, target_dir) File "/<>/debian/tmp/usr/lib/python3.11/dist-packages/brian2/sphinxext/generate_examples.py", line 72, in main with codecs.open(fname, 'rU', encoding='utf-8') as f: ^^ File "", line 906, in open ValueError: invalid mode: 'rUb' ... Documenting 89 examples make[1]: *** [debian/rules:44: override_dh_auto_install] Error 2 --- End Message --- --- Begin Message --- Source: brian Source-Version: 2.5.1-2 Done: Étienne Mollier We believe that the bug you reported is fixed in the latest version of brian, 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 1027...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Étienne Mollier (supplier of updated brian 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, 04 Jan 2023 22:51:57 +0100 Source: brian Architecture: source Version: 2.5.1-2 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Étienne Mollier Closes: 1027936 Changes: brian (2.5.1-2) unstable; urgency=medium . * python3.11.patch: add; fix ftbfs with python3.11. (Closes: #1027936) * d/copyright: bump copyright year. * privacy.patch: mark forward not-needed. * sphinx.patch: mark forward not-needed. * d/control: declare compliance to standards version 4.6.2. Checksums-Sha1: 0596875262f857533cd5c01fbe631fc5adb1dafb 2614 brian_2.5.1-2.dsc 31b4b0570579aeee28c356ae687136678000aceb 19048 brian_2.5.1-2.debian.tar.xz Checksums-Sha256: f8fbaf50c770252568692a048d4d550e3df851242d5bdfec4e0c05b32736877d 2614 brian_2.5.1-2.dsc 79c95ace092334131b31ad8a5ac060aa45547392c478a931cd95703898401381 19048 brian_2.5.1-2.debian.tar.xz Files: a9d4eeba9cbbdb3c2258c263e63275d1 2614 python optional brian_2.5.1-2.dsc afdb5888775c88af860110ecf55dc2ec 19048 python optional brian_2.5.1-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQJIBAEBCgAyFiEEj5GyJ8fW8rGUjII2eTz2fo8NEdoFAmO2AwIUHGVtb2xsaWVy QGRlYmlhbi5vcmcACgkQeTz2fo8NEdom2A//SN6R/332orgm/NuhhpXCDhqo8pNq 4YKAkI88UbtOc2DV8LtHdTRVmWdCpYlXkMjaG4b8hwOY/ccO1H9KA0TRWxtKtLOn gric+zj9Od1i9qw25Uji7aHoWFfZRtdlcE5tlurrzOqLXgdoZX0VeXqvMnNU5d2S 8rnAx4xTjQG8d9Jye/7k63UrDV2vp7BXSc6Exe1ZZVkk2ge5ntdF/RHKxFfR2uaU 7cyfpVbIe4mk+3qjk0O3GJ5/xYV5a+ANNourCdd2sJaInp48JYAHEZaTOfowZs1N 43YbWsEEwv8XZzLickJX4pid6AP0hDNpXyxjZwO0zeUZ5OAil7YkBYFwdphqING4 a63c1Sf2cX9mDOm174jcxbd2tDrPbNk+PDNKlE/oas6j/IUANsFNQDgkheaFqq9+ ETQis1NS2e+8z4PqVinZ4ISPE6+NiA9WhJ8kPajIzLTe2xK2VZL2+qPRamR9ITUY tQ2gT8B7f2EN8/BO0gY6dFv35Zc/FYguO8j6nLgnm5HZQbIgv6v8hgtsRqpLk7g0 oEhLW910zFBM2bLE9MXreFn+HRDrXRIaeKKEDTgraJyeM2OIsTV6afXI4s1/CMf/ 5a+rDph6iCNjJo7ETFdecYfZKVwIRr1I76FGYXvtZG6HThp0q20sz2Q5g0Wofv7N e2VoKHM9MbPlj08= =ns3E -END PGP SIGNATURE End Message ---
Processed: your mail
Processing commands for cont...@bugs.debian.org:
> fixed 1025981 ansible-lint/6.7.0-1
Bug #1025981 {Done: Paul Gevers } [src:ansible-lint]
ansible-core breaks ansible-lint autopkgtest: Ansible requires the locale
encoding to be UTF-8; Detected None.
Marked as fixed in versions ansible-lint/6.7.0-1.
> --
Stopping processing here.
Please contact me if you need assistance.
--
1025981: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025981
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1027947: python3-setuptools-scm: needs depend on python3-tomli during Python 3.11 transition
Package: python3-setuptools-scm
Version: 7.1.0-1
Severity: serious
Justification: missing dependency causes FTBFS in unrelated packages
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Dear maintainer,
python3-setuptools-scm has a 'python3-tomli || python3 (>> 3.11)'
dependency, which breaks python3.10 builds now that python3 has
transitioned to 3.11 as default version.
Adding python3-tomli unconditionally until Python 3.10 is dropped
from the archive will resolve the issue.
Example build log excerpt from ros-catkin-lint follows:
debian/rules clean
dh clean --buildsystem=pybuild
dh_auto_clean -O--buildsystem=pybuild
I: pybuild base:240: python3.10 setup.py clean
/usr/lib/python3/dist-packages/setuptools/installer.py:27:
SetuptoolsDeprecationWarning: setuptools.installer is deprecated. Requirements
should be satisfied by a PEP 517 installer.
warnings.warn(
WARNING: The wheel package is not available.
/usr/bin/python3.10: No module named pip
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/setuptools/installer.py", line 82, in
fetch_build_egg
subprocess.check_call(cmd)
File "/usr/lib/python3.10/subprocess.py", line 369, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['/usr/bin/python3.10', '-m', 'pip',
'--disable-pip-version-check', 'wheel', '--no-deps', '-w', '/tmp/tmpbhsnm7hs',
'--quiet', 'tomli>=1.0.0']' returned non-zero exit status 1.
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/<>/setup.py", line 42, in
setup(
File "/usr/lib/python3/dist-packages/setuptools/__init__.py", line 86, in
setup
_install_setup_requires(attrs)
File "/usr/lib/python3/dist-packages/setuptools/__init__.py", line 80, in
_install_setup_requires
dist.fetch_build_eggs(dist.setup_requires)
File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 874, in
fetch_build_eggs
resolved_dists = pkg_resources.working_set.resolve(
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 789, in
resolve
dist = best[req.key] = env.best_match(
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 1075,
in best_match
return self.obtain(req, installer)
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 1087,
in obtain
return installer(requirement)
File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 944, in
fetch_build_egg
return fetch_build_egg(self, req)
File "/usr/lib/python3/dist-packages/setuptools/installer.py", line 84, in
fetch_build_egg
raise DistutilsError(str(e)) from e
distutils.errors.DistutilsError: Command '['/usr/bin/python3.10', '-m', 'pip',
'--disable-pip-version-check', 'wheel', '--no-deps', '-w', '/tmp/tmpbhsnm7hs',
'--quiet', 'tomli>=1.0.0']' returned non-zero exit status 1.
E: pybuild pybuild:388: clean: plugin distutils failed with: exit code=1:
python3.10 setup.py clean
dh_auto_clean: error: pybuild --clean -i python{version} -p "3.10 3.11"
returned exit code 13
make: *** [debian/rules:24: clean] Error 25
-BEGIN PGP SIGNATURE-
iQGzBAEBCgAdFiEEJvtDgpxjkjCIVtam+C8H+466LVkFAmO2BMcACgkQ+C8H+466
LVkKwQwAjl+b4mijVOrvaxJ/gQm981m7Z+5QN9xjU/LKJ1f66QE/3lZW6tjS6VP9
1+uLpZx9nGTKCSEat2RXu8t+BgyxkoDM21QHyy6DbdeGaPsr8cvBvdlZYHCW7obn
bSnPHcMKEZfGptlZ5URCZvgbu8o23lTi+hkFNbzTIoMoR2jCev1mfl6Fx7LUwWCa
cbBlGFDGKYwcugNIx4yGt7VmW2urdTd/5UUqyz3CzeDkwof83dTLHrb7F9/dT91s
Qw3wc9STsSlsbNG4pBS2aTxx1C4CHLbSpXqHBjsoQ2zJQISm8ll9mq/nVaz2Rb58
EBil8GPCBzHHWhcUYrscHhUxPjbgsGkVFlGbN5308tO2bhKTYKwtTCS+IVbZsc8j
dwllYJJtlUxtslJsHgDIrU6/4vPrmAmQCuDXVT25uSawqo2PPNkqAAqx4rF+kIiZ
LQhgxwo8i5n6Ezi8kUWK3wLMOG/A8sJqdEDlm1N95BuheuJ/c568xFKtQywcUR8d
3x00rsS8
=KGeU
-END PGP SIGNATURE-
Bug#1025637: marked as done (debugpy: FTBFS in sid (test failures))
Your message dated Wed, 04 Jan 2023 22:52:25 + with message-id and subject line Bug#1025615: fixed in debugpy 1.6.4+git20221217.c419d5a+ds-1 has caused the Debian Bug report #1025615, regarding debugpy: FTBFS in sid (test failures) 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.) -- 1025615: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025615 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: debugpy Version: 1.6.3+git20221103.a2a3328+ds-1 Severity: serious Hello, as seen also in reproducible builds page, your package now FTBFS (test failures), probably due to newer Python3.11, even though I'm not really sure about it. Build log attached. Gianfranco debugpy.7z Description: application/7z-compressed OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: debugpy Source-Version: 1.6.4+git20221217.c419d5a+ds-1 Done: Julian Gilbey We believe that the bug you reported is fixed in the latest version of debugpy, 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 1025...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Julian Gilbey (supplier of updated debugpy 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, 04 Jan 2023 22:31:34 + Source: debugpy Architecture: source Version: 1.6.4+git20221217.c419d5a+ds-1 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Julian Gilbey Closes: 1025615 Changes: debugpy (1.6.4+git20221217.c419d5a+ds-1) unstable; urgency=medium . * New upstream version * Exclude failing tests on Python 3.11; hopefully this closes: #1025615), but it may be that other tests fail on architectures besides amd64 * Add a README explaining that this package is not yet compatible with Python 3.11, so many issues may arise Checksums-Sha1: 06b3f7454c5895658a70e9ff17e70dec0c7b6712 2682 debugpy_1.6.4+git20221217.c419d5a+ds-1.dsc e75828adf579370aa0609a17e395534621a36e00 143980 debugpy_1.6.4+git20221217.c419d5a+ds.orig.tar.xz adcace79e187b5a2be819c063233368bcaa4b1d6 7096 debugpy_1.6.4+git20221217.c419d5a+ds-1.debian.tar.xz cba9b91ae68bd1bb696fc39590c963afb5d793b5 9569 debugpy_1.6.4+git20221217.c419d5a+ds-1_amd64.buildinfo Checksums-Sha256: 085c70e8c573470bcd9b8316dea9cbc465a7901f7d438056f0f4ddf8fb0a63b2 2682 debugpy_1.6.4+git20221217.c419d5a+ds-1.dsc 133b7b93daeede0af5989a605f890c99add5186ea6fca9d7e4b965025c581193 143980 debugpy_1.6.4+git20221217.c419d5a+ds.orig.tar.xz bb0c7faeebda3f4380f494c872faaeb0840b9a3e06837398c1f5f276da33f732 7096 debugpy_1.6.4+git20221217.c419d5a+ds-1.debian.tar.xz 0b5d5e374f987a6e9f51ac6ec4d40346f3daec486f39945f3c65a9435301743f 9569 debugpy_1.6.4+git20221217.c419d5a+ds-1_amd64.buildinfo Files: 0f6d8df332dc2c6caf544f0c075f4f50 2682 python optional debugpy_1.6.4+git20221217.c419d5a+ds-1.dsc 08124822fdc9135d34ae88bf6392cbd7 143980 python optional debugpy_1.6.4+git20221217.c419d5a+ds.orig.tar.xz 5da2a3b540feac8d6284b236c481248e 7096 python optional debugpy_1.6.4+git20221217.c419d5a+ds-1.debian.tar.xz 86a5e0244c6eb57028b0b4a6d4174b31 9569 python optional debugpy_1.6.4+git20221217.c419d5a+ds-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJDBAEBCAAtFiEEfhrD+iemSShMMj72aVxCkxbAe/4FAmO1/+0PHGpkZ0BkZWJp YW4ub3JnAAoJEGlcQpMWwHv+/fYQAKmTbhb0cIyza4dyWfV3xb/HsCvHPIfDanA9 PeNHovrMm/MiwZW0+Z2jKjgyLqiXtc/wlTmwnt8hqsSYl2pxArG+wZcry38/k6gO dMnpxVKOY3jyJ7FPK4XkobuyAeNLf1YnnaX36S8wXqWmy+NjzGOsj9sB9GeSDyr8 FvZLEkg41qQiQ/zZKN4idbT9OvIjhWeo2A3KSZAaAp7KrSD2HNpFDCd/qrTMrWdH DSXw5qrRMzcjPXk83y7k4CSthgLQD7y66PIKdRkg91/peXLr+cT3Rv3625iMvw2H uY0vr39qRCGesiMO2t4RfPhFxBrWCOok+8v1a8HDI5am264GZxcEOmRQWM4cAMjL IEr7X8A/OTyvpmUi3JoX8LUM5jXQgOjswteQ0Ht4O8bbWlXU6P00qus6SZBwPYMW zt9H0O74BosmPC3Czsvy26U2HsGad7bb6n0kVH1s2y5Q+ZtOshhJzRd0xHCmPpcV DFWCd1GVHRo9a6DE6FQjg1QnAkS3apWVEkcbw/UZcfOIwnBzqCVYP7UAxT1a0eH0 ZGixGRMYmCGo1tavPLVK9PK0dMK447ayx5X6v/2aBsGQ8AH2BKRhmV6+/X9Odpp+ hHUb9z5ULMIhVElTFN5nfYbPfxAE6zYm/5ebTY8k1cN+/MmOk4I1PmeEhpRnOp8a bmL2yxiy =AIUh -END PGP SIGNATURE End Message ---
Bug#1016963: Please test u-boot for Mini-X
Hi Vagrant, * Vagrant Cascadian [2022-12-28 16:56]: This bug is just to delay migration to testing while more platforms get tested. If you have a relevent board, please consider testing and reporting the status: https://wiki.debian.org/U-boot/Status I have not received many test results for current or even remotely recent u-boot platforms in Debian, and u-boot has been blocked from migration to testing partly because of this. As the bookworm freeze approaches, this is getting to be... worrysome! If you have access to any of these boards, please consider testing u-boot versions as packaged in debian for versions from debian stable (2021.01*), testing (2022.04*), unstable (2022.10*) and experimental (2023.01-rc*) and updating the wiki page if successful and/or replying to 1016...@bugs.debian.org with a positive confirmation... ...and if not successful, filing bugs against the relevent u-boot-* packages and marking them as blocking 1016963. Mini-X Works fine with unstable, I've updated the wiki page. Cheers Jochen signature.asc Description: PGP signature
Bug#1026513: fixed patch
Hi!
Somehow, I accidentally created a reverse patch before; here's the
correct one.
- FC
--- a/nose_random/__init__.py 2023-01-04 23:12:59.008028925 +0100
+++ b/nose_random/__init__.py 2023-01-04 23:13:30.304246704 +0100
@@ -51,7 +51,7 @@
def randomize(n, scenario_generator, seed=12038728732):
def decorator(test):
def randomized_test(self):
-if config.scenario is not None:
+if config.scenario is not None and config.scenario is not _missing:
nseeds = 1
seeds = [config.scenario]
else:
@@ -70,4 +70,4 @@
else:
raise (type(e), type(e)('%s with scenario %s (%i of %i)' % (e.message, rseed, i+1, nseeds)), sys.exc_info()[2])
return randomized_test
-return decorator
\ No newline at end of file
+return decorator
Bug#1026294: marked as done (vip-manager: FTBFS: cannot use c.VIP (variable of type net.IP) as type netip.Addr in argument to arp.NewPacket)
Your message dated Wed, 04 Jan 2023 21:56:12 + with message-id and subject line Bug#1026294: fixed in vip-manager 1.0.2-4 has caused the Debian Bug report #1026294, regarding vip-manager: FTBFS: cannot use c.VIP (variable of type net.IP) as type netip.Addr in argument to arp.NewPacket 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.) -- 1026294: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026294 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: vip-manager Version: 1.0.2-3 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs vip-manager is failing to build in a clean sid schroot: > github.com/cybertec-postgresql/vip-manager/ipmanager > # github.com/cybertec-postgresql/vip-manager/ipmanager > src/github.com/cybertec-postgresql/vip-manager/ipmanager/basicConfigurer_linux.go:101:3: > cannot use c.VIP (variable of type net.IP) as type netip.Addr in argument to > arp.NewPacket > src/github.com/cybertec-postgresql/vip-manager/ipmanager/basicConfigurer_linux.go:103:3: > cannot use c.VIP (variable of type net.IP) as type netip.Addr in argument to > arp.NewPacket > src/github.com/cybertec-postgresql/vip-manager/ipmanager/basicConfigurer_linux.go:125:3: > cannot use c.VIP (variable of type net.IP) as type netip.Addr in argument to > arp.NewPacket > src/github.com/cybertec-postgresql/vip-manager/ipmanager/basicConfigurer_linux.go:127:3: > cannot use c.VIP (variable of type net.IP) as type netip.Addr in argument to > arp.NewPacket signature.asc Description: This is a digitally signed message part --- End Message --- --- Begin Message --- Source: vip-manager Source-Version: 1.0.2-4 Done: Michael Banck We believe that the bug you reported is fixed in the latest version of vip-manager, 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 1026...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Banck (supplier of updated vip-manager 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, 04 Jan 2023 22:33:30 +0100 Source: vip-manager Architecture: source Version: 1.0.2-4 Distribution: unstable Urgency: medium Maintainer: Debian PostgreSQL Maintainers Changed-By: Michael Banck Closes: 1026294 Changes: vip-manager (1.0.2-4) unstable; urgency=medium . * debian/patches/netip-port.patch: New patch, uses netip.Addr instead of net.IP, inline with the ARP module (Closes: #1026294). Checksums-Sha1: 69237461efa885e0fba13391310693168ed94e41 2445 vip-manager_1.0.2-4.dsc eec7f4e60f8cd9a3e4ea708abc404caa2ee53d2b 9028 vip-manager_1.0.2-4.debian.tar.xz 155c058ccaf7d158b1920b7f5256491e0dfd4bff 6182 vip-manager_1.0.2-4_source.buildinfo Checksums-Sha256: 2952515b43e53aafaacbdc431880b337fee56d3fe91cd4cff00662163e10c6e4 2445 vip-manager_1.0.2-4.dsc 2ecce61d5e8c4ad0b7d8f9449bdb0a4129e591c93e5574d6ab56334be822b036 9028 vip-manager_1.0.2-4.debian.tar.xz ab9d7ca1b9cb1cd3d9ddcae3022f270cd7300f9f5e937a6c05033a821bd8eff7 6182 vip-manager_1.0.2-4_source.buildinfo Files: 72c70b88288ac85d2218b70b98211a07 2445 net optional vip-manager_1.0.2-4.dsc 311c685011fe9652932813b948e38643 9028 net optional vip-manager_1.0.2-4.debian.tar.xz 8e9ec5ab99100309a8aa909bb4ba612d 6182 net optional vip-manager_1.0.2-4_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEnKh3dJ+rLk+paGLs3GhqJ7Q0gbAFAmO18MEACgkQ3GhqJ7Q0 gbAaIA//ZskCt1WDGS92LMQEHeiVeXT2E8jQJPX/fOvjsqKWN8XAkQLNT/7KWoBE E9icAkphhVnOkobpBuBaX4KYUEN6e0PQb7Fio98e1CyTtFTnsZLCw8l2US8XPaX9 /HDnN3PYxjates3Q5xm2VxKnZ1NXjx/1jGJ2ArYjVKeSqkuq8H1GA7yim1VI7d4b VgWaV+GktceGtlFjxS0Pm6mHOqvDcpKYUlJf/RJFJ3urwMRcpxD4xGIPowhrpOzm 7Fw20MCkvPJZqQnkePaKhwxDIWVacv80GKwllNZ5TUmpP69wHjwvOhESGTN11j9c aWJAMZEt5MD8NT/h33o2aKjxt/sVCTee2rB34y3wjGb3dkgQc15pgKoXt/4U2ulc V2iTqOSJsbQlfDTLS/r+IWZ4jooHTmWlwxaYgXpF0HPBMZQXkrPhJAM80ipZKlvc s/xkWgJRTT4R4EcYuKdiphHmD7+iISPlgDEgbGczUkQBRKnDEjHyO9z3lMZ6+YS8 UW7GOD2cKgMODBRp6z08NZuNHfSBChGzLzQ9GLznUJJUjznUDfeh+UPWIpYS9HSR F6MfjbwTzyjVe42TlPtlskcMhRXxIXyXUIyTaZiV53WR3SRo7qTP6zVhqj+gkdjK nOjRbQ2YtxmqrEtgTpBPlwKaR/U9zYHHEcNWbtFrHWqALWHd8lY= =7Ix3 -END PGP SIGNATURE End Message ---
Processed: retitle 1027934 to hugin: misses link_directories
Processing commands for cont...@bugs.debian.org: > retitle 1027934 hugin: misses link_directories Bug #1027934 [src:hugin] libflann-dev: pkg-config file now requires hdf5 but doesn't find it Changed Bug title to 'hugin: misses link_directories' from 'libflann-dev: pkg-config file now requires hdf5 but doesn't find it'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1027934: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027934 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1027936: marked as pending in brian
Control: tag -1 pending Hello, Bug #1027936 in brian 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/med-team/brian/-/commit/efa0c47633292b668744197bc71b5fe834cb8182 python3.11.patch: add; fix ftbfs with python3.11. Closes: #1027936 (this message was generated automatically) -- Greetings https://bugs.debian.org/1027936
Processed: Bug#1027936 marked as pending in brian
Processing control commands: > tag -1 pending Bug #1027936 [src:brian] brian FTBFS with Python 3.11 as default version Added tag(s) pending. -- 1027936: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027936 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: notfixed 1020899 in 0.1.3.0-1, tagging 1023443, tagging 985556, tagging 971640 ..., tagging 1027760 ...
Processing commands for cont...@bugs.debian.org:
> notfixed 1020899 0.1.3.0-1
Bug #1020899 {Done: Ilias Tsitsimpis }
[src:haskell-byte-order] haskell-byte-order: BD-Uninstallable on armel, armhf,
i386, mipsel
No longer marked as fixed in versions 0.1.3.0-1.
> tags 1023443 - sid
Bug #1023443 {Done: Vagrant Cascadian } [src:u-boot]
u-boot: Add colibri_imx6 configuration
Removed tag(s) sid.
> tags 985556 + experimental
Bug #985556 {Done: Simon McVittie } [glib2.0]
flatpak/1.2.5-0+deb10u4 FTBFS on IPv6-only buildds
Added tag(s) experimental.
> tags 971640 + experimental
Bug #971640 {Done: Reiner Herrmann } [firejail] firejail:
Build profile command no longer works
Added tag(s) experimental.
> reassign 1027891 src:linux
Bug #1027891 [linux-image-6.2.0-rc2] linux-image-6.2.0-rc2: cannot connect via
ethernet
Warning: Unknown package 'linux-image-6.2.0-rc2'
Bug reassigned from package 'linux-image-6.2.0-rc2' to 'src:linux'.
No longer marked as found in versions 6.2.0-rc2-1.
Ignoring request to alter fixed versions of bug #1027891 to the same values
previously set
> reassign 794821 src:wxwidgets3.2 3.2.1+dfsg-1
Bug #794821 [libwxbase3.2-0] libwxbase3.0-0: segmentation fault (SIGSEGV) with
gnuplot5
Warning: Unknown package 'libwxbase3.2-0'
Bug reassigned from package 'libwxbase3.2-0' to 'src:wxwidgets3.2'.
No longer marked as found in versions wxwidgets3.2/3.2.1+dfsg-1.
Ignoring request to alter fixed versions of bug #794821 to the same values
previously set
Bug #794821 [src:wxwidgets3.2] libwxbase3.0-0: segmentation fault (SIGSEGV)
with gnuplot5
Marked as found in versions wxwidgets3.2/3.2.1+dfsg-1.
> reassign 1024147 src:wxwidgets3.2 3.2.1+dfsg-1
Bug #1024147 {Done: Scott Talbert } [libwxgtk3.2-0] Please
build with --disable-glcanvasegl
Warning: Unknown package 'libwxgtk3.2-0'
Bug reassigned from package 'libwxgtk3.2-0' to 'src:wxwidgets3.2'.
No longer marked as found in versions wxwidgets3.2/3.2.1+dfsg-1.
No longer marked as fixed in versions wxwidgets3.2/3.2.1+dfsg-2.
Bug #1024147 {Done: Scott Talbert } [src:wxwidgets3.2] Please
build with --disable-glcanvasegl
Marked as found in versions wxwidgets3.2/3.2.1+dfsg-1.
> fixed 1024147 3.2.1+dfsg-2
Bug #1024147 {Done: Scott Talbert } [src:wxwidgets3.2] Please
build with --disable-glcanvasegl
Marked as fixed in versions wxwidgets3.2/3.2.1+dfsg-2.
> found 1026781 1.8.0-7
Bug #1026781 [pkgconf] pkgconf: breaks adequate missing-pkgconfig-dependency
check due to behaviour change in: pkg-config --exists --print-errors
There is no source info for the package 'pkgconf' at version '1.8.0-7' with
architecture ''
Unable to make a source version for version '1.8.0-7'
Marked as found in versions 1.8.0-7.
> found 1027733 4.9.0-3
Bug #1027733 [screen] GNU Screen does not support Unicode 14
Marked as found in versions screen/4.9.0-3.
> tags 1027760 + sid bookworm
Bug #1027760 [src:gortr] gortr appears to be unmaintained
Added tag(s) bookworm and sid.
> tags 1027854 + sid bookworm
Bug #1027854 [kismet-plugins] kismet-plugins: uninstallable due to dependency
on libssl1.1
Added tag(s) sid and bookworm.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1020899: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020899
1023443: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023443
1024147: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024147
1026781: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026781
1027733: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027733
1027760: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027760
1027854: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027854
1027891: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027891
794821: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794821
971640: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971640
985556: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985556
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1021325: marked as done (irrlicht: non-free files included)
Your message dated Wed, 04 Jan 2023 21:52:40 + with message-id and subject line Bug#1021325: fixed in irrlicht 1.8.5+ds2-1 has caused the Debian Bug report #1021325, regarding irrlicht: non-free files included 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.) -- 1021325: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021325 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: irrlicht Version: 1.8.5+ds-2 Severity: serious The irrlicht source includes the media/dwarf* files which have a non-free license. Please repack getting rid of it. The package will still build without them. --- End Message --- --- Begin Message --- Source: irrlicht Source-Version: 1.8.5+ds2-1 Done: Vincent Cheng We believe that the bug you reported is fixed in the latest version of irrlicht, 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 1021...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Vincent Cheng (supplier of updated irrlicht 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, 04 Jan 2023 13:03:53 -0800 Source: irrlicht Binary: libirrlicht-dev libirrlicht1.8 libirrlicht-doc Architecture: source Version: 1.8.5+ds2-1 Distribution: unstable Urgency: medium Maintainer: Debian Games Team Changed-By: Vincent Cheng Description: libirrlicht-dev - High performance realtime 3D engine development library libirrlicht-doc - High performance realtime 3D engine (API documentation) libirrlicht1.8 - High performance realtime 3D engine Closes: 927456 1021325 Changes: irrlicht (1.8.5+ds2-1) unstable; urgency=medium . [ Vincent Cheng ] * Repack source tarball to remove non-free files. (Closes: #1021325) * Update Standards-Version to 4.6.2, no changes needed. . [ Julien Puydt ] * Add a patch to stop using CFLAGS. (Closes: #927456) . [ Debian Janitor ] * debian/copyright: use spaces rather than tabs to start continuation lines. Checksums-Sha1: f85c4859ed796e0d6b24cadcd06ea271d83f31ee 2283 irrlicht_1.8.5+ds2-1.dsc ad126f55baa1425f29367fffc02b97c865e73897 7680364 irrlicht_1.8.5+ds2.orig.tar.xz a324720b84dd1c8cb191ecee35209d6b6c0f2e8d 50212 irrlicht_1.8.5+ds2-1.debian.tar.xz Checksums-Sha256: 245dfd17601f851a64b4bb7c3b9143aaf6f364ebca8a840271146c02fdec138e 2283 irrlicht_1.8.5+ds2-1.dsc 5af2b7e1509efcf70709a597252a4c6e35406e995c788103c037168218956ba8 7680364 irrlicht_1.8.5+ds2.orig.tar.xz 6437a3a6dc1b58aecb5db79a344c30efb4ae88578e17c7ee835200df68ee0e59 50212 irrlicht_1.8.5+ds2-1.debian.tar.xz Files: c206d5a31921ee65692a5605c63f9b3f 2283 libs optional irrlicht_1.8.5+ds2-1.dsc 8858f5836b7f753055828f11bae70cae 7680364 libs optional irrlicht_1.8.5+ds2.orig.tar.xz bcc335004a7da732ad242aec36749555 50212 libs optional irrlicht_1.8.5+ds2-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEE1TqBWjy3ZZr4guOVju3MG6ofMv8FAmO18LkACgkQju3MG6of Mv/0whAAqH7840o2PjGrtQ4S/tRbOqgjSfkNLlRV4Zf2toOrpbq1xalfPsRQFbXl w0EgOPJ8vixdN+dBptBgMaL5PSE71rSbrNnTtAswh7Kvcyg2jVL2gTxJjDuaIEGO IyPDZ5oJ8EDDc8YTxWK8jaAWeZO4SToSCuvPC6hrCVHWBH8yHXc+WsC/1m8UvZ9h KoKYT0KaAjEYKWtzKxeFb8YcazuOVWxCorWVI399U08NRmRf4A7L6jeOLLDkVuxm u4pnbfQrB0HOC7JthSp8NGCxZe/mC/qhPPpjEVpV120trH1eF/+67EFVx6NrvAFW 6VT1gSfZH0N6NOyvSX2JEvSDw4FrL53GSxj8mrC8edzEyf+IgEbgK1Bfegc8uie1 zY8wCHZ2vrDYCxZMSnvfKSLLtco/V/pj/fmduMNmilGlDevHCu7A3G07Dbwi9Cpl 6s8URJ1rw80s+c5d9aCaPKrPCHdFxLOY5573ntJuxpETxm3xz4bKgFJz01QoKIrE PY5Zr7dTBAoPn4Enq2604pyG8Lz0irm7lyjpiyz7tobO+hEXoCcUOlXBuDHXMKqe LGgqiotLUtCkyXlUeEah89G91WBJ9N7bTz7lF/znAS3sBrDtwzwd6RMKvYO16Vx2 1KgjDalAhSifd4ssLwf0Ne6oYC+LU2Hi/cCFl2ymoNw1Wa53k+s= =MWUu -END PGP SIGNATURE End Message ---
Bug#1027934: libflann-dev: pkg-config file now requires hdf5 but doesn't find it
Control: reassign -1 src:hugin 2022.0.0+dfsg
* Adrian Bunk [2023-01-04 22:02]:
https://buildd.debian.org/status/fetch.php?pkg=hugin=amd64=2022.0.0%2Bdfsg-1%2Bb2=1672840532=0
...
/usr/bin/c++ -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security
-Wall -Wdate-time -D_FORTIFY_SOURCE=2 -Wl,-z,relro -Wl,-z,now -Wl,--as-needed -Wl,-z,defs -fopenmp
CMakeFiles/cpfind.dir/PanoDetector.cpp.o CMakeFiles/cpfind.dir/PanoDetectorLogic.cpp.o CMakeFiles/cpfind.dir/TestCode.cpp.o
CMakeFiles/cpfind.dir/Utils.cpp.o CMakeFiles/cpfind.dir/main.cpp.o -o cpfind
-Wl,-rpath,/<>/obj-x86_64-linux-gnu/src/hugin_cpfind/localfeatures:/<>/obj-x86_64-linux-gnu/src/celeste:/<>/obj-x86_64-linux-gnu/src/hugin_base:
../localfeatures/liblocalfeatures.so.0.0 /usr/lib/x86_64-linux-gnu/libvigraimpex.so /usr/lib/x86_64-linux-gnu/libOpenEXR.so
/usr/lib/x86_64-linux-gnu/libImath-3_1.so /usr/lib/x86_64-linux-gnu/libIex-3_1.so /usr/lib/x86_64-linux-gnu/libIlmThread-3_1.so
/usr/lib/x86_64-linux-gnu/libz.so /usr/lib/x86_64-linux-gnu/libjpeg.so /usr/lib/x86_64-linux-gnu/libtiff.so
/usr/lib/x86_64-linux-gnu/libpng.so /usr/lib/x86_64-linux-gnu/libz.so /usr/lib/x86_64-linux-gnu/libz.so
/usr/lib/x86_64-linux-gnu/libexiv2.so /usr/lib/x86_64-linux-gnu/libpano13.so ../../foreign/levmar/libhuginlevmar.a
/usr/lib/x86_64-linux-gnu/libGLEW.so /usr/lib/x86_64-linux-gnu/libfftw3.so /usr/lib/x86_64-linux-gnu/libvigraimpex.so
/usr/lib/x86_64-linux-gnu/libOpenEXR.so /usr/lib/x86_64-linux-gnu/libImath-3_1.so /usr/lib/x86_64-linux-gnu/libIex-3_1.so
/usr/lib/x86_64-linux-gnu/libIlmThread-3_1.so /usr/lib/x86_64-linux-gnu/libz.so /usr/lib/x86_64-linux-gnu/libjpeg.so
/usr/lib/x86_64-linux-gnu/libtiff.so /usr/lib/x86_64-linux-gnu/libpng.so /usr/lib/x86_64-linux-gnu/libz.so
/usr/lib/x86_64-linux-gnu/libz.so /usr/lib/x86_64-linux-gnu/libexiv2.so /usr/lib/x86_64-linux-gnu/liblcms2.so
../../celeste/libceleste.so.0.0 -lflann -lflann_cpp -lhdf5 -lmpi -llz4 ../../hugin_base/libhuginbase.so.0.0
/usr/lib/x86_64-linux-gnu/libX11.so /usr/lib/x86_64-linux-gnu/libOpenGL.so /usr/lib/x86_64-linux-gnu/libGLX.so
/usr/lib/x86_64-linux-gnu/libGLU.so /usr/lib/x86_64-linux-gnu/libsqlite3.so /usr/lib/x86_64-linux-gnu/libpano13.so
../../foreign/levmar/libhuginlevmar.a /usr/lib/x86_64-linux-gnu/libGLEW.so
/usr/lib/x86_64-linux-gnu/libboost_filesystem.so.1.74.0 /usr/lib/x86_64-linux-gnu/libboost_system.so.1.74.0
/usr/lib/x86_64-linux-gnu/libfftw3.so /usr/lib/x86_64-linux-gnu/libvigraimpex.so /usr/lib/x86_64-linux-gnu/libOpenEXR.so
/usr/lib/x86_64-linux-gnu/libImath-3_1.so /usr/lib/x86_64-linux-gnu/libIex-3_1.so /usr/lib/x86_64-linux-gnu/libIlmThread-3_1.so
/usr/lib/x86_64-linux-gnu/libz.so /usr/lib/x86_64-linux-gnu/libjpeg.so /usr/lib/x86_64-linux-gnu/libpng.so
/usr/lib/x86_64-linux-gnu/libz.so /usr/lib/x86_64-linux-gnu/libjpeg.so /usr/lib/x86_64-linux-gnu/libpng.so
/usr/lib/x86_64-linux-gnu/libtiff.so /usr/lib/x86_64-linux-gnu/libexiv2.so /usr/lib/x86_64-linux-gnu/liblcms2.so
/usr/bin/ld: cannot find -lhdf5: No such file or directory
collect2: error: ld returned 1 exit status
make[3]: *** [src/hugin_cpfind/cpfind/CMakeFiles/cpfind.dir/build.make:221:
src/hugin_cpfind/cpfind/cpfind] Error 1
Relevant /usr/lib/x86_64-linux-gnu/pkgconfig/flann.pc diff:
│ │ │ -Version: 1.9.1
│ │ │ -Requires: liblz4
│ │ │ +Version: 1.9.2
│ │ │ +Requires: hdf5 liblz4
$ pkgconf --libs flann
-L/usr/lib/x86_64-linux-gnu\;-llz4 -lflann -lflann_cpp
-L/usr/lib/x86_64-linux-gnu/hdf5/openmpi -lhdf5
-L/usr/lib/x86_64-linux-gnu/openmpi/lib -lmpi -llz4
$ dpkg -S libhdf5.so
libhdf5-openmpi-dev: /usr/lib/x86_64-linux-gnu/hdf5/openmpi/libhdf5.so
$
From the log above:
Unpacking libopenmpi-dev:amd64 (4.1.4-3) ...
The problem is that hugin ignores the FLANN_LIBRARY_DIRS. This patch
fixes it:
--- hugin-2022.0.0+dfsg/CMakeModules/FindFLANN.cmake2018-11-01
18:26:55.0 +0100
+++ hugin-2022.0.0+dfsg-1/CMakeModules/FindFLANN.cmake 2023-01-04
22:49:27.667327549 +0100
@@ -11,6 +11,7 @@
if(UNIX)
find_package(PkgConfig QUIET)
pkg_check_modules(FLANN flann)
+ link_directories(${FLANN_LIBRARY_DIRS})
else()
find_path(FLANN_INCLUDE_DIRS flann/flann.hpp)
Cheers Jochen
signature.asc
Description: PGP signature
Processed: Re: Bug#1027934: libflann-dev: pkg-config file now requires hdf5 but doesn't find it
Processing control commands: > reassign -1 src:hugin 2022.0.0+dfsg Bug #1027934 [libflann-dev] libflann-dev: pkg-config file now requires hdf5 but doesn't find it Bug reassigned from package 'libflann-dev' to 'src:hugin'. No longer marked as found in versions flann/1.9.2+dfsg-1. Ignoring request to alter fixed versions of bug #1027934 to the same values previously set Bug #1027934 [src:hugin] libflann-dev: pkg-config file now requires hdf5 but doesn't find it The source 'hugin' and version '2022.0.0+dfsg' do not appear to match any binary packages Marked as found in versions hugin/2022.0.0+dfsg. -- 1027934: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027934 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1019772: freespace2-launcher-wxlauncher: Please transition to wxwidgets3.2
Processing control commands: > tags -1 + patch Bug #1019772 [src:freespace2-launcher-wxlauncher] freespace2-launcher-wxlauncher: Please transition to wxwidgets3.2 Added tag(s) patch. -- 1019772: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019772 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1019772: freespace2-launcher-wxlauncher: Please transition to wxwidgets3.2
Control: tags -1 + patch On Wed, Sep 14, 2022 at 03:42:14PM -0400, s...@techie.net wrote: > Please transition freespace2-launcher-wxlauncher from wxwidgets3.0 to > wxwidgets3.2. Just a friendly note to highlight that this package needs to re-enter testing to make it into bookworm, and that the release freeze cut-off for re-entering testing is 2023-02-12: https://release.debian.org/testing/freeze_policy.html#summary I think a package needs to actually *migrate* by that cut-off date, so the upload deadline is really 2/5/10 days earlier depending on whether there are autopkgtests, etc. Best to upload well before that if possible as there can be delays, especially if some other maintainers are frantically uploading to try to get in before the freeze. It looks like minor changes are required for wxwidgets3.2 compatibility and there's a patch which looks plausible submitted upstream (reviewed but not yet merged): https://github.com/scp-fs2open/wxLauncher/pull/173 Are you able to make an upload? I can try to find time to NMU, but I don't have the non-free files required to fully test this package. Cheers, Olly
Bug#1027939: clang-14 lost its (indirect) dependency on libclang-rt-14-dev
Yeah, this is by design. Most of the programs won't need compiler-rt. Halide should just add an extra dependency. Cheers Sylvestre Le 04/01/2023 à 22:30, Adrian Bunk a écrit : Package: clang-14 Version: 1:14.0.6-10~exp4 Severity: serious Tags: ftbfs Control: affects -1 src:halide https://buildd.debian.org/status/fetch.php?pkg=halide=amd64=14.0.0-2%2Bb1=1672837458=0 ... -- Check for working C compiler: /usr/bin/clang-14 -- Check for working C compiler: /usr/bin/clang-14 - broken CMake Error at /usr/share/cmake-3.25/Modules/CMakeTestCCompiler.cmake:70 (message): The C compiler "/usr/bin/clang-14" is not able to compile a simple test program. It fails with the following output: Change Dir: /<>/build/stage-0/halide/CMakeFiles/CMakeScratch/TryCompile-MA4jQl Run Build Command(s):/usr/bin/ninja cmTC_6af5a && [1/2] Building C object CMakeFiles/cmTC_6af5a.dir/testCCompiler.c.o clang: warning: -Wl,--build-id=sha1: 'linker' input unused [-Wunused-command-line-argument] clang: warning: argument unused during compilation: '-fuse-ld=lld-14' [-Wunused-command-line-argument] [2/2] Linking C executable cmTC_6af5a FAILED: cmTC_6af5a : && /usr/bin/clang-14 -g -fdebug-default-version=4 -fprofile-generate -Xclang -mllvm -Xclang -vp-counters-per-site=10.0 -fuse-ld=lld-14 -Wl,--build-id=sha1 -Wl,-z,relro CMakeFiles/cmTC_6af5a.dir/testCCompiler.c.o -o cmTC_6af5a && : ld.lld-14: error: cannot open /usr/lib/llvm-14/lib/clang/14.0.6/lib/linux/libclang_rt.profile-x86_64.a: No such file or directory clang: error: linker command failed with exit code 1 (use -v to see invocation) ninja: build stopped: subcommand failed. CMake will not be able to correctly generate this project. Call Stack (most recent call first): CMakeLists.txt:2 (project) -- Configuring incomplete, errors occurred! ___ Pkg-llvm-team mailing list pkg-llvm-t...@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-llvm-team
Bug#1027943: regina-normal FTBFS with Python 3.11 as default version
Source: regina-normal Version: 7.2-2 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=regina-normal=amd64=7.2-2%2Bb1=1672843144=0 ... 3: Test command: /<>/obj-x86_64-linux-gnu/python/testsuite/testbasic 3: Working Directory: /<>/obj-x86_64-linux-gnu/python/testsuite 3: Test timeout computed to be: 1000 3: 3: Test suite for python bindings with a basic embedded interpreter 3: 3: 3: Running alltypes.test ... FAILED (exit code 2) 3: Output was: 3: ... 3: ModuleNotFoundError: No module named 'regina' 3: ERROR: Could not import reginaRunning angles.test ... FAILED (exit code 2) ... 75% tests passed, 1 tests failed out of 4 Total Test time (real) = 277.26 sec The following tests FAILED: 3 - python-basic (Failed) Errors while running CTest make[2]: *** [Makefile:94: test] Error 8
Bug#1026507: marked as done (neuron: FTBFS: open: No such file or directory)
Your message dated Wed, 04 Jan 2023 21:32:47 + with message-id and subject line Bug#1026507: fixed in neuron 7.6.3-2 has caused the Debian Bug report #1026507, regarding neuron: FTBFS: open: No such file or directory to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1026507: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026507 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: neuron Version: 7.6.3-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20221220 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[5]: Entering directory '/<>' > echo "enter install-exec-hook in nrn/Makefile.am" > enter install-exec-hook in nrn/Makefile.am > if test "--verbose --home=/<>/debian/tmp/usr" != "no" ; then \ > cd src/nrnpython ; \ > /usr/bin/python3 setup.py install --verbose > --home=/<>/debian/tmp/usr ;\ > fi > running install > /usr/lib/python3/dist-packages/setuptools/command/install.py:34: > SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build and > pip and other standards-based tools. > warnings.warn( > /usr/lib/python3/dist-packages/setuptools/command/easy_install.py:146: > EasyInstallDeprecationWarning: easy_install command is deprecated. Use build > and pip and other standards-based tools. > warnings.warn( > Checking .pth file support in /<>/debian/tmp/usr/lib/python/ > /usr/bin/python3 -E -c pass > TEST FAILED: /<>/debian/tmp/usr/lib/python/ does NOT support > .pth files > bad install directory or PYTHONPATH > > You are attempting to install a package to a directory that is not > on PYTHONPATH and which Python does not read ".pth" files from. The > installation directory you specified (via --install-dir, --prefix, or > the distutils default setting) was: > > /<>/debian/tmp/usr/lib/python/ > > and your PYTHONPATH environment variable currently contains: > > '' > > Here are some of your options for correcting the problem: > > * You can choose a different installation directory, i.e., one that is > on PYTHONPATH or supports .pth files > > * You can add the installation directory to the PYTHONPATH environment > variable. (It must then also be on PYTHONPATH whenever you run > Python and want to use the package(s) you are installing.) > > * You can set up the installation directory to support ".pth" files by > using one of the approaches described here: > > > https://setuptools.pypa.io/en/latest/deprecated/easy_install.html#custom-installation-locations > > > Please make the appropriate changes for your system and try again. > running bdist_egg > running egg_info > creating /<>/debian/tmp/usr/share/nrn/lib/python/NEURON.egg-info > writing > /<>/debian/tmp/usr/share/nrn/lib/python/NEURON.egg-info/PKG-INFO > writing dependency_links to > /<>/debian/tmp/usr/share/nrn/lib/python/NEURON.egg-info/dependency_links.txt > writing top-level names to > /<>/debian/tmp/usr/share/nrn/lib/python/NEURON.egg-info/top_level.txt > writing manifest file > '/<>/debian/tmp/usr/share/nrn/lib/python/NEURON.egg-info/SOURCES.txt' > reading manifest file > '/<>/debian/tmp/usr/share/nrn/lib/python/NEURON.egg-info/SOURCES.txt' > writing manifest file > '/<>/debian/tmp/usr/share/nrn/lib/python/NEURON.egg-info/SOURCES.txt' > installing library code to build/bdist.linux-x86_64/egg > running install_lib > running build_py > creating build > creating build/lib.linux-x86_64-cpython-310 > creating build/lib.linux-x86_64-cpython-310/neuron > copying > /<>/debian/tmp/usr/share/nrn/lib/python/neuron/__init__.py -> > build/lib.linux-x86_64-cpython-310/neuron > copying /<>/debian/tmp/usr/share/nrn/lib/python/neuron/doc.py -> > build/lib.linux-x86_64-cpython-310/neuron > copying > /<>/debian/tmp/usr/share/nrn/lib/python/neuron/nonvint_block_supervisor.py > -> build/lib.linux-x86_64-cpython-310/neuron > copying > /<>/debian/tmp/usr/share/nrn/lib/python/neuron/hclass3.py -> > build/lib.linux-x86_64-cpython-310/neuron > copying > /<>/debian/tmp/usr/share/nrn/lib/python/neuron/hclass2.py -> > build/lib.linux-x86_64-cpython-310/neuron > copying > /<>/debian/tmp/usr/share/nrn/lib/python/neuron/psection.py -> > build/lib.linux-x86_64-cpython-310/neuron > copying /<>/debian/tmp/usr/share/nrn/lib/python/neuron/gui.py -> > build/lib.linux-x86_64-cpython-310/neuron > copying > /<>/debian/tmp/usr/share/nrn/lib/python/neuron/sections.py -> > build/lib.linux-x86_64-cpython-310/neuron > creating
Bug#460232: marked as done (Please clarify license)
Your message dated Wed, 04 Jan 2023 21:33:47 + with message-id and subject line Bug#460232: fixed in pam 1.5.2-6 has caused the Debian Bug report #460232, regarding Please clarify license 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.) -- 460232: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=460232 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: pam Version: 0.99.7.1-5 Hi! The copyright file contains: ALTERNATIVELY, this product may be distributed under the terms of the GNU General Public License, in which case the provisions of the GNU GPL are required INSTEAD OF the above restrictions. (This clause is necessary due to a potential conflict between the GNU GPL and the restrictions contained in a BSD-style copyright.) ... On Debian GNU/Linux systems, the complete text of the GNU General Public License can be found in `/usr/share/common-licenses/GPL'. Which version of the GPL does this refer to? The file in common-licenses is now actually GPLv3, but I suspect that Linux-PAM intended to use GPLv2 or GPLv1 here. In any case, I think the license of the package isn't clear. I looked in upstream sources, but couldn't find a copy of the GPL at all, so this problem may be due to upstream. Still, it would be good to fix it. /Simon --- End Message --- --- Begin Message --- Source: pam Source-Version: 1.5.2-6 Done: Sam Hartman We believe that the bug you reported is fixed in the latest version of pam, 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 460...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sam Hartman (supplier of updated pam 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: Tue, 03 Jan 2023 13:15:23 -0700 Source: pam Architecture: source Version: 1.5.2-6 Distribution: unstable Urgency: medium Maintainer: Steve Langasek Changed-By: Sam Hartman Closes: 460232 1004000 1022952 1024645 Changes: pam (1.5.2-6) unstable; urgency=medium . * Update debian/copyright, Thanks Bastian Germann, Closes: #460232 * When pam-auth-update is called with --root, use /usr/share/pam-configs from the root not from the host system, Thanks Johannes Schauer Marin Rodrigues, Closes: #1022952 * Build-depend on libcrypt-dev, Closes: #1024645 * Add pam-auth-udpate --disable, Closes: #1004000 * Add autopkgtests Checksums-Sha1: 8965f7e5f1ef5453002d92c9b4508a18b7991052 1998 pam_1.5.2-6.dsc 9f9578052a8467782061011c6c6197b6bee69d9e 122320 pam_1.5.2-6.debian.tar.xz Checksums-Sha256: 2dbff29f5fc189c95b863ffd690795a7313515619ddadc470eab8a50b7555903 1998 pam_1.5.2-6.dsc 97adad0df930ba5ed52b88bef6d494a1b303ca2eb5be9e347479a23e4d9254fc 122320 pam_1.5.2-6.debian.tar.xz Files: e054ae6cd6a7cfc3a194c9e7b7f5d692 1998 libs optional pam_1.5.2-6.dsc f62abdd59a5b1eab7d9c64cf15a68860 122320 libs optional pam_1.5.2-6.debian.tar.xz -BEGIN PGP SIGNATURE- iHUEARYIAB0WIQSj2jRwbAdKzGY/4uAsbEw8qDeGdAUCY7XlGwAKCRAsbEw8qDeG dM4sAP9YCWE0gkQXi+WnfgrAvuN4Y5YBALqLbUyolZfWNKSycgD/Xt36rP95G7jm Fk3Z7jmOH5u08dc+S//zP9TFaCD66Qo= =YfXI -END PGP SIGNATURE End Message ---
Bug#1027397: marked as done (ognibuild: autopkgtest regression: No module named 'ognibuild.tests')
Your message dated Wed, 04 Jan 2023 21:33:16 + with message-id and subject line Bug#1027397: fixed in ognibuild 0.0.16-2 has caused the Debian Bug report #1027397, regarding ognibuild: autopkgtest regression: No module named 'ognibuild.tests' 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.) -- 1027397: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027397 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ognibuild Version: 0.0.16-1 Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of ognibuild the autopkgtest of ognibuild fails in testing when that autopkgtest is run with the binary packages of ognibuild from unstable. It passes when run with only packages from testing. In tabular form: passfail ognibuild from testing0.0.16-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=ognibuild https://ci.debian.net/data/autopkgtest/testing/amd64/o/ognibuild/29784768/log.gz E == ERROR: tests (unittest.loader._FailedTest) -- ImportError: Failed to import test module: tests Traceback (most recent call last): File "/usr/lib/python3.10/unittest/loader.py", line 154, in loadTestsFromName module = __import__(module_name) ModuleNotFoundError: No module named 'ognibuild.tests' -- Ran 1 test in 0.000s FAILED (errors=1) autopkgtest [03:19:17]: test command1 OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: ognibuild Source-Version: 0.0.16-2 Done: Jelmer Vernooij We believe that the bug you reported is fixed in the latest version of ognibuild, 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 1027...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jelmer Vernooij (supplier of updated ognibuild 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, 04 Jan 2023 19:58:27 + Source: ognibuild Architecture: source Version: 0.0.16-2 Distribution: unstable Urgency: medium Maintainer: Jelmer Vernooij Changed-By: Jelmer Vernooij Closes: 1027397 Changes: ognibuild (0.0.16-2) unstable; urgency=medium . * Add missing recommends on python3-build. * Update standards version to 4.6.2, no changes needed. * Fix autopkgtest running tests. Closes: #1027397 Checksums-Sha1: 1f94555d65ac9194c1eb37189bf24185f6cc0596 2205 ognibuild_0.0.16-2.dsc 558202633662518b718fb77081269e0ce6044d25 34484 ognibuild_0.0.16-2.debian.tar.xz 29059766931cba04266b3b4bb8123055ac2a4685 10959 ognibuild_0.0.16-2_amd64.buildinfo Checksums-Sha256: 2aa5eb0e2f897f8b1e033b6436a5dba68d191d076ccc4c66fa9bb9758f991a48 2205 ognibuild_0.0.16-2.dsc a4df37da3e747eaef701fb24c1f28bb67e9da3db68ac04455b33a0b0ae0b2027 34484 ognibuild_0.0.16-2.debian.tar.xz 23256fffb850023cfa282b41d8962e5d3661c0c8e0a823db69f1fb4c0137cbfd 10959 ognibuild_0.0.16-2_amd64.buildinfo Files: 076f5a251df3f50a913c589c3970320f 2205 devel optional ognibuild_0.0.16-2.dsc 72196e590368ae6b0bd161f16b313c6d 34484 devel optional ognibuild_0.0.16-2.debian.tar.xz b85c01c785fd04835c379d661332d2ef 10959 devel optional ognibuild_0.0.16-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEsjhixBXWVlpOhsvXV5wWDUyeI+gFAmO15awACgkQV5wWDUye I+iFww//Q35aT0oG7/KWZAVLwg/cXfWKaTFq8EoJOd2McLPD3Vf0Uy7bYvhkW/5H Dvm/wddiTX9YZube4nVqwWa5JN+FHky1IfvNYkZB9o8sZXFD17uSoYe0TnqZh7E4 eVO/LJtStJkTyrp/IZJpp5AwFV7i5JNh6WTWuyEOHvMemRlT9P6yqOYIihwy88XV P8ehp25XHRrkB7SonG3vLi20HjnTlumPU7yEE2VEyE5vZ6hpqO0Ha+SP4biUdpbE
Bug#1019769: opencpn: Please transition to wxwidgets3.2
Just a friendly note to highlight that opencpn needs to re-enter testing to make it into bookworm, and that the release freeze cut-off for re-entering testing is 2023-02-12: https://release.debian.org/testing/freeze_policy.html#summary I think a package needs to actually *migrate* by that cut-off date, so the upload deadline is really 2/5/10 days earlier depending on whether there are autopkgtests, etc. Best to upload well before that if possible as there can be delays, especially if some other maintainers are frantically uploading to try to get in before the freeze. On Wed, Oct 26, 2022 at 01:12:18PM +0200, Alec Leamas wrote: > Opencpn has a plugin universe. For that reason, we cannot just update the > existing version 5.6.2 to wxWidgets 3.2 since it would break the plugin ABI. > > The plan is to update the wxWidget version when packaging the upcoming > version 5.8.0. This is slated for bookworm, and should be uploaded before > Christmas. Any problems with this plan? Looking at the upstream website, it seems this release hasn't happened yet. I'm looking at NMUing the small number of packages which haven't transitioned to wx3.2 yet, but I don't think I can usefully NMU in this case due to the plugin ABI situation - that really needs a maintainer to decide what to do. Cheers, Olly
Bug#1027939: clang-14 lost its (indirect) dependency on libclang-rt-14-dev
Package: clang-14 Version: 1:14.0.6-10~exp4 Severity: serious Tags: ftbfs Control: affects -1 src:halide https://buildd.debian.org/status/fetch.php?pkg=halide=amd64=14.0.0-2%2Bb1=1672837458=0 ... -- Check for working C compiler: /usr/bin/clang-14 -- Check for working C compiler: /usr/bin/clang-14 - broken CMake Error at /usr/share/cmake-3.25/Modules/CMakeTestCCompiler.cmake:70 (message): The C compiler "/usr/bin/clang-14" is not able to compile a simple test program. It fails with the following output: Change Dir: /<>/build/stage-0/halide/CMakeFiles/CMakeScratch/TryCompile-MA4jQl Run Build Command(s):/usr/bin/ninja cmTC_6af5a && [1/2] Building C object CMakeFiles/cmTC_6af5a.dir/testCCompiler.c.o clang: warning: -Wl,--build-id=sha1: 'linker' input unused [-Wunused-command-line-argument] clang: warning: argument unused during compilation: '-fuse-ld=lld-14' [-Wunused-command-line-argument] [2/2] Linking C executable cmTC_6af5a FAILED: cmTC_6af5a : && /usr/bin/clang-14 -g -fdebug-default-version=4 -fprofile-generate -Xclang -mllvm -Xclang -vp-counters-per-site=10.0 -fuse-ld=lld-14 -Wl,--build-id=sha1 -Wl,-z,relro CMakeFiles/cmTC_6af5a.dir/testCCompiler.c.o -o cmTC_6af5a && : ld.lld-14: error: cannot open /usr/lib/llvm-14/lib/clang/14.0.6/lib/linux/libclang_rt.profile-x86_64.a: No such file or directory clang: error: linker command failed with exit code 1 (use -v to see invocation) ninja: build stopped: subcommand failed. CMake will not be able to correctly generate this project. Call Stack (most recent call first): CMakeLists.txt:2 (project) -- Configuring incomplete, errors occurred!
Processed: clang-14 lost its (indirect) dependency on libclang-rt-14-dev
Processing control commands: > affects -1 src:halide Bug #1027939 [clang-14] clang-14 lost its (indirect) dependency on libclang-rt-14-dev Added indication that 1027939 affects src:halide -- 1027939: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027939 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1023365: prusa-slicer: Wrong wxWidgets Version linked during debian Build resulting in instant SIGSEGV on launch (due to lacking wxWidgets 3.2 support)
On Wed, Dec 28, 2022 at 12:55:20PM -0500, Scott Talbert wrote: > On Tue, 27 Dec 2022, Chow Loong Jin wrote: > > Alright, I'll leave the slic3r-prusa as-is then. I'm guessing that a > > binNMU will take care of things when we get there. > > wxwidgets3.2 has been rebuilt in unstable with EGL support disabled. The > release team skipped the binNMU of slic3r-prusa due to bug #1025827. If you > upload the (already merged) fix for that bug, that should take care of this > rebuild for slic3r-prusa too. Just a friendly note to highlight that slic3r-prusa needs an upload to re-enter testing, and the release freeze cut-off for re-entering testing is 2023-02-12: https://release.debian.org/testing/freeze_policy.html#summary I think a package needs to actually *migrate* by that cut-off date, so the upload deadline is really 2/5/10 days earlier depending on whether there are autopkgtests, etc. Best to upload well before that if possible as there can be delays, especially if some other maintainers are frantically uploading to try to get in before the freeze. The blockers on the wx3.2 side should now be resolved, but the FTBFS in #1025827 needs fixing. A fix for that seems to have already been merged to the git repo, so this just needs an upload. A maintainer upload would be best as there's nothing specific to wxwidgets3.2 to do. Cheers, Olly
Processed: tagging 1027934
Processing commands for cont...@bugs.debian.org: > tags 1027934 + ftbfs Bug #1027934 [libflann-dev] libflann-dev: pkg-config file now requires hdf5 but doesn't find it Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 1027934: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027934 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1027936: brian FTBFS with Python 3.11 as default version
Source: brian Version: 2.5.1-1 Severity: serious https://buildd.debian.org/status/fetch.php?pkg=brian=amd64=2.5.1-1%2Bb1=1672837036=0 ... Configuration error: There is a programmable error in your configuration file: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/sphinx/config.py", line 350, in eval_config_file exec(code, namespace) File "/<>/docs_sphinx/conf.py", line 71, in generate_examples.main(root_dir, target_dir) File "/<>/debian/tmp/usr/lib/python3.11/dist-packages/brian2/sphinxext/generate_examples.py", line 72, in main with codecs.open(fname, 'rU', encoding='utf-8') as f: ^^ File "", line 906, in open ValueError: invalid mode: 'rUb' ... Documenting 89 examples make[1]: *** [debian/rules:44: override_dh_auto_install] Error 2
Bug#1025000: marked as done (python-qtawesome: Includes non-source Font Awesome 5)
Your message dated Wed, 04 Jan 2023 20:50:28 + with message-id and subject line Bug#1025000: fixed in python-qtawesome 1.2.1+dfsg-1 has caused the Debian Bug report #1025000, regarding python-qtawesome: Includes non-source Font Awesome 5 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.) -- 1025000: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025000 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python-qtawesome-common Version: 1.1.1-1 Severity: serious Hi, This package contains three font files /usr/share/python-qtawesome/fonts/fontawesome5-*-webfont.ttf which are licensed freely but are not built from source and cannot be built from source (missing build system). #902981 has the details. Please repack the package to get rid of these files. Thanks, Bastian --- End Message --- --- Begin Message --- Source: python-qtawesome Source-Version: 1.2.1+dfsg-1 Done: Bastian Germann We believe that the bug you reported is fixed in the latest version of python-qtawesome, 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 1025...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bastian Germann (supplier of updated python-qtawesome 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, 04 Jan 2023 21:05:15 +0100 Source: python-qtawesome Architecture: source Version: 1.2.1+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Bastian Germann Closes: 1025000 Changes: python-qtawesome (1.2.1+dfsg-1) unstable; urgency=medium . * Team upload * Exclude fontawesome5 fonts (Closes: #1025000) * Replace excluded fonts with Fork Awesome * New upstream version 1.2.1+dfsg * Disable tests Checksums-Sha1: 293e1efb9624e0ff1a57d3ef3708d9ea09656ccb 2365 python-qtawesome_1.2.1+dfsg-1.dsc 1be2b61583bf96a03788906d6c950a02c6736a44 1552000 python-qtawesome_1.2.1+dfsg.orig.tar.xz a82f0696f5e9a138a030d90a839190f9a4589956 11440 python-qtawesome_1.2.1+dfsg-1.debian.tar.xz 2d85cc71e4795e6b5ad5c561512b242d822f4b92 13967 python-qtawesome_1.2.1+dfsg-1_source.buildinfo Checksums-Sha256: c3b21b1a5b054257e6e34c8088d0eefb74af59b990ce0107ef90246d9b336dea 2365 python-qtawesome_1.2.1+dfsg-1.dsc 271dfb2e4ab7d3584e644dfa3a928c8b4a9b4a482a2dad157121cbdd1fdb3ccb 1552000 python-qtawesome_1.2.1+dfsg.orig.tar.xz b37648eb2e2ad6f1cfd622504aa4dde6bea822ca40a92cbb63f7f057dd9efe01 11440 python-qtawesome_1.2.1+dfsg-1.debian.tar.xz 3613965056ca73ecb5edc95586cecd2f52498fb6f7a68df907509d4d0f21c5dc 13967 python-qtawesome_1.2.1+dfsg-1_source.buildinfo Files: 440fbfc709a9d06d42f999274d000d4a 2365 python optional python-qtawesome_1.2.1+dfsg-1.dsc 13be8bb5dd7a901eb5643830cf05bda2 1552000 python optional python-qtawesome_1.2.1+dfsg.orig.tar.xz 5cda409b629cdd6e72e709fd30453187 11440 python optional python-qtawesome_1.2.1+dfsg-1.debian.tar.xz c459db81b61033fc2903fe7d1b775e3b 13967 python optional python-qtawesome_1.2.1+dfsg-1_source.buildinfo -BEGIN PGP SIGNATURE- iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmO13bEQHGJhZ2VAZGVi aWFuLm9yZwAKCRAfXHqLRVZDFC/uDACx8LCRCX1nOP/zSdxYmlSnBSzC+yhEZP1Q FTZorDYgXf3FssZnlvocafcz55l8EdnmLCrnosOjlXcjtK46eLaxfAFFxuzKvPss ZPBWC1GYex9khk4nS5ySvtNY5b0OPpo6BUr3F0nmke8OLg268nDXbvAL1d58v/dm 97cBNNo43ugHdUgbHOpMiDH+Tko0gNFQ/6W2CqzF9rRVd1QAi5wwgpahMkuVb25l Pt+Bgr8L/lF0Qs3qUJfCtIcXaN3q3Ji1J37L+pHDG4gbPRYOqZnknVsnxykiPUCv wr/nb2MZOVnAnlYSPCwh2zOE3nk4OL39muP+jmjqsKPRSc42kRyFtnAwlT+ua5cn lxExnmFjwPwFo1jSC2SuQQ7Nzu9/RUtdgRqKBoezNDVNEFaJvkuEL58FLLt7FxV+ h7bCF376p0BfR8QhL2p9tXcSO4JcgvVLpzHPj6L7yGmfhwxK3V145ScKWwCIWAJs lUPO6p3OOqu1DHeN/AAaCKjMjkyzEFM= =Vwkj -END PGP SIGNATURE End Message ---
Bug#1019837: marked as done (treesheets: Please transition to wxwidgets3.2)
Your message dated Wed, 04 Jan 2023 20:51:12 + with message-id and subject line Bug#1019837: fixed in treesheets 1:1.0.2-1.1 has caused the Debian Bug report #1019837, regarding treesheets: Please transition to wxwidgets3.2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1019837: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019837 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: treesheets Severity: normal Control: block 1019416 by -1 Hi, Please transition treesheets from wxwidgets3.0 to wxwidgets3.2. wxWidgets 3.2 (a new API/ABI stable release) has been released a few months ago and is now packaged in unstable as wxwidgets3.2. Upstream has stopped supporting wxWidgets 3.0, so the Debian wx team would like to migrate all wx package users to wxwidgets3.2 for bullseye, with the plan to remove wxwidgets3.0 before release. For most packages, the transition should be as simple as changing Build-Depends from libwxgtk3.0-gtk3-dev to libwxgtk3.2-dev. Some packages may require small patches; I'm happy to help with those (and I have some already from working on this transition in Fedora already). Thanks, Scott --- End Message --- --- Begin Message --- Source: treesheets Source-Version: 1:1.0.2-1.1 Done: Olly Betts We believe that the bug you reported is fixed in the latest version of treesheets, 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 1019...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Olly Betts (supplier of updated treesheets 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, 05 Jan 2023 06:46:35 +1300 Source: treesheets Architecture: source Version: 1:1.0.2-1.1 Distribution: unstable Urgency: medium Maintainer: Ximin Luo Changed-By: Olly Betts Closes: 1019837 Changes: treesheets (1:1.0.2-1.1) unstable; urgency=medium . * Non-maintainer upload. * Update to use wxwidgets3.2. (Closes: #1019837) Checksums-Sha1: a44d2130016a86fbf3b07822e9b466252e64e2e7 1889 treesheets_1.0.2-1.1.dsc dcfef8f8e3f1a504ec38fbb7b3d0616386223a17 4868 treesheets_1.0.2-1.1.debian.tar.xz fcff2430b41d192048c738cdec0b020ddca4c553 12223 treesheets_1.0.2-1.1_amd64.buildinfo Checksums-Sha256: f1b5dc72ef3b9f6edd1db7bddd5690d9b03ec3abad9312048647c66465fa2d44 1889 treesheets_1.0.2-1.1.dsc 40c45154e487463c3167053bb2aacb4587b53edba06c34e6af5376ca917ab1ee 4868 treesheets_1.0.2-1.1.debian.tar.xz 2ed8e9d496af1a70919a3373103b640bb570c13406f7033c9126ff340405add0 12223 treesheets_1.0.2-1.1_amd64.buildinfo Files: 26827fa7acd45314ae55ebcfcee06f7b 1889 editors optional treesheets_1.0.2-1.1.dsc d6ba020e3a82af6a1dd3687d3a49dbab 4868 editors optional treesheets_1.0.2-1.1.debian.tar.xz d1c48c31ba1c33758ac951e4edb6861f 12223 editors optional treesheets_1.0.2-1.1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEECOJAD/f+j+3jrLUoGBR7BzutKwcFAmO124gACgkQGBR7Bzut KwdG4BAAojdu80UVgs4vl0SwokVIUfq3Ru7Ks59vLhe8yVc76Rwir5ekbw0aCERV /kAbA/iqB1Lz2Z8ARifovS3MXS1lU9EcXKvA0ep/bOVZi+d4MOUHZwUwZhI6DkN+ k0RDN/UdJMeAm4CxXjyDviBMefoM4BZ7EBwfWC4xabfNB0xf3bP8ICbTu3Q2n3Hw ocuzeEA0pUpow/RLw/DIO+NgsHRAanby7RpoSKx+SjtjHFo1sBkGiBP6YnWPG4Co JS+6Om22sEfH9mUTG1C33bSuEX8G+zzuVQR0Wl++P8PvkDf626qvVv+Y/ZiEyqsa UzSNFFDzDVoWoB5gZa+RwjMnFrijOiEYX7fNzT9lZRwz9exIz7ZC+zMe87wPYOyz cETNfLxzz+mVMo18RuTUBHJyiKmeIvXadqnBIZ4NqUp0sZRZbTEqdkCEEYbJKWwc YsaZ3DzVONaxQgOlWs3tpMHEHTB0SNtG43aSWEVQt5oxsoPblsyvt0tKXi67WBZZ DwbU/f7wuPfXXtCrRxtgDgmdL7Vm+gHkTYYXpeYBs/YQI+HxDHYh2rUjJ9xQFxUx lDiXqtqqr50rSX2xdnGkC3mUesi2470KvZSrrIuLSVVuC1F4xpCUBNoj/Qlmq/62 X5jHE5Ds9oQmJfnWsvln4HrMilH2DC3NXLz1YjifAPQvOG2zpcw= =3cPy -END PGP SIGNATURE End Message ---
Bug#1026294: vip-manager: FTBFS: cannot use c.VIP (variable of type net.IP) as type netip.Addr in argument to arp.NewPacket
Hi, On Sat, Dec 17, 2022 at 10:08:45PM +, Mathias Gibbens wrote: > Source: vip-manager > Version: 1.0.2-3 > Severity: serious > Justification: FTBFS > Tags: bookworm sid ftbfs > > vip-manager is failing to build in a clean sid schroot: > > > github.com/cybertec-postgresql/vip-manager/ipmanager > > # github.com/cybertec-postgresql/vip-manager/ipmanager > > src/github.com/cybertec-postgresql/vip-manager/ipmanager/basicConfigurer_linux.go:101:3: > > cannot use c.VIP (variable of type net.IP) as type netip.Addr in argument > > to arp.NewPacket > > src/github.com/cybertec-postgresql/vip-manager/ipmanager/basicConfigurer_linux.go:103:3: > > cannot use c.VIP (variable of type net.IP) as type netip.Addr in argument > > to arp.NewPacket > > src/github.com/cybertec-postgresql/vip-manager/ipmanager/basicConfigurer_linux.go:125:3: > > cannot use c.VIP (variable of type net.IP) as type netip.Addr in argument > > to arp.NewPacket > > src/github.com/cybertec-postgresql/vip-manager/ipmanager/basicConfigurer_linux.go:127:3: > > cannot use c.VIP (variable of type net.IP) as type netip.Addr in argument > > to arp.NewPacket This is due to an update in golang-github-mdlayher-arp-dev that pulled in this: https://github.com/mdlayher/arp/commit/6706a2966875c189c24afd003ffe801ff69542a1 Michael
Bug#1019790: eviacam: diff for NMU version 2.1.4-2.1
On Wed, Nov 09, 2022 at 11:44:29PM +, Olly Betts wrote: > On Wed, Nov 09, 2022 at 04:49:33PM +0100, Cesar Mauri wrote: > > I've just merged a PR that add support for OpenCV 4.6.0 and (hopefully) > > fixes the camera error > > > > https://github.com/cmauri/eviacam/tree/master > > Great. Will there be a new upstream release soon? Just a friendly note to highlight that eviacam needs updating to wxwidgets3.2 to re-enter testing, and the release freeze cut-off for re-entering testing is 2023-02-12: https://release.debian.org/testing/freeze_policy.html#summary I think a package needs to actually *migrate* by that cut-off date, so the upload deadline is really 2/5/10 days earlier depending on whether there are autopkgtests, etc. Best to upload well before that if possible as there can be delays, especially if some other maintainers are frantically uploading to try to get in before the freeze. I can't test the patch I attached earlier due to the other bug. If that bug is specific to some webcams/systems I could NMU the patch without testing if you think that's useful (let me know). I'm hesitant to try applying the PR too as I'm not at all familiar with this package, - it seems better for the maintainer to do that. Cheers, Olly
Bug#1025000: python-qtawesome: Includes non-source Font Awesome 5
I have replaced Font Awesome 5 with Fork Awesome and have tested it with finalcif. The icons look a bit different but it works.
Bug#1027112: bazel-bootstrap: /usr/include/absl/synchronization/mutex.h:550: error: undefined reference to 'absl::debian3::Mutex::Unlock()'
Hi there, On 1/4/23 09:51, Gianfranco Costamagna wrote: Hello, FWIW I think I crafted a patch that might fix the issue (in a ugly and hard-coded way) Thanks! It's always good to have options. --- bazel-bootstrap-4.2.3+ds.orig/tools/distributions/debian/debian_cc.BUILD +++ bazel-bootstrap-4.2.3+ds/tools/distributions/debian/debian_cc.BUILD @@ -39,6 +39,6 @@ cc_library( # libgrpc++-dev cc_library( name = "grpc++_unsecure", - linkopts = ["-lgrpc++_unsecure", "-lgrpc_unsecure", "-lgpr"], + linkopts = ["-lgrpc++_unsecure", "-lgrpc_unsecure", "-lgpr", "-labsl_throw_delegate", "-labsl_raw_logging_internal", "-labsl_str_format_internal", "-labsl_synchronization", "-labsl_log_severity"], visibility = ["//visibility:public"], ) Ah, I see. So you added the missing absl_synchronization linker flag to the bazel-bootstrap build process. I'm really curious to see if this works because from my (admittedly inexperienced) troubleshooting the problems seemed to be in the grpc package[1]. I just uploaded it in Ubuntu, lets see how the build goes. Well, I didn't have to wait long. From what I can see that build succeeded! Can you tell me if the autopkgtest succeeded? -Olek [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026937#15 OpenPGP_signature Description: OpenPGP digital signature
Bug#1019837: treesheets: diff for NMU version 1:1.0.2-1.1
Control: tags 1019837 + patch Dear maintainer, I've prepared an NMU for treesheets (versioned as 1:1.0.2-1.1) and uploaded it to unstable as per the NMU guidelines in the devref: https://www.debian.org/doc/manuals/developers-reference/pkgs.html#nmu-guidelines The package built with wxWidgets 3.2 without changes, and seems to run without problems (I worked through the tutorial it loads by default, and tried to exercise various windows from the menus). I'll open an MR on salsa with the changes too. Cheers, Olly diff -Nru treesheets-1.0.2/debian/changelog treesheets-1.0.2/debian/changelog --- treesheets-1.0.2/debian/changelog 2019-12-01 10:56:34.0 +1300 +++ treesheets-1.0.2/debian/changelog 2023-01-05 06:46:35.0 +1300 @@ -1,3 +1,10 @@ +treesheets (1:1.0.2-1.1) unstable; urgency=medium + + * Non-maintainer upload. + * Update to use wxwidgets3.2. (Closes: #1019837) + + -- Olly Betts Thu, 05 Jan 2023 06:46:35 +1300 + treesheets (1:1.0.2-1) unstable; urgency=medium * New upstream release. diff -Nru treesheets-1.0.2/debian/control treesheets-1.0.2/debian/control --- treesheets-1.0.2/debian/control 2019-12-01 05:24:15.0 +1300 +++ treesheets-1.0.2/debian/control 2023-01-05 06:46:21.0 +1300 @@ -4,8 +4,7 @@ Maintainer: Ximin Luo Build-Depends: debhelper (>= 9), cmake, - libwxgtk3.0-gtk3-dev, - wx3.0-headers, + libwxgtk3.2-dev, imagemagick Standards-Version: 4.3.0 Homepage: http://strlen.com/treesheets/
Processed: treesheets: diff for NMU version 1:1.0.2-1.1
Processing control commands: > tags 1019837 + patch Bug #1019837 [src:treesheets] treesheets: Please transition to wxwidgets3.2 Added tag(s) patch. -- 1019837: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019837 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1027934: libflann-dev: pkg-config file now requires hdf5 but doesn't find it
Package: libflann-dev Version: 1.9.2+dfsg-1 Severity: serious Control: affects -1 src:hugin https://buildd.debian.org/status/fetch.php?pkg=hugin=amd64=2022.0.0%2Bdfsg-1%2Bb2=1672840532=0 ... /usr/bin/c++ -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -Wdate-time -D_FORTIFY_SOURCE=2 -Wl,-z,relro -Wl,-z,now -Wl,--as-needed -Wl,-z,defs -fopenmp CMakeFiles/cpfind.dir/PanoDetector.cpp.o CMakeFiles/cpfind.dir/PanoDetectorLogic.cpp.o CMakeFiles/cpfind.dir/TestCode.cpp.o CMakeFiles/cpfind.dir/Utils.cpp.o CMakeFiles/cpfind.dir/main.cpp.o -o cpfind -Wl,-rpath,/<>/obj-x86_64-linux-gnu/src/hugin_cpfind/localfeatures:/<>/obj-x86_64-linux-gnu/src/celeste:/<>/obj-x86_64-linux-gnu/src/hugin_base: ../localfeatures/liblocalfeatures.so.0.0 /usr/lib/x86_64-linux-gnu/libvigraimpex.so /usr/lib/x86_64-linux-gnu/libOpenEXR.so /usr/lib/x86_64-linux-gnu/libImath-3_1.so /usr/lib/x86_64-linux-gnu/libIex-3_1.so /usr/lib/x86_64-linux-gnu/libIlmThread-3_1.so /usr/lib/x86_64-linux-gnu/libz.so /usr/lib/x86_64-linux-gnu/libjpeg.so /usr/lib/x86_64-linux-gnu/libtiff.so /usr/lib/x86_64-linux-gnu/libpng.so /usr/lib/x86_64-linux-gnu/libz.so /usr/lib/x86_64-linux-gnu/libz.so /usr/lib/x86_64-linux-gnu/libexiv2.so /usr/lib/x86_64-linux-gnu/libpano13.so ../../foreign/levmar/libhuginlevmar.a /usr/lib/x86_64-linux-gnu/libGLEW.so /usr/lib/x86_64-linux-gnu/libfftw3.so /usr/lib/x86_64-linux-gnu/libvigraimpex.so /usr/lib/x86_64-linux-gnu/libOpenEXR.so /usr/lib/x86_64-linux-gnu/libImath-3_1.so /usr/lib/x86_64-linux-gnu/libIex-3_1.so /usr/lib/x86_64-linux-gnu/libIlmThread-3_1.so /usr/lib/x86_64-linux-gnu/libz.so /usr/lib/x86_64-linux-gnu/libjpeg.so /usr/lib/x86_64-linux-gnu/libtiff.so /usr/lib/x86_64-linux-gnu/libpng.so /usr/lib/x86_64-linux-gnu/libz.so /usr/lib/x86_64-linux-gnu/libz.so /usr/lib/x86_64-linux-gnu/libexiv2.so /usr/lib/x86_64-linux-gnu/liblcms2.so ../../celeste/libceleste.so.0.0 -lflann -lflann_cpp -lhdf5 -lmpi -llz4 ../../hugin_base/libhuginbase.so.0.0 /usr/lib/x86_64-linux-gnu/libX11.so /usr/lib/x86_64-linux-gnu/libOpenGL.so /usr/lib/x86_64-linux-gnu/libGLX.so /usr/lib/x86_64-linux-gnu/libGLU.so /usr/lib/x86_64-linux-gnu/libsqlite3.so /usr/lib/x86_64-linux-gnu/libpano13.so ../../foreign/levmar/libhuginlevmar.a /usr/lib/x86_64-linux-gnu/libGLEW.so /usr/lib/x86_64-linux-gnu/libboost_filesystem.so.1.74.0 /usr/lib/x86_64-linux-gnu/libboost_system.so.1.74.0 /usr/lib/x86_64-linux-gnu/libfftw3.so /usr/lib/x86_64-linux-gnu/libvigraimpex.so /usr/lib/x86_64-linux-gnu/libOpenEXR.so /usr/lib/x86_64-linux-gnu/libImath-3_1.so /usr/lib/x86_64-linux-gnu/libIex-3_1.so /usr/lib/x86_64-linux-gnu/libIlmThread-3_1.so /usr/lib/x86_64-linux-gnu/libz.so /usr/lib/x86_64-linux-gnu/libjpeg.so /usr/lib/x86_64-linux-gnu/libpng.so /usr/lib/x86_64-linux-gnu/libz.so /usr/lib/x86_64-linux-gnu/libjpeg.so /usr/lib/x86_64-linux-gnu/libpng.so /usr/lib/x86_64-linux-gnu/libtiff.so /usr/lib/x86_64-linux-gnu/libexiv2.so /usr/lib/x86_64-linux-gnu/liblcms2.so /usr/bin/ld: cannot find -lhdf5: No such file or directory collect2: error: ld returned 1 exit status make[3]: *** [src/hugin_cpfind/cpfind/CMakeFiles/cpfind.dir/build.make:221: src/hugin_cpfind/cpfind/cpfind] Error 1 Relevant /usr/lib/x86_64-linux-gnu/pkgconfig/flann.pc diff: │ │ │ -Version: 1.9.1 │ │ │ -Requires: liblz4 │ │ │ +Version: 1.9.2 │ │ │ +Requires: hdf5 liblz4 $ pkgconf --libs flann -L/usr/lib/x86_64-linux-gnu\;-llz4 -lflann -lflann_cpp -L/usr/lib/x86_64-linux-gnu/hdf5/openmpi -lhdf5 -L/usr/lib/x86_64-linux-gnu/openmpi/lib -lmpi -llz4 $ dpkg -S libhdf5.so libhdf5-openmpi-dev: /usr/lib/x86_64-linux-gnu/hdf5/openmpi/libhdf5.so $
Processed: libflann-dev: pkg-config file now requires hdf5 but doesn't find it
Processing control commands: > affects -1 src:hugin Bug #1027934 [libflann-dev] libflann-dev: pkg-config file now requires hdf5 but doesn't find it Added indication that 1027934 affects src:hugin -- 1027934: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027934 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1027925: spamassassin FTBFS on IPV6-only buildds
On Wed, 2023-01-04 at 18:31 +, Adam D. Barratt wrote: > One difference at least is that "IPv6-only" buildds *do* have IPv4 > networking, but only on lo. As a result, your have_inet4 test will > return true: > > adsb@x86-conova-01:~$ ip --brief -4 a > lo UNKNOWN127.0.0.1/8 > > adsb@x86-conova-01:~$ perl -MIO::Socket::INET -e '$sock = > IO::Socket::INET->new(LocalAddr => "127.0.0.1", Proto => "udp");' -e > 'print $sock ? "true\n" : "false\n";' > true > > https://lists.debian.org/debian-devel/2020/07/msg00070.html is a > discussion of the general issue from a couple of years ago, which > actually includes spamassassin in its list of affected packages. Looking at the source, I think the issue is that spamd is calling ip_or_name_to_ip_addresses() on the IP address, which in turn is passing AI_ADDRCONFIG to getaddrinfo(), which will fail on a system configured in such a way, as it does not consider loopback addresses. https://salsa.debian.org/perl-team/interpreter/perl/-/commit/425d71c741280e5c7d61b8895993e39b0c6c7ca4 is how a similar issue there was solved, if it's useful. Regards, Adam
Processed: Re: Bug#1024036: nipy FTBFS with Python 3.11 as supported version
Processing control commands: > severity -1 serious Bug #1024036 [src:nipy] nipy FTBFS with Python 3.11 as supported version Severity set to 'serious' from 'important' -- 1024036: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024036 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: spaln: FTBFS: dbs.cc:568:54: error: cannot convert ‘gzFile’ {aka ‘gzFile_s*’} to ‘FILE*’
Processing control commands:
> tags -1 upstream
Bug #1026576 [src:spaln] spaln: FTBFS: dbs.cc:568:54: error: cannot convert
‘gzFile’ {aka ‘gzFile_s*’} to ‘FILE*’
Added tag(s) upstream.
> forwarded -1 https://github.com/ogotoh/spaln/issues/58
Bug #1026576 [src:spaln] spaln: FTBFS: dbs.cc:568:54: error: cannot convert
‘gzFile’ {aka ‘gzFile_s*’} to ‘FILE*’
Set Bug forwarded-to-address to 'https://github.com/ogotoh/spaln/issues/58'.
--
1026576: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026576
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1026576: spaln: FTBFS: dbs.cc:568:54: error: cannot convert ‘gzFile’ {aka ‘gzFile_s*’} to ‘FILE*’
Control: tags -1 upstream Control: forwarded -1 https://github.com/ogotoh/spaln/issues/58
Bug#1013156: marked as done (gdcm: vtk[6,7] removal)
Your message dated Wed, 04 Jan 2023 19:00:11 + with message-id and subject line Bug#1013156: fixed in gdcm 3.0.17-5 has caused the Debian Bug report #1013156, regarding gdcm: vtk[6,7] removal 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.) -- 1013156: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013156 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gdcm Severity: important User: gl...@debian.org Usertags: vtk6_vtk7_removal Dear maintainer, Debian archive has now three major versions of the VTK (The Visualization Toolkit) package: vtk6, vtk7 and vtk9. Old vesions (vtk6 and vtk7) are not supported by upstream and the package itself is not easy for the mainance. We aim to drop old and deprecated version vtk6 and vtk7 packages before the freeze of the Debian 12 Bookworm. The severity of this ticket will be raised to serious some time for the freeze. Your package depends on vtk6 or vtk7. Thus we ask you to migrate it to the latest vtk9 package. Thanks Anton --- End Message --- --- Begin Message --- Source: gdcm Source-Version: 3.0.17-5 Done: Mathieu Malaterre We believe that the bug you reported is fixed in the latest version of gdcm, 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 1013...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mathieu Malaterre (supplier of updated gdcm 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: Mon, 02 Jan 2023 10:00:45 +0100 Source: gdcm Binary: gdcm-doc libgdcm-cil libgdcm-cil-dbgsym libgdcm-dev libgdcm-java libgdcm-java-dbgsym libgdcm-tools libgdcm-tools-dbgsym libgdcm3.0 libgdcm3.0-dbgsym libvtkgdcm-9.1 libvtkgdcm-9.1-dbgsym libvtkgdcm-dev libvtkgdcm-tools libvtkgdcm-tools-dbgsym python3-gdcm python3-gdcm-dbgsym python3-vtkgdcm python3-vtkgdcm-dbgsym Architecture: source all amd64 Version: 3.0.17-5 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Mathieu Malaterre Description: gdcm-doc - Grassroots DICOM documentation libgdcm-cil - Grassroots DICOM CLI bindings libgdcm-dev - Grassroots DICOM development libraries and headers libgdcm-java - Grassroots DICOM Java bindings libgdcm-tools - Grassroots DICOM tools and utilities libgdcm3.0 - Grassroots DICOM runtime libraries libvtkgdcm-9.1 - Grassroots DICOM VTK runtime libraries libvtkgdcm-dev - Grassroots DICOM VTK development libraries and headers libvtkgdcm-tools - Grassroots DICOM VTK tools and utilities python3-gdcm - Grassroots DICOM Python bindings python3-vtkgdcm - Grassroots DICOM VTK/Python bindings Closes: 1013156 Changes: gdcm (3.0.17-5) unstable; urgency=medium . [ Andreas Tille ] * Switch to VTK9 and drop bindings for vtk for C# and Java Closes: #1013156 * Build-Depends: default-jdk-headless . [ Mathieu Malaterre ] * Team upload. * d/rules: Do not build VTK documentation. Closes: #1013156 * d/control: Finish transition to VTK9 Checksums-Sha1: 985ac866d240cc97d10f69f0d21464811c84f37a 3551 gdcm_3.0.17-5.dsc 02d7541341a0257880ab465516358136af9f07aa 277608 gdcm_3.0.17-5.debian.tar.xz 2b5df645a9d5e6b309a8c1feb097950d57335886 14309420 gdcm-doc_3.0.17-5_all.deb 2556ad36a5973679da73d846c6ad2bee30e9ce32 41972 gdcm_3.0.17-5_amd64.buildinfo c99fcc3c7a32345114f604c4c8000e06582d2d1c 2265164 libgdcm-cil-dbgsym_3.0.17-5_amd64.deb ab998cd088d21a238d7013f4234cb87d0aeb8db5 296236 libgdcm-cil_3.0.17-5_amd64.deb 812c8d3524578be20afb308c17f6100a25c97d00 263996 libgdcm-dev_3.0.17-5_amd64.deb d2bd2f3cc7720173df07bef796bb6b9a8765c19b 2496528 libgdcm-java-dbgsym_3.0.17-5_amd64.deb c5a8b65ae2470396a4a5bf7550ed56280830b4ee 617476 libgdcm-java_3.0.17-5_amd64.deb 2187b0db9be21ccfe6bf42d3e8752caa402006fb 3823092 libgdcm-tools-dbgsym_3.0.17-5_amd64.deb 9018c96deec1b7bad425f0d4aa532f7867fcdc12 475548 libgdcm-tools_3.0.17-5_amd64.deb 96618bc67712cbdb53ed068acc56d4201b198098 24134996 libgdcm3.0-dbgsym_3.0.17-5_amd64.deb ef3dca8b2e22bcebfc2540f4374ee8f0b6675c4a 2241064 libgdcm3.0_3.0.17-5_amd64.deb 569d049c877d16f266f566b124c735776c63bcd6 1879984 libvtkgdcm-9.1-dbgsym_3.0.17-5_amd64.deb
Bug#1027847: marked as done (libsigrokdecode FTBFS with Python 3.11 as default version)
Your message dated Wed, 04 Jan 2023 18:39:57 + with message-id and subject line Bug#1027847: fixed in libsigrokdecode 0.5.3-4 has caused the Debian Bug report #1027847, regarding libsigrokdecode FTBFS with Python 3.11 as default version 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.) -- 1027847: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027847 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libsigrokdecode Version: 0.5.3-3 Severity: serious https://buildd.debian.org/status/fetch.php?pkg=libsigrokdecode=amd64=0.5.3-3%2Bb1=1672741924=0 ... Detected libraries (required): - glib-2.0 >= 2.34 2.74.4 - python-3.10-embed... no - python-3.9-embed no - python-3.8-embed no ... /bin/bash ./libtool --tag=CC --mode=link gcc -std=c99 -fvisibility=hidden -Wall -Wextra -Wmissing-prototypes -Wshadow -Wformat=2 -Wno-format-nonliteral -Wfloat-equal -pthread -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/python3.11 -I/usr/include/x86_64-linux-gnu/python3.11 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro -Wl,--as-needed -o tests/main tests/main-main.o tests/main-core.o tests/main-decoder.o tests/main-inst.o tests/main-session.o libsigrokdecode.la -lm -lcheck_pic -lrt -lm -lsubunit -lglib-2.0 libtool: link: gcc -std=c99 -fvisibility=hidden -Wall -Wextra -Wmissing-prototypes -Wshadow -Wformat=2 -Wno-format-nonliteral -Wfloat-equal -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/python3.11 -I/usr/include/x86_64-linux-gnu/python3.11 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wl,-z -Wl,relro -Wl,--as-needed -o tests/.libs/main tests/main-main.o tests/main-core.o tests/main-decoder.o tests/main-inst.o tests/main-session.o ./.libs/libsigrokdecode.so -lcheck_pic -lrt -lm -lsubunit -lglib-2.0 -pthread /usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to `PyList_Insert' /usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to `PyModule_AddObject' /usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to `PySys_GetObject' /usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to `PyDict_SetItemString' /usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to `PyType_GenericNew' /usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to `PyImport_Import' /usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to `PyList_GetItem' /usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to `PyBytes_AsStringAndSize' /usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to `PyObject_CallMethod' /usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to `PyGILState_Release' /usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to `PyBytes_Size' /usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to `PyBool_FromLong' /usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to `PyUnicode_FromString' /usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to `PyObject_CallFunctionObjArgs' /usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to `PyExc_TypeError' /usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to `Py_InitializeEx' /usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to `PyExc_Exception' /usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to `PyObject_Str' /usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to `PyDict_Next' /usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to `PyLong_AsLong' /usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to `PyModule_AddIntConstant' /usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to `PyErr_Format' /usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to `PyFloat_FromDouble' /usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to `PyArg_ParseTuple' /usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to `PyErr_Occurred' /usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to `PySet_Pop' /usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to `PyObject_IsSubclass' /usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to `PyArg_ParseTupleAndKeywords' /usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to `PyFloat_Type' /usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to `PyExc_IndexError' /usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference
Bug#1027925: spamassassin FTBFS on IPV6-only buildds
On Wed, 2023-01-04 at 10:01 -0800, Noah Meyerhans wrote: > On Wed, Jan 04, 2023 at 06:58:30PM +0200, Adrian Bunk wrote: > > https://buildd.debian.org/status/logs.php?pkg=spamassassin=amd64 > > > > ... > > Jan 4 03:57:23.254 [3488924] dbg: logger: adding facilities: all > > Jan 4 03:57:23.255 [3488924] dbg: logger: logging level is DBG > > Jan 4 03:57:23.257 [3488924] dbg: logger: successfully opened file > > log/sa_check_spamd.g3uk5R/d.sa_check_spamd/spamd.err.0.timestamped > > Jan 4 03:57:23.257 [3488924] dbg: logger: successfully added file > > method > > Jan 4 03:57:23.257 [3488924] dbg: spamd: will perform setuids? 0 > > Jan 4 03:57:23.257 [3488924] dbg: spamd: socket module of choice: > > IO::Socket::IP 0.41, Socket 2.033, have PF_INET, have PF_INET6, > > using legacy Socket6::getaddrinfo, AI_ADDRCONFIG is supported > > Jan 4 03:57:23.257 [3488924] dbg: spamd: socket specification: > > "127.0.0.1", IP address: 127.0.0.1, port: 61558 > > server socket setup failed, retry 1: spamd: invalid address for a > > listen socket: "127.0.0.1": Address family for hostname not > > supported > > [...] > I haven't been able to reproduce this on VMs with IPv6-only > networking. > Is the buildd network environment documented anywhere? There's > clearly > something different about it than my test environment, but I haven't > been able to figure out what it is. > > In the meantime, I'm looking into printing more information about the > Network configuration when running these failing tests. See > https://salsa.debian.org/debian/spamassassin/-/commit/531bf8ea45cde94a60852d62ac701f70c0db4b3d > > On my IPv6-only build host, these changes print: > IP-DEBUG: have_inet4 returning false > IP-DEBUG: have_inet6 returning true > IP-DEBUG: Set spamdlocalhost to ::1 > IP-DEBUG: Set spamdhost to ::1 > > > noahm@localhost:~/spamassassin$ ip -4 addr ; ip -4 ro ; dpkg- > buildpackage -uc -us > /tmp/build.log 2>&1 > One difference at least is that "IPv6-only" buildds *do* have IPv4 networking, but only on lo. As a result, your have_inet4 test will return true: adsb@x86-conova-01:~$ ip --brief -4 a lo UNKNOWN127.0.0.1/8 adsb@x86-conova-01:~$ perl -MIO::Socket::INET -e '$sock = IO::Socket::INET->new(LocalAddr => "127.0.0.1", Proto => "udp");' -e 'print $sock ? "true\n" : "false\n";' true https://lists.debian.org/debian-devel/2020/07/msg00070.html is a discussion of the general issue from a couple of years ago, which actually includes spamassassin in its list of affected packages. Regards, Adam
Bug#1027925: spamassassin FTBFS on IPV6-only buildds
On Wed, Jan 04, 2023 at 06:58:30PM +0200, Adrian Bunk wrote:
> https://buildd.debian.org/status/logs.php?pkg=spamassassin=amd64
>
> ...
> Jan 4 03:57:23.254 [3488924] dbg: logger: adding facilities: all
> Jan 4 03:57:23.255 [3488924] dbg: logger: logging level is DBG
> Jan 4 03:57:23.257 [3488924] dbg: logger: successfully opened file
> log/sa_check_spamd.g3uk5R/d.sa_check_spamd/spamd.err.0.timestamped
> Jan 4 03:57:23.257 [3488924] dbg: logger: successfully added file method
> Jan 4 03:57:23.257 [3488924] dbg: spamd: will perform setuids? 0
> Jan 4 03:57:23.257 [3488924] dbg: spamd: socket module of choice:
> IO::Socket::IP 0.41, Socket 2.033, have PF_INET, have PF_INET6, using legacy
> Socket6::getaddrinfo, AI_ADDRCONFIG is supported
> Jan 4 03:57:23.257 [3488924] dbg: spamd: socket specification: "127.0.0.1",
> IP address: 127.0.0.1, port: 61558
> server socket setup failed, retry 1: spamd: invalid address for a listen
> socket: "127.0.0.1": Address family for hostname not supported
> server socket setup failed, retry 2: spamd: invalid address for a listen
> socket: "127.0.0.1": Address family for hostname not supported
> server socket setup failed, retry 3: spamd: invalid address for a listen
> socket: "127.0.0.1": Address family for hostname not supported
> server socket setup failed, retry 4: spamd: invalid address for a listen
> socket: "127.0.0.1": Address family for hostname not supported
> server socket setup failed, retry 5: spamd: invalid address for a listen
> socket: "127.0.0.1": Address family for hostname not supported
> server socket setup failed, retry 6: spamd: invalid address for a listen
> socket: "127.0.0.1": Address family for hostname not supported
> server socket setup failed, retry 7: spamd: invalid address for a listen
> socket: "127.0.0.1": Address family for hostname not supported
> server socket setup failed, retry 8: spamd: invalid address for a listen
> socket: "127.0.0.1": Address family for hostname not supported
> server socket setup failed, retry 9: spamd: invalid address for a listen
> socket: "127.0.0.1": Address family for hostname not supported
> spamd: invalid address for a listen socket: "127.0.0.1": Address family for
> hostname not supported
> ...
> Failed 30/213 test programs. 162/3101 subtests failed.
> make[2]: *** [Makefile:1473: test_dynamic] Error 255
I haven't been able to reproduce this on VMs with IPv6-only networking.
Is the buildd network environment documented anywhere? There's clearly
something different about it than my test environment, but I haven't
been able to figure out what it is.
In the meantime, I'm looking into printing more information about the
Network configuration when running these failing tests. See
https://salsa.debian.org/debian/spamassassin/-/commit/531bf8ea45cde94a60852d62ac701f70c0db4b3d
On my IPv6-only build host, these changes print:
IP-DEBUG: have_inet4 returning false
IP-DEBUG: have_inet6 returning true
IP-DEBUG: Set spamdlocalhost to ::1
IP-DEBUG: Set spamdhost to ::1
noahm@localhost:~/spamassassin$ ip -4 addr ; ip -4 ro ; dpkg-buildpackage -uc
-us > /tmp/build.log 2>&1
echo $?
tail -n20 /tmp/build.log
noahm@localhost:~/spamassassin$ echo $?
0
noahm@localhost:~/spamassassin$ tail -n20 /tmp/build.log
dh_makeshlibs -a
dh_shlibdeps -a
dh_installdeb
dh_gencontrol
dpkg-gencontrol: warning: package spamassassin: substitution variable
${perl:Depends} unused, but is defined
dpkg-gencontrol: warning: package sa-compile: substitution variable
${perl:Depends} unused, but is defined
dpkg-gencontrol: warning: Depends field of package spamd: substitution variable
${shlibs:Depends} used, but is not defined
dpkg-gencontrol: warning: package spamd: substitution variable ${perl:Depends}
unused, but is defined
dh_md5sums
dh_builddeb
dpkg-deb: building package 'spamassassin' in '../spamassassin_4.0.0-3_all.deb'.
dpkg-deb: building package 'spamc' in '../spamc_4.0.0-3_amd64.deb'.
dpkg-deb: building package 'spamc-dbgsym' in
'../spamc-dbgsym_4.0.0-3_amd64.deb'.
dpkg-deb: building package 'sa-compile' in '../sa-compile_4.0.0-3_all.deb'.
dpkg-deb: building package 'spamd' in '../spamd_4.0.0-3_all.deb'.
dpkg-genbuildinfo -O../spamassassin_4.0.0-3_amd64.buildinfo
dpkg-genchanges -O../spamassassin_4.0.0-3_amd64.changes
dpkg-genchanges: info: not including original source code in upload
dpkg-source --after-build .
dpkg-buildpackage: info: binary and diff upload (original source NOT included)
Processed: src:xml2rfc: fails to migrate to testing for too long: autopkgtest regression
Processing control commands: > close -1 3.15.2-1 Bug #1027930 [src:xml2rfc] src:xml2rfc: fails to migrate to testing for too long: autopkgtest regression Marked as fixed in versions xml2rfc/3.15.2-1. Bug #1027930 [src:xml2rfc] src:xml2rfc: fails to migrate to testing for too long: autopkgtest regression Marked Bug as done -- 1027930: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027930 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1027930: src:xml2rfc: fails to migrate to testing for too long: autopkgtest regression
Source: xml2rfc Version: 3.13.1-1 Severity: serious Control: close -1 3.15.2-1 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:xml2rfc has been trying to migrate for 61 days [2]. Hence, I am filing this bug. Your package is blocked because the autopkgtest regressed on all architectures we run it on. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bookworm, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=xml2rfc OpenPGP_signature Description: OpenPGP digital signature
Processed: src:r-cran-xts: fails to migrate to testing for too long: autopkgtest regression
Processing control commands:
> close -1 0.12.2-1
Bug #1027929 [src:r-cran-xts] src:r-cran-xts: fails to migrate to testing for
too long: autopkgtest regression
Marked as fixed in versions r-cran-xts/0.12.2-1.
Bug #1027929 [src:r-cran-xts] src:r-cran-xts: fails to migrate to testing for
too long: autopkgtest regression
Marked Bug as done
> block -1 by 1024012
Bug #1027929 {Done: Paul Gevers } [src:r-cran-xts]
src:r-cran-xts: fails to migrate to testing for too long: autopkgtest regression
1027929 was not blocked by any bugs.
1027929 was not blocking any bugs.
Added blocking bug(s) of 1027929: 1024012
--
1027929: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027929
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1027929: src:r-cran-xts: fails to migrate to testing for too long: autopkgtest regression
Source: r-cran-xts Version: 0.12.1-1 Severity: serious Control: close -1 0.12.2-1 Tags: sid bookworm User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 1024012 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:r-cran-xts has been trying to migrate for 61 days [2]. Hence, I am filing this bug. The migration is blocked by an autopkgtest regression reported in bug 1024012. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bookworm, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=r-cran-xts OpenPGP_signature Description: OpenPGP digital signature
Bug#1027594: marked as done (golang-github-linuxdeepin-go-dbus-factory: FTBFS: make[2]: *** [Makefile:15: bin] Error 1)
Your message dated Wed, 04 Jan 2023 17:35:41 + with message-id and subject line Bug#1027594: fixed in golang-github-linuxdeepin-go-dbus-factory 1.9.6-3 has caused the Debian Bug report #1027594, regarding golang-github-linuxdeepin-go-dbus-factory: FTBFS: make[2]: *** [Makefile:15: bin] Error 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.) -- 1027594: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027594 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: golang-github-linuxdeepin-go-dbus-factory Version: 1.9.6-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230101 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[2]: Entering directory > '/<>/_build/src/github.com/linuxdeepin/go-dbus-factory' > go build -o generator _tool/generator/*.go > ../../../pkg.deepin.io/lib/utils/schemas.go:24:2: cannot find package > "pkg.deepin.io/gir/gio-2.0" in any of: > /usr/lib/go-1.19/src/pkg.deepin.io/gir/gio-2.0 (from $GOROOT) > /<>/_build/src/pkg.deepin.io/gir/gio-2.0 (from $GOPATH) > /usr/share/gocode/src/pkg.deepin.io/gir/gio-2.0 > ../../../pkg.deepin.io/lib/utils/keyfile.go:27:2: cannot find package > "pkg.deepin.io/gir/glib-2.0" in any of: > /usr/lib/go-1.19/src/pkg.deepin.io/gir/glib-2.0 (from $GOROOT) > /<>/_build/src/pkg.deepin.io/gir/glib-2.0 (from $GOPATH) > /usr/share/gocode/src/pkg.deepin.io/gir/glib-2.0 > make[2]: *** [Makefile:15: bin] Error 1 The full build log is available from: http://qa-logs.debian.net/2023/01/01/golang-github-linuxdeepin-go-dbus-factory_1.9.6-2_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230101;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230101=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: golang-github-linuxdeepin-go-dbus-factory Source-Version: 1.9.6-3 Done: Arun Kumar Pariyar We believe that the bug you reported is fixed in the latest version of golang-github-linuxdeepin-go-dbus-factory, 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 1027...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Arun Kumar Pariyar (supplier of updated golang-github-linuxdeepin-go-dbus-factory 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, 04 Jan 2023 22:25:48 +0545 Source: golang-github-linuxdeepin-go-dbus-factory Architecture: source Version: 1.9.6-3 Distribution: unstable Urgency: medium Maintainer: Arun Kumar Pariyar Changed-By: Arun Kumar Pariyar Closes: 1027594 Changes: golang-github-linuxdeepin-go-dbus-factory (1.9.6-3) unstable; urgency=medium . * Add patch to change go-lib import path. (Closes: #1027594) * debian/control: Bump Standards version to 4.6.2. Checksums-Sha1: a8e4dacae83923777cea8fbe0a4c8600ef7d06d1 2493 golang-github-linuxdeepin-go-dbus-factory_1.9.6-3.dsc 082bf597f8c9d4cf1a25f9e67209770127e24e0f 4212 golang-github-linuxdeepin-go-dbus-factory_1.9.6-3.debian.tar.xz 1891cd8c65099d92ddb601cfc22faf4e545a10d4 15814 golang-github-linuxdeepin-go-dbus-factory_1.9.6-3_amd64.buildinfo Checksums-Sha256: a9962af30222bbe5f44175db670dbbd5408e44c695137ba809b336e9c43373ec 2493 golang-github-linuxdeepin-go-dbus-factory_1.9.6-3.dsc d80a95a1ad302bb3a113e3b0830409ff5330aaac70cc0090e7a34d6eaa67f3ac 4212 golang-github-linuxdeepin-go-dbus-factory_1.9.6-3.debian.tar.xz aa47a4334830189a87d5b53e86a992a26556e697fee2b74901085c165ee5cf3c 15814
Processed: tagging 1024576
Processing commands for cont...@bugs.debian.org: > tags 1024576 + pending Bug #1024576 [src:librepo] librepo: FTBFS against libgpgme-dev >= 1.18.0-2 Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1024576: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024576 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1027925: spamassassin FTBFS on IPV6-only buildds
Source: spamassassin Version: 4.0.0~rc2-2 Severity: serious https://buildd.debian.org/status/logs.php?pkg=spamassassin=amd64 ... Jan 4 03:57:23.254 [3488924] dbg: logger: adding facilities: all Jan 4 03:57:23.255 [3488924] dbg: logger: logging level is DBG Jan 4 03:57:23.257 [3488924] dbg: logger: successfully opened file log/sa_check_spamd.g3uk5R/d.sa_check_spamd/spamd.err.0.timestamped Jan 4 03:57:23.257 [3488924] dbg: logger: successfully added file method Jan 4 03:57:23.257 [3488924] dbg: spamd: will perform setuids? 0 Jan 4 03:57:23.257 [3488924] dbg: spamd: socket module of choice: IO::Socket::IP 0.41, Socket 2.033, have PF_INET, have PF_INET6, using legacy Socket6::getaddrinfo, AI_ADDRCONFIG is supported Jan 4 03:57:23.257 [3488924] dbg: spamd: socket specification: "127.0.0.1", IP address: 127.0.0.1, port: 61558 server socket setup failed, retry 1: spamd: invalid address for a listen socket: "127.0.0.1": Address family for hostname not supported server socket setup failed, retry 2: spamd: invalid address for a listen socket: "127.0.0.1": Address family for hostname not supported server socket setup failed, retry 3: spamd: invalid address for a listen socket: "127.0.0.1": Address family for hostname not supported server socket setup failed, retry 4: spamd: invalid address for a listen socket: "127.0.0.1": Address family for hostname not supported server socket setup failed, retry 5: spamd: invalid address for a listen socket: "127.0.0.1": Address family for hostname not supported server socket setup failed, retry 6: spamd: invalid address for a listen socket: "127.0.0.1": Address family for hostname not supported server socket setup failed, retry 7: spamd: invalid address for a listen socket: "127.0.0.1": Address family for hostname not supported server socket setup failed, retry 8: spamd: invalid address for a listen socket: "127.0.0.1": Address family for hostname not supported server socket setup failed, retry 9: spamd: invalid address for a listen socket: "127.0.0.1": Address family for hostname not supported spamd: invalid address for a listen socket: "127.0.0.1": Address family for hostname not supported ... Failed 30/213 test programs. 162/3101 subtests failed. make[2]: *** [Makefile:1473: test_dynamic] Error 255
Bug#1023284: libevent: FTBFS with glibc 2.36
On Fri, Nov 25, 2022 at 10:56:09AM -0500, Nicolas Mora wrote:
> Hello,
>
> Le 2022-11-17 à 04 h 15, Benjamin Drung a écrit :
> >
> > We did a library transition in Ubuntu to remove this symbol:
> > https://launchpad.net/bugs/1990941
> > Attached the patch we applied.
> >
> Thanks, I've made a new package based on your patch lately,
> libevent_2.1.12-stable-7 is in NEW for now [1]. Waiting for FTP masters to
> review the new package so the transition can start.
>
Probably late for this. But this really isn't right for a library transition.
I've read the discussion on launchpad. The orig patch to keep ABI has problem
for mixing arc4random functions from the vendored sources and glibc.
But as I read the code, the arc4random_addrandom shouldn't be called. So glibc
doesn't provide such.
(Why you want to add entropy yourself?)
Looking at other implementation that still has arc4random_addrandom, for example
https://docs.oracle.com/cd/E88353_01/html/E37843/arc4random-addrandom-3c.html
It's just empty function, provided for compatibility.
So Just make evutil_secure_rng_add_bytes noop with glibc's implemtation of
arc4random. Please see following patch.
diff --git a/evutil_rand.c b/evutil_rand.c
index 8e9afda..15deab3 100644
--- a/evutil_rand.c
+++ b/evutil_rand.c
@@ -190,14 +190,14 @@ evutil_secure_rng_get_bytes(void *buf, size_t n)
ev_arc4random_buf(buf, n);
}
-#if !defined(EVENT__HAVE_ARC4RANDOM) ||
defined(EVENT__HAVE_ARC4RANDOM_ADDRANDOM)
void
evutil_secure_rng_add_bytes(const char *buf, size_t n)
{
+#if defined(EVENT__HAVE_ARC4RANDOM_ADDRANDOM)
arc4random_addrandom((unsigned char*)buf,
n>(size_t)INT_MAX ? INT_MAX : (int)n);
-}
#endif
+}
void
evutil_free_secure_rng_globals_(void)
diff --git a/include/event2/util.h b/include/event2/util.h
index 02aa7ba..aa7177d 100644
--- a/include/event2/util.h
+++ b/include/event2/util.h
@@ -862,7 +862,6 @@ int evutil_secure_rng_init(void);
EVENT2_EXPORT_SYMBOL
int evutil_secure_rng_set_urandom_device_file(char *fname);
-#if !defined(EVENT__HAVE_ARC4RANDOM) ||
defined(EVENT__HAVE_ARC4RANDOM_ADDRANDOM)
/** Seed the random number generator with extra random bytes.
You should almost never need to call this function; it should be
@@ -879,7 +878,6 @@ int evutil_secure_rng_set_urandom_device_file(char *fname);
*/
EVENT2_EXPORT_SYMBOL
void evutil_secure_rng_add_bytes(const char *dat, size_t datlen);
-#endif
#ifdef __cplusplus
}
Bug#1027130: closing 1027130
close 1027130 1.0.0+dfsg-1 thanks
Processed: closing 1027130
Processing commands for cont...@bugs.debian.org: > close 1027130 1.0.0+dfsg-1 Bug #1027130 [libclamav9] libclamav9: LibClamAV Error: Can't verify database integrity There is no source info for the package 'libclamav9' at version '1.0.0+dfsg-1' with architecture '' Unable to make a source version for version '1.0.0+dfsg-1' Marked as fixed in versions 1.0.0+dfsg-1. Bug #1027130 [libclamav9] libclamav9: LibClamAV Error: Can't verify database integrity Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1027130: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027130 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1027130: libclamav9: LibClamAV Error: Can't verify database integrity
On Wed, 28 Dec 2022 10:10:21 +0100 Jan Huijsmans wrote: > Package: libclamav9 > Version: 0.103.7+dfsg-1+b2 > Severity: grave > Justification: renders package unusable > > Dear Maintainer, > > Upgrade of package and related clamav packages to 0.103.7+dfsg-1+b2 resulted > in an inability to verify the clamav database daily.cvd (1st it tries). > > Dodngrade of packages clamav-daemon and clamav-freshclam didn't dolve the issue, > libclamav9 needed to be downgraded to 0.103.7+dfsg-0+deb11u1 to be able to start > clamab-daemon again. > > Errors in syslog: > > LibClamAV Error: Can't load /var/lib/clamav/daily.cvd: Can't verify database integrity > LibClamAV Error: cli_loaddbdir(): error loading database /var/lib/clamav/ daily.cvd Verified this works with the clamav 1.0.0 in experimental. Scott K signature.asc Description: This is a digitally signed message part.
Bug#1027654: marked as done (ranger: FTBFS: dh_auto_test: error: make -j8 test PYTHON=python3 returned exit code 2)
Your message dated Wed, 04 Jan 2023 16:14:20 +
with message-id
and subject line Bug#1027654: fixed in ranger 1.9.3-5
has caused the Debian Bug report #1027654,
regarding ranger: FTBFS: dh_auto_test: error: make -j8 test PYTHON=python3
returned exit code 2
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1027654: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027654
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ranger
Version: 1.9.3-4
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230101 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[2]: Entering directory '/<>'
> Running pylint...
> pylint ./ranger/container ./ranger/gui ./ranger/api ./ranger/colorschemes
> ./ranger/ext ./ranger/core ./ranger/__init__.py ./doc/tools/print_keys.py
> ./doc/tools/print_colors.py ./doc/tools/convert_papermode_to_metadata.py
> ./doc/tools/performance_test.py ./examples/plugin_avfs.py
> ./examples/plugin_ipc.py ./examples/plugin_fasd_add.py
> ./examples/plugin_new_macro.py ./examples/plugin_chmod_keybindings.py
> ./examples/plugin_new_sorting_method.py ./examples/plugin_hello_world.py
> ./examples/plugin_file_filter.py ./examples/plugin_linemode.py
> ./examples/plugin_pmount_dynamic.py ./examples/plugin_pmount.py ./ranger.py
> ./setup.py ./tests
> Running flake8...
> flake8 ./ranger/container ./ranger/gui ./ranger/api ./ranger/colorschemes
> ./ranger/ext ./ranger/core ./ranger/__init__.py ./doc/tools/print_keys.py
> ./doc/tools/print_colors.py ./doc/tools/convert_papermode_to_metadata.py
> ./doc/tools/performance_test.py ./examples/plugin_avfs.py
> ./examples/plugin_ipc.py ./examples/plugin_fasd_add.py
> ./examples/plugin_new_macro.py ./examples/plugin_chmod_keybindings.py
> ./examples/plugin_new_sorting_method.py ./examples/plugin_hello_world.py
> ./examples/plugin_file_filter.py ./examples/plugin_linemode.py
> ./examples/plugin_pmount_dynamic.py ./examples/plugin_pmount.py ./ranger.py
> ./setup.py ./tests ./ranger/config
> Running doctests...
> Running py.test tests...
> py.test-3 tests
> Checking completeness of man page...
> Running shellcheck...
> Testing ranger/gui/widgets/console.py...
> sed '2,$s/^\(\s*\)#/\1/' ./ranger/data/scope.sh | shellcheck -a -
> Testing ranger/gui/ansi.py...
> Testing ranger/api/commands.py...
> Testing ranger/ext/human_readable.py...
> Testing ranger/ext/rifle.py...
>
> In - line 350:
> exit 1
> ^^ SC2317 (info): Command appears to be unreachable. Check usage (or
> ignore if invoked indirectly).
>
> For more information:
> https://www.shellcheck.net/wiki/SC2317 -- Command appears to be
> unreachable...
> make[2]: *** [Makefile:119: test_shellcheck] Error 1
> make[2]: *** Waiting for unfinished jobs
> = test session starts
> ==
> platform linux -- Python 3.10.9, pytest-7.2.0, pluggy-1.0.0+repack
> rootdir: /<>
> collected 7 items
>
> tests/ranger/container/test_bookmarks.py .. [
> 28%]
> tests/ranger/container/test_container.py .. [
> 57%]
> tests/ranger/container/test_fsobject.py .. [
> 85%]
> tests/ranger/core/test_main.py .
> [100%]
>
> == 7 passed in 0.26s
> ===
> Testing ranger/ext/widestring.py...
> Testing ranger/ext/keybinding_parser.py...
> Testing ranger/ext/signals.py...
> Testing ranger/ext/lazy_property.py...
> Testing ranger/ext/iter_tools.py...
> Testing ranger/ext/direction.py...
> * Module /<>/.pylintrc
> .pylintrc:1:0: W0012: Unknown option value for '--disable', expected a valid
> pylint message and got 'locally-enabled' (unknown-option-value)
> .pylintrc:1:0: W0012: Unknown option value for '--disable', expected a valid
> pylint message and got 'redefined-variable-type' (unknown-option-value)
> * Module ranger.container.settings
> ranger/container/settings.py:17:0: R0022: Useless option value for 'disable',
> 'bad-whitespace' was removed from pylint, see
> https://github.com/PyCQA/pylint/pull/3577. (useless-option-value)
> ranger/container/settings.py:23:0: R0022: Useless option value for 'enable',
> 'bad-whitespace' was removed from pylint, see
> https://github.com/PyCQA/pylint/pull/3577. (useless-option-value)
> ranger/container/settings.py:138:42: R1735: Consider using {} instead of
Bug#1010966: marked as done (Should wesnoth-1.14 be shipped in bookworm?)
Your message dated Wed, 04 Jan 2023 15:35:20 + with message-id and subject line Bug#1027856: Removed package(s) from unstable has caused the Debian Bug report #1010966, regarding Should wesnoth-1.14 be shipped in bookworm? 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.) -- 1010966: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010966 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: wesnoth-1.14 Version: 1:1.14.17-2 Severity: serious With wesnoth-1.16 already in bookworm, does it make sense to also ship wesnoth-1.14? --- End Message --- --- Begin Message --- Version: 1:1.14.17-2+rm Dear submitter, as the package wesnoth-1.14 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/1027856 The version of this package that was in Debian prior to this removal can still be found using https://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 ---
Processed: your mail
Processing commands for cont...@bugs.debian.org: > block 1026585 by 1026768 Bug #1026585 [src:gfxreconstruct] gfxreconstruct: FTBFS: generated_vulkan_enum_to_string.cpp:2006:10: error: ‘VK_STRUCTURE_TYPE_VIDEO_PROFILE_KHR’ was not declared in this scope; did you mean ‘VK_STRUCTURE_TYPE_VIDEO_PROFILE_INFO_KHR’? 1026585 was not blocked by any bugs. 1026585 was not blocking any bugs. Added blocking bug(s) of 1026585: 1026768 > thanks Stopping processing here. Please contact me if you need assistance. -- 1026585: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026585 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1027112: bazel-bootstrap: /usr/include/absl/synchronization/mutex.h:550: error: undefined reference to 'absl::debian3::Mutex::Unlock()'
Hello, FWIW I think I crafted a patch that might fix the issue (in a ugly and hard-coded way) at debian/patches/new-grpc.patch Description: Add result of pkg-config --libs grpc++_unsecure call to the BUILD file Author: Gianfranco Costamagna Bug-Debian: https://bugs.debian.org/1027112 Last-Update: 2023-01-04 --- bazel-bootstrap-4.2.3+ds.orig/tools/distributions/debian/debian_cc.BUILD +++ bazel-bootstrap-4.2.3+ds/tools/distributions/debian/debian_cc.BUILD @@ -39,6 +39,6 @@ cc_library( # libgrpc++-dev cc_library( name = "grpc++_unsecure", -linkopts = ["-lgrpc++_unsecure", "-lgrpc_unsecure", "-lgpr"], +linkopts = ["-lgrpc++_unsecure", "-lgrpc_unsecure", "-lgpr", "-labsl_throw_delegate", "-labsl_raw_logging_internal", "-labsl_throw_delegate", "-labsl_raw_logging_internal", "-labsl_raw_logging_internal", "-labsl_raw_logging_internal", "-labsl_raw_logging_internal", "-labsl_throw_delegate", "-labsl_raw_logging_internal", "-labsl_raw_logging_internal", "-labsl_throw_delegate", "-labsl_raw_logging_internal", "-labsl_throw_delegate", "-labsl_raw_logging_internal", "-labsl_raw_logging_internal", "-labsl_raw_logging_internal", "-labsl_raw_logging_internal", "-labsl_throw_delegate", "-labsl_raw_logging_internal", "-labsl_raw_logging_internal", "-labsl_raw_hash_set", "-labsl_hashtablez_sampler", "-labsl_hash", "-labsl_city", "-labsl_low_level_hash", "-labsl_random_distributions", "-labsl_throw_delegate", "-labsl_raw_logging_internal", "-labsl_throw_delegate", "-labsl_raw_logging_internal", "-labsl_raw_logging_internal", "-labsl_raw_logging_internal", "-labsl_random_seed_sequences", "-labsl_random_internal_pool_urbg", "-labsl_random_internal_randen", "-labsl_random_internal_randen_hwaes", "-labsl_random_internal_randen_hwaes_impl", "-labsl_random_internal_randen_slow", "-labsl_random_internal_platform", "-labsl_raw_logging_internal", "-labsl_throw_delegate", "-labsl_raw_logging_internal", "-labsl_random_internal_seed_material", "-labsl_raw_logging_internal", "-labsl_random_seed_gen_exception", "-labsl_statusor", "-labsl_status", "-labsl_cord", "-labsl_cordz_info", "-labsl_cord_internal", "-labsl_cordz_functions", "-labsl_exponential_biased", "-labsl_cordz_handle", "-labsl_bad_optional_access", "-labsl_strerror", "-labsl_str_format_internal", "-labsl_synchronization", "-labsl_graphcycles_internal", "-labsl_stacktrace", "-labsl_symbolize", "-labsl_debugging_internal", "-labsl_demangle_internal", "-labsl_malloc_internal", "-labsl_time", "-labsl_civil_time", "-labsl_strings", "-labsl_strings_internal", "-Wl,--push-state,--as-needed", "-latomic", "-Wl,--pop-state", "-lrt", "-labsl_base", "-labsl_spinlock_wait", "-labsl_int128", "-labsl_throw_delegate", "-labsl_time_zone", "-labsl_bad_variant_access", "-labsl_raw_logging_internal", "-labsl_log_severity"], visibility = ["//visibility:public"], ) I just uploaded it in Ubuntu, lets see how the build goes. G. OpenPGP_signature Description: OpenPGP digital signature
Bug#1026504: marked as done (specutils: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.11 3.10" returned exit code 13)
Your message dated Wed, 04 Jan 2023 14:46:58 +
with message-id
and subject line Bug#1026504: fixed in specutils 1.9.1-1
has caused the Debian Bug report #1026504,
regarding specutils: FTBFS: dh_auto_test: error: pybuild --test --test-pytest
-i python{version} -p "3.11 3.10" returned exit code 13
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.)
--
1026504: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026504
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: specutils
Version: 1.9.0-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221220 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules binary
> dh binary --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:240: python3.11 setup.py config
> /usr/lib/python3/dist-packages/setuptools/config/setupcfg.py:508:
> SetuptoolsDeprecationWarning: The license_file parameter is deprecated, use
> license_files instead.
> warnings.warn(msg, warning_class)
> running config
> I: pybuild base:240: python3.10 setup.py config
> /usr/lib/python3/dist-packages/setuptools/config/setupcfg.py:508:
> SetuptoolsDeprecationWarning: The license_file parameter is deprecated, use
> license_files instead.
> warnings.warn(msg, warning_class)
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:240: /usr/bin/python3.11 setup.py build
> /usr/lib/python3/dist-packages/setuptools/config/setupcfg.py:508:
> SetuptoolsDeprecationWarning: The license_file parameter is deprecated, use
> license_files instead.
> warnings.warn(msg, warning_class)
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.11/build/specutils
> copying specutils/__init__.py ->
> /<>/.pybuild/cpython3_3.11/build/specutils
> copying specutils/conftest.py ->
> /<>/.pybuild/cpython3_3.11/build/specutils
> copying specutils/version.py ->
> /<>/.pybuild/cpython3_3.11/build/specutils
> copying specutils/_astropy_init.py ->
> /<>/.pybuild/cpython3_3.11/build/specutils
> creating /<>/.pybuild/cpython3_3.11/build/specutils/manipulation
> copying specutils/manipulation/__init__.py ->
> /<>/.pybuild/cpython3_3.11/build/specutils/manipulation
> copying specutils/manipulation/resample.py ->
> /<>/.pybuild/cpython3_3.11/build/specutils/manipulation
> copying specutils/manipulation/smoothing.py ->
> /<>/.pybuild/cpython3_3.11/build/specutils/manipulation
> copying specutils/manipulation/model_replace.py ->
> /<>/.pybuild/cpython3_3.11/build/specutils/manipulation
> copying specutils/manipulation/estimate_uncertainty.py ->
> /<>/.pybuild/cpython3_3.11/build/specutils/manipulation
> copying specutils/manipulation/extract_spectral_region.py ->
> /<>/.pybuild/cpython3_3.11/build/specutils/manipulation
> copying specutils/manipulation/manipulation.py ->
> /<>/.pybuild/cpython3_3.11/build/specutils/manipulation
> copying specutils/manipulation/utils.py ->
> /<>/.pybuild/cpython3_3.11/build/specutils/manipulation
> creating /<>/.pybuild/cpython3_3.11/build/specutils/analysis
> copying specutils/analysis/__init__.py ->
> /<>/.pybuild/cpython3_3.11/build/specutils/analysis
> copying specutils/analysis/uncertainty.py ->
> /<>/.pybuild/cpython3_3.11/build/specutils/analysis
> copying specutils/analysis/correlation.py ->
> /<>/.pybuild/cpython3_3.11/build/specutils/analysis
> copying specutils/analysis/location.py ->
> /<>/.pybuild/cpython3_3.11/build/specutils/analysis
> copying specutils/analysis/flux.py ->
> /<>/.pybuild/cpython3_3.11/build/specutils/analysis
> copying specutils/analysis/template_comparison.py ->
> /<>/.pybuild/cpython3_3.11/build/specutils/analysis
> copying specutils/analysis/moment.py ->
> /<>/.pybuild/cpython3_3.11/build/specutils/analysis
> copying specutils/analysis/width.py ->
> /<>/.pybuild/cpython3_3.11/build/specutils/analysis
> copying specutils/analysis/utils.py ->
> /<>/.pybuild/cpython3_3.11/build/specutils/analysis
> creating /<>/.pybuild/cpython3_3.11/build/specutils/spectra
> copying specutils/spectra/__init__.py ->
> /<>/.pybuild/cpython3_3.11/build/specutils/spectra
> copying specutils/spectra/spectral_coordinate.py ->
> /<>/.pybuild/cpython3_3.11/build/specutils/spectra
> copying specutils/spectra/spectrum_list.py ->
> /<>/.pybuild/cpython3_3.11/build/specutils/spectra
> copying
Bug#1027843: marked as done (libgnatcoll-bindings FTBFS with Python 3.11 as default version)
Your message dated Wed, 04 Jan 2023 14:42:59 +
with message-id
and subject line Bug#1027843: fixed in libgnatcoll-bindings 23.0.0-4
has caused the Debian Bug report #1027843,
regarding libgnatcoll-bindings FTBFS with Python 3.11 as default version
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.)
--
1027843: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027843
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libgnatcoll-bindings
Version: 23.0.0-3
Severity: serious
https://buildd.debian.org/status/fetch.php?pkg=libgnatcoll-bindings=ppc64el=23.0.0-3%2Bb1=1672725764=0
...
/<>/python3/python_support.c: In function ‘ada_pyframe_get_code’:
/<>/python3/python_support.c:817:14: error: invalid use of
incomplete typedef ‘PyFrameObject’ {aka ‘struct _frame’}
817 |return obj->f_code;
| ^~
/<>/python3/python_support.c: In function ‘ada_pyframe_get_back’:
/<>/python3/python_support.c:823:14: error: invalid use of
incomplete typedef ‘PyFrameObject’ {aka ‘struct _frame’}
823 |return obj->f_back;
| ^~
compilation of python_support.c failed
gprbuild: *** compilation phase failed
--- End Message ---
--- Begin Message ---
Source: libgnatcoll-bindings
Source-Version: 23.0.0-4
Done: Nicolas Boulenguez
We believe that the bug you reported is fixed in the latest version of
libgnatcoll-bindings, 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 1027...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Nicolas Boulenguez (supplier of updated
libgnatcoll-bindings 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, 04 Jan 2023 13:52:00 +
Source: libgnatcoll-bindings
Architecture: source
Version: 23.0.0-4
Distribution: unstable
Urgency: medium
Maintainer: Nicolas Boulenguez
Changed-By: Nicolas Boulenguez
Closes: 1027843
Changes:
libgnatcoll-bindings (23.0.0-4) unstable; urgency=medium
.
* Adapt PyFrameObject accessors to python/3.11. Closes: #1027843.
Checksums-Sha1:
60ac9897ffd4caa6bc61f41025f919f872dcd38e 3400 libgnatcoll-bindings_23.0.0-4.dsc
b93e56ff2f6258ef676a83a1632b495a138a1348 11000
libgnatcoll-bindings_23.0.0-4.debian.tar.xz
Checksums-Sha256:
e44651230ccd505afbf976c85f9afc4395b7f091e0789e31c125a07d6f716459 3400
libgnatcoll-bindings_23.0.0-4.dsc
e9590f665d941ef1add9df29fb296817380fcf672b6f49cab134ef8547b097a3 11000
libgnatcoll-bindings_23.0.0-4.debian.tar.xz
Files:
08591d210223b16abe8e08050236ac6a 3400 libdevel optional
libgnatcoll-bindings_23.0.0-4.dsc
3ee9b081575327de2df1d7b86f6bc919 11000 libdevel optional
libgnatcoll-bindings_23.0.0-4.debian.tar.xz
-BEGIN PGP SIGNATURE-
iQJHBAEBCAAxFiEEawm/6zYhqkfTAKHtFHKayZgPCdIFAmO1h3kTHG5pY29sYXNA
ZGViaWFuLm9yZwAKCRAUcprJmA8J0ghGD/41SThLeXIQFj9krtQEETJUkMvtqbxH
v6clkzS4lKMbxk1JSgMAgJCaT0f7efESAbTsTpw1EREHhTXaiw8N6DfnJMXz1o+1
4IUjf0mQ279qedsStPA/+0jfTX2Znmazpx75r4k4GP8z6AhaBA02hOc4QArbPs41
LjqbqfKhv1SvU/zImBZi3TLlpSTTRAiAW3xJRutzOIY9MU9YOq5kG0szvGYelwW6
/F9PrHPhf8DXIIP6pThdKobZKOpl2IU99oLCGwbiWRshuPses6lSvJVxde0zl/el
qu4dwK/MNLNORu0dU7DdnyP0zZ8wR2Z0SS8nSo/XNs0lynOOjcwhAp8JZPw4+xvr
1mF+p8avKwMUZXmtpx1nSIP6/5QGDwucv3UKoJnrFCmH6F+yj4K0Nhgo5dDwemoL
MzPEHfYuCPOIQdCD5SsVtqfnDwT3mh8DvSIvRuk7i+BU7vgH6xQBOsVgdn2feIBo
FQzEOFCI5RWopUmFhkxysCQ1UAj36nFx4VrQ6rBXu+4KdKmK3VTmS3vxcQ05ilyD
vTrtKrEnSqyjOnN6f2KaausnLJqYyhkemc3ZbBx7WxhFdXk7qzTmu1X9iIpETNPi
NbzPiiC7dk7MiB6cLUJ3f6qoQ/pF+pzavSZOTbs4h8J1sJ8Dk/E90wzlg0tOtsBu
Vt0RQXIfQAhm5w==
=Ogrs
-END PGP SIGNATURE End Message ---
Bug#1027850: marked as done (graph-tool FTBFS with Python 3.11 as default version)
Your message dated Wed, 04 Jan 2023 14:40:00 + with message-id and subject line Bug#1027850: fixed in graph-tool 2.45+ds-10 has caused the Debian Bug report #1027850, regarding graph-tool FTBFS with Python 3.11 as default version 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.) -- 1027850: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027850 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: graph-tool Version: 2.45+ds-9 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=graph-tool=amd64=2.45%2Bds-9%2Bb1=1672782255=0 ... TEST STARTED Tue Jan 3 21:43:53 UTC 2023 rm -f _BUILD/test.png PYTHONPATH=/<>/debian/tmp//usr/lib/python3.11/dist-packages \ python3 -c "\ from graph_tool.all import *; \ show_config(); \ g = random_graph(10, lambda: 5, directed=False); \ graph_draw(g, output='_BUILD/test.png'); \ " Matplotlib created a temporary config/cache directory at /tmp/matplotlib-vsfk88vs because the default path (/sbuild-nonexistent/.config/matplotlib) is not a writable directory; it is highly recommended to set the MPLCONFIGDIR environment variable to a writable directory, in particular to speed up the import of Matplotlib and to better support multiprocessing. Traceback (most recent call last): File "", line 1, in File "/<>/debian/tmp/usr/lib/python3.11/dist-packages/graph_tool/generation/__init__.py", line 370, in random_graph if len(inspect.getargspec(deg_sampler)[0]) > 0: ^^ AttributeError: module 'inspect' has no attribute 'getargspec'. Did you mean: 'getargs'? version: 2.45 gcc version: 12.2.0 compilation flags: -DNDEBUG -Wdate-time -D_FORTIFY_SOURCE=2 -fopenmp -O3 -fvisibility=default -fvisibility-inlines-hidden -Wno-deprecated -Wall -Wextra -ftemplate-backtrace-limit=0 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro -Wl,-z,now install prefix: /usr python dir: /usr/lib/python3.11/dist-packages graph filtering: True openmp: True uname: Linux x86-csail-01 5.10.0-20-amd64 #1 SMP Debian 5.10.158-2 (2022-12-13) x86_64 make[1]: *** [debian/rules:43: override_dh_auto_install] Error 1 https://docs.python.org/3/whatsnew/3.11.html ... Removed from the inspect module: The getargspec() function, deprecated since Python 3.0; use inspect.signature() or inspect.getfullargspec() instead. https://docs.python.org/3/whatsnew/3.11.html ... --- End Message --- --- Begin Message --- Source: graph-tool Source-Version: 2.45+ds-10 Done: Jerome Benoit We believe that the bug you reported is fixed in the latest version of graph-tool, 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 1027...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jerome Benoit (supplier of updated graph-tool 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, 04 Jan 2023 14:08:40 + Source: graph-tool Architecture: source Version: 2.45+ds-10 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Jerome Benoit Closes: 1027850 Changes: graph-tool (2.45+ds-10) unstable; urgency=medium . * FTBFS fix release, patch material now obsoleted by Python 3.11 (Closes: #1027850). * Debianization: - d/patches/*: - d/p/upstream-fix-python311-migration.patch, introduce; - d/p/d-provide_fixed-ax_python_devel_DOT_m4.patch, obsoleted. Checksums-Sha1: ce9e9ab927dfb2a8059c760c5db0af068bad1cbe 3742 graph-tool_2.45+ds-10.dsc b73c16cc569a24ad6de45ae47a5d6706a5ed81f3 362488 graph-tool_2.45+ds-10.debian.tar.xz 831e1007f4864c9a707451df5647ebce74b757e2 16044 graph-tool_2.45+ds-10_source.buildinfo Checksums-Sha256: c5bb37ec32919df8ec264d53ad74d57effe3ef2c6bffb193d14feb26b7fdaac9 3742 graph-tool_2.45+ds-10.dsc e716594dd5b0607393a6eddc1040b315d3105c2b9d98357a3e52c6df917083f9 362488 graph-tool_2.45+ds-10.debian.tar.xz d2b4eb69632e6521ad61600603e2879d4f3cec36c3125c44669f48fe8a7b3885 16044 graph-tool_2.45+ds-10_source.buildinfo Files: 9e5512f1e7cf6de898cc12756c7c4829 3742 python optional graph-tool_2.45+ds-10.dsc
Bug#1011683: marked as done (freewheeling: FTBFS: fweelin_fluidsynth.cc:90:72: error: ‘FALSE’ was not declared in this scope)
Your message dated Wed, 04 Jan 2023 14:39:22 +
with message-id
and subject line Bug#1011683: fixed in freewheeling 0.6.6-1
has caused the Debian Bug report #1011683,
regarding freewheeling: FTBFS: fweelin_fluidsynth.cc:90:72: error: ‘FALSE’ was
not declared in this scope
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.)
--
1011683: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011683
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: freewheeling
Version: 0.6.4-1.1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220525 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> g++ -DPACKAGE_NAME=\"fweelin\" -DPACKAGE_TARNAME=\"fweelin\"
> -DPACKAGE_VERSION=\"0.6.4\" -DPACKAGE_STRING=\"fweelin\ 0.6.4\"
> -DPACKAGE_BUGREPORT=\"https://github.com/free-wheeling/freewheeling/issues\;
> -DPACKAGE_URL=\"\" -DPACKAGE=\"fweelin\" -DVERSION=\"0.6.4\"
> -DHAVE_LIBNETTLE=1 -DHAVE_LIBDL=1 -DHAVE_LIBFREETYPE=1 -DHAVE_LIBSDL_GFX=1
> -DCAPITAL_FILLED_PIE=1 -DHAVE_LIBSDL_TTF=1 -DHAVE_LIBSDL=1 -DHAVE_LIBLO=1
> -DHAVE_LIBXML2=1 -DHAVE_LIBM=1 -DHAVE_LIBPTHREAD=1 -DHAVE_LIBASOUND=1
> -DHAVE_LIBJACK=1 -DUSE_FLUIDSYNTH=1 -DHAVE_LIBVORBIS=1 -DHAVE_LIBVORBISFILE=1
> -DHAVE_LIBVORBISENC=1 -DHAVE_LIBOGG=1 -DHAVE_LIBSNDFILE=1 -DHAVE_STDIO_H=1
> -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1
> -DHAVE_STRINGS_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_UNISTD_H=1
> -DHAVE_SYS_TIME_H=1 -DSTDC_HEADERS=1 -DHAVE_ERRNO_H=1 -DHAVE_FCNTL_H=1
> -DHAVE_INTTYPES_H=1 -DHAVE_LIMITS_H=1 -DHAVE_STDINT_H=1 -DHAVE_STDLIB_H=1
> -DHAVE_STRING_H=1 -DHAVE_SYS_RESOURCE_H=1 -DHAVE_SYS_TIME_H=1
> -DHAVE_TERMIOS_H=1 -DHAVE_UNISTD_H=1 -DHAVE_UTIME_H=1 -DTIME_WITH_SYS_TIME=1
> -DHAVE__BOOL=1 -DHAVE_ALLOCA_H=1 -DHAVE_ALLOCA=1 -DHAVE_FORK=1 -DHAVE_VFORK=1
> -DHAVE_WORKING_VFORK=1 -DHAVE_WORKING_FORK=1 -DHAVE_MALLOC=1 -DHAVE_ATEXIT=1
> -DHAVE_DUP2=1 -DHAVE_FLOOR=1 -DHAVE_GETTIMEOFDAY=1 -DHAVE_MEMSET=1
> -DHAVE_POW=1 -DHAVE_REALPATH=1 -DHAVE_SELECT=1 -DHAVE_SQRT=1
> -DHAVE_STRCASECMP=1 -DHAVE_STRCHR=1 -DHAVE_STRNCASECMP=1 -DHAVE_STRRCHR=1
> -DHAVE_STRTOL=1 -I. -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat
> -Werror=format-security -g -O2 -ffile-prefix-map=/<>=.
> -fstack-protector-strong -Wformat -Werror=format-security -I. -g -Wall
> -Wno-write-strings -D_REENTRANT -DPTHREADS -DNDEBUG -DVERSION=\"0.6.4\"
> -DFWEELIN_DATADIR=\"/usr/share/fweelin\" -DADDON_DIR=\"/usr/local/lib/jack\"
> -I/usr/include/freetype2 -I/usr/include/libxml2 -funroll-loops
> -finline-functions -fomit-frame-pointer -ffast-math -fexpensive-optimizations
> -fstrict-aliasing -falign-loops=2 -falign-jumps=2 -falign-functions=2 -O9
> -Wno-non-virtual-dtor -g -O2 -ffile-prefix-map=/<>=.
> -fstack-protector-strong -Wformat -Werror=format-security -c -o
> elastin/elastin.o elastin/elastin.cc
> In file included from fweelin_block.h:34,
> from fweelin_config.h:27,
> from fweelin_core_dsp.cc:37:
> elastin/elastin.h: In member function ‘float Elastin::Correlate(el_nframes_t,
> el_nframes_t, el_nframes_t)’:
> elastin/elastin.h:309:20: warning: ISO C++17 does not allow ‘register’
> storage class specifier [-Wregister]
> 309 | register float cor = 0.0;
> |^~~
> elastin/elastin.h:310:18: warning: ISO C++17 does not allow ‘register’
> storage class specifier [-Wregister]
> 310 | register int numch = d->numch;
> | ^
> elastin/elastin.h:311:23: warning: ISO C++17 does not allow ‘register’
> storage class specifier [-Wregister]
> 311 | for (register int i = 0; i < numch; i++) {
> | ^
> elastin/elastin.h:312:29: warning: ISO C++17 does not allow ‘register’
> storage class specifier [-Wregister]
> 312 | register el_sample_t *t1 = &(sbufs[i][idx1]),
> | ^~
> elastin/elastin.h:313:10: warning: ISO C++17 does not allow ‘register’
> storage class specifier [-Wregister]
> 313 | *t2 = &(sbufs[i][idx2]);
> | ^~
> elastin/elastin.h:314:34: warning: ISO C++17 does not allow ‘register’
> storage class specifier [-Wregister]
> 314 | for (register el_nframes_t j = 0; j < cnt; j++, t1++, t2++)
> | ^
> In file included from elastin/elastin.cc:61:
> elastin/elastin.h: In member function ‘float
Processed: Re: Bug#1027913: kodi: FTBFS in bookworm (undeclared build-dependency on tzdata)
Processing control commands: > reassign -1 howardhinnant-date 3.0.1+ds-3 Bug #1027913 [src:kodi] kodi: FTBFS in bookworm (undeclared build-dependency on tzdata) Bug reassigned from package 'src:kodi' to 'howardhinnant-date'. No longer marked as found in versions kodi/2:20.0~rc2+dfsg-1. Ignoring request to alter fixed versions of bug #1027913 to the same values previously set Bug #1027913 [howardhinnant-date] kodi: FTBFS in bookworm (undeclared build-dependency on tzdata) There is no source info for the package 'howardhinnant-date' at version '3.0.1+ds-3' with architecture '' Unable to make a source version for version '3.0.1+ds-3' Marked as found in versions 3.0.1+ds-3. > retitle -1 howardhinnant-date must runtime-depend on tzdata Bug #1027913 [howardhinnant-date] kodi: FTBFS in bookworm (undeclared build-dependency on tzdata) Changed Bug title to 'howardhinnant-date must runtime-depend on tzdata' from 'kodi: FTBFS in bookworm (undeclared build-dependency on tzdata)'. > affects -1 = kodi Bug #1027913 [howardhinnant-date] howardhinnant-date must runtime-depend on tzdata Added indication that 1027913 affects kodi -- 1027913: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027913 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1027913: kodi: FTBFS in bookworm (undeclared build-dependency on tzdata)
Control: reassign -1 howardhinnant-date 3.0.1+ds-3 Control: retitle -1 howardhinnant-date must runtime-depend on tzdata Control: affects -1 = kodi Dear Santiago, Thanks for the bug report! The "discover_tz_dir" function is directly not used by Kodi and is part of howardhinnant-date. I looked through d/control of howardhinnant-date and it appears that libhowardhinnant-tz3 must explicitly depend on tzdata just like the source package build-depends on it. I can craft the Salsa MR if Andrea wants me to do that. -- Vasyl Gello == Certified SolidWorks Expert Mob.:+380 (98) 465 66 77 E-Mail: vasek.ge...@gmail.com == 호랑이는 죽어서 가죽을 남기고 사람은 죽어서 이름을 남긴다
