Processed: bug 963639 is forwarded to https://github.com/pygame/pygame/issues/2202
Processing commands for cont...@bugs.debian.org: > forwarded 963639 https://github.com/pygame/pygame/issues/2202 Bug #963639 [src:pygame] pygame: FTBFS with Sphinx 3.1: Invalid C declaration: Expected identifier in nested name. [error at 9] PyObject \*pgExc_BufferError Set Bug forwarded-to-address to 'https://github.com/pygame/pygame/issues/2202'. > thanks Stopping processing here. Please contact me if you need assistance. -- 963639: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963639 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#859926: speechd-up: fails to install
Hi Dennis, Samuel, On 02-09-2020 17:46, Dennis Filder wrote: > I looked into this a bit and came up with the attached patch (written > against 0.10.1-2), but for further improvement I'd need some feedback. > > The patch adds a new thread that is on the lookout for Pulseaudio > processes and reconfigures/restarts the output modules accordingly > once it finds one. This allows speech-dispatcher (with the correct > privileges) to transition between ALSA and Pulseaudio without the need > for a restart (albeit with the loss of the not-yet-spoken messages in > the module and a pause of about 1-2 seconds). In my experience it > works quite nicely. > > I don't doubt that making the output modules do the transition > themselves without restarting them would be better, but that would > require changes far more intrusive than the ones in this patch. > > N.B.: For this to fix the original bug during installation of > speechd-up, the default for AudioOutputMethod would have to be changed > to "pulse,alsa". @Dennis, thanks a lot for working on this. Did you send this upstream as well? If not, can you do it or do you prefer we do it? @Samuel, what do you think of the patch. It's way to involved for me to judge, but it claims to solve a long standing RC issue. Paul signature.asc Description: OpenPGP digital signature
Bug#971185: marked as done (pyqwt3d: FTBFS: sip: Unable to find file "QtCore/QtCoremod.sip")
Your message dated Sat, 17 Oct 2020 05:33:37 +
with message-id
and subject line Bug#971185: fixed in pyqwt3d 0.1.8-6
has caused the Debian Bug report #971185,
regarding pyqwt3d: FTBFS: sip: Unable to find file "QtCore/QtCoremod.sip"
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.)
--
971185: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971185
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pyqwt3d
Version: 0.1.8-5
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200926 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules build
> dh_testdir
> export QTDIR=/usr/share/qt5
> set -e ;\
> for py in 3.8 ; do \
> mkdir -p build/py$py-qt5; \
> cp -Rl `ls . |grep -v build|grep -v debian` build/py$py-qt5; \
> (cd build/py$py-qt5/configure;\
> python$py configure-qt5.py -5 -I /usr/include/qwtplot3d
> --extra-libs=qwtplot3d-qt5 -D GL2PS_HAVE_ZLIB); \
> done
> sip: Deprecation warning: ../sip/OpenGL_Qt5_Module.sip:31: %Module version
> number should be specified using the 'version' argument
> sip: Deprecation warning: ../sip/Qwt3D_Qt5_Module.sip:31: %Module version
> number should be specified using the 'version' argument
> sip: Unable to find file "QtCore/QtCoremod.sip"
> Command line options:
> {'debug': False,
> 'disable_numarray': False,
> 'disable_numeric': False,
> 'disable_numpy': False,
> 'excluded_features': [],
> 'extra_cflags': [],
> 'extra_cxxflags': [],
> 'extra_defines': ['GL2PS_HAVE_ZLIB'],
> 'extra_include_dirs': ['/usr/include/qwtplot3d'],
> 'extra_lflags': [],
> 'extra_lib_dirs': [],
> 'extra_libs': ['qwtplot3d-qt5'],
> 'jobs': '',
> 'module_install_path': '',
> 'modules': [],
> 'qt': 5,
> 'qwtplot3d_sources': '',
> 'sip_include_dirs': ['-I ../sip'],
> 'subdirs': [],
> 'timelines': [],
> 'trace': '',
> 'zlib_sources': ''}
>
> Found SIP-4.19.24.
>
> Found 'posix' operating system:
> 3.8.6 (default, Sep 25 2020, 09:36:53)
> [GCC 10.2.0]
>
> Found NumPy-1.19.2.
>
> Setup the OpenGL package build.
> -n PyQt5.sip -t Qt_5_14_0 -t WS_X11
> sip invokation:
> ('/usr/bin/sip -I /usr/share/sip/PyQt5 -n PyQt5.sip -t Qt_5_14_0 -t WS_X11 -b
> '
> 'tmp-OpenGL_Qt5/OpenGL_Qt5.sbf -c tmp-OpenGL_Qt5 '
> '../sip/OpenGL_Qt5_Module.sip')
> Copy tmp-OpenGL_Qt5/sipOpenGLcmodule.cpp -> OpenGL_Qt5/sipOpenGLcmodule.cpp.
> Copy tmp-OpenGL_Qt5/sipAPIOpenGL.h -> OpenGL_Qt5/sipAPIOpenGL.h.
> Copy tmp-OpenGL_Qt5/OpenGL_Qt5.sbf -> OpenGL_Qt5/OpenGL_Qt5.sbf.
> 3 file(s) lazily copied.
> Setup the Qwt3D package build.
> Extended options:
> {'debug': False,
> 'disable_numarray': False,
> 'disable_numeric': False,
> 'disable_numpy': False,
> 'excluded_features': ['-x HAS_QT3 -x HAS_QT4'],
> 'extra_cflags': [],
> 'extra_cxxflags': [],
> 'extra_defines': ['GL2PS_HAVE_ZLIB', 'HAS_NUMPY'],
> 'extra_include_dirs': ['/usr/include/qwtplot3d',
> '/usr/include/python3.8',
> '/usr/lib/python3/dist-packages/numpy/core/include',
> '/usr/include/x86_64-linux-gnu/qt5/Qt',
> '/usr/include/x86_64-linux-gnu/qt5/QtCore',
> '/usr/include/x86_64-linux-gnu/qt5/QtGui',
> '/usr/include/x86_64-linux-gnu/qt5/QtWidgets',
> '/usr/include/x86_64-linux-gnu/qt5/QtOpenGL',
> '/usr/include/x86_64-linux-gnu/qt5'],
> 'extra_lflags': [],
> 'extra_lib_dirs': [],
> 'extra_libs': ['qwtplot3d-qt5'],
> 'jobs': '',
> 'module_install_path': '/usr/lib/python3.8/dist-packages/PyQt5/Qwt3D',
> 'modules': [],
> 'opengl': 'OpenGL_Qt5',
> 'qt': 5,
> 'qwt3d': 'Qwt3D_Qt5',
> 'qwtplot3d_sources': '',
> 'sip_include_dirs': ['-I ../sip'],
> 'subdirs': ['Qwt3D_Qt5', 'OpenGL_Qt5'],
> 'timelines': [],
> 'trace': '',
> 'zlib_sources': ''}
>
> sip invokation:
> ('/usr/bin/sip -I /usr/share/sip/PyQt5 -n PyQt5.sip -t Qt_5_14_0 -t WS_X11 -b
> '
> 'tmp-Qwt3D_Qt5/qwt3d.sbf -c tmp-Qwt3D_Qt5 -I ../sip -x HAS_QT3 -x HAS_QT4 '
> '../sip/Qwt3D_Qt5_Module.sip')
>
> SIP failed to generate the C++ code.
> make: *** [debian/rules:25: configure-stamp] Error 1
The full build log is available from:
http://qa-logs.debian.net/2020/09/26/pyqwt3d_0.1.8-5_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
About the archive rebuild: The rebuild was done on EC2 VM i
Bug#971204: marked as done (onnx: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below)
Your message dated Sat, 17 Oct 2020 05:33:25 + with message-id and subject line Bug#971204: fixed in onnx 1.7.0+dfsg-2 has caused the Debian Bug report #971204, regarding onnx: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below 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.) -- 971204: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971204 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: onnx Version: 1.7.0+dfsg-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200926 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > dh_missing --fail-missing > make[1]: Leaving directory '/<>' >dh_dwz -O-Spybuild >dh_strip -O-Spybuild >dh_makeshlibs -O-Spybuild > dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see > diff output below > dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols > file: see diff output below > dpkg-gensymbols: warning: debian/libonnx1/DEBIAN/symbols doesn't match > completely debian/libonnx1.symbols.amd64 > --- debian/libonnx1.symbols.amd64 (libonnx1_1.7.0+dfsg-1_amd64) > +++ dpkg-gensymbolsmoGBDk 2020-09-27 11:07:10.622636058 + > @@ -101,8 +101,9 @@ > > _ZN4onnx10MakeStringIJA23_cA92_cEEENSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEDpRKT_@Base > 1.7.0+dfsg > > _ZN4onnx10MakeStringIJA23_cNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEA13_ciA34_ciEEES7_DpRKT_@Base > 1.6.0+dfsg > > _ZN4onnx10MakeStringIJA23_cS1_EEENSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEDpRKT_@Base > 1.7.0+dfsg > - > _ZN4onnx10MakeStringIJA31_cNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEA2_cEEES7_DpRKT_@Base > 1.6.0+dfsg > +#MISSING: 1.7.0+dfsg-1# > _ZN4onnx10MakeStringIJA31_cNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEA2_cEEES7_DpRKT_@Base > 1.6.0+dfsg > > _ZN4onnx10MakeStringIJA49_cNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEA2_cEEES7_DpRKT_@Base > 1.6.0+dfsg > + > _ZN4onnx10MakeStringIJA7_cNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEA18_ciA20_ciS1_iA3_cEEES7_DpRKT_@Base > 1.7.0+dfsg-1 > > _ZN4onnx10MakeStringIJA8_cA10_cA6_cA5_cA26_cEEENSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEDpRKT_@Base > 1.6.0+dfsg > > _ZN4onnx10MakeStringIJA8_cA6_cS2_A5_cA26_cEEENSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEDpRKT_@Base > 1.6.0+dfsg > > _ZN4onnx10MakeStringIJNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEA23_cS6_EEES6_DpRKT_@Base > 1.7.0+dfsg > @@ -432,6 +433,7 @@ > > _ZN4onnx11GetOpSchemaINS_36NegativeLogLikelihoodLoss_Onnx_ver12EEENS_8OpSchemaEv@Base > 1.7.0+dfsg > _ZN4onnx11SchemaErrorD0Ev@Base 1.6.0+dfsg > _ZN4onnx11SchemaErrorD1Ev@Base 1.6.0+dfsg > + _ZN4onnx11SchemaErrorD2Ev@Base 1.7.0+dfsg-1 > _ZN4onnx11encodeGraphEPNS_10GraphProtoERKSt10shared_ptrINS_5GraphEE@Base > 1.6.0+dfsg > > _ZN4onnx11make_uniqueINS_18version_conversion12Upsample_8_9EJEEENSt9enable_ifIXntsrSt8is_arrayIT_E5valueESt10unique_ptrIS5_St14default_deleteIS5_EEE4typeEDpOT0_@Base > 1.6.0+dfsg > > _ZN4onnx11make_uniqueINS_18version_conversion15TypeRestrictionEJRA4_KcNS_7OpSetIDES6_RSt6vectorINS_20TensorProto_DataTypeESaIS8_ENSt9enable_ifIXntsrSt8is_arrayIT_E5valueESt10unique_ptrISE_St14default_deleteISE_EEE4typeEDpOT0_@Base > 1.6.0+dfsg > @@ -446,6 +448,7 @@ > > _ZN4onnx11make_uniqueINS_18version_conversion30BroadcastBackwardCompatibilityEJRA4_KcNS_7OpSetIDES6_EEENSt9enable_ifIXntsrSt8is_arrayIT_E5valueESt10unique_ptrIS9_St14default_deleteIS9_EEE4typeEDpOT0_@Base > 1.6.0+dfsg > _ZN4onnx12ConvertErrorD0Ev@Base 1.6.0+dfsg > _ZN4onnx12ConvertErrorD1Ev@Base 1.6.0+dfsg > + _ZN4onnx12ConvertErrorD2Ev@Base 1.7.0+dfsg-1 > _ZN4onnx12addAttributeEPNS_9NodeProtoEPNS_4NodeENS_6SymbolE@Base 1.6.0+dfsg > _ZN4onnx12assert_errorD0Ev@Base 1.6.0+dfsg > _ZN4onnx12assert_errorD1Ev@Base 1.6.0+dfsg > @@ -461,28 +464,34 @@ > _ZN4onnx12optimization12NopEmptyPass7runPassERNS_5GraphE@Base 1.6.0+dfsg > _ZN4onnx12optimization12NopEmptyPassD0Ev@Base 1.6.0+dfsg > _ZN4onnx12optimization12NopEmptyPassD1Ev@Base 1.6.0+dfsg > + _ZN4onnx12optimization12NopEmptyPassD2Ev@Base 1.7.0+dfsg-1 > _ZN4onnx12optimization12SplitPredict7runPassERNS_5GraphE@Base 1.6.0+dfsg > _ZN4onnx12optimization12SplitPredictD0Ev@Base 1.6.0+dfsg > _ZN4onnx12optimization12SplitPredictD1Ev@Base 1.6.0+dfsg > + _ZN4onnx12optimization12SplitPredictD2Ev@Base 1.7.0+dfs
Bug#972014: marked as done (onnx ftbfs with python3.9 as supported python version)
Your message dated Sat, 17 Oct 2020 05:33:25 + with message-id and subject line Bug#972014: fixed in onnx 1.7.0+dfsg-2 has caused the Debian Bug report #972014, regarding onnx ftbfs with python3.9 as supported python version to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 972014: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972014 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:onnx Version: 1.7.0+dfsg-1 Severity: important Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: python3.9 [...] running install_egg_info Copying onnx.egg-info to /<>/onnx-1.7.0+dfsg/debian/python3-onnx/usr/lib/python3.8/dist-packages/onnx-1.7.0.egg-info Skipping SOURCES.txt running install_scripts Installing backend-test-tools script to /<>/onnx-1.7.0+dfsg/debian/python3-onnx/usr/bin Installing check-model script to /<>/onnx-1.7.0+dfsg/debian/python3-onnx/usr/bin Installing check-node script to /<>/onnx-1.7.0+dfsg/debian/python3-onnx/usr/bin # Remove duplicatd test data from include directory rm -f -rf debian/tmp/usr/include/onnx/backend/test/data # Use the test data installed in python package as the main copy mkdir -v -p debian/libonnx-testdata/usr/share/libonnx-testdata/ mkdir: created directory 'debian/libonnx-testdata' mkdir: created directory 'debian/libonnx-testdata/usr' mkdir: created directory 'debian/libonnx-testdata/usr/share' mkdir: created directory 'debian/libonnx-testdata/usr/share/libonnx-testdata/' mv debian/python3-onnx/usr/lib/python3*/dist-packages/onnx/backend/test/data \ debian/libonnx-testdata/usr/share/libonnx-testdata/ mv: cannot move 'debian/python3-onnx/usr/lib/python3.9/dist-packages/onnx/backend/test/data' to 'debian/libonnx-testdata/usr/share/libonnx-testdata/data': Directory not empty make[1]: *** [debian/rules:30: override_dh_auto_install] Error 1 make[1]: Leaving directory '/<>/onnx-1.7.0+dfsg' make: *** [debian/rules:7: binary] Error 2 --- End Message --- --- Begin Message --- Source: onnx Source-Version: 1.7.0+dfsg-2 Done: Mo Zhou We believe that the bug you reported is fixed in the latest version of onnx, 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 972...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mo Zhou (supplier of updated onnx package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 17 Oct 2020 13:22:23 +0800 Source: onnx Architecture: source Version: 1.7.0+dfsg-2 Distribution: unstable Urgency: medium Maintainer: Debian Deep Learning Team Changed-By: Mo Zhou Closes: 971204 972014 Changes: onnx (1.7.0+dfsg-2) unstable; urgency=medium . [ Christian Kastner ] * Demangle symbols file . [ Mo Zhou ] * d/rules: Fix FTBFS bug with multiple python3. (Closes: #972014) * Stop tracking the C++ symbols. (Closes: #971204) * Amend test data handling when there are multiple versions of python3. * Update maintainer mail address to debian-ai@l.d.o. Checksums-Sha1: 0fbeea06ce73a903f15c0d7edd9840a4add7a4a5 2432 onnx_1.7.0+dfsg-2.dsc 9841f1ffb2f32b6a7afac529a4109de7351d06e7 10972 onnx_1.7.0+dfsg-2.debian.tar.xz 2aa40c8299bab77cac9951906a17b661e1645e05 8019 onnx_1.7.0+dfsg-2_source.buildinfo Checksums-Sha256: 808ac0d66e4965d5dd16cc14162aef45d007730d8dd91182d0df979dc440c7df 2432 onnx_1.7.0+dfsg-2.dsc c59f6169ca175b740a69c252edea533c02a71d81e41810fdc5238dab392325a1 10972 onnx_1.7.0+dfsg-2.debian.tar.xz 3d0f1364b1f7d3732eccd000bec7859d46bb9df709b002221271d57331fc263a 8019 onnx_1.7.0+dfsg-2_source.buildinfo Files: eb5822ab8f30002b711ee0f303ab8d60 2432 science optional onnx_1.7.0+dfsg-2.dsc ec633afb34ca7ccd97962325f4ca36f8 10972 science optional onnx_1.7.0+dfsg-2.debian.tar.xz 8b3a5b2f99958df55ea1b68c124db378 8019 science optional onnx_1.7.0+dfsg-2_source.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEEY4vHXsHlxYkGfjXeYmRes19oaooFAl+Kf8wRHGx1bWluQGRl Ymlhbi5vcmcACgkQYmRes19oaoq7Yg//Vo2JkmFFjVLYFPEF8PiQ0qXpZxGY7pVn k4AlJLjxrTMVpmOd8v3h/3tE4i30sbbBdnO+PAtZC5drY1Eitl+tgwnQ65q9/t2t ZSTvjwxK6G/QpXm2shctWu1BN+/I0Qe5IpUXF5GcjPXiMgfPFuf0JPXCwQvCy1mV dyt4AbFgeWSvtkm8Otd2A5pTu/0m7ubufDYAf4VWAW063++AvS4rc7Awfo
Processed: forcibly merging 972340 972347
Processing commands for cont...@bugs.debian.org: > forcemerge 972340 972347 Bug #972340 [src:pyferret] pyferret FTBFS with more than one supported python3 version Bug #972340 [src:pyferret] pyferret FTBFS with more than one supported python3 version The source pyferret and version 5.3+dfsg1-3 do not appear to match any binary packages Marked as found in versions pyferret/5.3+dfsg1-3. Added tag(s) bullseye and sid. Bug #972347 [src:pyferret] pyferret ftbfs with python3.9 as supported python3 version The source pyferret and version 5.3+dfsg1-3 do not appear to match any binary packages Marked as found in versions pyferret/7.6.3-1. Merged 972340 972347 > thanks Stopping processing here. Please contact me if you need assistance. -- 972340: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972340 972347: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972347 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#971185: marked as pending in pyqwt3d
Control: tag -1 pending Hello, Bug #971185 in pyqwt3d 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/pyqwt3d/-/commit/878ac6498f5269dda9e5d943e8a06fce4abd4fe2 Add --sip-include-dirs parameter to configure. Has changed in pyqt5-dev since 5.15.0+dfsg-2. (Closes: #971185) (this message was generated automatically) -- Greetings https://bugs.debian.org/971185
Processed: Bug#971185 marked as pending in pyqwt3d
Processing control commands: > tag -1 pending Bug #971185 [src:pyqwt3d] pyqwt3d: FTBFS: sip: Unable to find file "QtCore/QtCoremod.sip" Added tag(s) pending. -- 971185: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971185 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#972029: marked as done (python-udatetime ftbfs with python3.9 as supported python3 version)
Your message dated Sat, 17 Oct 2020 04:48:52 +
with message-id
and subject line Bug#972029: fixed in python-udatetime 0.0.16-4
has caused the Debian Bug report #972029,
regarding python-udatetime ftbfs with python3.9 as supported python3 version
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
972029: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972029
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-udatetime
Version: 0.0.16-3
Severity: important
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.9
[...]
x86_64-linux-gnu-gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g
-fwrapv -O2 -Wall -g -fstack-protector-strong -Wformat -Werror=format-security
-g -fwrapv -O2 -g -O2 -fdebug-prefix-map=/<>=.
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
-D_FORTIFY_SOURCE=2 -fPIC -D_PYTHON3=1 -I/usr/include/python3.9 -c
./src/rfc3339.c -o build/temp.linux-x86_64-3.9/./src/rfc3339.o -Ofast -std=c99
./src/rfc3339.c: In function ‘_gettime’:
./src/rfc3339.c:100:18: error: storage size of ‘t’ isn’t known
100 | struct timeb t;
| ^
./src/rfc3339.c:101:5: warning: implicit declaration of function ‘ftime’; did
you mean ‘ctime’? [-Wimplicit-function-declaration]
101 | ftime(&t);
| ^
| ctime
./src/rfc3339.c:100:18: warning: unused variable ‘t’ [-Wunused-variable]
100 | struct timeb t;
| ^
./src/rfc3339.c: At top level:
./src/rfc3339.c:516:21: warning: ‘CAPI’ initialized and declared ‘extern’
516 | extern RFC3999_CAPI CAPI = {
| ^~~~
error: command '/usr/bin/x86_64-linux-gnu-gcc' failed with exit code 1
E: pybuild pybuild:352: build: plugin distutils failed with: exit code=1:
/usr/bin/python3.9 setup.py build
--- End Message ---
--- Begin Message ---
Source: python-udatetime
Source-Version: 0.0.16-4
Done: Stefano Rivera
We believe that the bug you reported is fixed in the latest version of
python-udatetime, 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 972...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Stefano Rivera (supplier of updated python-udatetime
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, 16 Oct 2020 21:31:51 -0700
Source: python-udatetime
Architecture: source
Version: 0.0.16-4
Distribution: unstable
Urgency: medium
Maintainer: Ilias Tsitsimpis
Changed-By: Stefano Rivera
Closes: 972029
Changes:
python-udatetime (0.0.16-4) unstable; urgency=medium
.
[ Stefano Rivera ]
* Team upload.
* Patch: Explicitly include for ftime(). Fixes FTBFS with
Python 3.9. (Closes: #972029)
.
[ Ondřej Nový ]
* d/control: Update Vcs-* fields with new Debian Python Team Salsa
layout.
Checksums-Sha1:
95d96a068f80a915c425e12368f89d641c162b14 1529 python-udatetime_0.0.16-4.dsc
423cf66015d6b816059d46b87e8c6724ab8ee27d 3468
python-udatetime_0.0.16-4.debian.tar.xz
d647f4f9b2e6af879949c140176db7b632631cef 5746
python-udatetime_0.0.16-4_source.buildinfo
Checksums-Sha256:
2e8f00275c3c67e720be44f6b966bf2347878b67b80380221b9f34083b413cf9 1529
python-udatetime_0.0.16-4.dsc
eb18f45758e9c434330982190c46514c97eb5e1667dd59e9b9e412bcf20705e1 3468
python-udatetime_0.0.16-4.debian.tar.xz
667224588da7b497306855c99475c16675f31156f63e538d13cc8906a6d407c8 5746
python-udatetime_0.0.16-4_source.buildinfo
Files:
d8bed45a9860ed3369d65962d415543d 1529 python optional
python-udatetime_0.0.16-4.dsc
9b201142dc2fd34768be7b0ff693268c 3468 python optional
python-udatetime_0.0.16-4.debian.tar.xz
9ed40e7ee0d75cf5397e1b90aa82a851 5746 python optional
python-udatetime_0.0.16-4_source.buildinfo
-BEGIN PGP SIGNATURE-
iHUEARYKAB0WIQTumtb5BSD6EfafSCRHew2wJjpU2AUCX4pz4wAKCRBHew2wJjpU
2FqMAQDQKoPY8MIl9+ZT/P2HxUSYfBnvL54cJrh7uX2JrAwfGwD+KZXk2YXKSkdw
Fr8ilXJfXDohJYuBe7Ywddu4UaWBngk=
=GxMU
-END PGP SIGNATURE End Message ---
Bug#972029: marked as pending in python-udatetime
Control: tag -1 pending Hello, Bug #972029 in python-udatetime 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-udatetime/-/commit/017f27f32726e2a2c865f280fbbe756f14a62bbe Patch: Explicitly include for ftime(). Fixes FTBFS with Python 3.9. (Closes: #972029) (this message was generated automatically) -- Greetings https://bugs.debian.org/972029
Bug#971226: marked as done (pyqt-qwt: FTBFS: sip: Unable to find file "QtCore/QtCoremod.sip")
Your message dated Sat, 17 Oct 2020 04:33:28 + with message-id and subject line Bug#971226: fixed in pyqt-qwt 1.02.00-3 has caused the Debian Bug report #971226, regarding pyqt-qwt: FTBFS: sip: Unable to find file "QtCore/QtCoremod.sip" 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.) -- 971226: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971226 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pyqt-qwt Version: 1.02.00-2 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200926 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > cp -a /usr/include/qwt header > cp header/qwt_*.h header/qwt/ > set -e ;\ > for py in 3.8 ; do \ > mkdir pybuild$py; \ > cd pybuild$py && ln -s ../sip .; \ > QT_SELECT=qt5 python$py ../configure.py \ > --qwt-incdir=../header/qwt \ > --qwt-libdir=/usr/lib \ > --qwt-lib=qwt-qt5 --verbose \ > --no-dist-info; \ > cd ..; \ > done > Error: Unable to create the C++ code. > /<>/header/qwt > Configuring Qwt 6.1.2... > Qwt 6.1.4 is being used. > The Qwt .sip files will be installed in /usr/share/sip/PyQt5. > Qwt will be installed in /usr/lib/python3/dist-packages/PyQt5. > PyQt 5.15.1 is being used. > Qt 5.14.2 is being used. > sip 4.19.24 is being used. > The sip executable is /usr/bin/sip. > Qwt is being built with 'protected' redefined as 'public'. > The PEP 484 stubs will be installed in /usr/lib/python3/dist-packages/PyQt5. > Generating the C++ source for the Qwt module... > /usr/bin/sip -n sip -n PyQt5.sip -t Qt_5_14_0 -t WS_X11 -B Qt_6_0_0 -I > /usr/share/sip/PyQt5 -y Qwt.pyi -P -o -c /<>/pybuild3.8/Qwt -I > sip sip/qwt.sip > sip: Deprecation warning: the -B flag is deprecated > sip: Unable to find file "QtCore/QtCoremod.sip" > make[1]: *** [debian/rules:14: override_dh_auto_configure] Error 1 The full build log is available from: http://qa-logs.debian.net/2020/09/26/pyqt-qwt_1.02.00-2_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- Source: pyqt-qwt Source-Version: 1.02.00-3 Done: Stefano Rivera We believe that the bug you reported is fixed in the latest version of pyqt-qwt, 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 971...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Stefano Rivera (supplier of updated pyqt-qwt 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, 16 Oct 2020 21:16:21 -0700 Source: pyqt-qwt Architecture: source Version: 1.02.00-3 Distribution: unstable Urgency: medium Maintainer: Gudjon I. Gudjonsson Changed-By: Stefano Rivera Closes: 971226 Changes: pyqt-qwt (1.02.00-3) unstable; urgency=medium . [ Stefano Rivera ] * Team upload. * Add pyqt-sipdir parameter to configure. Has changed in pyqt5-dev since 5.15.0+dfsg-2. (Closes: #971226) * Add version dependency to pyqt5-dev. Needed for the pyqt-sipdir parameter. * Explicitly disable installation of sip files. Previously they weren't installed because they weren't within the Python module. . [ Ondřej Nový ] * d/control: Update Vcs-* fields with new Debian Python Team Salsa layout. Checksums-Sha1: 25b3d111dcaca7df38049c6184ec143fc1920efd 1556 pyqt-qwt_1.02.00-3.dsc 2349bc6755fc174db2b6c8d934691d511f6fdddb 4392 pyqt-qwt_1.02.00-3.debian.tar.xz f2b369ee3b28d5556e94991cdf0e0cb0dfad 9109 pyqt-qwt_1.02.00-3_source.buildinfo Checksums-Sha256: 975bd706d1d8d37f8f2276aa6526e488679f625781292fd61cdad9400e3c8b3d 1556 pyqt-qwt_1.02.00-3.dsc 955a258f389ef3989a0bfdd023a07792b652c0fc002a6125d0c48c808775e4c8 4392 pyqt-qwt_1.02.00-3.debian.tar.xz d99cfbba2
Processed: tagging 972026
Processing commands for cont...@bugs.debian.org: > tags 972026 + pending Bug #972026 [src:python-pyo] python-pyo ftbfs with python3.9 as supported python version Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 972026: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972026 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#972029 marked as pending in python-udatetime
Processing control commands: > tag -1 pending Bug #972029 [src:python-udatetime] python-udatetime ftbfs with python3.9 as supported python3 version Added tag(s) pending. -- 972029: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972029 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#966638: gkrellm-cpufreq: Error: /usr/lib/gkrellm2/plugins/cpufreq.so: undefined symbol: cpufreq_cpu_exists
Dear Maintainer, it seems like previous versions just optimized the call to cpufreq_cpu_exists away? The current build relies to have the symbol external defined. Attached patch tries to query the number of CPUs from another function and (kind of ugly) avoids a later crash if frequencies could not be queried. Therefore and because the last upstream version is from 2006 one might ask if this package is really still useful? (At least on amd64?) Kind regards, Bernhard Description: Get number of CPUs Author: Bernhard Übelacker Bug-Debian: https://bugs.debian.org/966638 Forwarded: no Last-Update: 2020-10-16 Index: gkrellm2-cpufreq-0.6.4/cpufreq.c === --- gkrellm2-cpufreq-0.6.4.orig/cpufreq.c +++ gkrellm2-cpufreq-0.6.4/cpufreq.c @@ -49,6 +49,7 @@ #include #include +#include /* version number */ #define VERSION"0.6.4" @@ -616,8 +617,7 @@ GkrellmMonitor* gkrellm_init_plugin(void monitor = &plugin_mon; /* determine number of cpus */ - for( ncpu = 0; cpufreq_cpu_exists(ncpu)==0; ++ncpu ) -; + ncpu = get_nprocs(); ncpu = ncpu > NCPU_MAX ? NCPU_MAX : ncpu; /* determine maximal frequency */ @@ -625,7 +625,10 @@ GkrellmMonitor* gkrellm_init_plugin(void for ( cpu = 0; cpu
Bug#937184: Python 3 port of offlineimap underway
Sudip Mukherjee writes: > > upstream is asking to treat offlineimap and offlineimap3 as separate > package. https://github.com/OfflineIMAP/offlineimap3/issues/10 I think we should preserve offlineimap until offlineimap3 is released, and then we can probably rename offlineimap3 once offlineimap is considered unsupported by the maintainers. Thoughts? -- Brett M. Gilio bre...@gnu.org https://brettgilio.com/ E82A C026 95D6 FF02 43CA 1E5C F6C5 2DD1 BA27 CB87
Processed: fixed 972332 in 2.0.0-1
Processing commands for cont...@bugs.debian.org:
> fixed 972332 2.0.0-1
Bug #972332 {Done: Stefano Rivera } [src:python-falcon]
python-falcon: fails its tests with python3.9
Marked as fixed in versions python-falcon/2.0.0-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
972332: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972332
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#972033: Bug#969650: Bug#972033: python3.9, dask, pandas 1.1
Control: tags -1 - pending
The package currently in Salsa doesn't work. test_statsmodels is
probably a circular dependency that should be ignored for now;
TestHDFStore is under investigation.
=== FAILURES
===
TestHDFStore.test_append_frame_column_oriented
self = 0x7f753e5ba2e0>
setup_path = 'tmp.__PxTZkyR5w5__.h5'
@pytest.mark.xfail(condition=is_crashing_arch,reason="https://bugs.debian.org/790925",strict=False,run=False)
def test_append_frame_column_oriented(self, setup_path):
with ensure_clean_store(setup_path) as store:
# column oriented
df = tm.makeTimeDataFrame()
df.index = df.index._with_freq(None) # freq doesnt round-trip
_maybe_remove(store, "df1")
store.append("df1", df.iloc[:, :2], axes=["columns"])
store.append("df1", df.iloc[:, 2:])
tm.assert_frame_equal(store["df1"], df)
result = store.select("df1", "columns=A")
expected = df.reindex(columns=["A"])
tm.assert_frame_equal(expected, result)
# selection on the non-indexable
result = store.select("df1", ("columns=A",
"index=df.index[0:4]"))
expected = df.reindex(columns=["A"], index=df.index[0:4])
tm.assert_frame_equal(expected, result)
# this isn't supported
with pytest.raises(TypeError):
> store.select("df1", "columns=A and index>df.index[4]")
pandas/tests/io/pytables/test_store.py:1336:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _
pandas/io/pytables.py:876: in select
return it.get_result()
pandas/io/pytables.py:1930: in get_result
results = self.func(self.start, self.stop, where)
pandas/io/pytables.py:860: in func
return s.read(start=_start, stop=_stop, where=_where, columns=columns)
pandas/io/pytables.py:4483: in read
result = self._read_axes(where=where, start=start, stop=stop)
pandas/io/pytables.py:3682: in _read_axes
selection = Selection(self, where=where, start=start, stop=stop)
pandas/io/pytables.py:5167: in __init__
self.terms = self.generate(where)
pandas/io/pytables.py:5180: in generate
return PyTablesExpr(where, queryables=q, encoding=self.table.encoding)
pandas/core/computation/pytables.py:573: in __init__
self.terms = self.parse()
pandas/core/computation/expr.py:806: in parse
return self._visitor.visit(self.expr)
pandas/core/computation/expr.py:398: in visit
return visitor(node, **kwargs)
pandas/core/computation/expr.py:404: in visit_Module
return self.visit(expr, **kwargs)
pandas/core/computation/expr.py:398: in visit
return visitor(node, **kwargs)
pandas/core/computation/expr.py:407: in visit_Expr
return self.visit(node.value, **kwargs)
pandas/core/computation/expr.py:398: in visit
return visitor(node, **kwargs)
pandas/core/computation/expr.py:726: in visit_BoolOp
return reduce(visitor, operands)
pandas/core/computation/expr.py:720: in visitor
rhs = self._try_visit_binop(y)
pandas/core/computation/expr.py:715: in _try_visit_binop
return self.visit(bop)
pandas/core/computation/expr.py:398: in visit
return visitor(node, **kwargs)
pandas/core/computation/expr.py:699: in visit_Compare
return self.visit(binop)
pandas/core/computation/expr.py:398: in visit
return visitor(node, **kwargs)
pandas/core/computation/expr.py:520: in visit_BinOp
op, op_class, left, right = self._maybe_transform_eq_ne(node)
pandas/core/computation/expr.py:441: in _maybe_transform_eq_ne
right = self.visit(node.right, side="right")
pandas/core/computation/expr.py:398: in visit
return visitor(node, **kwargs)
pandas/core/computation/pytables.py:430: in visit_Subscript
return self.const_type(value[slobj], self.env)
pandas/core/indexes/extension.py:215: in __getitem__
result = self._data[key]
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _
self =
['2000-01-03 00:00:00', '2000-01-04 00:00:00', '2000-01-05 00:00:00',
'2000-01-06 00:00:00', '2000-01...2-08 00:00:00',
'2000-02-09 00:00:00', '2000-02-10 00:00:00', '2000-02-11 00:00:00']
Length: 30, dtype: datetime64[ns]
key = 4
def __getitem__(self, key):
"""
This getitem defers to the underlying array, which
by-definition can
only handle list-likes, slices, and integer scalars
"""
if lib.is_integer(key):
# fast-path
result = self._data[key]
if self.ndim == 1:
return self._box_func(result)
return self._simple_new(result, dtype=self.dtype)
if com.is_bool_indexer(key):
# first convert to boolean, because check_array_indexer doesn't
# allow object dtype
if is_object_dtype(key):
key = np.asarray(key, dtype=bool)
key = check_array_indexer(se
Bug#972246: numba ftbfs in unstable with python3.9 as supported python3 version
Looks like it's going to take a while to get Python 3.9 support in the numba stack: https://github.com/numba/numba/issues/6345#issuecomment-706722002 This isn't just a little python library, it's a Python JIT for Python, so I'd believe that supporting 3.9 is non-trivial. SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272
Bug#972363: etesync-dav: unsatisfiable build dependencies: python3-radicale (<< 2.1.12)
Source: etesync-dav Version: 0.17.0-1 Severity: serious Tags: ftbfs Justification: fails to build from source Hi, etesync-dav/experimental cannot be built any more since it build-depends on python3-radicale (<< 2.1.12) while sid already has 2.1.12-1. Andreas
Processed: Re: forcibly merging 966969 971916
Processing commands for cont...@bugs.debian.org: > unmerge 971916 Bug #971916 [src:basemap] basemap ftbfs with python3-defaults (python3.9) Bug #966969 [src:basemap] basemap: FTBFS: dh_install: error: missing files, aborting Disconnected #971916 from all other report(s). > thanks Stopping processing here. Please contact me if you need assistance. -- 966969: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966969 971916: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971916 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#971916 marked as pending in basemap
Processing control commands: > tag -1 pending Bug #971916 [src:basemap] basemap ftbfs with python3-defaults (python3.9) Bug #966969 [src:basemap] basemap: FTBFS: dh_install: error: missing files, aborting Ignoring request to alter tags of bug #971916 to the same tags previously set Ignoring request to alter tags of bug #966969 to the same tags previously set -- 966969: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966969 971916: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971916 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#966969 marked as pending in basemap
Processing control commands: > tag -1 pending Bug #966969 [src:basemap] basemap: FTBFS: dh_install: error: missing files, aborting Bug #971916 [src:basemap] basemap ftbfs with python3-defaults (python3.9) Added tag(s) pending. Added tag(s) pending. -- 966969: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966969 971916: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971916 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#971916: marked as pending in basemap
Control: tag -1 pending Hello, Bug #971916 in basemap 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/basemap/-/commit/4e820b288d7ecadac0932301e1f70c89e07f4d25 Cython before building, not after building before installing. (Closes: #971916) (this message was generated automatically) -- Greetings https://bugs.debian.org/971916
Bug#966969: marked as pending in basemap
Control: tag -1 pending Hello, Bug #966969 in basemap 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/basemap/-/commit/afa755f06d6fa89b38c8f783ddb209c4180c7405 Patch: Replace deprecated mathplotlib dedent with cleandoc. (Closes: #966969) (this message was generated automatically) -- Greetings https://bugs.debian.org/966969
Bug#937184: Python 3 port of offlineimap underway
On Thu, Sep 17, 2020 at 10:01:40PM +0200, Gaudenz Steinlin wrote: > > There is now a Python 3 port of offlineimap underway: > https://github.com/OfflineIMAP/offlineimap/issues/670 > > AFAICS it looks promising. Please wait with removing from unstable. upstream is asking to treat offlineimap and offlineimap3 as separate package. https://github.com/OfflineIMAP/offlineimap3/issues/10 -- Regards Sudip
Bug#972137: SSL certificate problem (Was: Bug#972137: r-bioc-tcgabiolinks: autopkgtest regression)
Hi Andreas, The software access an external database to retrieve the genome information. The database has experienced problems in the last days and it has not been fixed yet. I am trying to save the genome information inside the package so it does not depends on the database anymore. I'll let you know when I fix it. Best regards, Tiago Chedraoui Silva On Tue, Oct 13, 2020 at 6:04 AM Andreas Tille wrote: > Control: tags -1 upstream > Control: tags -1 help > Control: forwarded -1 Antonio Colaprico , Tiago > Chedraoui Silva > > > Hi Antonio and Tiago, > > the Debian packaged version of TCGAbiolinks received a bug report about > a failure in its test suite. I have the impression that the SSL > certificate of a site where data are downloaded from is not correct. > Could you please verify the test suite and let me know whether you > might also get > > ── 1. Error: Preparing HT_HG-U133A as SE works > (@test-prepare-download.R#193) ─ > > failed to get URL after 3 tries: > > >error: SSL certificate problem: unable to get local issuer certificate > > > > Kind regards > >Andreas. > > On Tue, Oct 13, 2020 at 08:36:21AM +0200, Graham Inggs wrote: > > Source: r-bioc-tcgabiolinks > > Version: 2.16.4+dfsg-1 > > Severity: serious > > Tags: sid bullseye > > X-Debbugs-CC: debian...@lists.debian.org > > User: debian...@lists.debian.org > > Usertags: regression > > > > Hi Maintainer > > > > Since 2020-10-08, the autopkgtest of r-bioc-tcgabiolinks has been > failing [1]. > > > > I've copied what I hope is the relevant part of the log below. > > > > Does this autopkgtest download data? If so, please add the > > 'needs-internet' [2] restriction to debian/tests/control, or even skip > > that particular test. > > > > Regards > > Graham > > > > > > [1] https://ci.debian.net/packages/r/r-bioc-tcgabiolinks/testing/amd64/ > > [2] > https://salsa.debian.org/ci-team/autopkgtest/raw/master/doc/README.package-tests.rst > > > > > > ── 1. Error: Preparing HT_HG-U133A as SE works > (@test-prepare-download.R#193) ─ > > failed to get URL after 3 tries: > > error: SSL certificate problem: unable to get local issuer certificate > > Backtrace: > > 1. TCGAbiolinks::GDCprepare(query, summarizedExperiment = TRUE) > > 2. TCGAbiolinks:::readGeneExpressionQuantification(...) > > 3. TCGAbiolinks:::makeSEfromGeneExpressionQuantification(...) > > 4. TCGAbiolinks::get.GRCh.bioMart(genome) > > > > ___ > > R-pkg-team mailing list > > r-pkg-t...@alioth-lists.debian.net > > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/r-pkg-team > > -- > http://fam-tille.de >
Bug#971105: closing 971105
close 971105 thanks sequoia dependencies are all sorted in unstable now that rust-dyn-clone propagated out of NEW. See #971099 and #971717.
Processed: closing 971105
Processing commands for cont...@bugs.debian.org: > close 971105 Bug #971105 [src:rust-sequoia-sop] rust-sequoia-sop: FTBFS: build-dependency not installable: librust-sequoia-openpgp-0.18+default-dev Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 971105: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971105 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#969650: Bug#972033: python3.9, dask, pandas 1.1
Processing control commands: > tags -1 - pending Bug #972033 [src:pandas] pandas ftbfs with python3.9 as supported python version Bug #972015 [src:pandas] pandas ftbfs with python3 as supported python version Removed tag(s) pending. Removed tag(s) pending. -- 972015: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972015 972033: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972033 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#972332: marked as done (python-falcon: fails its tests with python3.9)
Your message dated Fri, 16 Oct 2020 18:49:21 +
with message-id
and subject line Bug#972332: fixed in python-falcon 1.4.1-2.1
has caused the Debian Bug report #972332,
regarding python-falcon: fails its tests with python3.9
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.)
--
972332: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972332
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:falcon
Version: 1.4.1-2
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.9
falcon fails it's tests with python3.9:
[...]
=== FAILURES ===
__ test_msgpack[application/msgpack] ___
media_type = 'application/msgpack'
@pytest.mark.parametrize('media_type', [
('application/msgpack'),
('application/msgpack; charset=utf-8'),
('application/x-msgpack'),
])
def test_msgpack(media_type):
client = create_client({
> 'application/msgpack': media.MessagePackHandler(),
'application/x-msgpack': media.MessagePackHandler(),
})
tests/test_request_media.py:46:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
falcon/media/msgpack.py:31: in __init__
self.packer = msgpack.Packer(
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
> ???
E TypeError: __init__() got an unexpected keyword argument 'encoding'
msgpack/_packer.pyx:118: TypeError
___ test_msgpack[application/msgpack; charset=utf-8] ___
media_type = 'application/msgpack; charset=utf-8'
@pytest.mark.parametrize('media_type', [
('application/msgpack'),
('application/msgpack; charset=utf-8'),
('application/x-msgpack'),
])
def test_msgpack(media_type):
client = create_client({
> 'application/msgpack': media.MessagePackHandler(),
'application/x-msgpack': media.MessagePackHandler(),
})
tests/test_request_media.py:46:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
falcon/media/msgpack.py:31: in __init__
self.packer = msgpack.Packer(
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
> ???
E TypeError: __init__() got an unexpected keyword argument 'encoding'
msgpack/_packer.pyx:118: TypeError
_ test_msgpack[application/x-msgpack] __
media_type = 'application/x-msgpack'
@pytest.mark.parametrize('media_type', [
('application/msgpack'),
('application/msgpack; charset=utf-8'),
('application/x-msgpack'),
])
def test_msgpack(media_type):
client = create_client({
> 'application/msgpack': media.MessagePackHandler(),
'application/x-msgpack': media.MessagePackHandler(),
})
tests/test_request_media.py:46:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
falcon/media/msgpack.py:31: in __init__
self.packer = msgpack.Packer(
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
> ???
E TypeError: __init__() got an unexpected keyword argument 'encoding'
msgpack/_packer.pyx:118: TypeError
_ test_invalid_msgpack _
def test_invalid_msgpack():
> client = create_client({'application/msgpack':
> media.MessagePackHandler()})
tests/test_request_media.py:94:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
falcon/media/msgpack.py:31: in __init__
self.packer = msgpack.Packer(
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
> ???
E TypeError: __init__() got an unexpected keyword argument 'encoding'
msgpack/_packer.pyx:118: TypeError
__ test_msgpack[application/msgpack] ___
media_type = 'application/msgpack'
@pytest.mark.parametrize('media_type', [
(falcon.MEDIA_MSGPACK),
('application/msgpack; charset=utf-8'),
('application/x-msgpack'),
])
def test_msgpack(media_type):
client = create_client({
> 'application/msgpack': media.MessagePackHandler(),
'application/x-msgpack': media.MessagePackHandler(),
})
tests/test_response_media.py:85:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
falcon/media/msgpack.py:31: in __init__
self.packer = msgpack.Packer(
_ _ _ _ _ _
Bug#972228: CVE-2020-13991
Hi, I've updated to current upstream snapshot that fixes the issue, please upload: https://mentors.debian.net/package/iotjs/"; target="https://mentors.debian.net/package/iotjs/";>https://mentors.debian.net/package/iotjs/ The respective dsc file can be found at: https://mentors.debian.net/debian/pool/main/i/iotjs/iotjs_1.0+715-1.dsc"; target="https://mentors.debian.net/debian/pool/main/i/iotjs/iotjs_1.0+715-1.dsc";>https://mentors.debian.net/debian/pool/main/i/iotjs/iotjs_1.0+715-1.dsc -- https://purl.org/rzr/";>https://purl.org/rzr/ De : "Moritz Muehlenhoff" A : "Debian Bug Tracking System" Envoyé: mercredi 14 Octobre 2020 23:01 Objet : Bug#972228: CVE-2020-13991 Package: iotjs Severity: grave Tags: security X-Debbugs-Cc: Debian Security Team http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-13991 is for JerryScript, which iotjs appears to included. Cheers, Moritz
Processed: src:haskell-hoogle: fails to migrate to testing for too long: armhf autopkgtest regression
Processing control commands:
> close -1 5.0.18+dfsg1-1
Bug #972356 [src:haskell-hoogle] src:haskell-hoogle: fails to migrate to
testing for too long: armhf autopkgtest regression
Marked as fixed in versions haskell-hoogle/5.0.18+dfsg1-1.
Bug #972356 [src:haskell-hoogle] src:haskell-hoogle: fails to migrate to
testing for too long: armhf autopkgtest regression
Marked Bug as done
> block -1 by 971832
Bug #972356 {Done: Paul Gevers } [src:haskell-hoogle]
src:haskell-hoogle: fails to migrate to testing for too long: armhf autopkgtest
regression
972356 was not blocked by any bugs.
972356 was not blocking any bugs.
Added blocking bug(s) of 972356: 971832
> affects -1 src:ghc src:haskell-byte-order src:haskell-resolv
Bug #972356 {Done: Paul Gevers } [src:haskell-hoogle]
src:haskell-hoogle: fails to migrate to testing for too long: armhf autopkgtest
regression
Added indication that 972356 affects src:ghc, src:haskell-byte-order, and
src:haskell-resolv
--
972356: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972356
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#972356: src:haskell-hoogle: fails to migrate to testing for too long: armhf autopkgtest regression
Source: haskell-hoogle Version: 5.0.17.15+dfsg1-2 Severity: serious Control: close -1 5.0.18+dfsg1-1 Tags: sid bullseye User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 971832 Control: affects -1 src:ghc src:haskell-byte-order src:haskell-resolv Dear maintainer(s), As recently announced [1], the Release Team now considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing. Your package src:haskell-hoogle in its current version in unstable has been trying to migrate for 55 days [2]. But worse, it blocks several packages from migrating to testing, blocking the ghc transition. Hence, I am filing this bug. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bullseye, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=haskell-hoogle signature.asc Description: OpenPGP digital signature
Bug#972328: marked as done (beancount fails tests with python3.9)
Your message dated Fri, 16 Oct 2020 17:48:25 +
with message-id
and subject line Bug#972328: fixed in beancount 2.3.1-2
has caused the Debian Bug report #972328,
regarding beancount fails tests with python3.9
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.)
--
972328: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972328
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:beancount
Version: 2.3.1-1
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.9
beancount fails tests with python3.9:
[...]
=== FAILURES ===
___ TestScriptIdentify.test_identify ___
self =
def test_identify(self):
regexp = textwrap.dedent("""\
\\*\\*\\*\\* .*/Downloads/ofxdownload.ofx
Importer: +mybank-checking-ofx
Account: +Assets:Checking
\\*\\*\\*\\* .*/Downloads/Subdir/bank.csv
Importer: +mybank-credit-csv
Account: +Liabilities:CreditCard
\\*\\*\\*\\* .*/Downloads/Subdir/readme.txt
""").strip()
# Invoke with new-style imports as script, with an ingest() call in the
script.
with test_utils.capture('stdout', 'stderr') as (stdout, stderr):
env = os.environ.copy()
env['PYTHONPATH'] = ':'.join(sys.path)
> output = subprocess.check_output(
[path.join(self.tempdir, 'testimport.py'),
'--downloads', path.join(self.tempdir, 'Downloads'),
'identify'], shell=False, env=env)
beancount/ingest/identify_test.py:98:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
/usr/lib/python3.9/subprocess.py:420: in check_output
return run(*popenargs, stdout=PIPE, timeout=timeout, check=True,
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
input = None, capture_output = False, timeout = None, check = True
popenargs = (['/tmp/TestScriptIdentify.rj9xtztg/testimport.py', '--downloads',
'/tmp/TestScriptIdentify.rj9xtztg/Downloads', 'identify'],)
kwargs = {'env': {'APT_CONFIG': '/var/lib/sbuild/apt.conf', 'CCACHE_DIR':
'/<>/.pybuild/cca...g -Wformat -Werror=format-security',
'CPPFLAGS': '-Wdate-time -D_FORTIFY_SOURCE=2', ...}, 'shell': False, 'stdout':
-1}
process =
stdout = b'', stderr = None, retcode = 1
def run(*popenargs,
input=None, capture_output=False, timeout=None, check=False,
**kwargs):
"""Run command with arguments and return a CompletedProcess instance.
The returned instance will have attributes args, returncode, stdout and
stderr. By default, stdout and stderr are not captured, and those
attributes
will be None. Pass stdout=PIPE and/or stderr=PIPE in order to capture
them.
If check is True and the exit code was non-zero, it raises a
CalledProcessError. The CalledProcessError object will have the return
code
in the returncode attribute, and output & stderr attributes if those
streams
were captured.
If timeout is given, and the process takes too long, a TimeoutExpired
exception will be raised.
There is an optional argument "input", allowing you to
pass bytes or a string to the subprocess's stdin. If you use this
argument
you may not also use the Popen constructor's "stdin" argument, as
it will be used internally.
By default, all communication is in bytes, and therefore any "input"
should
be bytes, and the stdout and stderr will be bytes. If in text mode, any
"input" should be a string, and stdout and stderr will be strings
decoded
according to locale encoding, or by "encoding" if set. Text mode is
triggered by setting any of text, encoding, errors or
universal_newlines.
The other arguments are the same as for the Popen constructor.
"""
if input is not None:
if kwargs.get('stdin') is not None:
raise ValueError('stdin and input arguments may not both be
used.')
kwargs['stdin'] = PIPE
if capture_output:
if kwargs.get('stdout') is not None or kwargs.get('stderr') is not
None:
raise ValueError('stdout and stderr arguments may not be used '
'with capture_output.')
kwargs['stdout'] = PIPE
kwargs['stderr'] = PIPE
with Popen(*popenargs, **kwargs) as process:
Processed: Bug#972328 marked as pending in beancount
Processing control commands: > tag -1 pending Bug #972328 [src:beancount] beancount fails tests with python3.9 Added tag(s) pending. -- 972328: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972328 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#972328: marked as pending in beancount
Control: tag -1 pending Hello, Bug #972328 in beancount 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/beancount/-/commit/c2c24a8c051f9b4afe6327f0c6c7e5920b557759 Patch: Support testing against multiple python3.x versions. (Closes: #972328) (this message was generated automatically) -- Greetings https://bugs.debian.org/972328
Processed: notfixed 971737 in 1:78.3.1-2, closing 971737
Processing commands for cont...@bugs.debian.org:
> notfixed 971737 1:78.3.1-2
Bug #971737 {Done: Carsten Schoenert } [lightning]
lightning: all calendars disappeared (and throws errors when double-clicked)
No longer marked as fixed in versions 1:78.3.1-2.
> close 971737
Bug #971737 {Done: Carsten Schoenert } [lightning]
lightning: all calendars disappeared (and throws errors when double-clicked)
Bug 971737 is already marked as done; not doing anything.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
971737: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971737
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: tagging 972328
Processing commands for cont...@bugs.debian.org: > tags 972328 + ftbfs Bug #972328 [src:beancount] beancount fails tests with python3.9 Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 972328: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972328 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#972347: pyferret ftbfs with python3.9 as supported python3 version
Package: src:pyferret
Version: 5.3+dfsg1-3
Severity: serious
Tags: sid bullseye ftbfs
User: debian-pyt...@lists.debian.org
Usertags: python3.9
pyferret ftbfs with python3.9 as supported python3 version, packaging issue:
[...]
dh_python3 -a
D: dh_python3 dh_python3:161: version: 4.20200925
D: dh_python3 dh_python3:162: argv: ['/usr/bin/dh_python3', '-a']
D: dh_python3 dh_python3:163: options: {'guess_deps': True, 'skip_private':
False, 'verbose': False, 'arch': True, 'package': None, 'no_package': None,
'compile_all': False, 'vrange': None, 'regexpr': None,
'accept_upstream_versions': False, 'depends': None, 'depends_section': None,
'recommends': None, 'recommends_section': None, 'suggests': None,
'suggests_section': None, 'requires': None, 'shebang': None, 'ignore_shebangs':
False, 'clean_dbg_pkg': True, 'no_ext_rename': False, 'no_shebang_rewrite':
False, 'O': None}
D: dh_python3 dh_python3:164: args: []
D: dh_python3 dh_python3:165: supported Python versions: 3.8,3.9 (default=3.8)
D: dh_python3 debhelper:152: source=pyferret, binary packages=['python3-ferret']
D: dh_python3 dh_python3:183: processing package python3-ferret...
D: dh_python3 tools:102: fix_shebang (debian/python3-ferret/usr/bin/pyferret3):
doesn't look like a shebang: #! /bin/sh
I: dh_python3 fs:420: renaming gcircle-7.63-py3.8.egg-info to
gcircle-7.63.egg-info
I: dh_python3 fs:416: removing gcircle-7.63-py3.9.egg-info
(gcircle-7.63.egg-info is already available)
I: dh_python3 fs:420: renaming pipedviewer-7.63-py3.8.egg-info to
pipedviewer-7.63.egg-info
I: dh_python3 fs:416: removing pipedviewer-7.63-py3.9.egg-info
(pipedviewer-7.63.egg-info is already available)
I: dh_python3 fs:420: renaming pyferret-7.63-py3.8.egg-info to
pyferret-7.63.egg-info
I: dh_python3 fs:416: removing pyferret-7.63-py3.9.egg-info
(pyferret-7.63.egg-info is already available)
D: dh_python3 fs:260: package python3-ferret details = {'requires.txt': set(),
'egg-info':
{'debian/python3-ferret/usr/lib/python3/dist-packages/pipedviewer-7.63.egg-info',
'debian/python3-ferret/usr/lib/python3/dist-packages/gcircle-7.63.egg-info',
'debian/python3-ferret/usr/lib/python3/dist-packages/pyferret-7.63.egg-info'},
'nsp.txt': set(), 'shebangs': set(), 'public_vers': {Version('3')},
'private_dirs': {}, 'compile': True, 'ext_vers': {Version('3.8'),
Version('3.9')}, 'ext_no_version': set()}
D: dh_python3 depends:117: generating dependencies for package python3-ferret
D: dh_python3 pydist:142: trying to find dependency for multiprocessing
(python=None)
D: dh_python3 pydist:210: invoking dpkg -S
*python3/*/[Mm][Uu][Ll][Tt][Ii][Pp][Rr][Oo][Cc][Ee][Ss][Ss][Ii][Nn][Gg]-?*\.egg-info
D: dh_python3 pydist:226: dpkg -S did not find package for multiprocessing:
b'dpkg-query: no path found matching pattern
*python3/*/[Mm][Uu][Ll][Tt][Ii][Pp][Rr][Oo][Cc][Ee][Ss][Ss][Ii][Nn][Gg]-?*.egg-info\n'
I: dh_python3 pydist:229: Cannot find package that provides multiprocessing.
Please add package that provides it to Build-Depends or add "multiprocessing
python3-multiprocessing" line to debian/py3dist-overrides or add proper
dependency to Depends by hand and ignore this info.
D: dh_python3 pydist:142: trying to find dependency for numpy (python=None)
D: dh_python3 pydist:142: trying to find dependency for numpy (python=None)
D: dh_python3 depends:275: D={'python3 (<< 3.10)', 'python3 (>= 3.8~)',
'python3:any', 'python3:any (>= 3.6~)', 'python3-numpy'}; R=[]; S=[]; E=[],
B=[]; RT=[]
dh_lintian -a
install -d debian/python3-ferret/usr/share/lintian/overrides
install -p -m0644 debian/python3-ferret.lintian-overrides
debian/python3-ferret/usr/share/lintian/overrides/python3-ferret
dh_perl -a
dh_link -a
dh_strip_nondeterminism -a
dh_compress -a
cd debian/python3-ferret
chmod a-x usr/share/doc/python3-ferret/changelog.Debian
usr/share/doc/python3-ferret/changelog.Debian.amd64
gzip -9nf usr/share/doc/python3-ferret/changelog.Debian
usr/share/doc/python3-ferret/changelog.Debian.amd64
cd '/<>'
dh_fixperms -a
find debian/python3-ferret -true -print0 2>/dev/null | xargs -0r chown
--no-dereference 0:0
find debian/python3-ferret ! -type l -a -true -a -true -print0
2>/dev/null |
xargs -0r chmod go=rX,u+rw,a-s
find debian/python3-ferret/usr/share/doc -type f -a -true -a ! -regex
'debian/python3-ferret/usr/share/doc/[^/]*/examples/.*' -print0 2>/dev/null |
xargs -0r chmod 0644
find debian/python3-ferret/usr/share/doc -type d -a -true -a -true
-print0
2>/dev/null | xargs -0r chmod 0755
find debian/python3-ferret/usr/share/lintian/overrides -type f -a -true
-a
-true -print0 2>/dev/null | xargs -0r chmod 0644
find debian/python3-ferret -type f \( -name '*.so.*' -o -name '*.so' -o
-name
'*.la' -o -name '*.a' -o -name '*.js' -o -name '*.css' -o -name '*.scss' -o
-name '*.sass' -o -name '*.jpeg' -o -name '*.jpg' -o -name '*.png' -o -name
'*.gif' -o -name '*.cmxs' -o -name '*.node' \) -a -true -a -true -prin
Bug#972251: marked as done (python-line-profile ftbfs in unstable)
Your message dated Fri, 16 Oct 2020 15:35:41 +
with message-id
and subject line Bug#972251: fixed in python-line-profiler 2.1-2.1
has caused the Debian Bug report #972251,
regarding python-line-profile ftbfs in unstable
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
972251: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972251
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-line-profiler
Version: 2.1-2
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.9
likely not python3.9 specific, but needed to build for python3.9
[...]
I: pybuild base:217: /usr/bin/python3.9 setup.py build
running build
running build_py
copying line_profiler.py ->
/<>/.pybuild/cpython3_3.9_line-profiler/build
copying kernprof.py ->
/<>/.pybuild/cpython3_3.9_line-profiler/build
copying line_profiler_py35.py ->
/<>/.pybuild/cpython3_3.9_line-profiler/build
running build_ext
cythoning _line_profiler.pyx to _line_profiler.c
/usr/lib/python3/dist-packages/Cython/Compiler/Main.py:369: FutureWarning:
Cython directive 'language_level' not set, using 2 for now (Py2). This will
change in a later release! File: /<>/_line_profiler.pyx
tree = Parsing.p_module(s, pxd, full_module_name)
building '_line_profiler' extension
creating build
creating build/temp.linux-x86_64-3.9
x86_64-linux-gnu-gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g
-fwrapv -O2 -Wall -g -fstack-protector-strong -Wformat -Werror=format-security
-g -fwrapv -O2 -g -O2 -fdebug-prefix-map=/<>=.
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
-D_FORTIFY_SOURCE=2 -fPIC -I/usr/include/python3.9 -c _line_profiler.c -o
build/temp.linux-x86_64-3.9/_line_profiler.o
x86_64-linux-gnu-gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g
-fwrapv -O2 -Wall -g -fstack-protector-strong -Wformat -Werror=format-security
-g -fwrapv -O2 -g -O2 -fdebug-prefix-map=/<>=.
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
-D_FORTIFY_SOURCE=2 -fPIC -I/usr/include/python3.9 -c timers.c -o
build/temp.linux-x86_64-3.9/timers.o
timers.c:36:2: error: #error "This module requires gettimeofday() on non-Windows
platforms!"
36 | #error "This module requires gettimeofday() on non-Windows platforms!"
| ^
error: command '/usr/bin/x86_64-linux-gnu-gcc' failed with exit code 1
E: pybuild pybuild:352: build: plugin distutils failed with: exit code=1:
/usr/bin/python3.9 setup.py build
dh_auto_build: error: pybuild --build --test-pytest -i python{version} -p "3.9
3.8" returned exit code 13
make: *** [debian/rules:14: build-arch] Error 25
dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit
status 2
--- End Message ---
--- Begin Message ---
Source: python-line-profiler
Source-Version: 2.1-2.1
Done: Stefano Rivera
We believe that the bug you reported is fixed in the latest version of
python-line-profiler, 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 972...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Stefano Rivera (supplier of updated python-line-profiler
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Thu, 15 Oct 2020 23:00:41 -0700
Source: python-line-profiler
Architecture: source
Version: 2.1-2.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers
Changed-By: Stefano Rivera
Closes: 972251
Changes:
python-line-profiler (2.1-2.1) unstable; urgency=medium
.
* Non-maintainer upload.
* Patch: Python 3.9 compatibility, assume gettimeofday() exists and takes 2
arguments. (Closes: #972251)
Checksums-Sha1:
6a6dedbad9c755ef881ea5f7b2972cc1b3acb5fb 1662 python-line-profiler_2.1-2.1.dsc
e0c1877f617748806b165fd2646597abddcc7b77 6472
python-line-profiler_2.1-2.1.debian.tar.xz
ae4e4151f8a96a8707ecefe484abc7fa70c420e2 6528
python-line-profiler_2.1-2.1_source.buildinfo
Checksums-Sha256:
a84e91c07853933dde5d4bcb548f5fd92e17af8b273d9fac7195f137b095a26e 1662
python-line-profiler_2.1-2.1.dsc
bebb887457354be8b700cfb6e81c8baeb6ecda39c2afbe894de36f1c4b7001ae 6472
python-line-profiler_2.1-2.1.debian.tar.x
Bug#972241: FTBFS on amd64 and i386 (error: guestfs_launch failed)
guestfsd: error while loading shared libraries: libtirpc.so.3: cannot open shared object file: No such file or directory Did something change with how libtirpc gets packaged on Debian or upstream? Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-p2v converts physical machines to virtual machines. Boot with a live CD or over the network (PXE) and turn machines into KVM guests. http://libguestfs.org/virt-v2v
Bug#964592: libjson-rpc-cpp: diff for NMU version 0.7.0-1.1
Control: tags 964592 + patch
Control: tags 964592 + pending
Dear maintainer,
I'm sponsoring an NMU prepared by Baptiste Beauplat for libjson-rpc-cpp
(versioned as 0.7.0-1.1) and uploaded it to DELAYED/2.
Please feel free to tell me if I should delay it longer.
Regards.
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
More about me: https://mapreri.org : :' :
Launchpad user: https://launchpad.net/~mapreri `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia `-
diffstat for libjson-rpc-cpp-0.7.0 libjson-rpc-cpp-0.7.0
changelog |8 +
control|4
patches/0002-Fix-FTBFS-with-libmicrohttpd-0.9.71.patch | 77 +
patches/series |1
4 files changed, 88 insertions(+), 2 deletions(-)
diff -Nru libjson-rpc-cpp-0.7.0/debian/changelog libjson-rpc-cpp-0.7.0/debian/changelog
--- libjson-rpc-cpp-0.7.0/debian/changelog 2016-08-16 10:20:11.0 +0200
+++ libjson-rpc-cpp-0.7.0/debian/changelog 2020-10-08 22:45:52.0 +0200
@@ -1,3 +1,11 @@
+libjson-rpc-cpp (0.7.0-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Fix FTBFS with libmicrohttpd 0.9.71 (Closes: #964592)
+ * debian/control: Requires libmicrohttpd-dev (>= 0.9.71)
+
+ -- Baptiste Beauplat Thu, 08 Oct 2020 22:45:52 +0200
+
libjson-rpc-cpp (0.7.0-1) unstable; urgency=medium
* Imported Upstream version 0.7.0
diff -Nru libjson-rpc-cpp-0.7.0/debian/control libjson-rpc-cpp-0.7.0/debian/control
--- libjson-rpc-cpp-0.7.0/debian/control 2016-08-16 10:20:11.0 +0200
+++ libjson-rpc-cpp-0.7.0/debian/control 2020-10-08 22:45:52.0 +0200
@@ -7,7 +7,7 @@
libargtable2-dev,
libcurl4-openssl-dev | libcurl4-nss-dev,
libjsoncpp-dev,
- libmicrohttpd-dev
+ libmicrohttpd-dev (>= 0.9.71)
Standards-Version: 3.9.8.0
Section: libs
Homepage: https://github.com/cinemast/libjson-rpc-cpp
@@ -200,7 +200,7 @@
libjsonrpccpp-common0 (= ${binary:Version}),
libjsonrpccpp-server0 (= ${binary:Version}),
libjsonrpccpp-stub0 (= ${binary:Version}),
- libmicrohttpd-dev,
+ libmicrohttpd-dev (>= 0.9.71),
${misc:Depends}
Description: development files for JSON-RPC C++ framework
This package provides all required developer resources like header-files
diff -Nru libjson-rpc-cpp-0.7.0/debian/patches/0002-Fix-FTBFS-with-libmicrohttpd-0.9.71.patch libjson-rpc-cpp-0.7.0/debian/patches/0002-Fix-FTBFS-with-libmicrohttpd-0.9.71.patch
--- libjson-rpc-cpp-0.7.0/debian/patches/0002-Fix-FTBFS-with-libmicrohttpd-0.9.71.patch 1970-01-01 01:00:00.0 +0100
+++ libjson-rpc-cpp-0.7.0/debian/patches/0002-Fix-FTBFS-with-libmicrohttpd-0.9.71.patch 2020-10-08 22:45:52.0 +0200
@@ -0,0 +1,77 @@
+From: Baptiste Beauplat
+Date: Thu, 8 Oct 2020 22:44:11 +0200
+Subject: Fix FTBFS with libmicrohttpd 0.9.71
+
+Closes: #964592
+Bug: https://github.com/cinemast/libjson-rpc-cpp/issues/298
+---
+ src/jsonrpccpp/server/connectors/httpserver.cpp | 2 +-
+ src/jsonrpccpp/server/connectors/httpserver.h | 2 +-
+ src/test/testhttpserver.cpp | 4 ++--
+ src/test/testhttpserver.h | 4 ++--
+ 4 files changed, 6 insertions(+), 6 deletions(-)
+
+diff --git a/src/jsonrpccpp/server/connectors/httpserver.cpp b/src/jsonrpccpp/server/connectors/httpserver.cpp
+index 40d3c5e..d1bad41 100644
+--- a/src/jsonrpccpp/server/connectors/httpserver.cpp
b/src/jsonrpccpp/server/connectors/httpserver.cpp
+@@ -119,7 +119,7 @@ void HttpServer::SetUrlHandler(const string &url, IClientConnectionHandler *hand
+ this->SetHandler(NULL);
+ }
+
+-int HttpServer::callback(void *cls, MHD_Connection *connection, const char *url, const char *method, const char *version, const char *upload_data, size_t *upload_data_size, void **con_cls)
++MHD_Result HttpServer::callback(void *cls, MHD_Connection *connection, const char *url, const char *method, const char *version, const char *upload_data, size_t *upload_data_size, void **con_cls)
+ {
+ (void)version;
+ if (*con_cls == NULL)
+diff --git a/src/jsonrpccpp/server/connectors/httpserver.h b/src/jsonrpccpp/server/connectors/httpserver.h
+index 075962c..0f66423 100644
+--- a/src/jsonrpccpp/server/connectors/httpserver.h
b/src/jsonrpccpp/server/connectors/httpserver.h
+@@ -71,7 +71,7 @@ namespace jsonrpc
+
+ std::map urlhandler;
+
+-static int callback(void *cls, struct MHD_Connection *connection, const char *url, const char *method, const char *version, const char *upload_data, size_t *upload_data_size, void **con_cls);
++static MHD_Result callback(void *cls, struct MHD_Connection *connection, const char *url, const char *method, const c
Processed: libjson-rpc-cpp: diff for NMU version 0.7.0-1.1
Processing control commands: > tags 964592 + patch Bug #964592 [src:libjson-rpc-cpp] libjson-rpc-cpp FTBFS with libmicrohttpd 0.9.71 Added tag(s) patch. > tags 964592 + pending Bug #964592 [src:libjson-rpc-cpp] libjson-rpc-cpp FTBFS with libmicrohttpd 0.9.71 Added tag(s) pending. -- 964592: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964592 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#972250: [Debian-med-packaging] Bug#972250: vienna-rna needs a sourceful upload for python3.9
On Thu, 15 Oct 2020 at 12:03, Matthias Klose wrote: > vienna-rna needs a sourceful upload for python3.9, packages in contrib are not > built by the buildds. In this case, it seems the binaries for 2.4.14+dfsg-2 were never uploaded to the archive, so I think just building against current unstable and uploading should be fine.
Bug#972296: php-twig is available in buster-backports
Hi, Please use buster-backports version of php-twig and it will install. You can find how here: https://github.com/phpmyadmin/phpmyadmin/issues/15236#issuecomment-615954993 (apt-get install -t buster-backports php-twig) Regards, William Desportes
Processed: fixed 957365 in 20.3.0-1
Processing commands for cont...@bugs.debian.org: > fixed 957365 20.3.0-1 Bug #957365 [src:intel-mediasdk] intel-mediasdk: ftbfs with GCC-10 Marked as fixed in versions intel-mediasdk/20.3.0-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 957365: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957365 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#972340: pyferret FTBFS with more than one supported python3 version
Source: pyferret Version: 7.6.3-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/package.php?p=pyferret&suite=sid ... dh_missing -a dh_missing: warning: lib/python3.9/libpyferret.so exists in debian/tmp but is not installed to anywhere (related file: "debian/tmp/lib/python3.8/libpyferret.so") dh_missing: error: missing files, aborting ...
Bug#972339: armhf: hpcups crashes with free() invalid pointer for some printers
Package: printer-driver-hpcups Version: 3.20.9+dfsg0-3 Severity: serious Tags: upstream help According to the 3.20.9-3 armhf auutopkgtest run for migration testing; https://ci.debian.net/data/autopkgtest/testing/armhf/h/hplip/7460676/log.gz hpcups sometimes crashes with free(): invalid pointer. For instance, it seems that setting up a 'drv:///hpcups.drv/hp-officejet_pro_1150c.ppd' printer will let hpcups crash. I'd welcome assistance here as I'm no C gdb fluent person. -- Package-specific info: -- System Information: Debian Release: bullseye/sid APT prefers buildd-unstable APT policy: (990, 'buildd-unstable'), (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 'oldstable'), (100, 'experimental'), (1, 'experimental-debug') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.8.0-3-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND Locale: LANG=fr_CH.UTF-8, LC_CTYPE=fr_CH.UTF-8 (charmap=UTF-8), LANGUAGE=fr_CH:fr Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages printer-driver-hpcups depends on: ii cups 2.3.3-3 ii cups-filters [ghostscript-cups] 1.28.5-1 ii libc62.31-4 ii libcups2 2.3.3-3 ii libdbus-1-3 1.12.20-1 ii libgcc-s110.2.0-15 ii libhpmud03.20.9+dfsg0-3 ii libjpeg62-turbo 1:2.0.5-1.1 ii libstdc++6 10.2.0-15 ii zlib1g 1:1.2.11.dfsg-2 printer-driver-hpcups recommends no packages. Versions of packages printer-driver-hpcups suggests: pn hplip pn hplip-doc -- no debconf information
Processed: tagging 957123
Processing commands for cont...@bugs.debian.org: > tags 957123 + ftbfs Bug #957123 [src:dballe] dballe: ftbfs with GCC-10 Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 957123: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957123 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#969648: Bug#972033: python3.9, dask, pandas 1.1
On 10/14/20 8:11 PM, Matthias Klose wrote: > On 10/14/20 9:47 AM, Rebecca N. Palmer wrote: >> Control: severity 969648 serious >> Control: tags 969650 pending >> Control: tags 972033 pending >> >> Python 3.9 related breakage has been declared RC, so if nobody objects, I >> intend to upload pandas 1.1 to unstable (possibly tonight, but it probably >> won't >> build before numpy and matplotlib are binNMUd for Python 3.9) despite the >> dask >> breakage. >> >> As noted in #969648, it is likely that dask can be fixed, but this has not >> been >> tested in Debian. (Testing dask also currently fails for lack of a Python >> 3.9 >> numpy.) > > please wait until the required binNMUs are done. please give it a try now, and upload once the matplotlib binNMUs are also done for mipsel*
Processed: python-falcon: fails its tests with python3.9
Processing commands for cont...@bugs.debian.org: > reassign 972332 src:python-falcon 1.4.1-2 Bug #972332 [src:falcon] falcon fails it's tests with python3.9 Bug reassigned from package 'src:falcon' to 'src:python-falcon'. No longer marked as found in versions falcon/1.4.1-2. Ignoring request to alter fixed versions of bug #972332 to the same values previously set Bug #972332 [src:python-falcon] falcon fails it's tests with python3.9 Marked as found in versions python-falcon/1.4.1-2. > tags 972332 + ftbfs Bug #972332 [src:python-falcon] falcon fails it's tests with python3.9 Added tag(s) ftbfs. > retitle 972332 python-falcon: fails its tests with python3.9 Bug #972332 [src:python-falcon] falcon fails it's tests with python3.9 Changed Bug title to 'python-falcon: fails its tests with python3.9' from 'falcon fails it's tests with python3.9'. > thanks Stopping processing here. Please contact me if you need assistance. -- 972332: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972332 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#939324: marked as done (elixir: cannot be installed without Erlang from unstable)
Your message dated Fri, 16 Oct 2020 14:00:43 +0200 with message-id <20201016120043.ga2020...@mapreri.org> and subject line Re: Bug#939324: elixir: cannot be installed without Erlang from unstable has caused the Debian Bug report #939324, regarding elixir: cannot be installed without Erlang from unstable to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 939324: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939324 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: elixir Version: 1.9.1.dfsg-1~bpo10+1 Severity: normal Dear Maintainer, I tried installing elixir 1.9.1.dfsg-1~bpo10+1 from buster-backports. Apt marked it broken and told me to upgrade erlang-base to a version only available in unstable, even though installed version seemed to match the requirement. I think it may have something to do with #930497 because non-backports elixir 1.7.4-0.1 depends on erlang-base (>= 1:19) | erlang-base-hipe (>= 1:19), while elixir 1.9.1.dfsg-1~bpo10+1 depends on erlang-base:any (>= 1:20) | erlang-base-hipe:any (>= 1:20) and it seems buster versions of erlang don't have Multi-Arch: allowed. I'm not familiar enough with Debian packaging to try and suggest a fix. -- System Information: Debian Release: 10.0 APT prefers stable APT policy: (700, 'stable'), (600, 'unstable'), (500, 'stable-updates') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-5-amd64 (SMP w/6 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled --- End Message --- --- Begin Message --- On Thu, Oct 15, 2020 at 03:55:49PM +0200, Baptiste Beauplat wrote: > Control: tags -1 + patch > Control: severity -1 grave Note that this kind of thing is filed under "serious" not "grave" (even if at the end of the day they are pretty much the same) > On Tue, 03 Sep 2019 13:40:41 +0200 Michal Sidor > wrote: > > I tried installing elixir 1.9.1.dfsg-1~bpo10+1 from buster-backports. > > Apt marked it broken and told me to upgrade erlang-base to a version > > only available in unstable, even though installed version seemed to > > match the requirement. > > I've bump the severity as this bug actually makes the package uninstallable. > > I have prepared an NMU for elixir-lang (versioned as > 1.9.1.dfsg-1~bpo10+2). As I'm not a DD, I will be asking for my sponsor > (mattia, as CC'ed) to upload it for me to a DELAYED queue. Please feel > free to tell us if that NMU should be canceled/delayed. Since Evgeny gave his ACK, I'm uploading it directly. Note that uploads to backports do not close bugs, so I'm closing this bug manually now. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. More about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature --- End Message ---
Processed: severity of 964252 is important
Processing commands for cont...@bugs.debian.org:
> # reducing severity since this is a non-issue on the buildds
> severity 964252 important
Bug #964252 {Done: Sebastian Ramacher } [src:libbluray]
libbluray: FTBFS if texlive is installed in non-minimal build environment
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
964252: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964252
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#966968: marked as done (efp: FTBFS: efp.a65:line 89: 8000:Illegal segment error)
Your message dated Fri, 16 Oct 2020 11:19:25 + with message-id and subject line Bug#966968: fixed in efp 1.6-2 has caused the Debian Bug report #966968, regarding efp: FTBFS: efp.a65:line 89: 8000:Illegal segment error 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.) -- 966968: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966968 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: efp Version: 1.6-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200802 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > perl asm_to_a65.pl efp.asm > efp.a65 > sed -e '/^THRUST/d' -e 's/^;THRUST/THRUST/' efp.asm > efpbw.asm > perl asm_to_a65.pl efpbw.asm > efpbw.a65 > /usr/bin/xa -v5 -M efp.a65 -o efp.nes -l efp.lst > Copyright (C) 1989-2020 Andre Fachat, Jolse Maginnis, David Weinehall > and Cameron Kaiser. > Sun Aug 2 17:25:50 2020 > xAss65: Pass 1: efp.a65 > .zero > efp.a65:line 89: 8000:Illegal segment error > xAss65: Pass 2: > Statistics: > 137 of 5000 label used > 0 of4 byte label-memory used > 0 of 2340 PP-defs used > 0 of4 byte PP-memory used > 5981 of 20 byte buffer memory used > 0 blocks used > 0 seconds used > Break after 1 errors > make[1]: *** [Makefile:26: efp.nes] Error 1 The full build log is available from: http://qa-logs.debian.net/2020/08/02/efp_1.6-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- Source: efp Source-Version: 1.6-2 Done: Joseph Nahmias We believe that the bug you reported is fixed in the latest version of efp, 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 966...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Joseph Nahmias (supplier of updated efp package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 15 Oct 2020 22:46:10 -0400 Source: efp Architecture: source Version: 1.6-2 Distribution: unstable Urgency: medium Maintainer: Joseph Nahmias Changed-By: Joseph Nahmias Closes: 966968 Changes: efp (1.6-2) unstable; urgency=medium . [ Nicolas Boulenguez ] * [f702f8e] Typo spotted by Adam Gashlin * [454974b] Simplify and update copyright * [55df65e] Debhelper 13 * [f6aba05] Standards-Version: 4.5.0, Rules-Requires-Root: no * [02d92e3] Publish package history on salsa.debian.org. * [07ca481] Transfer maintainership . [ Joseph Nahmias ] * [ab59fee] build using dasm, not xa65 (Closes: 966968) * [c85df77] update maintainer field * [3381c4c] use salsa-ci pipeline Checksums-Sha1: 23cc028efac42f5cb230ec4e38a107cc02930722 1770 efp_1.6-2.dsc 14249d12a90e8452ee8a5cbb2b3be9592be5f927 4220 efp_1.6-2.debian.tar.xz 8d5e7d31efee08a8808f1ad63dc49f5a89f3cacd 5640 efp_1.6-2_amd64.buildinfo Checksums-Sha256: f3694ac608ae55f824af457dd4b9ef72992401a4ffc1c1a77067872793ea3cba 1770 efp_1.6-2.dsc d52057fabdcb2f27f93f738b83b473a44f6a058cda216a46a62d472684a861c9 4220 efp_1.6-2.debian.tar.xz 5f772824d020a122d6993b15585e5bbd5c3adee4be6df67eab8e81ba1d34b697 5640 efp_1.6-2_amd64.buildinfo Files: 6fbec52162506458425dc374490d4d0e 1770 games optional efp_1.6-2.dsc 6a42268be7b92aad346a40c7ec37a67a 4220 games optional efp_1.6-2.debian.tar.xz 66c25fa4a32832dd7413ebb4c53a110d 5640 games optional efp_1.6-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEcxc7CTsDz7hRCK0UsRvZGQeaO5gFAl+JevYACgkQsRvZGQea O5hHUw//RnFXvzE+lxGYBdhhzR5H4zjS11XqiEeJFpotM2xgxzEECodgaKCbWEFs IQwX5z5Wk29AH6CqfhO2jJrd0VwbD7oCo9Hp0eP3j4AacEJzc7mQZ6KmuGdnKNGQ T1CW1Q1S21oda8g6RBCHkvkBLxyI991zxDkvNKHgQ0eZRH8dJhs1GEvOz/p+tMVa SZgJzVttVhXG9S1TGrrXemR0Wy3Ns8iHgrgEUtLZZhjTqTo+JD01zx
Bug#972267: marked as done (gudhi: binary-all FTBFS)
Your message dated Fri, 16 Oct 2020 11:04:01 + with message-id and subject line Bug#972267: fixed in gudhi 3.3.0+dfsg-3 has caused the Debian Bug report #972267, regarding gudhi: binary-all FTBFS to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 972267: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972267 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gudhi Version: 3.3.0+dfsg-2 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=gudhi&ver=3.3.0%2Bdfsg-2 ... for py3ver in 3.9 3.8 ; do \ dh_auto_install --buildsystem=cmake --no-parallel --builddirectory=build-py$py3ver/userversion ; \ done cd build-py3.9/userversion && make -j1 install DESTDIR=/<>/gudhi-3.3.0\+dfsg/debian/tmp AM_UPDATE_INFO_DIR=no "INSTALL=install --strip-program=true" make[2]: Entering directory '/<>/build-py3.9/userversion' /usr/bin/cmake -S/<> -B/<>/build-py3.9/userversion --check-build-system CMakeFiles/Makefile.cmake 0 make -f CMakeFiles/Makefile2 preinstall make[3]: Entering directory '/<>/build-py3.9/userversion' make[3]: Nothing to be done for 'preinstall'. make[3]: Leaving directory '/<>/build-py3.9/userversion' Install the project... /usr/bin/cmake -P cmake_install.cmake -- Install configuration: "None" CMake Error at src/GudhUI/cmake_install.cmake:52 (file): file INSTALL cannot find "/<>/build-py3.9/userversion/src/GudhUI/GudhUI": No such file or directory. Call Stack (most recent call first): cmake_install.cmake:64 (include) make[2]: *** [Makefile:108: install] Error 1 ... --- End Message --- --- Begin Message --- Source: gudhi Source-Version: 3.3.0+dfsg-3 Done: Gard Spreemann We believe that the bug you reported is fixed in the latest version of gudhi, 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 972...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Gard Spreemann (supplier of updated gudhi 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, 16 Oct 2020 11:11:36 +0200 Source: gudhi Architecture: source Version: 3.3.0+dfsg-3 Distribution: unstable Urgency: medium Maintainer: Gard Spreemann Changed-By: Gard Spreemann Closes: 972267 Changes: gudhi (3.3.0+dfsg-3) unstable; urgency=medium . * Fix binary-all FTBFS. (Closes: #972267) Checksums-Sha1: 3c2488e4c643ab1005fce6c5304a43ac27cd1d19 3157 gudhi_3.3.0+dfsg-3.dsc 50b338a14fcb5d4eea1c833f24c178e9519e17d1 10968 gudhi_3.3.0+dfsg-3.debian.tar.xz a477944e71bd97f6679add87a5bc083aa4c7c6de 10866 gudhi_3.3.0+dfsg-3_source.buildinfo Checksums-Sha256: dd71169e6ce035713fe03300bd9e09484c65e3dbc5eb495cbddc07d1464410aa 3157 gudhi_3.3.0+dfsg-3.dsc d04038b43efa88cd60d79df81d86bfa5e7f360d005ff1a9a87f33150e229c66f 10968 gudhi_3.3.0+dfsg-3.debian.tar.xz 988deed4704ed8da319fe1756ba585072d7c0ef1090bc727ea2b89fdd15f4f6f 10866 gudhi_3.3.0+dfsg-3_source.buildinfo Files: 60101257e6324e007ceb21e9d8ddb99a 3157 math optional gudhi_3.3.0+dfsg-3.dsc eae3349b493797ae51b585acb8638537 10968 math optional gudhi_3.3.0+dfsg-3.debian.tar.xz 0c1ac64776654ee290acf0c5a066f498 10866 math optional gudhi_3.3.0+dfsg-3_source.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCgAwFiEEz8XvhRCFHnNVtV6AnRFYKv1UjPoFAl+JbrISHGdzcHJAbm9u ZW1wdHkub3JnAAoJEJ0RWCr9VIz67eoQAKHo+sqYHEyoSIX617AxleCgeunqt5HJ NOWuSohqi8rJI9AZiHr6VeYKKZVqxwji7HRZ88a+I52l/R5rOecMWzhVzGqikgsm Xp17ZUYWjJ2BrL2v6i/lh4KG9bPuScVLxUq6G1wpXQREsGC5NWuLV/a3Mu9vlZFl 04dI3P8JdifoofCl9oQixT1aJ9kwLnVGY5fo8QKgkskSG8hzrkSd0r39dEcpaEJn KWFLB0vaiG2QN2VFQWuacUhSRw83H6T4rKL6+ZxLvVL5t9vie++KH+9PkFkMEHvN fhYdJKXTRupd4corHIHfnVYovx4WysTQBhKNHHnjFUzvaZfRmgSc43FJaLl2jcim aJa5tcompDrQp5ETTlXeiQO3xZRfC3dufC6DjBgM8MqshMvr5Oufm1BXXEJwlRga 8T1mZNyknZiX/THM3luqr+SyNs4qp/ipqYvPf1VUKiM77mdfHtvl2GLIHJT9kj2b BnZtWJw3loE3F9E2vq8a8bPFVfM47gIOv3Y5OIpQP750i5JSuCZBEAWKTS6OJxUc 2c9E1ETLlfNDRCBZURNw7P2XUUGzfrXjABIS+4aEeLT6OpRMA7Cc7RMkMEwWNEJH 4ySls1sePwvihkVqAMOmoKAuAT6imx/fH9HAyfdXSPAW3ChlVCabBWD0rukvBYM5 XBDVG9wFUqht =qY6T -END PGP SIGNATURE End Message ---
Bug#972333: llvm-toolchain-11: FTBFS on mipsel: realloc(): invalid old size
Control: retitle -1 llvm-toolchain-11: FTBFS on ppc64el: realloc(): invalid old size On 2020-10-16 11:31:26, Sebastian Ramacher wrote: > Source: llvm-toolchain-11 > Version: 1:11.0.0-1 > Severity: serious > Tags: ftbfs sid bullseye > Justification: fails to build from source (but built successfully in the past) > > llvm-toolchain-11 currently FTBFS on mipsel64: Should have been ppc64el, of course. Cheers > | cd build-llvm; \ > | CFLAGS=`dpkg-buildflags --get CFLAGS`; \ > | CFLAGS="$CFLAGS `dpkg-buildflags --get CPPFLAGS`"; \ > | echo $CFLAGS; \ > | /<>/build-llvm/tools/clang/stage2-bins/bin/clang++ -c $CFLAGS > -std=c++11 /<>/compiler-rt/lib/fuzzer/*.cpp -IFuzzer; \ > | ar ruv libFuzzer.a Fuzzer*.o > | -g -O2 -fdebug-prefix-map=/<>/build-llvm=. > -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time > -D_FORTIFY_SOURCE=2 > | realloc(): invalid old size > | Aborted > | ar: `u' modifier ignored since `D' is the default (see `U') > | ar: creating libFuzzer.a > | ar: Fuzzer*.o: No such file or directory > | make[1]: *** [debian/rules:425: debian-libfuzzer-build] Error 1 > > See > https://buildd.debian.org/status/fetch.php?pkg=llvm-toolchain-11&arch=ppc64el&ver=1%3A11.0.0-2&stamp=1602683353&raw=0 > > It fails in the same step as llvm-toolchain-10 (#972318), but fails in a > different way. > > Cheers -- Sebastian Ramacher
Processed: Re: Bug#972333: llvm-toolchain-11: FTBFS on mipsel: realloc(): invalid old size
Processing control commands: > retitle -1 llvm-toolchain-11: FTBFS on ppc64el: realloc(): invalid old size Bug #972333 [src:llvm-toolchain-11] llvm-toolchain-11: FTBFS on mipsel: realloc(): invalid old size Changed Bug title to 'llvm-toolchain-11: FTBFS on ppc64el: realloc(): invalid old size' from 'llvm-toolchain-11: FTBFS on mipsel: realloc(): invalid old size'. -- 972333: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972333 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#972334: llvm-toolchain-11: autopkgtest failure on i386: integration-test-suite-test FAIL non-zero exit status 2
Source: llvm-toolchain-11 Version: 1:11.0.0-2 Severity: serious The autopkgtest for i386 currently fail: | | Failed Tests (4): | LLVM regression suite :: basic_lldb.c | LLVM regression suite :: basic_lldb2.cpp | LLVM regression suite :: test_asan_lc.c | LLVM regression suite :: test_tsan.c | | | Testing Time: 13.96s | Unsupported: 3 | Passed : 18 | Failed : 4 See https://ci.debian.net/data/autopkgtest/testing/i386/l/llvm-toolchain-11/7487758/log.gz for the full log Cheers -- Sebastian Ramacher
Processed: severity of 952741 is important
Processing commands for cont...@bugs.debian.org: > severity 952741 important Bug #952741 [src:puma] [RFH] FTBFS: Tests sometimes get stuck and the build gets forcefully terminated Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 952741: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952741 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#942735: marked as done (rules snippet to move the include directory is not valid shell script and breaks with Python 3.8)
Your message dated Fri, 16 Oct 2020 09:49:50 + with message-id and subject line Bug#942735: fixed in python-persistent 4.6.4-0.1 has caused the Debian Bug report #942735, regarding rules snippet to move the include directory is not valid shell script and breaks with Python 3.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.) -- 942735: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942735 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:python-persistent Version: 4.2.2-3 Severity: serious Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: python3.8 this doesn't do what is intended, and will break with 3.8. [...] override_dh_install: dh_install for d in debian/python3-persistent/usr/include/python*; do \ [ "$$d" = *m ] || mv "$$d" "$$d"m; \ done --- End Message --- --- Begin Message --- Source: python-persistent Source-Version: 4.6.4-0.1 Done: Matthias Klose We believe that the bug you reported is fixed in the latest version of python-persistent, 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 942...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matthias Klose (supplier of updated python-persistent 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: Fri, 16 Oct 2020 11:15:27 +0200 Source: python-persistent Architecture: source Version: 4.6.4-0.1 Distribution: unstable Urgency: medium Maintainer: Debian Python Modules Team Changed-By: Matthias Klose Closes: 942735 970165 Changes: python-persistent (4.6.4-0.1) unstable; urgency=medium . * Non-maintainer upload. * New upstream version. * Clean uploaders list. Closes: #970165. * Bump debhelper and standards versions. * Build-depend on python3-cffi, python3-manuel. * Drop the special casing of the header installs. Closes: #942735. Checksums-Sha1: bf0f9844d05766e33f8bdcf9289555b3998b396e 2258 python-persistent_4.6.4-0.1.dsc 3401447c0f67aaac5230e7afb7b16f519f9497d2 120032 python-persistent_4.6.4.orig.tar.gz de62aa5381025bdc780d406a4d025b1e524213af 4464 python-persistent_4.6.4-0.1.debian.tar.xz 3c6baafba056e70ce89c9caf2c25c028d6ce8d35 8114 python-persistent_4.6.4-0.1_source.buildinfo Checksums-Sha256: b2b19fe4ce6892848975802e2e9f0ed30147da72f274a1b6bba93e75e72b11e3 2258 python-persistent_4.6.4-0.1.dsc f83f54355a44cf8ec38c29ce47b378a8c70444e9a745581dbb13d201a24cb546 120032 python-persistent_4.6.4.orig.tar.gz 14add2c0c76523e31bac6b6f6d618008533760e4b1120aa48256aef61f80f099 4464 python-persistent_4.6.4-0.1.debian.tar.xz d9ebdc79a5f34a9e172362ae34cd5e6e10b4a3940ebcbe3e745624bf3d85abbb 8114 python-persistent_4.6.4-0.1_source.buildinfo Files: 88a410f547e459bc93e66d49aa366da0 2258 python optional python-persistent_4.6.4-0.1.dsc 6878fd3a3008fb5b7da7a374155fd6c2 120032 python optional python-persistent_4.6.4.orig.tar.gz b2274632e03146fb23897daea5f48482 4464 python optional python-persistent_4.6.4-0.1.debian.tar.xz dbc493010134cf666b6ce8d45d1eb822 8114 python optional python-persistent_4.6.4-0.1_source.buildinfo -BEGIN PGP SIGNATURE- iQJEBAEBCAAuFiEE1WVxuIqLuvFAv2PWvX6qYHePpvUFAl+JZwAQHGRva29AZGVi aWFuLm9yZwAKCRC9fqpgd4+m9TbTD/9Ptx57oJ8ohTJXG3z54kAM/OQ7LEUneL2S BXywaLJ3sBsLWwHl/B9cBbqUSV24QeQYSU8XdzrSdrJhCKuYe5as0pDNs9FmzGmi Qcr/5OFickDOdNIjE6U+5suQiRsWt4BrVTeZ8Ahfi090mCqJfA/7bQFyBO2ADuXM ZPb5gtifcMG9s7kzQuImhVyx6P0jxMPBcxz48w34JShC2Um+BE2Sw7gjgdTsU5CA lka7XMdAxW/moqiO2wxHVEgoGbAEThUuyHYTRKeCWBZQXIWf0ZeQtAIcvG5Chnnu +/hSxa//Esgsc5u5/btN5Iu2oxWLJ+M2I9zv3fL+F79eJGJr088AYNZP7ZEs//s9 a53xx8TXXFbbqCUguCiu/VVj2IEHBO9F7p8RohltHMBoIAcfRjuvC/w9IKMhZNKc qM8S3NuUF56CA9xrgSsaVucwp/qSSM+gbSWZgiwHjZJ2g3XzBMCT9f+p1ksTGxnG 3ZvuToJ4rphyiEZ5xp1DA1OfB8IAzzClKJymzBdlj6mpgYrExMwWq0S1b+dhdnth ZsnPuN0KxSrwdeUUA79D6aGNvmRuskkmV0LiQe5pRx1bWk1peBhRfwbPHgCkKnKw Waf4ryK8cjpf0SxTs4jGwW4kEWaP00NcO38Rk+ry0T5OI+NwZ1h+HwwMNFKJo17E 9fShtxDhVg== =5VbF -END PGP SIGNATURE End Message ---
Processed: Re: mdadm: mdcheck_start.service trying to start unexisting file
Processing commands for cont...@bugs.debian.org:
> found 960132 4.1-1
Bug #960132 {Done: Felix Lechner } [mdadm] mdadm:
mdcheck_start.service trying to start unexisting file
Marked as found in versions mdadm/4.1-1.
> severity 960132 serious
Bug #960132 {Done: Felix Lechner } [mdadm] mdadm:
mdcheck_start.service trying to start unexisting file
Severity set to 'serious' from 'normal'
> --
Stopping processing here.
Please contact me if you need assistance.
--
960132: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960132
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#972333: llvm-toolchain-11: FTBFS on mipsel: realloc(): invalid old size
Source: llvm-toolchain-11 Version: 1:11.0.0-1 Severity: serious Tags: ftbfs sid bullseye Justification: fails to build from source (but built successfully in the past) llvm-toolchain-11 currently FTBFS on mipsel64: | cd build-llvm; \ | CFLAGS=`dpkg-buildflags --get CFLAGS`; \ | CFLAGS="$CFLAGS `dpkg-buildflags --get CPPFLAGS`"; \ | echo $CFLAGS; \ | /<>/build-llvm/tools/clang/stage2-bins/bin/clang++ -c $CFLAGS -std=c++11 /<>/compiler-rt/lib/fuzzer/*.cpp -IFuzzer; \ | ar ruv libFuzzer.a Fuzzer*.o | -g -O2 -fdebug-prefix-map=/<>/build-llvm=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 | realloc(): invalid old size | Aborted | ar: `u' modifier ignored since `D' is the default (see `U') | ar: creating libFuzzer.a | ar: Fuzzer*.o: No such file or directory | make[1]: *** [debian/rules:425: debian-libfuzzer-build] Error 1 See https://buildd.debian.org/status/fetch.php?pkg=llvm-toolchain-11&arch=ppc64el&ver=1%3A11.0.0-2&stamp=1602683353&raw=0 It fails in the same step as llvm-toolchain-10 (#972318), but fails in a different way. Cheers -- Sebastian Ramacher
Processed: tagging 972318
Processing commands for cont...@bugs.debian.org: > tags 972318 + ftbfs Bug #972318 [src:llvm-toolchain-10] FTBFS on ppc64el Ignoring request to alter tags of bug #972318 to the same tags previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 972318: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972318 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#959527: marked as done (php-phpmyadmin-motranslator: Parse error: unexpected 'const' (T_CONST) in Translator.php on line 58)
Your message dated Fri, 16 Oct 2020 10:54:27 +0200 with message-id <175309e1458.f76b484d199825.6932515123807077...@wdes.fr> and subject line Nothing to be done. has caused the Debian Bug report #959527, regarding php-phpmyadmin-motranslator: Parse error: unexpected 'const' (T_CONST) in Translator.php on line 58 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.) -- 959527: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959527 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: php-phpmyadmin-motranslator Version: 5.0.0-2 Severity: grave Tags: a11y Justification: renders package unusable Dear Maintainer, I tried to open the index page of my local phpmyadmin installation in my webbrowser, but it crashed with the following error. Parse error: syntax error, unexpected 'const' (T_CONST), expecting variable (T_VARIABLE) in /usr/share/php/PhpMyAdmin/MoTranslator/Translator.php on line 58 -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.5.0-2-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages php-phpmyadmin-motranslator depends on: ii php-common 2:69 ii php-symfony-expression-language 4.4.4-1 php-phpmyadmin-motranslator recommends no packages. php-phpmyadmin-motranslator suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- X-CrossAssassin-Score: 20167--- End Message ---
Bug#972018: pyfftw ftbfs with python3.9 as supported python version
Source: pyfftw Followup-For: Bug #972018 Key piece of information missing in this bug report. Which arch is failing? Is this a duplicate of #917095 ?
Bug#972332: falcon fails it's tests with python3.9
Package: src:falcon
Version: 1.4.1-2
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.9
falcon fails it's tests with python3.9:
[...]
=== FAILURES ===
__ test_msgpack[application/msgpack] ___
media_type = 'application/msgpack'
@pytest.mark.parametrize('media_type', [
('application/msgpack'),
('application/msgpack; charset=utf-8'),
('application/x-msgpack'),
])
def test_msgpack(media_type):
client = create_client({
> 'application/msgpack': media.MessagePackHandler(),
'application/x-msgpack': media.MessagePackHandler(),
})
tests/test_request_media.py:46:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
falcon/media/msgpack.py:31: in __init__
self.packer = msgpack.Packer(
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
> ???
E TypeError: __init__() got an unexpected keyword argument 'encoding'
msgpack/_packer.pyx:118: TypeError
___ test_msgpack[application/msgpack; charset=utf-8] ___
media_type = 'application/msgpack; charset=utf-8'
@pytest.mark.parametrize('media_type', [
('application/msgpack'),
('application/msgpack; charset=utf-8'),
('application/x-msgpack'),
])
def test_msgpack(media_type):
client = create_client({
> 'application/msgpack': media.MessagePackHandler(),
'application/x-msgpack': media.MessagePackHandler(),
})
tests/test_request_media.py:46:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
falcon/media/msgpack.py:31: in __init__
self.packer = msgpack.Packer(
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
> ???
E TypeError: __init__() got an unexpected keyword argument 'encoding'
msgpack/_packer.pyx:118: TypeError
_ test_msgpack[application/x-msgpack] __
media_type = 'application/x-msgpack'
@pytest.mark.parametrize('media_type', [
('application/msgpack'),
('application/msgpack; charset=utf-8'),
('application/x-msgpack'),
])
def test_msgpack(media_type):
client = create_client({
> 'application/msgpack': media.MessagePackHandler(),
'application/x-msgpack': media.MessagePackHandler(),
})
tests/test_request_media.py:46:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
falcon/media/msgpack.py:31: in __init__
self.packer = msgpack.Packer(
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
> ???
E TypeError: __init__() got an unexpected keyword argument 'encoding'
msgpack/_packer.pyx:118: TypeError
_ test_invalid_msgpack _
def test_invalid_msgpack():
> client = create_client({'application/msgpack':
> media.MessagePackHandler()})
tests/test_request_media.py:94:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
falcon/media/msgpack.py:31: in __init__
self.packer = msgpack.Packer(
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
> ???
E TypeError: __init__() got an unexpected keyword argument 'encoding'
msgpack/_packer.pyx:118: TypeError
__ test_msgpack[application/msgpack] ___
media_type = 'application/msgpack'
@pytest.mark.parametrize('media_type', [
(falcon.MEDIA_MSGPACK),
('application/msgpack; charset=utf-8'),
('application/x-msgpack'),
])
def test_msgpack(media_type):
client = create_client({
> 'application/msgpack': media.MessagePackHandler(),
'application/x-msgpack': media.MessagePackHandler(),
})
tests/test_response_media.py:85:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
falcon/media/msgpack.py:31: in __init__
self.packer = msgpack.Packer(
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
> ???
E TypeError: __init__() got an unexpected keyword argument 'encoding'
msgpack/_packer.pyx:118: TypeError
___ test_msgpack[application/msgpack; charset=utf-8] ___
media_type = 'application/msgpack; charset=utf-8'
@pytest.mark.parametrize('media_type', [
(falcon.MEDIA_MSGPACK),
('application/msgpack; charset=utf-8'),
('application/x-msgpack'),
])
def test_msgpack(media_type):
client = create_client({
> 'application/msgpack': media.MessagePackHandler(),
'application/x-msgpack': media.MessagePackHandler(),
})
tests/test_response_media.py:85:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
falcon/media/
Bug#972296: marked as done (phpmyadmin: missing dependency (php-twig >= 2.9))
Your message dated Fri, 16 Oct 2020 10:46:53 +0200 with message-id <1753097255d.b13d838e198818.4083590490795138...@wdes.fr> and subject line php-twig is available in buster-backports has caused the Debian Bug report #972296, regarding phpmyadmin: missing dependency (php-twig >= 2.9) 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.) -- 972296: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972296 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: phpmyadmin Version: 4:4.9.5+dfsg1-2~bpo10+1 Severity: grave Justification: renders package unusable Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? I tried to install this package: apt-cache policy phpmyadmin phpmyadmin: Installed: (none) Candidate: 4:4.9.5+dfsg1-2~bpo10+1 Version table: 4:4.9.5+dfsg1-2~bpo10+1 100 100 http://deb.debian.org/debian buster-backports/main amd64 Packages Install failed with a missing dependency: apt install phpmyadmin Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: phpmyadmin : Depends: php-twig (>= 2.9) but 2.6.2-2 is to be installed E: Unable to correct problems, you have held broken packages. There is, however, a dependency to package php-twig >= 2.9. Thw freshest version of this package available in Buster doesn't satisfy this dependency: apt-cache policy php-twig php-twig: Installed: (none) Candidate: 2.6.2-2 Version table: 2.13.1-1~bpo10+1 100 100 http://deb.debian.org/debian buster-backports/main amd64 Packages 2.6.2-2 500 500 http://deb.debian.org/debian buster/main amd64 Packages Package depencies should be checked. Is it really necessary to have php-twig in version 2.9? One should think this outdated version of phpMyAdmin can work with the php-twig package included in Buster. *** End of the template - remove these template lines *** -- System Information: Debian Release: 10.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-10-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages phpmyadmin depends on: ii dbconfig-common 2.0.11+deb10u1 ii debconf [debconf-2.0] 1.5.71 pn libjs-openlayers pn libjs-sphinxdoc pn php ii php-common 2:76+0~20200511.26+debian10~1.gbpc9beb6 pn php-google-recaptcha ii php-json2:7.4+76+0~20200511.26+debian10~1.gbpc9beb6 ii php-mbstring2:7.4+76+0~20200511.26+debian10~1.gbpc9beb6 ii php-mysql 2:7.4+76+0~20200511.26+debian10~1.gbpc9beb6 pn php-phpmyadmin-motranslator pn php-phpmyadmin-shapefile pn php-phpmyadmin-sql-parser pn php-phpseclib pn php-psr-container pn php-symfony-expression-languag pn php-twig pn php-twig-extensions ii php-xml 2:7.4+76+0~20200511.26+debian10~1.gbpc9beb6 ii php7.4-cli [php-cli]7.4.11-1+0~20201008.26+debian10~1.gbpcf3106 ii php7.4-json [php-json] 7.4.11-1+0~20201008.26+debian10~1.gbpcf3106 ii php7.4-mbstring [php-mbstring] 7.4.11-1+0~20201008.26+debian10~1.gbpcf3106 ii php7.4-xml [php-xml]7.4.11-1+0~20201008.26+debian10~1.gbpcf3106 ii sensible-utils 0.0.12 ii ucf 3.0038+nmu1 Versions of packages phpmyadmin recommends: ii apache2 [httpd] 2.4.46-2~20200810.12+debian10 ii php
Bug#972328: beancount fails tests with python3.9
Package: src:beancount
Version: 2.3.1-1
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.9
beancount fails tests with python3.9:
[...]
=== FAILURES ===
___ TestScriptIdentify.test_identify ___
self =
def test_identify(self):
regexp = textwrap.dedent("""\
\\*\\*\\*\\* .*/Downloads/ofxdownload.ofx
Importer: +mybank-checking-ofx
Account: +Assets:Checking
\\*\\*\\*\\* .*/Downloads/Subdir/bank.csv
Importer: +mybank-credit-csv
Account: +Liabilities:CreditCard
\\*\\*\\*\\* .*/Downloads/Subdir/readme.txt
""").strip()
# Invoke with new-style imports as script, with an ingest() call in the
script.
with test_utils.capture('stdout', 'stderr') as (stdout, stderr):
env = os.environ.copy()
env['PYTHONPATH'] = ':'.join(sys.path)
> output = subprocess.check_output(
[path.join(self.tempdir, 'testimport.py'),
'--downloads', path.join(self.tempdir, 'Downloads'),
'identify'], shell=False, env=env)
beancount/ingest/identify_test.py:98:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
/usr/lib/python3.9/subprocess.py:420: in check_output
return run(*popenargs, stdout=PIPE, timeout=timeout, check=True,
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
input = None, capture_output = False, timeout = None, check = True
popenargs = (['/tmp/TestScriptIdentify.rj9xtztg/testimport.py', '--downloads',
'/tmp/TestScriptIdentify.rj9xtztg/Downloads', 'identify'],)
kwargs = {'env': {'APT_CONFIG': '/var/lib/sbuild/apt.conf', 'CCACHE_DIR':
'/<>/.pybuild/cca...g -Wformat -Werror=format-security',
'CPPFLAGS': '-Wdate-time -D_FORTIFY_SOURCE=2', ...}, 'shell': False, 'stdout':
-1}
process =
stdout = b'', stderr = None, retcode = 1
def run(*popenargs,
input=None, capture_output=False, timeout=None, check=False,
**kwargs):
"""Run command with arguments and return a CompletedProcess instance.
The returned instance will have attributes args, returncode, stdout and
stderr. By default, stdout and stderr are not captured, and those
attributes
will be None. Pass stdout=PIPE and/or stderr=PIPE in order to capture
them.
If check is True and the exit code was non-zero, it raises a
CalledProcessError. The CalledProcessError object will have the return
code
in the returncode attribute, and output & stderr attributes if those
streams
were captured.
If timeout is given, and the process takes too long, a TimeoutExpired
exception will be raised.
There is an optional argument "input", allowing you to
pass bytes or a string to the subprocess's stdin. If you use this
argument
you may not also use the Popen constructor's "stdin" argument, as
it will be used internally.
By default, all communication is in bytes, and therefore any "input"
should
be bytes, and the stdout and stderr will be bytes. If in text mode, any
"input" should be a string, and stdout and stderr will be strings
decoded
according to locale encoding, or by "encoding" if set. Text mode is
triggered by setting any of text, encoding, errors or
universal_newlines.
The other arguments are the same as for the Popen constructor.
"""
if input is not None:
if kwargs.get('stdin') is not None:
raise ValueError('stdin and input arguments may not both be
used.')
kwargs['stdin'] = PIPE
if capture_output:
if kwargs.get('stdout') is not None or kwargs.get('stderr') is not
None:
raise ValueError('stdout and stderr arguments may not be used '
'with capture_output.')
kwargs['stdout'] = PIPE
kwargs['stderr'] = PIPE
with Popen(*popenargs, **kwargs) as process:
try:
stdout, stderr = process.communicate(input, timeout=timeout)
except TimeoutExpired as exc:
process.kill()
if _mswindows:
# Windows accumulates the output in a single blocking
# read() call run on child threads, with the timeout
# being done in a join() on those threads. communicate()
# _after_ kill() is required to collect that and add it
# to the exception.
exc.stdout, exc.stderr = process.communicate()
else:
# POSIX _communicate already populated the output so
# far into the TimeoutExpired exception.
process.wait()
Bug#972327: zfsutils-linux: No NMU binary compliant
Package: zfsutils-linux Version: 0.8.4-2 Severity: serious Dear Maintainer, zfsutils-linux 0.8.4-2+b1 is uninstabblable because the zfs-dkms package is architecture all and thus has been not rebuild : $ LANG=C sudo apt-get install zfsutils-linux zfs-dkms Reading package lists... Done Building dependency tree Reading state information... Done zfs-dkms is already the newest version (0.8.4-2). Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: zfsutils-linux : Breaks: zfs-dkms (< 0.8.4-2+b1) but 0.8.4-2 is to be installed E: Unable to correct problems, you have held broken packages. Christian -- System Information: Debian Release: bullseye/sid APT prefers buildd-unstable APT policy: (500, 'buildd-unstable'), (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.8.15 (SMP w/8 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages zfsutils-linux depends on: ii libblkid12.36-3+b1 ii libc62.31-4 ii libnvpair1linux 0.8.4-2 ii libuuid1 2.36-3+b1 ii libuutil1linux 0.8.4-2 ii libzfs2linux 0.8.4-2 ii libzpool2linux 0.8.4-2 ii python3 3.8.6-1 Versions of packages zfsutils-linux recommends: ii lsb-base11.1.0 ii zfs-dkms [zfs-modules] 0.8.4-2 pn zfs-zed Versions of packages zfsutils-linux suggests: pn nfs-kernel-server ii samba-common-bin2:4.12.5+dfsg-3 pn zfs-initramfs | zfs-dracut -- Configuration Files: /etc/sudoers.d/zfs [Errno 13] Permission non accordée: '/etc/sudoers.d/zfs' -- no debconf information
Bug#969917: trimage: Trimage crashes with 10 or more png images
Control: tags -1 upstream Control: forwarded -1 https://github.com/Kilian/Trimage/issues/77
Processed: Re: trimage: Trimage crashes with 10 or more png images
Processing control commands: > tags -1 upstream Bug #969917 [trimage] trimage: Trimage crashes with 10 or more png images Added tag(s) upstream. > forwarded -1 https://github.com/Kilian/Trimage/issues/77 Bug #969917 [trimage] trimage: Trimage crashes with 10 or more png images Set Bug forwarded-to-address to 'https://github.com/Kilian/Trimage/issues/77'. -- 969917: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969917 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#939324: elixir: cannot be installed without Erlang from unstable
Hello Baptiste Thank you for your help. Feel free to upload the package. -- Evgeny On Thu, 15 Oct 2020 at 16:57, Baptiste Beauplat wrote: > Control: tags -1 + patch > Control: severity -1 grave > X-Debbugs-CC: Mattia Rizzolo > > Dear maintainer, > > On Tue, 03 Sep 2019 13:40:41 +0200 Michal Sidor > wrote: > > I tried installing elixir 1.9.1.dfsg-1~bpo10+1 from buster-backports. > > Apt marked it broken and told me to upgrade erlang-base to a version > > only available in unstable, even though installed version seemed to > > match the requirement. > > I've bump the severity as this bug actually makes the package > uninstallable. > > I have prepared an NMU for elixir-lang (versioned as > 1.9.1.dfsg-1~bpo10+2). As I'm not a DD, I will be asking for my sponsor > (mattia, as CC'ed) to upload it for me to a DELAYED queue. Please feel > free to tell us if that NMU should be canceled/delayed. > > Best, > -- > Baptiste Beauplat - lyknode >
