Bug#1054813: marked as pending in python-dmidecode
Control: tag -1 pending Hello, Bug #1054813 in python-dmidecode 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-dmidecode/-/commit/5dd99281ee181371c0ed5bce4862a2873e625291 support Python 2-digits minor version, fixing a FTBFS; Closes: #1054813 (this message was generated automatically) -- Greetings https://bugs.debian.org/1054813
Processed: Bug#1054813 marked as pending in python-dmidecode
Processing control commands: > tag -1 pending Bug #1054813 [src:python-dmidecode] python-dmidecode: FTBFS: make[2]: *** [Makefile:4: test] Error 1 Ignoring request to alter tags of bug #1054813 to the same tags previously set -- 1054813: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054813 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1056802: marked as done (gensim: ftbfs with cython 3.0.x)
Your message dated Sat, 20 Jan 2024 07:49:04 + with message-id and subject line Bug#1056802: fixed in gensim 4.3.2+dfsg-1 has caused the Debian Bug report #1056802, regarding gensim: ftbfs with cython 3.0.x 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.) -- 1056802: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056802 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:gensim Version: 4.2.0+dfsg-1 Severity: important Tags: sid trixie User: debian-pyt...@lists.debian.org Usertags: cython3 [This bug is targeted to the upcoming trixie release] The package fails to build in a test rebuild on at least arm64 with cython 3.0.5, but succeeds to build with cython 0.29.36. Please update the package to build with cython 3.0.5 (available in experimental). If the package cannot be built with cython 3.0.5, please change the build dependency from cython3 to cython3-legacy (available now in unstable). There is no replacement for cython3-dbg. Build logs building with cython 3.0.5 can be found at https://people.debian.org/~stefanor/cython3/cython-3.0.5/ See also https://lists.debian.org/debian-python/2023/11/msg00034.html --- End Message --- --- Begin Message --- Source: gensim Source-Version: 4.3.2+dfsg-1 Done: Andreas Tille We believe that the bug you reported is fixed in the latest version of gensim, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1056...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille (supplier of updated gensim package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 20 Jan 2024 08:08:01 +0100 Source: gensim Architecture: source Version: 4.3.2+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Andreas Tille Closes: 1056802 Changes: gensim (4.3.2+dfsg-1) unstable; urgency=medium . * Team upload. . [ Debian Janitor ] * Remove constraints unnecessary since buster (oldstable): + Build-Depends: Drop versioned constraint on python3-scipy. . [ Andreas Tille ] * New upstream version Closes: #1056802 * Add debian/gbp.conf due to non-default branch layout per Debian Science team policy * Standards-Version: 4.6.2 (routine-update) * Remove trailing whitespace in debian/changelog (routine-update) * Add salsa-ci file (routine-update) * Set upstream metadata fields: Security-Contact. * Build-Depends: s/dh-python/dh-sequence-python3/ (routine-update) * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository, Repository-Browse. * Generate numpy ABI Checksums-Sha1: fd0658518401ed3fd7442fc26816beff71bb18e5 2349 gensim_4.3.2+dfsg-1.dsc 35f037c7e856bdd207471177584039501c66c304 454652 gensim_4.3.2+dfsg.orig.tar.xz d3645c93effd715d95117b0cb208399bbf8a8611 6176 gensim_4.3.2+dfsg-1.debian.tar.xz 8a8ddb80034325e6e6c51a8baef5a2e3113f6c1a 10398 gensim_4.3.2+dfsg-1_amd64.buildinfo Checksums-Sha256: f56879464402b1de927922fd2933ad60cbab57bd190be08b815649cb6552c743 2349 gensim_4.3.2+dfsg-1.dsc 98ab64f60dbb83bcabbaf8ae8b0a776082ec8f862e3877a0d0a3d7b41b933232 454652 gensim_4.3.2+dfsg.orig.tar.xz 7be9301f43de2387a1b99a8ebacf8423eaf4644241d673b4311e51349c21da42 6176 gensim_4.3.2+dfsg-1.debian.tar.xz bb7259818ac31538d42162eece2dbc18fc4a8489de6357c14dd9cdc8716f4bc7 10398 gensim_4.3.2+dfsg-1_amd64.buildinfo Files: d528afa31bb2b0af7f1104a88a40b7d4 2349 python optional gensim_4.3.2+dfsg-1.dsc f92d313946a2b1a2dd7b1f1b13edddef 454652 python optional gensim_4.3.2+dfsg.orig.tar.xz b082133610ebecb3552f3bbf881067e5 6176 python optional gensim_4.3.2+dfsg-1.debian.tar.xz 4fbad2caca87850f9a0830c67dd99f5e 10398 python optional gensim_4.3.2+dfsg-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmWrdz8RHHRpbGxlQGRl Ymlhbi5vcmcACgkQV4oElNHGRtHlHg/9FkxSgGL4aQ5mm3KDDml4PYivgB00UlBH K4+gsRvogJYdZfxhBMW2MRXNoZZWlJl+VzZhYjZfftSDvLXOzhgKPqfzyo5TSpI1 RqjXVtcmizK8oFmIbT+p1wBx2RfrKClsGpz06x2fEvEza4dGeUCI+WJtZOLqKwxH SYInTC96Iy3tnWXn2vwyE+xCapJtxww18xQG29vRhqpnyU2OwIPTSICMJZoKeTMO 429K063ADjl/MRwu0r7QI+zJfNX+qpr4nwzfUhPHrT49ji1Xtq/
Processed: found 1061162 in 2.12.1-3
Processing commands for cont...@bugs.debian.org: > found 1061162 2.12.1-3 Bug #1061162 [src:pypdf2] pypdf2: Do not release with Trixie Marked as found in versions pypdf2/2.12.1-3. > thanks Stopping processing here. Please contact me if you need assistance. -- 1061162: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061162 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1057430: marked as done (ring: FTBFS: configure: error: sdbus-c++ not found)
Your message dated Fri, 19 Jan 2024 20:30:06 -0500 with message-id <87a5p0pza9@gnu.org> and subject line Re: Bug#1057430: ring: FTBFS: configure: error: sdbus-c++ not found has caused the Debian Bug report #1057430, regarding ring: FTBFS: configure: error: sdbus-c++ not found to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1057430: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057430 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ring Version: 20230922.0~ds2-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=ring&arch=amd64&ver=20230922.0%7Eds2-1%2Bb1&stamp=1701601320&raw=0 checking for zlib... yes checking for libgit2 >= 1.1.0... yes checking for libpjproject... yes checking for yaml-cpp >= 0.5.1... yes checking for yaml-cpp >= 0.5.1... yes checking for jsoncpp >= 1.6.5... yes checking for alsa >= 1.0... yes checking for libpulse >= 0.9.15... yes checking for jack... no checking for sdbus-c++... no configure: error: sdbus-c++ not found make[1]: *** [debian/rules:31: override_dh_auto_configure] Error 1 make[1]: Leaving directory '/<>' Cheers -- Sebastian Ramacher --- End Message --- --- Begin Message --- Hello, Sebastian Ramacher writes: > Source: ring > Version: 20230922.0~ds2-1 > Severity: serious > Tags: ftbfs > Justification: fails to build from source (but built successfully in the past) > X-Debbugs-Cc: sramac...@debian.org > > https://buildd.debian.org/status/fetch.php?pkg=ring&arch=amd64&ver=20230922.0%7Eds2-1%2Bb1&stamp=1701601320&raw=0 > > checking for zlib... yes > checking for libgit2 >= 1.1.0... yes > checking for libpjproject... yes > checking for yaml-cpp >= 0.5.1... yes > checking for yaml-cpp >= 0.5.1... yes > checking for jsoncpp >= 1.6.5... yes > checking for alsa >= 1.0... yes > checking for libpulse >= 0.9.15... yes > checking for jack... no > checking for sdbus-c++... no > configure: error: sdbus-c++ not found > make[1]: *** [debian/rules:31: override_dh_auto_configure] Error 1 > make[1]: Leaving directory '/<>' > > Cheers john faulk writes: > I can't seem to figure why, it compiles fine on my machine. the error > you're showing is due to libsdbus-c++-dev being missing from your > system. If this is not in the build-deps, a simple fix would be to add > this package to them. > > libsdbus-c++-dev was already listed in our Build-Depends, guaranteeing it being pulled in and available at build time. This actually turned out to be an issue in the pkgconfig file shipped in sdbus-cpp 1.4.0 that broke any packages that depend it, including jami - see #1059422. I'll soon be doing a new upload of jami, so I'm closing this bug now. Thanks, -a--- End Message ---
Processed: 1057430 blocked by 1059422
Processing commands for cont...@bugs.debian.org: > block 1057430 by 1059422 Bug #1057430 [src:ring] ring: FTBFS: configure: error: sdbus-c++ not found 1057430 was not blocked by any bugs. 1057430 was not blocking any bugs. Added blocking bug(s) of 1057430: 1059422 > thanks Stopping processing here. Please contact me if you need assistance. -- 1057430: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057430 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1056787: marked as done (astra-toolbox: ftbfs with cython 3.0.x)
Your message dated Fri, 19 Jan 2024 22:49:08 + with message-id and subject line Bug#1056787: fixed in astra-toolbox 2.1.0-4 has caused the Debian Bug report #1056787, regarding astra-toolbox: ftbfs with cython 3.0.x 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.) -- 1056787: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056787 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:astra-toolbox Version: 2.1.0-3 Severity: important Tags: sid trixie User: debian-pyt...@lists.debian.org Usertags: cython3 [This bug is targeted to the upcoming trixie release] The package fails to build in a test rebuild on at least arm64 with cython 3.0.5, but succeeds to build with cython 0.29.36. Please update the package to build with cython 3.0.5 (available in experimental). If the package cannot be built with cython 3.0.5, please change the build dependency from cython3 to cython3-legacy (available now in unstable). There is no replacement for cython3-dbg. Build logs building with cython 3.0.5 can be found at https://people.debian.org/~stefanor/cython3/cython-3.0.5/ See also https://lists.debian.org/debian-python/2023/11/msg00034.html --- End Message --- --- Begin Message --- Source: astra-toolbox Source-Version: 2.1.0-4 Done: Andreas Tille We believe that the bug you reported is fixed in the latest version of astra-toolbox, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1056...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille (supplier of updated astra-toolbox package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 19 Jan 2024 23:01:19 +0100 Source: astra-toolbox Architecture: source Version: 2.1.0-4 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Andreas Tille Closes: 1023675 1056787 Changes: astra-toolbox (2.1.0-4) unstable; urgency=medium . * Team upload . [ Bas Couwenberg ] * Switch to cython3-legacy. Closes: #1056787 * Change liboctave-dev to octave-dev. . [ Andreas Tille ] * Remove NVCCFLAGS="-ccbin clang-9" variable Closes: #1023675 * Standards-Version: 4.6.2 (routine-update) * Rules-Requires-Root: no (routine-update) * Fix install target Checksums-Sha1: a6b52963b83cf005f5875374eb0af9819f96697b 2366 astra-toolbox_2.1.0-4.dsc 02f2dbb79be6218adc22dc36b4009e8ff56b29fe 6292 astra-toolbox_2.1.0-4.debian.tar.xz 5632f42bebb5955fcbff540b3003e9d3570cfbbf 24433 astra-toolbox_2.1.0-4_source.buildinfo Checksums-Sha256: 696057350f1aea8de82b09ce5a6dffc5657751eb67d347ab3f5f3db058810718 2366 astra-toolbox_2.1.0-4.dsc 6fc637b8648d5c91f029072672b6b8bd2750bed3c5becadac4f80065830264ef 6292 astra-toolbox_2.1.0-4.debian.tar.xz abe30c8049d2ede9010ce22d430a92815d8af3757d585eef84bf9a141476f7e1 24433 astra-toolbox_2.1.0-4_source.buildinfo Files: 972ad32b06baa0f2717d0e257f067e6e 2366 contrib/python optional astra-toolbox_2.1.0-4.dsc 5c3fc832dbe993d547193c227ae9167f 6292 contrib/python optional astra-toolbox_2.1.0-4.debian.tar.xz 2aede27689bce0e2d7367c608d554df0 24433 contrib/python optional astra-toolbox_2.1.0-4_source.buildinfo -BEGIN PGP SIGNATURE- iQJCBAEBCgAsFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmWq9rYOHHRpbGxlYUBy a2kuZGUACgkQV4oElNHGRtESwQ//TJEF8M24BnInJTFG3MoGSLIoPpO0pNaJDeN8 IE022ZIGJGS1a8jeG44x9fqoK5hxVmpCdNtMxalQs8HijjUouzOCFpgYtbDMr4+n 1hcTMW6qPAUFFMovo7IHfBY4fs5lcPvg/9t1YpUerfZxxIHFWqbbKPlKUC9ejjfU q2xB/m3WBtS3+9P6nko+kUmasx6z7ThnQmPRx3HvWpA3XxWBr26Hhkb7FPZtD1HE waQVhzG+hPRoER1Zj9DzZRwwx+gawNDddTuHitOWfTEt6bSW04ZR50hVsxAvY/gh 1fE2Za4UKFTyvhRCw7jwr74usKT7L2sC05hAkyDDe02eXXL/Eo+7V0NwsbxDdsVo uZxM0hJnwSE81ot53T/5rGr8XbxxVPPLWseVnz3CdeInczsUoajz43INjjG04oSc R9q5nPRy9t3mGgiBPpNpP1UVUcDPkILePP907Q4iaJx0v0FljTDZLryXlwqQ7c1x 5BqFMrKbWNncnt9bJC7mi7EE3QsjN4+/Oj8m9QH/OVzkZZBKMDYqa4JWTkl/wgOR RONrJv4r7fRVGqM8fvskJJ7BR06zxIf/P48prDmlU8GH+FUskaLCzCSaQocjCWat G+crXBow3tOMzSS91D0/q17FxrTT5c/a5yMRHf3SluNpQ3DyBpLNuhUvxz1vteQe 3RJz0ko= =8Rac -END PGP SIGNATURE End Message ---
Bug#1061162: pypdf2: Do not release with Trixie
Source: pypdf2 Version: 2.12.1-4 Severity: serious Tags: upstream Justification: Maintainer opinion PyPDF2 has been replaced by pypdf upstream. We should not release this package with Trixie. Rdepends should be either ported or removed. Scott K
Bug#1056841: pymatgen: ftbfs with cython 3.0.x
Am Fri, Jan 19, 2024 at 08:22:21PM +0100 schrieb Drew Parsons: > On 2024-01-19 18:52, Drew Parsons wrote: > > > > Hi Andreas, could you push your upstream and pristine-tar branches? > > Otherwise we can't use your 2023.12.18 branch. > > I see what you mean. The tag is there, the orig tarball can be regenerated > with > gbp export-orig. Good to know that you can work what is on Salsa - I have removed my local clone. Good luck Andreas. -- http://fam-tille.de
Bug#1060935: marked as done (python-crontab: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13)
Your message dated Fri, 19 Jan 2024 21:42:14 +
with message-id
and subject line Bug#1060935: fixed in python-crontab 3.0.0-3
has caused the Debian Bug report #1060935,
regarding python-crontab: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p "3.12 3.11" 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.)
--
1060935: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060935
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-crontab
Version: 3.0.0-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240115 ftbfs-trixie
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
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild plugin_pyproject:129: Building wheel for python3.12 with "build"
> module
> I: pybuild base:305: python3.12 -m build --skip-dependency-check
> --no-isolation --wheel --outdir
> /<>/.pybuild/cpython3_3.12_crontab
> * Building wheel...
> /usr/lib/python3/dist-packages/setuptools/_distutils/dist.py:265:
> UserWarning: Unknown distribution option: 'release'
> warnings.warn(msg)
> running bdist_wheel
> running build
> running build_py
> creating build
> creating build/lib
> copying crontab.py -> build/lib
> copying crontabs.py -> build/lib
> copying cronlog.py -> build/lib
> installing to build/bdist.linux-x86_64/wheel
> running install
> running install_lib
> creating build/bdist.linux-x86_64
> creating build/bdist.linux-x86_64/wheel
> copying build/lib/crontab.py -> build/bdist.linux-x86_64/wheel
> copying build/lib/cronlog.py -> build/bdist.linux-x86_64/wheel
> copying build/lib/crontabs.py -> build/bdist.linux-x86_64/wheel
> running install_egg_info
> running egg_info
> creating python_crontab.egg-info
> writing python_crontab.egg-info/PKG-INFO
> writing dependency_links to python_crontab.egg-info/dependency_links.txt
> writing requirements to python_crontab.egg-info/requires.txt
> writing top-level names to python_crontab.egg-info/top_level.txt
> writing manifest file 'python_crontab.egg-info/SOURCES.txt'
> reading manifest file 'python_crontab.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> adding license file 'COPYING'
> adding license file 'AUTHORS'
> writing manifest file 'python_crontab.egg-info/SOURCES.txt'
> Copying python_crontab.egg-info to
> build/bdist.linux-x86_64/wheel/python_crontab-3.0.0.egg-info
> running install_scripts
> creating build/bdist.linux-x86_64/wheel/python_crontab-3.0.0.dist-info/WHEEL
> creating
> '/<>/.pybuild/cpython3_3.12_crontab/.tmp-3f8e1aax/python_crontab-3.0.0-py3-none-any.whl'
> and adding 'build/bdist.linux-x86_64/wheel' to it
> adding 'cronlog.py'
> adding 'crontab.py'
> adding 'crontabs.py'
> adding 'python_crontab-3.0.0.dist-info/AUTHORS'
> adding 'python_crontab-3.0.0.dist-info/COPYING'
> adding 'python_crontab-3.0.0.dist-info/METADATA'
> adding 'python_crontab-3.0.0.dist-info/WHEEL'
> adding 'python_crontab-3.0.0.dist-info/top_level.txt'
> adding 'python_crontab-3.0.0.dist-info/RECORD'
> removing build/bdist.linux-x86_64/wheel
> Successfully built python_crontab-3.0.0-py3-none-any.whl
> I: pybuild plugin_pyproject:144: Unpacking wheel built for python3.12 with
> "installer" module
> I: pybuild plugin_pyproject:129: Building wheel for python3.11 with "build"
> module
> I: pybuild base:305: python3.11 -m build --skip-dependency-check
> --no-isolation --wheel --outdir
> /<>/.pybuild/cpython3_3.11_crontab
> * Building wheel...
> /usr/lib/python3/dist-packages/setuptools/_distutils/dist.py:265:
> UserWarning: Unknown distribution option: 'release'
> warnings.warn(msg)
> running bdist_wheel
> running build
> running build_py
> installing to build/bdist.linux-x86_64/wheel
> running install
> running install_lib
> creating build/bdist.linux-x86_64/wheel
> copying build/lib/crontab.py -> build/bdist.linux-x86_64/wheel
> copying build/lib/cronlog.py -> build/bdist.linux-x86_64/wheel
> copying build/lib/crontabs.py -> build/bdist.linux-x86_64/wheel
> running install_egg_info
> running egg_info
> writing python_crontab.egg-info/PKG-INFO
> writing dependency_links to python_crontab.egg-info/dependency_links.txt
> writing requirements to python_crontab.egg-info/requires.txt
> writing top-level names to python_c
Bug#1055686: marked as done (dm-tree ftbfs with Python 3.12)
Your message dated Fri, 19 Jan 2024 21:34:22 +
with message-id
and subject line Bug#1055686: fixed in dm-tree 0.1.8-3
has caused the Debian Bug report #1055686,
regarding dm-tree ftbfs with Python 3.12
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.)
--
1055686: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055686
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:dm-tree
Version:
Severity: important
Tags: sid trixie
User: debian-pyt...@lists.debian.org
Usertags: python3.12
dm-tree ftbfs with Python 3.12, although the build and test of the
extension succeed with 3.12. The build then fails building the docs:
debian/rules execute_before_dh_sphinxdoc
make[1]: Entering directory '/<>'
cd $(pybuild --print build_dir --name dm-tree |head -n1 |awk -F ': '
'{print $2}'); python3 -m sphinx -b html -N /<>/docs
/<>/debian/python-dm-tree-doc/usr/share/doc/python-dm-tree-doc/html
Running Sphinx v7.2.6
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 358, in
eval_config_file
exec(code, namespace) # NoQA: S102
^
File "/<>/docs/conf.py", line 34, in
import tree
File
"/<>/.pybuild/cpython3_3.12_dm-tree/build/tree/__init__.py",
line 23, in
from .sequence import _is_attrs
File
"/<>/.pybuild/cpython3_3.12_dm-tree/build/tree/sequence.py",
line 19, in
from tree import _tree
ImportError: cannot import name '_tree' from partially initialized
module 'tree' (most likely due to a circular import)
(/<>/.pybuild/cpython3_3.12_dm-tree/build/tree/__init__.py)
make[1]: *** [debian/rules:11: execute_before_dh_sphinxdoc] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:7: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit
status 2
complete build log at
https://launchpadlibrarian.net/696984001/buildlog_ubuntu-noble-amd64.dm-tree_0.1.8-2_BUILDING.txt.gz
--- End Message ---
--- Begin Message ---
Source: dm-tree
Source-Version: 0.1.8-3
Done: Michael Fladischer
We believe that the bug you reported is fixed in the latest version of
dm-tree, 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 1055...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Michael Fladischer (supplier of updated dm-tree package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Fri, 19 Jan 2024 20:58:35 +
Source: dm-tree
Architecture: source
Version: 0.1.8-3
Distribution: unstable
Urgency: low
Maintainer: Debian Python Team
Changed-By: Michael Fladischer
Closes: 1055686
Changes:
dm-tree (0.1.8-3) unstable; urgency=low
.
* Add patch to resolve circular imports of tree._tree (Closes: #1055686).
Checksums-Sha1:
7d300cd58e02ffe0f3d08aef44b31ff5d35459b7 1975 dm-tree_0.1.8-3.dsc
a3fafcdb30276d8b91d329bb871a9f062a31aec1 5404 dm-tree_0.1.8-3.debian.tar.xz
23140c98ff2f5ab9ffb1ea576213ede9755216c4 9324 dm-tree_0.1.8-3_arm64.buildinfo
Checksums-Sha256:
b9cd9f7c91ada62680564f85d0e2c3b7335f77f505d2a3816b5292094022ae3e 1975
dm-tree_0.1.8-3.dsc
942b483cd65a42a5a8dc9b6e234b4a74a65285d535b62c6e4e62fca9cd385fbc 5404
dm-tree_0.1.8-3.debian.tar.xz
de40059011c4240a2893b23d474141bccc7998a30400b0911ad52d698e1f2cce 9324
dm-tree_0.1.8-3_arm64.buildinfo
Files:
43e6ceec330e1714f2120c1d440b0543 1975 python optional dm-tree_0.1.8-3.dsc
89c7827ecfb81c311c5130e57040a1df 5404 python optional
dm-tree_0.1.8-3.debian.tar.xz
4b9725d9c3170f8a1454a37809d314e3 9324 python optional
dm-tree_0.1.8-3_arm64.buildinfo
-BEGIN PGP SIGNATURE-
iQEzBAEBCgAdFiEEqVSlRXW87UkkCnJc/9PIi5l90WoFAmWq5CoACgkQ/9PIi5l9
0WpvDwgArvjS/aYMbKbGIhaAmGM7JDwl4nmdO8PBwlwT0tw0o+R3WmgNSnXTOvNS
T+CwbZa4kSYC37J6Kklgsz8diKV7qPMRiqC7edL1YNLl0bUO9PONUBgtUcgmJptl
qftad7sIjCQYuKRQdUaaAr64rFDs1yTMaYPOnBgH0A++yK0FzjIuQqVCMRk8bDgO
K2GdHO70+XgmrKougt2l/rahXvWVyAcCE5/h7LVF/P4w3p8prR4s2eCTlxNmfuiS
fTXIXfoAH5rM3wSlu4ScOzh0p2hktZoayrcNqnYaiPSJqBUqqEq1YkQ/I7MUVdkl
OLoCUuI8aflJh+fTUsWR6/+DlC0pfw==
=u7ms
-END PGP SIGNATURE End Message ---
Bug#1060935: marked as pending in python-crontab
Control: tag -1 pending Hello, Bug #1060935 in python-crontab 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-crontab/-/commit/a4a360c0740c4f2b6012b57fe6923216fc66eaea Add patches to fix upstream tests (Closes: #1060935). (this message was generated automatically) -- Greetings https://bugs.debian.org/1060935
Processed: Bug#1060935 marked as pending in python-crontab
Processing control commands:
> tag -1 pending
Bug #1060935 [src:python-crontab] python-crontab: FTBFS: dh_auto_test: error:
pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit
code 13
Added tag(s) pending.
--
1060935: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060935
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1061159: sdaps: FTBFS: command 'sdaps_clean_i18n' has no such option 'all'
Source: sdaps
Version: 1.9.8-0.1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Dear maintainer,
sdaps fails to build from source. From my build log on amd64:
| dpkg-buildpackage: info: source package sdaps
| dpkg-buildpackage: info: source version 1.9.8-0.1
| dpkg-buildpackage: info: source distribution unstable
| dpkg-source --before-build .
| dpkg-buildpackage: info: host architecture amd64
| fakeroot debian/rules clean
| dh clean --with python3 --buildsystem=pybuild
|dh_auto_clean -O--buildsystem=pybuild
| I: pybuild base:305: python3.11 setup.py clean
| error: error in
/<>/.pybuild/cpython3_3.11_sdaps/.pydistutils.cfg: command
'sdaps_clean_i18n' has no such option 'all'
| E: pybuild pybuild:391: 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:7: clean] Error 25
| dpkg-buildpackage: error: fakeroot debian/rules clean subprocess returned
exit status 2
The full build log for riscv64 is also available here:
https://buildd.debian.org/status/fetch.php?pkg=sdaps&arch=riscv64&ver=1.9.8-0.1%2Bb1&stamp=1705322530&raw=0
The reproducible builds also show the same issue:
https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/sdaps_1.9.8-0.1.rbuild.log.gz
Regards
Aurelien
Bug#1061018: marked as done (octave-splines: FTBFS: make: *** [debian/rules:5: binary] Error 134)
Your message dated Fri, 19 Jan 2024 20:25:02 +0100 with message-id and subject line Re: Bug#1061018: octave-splines: FTBFS: make: *** [debian/rules:5: binary] Error 134 has caused the Debian Bug report #1061018, regarding octave-splines: FTBFS: make: *** [debian/rules:5: binary] Error 134 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.) -- 1061018: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061018 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: octave-splines Version: 1.3.5-2 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240115 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules binary > dh binary --buildsystem=octave >dh_update_autotools_config -O--buildsystem=octave >dh_autoreconf -O--buildsystem=octave >dh_octave_version -O--buildsystem=octave > Checking the Octave version... ok >dh_auto_configure -O--buildsystem=octave >dh_auto_build -O--buildsystem=octave >dh_auto_test -O--buildsystem=octave >create-stamp debian/debhelper-build-stamp >dh_testroot -O--buildsystem=octave >dh_prep -O--buildsystem=octave >dh_auto_install --destdir=debian/octave-splines/ -O--buildsystem=octave > octave --no-gui --no-history --silent --no-init-file --no-window-system > /usr/share/dh-octave/install-pkg.m > /<>/debian/octave-splines/usr/share/octave/packages > /<>/debian/octave-splines/usr/lib/x86_64-linux-gnu/octave/packages > For information about changes from previous versions of the splines package, > run 'news splines'. >dh_octave_check -O--buildsystem=octave > Checking package... > Run the unit tests... > Checking m files ... > [inst/tps_val_der.m] > > /<>/inst/tps_val_der.m > * shared a,b,x,y,x1,x2,y1,c,dy,dy0 > a = 2; b = -3; x = ([1:2:10 10.5 11.3])'; y = a*x; > c = tpaps(x,y,1); > * assert (a*ones(size(x)), tps_val_der(x,c,x), 1E3*eps); > [x1 x2] = meshgrid(x, x); > y1 = a*x1+b*x2; > c = tpaps([x1(:) x2(:)],y1(:),0.5); > dy = tps_val_der([x1(:) x2(:)],c,[x1(:) x2(:)]); > dy0 = tps_val_der([x1(:) x2(:)],c,[x1(:) x2(:)],false); > * assert (a*ones(size(x1(:))), dy(:, 1), 1E3*eps); > * assert (b*ones(size(x2(:))), dy(:, 2), 1E3*eps); > * assert (dy0, dy, 1E3*eps); > 4 tests, 4 passed, 0 known failure, 0 skipped > [inst/bin_values.m] > > /<>/inst/bin_values.m > * shared x, y, x_bin, y_bin, w_bin, n_bin > x = [1; 2; 2; 3; 4]; > y = [0 0; 1 1; 2 1; 3 4; 5 NaN]; > [x_bin y_bin w_bin n_bin] = bin_values(x, y); > * assert (x_bin, [1; 7/3]); > * assert (y_bin, [0 0; 2 2]); > * assert (!any(isfinite(w_bin(1, :; > * assert (w_bin(2, :), [3 1]); > * assert (n_bin, [1; 3]); > 5 tests, 5 passed, 0 known failure, 0 skipped > [inst/csaps_sel.m] > > /<>/inst/csaps_sel.m > * shared x,y,ret,p,sigma2,unc_y > x = [0:0.01:1]'; y = sin(x); > [ret,p,sigma2,unc_y] = csaps_sel(x,y,x); > malloc(): invalid size (unsorted) > fatal: caught signal Aborted -- stopping myself... > Aborted > make: *** [debian/rules:5: binary] Error 134 The full build log is available from: http://qa-logs.debian.net/2024/01/15/octave-splines_1.3.5-2_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240115;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20240115&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=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 --- Le mercredi 17 janvier 2024 à 12:47 +0100, Sébastien Villemot a écrit : > Control: block -1 by 1061049 > > Le mardi 16 janvier 2024 à 20:43 +0100, Lucas Nussbaum a écrit : > > Source: octave-splines > > Version: 1.3.5-2 > > Severity: serious > > Justification: FTBFS > > Tags: trixie sid ftbfs > > User: lu...@debian.org > > Usertags: ftbfs-20240115 ftbfs-trixie > > > > Hi, > > > > During a rebuild of all packages in sid, your package failed to build > > on amd64. > > > > >
Bug#1061017: marked as done (octave-divand: FTBFS: make: *** [debian/rules:5: binary] Error 134)
Your message dated Fri, 19 Jan 2024 20:24:41 +0100 with message-id and subject line Re: Bug#1061017: octave-divand: FTBFS: make: *** [debian/rules:5: binary] Error 134 has caused the Debian Bug report #1061017, regarding octave-divand: FTBFS: make: *** [debian/rules:5: binary] Error 134 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.) -- 1061017: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061017 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: octave-divand Version: 1.1.2+dfsg-6 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240115 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules binary > dh binary --buildsystem=octave >dh_update_autotools_config -O--buildsystem=octave >dh_autoreconf -O--buildsystem=octave >dh_octave_version -O--buildsystem=octave > Checking the Octave version... ok >dh_auto_configure -O--buildsystem=octave >dh_auto_build -O--buildsystem=octave >dh_auto_test -O--buildsystem=octave >create-stamp debian/debhelper-build-stamp >dh_testroot -O--buildsystem=octave >dh_prep -O--buildsystem=octave >dh_auto_install --destdir=debian/octave-divand/ -O--buildsystem=octave > octave --no-gui --no-history --silent --no-init-file --no-window-system > /usr/share/dh-octave/install-pkg.m > /<>/octave-divand-1.1.2\+dfsg/debian/octave-divand/usr/share/octave/packages > > /<>/octave-divand-1.1.2\+dfsg/debian/octave-divand/usr/lib/x86_64-linux-gnu/octave/packages > For information about changes from previous versions of the divand package, > run 'news divand'. >dh_octave_check -O--buildsystem=octave > Checking package... > Run the unit tests... > Checking m files ... > [inst/statevector_init.m] > > /<>/inst/statevector_init.m > * test > mask = rand(10,10) > .5; > mask_u = rand(9,10) > .5; > mask_v = rand(10,9) > .5; > sv = statevector_init(mask,mask_u,mask_v); > var = rand(10,10); > var(mask==0) = 0; > var_u = rand(9,10); > var_u(mask_u==0) = 0; > var(mask==0) = 0; > var_v = rand(10,9); > var_v(mask_v==0) = 0; > [E] = statevector_pack(sv,var,var_u,var_v); > [Ezeta2,Eu2,Ev2] = statevector_unpack(sv,E); > assert(Ezeta2,var) > assert(Eu2,var_u) > assert(Ev2,var_v) > 1 test, 1 passed, 0 known failure, 0 skipped > Checking C++ files ... > Run tests in debian/check.m > [test_divand] > run test_interp_1d: (max difference=2.77556e-16) [42m OK [0m > run test_interp_2d: (max difference=2.22045e-16) [42m OK [0m > run test_interp_regular: (max difference=2.22045e-16) [42m OK [0m > run test_sparse_diff: (max difference=0) [42m OK [0m > run test_1dvar: malloc(): invalid size (unsorted) > fatal: caught signal Aborted -- stopping myself... > Aborted > make: *** [debian/rules:5: binary] Error 134 The full build log is available from: http://qa-logs.debian.net/2024/01/15/octave-divand_1.1.2+dfsg-6_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240115;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20240115&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=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 --- Le mercredi 17 janvier 2024 à 12:42 +0100, Sébastien Villemot a écrit : > Control: block -1 by 1061049 > > Le mardi 16 janvier 2024 à 20:43 +0100, Lucas Nussbaum a écrit : > > Source: octave-divand > > Version: 1.1.2+dfsg-6 > > Severity: serious > > Justification: FTBFS > > Tags: trixie sid ftbfs > > User: lu...@debian.org > > Usertags: ftbfs-20240115 ftbfs-trixie > > > > During a rebuild of all packages in sid, your package failed to build > > on amd64. > > > > > > Relevant part (hopefully): > > > debian/rules binary > > > dh binary --buildsystem=octave > > >dh_update_autotools_config -O--buildsystem=octave > > >dh_autoreconf -O--buildsystem=octave > > >dh_octave_version -O--buildsystem=octave > > > Checki
Bug#1056841: pymatgen: ftbfs with cython 3.0.x
On 2024-01-19 18:52, Drew Parsons wrote: Hi Andreas, could you push your upstream and pristine-tar branches? Otherwise we can't use your 2023.12.18 branch. I see what you mean. The tag is there, the orig tarball can be regenerated with gbp export-orig.
Bug#1058040: pymatgen: FTBFS with Python 3.12
Source: pymatgen Followup-For: Bug #1058040 No, other way around. The new monty is causing the problem. Will need to patch or upgrade pymatgen.
Bug#1058040: pymatgen: FTBFS with Python 3.12
Source: pymatgen Followup-For: Bug #1058040 Sounds like it will need the new version of monty
Bug#1061155: cron: "crontab -e" does not report "unsafe" mail and so job output can be lost
Package: cron Version: 3.0pl1-182 Severity: grave Justification: causes non-serious data loss Dear Maintainer, * What led up to the situation? 1. A user ran "crontab -e" 2. He added the line (note the space): MAILTO=a...@example.org, b...@example.com 3. He saved and exited 4. No errors were reported to the user. * What was the outcome of this action? Subsequently, jobs ran but output was discarded. /var/log/syslog contains "UNSAFE MAIL" messages which the user cannot see. * What outcome did you expect instead? At step 4, crontab should have reported an error to the user and not applied the update. -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.15.0-91-generic (SMP w/1 CPU thread) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages cron depends on: ii cron-daemon-common 3.0pl1-182 ii init-system-helpers 1.66 ii libc62.37-13 ii libpam-runtime 1.5.2-9.1 ii libpam0g 1.5.2-9.1+b1 ii libselinux1 3.5-1+b2 ii sensible-utils 0.0.20 Versions of packages cron recommends: ii exim4-daemon-heavy [mail-transport-agent] 4.97-4+b1 Versions of packages cron suggests: pn anacron pn checksecurity ii logrotate 3.21.0-2 Versions of packages cron is related to: pn libnss-ldap pn libnss-ldapd pn libpam-ldap pn libpam-mount pn nis pn nscd -- no debconf information
Processed: qiime issues: meaningful titles
Processing commands for cont...@bugs.debian.org:
> retitle 1060965 q2-feature-classifier: AttributeError: module 'bibtexparser'
> has no attribute 'bparser'
Bug #1060965 [src:qiime] q2-feature-classifier: FTBFS: dh_auto_test: error:
pybuild --test -i python{version} -p 3.11 -s custom "--test-args=cd
{build_dir}; py.test-3 --cov=q2_feature_classifier" returned exit code 13
Bug #1060987 [src:qiime] qiime: FTBFS: AttributeError: module 'bibtexparser'
has no attribute 'bparser'
Changed Bug title to 'q2-feature-classifier: AttributeError: module
'bibtexparser' has no attribute 'bparser'' from 'q2-feature-classifier: FTBFS:
dh_auto_test: error: pybuild --test -i python{version} -p 3.11 -s custom
"--test-args=cd {build_dir}; py.test-3 --cov=q2_feature_classifier" returned
exit code 13'.
Changed Bug title to 'q2-feature-classifier: AttributeError: module
'bibtexparser' has no attribute 'bparser'' from 'qiime: FTBFS: AttributeError:
module 'bibtexparser' has no attribute 'bparser''.
> retitle 1060987 q2cli: AttributeError: module 'bibtexparser' has no attribute
> 'bparser'
Bug #1060987 [src:qiime] q2-feature-classifier: AttributeError: module
'bibtexparser' has no attribute 'bparser'
Bug #1060965 [src:qiime] q2-feature-classifier: AttributeError: module
'bibtexparser' has no attribute 'bparser'
Changed Bug title to 'q2cli: AttributeError: module 'bibtexparser' has no
attribute 'bparser'' from 'q2-feature-classifier: AttributeError: module
'bibtexparser' has no attribute 'bparser''.
Changed Bug title to 'q2cli: AttributeError: module 'bibtexparser' has no
attribute 'bparser'' from 'q2-feature-classifier: AttributeError: module
'bibtexparser' has no attribute 'bparser''.
> thank you
Stopping processing here.
Please contact me if you need assistance.
--
1060965: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060965
1060987: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060987
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: q2-feature-classifier merge with qiime/q2cli bug.
Processing commands for cont...@bugs.debian.org:
> affects 1060965 - q2-feature-classifier
Bug #1060965 [src:qiime] q2-feature-classifier: FTBFS: dh_auto_test: error:
pybuild --test -i python{version} -p 3.11 -s custom "--test-args=cd
{build_dir}; py.test-3 --cov=q2_feature_classifier" returned exit code 13
Removed indication that 1060965 affects q2-feature-classifier
> affects 1060965 + q2cli
Bug #1060965 [src:qiime] q2-feature-classifier: FTBFS: dh_auto_test: error:
pybuild --test -i python{version} -p 3.11 -s custom "--test-args=cd
{build_dir}; py.test-3 --cov=q2_feature_classifier" returned exit code 13
Added indication that 1060965 affects q2cli
> merge 1060965 1060987
Bug #1060965 [src:qiime] q2-feature-classifier: FTBFS: dh_auto_test: error:
pybuild --test -i python{version} -p 3.11 -s custom "--test-args=cd
{build_dir}; py.test-3 --cov=q2_feature_classifier" returned exit code 13
Bug #1060987 [src:qiime] qiime: FTBFS: AttributeError: module 'bibtexparser'
has no attribute 'bparser'
Merged 1060965 1060987
> affects 1060965 + q2-feature-classifier
Bug #1060965 [src:qiime] q2-feature-classifier: FTBFS: dh_auto_test: error:
pybuild --test -i python{version} -p 3.11 -s custom "--test-args=cd
{build_dir}; py.test-3 --cov=q2_feature_classifier" returned exit code 13
Bug #1060987 [src:qiime] qiime: FTBFS: AttributeError: module 'bibtexparser'
has no attribute 'bparser'
Added indication that 1060965 affects q2-feature-classifier
Added indication that 1060987 affects q2-feature-classifier
> thank you
Stopping processing here.
Please contact me if you need assistance.
--
1060965: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060965
1060987: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060987
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1060965: q2-feature-classifier: FTBFS due to qiime AttributeError: module 'bibtexparser' has no attribute 'bparser'
Control: reassign -1 src:qiime 2022.11.1-2 Control: affects -1 + q2-feature-classifier Control: merge -1 1060987 This is another manifestation of #1060987, this time affecting q2-feature-classifier: > /usr/lib/python3/dist-packages/qiime2/core/cite.py:26: in load > parser = bp.bparser.BibTexParser() > E AttributeError: module 'bibtexparser' has no attribute 'bparser' Have a nice day, :) -- .''`. Étienne Mollier : :' : pgp: 8f91 b227 c7d6 f2b1 948c 8236 793c f67e 8f0d 11da `. `' sent from /dev/pts/2, please excuse my verbosity `- signature.asc Description: PGP signature
Processed (with 1 error): q2-feature-classifier: FTBFS due to qiime AttributeError: module 'bibtexparser' has no attribute 'bparser'
Processing control commands:
> reassign -1 src:qiime 2022.11.1-2
Bug #1060965 [src:q2-feature-classifier] q2-feature-classifier: FTBFS:
dh_auto_test: error: pybuild --test -i python{version} -p 3.11 -s custom
"--test-args=cd {build_dir}; py.test-3 --cov=q2_feature_classifier" returned
exit code 13
Bug reassigned from package 'src:q2-feature-classifier' to 'src:qiime'.
No longer marked as found in versions q2-feature-classifier/2023.7.0-1.
Ignoring request to alter fixed versions of bug #1060965 to the same values
previously set
Bug #1060965 [src:qiime] q2-feature-classifier: FTBFS: dh_auto_test: error:
pybuild --test -i python{version} -p 3.11 -s custom "--test-args=cd
{build_dir}; py.test-3 --cov=q2_feature_classifier" returned exit code 13
Marked as found in versions qiime/2022.11.1-2.
> affects -1 + q2-feature-classifier
Bug #1060965 [src:qiime] q2-feature-classifier: FTBFS: dh_auto_test: error:
pybuild --test -i python{version} -p 3.11 -s custom "--test-args=cd
{build_dir}; py.test-3 --cov=q2_feature_classifier" returned exit code 13
Added indication that 1060965 affects q2-feature-classifier
> merge -1 1060987
Bug #1060965 [src:qiime] q2-feature-classifier: FTBFS: dh_auto_test: error:
pybuild --test -i python{version} -p 3.11 -s custom "--test-args=cd
{build_dir}; py.test-3 --cov=q2_feature_classifier" returned exit code 13
Unable to merge bugs because:
affects of #1060987 is 'q2cli' not 'q2-feature-classifier'
Failed to merge 1060965: Did not alter merged bugs.
--
1060965: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060965
1060987: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060987
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: reassign 1060987 to qiime 2022.11.1-2
Processing commands for cont...@bugs.debian.org: > reassign 1060987 src:qiime 2022.11.1-2 Bug #1060987 [src:q2cli] qiime: FTBFS: AttributeError: module 'bibtexparser' has no attribute 'bparser' Bug reassigned from package 'src:q2cli' to 'src:qiime'. No longer marked as found in versions q2cli/2022.11.1-2. Ignoring request to alter fixed versions of bug #1060987 to the same values previously set Bug #1060987 [src:qiime] qiime: FTBFS: AttributeError: module 'bibtexparser' has no attribute 'bparser' Marked as found in versions qiime/2022.11.1-2. > thank you Stopping processing here. Please contact me if you need assistance. -- 1060987: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060987 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Move where it was fixed
Processing commands for cont...@bugs.debian.org: > reassign 1056042 python3-uncertainties Bug #1056042 [src:xrayutilities] xrayutilities ftbfs with Python 3.12 Bug reassigned from package 'src:xrayutilities' to 'python3-uncertainties'. No longer marked as found in versions xrayutilities/1.7.4-1. Ignoring request to alter fixed versions of bug #1056042 to the same values previously set > affects 1056042 src:xrayutilities Bug #1056042 [python3-uncertainties] xrayutilities ftbfs with Python 3.12 Added indication that 1056042 affects src:xrayutilities > close 1056042 3.1.7-1 Bug #1056042 [python3-uncertainties] xrayutilities ftbfs with Python 3.12 Marked as fixed in versions uncertainties/3.1.7-1. Bug #1056042 [python3-uncertainties] xrayutilities ftbfs with Python 3.12 Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1056042: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056042 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed (with 1 error): q2cli: FTBFS: AttributeError: module 'bibtexparser' has no attribute 'bparser'
Processing control commands:
> reassign -1 src:qiime/2022.11.1-2
Unknown command or malformed arguments to command.
> retitle -1 qiime: FTBFS: AttributeError: module 'bibtexparser' has no
> attribute 'bparser'
Bug #1060987 [src:q2cli] q2cli: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p 3.11 returned exit code 13
Changed Bug title to 'qiime: FTBFS: AttributeError: module 'bibtexparser' has
no attribute 'bparser'' from 'q2cli: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p 3.11 returned exit code 13'.
> affects -1 + q2cli
Bug #1060987 [src:q2cli] qiime: FTBFS: AttributeError: module 'bibtexparser'
has no attribute 'bparser'
Added indication that 1060987 affects q2cli
--
1060987: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060987
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1060987: q2cli: FTBFS: AttributeError: module 'bibtexparser' has no attribute 'bparser'
Control: reassign -1 src:qiime/2022.11.1-2 Control: retitle -1 qiime: FTBFS: AttributeError: module 'bibtexparser' has no attribute 'bparser' Control: affects -1 + q2cli This looks to be the main issue: > /usr/lib/python3/dist-packages/qiime2/core/cite.py:26: in load > parser = bp.bparser.BibTexParser() > E AttributeError: module 'bibtexparser' has no attribute 'bparser' Since update of bibtexparser to 2.0.0b, the bparser has been either removed or not reimplemented yet. The documentation exposed in the bibtexparser source code gives little clue how to migrate from that particular situation. Quick lookup at contemporary qiime source code[1] shows the invocation is still around as of today, so an upstream version bump won't help yet. Maybe an option could be to avoid attemting to apply the bibtex parser customization when the bparser does not exist anymore? I'm not entirely confident on the side effects downstream. Only other option I can think of would be to wait and see how the bibtexparser v2.0.0 release will behave if there are planned changes on the parser or unicode customizations front. [1]: https://github.com/qiime2/qiime2/blob/dev/qiime2/core/cite.py Have a nice day, :) -- .''`. Étienne Mollier : :' : pgp: 8f91 b227 c7d6 f2b1 948c 8236 793c f67e 8f0d 11da `. `' sent from /dev/pts/3, please excuse my verbosity `-on air: Fish - Little Man What Now? signature.asc Description: PGP signature
Bug#1056841: pymatgen: ftbfs with cython 3.0.x
On 2024-01-16 17:55, Andreas Tille wrote: Control: tags -1 pending Hi, I've applied the patch in Git and also tried to upgrade to latest upstream since there is a chance that other Python3.12 issues might be fixed. Unfortunately the upgrade is all but straightforward and I gave up finally over the changes in the sphinx documention where finally some files are missing. I've created a branch 2023.12.18 which fails with Sphinx error: root file /build/pymatgen-2023.12.18+dfsg1/docs/apidoc/index.rst not found I hope that my preliminary work might be helpful for the package but I have to give up now due to time constraints. Hope this helps Andreas. Hi Andreas, could you push your upstream and pristine-tar branches? Otherwise we can't use your 2023.12.18 branch. Drew
Bug#1060970: marked as done (openturns: FTBFS: make[2]: *** [Makefile:94: test] Error 8)
Your message dated Fri, 19 Jan 2024 17:40:12 + with message-id and subject line Bug#1061049: fixed in suitesparse 1:7.5.1+dfsg-2 has caused the Debian Bug report #1061049, regarding openturns: FTBFS: make[2]: *** [Makefile:94: test] Error 8 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.) -- 1061049: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061049 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: openturns Version: 1.21.1-4 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240115 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[2]: Entering directory '/<>/builddir' > Running tests... > /usr/bin/ctest --force-new-ctest-process -j8 -R cppcheck > Test project /<>/builddir > Start 1: cppcheck_Object_std > Start 2: cppcheck_OStream_std > Start 3: cppcheck_PersistentObject_std > Start 4: cppcheck_Pointer_std > Start 5: cppcheck_Pointer_cast > Start 6: cppcheck_Exception_std > Start 7: cppcheck_Log_std > Start 8: cppcheck_IdFactory_std > 1/530 Test #4: cppcheck_Pointer_std > . Passed0.08 sec > Start 9: cppcheck_ComparisonOperator_std > 2/530 Test #1: cppcheck_Object_std > .. Passed0.09 sec > Start 10: cppcheck_Study_saveload > 3/530 Test #2: cppcheck_OStream_std > . Passed0.11 sec > Start 11: cppcheck_Study_h5 > 4/530 Test #5: cppcheck_Pointer_cast > Passed0.11 sec > Start 12: cppcheck_ResourceMap_std > 5/530 Test #8: cppcheck_IdFactory_std > ... Passed0.12 sec > Start 13: cppcheck_Catalog_std > 6/530 Test #3: cppcheck_PersistentObject_std > Passed0.13 sec > Start 14: cppcheck_AtomicInt_std > 7/530 Test #6: cppcheck_Exception_std > ... Passed0.13 sec > Start 15: cppcheck_Collection_std > 8/530 Test #7: cppcheck_Log_std > . Passed0.19 sec > Start 16: cppcheck_Indices_std > 9/530 Test #9: cppcheck_ComparisonOperator_std > .. Passed0.12 sec > Start 17: cppcheck_IndicesCollection_std > 10/530 Test #12: cppcheck_ResourceMap_std > . Passed0.11 sec > Start 18: cppcheck_Description_std > 11/530 Test #13: cppcheck_Catalog_std > . Passed0.11 sec > Start 19: cppcheck_Point_std > 12/530 Test #15: cppcheck_Collection_std > .. Passed0.22 sec > Start 20: cppcheck_Point_description > 13/530 Test #16: cppcheck_Indices_std > . Passed0.23 sec > Start 21: cppcheck_Matrix_std > 14/530 Test #17: cppcheck_IndicesCollection_std > ... Passed0.28 sec > Start 22: cppcheck_SparseMatrix_std > 15/530 Test #18: cppcheck_Description_std > . Passed0.27 sec > Start 23: cppcheck_IdentityMatrix_std > 16/530 Test #19: cppcheck_Point_std > ... Passed0.26 sec > Start 24: cppcheck_Tensor_std > 17/530 Test #21: cppcheck_Matrix_std > .. Passed0.19 sec > Start 25: cppcheck_ComplexTensor_std > 18/530 Test #14: cppcheck_AtomicInt_std > ... Passed0.51 sec > Start 26: cppcheck_SymmetricTensor_std > 19/530 Test #24: cppcheck_Tensor_std > .. Passed0.18 sec > Start 27: cppcheck_SquareMatrix_std > 20/530 Test #23: cppcheck_IdentityMatrix_std > .. Passed0.21 sec > Start 28: cppcheck_TriangularMatrix_std > 21/530 Test #22: cppcheck_SparseMatrix_std > Passed0.23 sec > Start 29: cppcheck_SymmetricMatrix_std > 22/530 Test #20: cppcheck_Point_description > .
Bug#1061123: marked as done (suitesparse breaks octave autopkgtest: it hangs)
Your message dated Fri, 19 Jan 2024 17:40:12 + with message-id and subject line Bug#1061049: fixed in suitesparse 1:7.5.1+dfsg-2 has caused the Debian Bug report #1061049, regarding suitesparse breaks octave autopkgtest: it hangs 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.) -- 1061049: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061049 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: suitesparse, octave Control: found -1 suitesparse/1:7.5.1+dfsg-1 Control: found -1 octave/8.4.0-1 Severity: serious Tags: sid trixie User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a recent upload of suitesparse the autopkgtest of octave fails in testing when that autopkgtest is run with the binary packages of suitesparse from unstable. It passes when run with only packages from testing. In tabular form: passfail suitesparsefrom testing1:7.5.1+dfsg-1 octave from testing8.4.0-1 all others from testingfrom testing I copied some of the output at the bottom of this report. Normally the test only takes a couple of minutes, now it times out after 2:47 hours. I'm notifying you already as this is currently also impacting the perl transition via texinfo. Currently this regression is blocking the migration of suitesparse 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=suitesparse https://ci.debian.net/data/autopkgtest/testing/amd64/o/octave/41870107/log.gz 94s 94s Integrated test scripts: 94s 94s liboctave/array/Array-base.cc-tst .. pass 21/21 94s liboctave/array/CMatrix.cc-tst . pass 11/11 94s liboctave/array/CSparse.cc-tst . pass 10/10 94s liboctave/array/Sparse.cc-tst .. pass 107/107 94s liboctave/array/dMatrix.cc-tst . pass 10/10 94s liboctave/array/dSparse.cc-tst . pass 12/12 94s liboctave/array/fCMatrix.cc-tst pass 11/11 94s liboctave/array/fMatrix.cc-tst . pass 8/894s liboctave/array/idx-vector.cc-tst .. pass2/294s liboctave/util/oct-inttypes.cc-tst . pass 28/28 94s libinterp/corefcn/Cell.cc-tst .. pass5/594s libinterp/corefcn/__contourc__.cc-tst .. pass 1/194s libinterp/corefcn/__dsearchn__.cc-tst .. pass1/194s libinterp/corefcn/__eigs__.cc-tst .. pass 1/194s libinterp/corefcn/__ichol__.cc-tst . pass1/194s libinterp/corefcn/__ilu__.cc-tst ... pass 1/195s libinterp/corefcn/__isprimelarge__.cc-tst .. pass 10/10 95s libinterp/corefcn/__lin_interpn__.cc-tst ... pass 1/195s libinterp/corefcn/__magick_read__.cc-tst ... pass4/495s libinterp/corefcn/__pchip_deriv__.cc-tst ... pass 4/495s libinterp/corefcn/__qp__.cc-tst pass1/195s libinterp/corefcn/amd.cc-tst ... pass 4/495s libinterp/corefcn/besselj.cc-tst ... pass 200/200 96s libinterp/corefcn/bitfcns.cc-tst ... pass 60/60 100s libinterp/corefcn/bsxfun.cc-tst pass 82/82 100s libinterp/corefcn/call-stack.cc-tst pass 3/3 102s libinterp/corefcn/cellfun.cc-tst ... pass 134/134 102s libinterp/corefcn/chol.cc-tst ..malloc(): invalid size (unsorted) 10094s fatal: caught signal autopkgtest [06:55:22]: ERROR: timed out on command "su -s /bin/bash debci -c set -e; exec /tmp/autopkgtest-lxc.gixhwtgb/downtmp/wrapper.sh --artifacts=/tmp/autopkgtest-lxc.gixhwtgb/downtmp/upstream-testsuite-artifacts --chdir=/tmp/autopkgt
Bug#1060952: marked as done (persalys: FTBFS: make[2]: *** [Makefile:94: test] Error 8)
Your message dated Fri, 19 Jan 2024 17:40:12 + with message-id and subject line Bug#1061049: fixed in suitesparse 1:7.5.1+dfsg-2 has caused the Debian Bug report #1061049, regarding persalys: FTBFS: make[2]: *** [Makefile:94: test] Error 8 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.) -- 1061049: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061049 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: persalys Version: 15.0+ds-3 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240115 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[2]: Entering directory '/<>/builddir' > Running tests... > /usr/bin/ctest --force-new-ctest-process -j8 -R pyinstallcheck > Test project /<>/builddir > Start 23: pyinstallcheck_SymbolicPhysicalModel_std > Start 24: pyinstallcheck_PythonPhysicalModel_std > Start 25: pyinstallcheck_PythonPhysicalModel_mp > Start 26: pyinstallcheck_DesignOfExperiment_mp > Start 27: pyinstallcheck_CouplingPhysicalModel_std > Start 28: pyinstallcheck_AnsysParser_std > Start 29: pyinstallcheck_CouplingPhysicalModel_logistic > Start 30: pyinstallcheck_features > 1/47 Test #30: pyinstallcheck_features . > Passed0.60 sec > Start 31: pyinstallcheck_Cogeneration_std > 2/47 Test #23: pyinstallcheck_SymbolicPhysicalModel_std > Passed0.64 sec > Start 32: pyinstallcheck_Crue_std > 3/47 Test #28: pyinstallcheck_AnsysParser_std .. > Passed0.72 sec > Start 33: pyinstallcheck_DesignOfExperiment_std > 4/47 Test #29: pyinstallcheck_CouplingPhysicalModel_logistic ... > Passed0.78 sec > Start 34: pyinstallcheck_AxialStressedBeam_std > 5/47 Test #26: pyinstallcheck_DesignOfExperiment_mp > Passed0.79 sec > Start 35: pyinstallcheck_CantileverBeam_std > 6/47 Test #24: pyinstallcheck_PythonPhysicalModel_std .. > Passed1.16 sec > Start 36: pyinstallcheck_DataModel_std > 7/47 Test #25: pyinstallcheck_PythonPhysicalModel_mp ... > Passed1.22 sec > Start 37: pyinstallcheck_FunctionalChaosAnalysis_std > 8/47 Test #32: pyinstallcheck_Crue_std . > Passed0.82 sec > Start 38: pyinstallcheck_KrigingAnalysis_std > 9/47 Test #33: pyinstallcheck_DesignOfExperiment_std ... > Passed0.81 sec > Start 39: pyinstallcheck_MetaModelAnalysis_std > 10/47 Test #34: pyinstallcheck_AxialStressedBeam_std > Passed0.82 sec > Start 40: pyinstallcheck_PolynomialRegressionAnalysis_std > 11/47 Test #39: pyinstallcheck_MetaModelAnalysis_std > ***Failed0.53 sec > *** stack smashing detected ***: terminated > Aborted > > Start 41: pyinstallcheck_MonteCarloAnalysis_std > 12/47 Test #37: pyinstallcheck_FunctionalChaosAnalysis_std .. > Passed0.86 sec > Start 42: pyinstallcheck_MonteCarloReliabilityAnalysis_std > 13/47 Test #36: pyinstallcheck_DataModel_std > Passed0.94 sec > Start 43: pyinstallcheck_ImportanceSamplingAnalysis_std > 14/47 Test #35: pyinstallcheck_CantileverBeam_std ... > Passed1.47 sec > Start 44: pyinstallcheck_FORMAnalysis_std > 15/47 Test #38: pyinstallcheck_KrigingAnalysis_std .. > Passed0.83 sec > Start 45: pyinstallcheck_SORMAnalysis_std > 16/47 Test #31: pyinstallcheck_Cogeneration_std . > Passed1.92 sec > Start 46: pyinstallcheck_FORMImportanceSamplingAnalysis_std > 17/47 Test #42: pyinstallcheck_MonteCarloReliabilityAnalysis_std > Passed0.60 sec > Start 47: pyinstallcheck_TaylorExpansionMomentsAnalysis_std > 18/47 Test #27: pyinstallcheck_CouplingPhysicalModel_std > Passed2.82 sec > Start 48: pyinstallcheck_SobolAnalysis_std > 19/47 Test #44: pyinstallcheck_FORMAnalysis_std . > Passed0.58 sec > Start 49: pyinstallcheck_SRCAnalysis_std > 20/47 Test #43: pyinstallcheck_ImportanceSamplingAnalysis_std ... > Passed0.80 sec > Start 50: pyinstallcheck_LimitState_std > 21/47 Test #45: pyinstallcheck_SORMAnalysis_std . > Passed0.65 sec > Start 51: pyins
Bug#1061049: marked as done (libsuitesparse-dev: libsuitesparse-dev 7.4.0 has an ABI break in libcholmod5 without bumping to "libcholmod6")
Your message dated Fri, 19 Jan 2024 17:40:12 +
with message-id
and subject line Bug#1061049: fixed in suitesparse 1:7.5.1+dfsg-2
has caused the Debian Bug report #1061049,
regarding libsuitesparse-dev: libsuitesparse-dev 7.4.0 has an ABI break in
libcholmod5 without bumping to "libcholmod6"
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.)
--
1061049: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061049
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libsuitesparse-dev
Version: 1:7.3.1+dfsg-2
Severity: serious
X-Debbugs-Cc: none, Dima Kogan
Hi. I'm chasing down
http://bugs.debian.org/1060986
The problem is that mrcal uses libdogleg, which contains
typedef struct
{
cholmod_common common;
} dogleg_solverContext_t;
The existing "libdogleg2" package was built against libsuitesparse-dev
7.3, so it must be linked with packages that use that ABI. But in
suitesparse 7.4 the cholmod_common structure has a new member at the
end:
FILE *blas_dump ; // only used if CHOLMOD is compiled with -DBLAS_DUMP
This is in CHOLMOD/Include/cholmod.h
This extra member changes sizeof(cholmod_common), which changes the ABI,
causing the crash. One way to fix this is to bump the SONAME of
libcholmod.
Thanks.
--- End Message ---
--- Begin Message ---
Source: suitesparse
Source-Version: 1:7.5.1+dfsg-2
Done: Sébastien Villemot
We believe that the bug you reported is fixed in the latest version of
suitesparse, 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 1061...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Sébastien Villemot (supplier of updated suitesparse
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Fri, 19 Jan 2024 17:54:36 +0100
Source: suitesparse
Architecture: source
Version: 1:7.5.1+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team
Changed-By: Sébastien Villemot
Closes: 1061049
Changes:
suitesparse (1:7.5.1+dfsg-2) unstable; urgency=medium
.
* cholmod-abi-fix.patch: new patch taken from upstream.
Reverts ABI break introduced in suitesparse 1:7.4.0+dfsg-1.
(Closes: #1061049)
Checksums-Sha1:
985e0cc69527c78fafea67567ab5503b73b76853 3302 suitesparse_7.5.1+dfsg-2.dsc
7d3a476c7abc447f4c64f3d0b67fb1f48c2ab07c 26708
suitesparse_7.5.1+dfsg-2.debian.tar.xz
17d52de377e5efa979274f4df22f8b11c79cd1f9 21173
suitesparse_7.5.1+dfsg-2_amd64.buildinfo
Checksums-Sha256:
8b55f7ca28d7940534fa5f93a6669ed8aa404ef974c398b0c056db1bf7f20b2c 3302
suitesparse_7.5.1+dfsg-2.dsc
45ac2b9a116c506525094c409046ac6282a4c8196cc326bb2cfcded4e635f71e 26708
suitesparse_7.5.1+dfsg-2.debian.tar.xz
d83c393ca9f588d8a2a525304c136c06c2f4feb75e451be81c880a1aaaeefc30 21173
suitesparse_7.5.1+dfsg-2_amd64.buildinfo
Files:
d138915da05ca469fe4ebf0d90049945 3302 math optional
suitesparse_7.5.1+dfsg-2.dsc
ac23141f6d6dc7a8b6eac7bf551189d1 26708 math optional
suitesparse_7.5.1+dfsg-2.debian.tar.xz
4b49409070a0b94a3fb4d5a65a033c71 21173 math optional
suitesparse_7.5.1+dfsg-2_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEEU5UdlScuDFuCvoxKLOzpNQ7OvkoFAmWqrtwACgkQLOzpNQ7O
vkrJoA/9EktFUTLJ68wO2lkBh8QqrgxxygEiofYaUDWQUhNTx3FjhM3JduWWkt0m
bwJRq6q+rhI000iw942mE/XcazyXDUYWnvA722OuLNBhkudgSG9t+S3+0AvoX8tW
IGrA3LUm+txpb1U85AXtsg9XhS5Ds+SmEd5pebhVGHUDTGRJUNp25TvdheNxlwqu
HpNFcIS6Y9GbrXXrtfY7eHu1fobNbAbLFRuFO3uZoJahZYNFl0cGw0HORHrvPvRg
yD2oUjZYvNpX9EA0CM/5/YXe0ZssobGe6l4N4k3wiPqOEF+45/k4mtYHyrHfnu1U
YDds7uFho0tGgylN2NLl0JnzkT5tdnGO+VcxY+qdjzEmXgtEsCMgkCAGdG7vCtQD
6iPK6q6HvJtU62Vl4cv0soUjElycC+F5++BdbmTM1/BlmNxJ5k70pxWALVFgnmQx
5VcZETVYA/F6Xgs/2SC0mtYenPVZ5mJiAIEBVInN85d3aZcqmDWbD1BpjFy1ealU
dTkIdX2qYoy5phBFF448XmwTnUPKiAbEB1Ol03BkqA7FDD6/1HceFsHGkYW2MvY9
DHvYYWa5AnvoJ0q8QoCGUel/QvlmYu/NSnQ3isIu2o3CXPLdKjp7bqkTIY3N2VTo
9E4/2nX/aTj3JBLrav8pAFCVnuFohc66KHthZrSX1rG6SGkAsAo=
=74FC
-END PGP SIGNATURE End Message ---
Bug#1061126: marked as done (mysql-8.0: Security fixes from January 2024 CPU)
Your message dated Fri, 19 Jan 2024 17:17:45 + with message-id and subject line Bug#1061126: fixed in mysql-8.0 8.0.36-1 has caused the Debian Bug report #1061126, regarding mysql-8.0: Security fixes from January 2024 CPU 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.) -- 1061126: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061126 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mysql-8.0 Version: 8.0.35-1 Severity: grave Tags: security upstream Justification: user security hole X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, See https://www.oracle.com/security-alerts/cpujan2024.html#AppendixMSQL for a list of CVEs affecting src:mysql-8.0. Regards, Salvatore --- End Message --- --- Begin Message --- Source: mysql-8.0 Source-Version: 8.0.36-1 Done: Lena Voytek We believe that the bug you reported is fixed in the latest version of mysql-8.0, 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 1061...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Lena Voytek (supplier of updated mysql-8.0 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 17 Jan 2024 09:23:59 -0700 Source: mysql-8.0 Built-For-Profiles: noudeb Architecture: source Version: 8.0.36-1 Distribution: unstable Urgency: medium Maintainer: Debian MySQL Maintainers Changed-By: Lena Voytek Closes: 1061126 Launchpad-Bugs-Fixed: 1999075 2024276 Changes: mysql-8.0 (8.0.36-1) unstable; urgency=medium . [ Lena Voytek ] * Imported upstream version 8.0.36 to fix security issues - https://www.oracle.com/security-alerts/cpujan2024.html#AppendixMSQL - CVE-2023-5363 CVE-2023-39975 CVE-2024-20960 CVE-2024-20961 CVE-2024-20962 CVE-2024-20963 CVE-2024-20964 CVE-2024-20965 CVE-2024-20966 CVE-2024-20967 CVE-2024-20968 CVE-2024-20969 CVE-2024-20970 CVE-2024-20971 CVE-2024-20972 CVE-2024-20973 CVE-2024-20974 CVE-2024-20975 CVE-2024-20976 CVE-2024-20977 CVE-2024-20978 CVE-2024-20981 CVE-2024-20982 CVE-2024-20983 CVE-2024-20984 CVE-2024-20985 Upstream release notes: - https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-36.html (Closes: #1061126) * d/p/revert_faster_tls_model.patch: Refresh . [ Marc Deslauriers ] * Removed patch no longer needed with 8.0.35 - debian/patches/revert-be8348a7.patch: fix crash on startup on armhf * Enable test suite on armhf (LP: #2024276) - debian/rules: check for failures in armhf tests - debian/patches/suppress_armhf_test_warning.patch: suppress warning about the CYCLE timer not being available on armhf. (LP: #1999075) - debian/patches/disable_64bits_time_armhf.patch: specify armhf doesn't have a 64bit timer in mysql-test/include/have_64bits_time.inc. Checksums-Sha1: 6d64eeab77cf5e2157085a5a362bef9ff611b9ee 3750 mysql-8.0_8.0.36-1.dsc fdbf5b1b37a5d882643695593ca25d0a75eb69ed 438154682 mysql-8.0_8.0.36.orig.tar.gz 63697ffd9d95840508e0575471d52f6ed04fd7ab 833 mysql-8.0_8.0.36.orig.tar.gz.asc d41437b654e883e911a172e6139af7cf004f5353 145388 mysql-8.0_8.0.36-1.debian.tar.xz 019fa1a38008684aec69d2028657c1a130029206 10299 mysql-8.0_8.0.36-1_source.buildinfo Checksums-Sha256: 7b8fc4d8c4bf9b3e0a5a4c8e4f9afcc0e179be9b0c77fdb7a3e66eab4c591f76 3750 mysql-8.0_8.0.36-1.dsc 429c5f69f3722e31807e74119d157a023277af210bfee513443cae60ebd2a86d 438154682 mysql-8.0_8.0.36.orig.tar.gz edce2ab3083d35693206c1d4065f9946919c05be6493e946029ef69791078f49 833 mysql-8.0_8.0.36.orig.tar.gz.asc c6a721db60e9f8c45a5b23d683dd42a4d9bb7043b6262ed6ec4c59a37775238a 145388 mysql-8.0_8.0.36-1.debian.tar.xz da3527359a066c47d3fa68851a25cdf0945fd99407b5f7b8ed1b294fc25f069e 10299 mysql-8.0_8.0.36-1_source.buildinfo Files: bbd33d89f690d8b1b7a5836499f523ee 3750 database optional mysql-8.0_8.0.36-1.dsc 6708e66d69bafc0dd7b481468e192203 438154682 database optional mysql-8.0_8.0.36.orig.tar.gz afc548c1ccd65441d08a81b22293 833 database optional mysql-8.0_8.0.36.orig.tar.gz.asc 234ec00cde3b548d4373042aca6a561a 145388 database optional mysql-8.0_8.0.36-1.debian.tar.xz 22a84e4c2ca992d56e820b7b8e1
Processed: tagging 1061049
Processing commands for cont...@bugs.debian.org: > tags 1061049 - ftbfs Bug #1061049 [libsuitesparse-dev] libsuitesparse-dev: libsuitesparse-dev 7.4.0 has an ABI break in libcholmod5 without bumping to "libcholmod6" Bug #1060952 [libsuitesparse-dev] persalys: FTBFS: make[2]: *** [Makefile:94: test] Error 8 Bug #1060970 [libsuitesparse-dev] openturns: FTBFS: make[2]: *** [Makefile:94: test] Error 8 Bug #1061123 [libsuitesparse-dev] suitesparse breaks octave autopkgtest: it hangs Removed tag(s) ftbfs. Removed tag(s) ftbfs. Removed tag(s) ftbfs. Removed tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 1060952: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060952 1060970: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060970 1061049: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061049 1061123: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061123 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: RC bugs in openturns and persalys are caused by recent suitesparse update
Processing commands for cont...@bugs.debian.org: > reassign 1060952 libsuitesparse-dev Bug #1060952 [src:persalys] persalys: FTBFS: make[2]: *** [Makefile:94: test] Error 8 Bug reassigned from package 'src:persalys' to 'libsuitesparse-dev'. No longer marked as found in versions persalys/15.0+ds-3. Ignoring request to alter fixed versions of bug #1060952 to the same values previously set > reassign 1060970 libsuitesparse-dev Bug #1060970 [src:openturns] openturns: FTBFS: make[2]: *** [Makefile:94: test] Error 8 Bug reassigned from package 'src:openturns' to 'libsuitesparse-dev'. No longer marked as found in versions openturns/1.21.1-4. Ignoring request to alter fixed versions of bug #1060970 to the same values previously set > forcemerge 1061049 1060952 1060970 Bug #1061049 [libsuitesparse-dev] libsuitesparse-dev: libsuitesparse-dev 7.4.0 has an ABI break in libcholmod5 without bumping to "libcholmod6" Bug #1061123 [libsuitesparse-dev] suitesparse breaks octave autopkgtest: it hangs Bug #1060952 [libsuitesparse-dev] persalys: FTBFS: make[2]: *** [Makefile:94: test] Error 8 Set Bug forwarded-to-address to 'https://github.com/DrTimothyAldenDavis/SuiteSparse/issues/741'. 1061018 was blocked by: 1061123 1061049 1061018 was not blocking any bugs. Added blocking bug(s) of 1061018: 1060952 1061017 was blocked by: 1061123 1061049 1061017 was not blocking any bugs. Added blocking bug(s) of 1061017: 1060952 1060986 was blocked by: 1061049 1061123 1060986 was not blocking any bugs. Added blocking bug(s) of 1060986: 1060952 Added indication that 1060952 affects ceres-solver,octave,libdogleg2 Marked as found in versions suitesparse/1:7.4.0+dfsg-1. Added tag(s) upstream. Bug #1061049 [libsuitesparse-dev] libsuitesparse-dev: libsuitesparse-dev 7.4.0 has an ABI break in libcholmod5 without bumping to "libcholmod6" Added tag(s) ftbfs. Added tag(s) ftbfs. Bug #1060970 [libsuitesparse-dev] openturns: FTBFS: make[2]: *** [Makefile:94: test] Error 8 Set Bug forwarded-to-address to 'https://github.com/DrTimothyAldenDavis/SuiteSparse/issues/741'. 1061017 was blocked by: 1060952 1061123 1061049 1061017 was not blocking any bugs. Added blocking bug(s) of 1061017: 1060970 1060986 was blocked by: 1061049 1061123 1060952 1060986 was not blocking any bugs. Added blocking bug(s) of 1060986: 1060970 1061018 was blocked by: 1061049 1061123 1060952 1061018 was not blocking any bugs. Added blocking bug(s) of 1061018: 1060970 Added indication that 1060970 affects ceres-solver,octave,libdogleg2 Marked as found in versions suitesparse/1:7.4.0+dfsg-1. Added tag(s) upstream. Bug #1061123 [libsuitesparse-dev] suitesparse breaks octave autopkgtest: it hangs Merged 1060952 1060970 1061049 1061123 > affects 1061049 + src:openturns src:persalys Bug #1061049 [libsuitesparse-dev] libsuitesparse-dev: libsuitesparse-dev 7.4.0 has an ABI break in libcholmod5 without bumping to "libcholmod6" Bug #1060952 [libsuitesparse-dev] persalys: FTBFS: make[2]: *** [Makefile:94: test] Error 8 Bug #1060970 [libsuitesparse-dev] openturns: FTBFS: make[2]: *** [Makefile:94: test] Error 8 Bug #1061123 [libsuitesparse-dev] suitesparse breaks octave autopkgtest: it hangs Added indication that 1061049 affects src:openturns and src:persalys Added indication that 1060952 affects src:openturns and src:persalys Added indication that 1060970 affects src:openturns and src:persalys Added indication that 1061123 affects src:openturns and src:persalys > thanks Stopping processing here. Please contact me if you need assistance. -- 1060952: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060952 1060970: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060970 1060986: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060986 1061017: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061017 1061018: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061018 1061049: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061049 1061123: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061123 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed (with 2 errors): RC bugs in openturns and persalys are caused by recent suitesparse update
Processing commands for cont...@bugs.debian.org: > forcemerge 1061049 1060952 1060970 Bug #1061049 [libsuitesparse-dev] libsuitesparse-dev: libsuitesparse-dev 7.4.0 has an ABI break in libcholmod5 without bumping to "libcholmod6" Bug #1061123 [libsuitesparse-dev] suitesparse breaks octave autopkgtest: it hangs Unable to merge bugs because: package of #1060970 is 'src:openturns' not 'libsuitesparse-dev' package of #1060952 is 'src:persalys' not 'libsuitesparse-dev' Failed to forcibly merge 1061049: Did not alter merged bugs. > affects 1061049 + src:openturns src:persalys Failed to mark 1061049 as affecting package(s): failed to get lock on /srv/bugs.debian.org/spool/lock/1061049 -- Unable to lock /srv/bugs.debian.org/spool/lock/1061049 Resource temporarily unavailable. Unable to lock /srv/bugs.debian.org/spool/lock/1061049 Resource temporarily unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692. Unable to lock /srv/bugs.debian.org/spool/lock/1061049 Resource temporarily unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692. Unable to lock /srv/bugs.debian.org/spool/lock/1061049 Resource temporarily unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692. Unable to lock /srv/bugs.debian.org/spool/lock/1061049 Resource temporarily unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692. Unable to lock /srv/bugs.debian.org/spool/lock/1061049 Resource temporarily unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692. Unable to lock /srv/bugs.debian.org/spool/lock/1061049 Resource temporarily unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692. Unable to lock /srv/bugs.debian.org/spool/lock/1061049 Resource temporarily unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692. Unable to lock /srv/bugs.debian.org/spool/lock/1061049 Resource temporarily unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692. Unable to lock /srv/bugs.debian.org/spool/lock/1061049 Resource temporarily unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692. at /usr/local/lib/site_perl/Debbugs/Common.pm line 650. > thanks Stopping processing here. Please contact me if you need assistance. -- 1060952: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060952 1060970: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060970 1061049: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061049 1061123: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061123 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: armhf: h5py's tests expose unaligned memory accesses during the build
Processing control commands: > forwarded 1061063 https://github.com/h5py/h5py/issues/1927 Bug #1061063 [src:h5py] armhf: h5py's tests expose unaligned memory accesses during the build Set Bug forwarded-to-address to 'https://github.com/h5py/h5py/issues/1927'. -- 1061063: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061063 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1061063: armhf: h5py's tests expose unaligned memory accesses during the build
Source: h5py Followup-For: Bug #1061063 Control: forwarded 1061063 https://github.com/h5py/h5py/issues/1927 The problem was raised upstream at https://github.com/h5py/h5py/issues/1927 Makes it difficult to test if we can't reproduce it on all armhf environments. A patch was suggested for the upstream report but has already been applied (fix-unaligned-access.patch). I'm not sure that we can do much more than that, since we can't reproduce the bug on debian armhf systems.
Bug#1060937: marked as done (ionit: FTBFS: AttributeError: module 'astroid.nodes' has no attribute 'TryExcept')
Your message dated Fri, 19 Jan 2024 17:04:27 +0100 with message-id <7df9c5244c1140426702f0986cdc5a767d67cafc.ca...@debian.org> and subject line Re: Bug#1060937: ionit: FTBFS: AttributeError: module 'astroid.nodes' has no attribute 'TryExcept' has caused the Debian Bug report #1060937, regarding ionit: FTBFS: AttributeError: module 'astroid.nodes' has no attribute 'TryExcept' 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.) -- 1060937: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060937 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ionit Version: 0.5.0-1.1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240115 ftbfs-trixie 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_build > I: pybuild base:305: /usr/bin/python3 setup.py build > running build > running build_py > copying ionit_plugin.py -> /<>/.pybuild/cpython3_3.11/build > running build_scripts > creating build > creating build/scripts-3.11 > copying and adjusting ionit -> build/scripts-3.11 > changing mode of build/scripts-3.11/ionit from 644 to 755 > pandoc -s -t man ionit.1.md -o ionit.1 > make[1]: Leaving directory '/<>' >dh_auto_test -O--buildsystem=pybuild > I: pybuild base:305: cd /<>/.pybuild/cpython3_3.11/build; > python3.11 -m unittest discover -v -s /<> > test_black (tests.test_black.BlackTestCase.test_black) > Test: Run black code formatter on Python source code. ... Running following > command: > black --check --diff -l 99 /<>/ionit tests ionit_plugin.py > /<>/setup.py > ok > test_flake8 (tests.test_flake8.Flake8TestCase.test_flake8) > Test: Run flake8 on Python source code. ... Running following command: > /usr/bin/python3.11 -m flake8 --max-line-length=99 /<>/ionit > tests ionit_plugin.py /<>/setup.py > ok > test_collect_function > (tests.test_ionit.TestCollectContext.test_collect_function) > Test: Run collect_context(["tests/config/function"]) ... ok > test_collect_static_context > (tests.test_ionit.TestCollectContext.test_collect_static_context) > Test: Run collect_context(["tests/config/static"]) ... ok > test_configuration_file > (tests.test_ionit.TestCollectContext.test_configuration_file) > Test: Run collect_context(["tests/config/static/second.yaml"]) ... ok > test_context_stacking > (tests.test_ionit.TestCollectContext.test_context_stacking) > Test: Run collect_context(["tests/config/stacking"]) ... ok > test_empty_context (tests.test_ionit.TestCollectContext.test_empty_context) > Test: Run collect_context(["tests/config/empty-context"]) ... ok > test_empty_python_file > (tests.test_ionit.TestCollectContext.test_empty_python_file) > Test: Run collect_context(["tests/config/empty"]) ... ok > test_ignoring_additional_files > (tests.test_ionit.TestCollectContext.test_ignoring_additional_files) > Test: Run collect_context(["tests/config/additional-file"]) ... ok > test_invalid_json (tests.test_ionit.TestCollectContext.test_invalid_json) > Test: Run collect_context(["tests/config/invalid-json"]) ... ok > test_invalid_python (tests.test_ionit.TestCollectContext.test_invalid_python) > Test: Run collect_context(["tests/config/invalid-python"]) ... ok > test_invalid_yaml (tests.test_ionit.TestCollectContext.test_invalid_yaml) > Test: Run collect_context(["tests/config/invalid-yaml"]) ... ok > test_missing_directory > (tests.test_ionit.TestCollectContext.test_missing_directory) > Test: Non-existing context directory ... ok > test_non_dict_context > (tests.test_ionit.TestCollectContext.test_non_dict_context) > Test failure for collect_context(["tests/config/non-dict"]) ... ok > test_python_module (tests.test_ionit.TestCollectContext.test_python_module) > Test: Run collect_context(["tests/config/python"]) ... ok > test_raise_exception > (tests.test_ionit.TestCollectContext.test_raise_exception) > Test failure for collect_context(["tests/config/exception"]) ... ok > test_main_append_templates > (tests.test_ionit.TestMain.test_main_append_templates) > Test main() with static context and multiple template directories ... > 2024-01-15 20:28:28,536 ionit INFO: Reading configuration file > '/<>/tests/config/static/first.json'... > 2024-01-15 20:28:28,536 ionit INFO: Reading configuration file > '/<>/tests/config/static/second.yaml'... > 2024-01-15 20:28:28,539 ionit INFO: Rendered > '/<>/tests/template/static/counting.jinja' to > '/<>/tests/template/static/counting'. > 2024-01-15 20:28:28,540 ionit INFO: Rendered > '/<>/test
Bug#1061031: marked as done (bdebstrap: FTBFS: AttributeError: module 'astroid.nodes' has no attribute 'TryExcept')
Your message dated Fri, 19 Jan 2024 17:04:30 +0100 with message-id and subject line Re: Bug#1061031: bdebstrap: FTBFS: AttributeError: module 'astroid.nodes' has no attribute 'TryExcept' has caused the Debian Bug report #1061031, regarding bdebstrap: FTBFS: AttributeError: module 'astroid.nodes' has no attribute 'TryExcept' 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.) -- 1061031: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061031 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: bdebstrap Version: 0.6.0-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240115 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules binary > dh binary --buildsystem pybuild --with python3 >dh_update_autotools_config -O--buildsystem=pybuild >dh_autoreconf -O--buildsystem=pybuild >dh_auto_configure -O--buildsystem=pybuild > I: pybuild base:305: python3.11 setup.py config > running config >dh_auto_build -O--buildsystem=pybuild > I: pybuild base:305: /usr/bin/python3 setup.py build > running build > running doc > running command: pandoc -s -t man bdebstrap.1.md -o bdebstrap.1 > running build_scripts > creating build > creating build/scripts-3.11 > copying and adjusting bdebstrap -> build/scripts-3.11 > changing mode of build/scripts-3.11/bdebstrap from 644 to 755 >dh_auto_test -O--buildsystem=pybuild > I: pybuild base:305: cd /<>/.pybuild/cpython3_3.11/build; > python3.11 -m unittest discover -v -s /<> > test_get_path_exists (tests.TestGetPath.test_get_path_exists) > Test get_path(__file__). ... ok > test_get_path_missing (tests.TestGetPath.test_get_path_missing) > Test non-existing file for get_path(). ... ok > test_get_path_pybuild (tests.TestGetPath.test_get_path_pybuild) > Test changing current directory before calling get_path(). ... ok > test_black (tests.test_black.BlackTestCase.test_black) > Test: Run black code formatter on Python source code. ... Running following > command: > black --check --diff -l 99 /<>/bdebstrap tests > /<>/setup.py > ok > test_debug (tests.test_config.TestArguments.test_debug) > Test --debug argument parsing. ... ok > test_empty_args (tests.test_config.TestArguments.test_empty_args) > Test setting arguments to empty strings. ... ok > test_malformed_env (tests.test_config.TestArguments.test_malformed_env) > Test malformed --env parameter (missing equal sign). ... ok > test_mirrors_with_spaces > (tests.test_config.TestArguments.test_mirrors_with_spaces) > Test --mirrors with leading/trailing spaces. ... ok > test_no_args (tests.test_config.TestArguments.test_no_args) > Test calling bdebstrap without arguments. ... ok > test_optional_args (tests.test_config.TestArguments.test_optional_args) > Test optional arguments (which also have positional ones). ... ok > test_parse_env (tests.test_config.TestArguments.test_parse_env) > Test parsing --env parameters. ... ok > test_positional_args (tests.test_config.TestArguments.test_positional_args) > Test positional arguments (overwriting optional ones). ... ok > test_split (tests.test_config.TestArguments.test_split) > Test splitting comma and space separated values. ... ok > test_add_command_line_arguments > (tests.test_config.TestConfig.test_add_command_line_arguments) > Test Config.add_command_line_arguments(). ... ok > test_add_command_line_arguments_no_config > (tests.test_config.TestConfig.test_add_command_line_arguments_no_config) > Test Config.add_command_line_arguments() with no config file. ... ok > test_check_example (tests.test_config.TestConfig.test_check_example) > Test example unstable.yaml file. ... ok > test_commented_packages (tests.test_config.TestConfig.test_commented_packages) > Test commented-packages.yaml file. ... ok > test_config_and_arguments > (tests.test_config.TestConfig.test_config_and_arguments) > Test Config.add_command_line_arguments() with config file and arguments. ... > ok > test_env_items (tests.test_config.TestConfig.test_env_items) > Test environment variables for example unstable.yaml. ... ok > test_loading (tests.test_config.TestConfig.test_loading) > Test loading a YAML configuration file. ... ok > test_sanitize_packages_debs > (tests.test_config.TestConfig.test_sanitize_packages_debs) > Test sanitize_packages method: multiple local .debs ... ok > test_sanitize_packages_duplicate_debs > (tests.test_config.TestConfig.test_sanitize_packages_duplicate_debs) > Test sanitize_packages method: remove duplicate local .
Bug#1041519: Bug#1042027: transmission 4.0.5-1
Hi, > > please push this packaging effort to a personal (but publicly > > accessible) git repo on salsa, so that i can cherry pick the changes i > > like, thanks > > Here: > > > https://salsa.debian.org/niol/transmission/-/tree/master-candidate?ref_type=heads I've also updated my pull request to make it easier to review cherry-picking the appropriate change. https://salsa.debian.org/debian/transmission/-/merge_requests/16 Thanks, Alex
Bug#1042529: marked as done (sogo: Multiple embdeded and minified javascript library)
Your message dated Fri, 19 Jan 2024 15:21:04 + with message-id and subject line Bug#1042529: fixed in sogo 5.9.0-1 has caused the Debian Bug report #1042529, regarding sogo: Multiple embdeded and minified javascript library 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.) -- 1042529: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042529 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: sogo Severity: serious Tags: ftbfs security Justification: FTBFS + security X-Debbugs-Cc: Debian Security Team Dear Maintainer, https://sources.debian.org/src/sogo/5.8.4-1/UI/WebServerResources/js/vendor/ inlclude a few library precompiled and that seems outdated (bad from a security point of view due to recent CVE for ckeditor) Could you deembed and use packaged library Thanks Bastien signature.asc Description: This is a digitally signed message part. --- End Message --- --- Begin Message --- Source: sogo Source-Version: 5.9.0-1 Done: Jordi Mallach We believe that the bug you reported is fixed in the latest version of sogo, 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 1042...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jordi Mallach (supplier of updated sogo package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 28 Nov 2023 09:46:18 +0100 Source: sogo Architecture: source Version: 5.9.0-1 Distribution: experimental Urgency: medium Maintainer: Debian SOGo Maintainers Changed-By: Jordi Mallach Closes: 1042529 Changes: sogo (5.9.0-1) experimental; urgency=medium . * New upstream release. * Refresh Remove-build-date patch. * Fix replacement of vendored JS libraries with packaged versions (closes: #1042529). * Drop unneeded Build-Depends on js libs. Checksums-Sha1: b5e6a1202f0b7ff7e4245f454a3b0ddefa9a2341 2264 sogo_5.9.0-1.dsc 8c32caee8c69149eb903b7477cf4eab9212713f1 34806178 sogo_5.9.0.orig.tar.gz 1094946d36fb79755097c3e50f2e8f03c1a763ee 18520 sogo_5.9.0-1.debian.tar.xz ce39c825787d9e3ec8bdb8b51202179560503f19 11058 sogo_5.9.0-1_amd64.buildinfo Checksums-Sha256: 829730bffbecdff6c67af4a195fe3de7802833a4d2cd24a6677cffe272e78f27 2264 sogo_5.9.0-1.dsc 2e16a08fb266ccee9131249fba06da15177620998587af2e31f1b9cca99ba48d 34806178 sogo_5.9.0.orig.tar.gz ddf4d4b7f10dfda6e35af32f5dd869dbdb1826bd949e66f7a38ba744a7eb7ee2 18520 sogo_5.9.0-1.debian.tar.xz 98f3ca61c5767ea730863f1fbc5c6183ebe4441930998a10f09fb863f8c9f858 11058 sogo_5.9.0-1_amd64.buildinfo Files: bc541b65b0f8471bd8c8d55dd6acc592 2264 mail optional sogo_5.9.0-1.dsc 43dddfc2996b8f21b138b9b232239fdb 34806178 mail optional sogo_5.9.0.orig.tar.gz 97e96e4f72a02273715ef815dfba9f82 18520 mail optional sogo_5.9.0-1.debian.tar.xz db3f1716a25e34780664b36a3ebe3465 11058 mail optional sogo_5.9.0-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE6BdUhsApKYN8KGoWJVAvb8vjywQFAmWqjbUACgkQJVAvb8vj ywRHARAAtp1E+AYI/ejDYx2cPr00glCGVbtAuQrkaY6kr6tEurFTlrOkcKdF1G/J /FJ82Ii4OV8DJpXfbJSNcJImcCxGUmo76pPIsukvEv/rKi3Ihzy+JCSvS9nmClK+ cP5sCe4rTkSMQ0eUrSZDrn2N9Y0F7nOeyzusHkXZcqT4na4UnRSXUpkYkro4Y1XV 1g0XjzZKpmn4SB1DzVhPmQNmlbqxZb98Lne189OIjYp3M12CyNDl3bmhotJCoEUN 22XHZD7rX1U/g0jK2hFx8CT7V5FHlJ+92izgHPJsCdjkF0MXXN87hYS0TaTDSVOq 4EasHPNz95D+aNxeq99IuUuWGO3T+Su4PP7eMl+ZAgmiUfs+tvTOAtLoVKUmrnq2 4IzEJm+y0fNurg4u5GkokdIK17FdSsAr6I/MJMWLc4UvWIjMUT/144BO6I/pdDKb zhEe12J/HJLPbwKuhb9iXM4owycd/1orCaOHAK4ImsA51Oc9uutxnEwZqgb11edZ tkIYKieCzJPUxvlEOdw2Mv89hPPKBnno9QVhGN0nZVmJhZVVK4l4oBC0qUHFT7Yw 7ukj7pEFi9r1YtgF9PbGICq+vSigFrMM/1RVTooohbX34EsOsfxiiqRc1SQnqKFW oxsUuEU/bCsjHL92uD1UigJHG3okwOcU1BrxECidN0pkLCbKs80= =tEm+ -END PGP SIGNATURE End Message ---
Bug#983619: marked as done (vdr-markad: fails to install: chown: invalid user: 'vdr:vdr')
Your message dated Fri, 19 Jan 2024 13:49:54 + with message-id and subject line Bug#983619: fixed in vdr-plugin-markad 3.4.5-3 has caused the Debian Bug report #983619, regarding vdr-markad: fails to install: chown: invalid user: 'vdr:vdr' 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.) -- 983619: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983619 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: vdr-markad Version: 0.1.4+git20180120-3 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. >From the attached log (scroll to the bottom...): Setting up vdr-markad (0.1.4+git20180120-3) ... chown: invalid user: 'vdr:vdr' dpkg: error processing package vdr-markad (--configure): installed vdr-markad package post-installation script subprocess returned error exit status 1 Processing triggers for libc-bin (2.31-9) ... Errors were encountered while processing: vdr-markad cheers, Andreas vdr-markad_0.1.4+git20180120-3.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: vdr-plugin-markad Source-Version: 3.4.5-3 Done: Christoph Martin We believe that the bug you reported is fixed in the latest version of vdr-plugin-markad, 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 983...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Christoph Martin (supplier of updated vdr-plugin-markad package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 19 Jan 2024 13:53:46 +0100 Source: vdr-plugin-markad Architecture: source Version: 3.4.5-3 Distribution: unstable Urgency: medium Maintainer: Debian VDR Team Changed-By: Christoph Martin Closes: 983619 Changes: vdr-plugin-markad (3.4.5-3) unstable; urgency=medium . * chown vdr /var/lib/markad in plugin package (closes: #983619) Checksums-Sha1: 5725faddc0e115eb99b4e3e8c8853e58848cdcb4 2242 vdr-plugin-markad_3.4.5-3.dsc f56969a8ed905d12f9bfad9f214f3cfb6879757c 269115 vdr-plugin-markad_3.4.5.orig.tar.gz f6ba1223f8cda8a4bf970c33b83e0b39aec140b5 10756 vdr-plugin-markad_3.4.5-3.debian.tar.xz 1eb53d0d4d3cad3ba84adfa54bbfa4283f274ab2 12740 vdr-plugin-markad_3.4.5-3_amd64.buildinfo Checksums-Sha256: 8ae2ac173314874f0893dd50ed7594bb7c85fb74f0c27d312e9bae4f540f21a2 2242 vdr-plugin-markad_3.4.5-3.dsc 439d7eafa0b13f51cb9fdfad7b49dc00f01ef29877dd25d0e2e7670eed245963 269115 vdr-plugin-markad_3.4.5.orig.tar.gz 0a6ff4e02ab994c006f672b0f04da4f0976f509aaf174a02fd171e3b77559f8c 10756 vdr-plugin-markad_3.4.5-3.debian.tar.xz 1633e68e62eada3fec189b846f475226e84507ff42f3ba4ffb7bbc3be5bdd439 12740 vdr-plugin-markad_3.4.5-3_amd64.buildinfo Files: be00af3fd61c0b448a59d19a9ef5d3d1 2242 video optional vdr-plugin-markad_3.4.5-3.dsc e311e1dfd488a3f3916ab4bc00fa5eb2 269115 video optional vdr-plugin-markad_3.4.5.orig.tar.gz bc5805214e25af45202d7bf8d5bcdf0d 10756 video optional vdr-plugin-markad_3.4.5-3.debian.tar.xz cf25f00b3a9ae2f488a3534c78d27e6e 12740 video optional vdr-plugin-markad_3.4.5-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEdDnWZeAGEWiqWy6hesz1la2n0EoFAmWqekwACgkQesz1la2n 0EqgTw//WiZwmSCCdI7BpBswoTec6OQUmL1aYqJf422WKJTZXD7pWW5n0bmlJC96 0ZOtEU1tOH+WSX+xPm9m2YwXM6F8xLHQ2OcKMx9Wt0Ps7iUbQstXXf0bB59JCYMf /SC9CcGPQ+q2EaK8z66UKDkYL+bt8LhOTjB2e/wgz+AMI35IVDZ+MXZH2pQDmdmr zuey3lAPjKSOeZIUDHWU3ITf6GNaPdtqxyfmBdpq54hlhc56LSiZWNyKHLOGl3Jg Jq5vQ1xo5OzpUAm7CGL9GvzEkE3s1oX85tsRTkVYToa7lS1kHBQDoDbitiTrzcNa rCpQ3Cw8KeqReGxxNoI2f2YooOPi3gpZx29E454MMgNxTcrdCeaUqx4uHxUdYpnY W6w9lmgr8SunD3N0qg33GNaUBhZ1DAwLywbBJp75ymWOLiEZ3hKi2PkEl+BWv8W3 uPv3HZujC35dVn5kAvzCrZtDB8mDmdfZgSus/UQ3V1ExcoTQa/WZodF5lR9PD4Vy VReiHaXw1J0gHyUbHLMOYK4DmNwe4WQoTYSefA2z7T2OFqH1cXIDmwevick+ya2S BengOq0vsHHdgLeZEOLKGw3XiHIbrHFIiBE44tTDKy6gsZ1yGEd7pKvROpqya22j 9bqc2WXr+kZqpJkabg4bgyKQQYrwyQUltcJ+hTi4QUaz6hv4YuU= =laMY -END PGP SIGNATURE End Message ---
Processed: Bug#1014862 vdr-plugin-markad: FTBFS: Cannot find (any matches for) "command/markad"
Processing commands for cont...@bugs.debian.org: > notfound 1014862 3.4.5-1 Bug #1014862 [src:vdr-plugin-markad] vdr-plugin-markad: FTBFS: Cannot find (any matches for) "command/markad" Ignoring request to alter found versions of bug #1014862 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 1014862: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014862 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1014862: vdr-plugin-markad: FTBFS: Cannot find (any matches for) "command/markad"
notfound 1014862 3.4.5-1 thanks In the current build this bug does not exist. OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1052751: marked as done (binutils-mipsen: FTBFS: ld: mips.o:(.data.rel.ro+0x740): undefined reference to `gold::Output_data_reloc_base<9, true, 32, true>::do_adjust_output_section(gold::Output_sec
Your message dated Fri, 19 Jan 2024 19:36:23 +0800 with message-id and subject line Re: Bug#1050431: binutils-mipsen: FTBFS on all architectures has caused the Debian Bug report #1050431, regarding binutils-mipsen: FTBFS: ld: mips.o:(.data.rel.ro+0x740): undefined reference to `gold::Output_data_reloc_base<9, true, 32, true>::do_adjust_output_section(gold::Output_section*)' 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.) -- 1050431: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050431 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: binutils-mipsen Version: 10+c5 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230925 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /usr/bin/ld: mips.o:./builddir-mips/gold/../../gold/output.h:1276: more > undefined references to `gold::Output_reloc<9, true, 32, > true>::compare(gold::Output_reloc<9, true, 32, true> const&) const' follow > /usr/bin/ld: mips.o:(.data.rel.ro+0x740): undefined reference to > `gold::Output_data_reloc_base<9, true, 32, > true>::do_adjust_output_section(gold::Output_section*)' > /usr/bin/ld: mips.o:(.data.rel.ro+0xd40): undefined reference to > `gold::Output_data_reloc_base<9, true, 32, > false>::do_adjust_output_section(gold::Output_section*)' > /usr/bin/ld: > mips.o:(.data.rel.ro._ZTVN4gold22Output_data_reloc_baseILi9ELb1ELi32ELb1EEE[_ZTVN4gold22Output_data_reloc_baseILi9ELb1ELi32ELb1EEE]+0x20): > undefined reference to `gold::Output_data_reloc_base<9, true, 32, > true>::do_write(gold::Output_file*)' > /usr/bin/ld: > mips.o:(.data.rel.ro._ZTVN4gold22Output_data_reloc_baseILi9ELb1ELi32ELb1EEE[_ZTVN4gold22Output_data_reloc_baseILi9ELb1ELi32ELb1EEE]+0xb0): > undefined reference to `gold::Output_data_reloc_base<9, true, 32, > true>::do_adjust_output_section(gold::Output_section*)' > /usr/bin/ld: > mips.o:(.data.rel.ro._ZTVN4gold22Output_data_reloc_baseILi9ELb1ELi32ELb0EEE[_ZTVN4gold22Output_data_reloc_baseILi9ELb1ELi32ELb0EEE]+0x20): > undefined reference to `gold::Output_data_reloc_base<9, true, 32, > false>::do_write(gold::Output_file*)' > /usr/bin/ld: > mips.o:(.data.rel.ro._ZTVN4gold22Output_data_reloc_baseILi9ELb1ELi32ELb0EEE[_ZTVN4gold22Output_data_reloc_baseILi9ELb1ELi32ELb0EEE]+0xb0): > undefined reference to `gold::Output_data_reloc_base<9, true, 32, > false>::do_adjust_output_section(gold::Output_section*)' > collect2: error: ld returned 1 exit status The full build log is available from: http://qa-logs.debian.net/2023/09/25/binutils-mipsen_10+c5_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230925;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20230925&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=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 --- It's now buildable.--- End Message ---
Bug#1050431: marked as done (binutils-mipsen: FTBFS on all architectures)
Your message dated Fri, 19 Jan 2024 19:36:23 +0800 with message-id and subject line Re: Bug#1050431: binutils-mipsen: FTBFS on all architectures has caused the Debian Bug report #1050431, regarding binutils-mipsen: FTBFS on all architectures to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1050431: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050431 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: binutils-mipsen Version: 10+c4 Severity: serious Tags: ftbfs Justification: FTBFS Control: block 1040626 by -1 Dear maintainer, The latest upload of binutils-mipsen failed to build from source on all architectures. Apart from this being an issue by itself, it's also blocking progress in other RC bugs. https://buildd.debian.org/status/package.php?p=binutils-mipsen&ver=10 Paul -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (990, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 6.4.0-2-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled --- End Message --- --- Begin Message --- It's now buildable.--- End Message ---
Bug#1052345: src:binutils-mipsen: fails to migrate to testing for too long: FTBFS
It's now buildable.
Bug#1056529: marked as done (sphinx-autoapi's autopkg tests fail with Python 3.12)
Your message dated Fri, 19 Jan 2024 10:49:10 + with message-id and subject line Bug#1056529: fixed in sphinx-autoapi 3.0.0-0.1 has caused the Debian Bug report #1056529, regarding sphinx-autoapi's autopkg tests fail with Python 3.12 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.) -- 1056529: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056529 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:sphinx-autoapi Version: 2.0.0-2 Severity: important Tags: sid trixie User: debian-pyt...@lists.debian.org Usertags: python3.12 sphinx-autoapi's autopkg tests fail with Python 3.12: [...] 265s autopkgtest [19:18:48]: test upstream: [--- 265s 'tests/' -> '/tmp/autopkgtest.wYiNeq/autopkgtest_tmp/tests' 265s 'tests/dotnetexample' -> '/tmp/autopkgtest.wYiNeq/autopkgtest_tmp/tests/dotnetexample' 265s 'tests/dotnetexample/Makefile' -> '/tmp/autopkgtest.wYiNeq/autopkgtest_tmp/tests/dotnetexample/Makefile' 265s 'tests/dotnetexample/README.md' -> '/tmp/autopkgtest.wYiNeq/autopkgtest_tmp/tests/dotnetexample/README.md' 265s 'tests/dotnetexample/conf.py' -> '/tmp/autopkgtest.wYiNeq/autopkgtest_tmp/tests/dotnetexample/conf.py' 265s 'tests/dotnetexample/example' -> '/tmp/autopkgtest.wYiNeq/autopkgtest_tmp/tests/dotnetexample/example' 265s 'tests/dotnetexample/example/clone.sh' -> '/tmp/autopkgtest.wYiNeq/autopkgtest_tmp/tests/dotnetexample/example/clone.sh' 265s 'tests/dotnetexample/index.rst' -> '/tmp/autopkgtest.wYiNeq/autopkgtest_tmp/tests/dotnetexample/index.rst' 265s 'tests/fixtures' -> '/tmp/autopkgtest.wYiNeq/autopkgtest_tmp/tests/fixtures' 265s 'tests/fixtures/dotnet.json' -> '/tmp/autopkgtest.wYiNeq/autopkgtest_tmp/tests/fixtures/dotnet.json' 265s 'tests/fixtures/go.json' -> '/tmp/autopkgtest.wYiNeq/autopkgtest_tmp/tests/fixtures/go.json' 265s 'tests/fixtures/javascript.json' -> '/tmp/autopkgtest.wYiNeq/autopkgtest_tmp/tests/fixtures/javascript.json' 265s 'tests/goexample' -> '/tmp/autopkgtest.wYiNeq/autopkgtest_tmp/tests/goexample' 265s 'tests/goexample/conf.py' -> '/tmp/autopkgtest.wYiNeq/autopkgtest_tmp/tests/goexample/conf.py' 265s 'tests/goexample/example' -> '/tmp/autopkgtest.wYiNeq/autopkgtest_tmp/tests/goexample/example' 265s 'tests/goexample/example/godocjson.go' -> '/tmp/autopkgtest.wYiNeq/autopkgtest_tmp/tests/goexample/example/godocjson.go' 265s 'tests/goexample/index.rst' -> '/tmp/autopkgtest.wYiNeq/autopkgtest_tmp/tests/goexample/index.rst' 265s 'tests/jsexample' -> '/tmp/autopkgtest.wYiNeq/autopkgtest_tmp/tests/jsexample' 265s 'tests/jsexample/conf.py' -> '/tmp/autopkgtest.wYiNeq/autopkgtest_tmp/tests/jsexample/conf.py' 265s 'tests/jsexample/example' -> '/tmp/autopkgtest.wYiNeq/autopkgtest_tmp/tests/jsexample/example' 265s 'tests/jsexample/example/jsdoc-example.js' -> '/tmp/autopkgtest.wYiNeq/autopkgtest_tmp/tests/jsexample/example/jsdoc-example.js' 265s 'tests/jsexample/index.rst' -> '/tmp/autopkgtest.wYiNeq/autopkgtest_tmp/tests/jsexample/index.rst' 265s 'tests/python' -> '/tmp/autopkgtest.wYiNeq/autopkgtest_tmp/tests/python' 265s 'tests/python/py38positionalparams' -> '/tmp/autopkgtest.wYiNeq/autopkgtest_tmp/tests/python/py38positionalparams' 265s 'tests/python/py38positionalparams/conf.py' -> '/tmp/autopkgtest.wYiNeq/autopkgtest_tmp/tests/python/py38positionalparams/conf.py' 265s 'tests/python/py38positionalparams/example' -> '/tmp/autopkgtest.wYiNeq/autopkgtest_tmp/tests/python/py38positionalparams/example' 265s 'tests/python/py38positionalparams/example/example.py' -> '/tmp/autopkgtest.wYiNeq/autopkgtest_tmp/tests/python/py38positionalparams/example/example.py' 265s 'tests/python/py38positionalparams/index.rst' -> '/tmp/autopkgtest.wYiNeq/autopkgtest_tmp/tests/python/py38positionalparams/index.rst' 265s 'tests/python/py3example' -> '/tmp/autopkgtest.wYiNeq/autopkgtest_tmp/tests/python/py3example' 265s 'tests/python/py3example/conf.py' -> '/tmp/autopkgtest.wYiNeq/autopkgtest_tmp/tests/python/py3example/conf.py' 265s 'tests/python/py3example/example' -> '/tmp/autopkgtest.wYiNeq/autopkgtest_tmp/tests/python/py3example/example' 265s 'tests/python/py3example/example/example.py' -> '/tmp/autopkgtest.wYiNeq/autopkgtest_tmp/tests/python/py3example/example/example.py' 265s 'tests/python/py3example/example/example2.py' -> '/tmp/autopkgtest.wYiNeq/autopkgtest_tmp/tests/python/py3example/example/example2.py' 265s 'tests/python/py3example/index.rst' -> '/tmp/autopkgtest.wYiNeq/autopkgtest_tmp/tests/python/py3example/index.rst' 265s 'tests/python/py3implicitnamespace' -> '/tmp/autopkgtest.wYiNeq/autopkgtest_tmp/tests/pytho
Bug#1058408: marked as pending in sphinx-autoapi
Control: tag -1 pending Hello, Bug #1058408 in sphinx-autoapi 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/sphinx-autoapi/-/commit/8171c970d61aa4183b21033e13b40795ab604852 * Non-maintainer upload. * New upstream version. Closes: #1056529, #1058408. * Build-depend on python3-sphinx-design, furo. * Still use unidecode instead of anyascii (not yet packaged). * Add python-bs4 and python3-packaging as test dependencies. (this message was generated automatically) -- Greetings https://bugs.debian.org/1058408
Processed: Bug#1058408 marked as pending in sphinx-autoapi
Processing control commands:
> tag -1 pending
Bug #1058408 [src:sphinx-autoapi] sphinx-autoapi: FTBFS: dh_auto_test: error:
pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit
code 13
Added tag(s) pending.
--
1058408: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058408
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1056529: marked as pending in sphinx-autoapi
Control: tag -1 pending Hello, Bug #1056529 in sphinx-autoapi 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/sphinx-autoapi/-/commit/8171c970d61aa4183b21033e13b40795ab604852 * Non-maintainer upload. * New upstream version. Closes: #1056529, #1058408. * Build-depend on python3-sphinx-design, furo. * Still use unidecode instead of anyascii (not yet packaged). * Add python-bs4 and python3-packaging as test dependencies. (this message was generated automatically) -- Greetings https://bugs.debian.org/1056529
Processed: Bug#1056529 marked as pending in sphinx-autoapi
Processing control commands: > tag -1 pending Bug #1056529 [src:sphinx-autoapi] sphinx-autoapi's autopkg tests fail with Python 3.12 Added tag(s) pending. -- 1056529: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056529 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1055848: Reproducing
I've now been able to setup autopkgtest locally based on sbuild. I get failures in an autopkgtest (sbuild sid) chroot, but not when I do a clean pbuilder chroot via sid to do "pbuilder login". Investigating the differences between what should be identical chroots. Alastair -- Alastair McKinstry, GPG: 82383CE9165B347C787081A2CBE6BB4E5D9AD3A5 ph: +353 87 6847928 e: alast...@mckinstry.ie, im: @alastair:mckinstry.ie
Bug#1061000: marked as done (dqlite: FTBFS: dh_auto_test: error: make -j8 check "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2)
Your message dated Fri, 19 Jan 2024 09:04:05 + with message-id and subject line Bug#1061000: fixed in dqlite 1.16.0-4 has caused the Debian Bug report #1061000, regarding dqlite: FTBFS: dh_auto_test: error: make -j8 check "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 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.) -- 1061000: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061000 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: dqlite Version: 1.16.0-3 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240115 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[3]: Entering directory '/<>' > PASS: unit-test > FAIL: integration-test > >libdqlite 1.16.0: ./test-suite.log > > > # TOTAL: 2 > # PASS: 1 > # SKIP: 0 > # XFAIL: 0 > # FAIL: 1 > # XPASS: 0 > # ERROR: 0 > > .. contents:: :depth: 2 > > FAIL: integration-test > == > > Running test suite with seed 0x48146ffc... > client/exec > disk_mode=0 [ OK] [ > 0.00848620 / 0.00474892 CPU ] > disk_mode=1 [ OK] [ > 0.00903412 / 0.00310910 CPU ] > client/execWithOneParam > disk_mode=0 [ OK] [ > 0.01107855 / 0.00322604 CPU ] > disk_mode=1 [ OK] [ > 0.01084037 / 0.00271260 CPU ] > client/execSql > disk_mode=0 [ OK] [ > 0.00588297 / 0.00149010 CPU ] > disk_mode=1 [ OK] [ > 0.00743165 / 0.00155657 CPU ] > client/query > disk_mode=0 [ OK] [ > 0.04957668 / 0.02712912 CPU ] > disk_mode=1 [ OK] [ > 0.02748792 / 0.01775024 CPU ] > client/querySql > disk_mode=0 [ OK] [ > 0.03543575 / 0.02319791 CPU ] > disk_mode=1 [ OK] [ > 0.03526996 / 0.01552904 CPU ] > cluster/restart > num_records=0, disk_mode=0[ OK] [ > 0.09370341 / 0.02169809 CPU ] > num_records=0, disk_mode=1[ OK] [ > 0.12578984 / 0.02156978 CPU ] > num_records=1, disk_mode=0[ OK] [ > 0.08911703 / 0.02158624 CPU ] > num_records=1, disk_mode=1[ OK] [ > 0.10179450 / 0.02262160 CPU ] > num_records=256, disk_mode=0 [ OK] [ > 1.33302500 / 0.36639435 CPU ] > num_records=256, disk_mode=1 [ OK] [ > 1.09571285 / 0.30773684 CPU ] > num_records=993, disk_mode=0 [ OK] [ > 4.43455608 / 1.49089326 CPU ] > num_records=993, disk_mode=1 [ OK] [ > 4.07793608 / 1.49977670 CPU ] > num_records=2200, disk_mode=0 [ OK] [ > 9.31523289 / 2.74274570 CPU ] > num_records=2200, disk_mode=1 [ OK] [ > 8.22212519 / 2.03489432 CPU ] > cluster/dataOnNewNode > num_records=0, disk_mode=0[ OK] [ > 1.02777129 / 0.01749712 CPU ] > num_records=0, disk_mode=1[ OK] [ > 1.02522202 / 0.01251844 CPU ] > num_records=1, disk_mode=0[ OK] [ > 1.04220156 / 0.01379738 CPU ] > num_records=1, disk_mode=1[ OK] [ > 1.02847857 / 0.01512479 CPU ] > num_records=256, disk_mode=0 [ OK] [ > 1.93572853 / 0.23575930 CPU ] > num_records=256, disk_mode=1 [ OK] [ > 2.27937617 / 0.42763899 CPU ] > num_records=993, disk_mode=0 [ ERROR ] > Error: test/integration/test_cluster.c:165: assertion failed: rv_ == 0 (1 == > 0) > Error: child killed by signal 6 (Ab
