Bug#1071193: libqt6core6t64/experimental breaks ABI
Hi all, On Fri, May 17, 2024 at 01:07:31AM +0300, Adrian Bunk wrote: > Apparently the symbols were moved to PRIVATE_API: > _ZN5QUtf816convertToUnicodeE14QByteArrayViewPN20QStringConverterBase5StateE@@Qt_6_PRIVATE_API > _ZN5QUtf816convertToUnicodeEPDs14QByteArrayView@@Qt_6_PRIVATE_API > _ZN6QUtf1616convertToUnicodeE14QByteArrayViewPN20QStringConverterBase5StateE14DataEndianness@@Qt_6_PRIVATE_API > _ZN6QUtf3216convertToUnicodeE14QByteArrayViewPN20QStringConverterBase5StateE14DataEndianness@@Qt_6_PRIVATE_API > _ZN5QUtf818convertFromUnicodeE11QStringView@@Qt_6_PRIVATE_API > _ZN5QUtf818convertFromUnicodeE11QStringViewPN20QStringConverterBase5StateE@@Qt_6_PRIVATE_API > _ZN6QUtf1618convertFromUnicodeE11QStringViewPN20QStringConverterBase5StateE14DataEndianness@@Qt_6_PRIVATE_API > _ZN6QUtf3218convertFromUnicodeE11QStringViewPN20QStringConverterBase5StateE14DataEndianness@@Qt_6_PRIVATE_API I suspect this may be related to a change in Qt 6.5 where they replaced Perl code to look for private classes (findclasslist.pl) with C++ code in syncqt [1][2]. These QUtf8 / QUtf16 / QUtf32 structs were always defined in a private header (qstringconverter_p.h), so marking them as private is correct. Maybe findclasslist.pl only looked at classes marked as Q_*_EXPORT, while these structs are not marked as such (individual members are marked instead). [1]: https://code.qt.io/cgit/qt/qtbase.git/commit/?id=5a5ad8c0029ef9f9 [2]: https://code.qt.io/cgit/qt/qtbase.git/commit/?id=7f4aa1a3fa461064 > This is an upstream(?) ABI break, but since libqt6core5compat6 seems > to be the only affected package something like > Breaks: libqt6core5compat6 (<< 6.6) > might be the best available option to avoid issues when upgrading > from bookworm. I agree. -- Dmitry Shachnev signature.asc Description: PGP signature
Bug#1070389: uim: FTBFS: error: some symbols or patterns disappeared in the symbols file
Control: tags -1 + pending On Sat, May 04, 2024 at 08:52:16PM +0300, Dmitry Shachnev wrote: > I have prepared a merge request on salsa [2] fixing this build failure. > > [1]: > https://tracker.debian.org/news/1526298/accepted-glibc-238-7-source-into-unstable/ > [2]: https://salsa.debian.org/debian/uim/-/merge_requests/15 And as the Qt transition is starting soon and this is one of the blockers, I have uploaded NMU to DELAYED/2 based on that merge request. -- Dmitry Shachnev signature.asc Description: PGP signature
Bug#1068078: marked as pending in pyside2
Control: tag -1 pending Hello, Bug #1068078 in pyside2 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/qt-kde-team/qt/pyside2/-/commit/d13fffb9ad00291dc9e6636b8028db704b3b8ced Blacklist smart_pointer test. Closes: #1068078. (this message was generated automatically) -- Greetings https://bugs.debian.org/1068078
Bug#1066320: astlib: FTBFS: PyWCSTools/wcssubs-3.9.5/wcscon_wrap.c:3533:3: error: implicit declaration of function ‘wcscon’; did you mean ‘wcstoq’? [-Werror=implicit-function-declaration]
Control: tags -1 + patch Hi, On Wed, Mar 13, 2024 at 12:47:51PM +0100, Lucas Nussbaum wrote: > Source: astlib > Version: 0.11.10-1 > Severity: serious > Justification: FTBFS > Tags: trixie sid ftbfs > User: lu...@debian.org > Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef > > Hi, > > During a rebuild of all packages in sid, your package failed to build > on amd64. > > This is most likely caused by a change in dpkg 1.22.6, that enabled > -Werror=implicit-function-declaration. For more information, see > https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration I have created a MR on salsa which fixes this bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066320 -- Dmitry Shachnev signature.asc Description: PGP signature
Bug#1068038: FTBFS: error: ‘struct input_event’ has no member named ‘time’
Control: tags -1 + pending Hi, On Sat, Mar 30, 2024 at 02:10:56AM +0500, Andrey Rakhmatullin wrote: > Source: flightgear > Version: 1:2020.3.18+dfsg-1 > Severity: serious > Tags: ftbfs > > https://buildd.debian.org/status/fetch.php?pkg=flightgear=armhf=1%3A2020.3.18%2Bdfsg-1%2Bb2=1711729288=0 > > /<>/src/Input/FGLinuxEventInput.cxx: In member function ‘virtual > void FGLinuxInputDevice::Send(const char*, double)’: > /<>/src/Input/FGLinuxEventInput.cxx:418:7: error: ‘struct > input_event’ has no member named ‘time’ > 418 | evt.time.tv_sec = 0; > | ^~~~ > /<>/src/Input/FGLinuxEventInput.cxx:419:7: error: ‘struct > input_event’ has no member named ‘time’ > 419 | evt.time.tv_usec = 0; > | ^~~~ I have uploaded NMU which fixes this to DELAYED/2. The diff can be seen here: https://salsa.debian.org/debian/flightgear/-/merge_requests/3 It depends on my another NMU for simgear: unless simgear is rebuilt with the new time_t ABI, flightgear will fail to build with link failures. And simgear is a static library so we cannot just bump SONAME for it. -- Dmitry Shachnev signature.asc Description: PGP signature
Bug#1060926: simgear: FTBFS: Compositor.hxx:137:34: error: field ‘_uniforms’ has incomplete type ‘simgear::compositor::Compositor::BuiltinUniforms’ {aka ‘std::array, 14>’}
Control: tags -1 + pending
Hi,
On Tue, Jan 16, 2024 at 08:36:13PM +0100, Lucas Nussbaum wrote:
> Source: simgear
> Version: 1:2020.3.18+dfsg-2
> Severity: serious
> Justification: FTBFS
> Tags: trixie sid ftbfs
> User: lu...@debian.org
> Usertags: ftbfs-20240115 ftbfs-trixie
>
> Hi,
>
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
>
> Relevant part (hopefully):
> > cd /<>/build/simgear && /usr/bin/c++ -DHAVE_CONFIG_H
> > -DHAVE_INTTYPES_H -I/<> -I/<>/build/simgear
> > -I/<>/build -I/usr/include/AL
> > -I/<>/simgear/canvas/ShivaVG/include
> > -I/<>/3rdparty/utf8/source -g -O2
> > -ffile-prefix-map=/<>=. -fstack-protector-strong
> > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection
> > -Wdate-time -D_FORTIFY_SOURCE=2 -msse2 -mfpmath=sse -ftree-vectorize
> > -ftree-slp-vectorize -Wall -fPIC -Wno-unused-local-typedefs
> > -DBOOST_BIMAP_DISABLE_SERIALIZATION -DBOOST_NO_STDLIB_CONFIG -O3 -g
> > -DNDEBUG -msse2 -mfpmath=sse -ftree-vectorize -ftree-slp-vectorize
> > -std=gnu++11 -MD -MT
> > simgear/CMakeFiles/SimGearScene.dir/sound/xmlsound.cxx.o -MF
> > CMakeFiles/SimGearScene.dir/sound/xmlsound.cxx.o.d -o
> > CMakeFiles/SimGearScene.dir/sound/xmlsound.cxx.o -c
> > /<>/simgear/sound/xmlsound.cxx
> > In file included from
> > /<>/simgear/scene/viewer/Compositor.cxx:17:
> > /<>/simgear/scene/viewer/Compositor.hxx:137:34: error: field
> > ‘_uniforms’ has incomplete type
> > ‘simgear::compositor::Compositor::BuiltinUniforms’ {aka
> > ‘std::array, 14>’}
> > 137 | BuiltinUniforms _uniforms;
> > | ^
> > In file included from /usr/include/c++/13/bits/hashtable_policy.h:34,
> > from /usr/include/c++/13/bits/hashtable.h:35,
> > from /usr/include/c++/13/bits/unordered_map.h:33,
> > from /usr/include/c++/13/unordered_map:41,
> > from
> > /<>/simgear/scene/viewer/Compositor.hxx:20:
> > /usr/include/c++/13/tuple:2005:45: note: declaration of
> > ‘simgear::compositor::Compositor::BuiltinUniforms’ {aka ‘struct
> > std::array, 14>’}
> > 2005 | template struct array;
> > | ^
I have uploaded NMU which fixes this and another build failure to DELAYED/2.
The diff can be seen here:
https://salsa.debian.org/debian/simgear/-/merge_requests/1
--
Dmitry Shachnev
signature.asc
Description: PGP signature
Bug#1068155: lmms: FTBFS on i386: dh_install: warning: Cannot find (any matches for) "usr/lib/*/lmms/libvestige.so" (tried in ., debian/tmp)
Control: reassign -1 libwine-dev 9.0~repack-4 Control: affects -1 + src:lmms Hi all, On Tue, Apr 02, 2024 at 12:16:09PM +0200, Andreas Beckmann wrote: > Comparing bookworm and sid buildlogs shows the following relevant > differences during cmake: > > -Setting up libwine-dev:i386 (8.0~repack-4) ...^M > +Setting up libwine-dev:i386 (9.0~repack-4+b1) ...^M > > --- Found Wine: /usr/lib/i386-linux-gnu/wine/libwine.so > +CMake Warning (dev) at cmake/modules/FindWine.cmake:20 (EXEC_PROGRAM): > + Policy CMP0153 is not set: The exec_program command should not be called. > + Run "cmake --help-policy CMP0153" for policy details. Use the cmake_policy > + command to set the policy and suppress this warning. > + > + Use execute_process() instead. > +Call Stack (most recent call first): > + CMakeLists.txt:462 (FIND_PACKAGE) > +This warning is for project developers. Use -Wno-dev to suppress it. > + > +-- Could NOT find Wine (missing: WINE_LIBRARIES) > > -* VST-instrument hoster : OK, with workaround linking > /usr/lib/i386-linux-gnu/wine/i386-unix/libwinecrt0.a/ > -* VST-effect hoster : OK, with workaround linking > /usr/lib/i386-linux-gnu/wine/i386-unix/libwinecrt0.a/ > +* VST-instrument hoster : not found, please install (lib)wine-dev (or > similar) - 64 bit systems additionally need gcc-multilib and g++-multilib > +* VST-effect hoster : not found, please install (lib)wine-dev (or > similar) - 64 bit systems additionally need gcc-multilib and g++-multilib This is actually a bug in libwine-dev: libwine.so is a broken symlink: # ls -l /usr/lib/i386-linux-gnu/wine/libwine.so lrwxrwxrwx 1 root root 22 Mar 12 18:22 /usr/lib/i386-linux-gnu/wine/libwine.so -> i386-unix/libwine.so.1 # ls -l $(realpath /usr/lib/i386-linux-gnu/wine/libwine.so) ls: cannot access '/usr/lib/i386-linux-gnu/wine/i386-unix/libwine.so.1': No such file or directory The problem is not specific to i386, the same thing is on amd64: # ls -l $(realpath /usr/lib/x86_64-linux-gnu/wine/libwine.so) ls: cannot access '/usr/lib/x86_64-linux-gnu/wine/x86_64-unix/libwine.so.1': No such file or directory It's just lmms uses wine only on i386. -- Dmitry Shachnev signature.asc Description: PGP signature
Bug#1067326: mkdocstrings: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13
Hi Carsten! On Wed, Mar 20, 2024 at 10:00:48PM +0100, Lucas Nussbaum wrote: > Source: mkdocstrings > Version: 0.24.1-1 > Severity: serious > Justification: FTBFS > Tags: trixie sid ftbfs > User: lu...@debian.org > Usertags: ftbfs-20240319 ftbfs-trixie > > Hi, > > During a rebuild of all packages in sid, your package failed to build > on amd64. > > [...] > > The full build log is available from: > http://qa-logs.debian.net/2024/03/19/mkdocstrings_0.24.1-1_unstable.log Upstream released 0.24.2 today, which should fix this failure [1]. [1]: https://github.com/mkdocstrings/mkdocstrings/commit/c0d009000678a2cc -- Dmitry Shachnev signature.asc Description: PGP signature
Bug#1068078: FTBFS on armel: shiboken2:smart::smart_pointer Newly detected Real test failure!
Hi, (CCing debian-arm@l.d.o. Please CC me back as I’m not subscribed.) On Sat, Mar 30, 2024 at 02:11:32PM +0500, Andrey Rakhmatullin wrote: > Source: pyside2 > Version: 5.15.12-6.1 > Severity: serious > Tags: ftbfs > > https://buildd.debian.org/status/fetch.php?pkg=pyside2=armel=5.15.12-6.1=1711789575=0 > > RUN 2: Test project /<>/pyside3_build/py3.11-qt5.15.10-32bit- > relwithdebinfo/shiboken2 > RUN 2: Start 181: smart_smart_pointer > RUN 2: 1/1 Test #181: smart_smart_pointer ..***Failed0.23 sec > RUN 2: Running garbage collector for reference test > RUN 2: FFF > RUN 2: == > RUN 2: FAIL: testObjSmartPointer > (__main__.SmartPointerTests.testObjSmartPointer) > RUN 2: -- > RUN 2: Traceback (most recent call last): > RUN 2: File > "/<>/sources/shiboken2/tests/smartbinding/smart_pointer_test.py", > line 94, in testObjSmartPointer > RUN 2: self.assertEqual(integerCount(), 1) > RUN 2: AssertionError: 2 != 1 > [...] I tried to build pyside2 on two porterboxes, amdahl.d.o and abel.d.o, and on both it built successfully (in sid_armel-dchroot). I also ran the test manually several times after build, and it was successful too: (sid_armel-dchroot)mitya57@abel:~/pyside2-5.15.12/pyside3_build/py3.11-qt5.15.10-32bit-relwithdebinfo/shiboken2$ ctest --tests-regex '^(smart_smart_pointer)$' Test project /home/mitya57/pyside2-5.15.12/pyside3_build/py3.11-qt5.15.10-32bit-relwithdebinfo/shiboken2 Start 181: smart_smart_pointer 1/1 Test #181: smart_smart_pointer .. Passed0.48 sec 100% tests passed, 0 tests failed out of 1 Total Test time (real) = 0.53 sec Does anyone have ideas why there may be such difference between the buildds (arm-conova-01, arm-arm-03) and the porter boxes? It’s worth noting that the armhf build ran on the same arm-conova-01, and it was successful. -- Dmitry Shachnev signature.asc Description: PGP signature
Bug#1067906: marked as pending in qtwebengine-opensource-src
Control: tag -1 pending Hello, Bug #1067906 in qtwebengine-opensource-src 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/qt-kde-team/qt/qtwebengine/-/commit/d79902e07b870c7d8ef0b9912562885e96cbab76 Update debian/libqt5webenginecore5.symbols for armhf. Closes: #1067906. (this message was generated automatically) -- Greetings https://bugs.debian.org/1067906
Bug#1067906: marked as pending in qtwebengine-opensource-src
Control: tag -1 pending Hello, Bug #1067906 in qtwebengine-opensource-src 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/qt-kde-team/qt/qtwebengine/-/commit/d79902e07b870c7d8ef0b9912562885e96cbab76 Update debian/libqt5webenginecore5.symbols for armhf. Closes: #1067906. (this message was generated automatically) -- Greetings https://bugs.debian.org/1067906
Bug#1066967: Bug#1064593: Bug#1066967: dh_sphinxdoc: replaces files provided by read-the-doc theme by empty symlinks
Hi,
On Fri, Mar 22, 2024 at 03:30:55PM +0100, Holger Wansing wrote:
> Ok, I see.
> So, we will need to get sphinx-rtd-theme-common installed on all debian.org
> website mirrors, and it will just work (?) ...
From your earlier message it seemed to me like you are using the build
tree in your deploy process, not the built package.
That is why I suggested not running dh_sphinxdoc, however my suggestion
applied only to your deploy procedure. The package which is being uploaded
to Debian archive should still use dh_sphinxdoc.
If you are using the built package and installing it on the remote server,
then yes, install sphinx-rtd-theme-common and you should be good.
Actually, I would move ${sphinxdoc:Depends} from Recommends to Depends,
because the documentation is mostly unusable without the static files.
--
Dmitry Shachnev
signature.asc
Description: PGP signature
Bug#1066967: Bug#1064593: Bug#1066967: dh_sphinxdoc: replaces files provided by read-the-doc theme by empty symlinks
On Fri, Mar 22, 2024 at 01:46:48PM +0100, Holger Wansing wrote: > [...] > Anyway, the symlink points to some path inside the package build path, here: > /srv/debian-policy/debian-policy-4.6.2.1/debian/debian-policy/usr/share/sphinx_rtd_theme_static/css/theme.css > > and that path does not exist. > Same in the debian-policy binary package. This is expected. The path in the build tree is relative in a way that when a package is built and installed, it becomes working. The symlink is generated relative per Policy 10.5. And I think that even if dh_sphinxdoc generated it as absolute, dh_link would later change it to relative. If you are trying to rely on something that is in the build directory, you have to turn relative symlinks into absolute ones on your own. Or just don't call dh_sphinxdoc, then you will get normal files. -- Dmitry Shachnev signature.asc Description: PGP signature
Bug#1066967: dh_sphinxdoc: replaces files provided by read-the-doc theme by empty symlinks
Control: tags 1066967 +unreproducible
Hi Holger!
On Sat, Mar 16, 2024 at 09:52:54AM +0100, Holger Wansing wrote:
> Package: sphinx-common
> Severity: serious
>
> Hi,
>
> dh_sphinxdoc does not work well with read-the-doc theme, apparently.
> Debian policy document has switched to sphinx_rtd_theme recently (see
> https://salsa.debian.org/dbnpolicy/policy/-/commit/686622814018b5a121252b189d99c1968f332b78
> )
>
> However, the built document has a completely broken html layout, because
> many files under _static/ are empty (0B size), most noteably
> _static/css/theme.css.
>
> If I replace
> dh $@ --with sphinxdoc
> by
> dh $@
> (so do not use dh_sphinxdoc), I get a valid html file with the theme
> in use.
I cannot reproduce this. I downloaded debian-policy source package and built
it in an up-to-date sid chroot. And the built package has this:
$ dpkg-deb -c debian-policy_4.6.2.1_all.deb | grep theme.css
lrwxrwxrwx root/root 0 2024-02-24 15:39
./usr/share/doc/debian-policy/policy.html/_static/css/theme.css ->
../../../../../sphinx_rtd_theme/static/css/theme.css
So, it is a symlink, not an empty file. When resolving the relative path,
I get /usr/share/sphinx_rtd_theme/static/css/theme.css, and that file
exists in sphinx-rtd-theme-common and is non-empty.
The only issue I see is that sphinx-rtd-theme-common is in Recommends of
debian-policy, not in Depends. But that is because ${sphinxdoc:Depends}
was put there.
Am I doing something wrong?
--
Dmitry Shachnev
signature.asc
Description: PGP signature
Bug#1067009: lomiri-ui-toolkit: FTBFS: 63 failures which MUST be fixed
Source: lomiri-ui-toolkit Version: 1.3.5012+dfsg-5 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Control: block 1061179 by -1 Dear Maintainer, As can be seen in [1], the package failed to build on buildds in unstable. The relevant part is: /<>/tests/checkresults.sh /<>/tests/*.xml || exit 1; 63 failures which MUST be fixed: tst_scrollbar.13.qml tst_scrollbar_header.13.qml tst_scrollview.13.qml The reasons why the tests failed can be found by searching for FAIL!. E.g., the first test failed with this error: FAIL! : components::Scrollbar::test_defaultStylingValues(vertical scrollbar) Uncaught exception: Cannot read property 'interactive' of null Loc: [/<>/tests/unit/visual/tst_scrollbar.13.qml(1187)] [1]: https://buildd.debian.org/status/package.php?p=lomiri-ui-toolkit -- Dmitry Shachnev signature.asc Description: PGP signature
Bug#1056419: Spinx help needed
Hi Andreas! On Thu, Feb 15, 2024 at 08:37:38AM +0100, Andreas Tille wrote: > Control: tags -1 pending > > Hi, > > I pushed fixes for #1056419 and #1058311 to Git and I think should be > fixed as well. The only remaining build problem is new and caused by > sphinx[1]: > > dh_sphinxdoc -i -O--buildsystem=pybuild > dh_sphinxdoc: error: > debian/python-lmfit-doc/usr/share/doc/python3-lmfit/html/search.html > top-level node does not have data-content_root attribute > > Unfortunately I have no idea how to fix this. Any ideas? lmfit-py ships a vendored copy of sphinx13 theme [1], which was copied from Sphinx source code with a minor modification in 2020 [2] and rebased in January 2022 [3]. However, there were more Sphinx releases since that month, and the theme needs to be updated for compatibility with them. In particular, the basic_layout.html file misses the change which was made in Sphinx commit [4], without which the search will not work. There is a comment under that commit which illustrates how exactly it will not work: contentRoot will be undefined, and the browser will attempt to make requests to a URL that has "undefined" in it. dh_sphinxdoc catches such issues and produces an error about them. So, to fix this issue, you should copy sphinx/themes/basic/layout.html from the latest stable version of Sphinx to lmfit-py's basic_layout.html, applying the one-line change which is described in [2] and [3]. [1]: doc/sphinx/theme/sphinx13/* [2]: https://github.com/lmfit/lmfit-py/commit/29e4712036606913149e16b246340a7fbedd8829 [3]: https://github.com/lmfit/lmfit-py/commit/e2418377c9870e02c820d0fe40d2232187864a81 [4]: https://github.com/sphinx-doc/sphinx/commit/8e730ae303ae686705ea12f44ef11da926a87cf5 -- Dmitry Shachnev signature.asc Description: PGP signature
Bug#1061206: Please upgrade to llvm-toolchain-17
Hi Sylvestre! On Sat, Jan 20, 2024 at 09:57:51PM +0100, Sylvestre Ledru wrote: > Source: pyside2 > Severity: important > > Dear Maintainer, > > As part of the effort to limit the number of llvm packages in the > archive, it would be great if you could upgrade to -17. > > This package depends on 15. It was not easy, but I backported 9 patches from upstream 6.x branch and added one my patch on top of them, and now pyside2 can build with LLVM 16 and LLVM 17. I did as you suggested and forced build with 17, and uploaded to unstable. However now it dep-waits on mips64el, because llvm-toolchain-17 failed to build there. Should I roll back to the default version (16) for now? Or this will be resolved somehow? I will need rebuilding pyside2 for Qt 5.15.12 transition soon, and if it does not build on mips64el, that will prevent Qt from migrating. -- Dmitry Shachnev signature.asc Description: PGP signature
Bug#1061206: marked as pending in pyside2
Control: tag -1 pending Hello, Bug #1061206 in pyside2 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/qt-kde-team/qt/pyside2/-/commit/b76b5131541ceaae7b058ed5da99e64fa875d2c3 Build with llvm-toolchain-17. Closes: #1061206. (this message was generated automatically) -- Greetings https://bugs.debian.org/1061206
Bug#1060802: stellarium: FTBFS on armel, ppc64el, s390x: unsatisfiable Build-Depends: qtwebengine5-dev (>= 5.15)
Hi James! On Wed, Jan 31, 2024 at 11:57:52PM +, James Addison wrote: > Source: stellarium > Followup-For: Bug #1060802 > X-Debbugs-Cc: tom...@debian.org, mity...@debian.org > > > stellarium 23.4-1 added a new build-dependency on qtwebengine5-dev, which > > prevents it from building on some release architectures (and all non-release > > ones). > > Would 'qtwebengine5-dev | libqt5webkit5-dev' provide an acceptable alternative > build dependency spec? > > Ref: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913043;msg=10 Qt WebEngine and (deprecated) Qt WebKit are not compatible with each other, they provide different sets of classes. And it looks like upstream stellarium only supports Qt WebEngine, not WebKit. Good news is that Qt WebEngine support is optional and you can just build without it on architectures where it's not available. This can be achieved by limiting the build-dependency: qtwebengine5-dev (>= 5.15) [amd64 arm64 armhf i386 mips64el], I did that in Ubuntu [1] and the package built on all Ubuntu's architectures. [1]: https://launchpad.net/ubuntu/+source/stellarium/23.4-1ubuntu1 -- Dmitry Shachnev signature.asc Description: PGP signature
Bug#1060802: stellarium: FTBFS on armel, ppc64el, s390x: unsatisfiable Build-Depends: qtwebengine5-dev (>= 5.15)
Source: stellarium Version: 23.4-1 Severity: serious Justification: fails to build from source (but built successfully in the past) Tags: ftbfs Dear Maintainer, stellarium 23.4-1 added a new build-dependency on qtwebengine5-dev, which prevents it from building on some release architectures (and all non-release ones). Upstream mentions [1] that Qt WebEngine build-dependency is optional and can be either detected automatically by the build system, or configured explicitly using -DENABLE_QTWEBENGINE=ON/OFF [2]. Qt WebEngine is available only amd64, arm64, armhf, i386 and mips64el, and it's unlikely that this set of architectures will be changed for Qt 5. So you can limit the build-dependency to these architectures. [1]: https://github.com/Stellarium/stellarium/blob/master/BUILDING.md#linux-without-qtwebengine [2]: https://github.com/Stellarium/stellarium/blob/master/BUILDING.md#supported-cmake-parameters -- Dmitry Shachnev signature.asc Description: PGP signature
Bug#1058371: python-cloup: FTBFS: make[1]: *** [Makefile:20: html] Error 2
Control: reassign -1 python3-astroid 2.15.6-1 Control: retitle -1 python3-astroid: incompatible with Python 3.12 (exception: 'TreeRebuilder' object has no attribute 'visit_typealias') Control: affects -1 + src:python-cloup src:sphinx-autoapi Control: block 1056529 1058408 by -1 Control: tags -1 + fixed-upstream Hi all, On Tue, Dec 12, 2023 at 09:27:12AM +0100, Lucas Nussbaum wrote: > Source: python-cloup > Version: 3.0.3-1 > Severity: serious > Justification: FTBFS > Tags: trixie sid ftbfs > User: lu...@debian.org > Usertags: ftbfs-20231212 ftbfs-trixie > > Hi, > > During a rebuild of all packages in sid, your package failed to build > on amd64. > > Relevant part (hopefully): > > make[1]: Entering directory '/<>/docs' > > Running Sphinx v7.2.6 > > making output directory... done > > /usr/lib/python3/dist-packages/autoapi/extension.py:137: > > RemovedInSphinx80Warning: Sphinx 8 will drop support for representing paths > > as strings. Use "pathlib.Path" or "os.fspath" instead. > > elif app.srcdir != os.getcwd(): > > /usr/lib/python3/dist-packages/autoapi/mappers/python/mapper.py:300: > > RemovedInSphinx80Warning: The alias 'sphinx.util.status_iterator' is > > deprecated, use 'sphinx.util.display.status_iterator' instead. Check > > CHANGES for Sphinx API modifications. > > for dir_root, path in sphinx.util.status_iterator( > > [2K[AutoAPI] Reading files... [ 4%] /<>/cloup/__init__.py > > [2K[AutoAPI] Reading files... [ 9%] /<>/cloup/_util.py > > [2K[AutoAPI] Reading files... [ 13%] /<>/cloup/_sections.py > > [2K[AutoAPI] Reading files... [ 17%] /<>/cloup/_commands.py > > > > Extension error (autoapi.extension): > > Handler for event 'builder-inited' > > threw an exception (exception: 'TreeRebuilder' object has no attribute > > 'visit_typealias') > > make[1]: *** [Makefile:20: html] Error 2 This is actually caused by astroid 2.15 being incompatible with Python 3.12. In upstream it was fixed in commit [1], which is part of a larger PR [2] that adds support for Python 3.12. These changes were included in astroid 3.0, so updating to that release should fix the problem. [1]: https://github.com/pylint-dev/astroid/commit/6d4f364a08289bf3 [2]: https://github.com/pylint-dev/astroid/pull/2219 -- Dmitry Shachnev signature.asc Description: PGP signature
Bug#1059648: sip4: autopkgtest failure with Python 3.12
On Sun, Jan 07, 2024 at 06:34:24PM +0300, Dmitry Shachnev wrote: > krita and pyqwt3d have open bugs to move to sip6, but I will need to file > bugs for the other packages too. All the missing bugs are filed now: https://bugs.debian.org/cgi-bin/pkgreport.cgi?users=mity...@debian.org;tag=sip6 -- Dmitry Shachnev signature.asc Description: PGP signature
Bug#1059648: sip4: autopkgtest failure with Python 3.12
Hi Gregor! On Sun, Jan 07, 2024 at 03:40:49PM +0100, Gregor Riepl wrote: > I can reproduce that, although I should mention that the segfault happens > during teardown, not when the module is loaded: > > >>> import sip > >>> print(sip) > '/usr/lib/python3/dist-packages/sip.cpython-312-x86_64-linux-gnu.so'> > >>> > > Program received signal SIGSEGV, Segmentation fault. > 0x00513a8d in PyMem_Free () > (gdb) bt > #0 0x00513a8d in PyMem_Free () > #1 0x7f73de6feaf9 in sip_api_free (mem=) at > ./siplib/siplib.c:2241 > #2 0x7f73de710c6d in sipOMFinalise (om=) at > ./siplib/objmap.c:69 > #3 0x7f73de6febaf in finalise () at ./siplib/siplib.c:2143 > #4 0x004591ab in ?? () > #5 0x00662d77 in Py_RunMain () > #6 0x006232eb in Py_BytesMain () > #7 0x7f73deba66ca in __libc_start_call_main (main=main@entry=0x623240, > argc=argc@entry=1, argv=argv@entry=0x7ffd043a59b8) at > ../sysdeps/nptl/libc_start_call_main.h:58 > #8 0x7f73deba6785 in __libc_start_main_impl (main=0x623240, argc=1, > argv=0x7ffd043a59b8, init=, fini=, > rtld_fini=, stack_end=0x7ffd043a59a8) > at ../csu/libc-start.c:360 > #9 0x00623171 in _start () Yes, I saw the same. In SIP 6, there were 3 commits to add support for Python 3.12, but the code diverged a lot so it's not trivial to backport them to SIP 4. > I'd also like to point out that SIP4 is no longer supported upstream. The > current version is 6.8.1, which is already packaged for Debian. > https://www.riverbankcomputing.com/software/sip/download > > > SIP v4 is no longer supported. This is the last release. > > sip-4.19.25.tar.gz > > Cura was made fit for PyQt6 and SIP6 in April 2022, and I think 5.0 has all > the needed changes. I will investigate if we can drop the dependency on > python3-sip-dev. As far as I can see, there are no other users of SIP4 in > Debian, so maybe it can be dropped completely after fixing Cura. Unfortunately there are other users: $ reverse-depends src:sip4 -r sid Reverse-Recommends == * krita [amd64 arm64 armel armhf i386 mips64el ppc64el s390x] Reverse-Depends === * gnuradio [amd64 arm64 armel armhf i386 mips64el ppc64el s390x] * meteo-qt [amd64 arm64 armel armhf i386 mips64el ppc64el s390x] * python3-pykdl [amd64 arm64 armel armhf i386 mips64el ppc64el s390x] * python3-python-qt-binding (for python3-sip-dev) * python3-python-qt-binding (for sip-dev) * qutebrowser (for python3-sip) * tulip [amd64 arm64 i386 mips64el ppc64el s390x] * vistrails (for python3-sip) $ reverse-depends -b src:sip4 -r sid Reverse-Testsuite-Triggers == * geophar (for python3-sip) Reverse-Build-Depends = * ball (for python3-sip-dev) * geophar (for python3-sip) * guidata (for python3-sip) * krita (for python3-sip-dev) * libarcus (for python3-sip-dev) * libsavitar(for python3-sip-dev) * openstructure (for sip-dev) * orocos-kdl(for python3-sip-dev) * pynest2d (for python3-sip-dev) * pyqwt3d (for python3-sip-dev) * stimfit (for python3-sip-dev) * tulip (for python3-sip-dev) Reverse-Build-Depends-Indep === * eric (for python3-sip-dev) krita and pyqwt3d have open bugs to move to sip6, but I will need to file bugs for the other packages too. -- Dmitry Shachnev signature.asc Description: PGP signature
Bug#1059661: marked as pending in python-changelog
Control: tag -1 pending Hello, Bug #1059661 in python-changelog 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-changelog/-/commit/56e0707bb663442e2d444ca9464b82ef21e4a4e1 Add run-time dependency on python3-setuptools. Closes: #1059661. (this message was generated automatically) -- Greetings https://bugs.debian.org/1059661
Bug#1058303: marked as pending in sphinx
Control: tag -1 pending Hello, Bug #1058303 in sphinx reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/packages/sphinx/-/commit/e4aef09c658bd7d3a7fd2eb5b72067526ac2774d Add a patch to fix build with Python 3.11.7+. Thanks Hugo van Kemenade for the upstream pull request! Closes: #1058303. (this message was generated automatically) -- Greetings https://bugs.debian.org/1058303
Bug#1058446: marked as pending in sphinxcontrib-jquery
Control: tag -1 pending Hello, Bug #1058446 in sphinxcontrib-jquery 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/sphinxcontrib-jquery/-/commit/19d8a31a638270ee454af2384fde15f64aaec1cd Update sphinx_7.2.patch to stop monkey-patching _StrPath. To make the tests pass with Python 3.12. Closes: #1058446. (this message was generated automatically) -- Greetings https://bugs.debian.org/1058446
Bug#1057357: marked as pending in qtremoteobjects-everywhere-src
Control: tag -1 pending Hello, Bug #1057357 in qtremoteobjects-everywhere-src 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/qt-kde-team/qt/qtremoteobjects/-/commit/882ef0c6c964fc2fec6162b6ddfb4a488a7b10bc Regenerate the test certificates with a longer validity period. Thanks Santiago Vila! Closes: #1057357. (this message was generated automatically) -- Greetings https://bugs.debian.org/1057357
Bug#1057674: marked as pending in pyqt6
Control: tag -1 pending Hello, Bug #1057674 in pyqt6 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/pyqt6/-/commit/562b433605800d0943609ac58fbb87f7419a49d9 Do not use dh_python3 on examples. Closes: #1057674. (this message was generated automatically) -- Greetings https://bugs.debian.org/1057674
Bug#1057357: qtremoteobjects-everywhere-src: FTBFS in bullseye and bookworm because of expired SSL certificates, will also FTBFS in trixie/sid eventually
Hi Santiago! On Sun, Dec 03, 2023 at 11:23:07PM +0100, Santiago Vila wrote: > [...] > > I'm attaching two patches to fix this. > > The first one modifies the script > tests/auto/external_IODevice/cert/generate.sh > so that certificates expire in ten years. > > The second patch is merely the result of running the script. Generally, we try to avoid including patches which have not been applied upstream. And upstream has solved this problem by simply regenerating the patches with the old configuration [1]. So I have forwarded your first patch to upstream [2] to give them chance to review it. If it's approved/merged, I will submit your second patch to regenerate the certificates again (I hope you don't mind). If there is no response from upstream, I will go ahead and make uploads with both patches in a week. [1]: https://code.qt.io/cgit/qt/qtremoteobjects.git/commit/?id=ac3b93c886c04bc1 [2]: https://codereview.qt-project.org/c/qt/qtremoteobjects/+/522923 -- Dmitry Shachnev signature.asc Description: PGP signature
Bug#1042609: sphinxcontrib-mermaid: FTBFS with Sphinx 7.1, docutils 0.20: Could not import sphinx.util.SphinxParallelError (exception: No module named 'sphinx.util.SphinxParallelError')
Hi Faidon! On Mon, Nov 13, 2023 at 10:52:58AM +0200, Faidon Liambotis wrote: > Upstream commit 6f8de39¹, the only commit since 0.9.2, replaces > sphinx.util.SphinxParallelError by sphinx.util.DownloadFiles. > > I've verified that backporting this commit makes the package build > successfully in unstable, with Sphinx 7.2.6-2. > > However, the very same commit changes requirements.txt from > "Sphinx>=3.2.1" to "Sphinx<7". > > I'm not sure why. I'm not using, nor am I familiar with this plugin, so > I was hoping someone else that is could perhaps validate whether besides > being able to be built, the package actually works. > > 1: > https://github.com/mgaitan/sphinxcontrib-mermaid/commit/6f8de39a84fddc398542e9d4dc74ba55101e7d5e The SphinxParallelError class is defined in sphinx.errors module. It was available in sphinx.util because that module happened to import it from sphinx.errors, but that is no longer the case since Sphinx 6.1. Probably the author of the linked commit was testing with Sphinx 6.1 (or 6.2), but had different problems with early Sphinx 7 versions (only Sphinx 7.0.1 was available at that moment), so changed the dependency to <7. The change in README.rst looks trivial, so if it helps, I would go ahead and cherry-pick it to our packaging without the requirements.txt change. -- Dmitry Shachnev signature.asc Description: PGP signature
Bug#1042624: marked as pending in factory-boy
Control: tag -1 pending Hello, Bug #1042624 in factory-boy 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/factory-boy/-/commit/7fc4fca92d92e8956c012a16f457fa58b4647e56 Backport upstream patch to fix extlinks placeholder. Closes: #1042624. (this message was generated automatically) -- Greetings https://bugs.debian.org/1042624
Bug#1042602: marked as pending in sphinx-panels
Control: tag -1 pending Hello, Bug #1042602 in sphinx-panels reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/packages/sphinx-panels/-/commit/1f3d878102410405119f5633b807b16f39060282 Add a patch to make the tests pass with Sphinx 7. Closes: #1042602. (this message was generated automatically) -- Greetings https://bugs.debian.org/1042602
Bug#1042668: Package builds fine
Control: tags -1 + patch Hi Thomas! On Mon, Oct 30, 2023 at 04:27:51PM +0100, Thomas Goirand wrote: > Tried rebuilding and it works. Closing... In fact, this package still FTBFS with new Sphinx. Backporting upstream commit [1] helps. I have created a merge request in salsa [2] to do that. I think ideally this bug should be re-opened and then closed from the changelog, but as you explicitly asked to not re-open bugs [3], I am not doing that. [1]: https://opendev.org/openstack/pbr/commit/47c5afe79aa334b3 [2]: https://salsa.debian.org/openstack-team/libs/python-pbr/-/merge_requests/4 [3]: https://lists.debian.org/debian-python/2023/10/msg00059.html -- Dmitry Shachnev signature.asc Description: PGP signature
Bug#1043075: Package builds fine
Hi Thomas! On Mon, Oct 30, 2023 at 04:35:22PM +0100, Thomas Goirand wrote: > I tried rebuilding, and it works. Closing this bug. This bug was not about python-openstackdocstheme itself failing to build, but about its reverse dependencies. As I mentioned in the bug description, during the test rebuild against new Sphinx, 104 packages failed to build with "dh_sphinxdoc: error: .../_static/underscore.js is missing" error [1]. This error is caused by outdated python3-openstackdocstheme. Please reopen this bug and upgrade to version 3.2.0, which will fix this. [1]: http://qa-logs.debian.net/2023/07/30/diff.txt -- Dmitry Shachnev signature.asc Description: PGP signature
Bug#1054685: marked as pending in sphinx-rtd-theme
Control: tag -1 pending Hello, Bug #1054685 in sphinx-rtd-theme reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/packages/sphinx-rtd-theme/-/commit/0bd15ff46b20bd670b5cc23c3db57ea79cabca76 Add a patch to support strings in css_files. Closes: #1054685. (this message was generated automatically) -- Greetings https://bugs.debian.org/1054685
Bug#1051886: marked as pending in pyside2
Control: tag -1 pending Hello, Bug #1051886 in pyside2 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/qt-kde-team/qt/pyside2/-/commit/a8638ccd6c5fd8c71b2777f1eeffb8e004f42d67 Build with LLVM 15 for now. Closes: #1051886. (this message was generated automatically) -- Greetings https://bugs.debian.org/1051886
Bug#1052759: qtremoteobjects-everywhere-src: FTBFS: qcontainerfwd.h:63:7: error: typedef redefinition with different types ('QList' vs 'QByteArrayList')
Control: retitle -1 qtremoteobjects-everywhere-src: FTBFS:
tst_usertypes::extraPropertyInQml2() fails
Control: severity -1 important
Control: tags -1 + unreproducible
Hi Lucas!
On Tue, Sep 26, 2023 at 02:38:35PM +0200, Lucas Nussbaum wrote:
> Source: qtremoteobjects-everywhere-src
> Version: 5.15.10-2
> Severity: serious
> Justification: FTBFS
> Tags: trixie sid ftbfs
> User: lu...@debian.org
> Usertags: ftbfs-20230925 ftbfs-trixie
>
> Hi,
>
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
I have just built this package successfully two times in my sid chroot.
Also, it builds successfully in the reproducible builds environment [1].
[1]:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/qtremoteobjects-everywhere-src.html
> Relevant part (hopefully):
> > make[6]: Entering directory '/<>/src/remoteobjects'
> > /usr/lib/qt5/bin/qtattributionsscanner /<> --filter
> > QDocModule=qtremoteobjects -o
> > /<>/src/remoteobjects/codeattributions.qdoc
> > /<>/src/remoteobjects/qdoc_wrapper.sh -outputdir
> > /<>/doc/qtremoteobjects -installdir /usr/share/qt5/doc
> > /<>/src/remoteobjects/doc/qtremoteobjects.qdocconf -prepare
> > -indexdir /usr/share/qt5/doc -no-link-errors -I. -I../../include
> > -I../../include/QtRemoteObjects -I../../include/QtRemoteObjects/5.15.10
> > -I../../include/QtRemoteObjects/5.15.10/QtRemoteObjects -I.
> > -I/usr/include/x86_64-linux-gnu/qt5
> > -I/usr/include/x86_64-linux-gnu/qt5/QtNetwork
> > -I/usr/include/x86_64-linux-gnu/qt5/QtCore/5.15.10
> > -I/usr/include/x86_64-linux-gnu/qt5/QtCore/5.15.10/QtCore
> > -I/usr/include/x86_64-linux-gnu/qt5/QtCore -I.moc
> > -I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -I/usr/include/c++/13
> > -I/usr/include/x86_64-linux-gnu/c++/13 -I/usr/include/c++/13/backward
> > -I/usr/lib/gcc/x86_64-linux-gnu/13/include -I/usr/local/include
> > -I/usr/include/x86_64-linux-gnu -I/usr/include
> > qt.qdoc: Start qdoc for QtRemoteObjects in dual process mode: prepare phase.
> > /usr/include/x86_64-linux-gnu/qt5/QtCore/qcontainerfwd.h:63:7: error:
> > typedef redefinition with different types ('QList' vs
> > 'QByteArrayList')
No, this is an error when generating documentation, but it does not make the
build fail.
The really relevant part is this one:
> > * Start testing of tst_usertypes *
> > Config: Using QtTest library 5.15.10, Qt 5.15.10 (x86_64-little_endian-lp64
> > shared (dynamic) release build; by GCC 13.1.0), debian unknown
> > PASS : tst_usertypes::initTestCase()
> > PASS : tst_usertypes::extraPropertyInQml()
> > QSYSTEM: tst_usertypes::extraPropertyInQml2() qt.remoteobjects: Listen
> > failed for URL: QUrl("local:test2")
> > QSYSTEM: tst_usertypes::extraPropertyInQml2() qt.remoteobjects:
> > QAbstractSocket::AddressInUseError
> > FAIL! : tst_usertypes::extraPropertyInQml2() Compared values are not the
> > same
> >Actual ((obj->property("hour").value())): 6
> >Expected (10) : 10
> >Loc: [tst_usertypes.cpp(106)]
Maybe this test is flaky, but as I said, it works for me.
Can you reproduce this error? Maybe there is some difference between our
setups that makes it fail?
--
Dmitry Shachnev
signature.asc
Description: PGP signature
Bug#1052779: marked as pending in sphinxcontrib-websupport
Control: tag -1 pending Hello, Bug #1052779 in sphinxcontrib-websupport 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/sphinxcontrib-websupport/-/commit/58679f53f6406fe2a69332b6da4527221c316177 Add a patch to fix test failures. Closes: #1052779. (this message was generated automatically) -- Greetings https://bugs.debian.org/1052779
Bug#1052802: marked as pending in nose
Control: tag -1 pending Hello, Bug #1052802 in nose 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/nose/-/commit/63ce6f791e235910342152b469cf66c717e92842 Disable pybuild’s clean, it deletes test .egg-info directories. Rely on debian/clean instead. Closes: #1052802. (this message was generated automatically) -- Greetings https://bugs.debian.org/1052802
Bug#1051883: marked as pending in qttools-opensource-src
Hi Sebastian! On Sun, Sep 17, 2023 at 08:14:44PM +0200, Sebastian Ramacher wrote: > Control: reopen -1 > > On 2023-09-17 14:13:08 +0000, Dmitry Shachnev wrote: > > Control: tag -1 pending > > > > Hello, > > > > Bug #1051883 in qttools-opensource-src 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/qt-kde-team/qt/qttools/-/commit/c29ff951dc40dd804542a6dbbb9a32854e3087d8 > > > > > > Build with LLVM 15 for now. > > > > Closes: #1051883. > > The build fails with llvm-toolchain-15 in the same way. Looks like llvm > is not the cause of the FTBFS. No, it fails not in the same way. With llvm-toolchain-16 the failed tests were qdoc tests: tst_generatedOutput::webXmlFromCpp() and tst_generatedOutput::preparePhase(), which are directly related to LLVM (qdoc uses it to parse C++ code). I spent some time searching for an upstream fix, but with no luck (upstream does not support 5.15 branch officially anymore, and with 6.4.2 I get different failures in this test). Now, these two tests passed, but tst_QHelpEngineCore::setCollectionFile() failed, which is something new (it did not fail in my local build). I will investigate. -- Dmitry Shachnev signature.asc Description: PGP signature
Bug#1051883: marked as pending in qttools-opensource-src
Control: tag -1 pending Hello, Bug #1051883 in qttools-opensource-src 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/qt-kde-team/qt/qttools/-/commit/c29ff951dc40dd804542a6dbbb9a32854e3087d8 Build with LLVM 15 for now. Closes: #1051883. (this message was generated automatically) -- Greetings https://bugs.debian.org/1051883
Bug#1051886: marked as pending in qtbase-opensource-src
Control: tag -1 pending Hello, Bug #1051886 in qtbase-opensource-src 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/qt-kde-team/qt/qtbase/-/commit/830c9dcdde8b1ed0463bd4368a2ac60610fc34ae Add a patch from OpenMandriva to work around broken pyside2 build. Closes: #1051886. (this message was generated automatically) -- Greetings https://bugs.debian.org/1051886
Bug#1037827: marked as pending in qscintilla2
Control: tag -1 pending Hello, Bug #1037827 in qscintilla2 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/qscintilla2/-/commit/91e16749c09fbd2a0e8d70ba8b2263ba756d0ac3 Update symbols files for GCC 13. Closes: #1037827. (this message was generated automatically) -- Greetings https://bugs.debian.org/1037827
Bug#1041250: Insufficient RAM?
Hi Soren! On Mon, Jul 17, 2023 at 08:40:14AM -0700, Soren Stoutner wrote: > Am I reading that error message correctly that it is failing to build from > source simply because the build machine doesn’t have enough RAM? No, we are limited not by physical RAM, but by address space which is just 2 GB on mipsel. See https://wiki.debian.org/MIPSPort#Generic_issues. However, as the latest version built fine on a porter box, I retried the last build on buildd. -- Dmitry Shachnev signature.asc Description: PGP signature
Bug#1038402: openorienteering-mapper: FTBFS with Qt ≥ 5.15.9: QPainterTest failures
Control: tags -1 +pending
Hi,
On Sat, Jun 17, 2023 at 09:24:07PM +0300, Dmitry Shachnev wrote:
> Dear Maintainer,
>
> openorienteering-mapper fails to build with Qt ≥ 5.15.9, which is currently
> available in experimental (but I am going to upload it to unstable soon).
>
> [...]
>
> I have created an upstream pull request that fixes this issue, see the
> Forwarded URL.
As Qt 5.15.10 is in unstable now and this package needs to be rebuilt against
the new private ABI, I have uploaded NMU to DELAYED/2.
The debdiff is attached. Also created a merge request on salsa:
https://salsa.debian.org/debian/openorienteering-mapper/-/merge_requests/2
--
Dmitry Shachnev
diff -Nru openorienteering-mapper-0.9.5/debian/changelog openorienteering-mapper-0.9.5/debian/changelog
--- openorienteering-mapper-0.9.5/debian/changelog 2021-12-28 12:45:41.0 +0300
+++ openorienteering-mapper-0.9.5/debian/changelog 2023-07-09 23:48:02.0 +0300
@@ -1,3 +1,11 @@
+openorienteering-mapper (0.9.5-3.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Add a patch to make the QPainterTest pass with Qt 5.15.9
+(closes: #1038402).
+
+ -- Dmitry Shachnev Sun, 09 Jul 2023 23:48:02 +0300
+
openorienteering-mapper (0.9.5-3) unstable; urgency=medium
* Cherry-pick upstream commit updating expected
diff -Nru openorienteering-mapper-0.9.5/debian/patches/qt-5.15.9.patch openorienteering-mapper-0.9.5/debian/patches/qt-5.15.9.patch
--- openorienteering-mapper-0.9.5/debian/patches/qt-5.15.9.patch 1970-01-01 03:00:00.0 +0300
+++ openorienteering-mapper-0.9.5/debian/patches/qt-5.15.9.patch 2023-07-09 23:48:02.0 +0300
@@ -0,0 +1,60 @@
+Description: make QPainterTest pass with Qt 5.15.9
+ https://bugreports.qt.io/browse/QTBUG-100327 was fixed in 5.15.9,
+ so now we have a good result from the beginning and don't need
+ ImageTransparencyFixup.
+Author: Dmitry Shachnev
+Forwarded: https://github.com/OpenOrienteering/mapper/pull/2156
+Last-Update: 2023-07-09
+
+--- a/src/core/image_transparency_fixup.h
b/src/core/image_transparency_fixup.h
+@@ -57,6 +57,9 @@ public:
+ *
+ * The image must be of QImage::Format_ARGB32_Premultiplied.
+ * It may be null.
++ *
++ * This fixup is needed for Qt5 < 5.15.9 and Qt6 < 6.2.4 which are
++ * affected by https://bugreports.qt.io/browse/QTBUG-100327.
+ */
+ inline ImageTransparencyFixup(QImage* image)
+ : dest(0), dest_end(0)
+@@ -81,11 +84,13 @@ public:
+ */
+ inline void operator()() const
+ {
++#if QT_VERSION < QT_VERSION_CHECK(5, 15, 9) || (QT_VERSION >= QT_VERSION_CHECK(6, 0, 0) && QT_VERSION < QT_VERSION_CHECK(6, 2, 4))
+ for (QRgb* px = dest; px < dest_end; px++)
+ {
+ if (*px == 0x0100) /* qRgba(0, 0, 0, 1) */
+ *px = 0x; /* qRgba(0, 0, 0, 0) */
+ }
++#endif
+ }
+
+ protected:
+--- a/test/qpainter_t.cpp
b/test/qpainter_t.cpp
+@@ -80,9 +80,10 @@ void QPainterTest::multiplyComposition()
+ QCOMPARE(compose(white_img, white_img, multiply).pixel(0,0), qRgba(255, 255, 255, 255));
+ QCOMPARE(compose(black_img, black_img, multiply).pixel(0,0), qRgba(0, 0, 0, 255));
+
++#if QT_VERSION < QT_VERSION_CHECK(5, 15, 9) || (QT_VERSION >= QT_VERSION_CHECK(6, 0, 0) && QT_VERSION < QT_VERSION_CHECK(6, 2, 4))
+ QEXPECT_FAIL("", "CompositionMode_Multiply incorrectly composes full transparency.", Continue);
++#endif
+ QCOMPARE(compose(trans_img, trans_img, multiply).pixel(0,0), qRgba(0, 0, 0, 0));
+- QCOMPARE(compose(trans_img, trans_img, multiply).pixel(0,0), qRgba(0, 0, 0, 1)); // This should fail!
+
+ // ImageTransparencyFixup fixes the particular issue.
+ QImage result = compose(trans_img, trans_img, multiply);
+@@ -107,9 +108,10 @@ void QPainterTest::darkenComposition()
+ QCOMPARE(compose(white_img, white_img, darken).pixel(0,0), qRgba(255, 255, 255, 255));
+ QCOMPARE(compose(black_img, black_img, darken).pixel(0,0), qRgba(0, 0, 0, 255));
+
++#if QT_VERSION < QT_VERSION_CHECK(5, 15, 9) || (QT_VERSION >= QT_VERSION_CHECK(6, 0, 0) && QT_VERSION < QT_VERSION_CHECK(6, 2, 4))
+ QEXPECT_FAIL("", "CompositionMode_Darken incorrectly composes full transparency.", Continue);
++#endif
+ QCOMPARE(compose(trans_img, trans_img, darken).pixel(0,0), qRgba(0, 0, 0, 0));
+- QCOMPARE(compose(trans_img, trans_img, darken).pixel(0,0), qRgba(0, 0, 0, 1)); // This should fail!
+
+ // ImageTransparencyFixup fixes the particular issue.
+ QImage result = compose(trans_img, trans_img, darken);
diff -Nru openorienteering-mapper-0.9.5/debian/patches/series openorienteering-mapper-0.9.5/debian/patches/series
--- openorienteering-mapper-0.9.5/debian/patches/series 2021-12-28 12:06:01.0 +0300
+++ openorienteering-mapper-0.9.5/debian/patches/series 2023-07-09 23:48:02.0 +0300
@@ -1,3 +1,4 @@
fix-help-data-dir.patch
proj8.patch
proj8.2.0.patch
+qt-5.15.9.patch
signature.asc
Description: PGP signature
Bug#1038737: FTBFS on mips64el: Unable to import PyChromecast
Hi Adrian! On Wed, Jun 21, 2023 at 12:25:53PM +0300, Adrian Bunk wrote: > python3-pychromecast is also an unconditional runtime dependency, > so building on an architecture without it would anyway be pointless > (and for release architectures break testing migration). > > Trying on the porterbox for mips64el, I think the original problem was > just a timeout in the cmake "import pychromecast" test, the patch below > works for me. Indeed, your patch is the proper fix. Thank you! -- Dmitry Shachnev signature.asc Description: PGP signature
Bug#1038703: dtkcore: FTBFS: /usr/include/gtest/internal/gtest-port.h:270:2: error: #error C++ versions less than C++14 are not supported
Control: tags -1 + patch
On Tue, Jun 20, 2023 at 12:52:53PM +0300, Dmitry Shachnev wrote:
> [...]
>
> googletest 1.13 was uploaded to unstable recently, and it dropped support
> for C++ versions less than C++14:
>
> https://github.com/google/googletest/releases/tag/v1.13.0
>
> But dtkcore sets CONFIG += c++11 in its .pro files.
Attaching a patch that fixes the build failure.
--
Dmitry Shachnev
Description: don't force old C++ version for tests
Author: Dmitry Shachnev
Forwarded: no
Last-Update: 2023-06-20
--- a/tests/ddesktopentry/ddesktopentry.pro
+++ b/tests/ddesktopentry/ddesktopentry.pro
@@ -3,7 +3,6 @@ QT -= gui
TARGET = tst_ddesktopentrytest
TEMPLATE = app
-CONFIG += c++11
CONFIG -= app_bundle
!isEmpty(DTK_STATIC_LIB){
--- a/tests/dthreadutils/dthreadutils.pro
+++ b/tests/dthreadutils/dthreadutils.pro
@@ -2,7 +2,6 @@ QT += testlib concurrent
QT -= gui
TEMPLATE = app
-CONFIG += c++11
!isEmpty(DTK_STATIC_LIB){
DEFINES += DTK_STATIC_LIB
--- a/tests/dutils/dutils.pro
+++ b/tests/dutils/dutils.pro
@@ -2,7 +2,6 @@ QT += testlib dbus
QT -= gui
TEMPLATE = app
-CONFIG += c++11
!isEmpty(DTK_STATIC_LIB){
DEFINES += DTK_STATIC_LIB
--- a/tests/dvtablehook/dvtablehook.pro
+++ b/tests/dvtablehook/dvtablehook.pro
@@ -2,7 +2,6 @@ QT += testlib
QT -= gui
TEMPLATE = app
-CONFIG += c++11
# TODO: vtabhook release test failed
QMAKE_CXXFLAGS_RELEASE -= -O2
--- a/tests/tests.pro
+++ b/tests/tests.pro
@@ -1,6 +1,6 @@
TEMPLATE = app
QT += core dbus xml testlib concurrent
-CONFIG += thread c++11 link_pkgconfig
+CONFIG += thread link_pkgconfig
CONFIG -= app_bundle
QMAKE_LFLAGS += -Wl,--export-dynamic
signature.asc
Description: PGP signature
Bug#1038737: FTBFS on mips64el: Unable to import PyChromecast
Source: photoqt Version: 3.3+ds-1 Severity: serious Tags: ftbfs patch Justification: fails to build from source (but built successfully in the past) Dear Maintainer, The latest photoqt upload failed to build on mips64el, m68k and riscv64. mips64el is a release architecture, this I set severity to serious. The error is: Traceback (most recent call last): File "", line 1, in ModuleNotFoundError: No module named 'pychromecast' CMake Error at CMakeLists.txt:386 (message): ** Unable to import PyChromecast, make sure it is installed. Enabling the CHROMECAST_PIPINSTALL option allows CMake to try to install it locally using pip. -- Configuring incomplete, errors occurred! I have attached a patch which should fix this problem. At least it seems to do so on riscv64. Also, I think with my change you can drop disable-pychromecast patch which is currently commented out anyway. -- Dmitry Shachnev --- photoqt-3.3+ds/debian/rules +++ photoqt-3.3+ds/debian/rules @@ -13,10 +13,7 @@ ifeq ($(DEB_BUILD_ARCH_OS),kfreebsd) MAGICK = -DGRAPHICSMAGICK=OFF -DIMAGEMAGICK=OFF endif -ifeq ($(DEB_BUILD_ARCH_OS),ia64) -CHROMECAST = -DCHROMECAST=OFF -endif -ifeq ($(DEB_BUILD_ARCH_OS),x86_64) +ifneq (,$(filter $(DEB_BUILD_ARCH),ia64 kfreebsd-amd64 kfreebsd-i386 sparc64 sh4 riscv64 m68k hppa mips64el)) CHROMECAST = -DCHROMECAST=OFF endif ifeq ($(DEB_BUILD_ARCH_OS),hppa) signature.asc Description: PGP signature
Bug#1038132: qtwebengine-opensource-src: FTBFS: ../../3rdparty/chromium/third_party/ffmpeg/libavcodec/x86/mathops.h:125: Error: operand type mismatch for `shr'
On Mon, Jun 19, 2023 at 01:24:50PM -0700, Gerardo Esteban Malazdrewicz wrote: > Please apply ffmpeg-remove-x86-optimization.patch to qtwebengine-opensource- > src-5.15.14 Done: https://tracker.debian.org/news/1436528/accepted-qtwebengine-opensource-src-51514dfsg-3-source-into-experimental/ -- Dmitry Shachnev signature.asc Description: PGP signature
Bug#1017144: gammaray: FTBFS: test failed
Control: severity -1 important On Sun, Aug 14, 2022 at 09:13:36AM +0200, Lucas Nussbaum wrote: > Source: gammaray > Version: 2.11.3-1 > Severity: serious > Justification: FTBFS > Tags: bookworm sid ftbfs > User: lu...@debian.org > Usertags: ftbfs-20220813 ftbfs-bookworm > > Hi, > > During a rebuild of all packages in sid, your package failed to build > on amd64. > > Relevant part (hopefully): > > Start 2: connectiontest-preload-filter > > > [...] > > Injector error: Process crashed I acknowledge that a few tests are flaky, but it does not mean that this package fails to build completely. Since this bug was filed on 2022-08-14, it built successfully on amd64 buildds on 2022-10-01, 2022-12-21, 2022-12-24, 2023-01-15 and 2023-03-02. Downgrading severity to important so it doesn't block bookworm release. -- Dmitry Shachnev signature.asc Description: PGP signature
Bug#1033667: verilator: Uninstallable in sid because of ${sphinxdoc:Built-Using} dependency
Package: verilator
Version: 5.006-2
Severity: serious
Tags: patch
Dear Maintainer,
In a clean sid chroot, verilator is not installable:
# apt install verilator
Reading package lists... Done
Building dependency tree... Done
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:
verilator : Depends: sphinx (= 5.3.0-3)
E: Unable to correct problems, you have held broken packages.
This is because that package has ${sphinxdoc:Built-Using} among its
dependencies.
That substitution variable is intended to be used in Built-Using field of
architecture-dependent packages, NOT in Depends field.
I have created a merge request [1] on salsa to fix this.
[1]: https://salsa.debian.org/electronics-team/verilator/-/merge_requests/3
--
Dmitry Shachnev
signature.asc
Description: PGP signature
Bug#1026514: python-param: FTBFS: TypeError: The only supported seed types are: None,
On Fri, Feb 03, 2023 at 06:45:56PM +0100, FC Stegerman wrote:
> Thanks!
>
> Updating my previous suggestion based on this new information, it
> becomes:
>
> adding this to debian/rules
>
> include /usr/share/dpkg/pkg-info.mk
I think one more line is needed in debian/rules:
export DEB_VERSION_UPSTREAM
> and patching setup.py to change
>
> def get_setup_version(reponame):
> """Use autover to get up to date version."""
> # importing self into setup.py is unorthodox, but param has no
> # required dependencies outside of python
> from param.version import Version
> return
> Version.setup_version(os.path.dirname(__file__),reponame,archive_commit="$Format:%h$")
>
> to e.g.
>
> def get_setup_version(reponame):
> """Use autover to get up to date version."""
> if version := os.environ.get("DEB_VERSION_UPSTREAM"):
> return version
> # importing self into setup.py is unorthodox, but param has no
> # required dependencies outside of python
> from param.version import Version
> return
> Version.setup_version(os.path.dirname(__file__),reponame,archive_commit="$Format:%h$")
--
Dmitry Shachnev
signature.asc
Description: PGP signature
Bug#1030188: marked as pending in sip6
Control: tag -1 pending Hello, Bug #1030188 in sip6 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/sip6/-/commit/37b2bd4bb8d249ddae6db1c8ca804fc7036a8f2c Backport upstream patch to fix handling of composite classes. Closes: #1030188. (this message was generated automatically) -- Greetings https://bugs.debian.org/1030188
Bug#1029073: veusz: autopkgtest failure with Numpy 1.24
Hi Bas and Jeremy! On Tue, Jan 17, 2023 at 01:40:47PM +0100, Bas Couwenberg wrote: > The autopkgtest of your package fail with Numpy 1.24: > > [...] > AttributeError: module 'numpy' has no attribute 'bool'. Did you mean: > 'bool_'? > > https://ci.debian.net/data/autopkgtest/testing/amd64/v/veusz/30472445/log.gz > > A patch for this has been committed in git: > > > https://salsa.debian.org/science-team/veusz/-/commit/9ad531101e6fc08852759ce537a85126d7fe4905 I went ahead and uploaded this, because the autopkgtest regression was blocking Qt 5.15.8 migration to testing. Thanks for the patch! -- Dmitry Shachnev signature.asc Description: PGP signature
Bug#1028621: marked as pending in sphinx
Control: tag -1 pending Hello, Bug #1028621 in sphinx reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/packages/sphinx/-/commit/7333d4cec01ecf284eeb6ef4fc9bb2dc335e291d Backport upstream patch to update tests for Pygments 2.14. Closes: #1028621. (this message was generated automatically) -- Greetings https://bugs.debian.org/1028621
Bug#1027679: marked as pending in qtimageformats-opensource-src
Control: tag -1 pending Hello, Bug #1027679 in qtimageformats-opensource-src 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/qt-kde-team/qt/qtimageformats/-/commit/6ced0af17cf93588ea68d3d7e1be66097cc02ea3 Fix tests with libtiff 4.5. - Depend on qtbase version which has image_deletion_order.diff. - Add a patch to implement support for file memory mapping for tiff. Closes: #1027679. (this message was generated automatically) -- Greetings https://bugs.debian.org/1027679
Bug#1027679: qtimageformats-opensource-src: FTBFS with tiff 4.5.0+
Hi László! On Sun, Jan 01, 2023 at 08:20:00PM +0100, László Böszörményi wrote: > Hi, > > Your package fails to build with the new major tiff release. During > self-testing two tiff RGB tests fail, I think maybe due to broken > images. Fixing it is easy, just disable those two tests, patch is > attached. I don't think disabling the tests is the right fix. It looks like this test uncovered a real bug in libtiff, which is described here: https://gitlab.com/libtiff/libtiff/-/issues/505 -- Dmitry Shachnev signature.asc Description: PGP signature
Bug#1027416: marked as pending in qscintilla2
Control: tag -1 pending Hello, Bug #1027416 in qscintilla2 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/qscintilla2/-/commit/f81d3c0cf8218b54e5ed178877430034b8951e7f Copy the right file to pyproject.toml when installing Python bindings. The install target calls sip-distinfo, which reads pyproject.toml file to get the metadata. After build, pyproject.toml has contents from pyproject-qt6.toml, which caused both Qt 5 and Qt 6 variants to get metadata for Qt 6 variant. Closes: #1027416. (this message was generated automatically) -- Greetings https://bugs.debian.org/1027416
Bug#1026980: marked as pending in pyqt5
Control: tag -1 pending Hello, Bug #1026980 in pyqt5 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/pyqt5/-/commit/d20365bb3aefff2b00f5aaf5f928f45a3cb42974 Disable generation of .pyi files on mipsel to reduce memory consumption. Closes: #1026980. (this message was generated automatically) -- Greetings https://bugs.debian.org/1026980
Bug#1026980: pyqt5: FTBFS on mipsel (MemoryError)
Control: forwarded -1 https://www.riverbankcomputing.com/pipermail/pyqt/2022-December/045088.html Hi Bas! On Sun, Dec 25, 2022 at 03:57:22PM +0100, Bas Couwenberg wrote: > Source: pyqt5 > Version: 5.15.7+dfsg-2 > Severity: serious > Tags: upstream ftbfs > Control: block 1025863 by -1 > > Dear Maintainer, > > Your package FTBFS on mipsel, even on buildds where it built successfully > before, during the qtbase-opensource-src transition: > > Generating the _QOpenGLFunctions_2_0 bindings... > sip-build: An internal error occurred... > [...] > MemoryError I have contacted upstream about this, but I do not expect quick reply because of the holidays. I noticed that code generation with Python 3.11 succeeded, and failed only with Python 3.10. My hypothesis is that it happened because we do not generate .pyi files with non-default Python versions. I will try to disable .pyi generation completely and see if the package builds on a porterbox. -- Dmitry Shachnev signature.asc Description: PGP signature
Bug#1025678: coreboot-utils-doc: Uninstallable in sid because of ${sphinxdoc:Built-Using} dependency
Package: coreboot-utils-doc
Version: 4.15~dfsg-2
Severity: serious
Dear Maintainer,
In a clean sid chroot, coreboot-utils-doc is not installable:
# apt install coreboot-utils-doc
Reading package lists... Done
Building dependency tree... Done
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:
coreboot-utils-doc : Depends: sphinx (= 4.5.0-4)
E: Unable to correct problems, you have held broken packages.
This is because that package has ${sphinxdoc:Built-Using} among its
dependencies.
That substitution variable is intended to be used in Built-Using field of
architecture-dependent packages, NOT in Depends field. For "Architecture: all"
packages it is not needed at all. Please remove it.
--
Dmitry Shachnev
signature.asc
Description: PGP signature
Bug#938322: fixed in qtwebengine-opensource-src 5.15.11+dfsg-1
Hi Bastian! On Sun, Dec 04, 2022 at 12:15:04AM +0100, Bastian Germann wrote: > On Sun, 27 Nov 2022 10:00:56 + Debian FTP Masters > wrote: > >* Use Python 3 instead of Python 2 for building (closes: #938322). > > - Update build-dependency. > > - Add python3.patch, inspired by Arch Linux but using versioned > > python3. > > - Add chromium-python3.patch, copied from Arch Linux. > > This is now literally the last package that has build depends on python2 in > bookworm. > Is there a chance to move the experimental package to sid soon? Done! It requires binNMU of two reverse deps, that is tracked in #1025055. -- Dmitry Shachnev signature.asc Description: PGP signature
Bug#1025029: python-docutils: (autopkgtest) needs update for python3.11: 'NoneType' object is not subscriptable
Hi Stuart! On Wed, Nov 30, 2022 at 12:36:29AM +1100, Stuart Prescott wrote: > Version: 0.19+dfsg-2 > > The failing test in python-docutils in sid is fixed in the version in > experimental. Can the 0.19 release be uploaded to sid, or does the fix need > to be backported? Unfortunately this is blocked by sphinx-rtd-theme which still does not support docutils 0.18 or 0.19: - https://github.com/readthedocs/sphinx_rtd_theme/issues/1302 - https://github.com/readthedocs/sphinx_rtd_theme/issues/1322 - https://github.com/readthedocs/sphinx_rtd_theme/pull/1336 - https://github.com/readthedocs/sphinx_rtd_theme/pull/1381 (Also blocked by Sphinx, but it's blocked by sphinx-rtd-theme too.) I will try to identify fixes and cherry-pick them to 0.18. -- Dmitry Shachnev signature.asc Description: PGP signature
Bug#938322: marked as pending in qtwebengine-opensource-src
Control: tag -1 pending Hello, Bug #938322 in qtwebengine-opensource-src 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/qt-kde-team/qt/qtwebengine/-/commit/0db62e47f0e2f5e4e00193b65da912fe0083088c Use Python 3 instead of Python 2 for building. - Update build-dependency. - Add python3.patch, inspired by Arch Linux but using versioned python3. - Add chromium-python3.patch, copied from Arch Linux. Closes: #938322. (this message was generated automatically) -- Greetings https://bugs.debian.org/938322
Bug#1019974: uim: FTBFS on armhf: [Makefile:871: installed-modules.scm] Segmentation fault
On Tue, Oct 04, 2022 at 03:37:36PM +0300, Adrian Bunk wrote: > I cannot reproduce this, but I can NMU to build with -O1 everywhere. Thank you very much. I have just closed by RM bug. -- Dmitry Shachnev signature.asc Description: PGP signature
Bug#1019974: uim: FTBFS on armhf: [Makefile:871: installed-modules.scm] Segmentation fault
Hi Adrian! On Mon, Oct 03, 2022 at 07:48:08PM +0300, Adrian Bunk wrote: > The workaround below fixes the build. > > I looked through the backtrace in gdb, but debugging a Scheme > interpreter is outside of what I am feeling comfortable doing. Thank you for the patch. Can you go ahead and upload it as NMU? If you do it, I will withdraw my RM request (#1021102). And I would also include arm64 to the list because currently uim segfaults during installation there: https://ci.debian.net/data/autopkgtest/testing/arm64/u/uim/26665072/log.gz Setting up uim (1:1.8.8-9.1+b1) ... Segmentation fault dpkg: error processing package uim (--configure): installed uim package post-installation script subprocess returned error exit status 139 -- Dmitry Shachnev signature.asc Description: PGP signature
Bug#1020199: libqtxdg: FTBFS: make[1]: *** [debian/rules:15: override_dh_auto_configure] Error 2
Control: reassign -1 lxqt-build-tools 0.11.0-0.1 Control: affects -1 src:libqtxdg Control: fixed -1 lxqt-build-tools/0.11.0-1 Control: close -1 Control: merge 1020151 -1 On Sun, Sep 18, 2022 at 08:55:04AM +0200, Lucas Nussbaum wrote: > Hi, > > During a rebuild of all packages in sid, your package failed to build > on amd64. > > Relevant part (hopefully): > > -- Checking for module 'gio-unix-2.0' > > -- Found gio-unix-2.0, version 2.73.3 > > CMake Error at > > /usr/share/cmake-3.24/Modules/FindPackageHandleStandardArgs.cmake:230 > > (message): > > Could NOT find GLIB (missing: GLIB_GIO_UNIX_INCLUDE_DIR) (found suitable > > version "2.73.3", minimum required is "2.41.0") > > Call Stack (most recent call first): > > /usr/share/cmake-3.24/Modules/FindPackageHandleStandardArgs.cmake:594 > > (_FPHSA_FAILURE_MESSAGE) > > /usr/share/cmake/lxqt-build-tools/find-modules/FindGLIB.cmake:113 > > (FIND_PACKAGE_HANDLE_STANDARD_ARGS) > > CMakeLists.txt:26 (find_package) It is the same bug as #1020151, fixed in lxqt-build-tools 0.11.0-1. -- Dmitry Shachnev signature.asc Description: PGP signature
Bug#1020980: nodejs: "Cannot load externalized builtin" error
Package: nodejs Version: 18.10.0+dfsg-1 Severity: grave Control: block 1020230 by -1 Dear Maintainer, Trying to run "nodejs --version" in a fresh sid chroot results in this error: Cannot load externalized builtin: "internal/deps/cjs-module-lexer/lexer:/usr/share/nodejs/cjs-module-lexer/lexer.js". 1: 0x7f88e7f6ae58 node::Abort() [/lib/x86_64-linux-gnu/libnode.so.108] 2: 0x7f88e7f4bbfb [/lib/x86_64-linux-gnu/libnode.so.108] 3: 0x7f88e7f4bd36 node::builtins::BuiltinLoader::BuiltinLoader() [/lib/x86_64-linux-gnu/libnode.so.108] 4: 0x7f88e7e881df [/lib/x86_64-linux-gnu/libnode.so.108] 5: 0x7f88ea120cee [/lib64/ld-linux-x86-64.so.2] 6: 0x7f88ea120dd4 [/lib64/ld-linux-x86-64.so.2] 7: 0x7f88ea13797a [/lib64/ld-linux-x86-64.so.2] Aborted (core dumped) A stack trace obtained with gdb is attached. -- Dmitry Shachnev (gdb) r --version Starting program: /usr/lib/nodejs/bin/node --version [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Cannot load externalized builtin: "internal/deps/cjs-module-lexer/lexer:/usr/share/nodejs/cjs-module-lexer/lexer.js". 1: 0x75e13e58 node::Abort() [/lib/x86_64-linux-gnu/libnode.so.108] 2: 0x75df4bfb [/lib/x86_64-linux-gnu/libnode.so.108] 3: 0x75df4d36 node::builtins::BuiltinLoader::BuiltinLoader() [/lib/x86_64-linux-gnu/libnode.so.108] 4: 0x75d311df [/lib/x86_64-linux-gnu/libnode.so.108] 5: 0x77fcdcee [/lib64/ld-linux-x86-64.so.2] 6: 0x77fcddd4 [/lib64/ld-linux-x86-64.so.2] 7: 0x77fe497a [/lib64/ld-linux-x86-64.so.2] Program received signal SIGABRT, Aborted. __pthread_kill_implementation (threadid=, signo=signo@entry=6, no_tid=no_tid@entry=0) at ./nptl/pthread_kill.c:44 44 ./nptl/pthread_kill.c: No such file or directory. (gdb) bt #0 __pthread_kill_implementation (threadid=, signo=signo@entry=6, no_tid=no_tid@entry=0) at ./nptl/pthread_kill.c:44 #1 0x752a55df in __pthread_kill_internal (signo=6, threadid=) at ./nptl/pthread_kill.c:78 #2 0x75259a02 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #3 0x75244469 in __GI_abort () at ./stdlib/abort.c:79 #4 0x75e13e65 in node::Abort () at ../src/node_errors.cc:299 #5 0x75df4bfb in node::builtins::BuiltinLoader::AddExternalizedBuiltin (id=id@entry=0x777eacb0 "internal/deps/cjs-module-lexer/lexer", filename=filename@entry=0x777eac80 "/usr/share/nodejs/cjs-module-lexer/lexer.js") at ../src/node_builtins.cc:261 #6 0x75df4d36 in node::builtins::BuiltinLoader::BuiltinLoader (this=0x77fa44a0 ) at ../src/node_builtins.cc:37 #7 0x75d311df in __static_initialization_and_destruction_0 (__initialize_p=1, __priority=65535) at ../src/node_builtins.cc:31 #8 _GLOBAL__sub_I_node_builtins.cc(void) () at ../src/node_builtins.cc:700 #9 0x77fcdcee in call_init (env=0x7fffe3c0, argv=0x7fffe3a8, argc=2, l=) at ./elf/dl-init.c:70 #10 call_init (l=, argc=2, argv=0x7fffe3a8, env=0x7fffe3c0) at ./elf/dl-init.c:26 #11 0x77fcddd4 in _dl_init (main_map=0x77ffe2c0, argc=2, argv=0x7fffe3a8, env=0x7fffe3c0) at ./elf/dl-init.c:117 #12 0x77fe497a in _dl_start_user () from /lib64/ld-linux-x86-64.so.2 #13 0x0002 in ?? () #14 0x7fffe621 in ?? () #15 0x7fffe63a in ?? () #16 0x in ?? () signature.asc Description: PGP signature
Bug#1016264: maliit-framework: FTBFS: qtestcase.h:352:34: error: no match for ‘operator==’ (operand types are ‘const MImServerCommonOptions’ and ‘const MImServerCommonOptions’)
Control: tags -1 pending On Fri, Jul 29, 2022 at 06:21:52PM +0200, Lucas Nussbaum wrote: > Source: maliit-framework > Version: 2.2.1-2 > Severity: serious > Justification: FTBFS > Tags: bookworm sid ftbfs > User: lu...@debian.org > Usertags: ftbfs-20220728 ftbfs-bookworm > > Hi, > > During a rebuild of all packages in sid, your package failed to build > on amd64. I have just uploaded an NMU which fixes this. Attached a debdiff. -- Dmitry Shachnev diff -Nru maliit-framework-2.2.1/debian/changelog maliit-framework-2.2.1/debian/changelog --- maliit-framework-2.2.1/debian/changelog 2022-06-25 17:04:48.0 +0300 +++ maliit-framework-2.2.1/debian/changelog 2022-09-18 16:55:17.0 +0300 @@ -1,3 +1,15 @@ +maliit-framework (2.2.1-2.1) unstable; urgency=medium + + * Non-maintainer upload. + * Add two patches to fix FTBFS (closes: #1016264). +- debian/patches/0001_move-operator-definition.patch: Move the + operator== definition to global namespace. +- debian/patches/1001_fix-segfault.patch: Prevent QList returned + by subject->pluginDescriptions from being deleted. + * Update debian/libmaliit-plugins2.symbols from the current build logs. + + -- Dmitry Shachnev Sun, 18 Sep 2022 16:55:17 +0300 + maliit-framework (2.2.1-2) unstable; urgency=medium * debian/libmaliit-plugins2.symbols: diff -Nru maliit-framework-2.2.1/debian/libmaliit-plugins2.symbols maliit-framework-2.2.1/debian/libmaliit-plugins2.symbols --- maliit-framework-2.2.1/debian/libmaliit-plugins2.symbols 2022-06-25 17:04:08.0 +0300 +++ maliit-framework-2.2.1/debian/libmaliit-plugins2.symbols 2022-09-18 16:55:17.0 +0300 @@ -831,7 +831,6 @@ _ZN43MImSettingsQSettingsTemporaryBackendFactoryD0Ev@Base 2.0.0 _ZN43MImSettingsQSettingsTemporaryBackendFactoryD1Ev@Base 2.0.0 _ZN43MImSettingsQSettingsTemporaryBackendFactoryD2Ev@Base 2.0.0 - (optional=templinst|arch=!i386 !mipsel)_ZN4QMapI7QString14QSharedPointerI12MKeyOverrideEE6insertERKS0_RKS3_@Base 2.0.0 (optional=templinst)_ZN4QMapI7QString14QSharedPointerI12MKeyOverrideEED1Ev@Base 2.0.0 (optional=templinst)_ZN4QMapI7QString14QSharedPointerI12MKeyOverrideEED2Ev@Base 2.0.0 (optional=templinst)_ZN4QMapI7QString8QVariantE13detach_helperEv@Base 2.0.0 @@ -847,7 +846,7 @@ (optional=templinst)_ZN4QMapIN6Maliit12HandlerStateEPNS0_7Plugins17InputMethodPluginEE13detach_helperEv@Base 2.0.0 (optional=templinst)_ZN4QMapIPN6Maliit7Plugins17InputMethodPluginEN23MIMPluginManagerPrivate17PluginDescriptionEE13detach_helperEv@Base 2.0.0 (optional=templinst)_ZN4QMapIPN6Maliit7Plugins17InputMethodPluginEN23MIMPluginManagerPrivate17PluginDescriptionEE6insertERKS3_RKS5_@Base 2.0.0 - (optional=templinst|arch=!amd64 !arm64)_ZN4QMapIPN6Maliit7Plugins17InputMethodPluginEN23MIMPluginManagerPrivate17PluginDescriptionEEixERKS3_@Base 2.2.1 + (optional=templinst)_ZN4QMapIPN6Maliit7Plugins17InputMethodPluginEN23MIMPluginManagerPrivate17PluginDescriptionEEixERKS3_@Base 2.2.1 (optional=templinst)_ZN5QHashI21MAttributeExtensionId14QSharedPointerI19MAttributeExtensionEE11deleteNode2EPN9QHashData4NodeE@Base 2.0.0 (optional=templinst)_ZN5QHashI21MAttributeExtensionId14QSharedPointerI19MAttributeExtensionEE13detach_helperEv@Base 2.0.0 (optional=templinst)_ZN5QHashI21MAttributeExtensionId14QSharedPointerI19MAttributeExtensionEE13duplicateNodeEPN9QHashData4NodeEPv@Base 2.0.0 @@ -858,19 +857,17 @@ (optional=templinst)_ZN5QHashI7QString14QSharedPointerI45MSharedAttributeExtensionManagerPluginSettingEE11deleteNode2EPN9QHashData4NodeE@Base 2.0.0 (optional=templinst)_ZN5QHashI7QString14QSharedPointerI45MSharedAttributeExtensionManagerPluginSettingEE13detach_helperEv@Base 2.0.0 (optional=templinst)_ZN5QHashI7QString14QSharedPointerI45MSharedAttributeExtensionManagerPluginSettingEE13duplicateNodeEPN9QHashData4NodeEPv@Base 2.0.0 - (optional=templinst)_ZN5QHashI7QString14QSharedPointerI45MSharedAttributeExtensionManagerPluginSettingEEixERKS0_@Base 2.0.0 (optional=templinst)_ZN5QHashI7QString15QHashDummyValueE11deleteNode2EPN9QHashData4NodeE@Base 2.0.0 (optional=templinst)_ZN5QHashI7QString5QListIP27MImSettingsQSettingsBackendEE11deleteNode2EPN9QHashData4NodeE@Base 2.0.0 (optional=templinst)_ZN5QHashI7QString5QListIP27MImSettingsQSettingsBackendEE13detach_helperEv@Base 2.0.0 (optional=templinst)_ZN5QHashI7QString5QListIP27MImSettingsQSettingsBackendEE13duplicateNodeEPN9QHashData4NodeEPv@Base 2.0.0 - (optional=templinst)_ZN5QHashI7QString5QListIP27MImSettingsQSettingsBackendEE5eraseENS5_14const_iteratorE@Base 2.0.0 + (optional=templinst|arch=!i386)_ZN5QHashI7QString5QListIP27MImSettingsQSettingsBackendEE5eraseENS5_14const_iteratorE@Base 2.0.0 (optional=templinst)_ZN5QHashI7QString5QListIP27MImSettingsQSettingsBackendEED1Ev@Base 2.0.0 (optional=templinst)_ZN5QHashI7QString5QListIP27MImSettingsQSettingsBackendEED2Ev@Base 2.0.0 (optional=templinst)_ZN5QHashI7QString8QVariantE11deleteNode2EPN9QHashData
Bug#1020151: libfm-qt: FTBFS: make[1]: *** [debian/rules:15: override_dh_auto_configure] Error 2
Control: reassign -1 lxqt-build-tools 0.11.0-0.1 Control: affects -1 src:libfm-qt Control: fixed -1 lxqt-build-tools/0.11.0-1 Control: close -1 On Sun, Sep 18, 2022 at 08:55:01AM +0200, Lucas Nussbaum wrote: > Hi, > > During a rebuild of all packages in sid, your package failed to build > on amd64. > > Relevant part (hopefully): > > -- Checking for module 'gio-unix-2.0' > > -- Found gio-unix-2.0, version 2.73.3 > > CMake Error at > > /usr/share/cmake-3.24/Modules/FindPackageHandleStandardArgs.cmake:230 > > (message): > > Could NOT find GLIB (missing: GLIB_GIO_UNIX_INCLUDE_DIR) (found suitable > > version "2.73.3", minimum required is "2.50.0") > > Call Stack (most recent call first): > > /usr/share/cmake-3.24/Modules/FindPackageHandleStandardArgs.cmake:594 > > (_FPHSA_FAILURE_MESSAGE) > > /usr/share/cmake/lxqt-build-tools/find-modules/FindGLIB.cmake:113 > > (FIND_PACKAGE_HANDLE_STANDARD_ARGS) > > CMakeLists.txt:39 (find_package) This was fixed in yesterday's lxqt-build-tools 0.11.0-1 upload: * debian/patches: Use gdesktopappinfo.h to find gio-unix-2.0 -- Dmitry Shachnev signature.asc Description: PGP signature
Bug#1013060: veyon: ftbfs with GCC-12
On Thu, Jun 16, 2022 at 12:14:44PM +, Matthias Klose wrote:
> The package fails to build in a test rebuild on at least amd64 with
> gcc-12/g++-12, but succeeds to build with gcc-11/g++-11. The
> severity of this report will be raised before the bookworm release.
>
> [...]
>
> /<>/core/src/VncView.cpp: In member function ‘virtual void
> VncView::mouseEventHandler(QMouseEvent*)’:
> /<>/core/src/VncView.cpp:580:59: error: variable ‘constexpr
> const std::array 3> buttonTranslationMap’ has initializer but incomplete type
> 580 | static constexpr std::array
> buttonTranslationMap{ {
> |
> ^~~~
I have just NMUed veyon. Diff can be seen here:
https://salsa.debian.org/debian-edu-pkg-team/veyon/-/merge_requests/2
--
Dmitry Shachnev
signature.asc
Description: PGP signature
Bug#1016274: marked as pending in qtsystems-opensource-src
Control: tag -1 pending Hello, Bug #1016274 in qtsystems-opensource-src 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/qt-kde-team/qt/qtsystems/-/commit/44d85a47e316df25de7c7b54c208b2bc3a70fdc3 Update 1004_mark-as-override.patch to add override keyword only to *.h. Closes: #1016274. (this message was generated automatically) -- Greetings https://bugs.debian.org/1016274
Bug#1016277: qbs: FTBFS: ERROR: /usr/bin/ld: unrecognized option '-Wl,-s'
Control: fixed -1 qbs/1.23.0-1 Control: close -1 Control: merge 1013020 -1 On Fri, Jul 29, 2022 at 06:24:03PM +0200, Lucas Nussbaum wrote: > During a rebuild of all packages in sid, your package failed to build > on amd64. > > Relevant part (hopefully): > > 3: ERROR: /usr/bin/ld: unrecognized option '-Wl,-s' > > 3: /usr/bin/ld: use the --help option for usage information > > 3: collect2: error: ld returned 1 exit status No, the relevant part is this: > dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols > file: see diff output below So it is the same bug as #1013020, which is fixed in experimental. I hope I will upload it to unstable soon, but I need to find a workaround for #1016041. -- Dmitry Shachnev signature.asc Description: PGP signature
Bug#1013025: marked as pending in qtwebengine-opensource-src
Control: tag -1 pending Hello, Bug #1013025 in qtwebengine-opensource-src 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/qt-kde-team/qt/qtwebengine/-/commit/32198a3e0694401b745b4d01add18cdcddf658b4 Add a patch to fix build with GCC 12. Closes: #1013025. (this message was generated automatically) -- Greetings https://bugs.debian.org/1013025
Bug#1013027: marked as pending in qtwebkit-opensource-src
Control: tag -1 pending Hello, Bug #1013027 in qtwebkit-opensource-src 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/qt-kde-team/qt/qt5webkit/-/commit/7944fb5604c95e1edcc7d394ca421d259ab89c55 Update debian/libqt5webkit5.symbols for GCC 12. Closes: #1013027. (this message was generated automatically) -- Greetings https://bugs.debian.org/1013027
Bug#1013020: marked as pending in qbs
Control: tag -1 pending Hello, Bug #1013020 in qbs 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/qt-kde-team/qt/qbs/-/commit/99055c82fd9068f551589d421d9486da6f7899df Update debian/libqbscore1.23.symbols for new release and GCC 12. Closes: #1013020. (this message was generated automatically) -- Greetings https://bugs.debian.org/1013020
Bug#1004594: qtwebengine-opensource-src: FTBFS with ffmpeg 5.0
Control: forwarded -1 https://bugs.chromium.org/p/chromium/issues/detail?id=1251779 Hi Sebastian, and sorry for the long delay. On Wed, Feb 16, 2022 at 12:12:01AM +0100, Sebastian Ramacher wrote: > This came up on ffmpeg-devel [1]. Their suggestion is to keep track of > that value in chromium similar to [2]. That is: as long as the first DTS > was not store, take PTS from the first packet that has it and compute it > from PTS. > > Cheers > > [1] https://ffmpeg.org/pipermail/ffmpeg-devel/2021-September/285401.html > [2] https://github.com/FFmpeg/FFmpeg/commit/ab4f299e23 I see there is an open Chromium bug which has a link to the same ffpmeg-devel email: https://bugs.chromium.org/p/chromium/issues/detail?id=1251779 I don't want to touch Chromium code, so I will build with bundled ffmpeg for now, and wait for that bug to be fixed. I see that our Qt 6 maintainer did the same in qt6-webengine. -- Dmitry Shachnev signature.asc Description: PGP signature
Bug#1004594: marked as pending in qtwebengine-opensource-src
Control: tag -1 pending Hello, Bug #1004594 in qtwebengine-opensource-src 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/qt-kde-team/qt/qtwebengine/-/commit/7f6a137085aef4c654ad69f25f1d1909e9dbe04e Build with bundled ffmpeg for now. Closes: #1004594. (this message was generated automatically) -- Greetings https://bugs.debian.org/1004594
Bug#1012019: It's actually a sphinx issue
Control: reassign -1 src:coq-doc 8.15.1-1 Control: forwarded -1 https://github.com/coq/coq/pull/16193 Hi Julien! On Sat, Jun 11, 2022 at 09:16:50AM +0200, julien.pu...@gmail.com wrote: > reassign #1012019 sphinx 4.5.0 > affects #1012019 coq-doc > forwarded #1012019 https://github.com/sphinx-doc/sphinx/issues/10332 > thanks > > Hi, > > the problem with coq-doc actually stems from a sphinx 4.5.0 issue with > latex: https://github.com/sphinx-doc/sphinx/issues/10332 Actually the issue is in coq-doc because it's monkey-patching one of Sphinx methods, and the code is based on old version of Sphinx. I submitted a pull request upstream to rebase the monkey-patched version on top of the new version of that method (see Forwarded link). With that patch coq-doc builds successfully. So reassigning back to coq-doc. -- Dmitry Shachnev signature.asc Description: PGP signature
Bug#984102: NMU: libfm-qt: ftbfs with GCC-11
Hi Mateusz! On Wed, Jun 15, 2022 at 09:36:06PM +0200, Mateusz Łukasik wrote: > I see that. Fixed again on mentors. Uploaded. Thank you for the fix! -- Dmitry Shachnev signature.asc Description: PGP signature
Bug#1012793: libpyside2-py3-5.15 uninstallable on unstable: unsatisfiable Depends
Hi Julian! On Tue, Jun 14, 2022 at 08:37:38AM +0100, Julian Gilbey wrote: > Package: libpyside2-py3-5.15 > Version: 5.15.2-2.1 > Severity: serious > > This package depends on qtbase-abi-5-15-2 and > qtdeclarative-abi-5-15-2, but libqt5core5a now Provides: > qtbase-abi-5-15-4 and libqt5qml5 now Provides: > qtdeclarative-abi-5-15-4. The dependencies of this package need > updating to bring them into sync. We are now in a middle of Qt 5.15.4 transition [1][2]. Wait a couple of days, pyside2 will be rebuilt by the Release team. [1]: https://release.debian.org/transitions/html/qtbase-abi-5-15-4.html [2]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1007170 -- Dmitry Shachnev signature.asc Description: PGP signature
Bug#1012188: marked as done (python3-poppler-qt5: puts files in /usr/lib/python3.10/site-packages)
Hi Anthony! On Tue, Jun 07, 2022 at 03:54:03PM +, Debian Bug Tracking System wrote: >* > /usr/lib/python3.10/site-packages/python_poppler_qt5-0.75.0.dist-info/RECORD > or anything similar is no longer found after a Debian package rebuild. > Was it a temporary glitch in the binNMU of 0.75.0-3+b1 on 2021-11-20? > Thanks to Julian Gilbey for the heads-up! (Closes: #1012188) It was probably fixed by this dh-python change: https://salsa.debian.org/python-team/tools/dh-python/-/commit/d87523fc793daa7b -- Dmitry Shachnev signature.asc Description: PGP signature
Bug#1002382: nbsphinx: FTBFS: AttributeError: module 'mistune' has no attribute 'BlockGrammar'
Control: reassign -1 src:nbconvert 6.1.0-1 Control: unarchive 1002372 Control: forcemerge 1002372 -1 Control: archive 1002372 On Wed, Dec 22, 2021 at 09:05:08AM +0100, Lucas Nussbaum wrote: > Source: nbsphinx > Version: 0.8.7+ds-1 > Severity: serious > Justification: FTBFS > Tags: bookworm sid ftbfs > User: lu...@debian.org > Usertags: ftbfs-20211220 ftbfs-bookworm > > Hi, > > During a rebuild of all packages in sid, your package failed to build > on amd64. > > Relevant part (hopefully): > > make[1]: Entering directory '/<>' > > PYTHONPATH=/<>/src python3 -m sphinx -b html doc > > /<>/debian/python-nbsphinx-doc/usr/share/doc/python-nbsphinx/html > > Running Sphinx v4.3.2 > > > > Exception occurred: > > File > > "/usr/lib/python3/dist-packages/nbconvert/filters/markdown_mistune.py", > > line 31, in > > class MathBlockGrammar(mistune.BlockGrammar): > > AttributeError: module 'mistune' has no attribute 'BlockGrammar' It is a bug in nbconvert, same as #1002372. And already fixed. -- Dmitry Shachnev signature.asc Description: PGP signature
Bug#1009939: sip6: AttributeError: 'YaccProduction' object has no attribute 'parser_manager'
Hi Sebastiaan! On Fri, May 13, 2022 at 03:23:07PM +0200, Sebastiaan Couwenberg wrote: > On 4/21/22 05:39, Bas Couwenberg wrote: > > Since the upgrade to 6.6.1+dfsg-1 qgis FTBFS: > According to [0] the current hg tip enables successfull building of QGIS > again. > > That's quite a number of additional changes which I doubt is a good idea to > add as patches. That is unless it's going to take a long time until 6.6.2 > release. > > Do you have any insight when to expect the next sip6 upstream release? According to [1] it is “hopefully before the end of this month”. But given that this bug is RC, and there is another bug [2] affecting another package, then I don't have much choice. So doing a new upload with 27 patches added. [1]: https://www.riverbankcomputing.com/pipermail/pyqt/2022-May/044649.html [2]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010910 -- Dmitry Shachnev signature.asc Description: PGP signature
Bug#1009939: marked as pending in sip6
Control: tag -1 pending Hello, Bug #1009939 in sip6 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/sip6/-/commit/0ede128e111aaf94e535cacb96828fef4506ee6f Add upstream changes up to 2022-05-13. Except one commit which changes runtime module ABI. Closes: #1009939, #1010910. (this message was generated automatically) -- Greetings https://bugs.debian.org/1009939
Bug#1008416: libqtxdg: FTBFS: Could NOT find GLIB (missing: GLIB_GIO_UNIX_INCLUDE_DIR) (found suitable version "2.72.0", minimum required is "2.41.0")
Control: tags -1 + pending
On Tue, Apr 12, 2022 at 10:09:41PM +0300, Dmitry Shachnev wrote:
> This needs a fix in lxqt-build-tools:
>
> https://github.com/lxqt/lxqt-build-tools/commit/62b77bb807aa2ac2
On 2022-04-15, new upstream version 0.11.0 was released, which includes
this fix (it is the only change).
I have now uploaded NMU to DELAYED/2, packaging this new version.
Debdiff is attached. Also created a merge request on salsa:
https://salsa.debian.org/lxqt-team/lxqt-build-tools/-/merge_requests/3
--
Dmitry Shachnev
--- lxqt-build-tools-0.10.0/CHANGELOG
+++ lxqt-build-tools-0.11.0/CHANGELOG
@@ -1,3 +1,7 @@
+lxqt-build-tools-0.11.0 / 2022-04-15
+===
+ * Replaced `gunixconnection.h` file in `gio-unix` include dir check (after GLib 2.71.1).
+
lxqt-build-tools-0.10.0 / 2021-11-04
===
* Set the minimum required version of Qt to 5.15.
--- lxqt-build-tools-0.10.0/cmake/find-modules/FindGLIB.cmake
+++ lxqt-build-tools-0.11.0/cmake/find-modules/FindGLIB.cmake
@@ -101,7 +101,7 @@
elseif (${_component} STREQUAL "gio-unix")
pkg_check_modules(GIO_UNIX gio-unix-2.0)
find_path(GLIB_GIO_UNIX_INCLUDE_DIR
- NAMES gio/gunixconnection.h
+ NAMES gio/gunixfdlist.h
HINTS ${GIO_UNIX_INCLUDEDIR}
PATH_SUFFIXES gio-unix-2.0)
--- lxqt-build-tools-0.10.0/CMakeLists.txt
+++ lxqt-build-tools-0.11.0/CMakeLists.txt
@@ -9,7 +9,7 @@
option(WITH_XDG_DIRS_FALLBACK "Use our XDG_CONFIG_DIRS fallback" ON)
set(LXQT_BUILD_TOOLS_MAJOR_VERSION 0)
-set(LXQT_BUILD_TOOLS_MINOR_VERSION 10)
+set(LXQT_BUILD_TOOLS_MINOR_VERSION 11)
set(LXQT_BUILD_TOOLS_PATCH_VERSION 0)
set(LXQT_BUILD_TOOLS_VERSION ${LXQT_BUILD_TOOLS_MAJOR_VERSION}.${LXQT_BUILD_TOOLS_MINOR_VERSION}.${LXQT_BUILD_TOOLS_PATCH_VERSION})
set(LXQT_MIN_LINGUIST_VERSION "5.15.0")
--- lxqt-build-tools-0.10.0/debian/changelog
+++ lxqt-build-tools-0.11.0/debian/changelog
@@ -1,3 +1,11 @@
+lxqt-build-tools (0.11.0-0.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * New upstream release.
+- Fixes compatibility with GLib ≥ 2.71.1 (closes: #1008416).
+
+ -- Dmitry Shachnev Sat, 14 May 2022 16:00:20 +0300
+
lxqt-build-tools (0.10.0-1) unstable; urgency=medium
[ Andrew Lee (李健秋) ]
signature.asc
Description: PGP signature
Bug#1010446: nodejs 14.19 hangs on mipsel/mips64el when building qtwebengine frontend with rollup and terser plugin
Package: nodejs Version: 16.13.2+really14.19.1~dfsg-6 Severity: serious Control: fixed -1 nodejs/16.14.2+dfsg-1 Affects: src:qtwebengine-opensource-src Dear nodejs maintainers, Currently qtwebengine-opensource-src FTBFS on mipsel and mips64el: https://buildd.debian.org/status/logs.php?pkg=qtwebengine-opensource-src=5.15.8%2Bdfsg-1%2Bb2=mips64el This started happening after nodejs was upgraded from 12.22 to 14.19, and it does not happen with 16.14 from experimental. Here are the steps to reproduce this bug (qtwebengine is huge, I tried to make the test case smaller): # apt install nodejs rollup node-rollup-plugin-terser $ wget https://mitya57.me/nodejs/front_end.tar.xz $ tar xJf front_end.tar.xz $ cd front_end $ nodejs /usr/bin/rollup --plugin terser --config rollup.config.js --input timeline_model/timeline_model.prebundle.js On eller porter box, with nodejs 16.14 this command succeeds in ~11 seconds. With nodejs 14.19, it hangs and does not finish in an hour. With 16.14 it prints a warning about circular dependency, but it's just a warning, not an error (the build still succeeds). I see there is a transition to new nodejs planned (#1010438), but I am still filing this bug for documentation purposes and with RC severity, as requested by Sebastian Ramacher. -- Dmitry Shachnev signature.asc Description: PGP signature
Bug#1009939: marked as pending in sip6
Control: tag -1 pending Hello, Bug #1009939 in sip6 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/sip6/-/commit/01d514183637bbe5ba0e183cc6e66fe88cf9329e Backport patch to fix an attribute mis-naming in the parsing of exceptions. Closes: #1009939. (this message was generated automatically) -- Greetings https://bugs.debian.org/1009939
Bug#1009445: marked as pending in sphinx
Control: tag -1 pending Hello, Bug #1009445 in sphinx reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/packages/sphinx/-/commit/153a10527b608120caf7afba06a1ea39e02e89af Depend on python3-importlib-metadata. Needed because we still support Python 3.9. Closes: #1009382, #1009434, #1009445. (this message was generated automatically) -- Greetings https://bugs.debian.org/1009445
Bug#1009382: marked as pending in sphinx
Control: tag -1 pending Hello, Bug #1009382 in sphinx reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/packages/sphinx/-/commit/153a10527b608120caf7afba06a1ea39e02e89af Depend on python3-importlib-metadata. Needed because we still support Python 3.9. Closes: #1009382, #1009434, #1009445. (this message was generated automatically) -- Greetings https://bugs.debian.org/1009382
Bug#1008416: libqtxdg: FTBFS: Could NOT find GLIB (missing: GLIB_GIO_UNIX_INCLUDE_DIR) (found suitable version "2.72.0", minimum required is "2.41.0")
Control: reassign -1 lxqt-build-tools 0.10.0-1 Control: affects -1 src:libqtxdg Control: forwarded -1 https://github.com/lxqt/lxqt-build-tools/pull/74 On Sat, Mar 26, 2022 at 10:53:57PM +0100, Lucas Nussbaum wrote: > Hi, > > During a rebuild of all packages in sid, your package failed to build > on amd64. > > > Relevant part (hopefully): > [...] > > -- Checking for module 'glib-2.0' > > -- Found glib-2.0, version 2.72.0 > > -- Checking for module 'gio-unix-2.0' > > -- Found gio-unix-2.0, version 2.72.0 > > CMake Error at > > /usr/share/cmake-3.22/Modules/FindPackageHandleStandardArgs.cmake:230 > > (message): > > Could NOT find GLIB (missing: GLIB_GIO_UNIX_INCLUDE_DIR) (found suitable > > version "2.72.0", minimum required is "2.41.0") > > Call Stack (most recent call first): > > /usr/share/cmake-3.22/Modules/FindPackageHandleStandardArgs.cmake:594 > > (_FPHSA_FAILURE_MESSAGE) > > /usr/share/cmake/lxqt-build-tools/find-modules/FindGLIB.cmake:113 > > (FIND_PACKAGE_HANDLE_STANDARD_ARGS) > > CMakeLists.txt:26 (find_package) > > > > > > -- Configuring incomplete, errors occurred! This needs a fix in lxqt-build-tools: https://github.com/lxqt/lxqt-build-tools/commit/62b77bb807aa2ac2 So reassigning accordingly. -- Dmitry Shachnev signature.asc Description: PGP signature
Bug#1008006: dde-qt5integration: FTBFS: Unknown module(s) in QT: dtkgui5.5 dtkwidget5.5
Source: dde-qt5integration
Version: 5.5.8-1
Severity: serious
Tags: ftbfs
Dear Maintainer,
dde-qt5integration fails to build from source in a clean sid chroot:
Project ERROR: Unknown module(s) in QT: dtkgui5.5 dtkwidget5.5
make[2]: *** [Makefile:47: sub-chameleon-make_first] Error 3
make[2]: Leaving directory '/build/dde-qt5integration-5.5.8/styleplugins'
The full build log is attached.
--
Dmitry Shachnev
[0mI: pbuilder: network access will be disabled during build[0m
[0mI: Current time: Sun Mar 20 17:03:02 MSK 2022[0m
[0mI: pbuilder-time-stamp: 1647784982[0m
[0mI: Building the build Environment[0m
[0mI: extracting base tarball [/home/dmitry/pbuilder/sid-base.tgz][0m
[0mI: copying local configuration[0m
[1;33mW: --override-config is not set; not updating apt.conf Read the manpage
for details.[0m
[0mI: mounting /proc filesystem[0m
[0mI: mounting /sys filesystem[0m
[0mI: creating /{dev,run}/shm[0m
[0mI: mounting /dev/pts filesystem[0m
[0mI: redirecting /dev/ptmx to /dev/pts/ptmx[0m
[0mI: policy-rc.d already exists[0m
[0mI: Obtaining the cached apt archive contents[0m
[0mI: Copying source file[0m
[0mI: copying [dde-qt5integration_5.5.8-1.dsc][0m
[0mI: copying [./dde-qt5integration_5.5.8.orig.tar.gz][0m
[0mI: copying [./dde-qt5integration_5.5.8-1.debian.tar.xz][0m
[0mI: Extracting source[0m
gpgv: unknown type of key resource 'trustedkeys.kbx'
gpgv: keyblock resource '/tmp/dpkg-verify-sig.dxFptRaa/trustedkeys.kbx':
General error
gpgv: Signature made Wed Nov 10 01:28:36 2021 UTC
gpgv:using RSA key 7E7729476D87D6F11D91ACCBC293E7B461825ACE
gpgv: Can't check signature: No public key
dpkg-source: warning: cannot verify signature ./dde-qt5integration_5.5.8-1.dsc
dpkg-source: info: extracting dde-qt5integration in dde-qt5integration-5.5.8
dpkg-source: info: unpacking dde-qt5integration_5.5.8.orig.tar.gz
dpkg-source: info: unpacking dde-qt5integration_5.5.8-1.debian.tar.xz
dpkg-source: info: using patch list from debian/patches/series
dpkg-source: info: applying 0001-disable-googletest-for-now.patch
[0mI: Not using root during the build.[0m
[0mI: Installing the build-deps[0m
-> Attempting to satisfy build-dependencies
-> Creating pbuilder-satisfydepends-dummy package
Package: pbuilder-satisfydepends-dummy
Version: 0.invalid.0
Architecture: amd64
Maintainer: Debian Pbuilder Team
Description: Dummy package to satisfy dependencies with aptitude - created by
pbuilder
This package was created automatically by pbuilder to satisfy the
build-dependencies of the package being currently built.
Depends: debhelper-compat (= 13), libdtkgui-dev (>= 5.5.17~), libdtkwidget-dev
(>= 5.5.17~), libegl1-mesa-dev, libfontconfig1-dev, libfreetype6-dev,
libglib2.0-dev, libmtdev-dev, libqt5svg5-dev, libqt5x11extras5-dev,
libqt5xdg-dev, libqt5xdgiconloader-dev (>= 3.2.0~), libxrender-dev, pkg-config,
qt5-qmake, qtbase5-dev, qtbase5-private-dev
dpkg-deb: building package 'pbuilder-satisfydepends-dummy' in
'/tmp/satisfydepends-aptitude/pbuilder-satisfydepends-dummy.deb'.
Selecting previously unselected package pbuilder-satisfydepends-dummy.
(Reading database ... 13644 files and directories currently installed.)
Preparing to unpack .../pbuilder-satisfydepends-dummy.deb ...
Unpacking pbuilder-satisfydepends-dummy (0.invalid.0) ...
dpkg: pbuilder-satisfydepends-dummy: dependency problems, but configuring
anyway as you requested:
pbuilder-satisfydepends-dummy depends on debhelper-compat (= 13); however:
Package debhelper-compat is not installed.
pbuilder-satisfydepends-dummy depends on libdtkgui-dev (>= 5.5.17~); however:
Package libdtkgui-dev is not installed.
pbuilder-satisfydepends-dummy depends on libdtkwidget-dev (>= 5.5.17~);
however:
Package libdtkwidget-dev is not installed.
pbuilder-satisfydepends-dummy depends on libegl1-mesa-dev; however:
Package libegl1-mesa-dev is not installed.
pbuilder-satisfydepends-dummy depends on libfontconfig1-dev; however:
Package libfontconfig1-dev is not installed.
pbuilder-satisfydepends-dummy depends on libfreetype6-dev; however:
Package libfreetype6-dev is not installed.
pbuilder-satisfydepends-dummy depends on libglib2.0-dev; however:
Package libglib2.0-dev is not installed.
pbuilder-satisfydepends-dummy depends on libmtdev-dev; however:
Package libmtdev-dev is not installed.
pbuilder-satisfydepends-dummy depends on libqt5svg5-dev; however:
Package libqt5svg5-dev is not installed.
pbuilder-satisfydepends-dummy depends on libqt5x11extras5-dev; however:
Package libqt5x11extras5-dev is not installed.
pbuilder-satisfydepends-dummy depends on libqt5xdg-dev; however:
Package libqt5xdg-dev is not installed.
pbuilder-satisfydepends-dummy depends on libqt5xdgiconloader-dev (>= 3.2.0~);
however:
Package libqt5xdgiconloader-dev is not installed.
pbuilder-satisfydepends-dummy depends on libxrender-dev; however:
Package libxrender-dev is not installed.
pbuilder-satisfydepe
Bug#1006009: fixed in libwebp 1.2.2-1
Control: reopen -1 Control: found -1 libwebp/1.2.2-1 Hi all, On Thu, Mar 10, 2022 at 11:17:50PM -0500, Andres Salomon wrote: > Hi, > > Are you sure that 1.2.2 fixes the build failure? The 1.2.2 release was > tagged on Jan 20th: > > https://chromium.googlesource.com/webm/libwebp/+/refs/tags/v1.2.2 > > The MIPS regression wasn't reported until Feb, and the commit that fixed it > was made on March 1st: > > https://bugs.chromium.org/p/webp/issues/detail?id=558 > > https://chromium.googlesource.com/webm/libwebp/+/e4cbcdd2b5ff33a64f97fe49d67fb56f915657e8%5E%21/ > > So it would remain unfixed in 1.2.2-1 unless you patched something else to > fix it? I don't see that particular commit in the uploaded source: > > https://sources.debian.org/src/libwebp/1.2.2-1/src/dsp/lossless_enc_mips32.c/ Indeed, with 1.2.2-1 this bug appears again: https://buildd.debian.org/status/fetch.php?pkg=qtimageformats-opensource-src=mipsel=5.15.3-1=1647075018=0 Please add back the patch from NMU which was dropped. -- Dmitry Shachnev signature.asc Description: PGP signature
Bug#1006009: qtimageformats-opensource-src: FTBFS on mipsel: test failure
Control: reassign -1 libwebp7 1.2.1-7 Control: affects -1 src:qtimageformats-opensource-src Hi Sebastian and libwebp maintainers! On Fri, Feb 18, 2022 at 10:39:23PM +0100, Sebastian Ramacher wrote: > Source: qtimageformats-opensource-src > Version: 5.15.2-2 > Severity: serious > Tags: ftbfs > Justification: fails to build from source (but built successfully in the past) > X-Debbugs-Cc: sramac...@debian.org > > qtimageformats-opensource-src FTBFS on mipsel: > > TIFFReadDirectory: Warning, Sum of Photometric type-related color channels > and ExtraSamples doesn't match SamplesPerPixel. Defining non-color channels > as ExtraSamples.. > TIFFReadDirectory: Warning, Sum of Photometric type-related color channels > and ExtraSamples doesn't match SamplesPerPixel. Defining non-color channels > as ExtraSamples.. > PASS : tst_qtiff::tiffGrayscale() > FAIL! : tst_qwebp::writeImage(kollada_noalpha-100) '!reread.isNull()' > returned FALSE. () >Loc: [tst_qwebp.cpp(174)] > PASS : tst_qwebp::cleanupTestCase() > Totals: 10 passed, 1 failed, 0 skipped, 0 blacklisted, 632ms > * Finished testing of tst_qwebp * > > See > https://buildd.debian.org/status/fetch.php?pkg=qtimageformats-opensource-src=mipsel=5.15.2-2%2Bb1=1645209225=0 It looks to me like a bug in new libwebp version: encoder generates broken webp files on mipsel. I can reproduce it without any Qt code by encoding the attached PNG file and then trying to decode it back: (sid_mipsel-dchroot)mitya57@eller:~$ cwebp kollada_noalpha.png -lossless -o kollada_noalpha.webp Saving file 'kollada_noalpha.webp' File: kollada_noalpha.png Dimension: 436 x 160 Output:37004 bytes (4.24 bpp) Lossless-ARGB compressed size: 37004 bytes * Header size: 636 bytes, image data size: 36342 * Precision Bits: histogram=3 transform=3 cache=1 (sid_mipsel-dchroot)mitya57@eller:~$ dwebp kollada_noalpha.webp Decoding of kollada_noalpha.webp failed. Status: 3(BITSTREAM_ERROR) I am also attaching the generated broken WEBP file. -- Dmitry Shachnev kollada_noalpha.webp Description: Binary data signature.asc Description: PGP signature
Bug#1006041: marked as pending in pymarkups
Control: tag -1 pending Hello, Bug #1006041 in pymarkups 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/pymarkups/-/commit/2d7dcce330930a129fd70b0254e1f0f853715188 Add a patch to fix build with Pygments 2.11. Closes: #1006041. (this message was generated automatically) -- Greetings https://bugs.debian.org/1006041
Bug#1000184: Can dh_sphinxdoc disable intersphinx_mapping support?
Hi Neil! On Fri, Nov 19, 2021 at 09:48:56AM +, Neil Williams wrote: > tag 1000184 - pending > thanks > > Does dh_sphinxdoc need to also disable https: or does > intersphinx_mapping have to be patched out of every package using Sphinx? dh_sphinxdoc is a packaging helper that is called *after* the documentation is built and installed. It cannot affect the docs build process in any way. If you want to disable network access, you should set the environment variables yourself in debian/rules. http_proxy is not enough, you need to set https_proxy to the same value. > This will inevitably cause another difference between the upstream > documentation and the packaged documentation, unless some sort of cache > can be created. > > For python-jira and a number of other Python packages, the only > solution for now is to patch out intersphinx support entirely. > > (Spotted via a reproducibility failure). You can make it link to packaged versions of documentation. See what I do in packaging of sphinx itself: https://salsa.debian.org/python-team/packages/sphinx/-/blob/debian/master/debian/patches/intersphinx_local.diff -- Dmitry Shachnev signature.asc Description: PGP signature
Bug#998837: marked as pending in gnome-flashback
Control: tag -1 pending Hello, Bug #998837 in gnome-flashback 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/gnome-team/gnome-flashback/-/commit/8a5b0ece8f61c547723cfb78ee64c78ad4dfd0a7 Backport upstream patch to fix segfault on login. Closes: #998837. Thanks: Timothy Allen for the bug report. (this message was generated automatically) -- Greetings https://bugs.debian.org/998837
Bug#998567: qgis: FTBFS: sip: /usr/lib/python3/dist-packages/PyQt5/bindings/QtCore/QtCoremod.sip:23: syntax error
Hi Sebastiaan!
On Fri, Nov 05, 2021 at 06:45:00PM +0100, Sebastiaan Couwenberg wrote:
> Control: tags -1 upstream
>
> On 11/4/21 20:49, Lucas Nussbaum wrote:
> > > sip:
> > > /usr/lib/python3/dist-packages/PyQt5/bindings/QtCore/QtCoremod.sip:23:
> > > syntax error
>
> This seems to be caused by the recent switch to sip6 in pyqt5.
I have updated sip4 to not break on the new syntax. This should help.
> Upstream recently added support for sip6 in their non-LTR, but those changes
> aren't enough for build 3.16.x successfully with sip6:
>
> Querying qmake about your Qt installation...
> These bindings will be built: analysis.
> Generating the analysis bindings...
> sip-build: Unable to find file "QtCore/QtCoremod.sip"
>
> ...
>
> Querying qmake about your Qt installation...
> These bindings will be built: 3d.
> Generating the 3d bindings...
> sip-build: Unable to find file "QtXml/QtXmlmod.sip"
>
> These files are provided by pyqt5-dev under
> /usr/lib/python3/dist-packages/PyQt5/bindings/ but not found for some
> reason.
>
> We may have to wait for the QGIS 3.22.4 LTR in February to be able to build
> successfully with sip6.
>
> Dmitry, do you have any suggestion how to fix the sip6 support in qgis?
Please make sure you are passing --target-dir /usr/lib/python3/dist-packages
to sip-build.
Without that option, it will look in /usr/lib/python3.x/site-packages
because that path is returned by sysconfig.get_path('platlib').
--
Dmitry Shachnev
signature.asc
Description: PGP signature
Bug#998605: krita: FTBFS: sip: /usr/lib/python3/dist-packages/PyQt5/bindings/QtCore/QtCoremod.sip:23: syntax error
Hi Jochen! On Fri, Nov 05, 2021 at 09:13:14AM +0100, Jochen Sprickerhof wrote: > Hi Dmitry, > > Agreed, this also affects src:ros-rviz, src:qgis and src:pyqwt3d, in > #998561, #998567 and #998595. I didn't reassign the bugs as sip4 is > deprecated. Thank you for giving me a list of these bugs! > The easy fix would be to revert the change in > > /usr/lib/python3/dist-packages/PyQt5/bindings/QtCore/QtCoremod.sip:23 > > Alternatively we could add py_ssize_t_clean to the sip4 parser, see the > attached patch. > > I've verified that both fix ros-rviz. I prefer adding functionality to SIP 4 to removing the functionality from SIP 6 or PyQt5. So thank you for the patch, I have applied it to sip4 package and uploaded. > Looking at > > https://udd.debian.org/cgi-bin/bts-usertags.cgi?user=mitya57%40debian.org=sip5 > > I guess we want to src:ros-rviz and src:qgis to the list. > Do you have any documentation on how to port from sip4 to sip6? > Esp how to do code generation like /usr/bin/sip with sip6. Unfortunately there is no replacement for /usr/bin/sip. The recommended way is to use the new sip-build tool, and two files to configure it: pyproject.toml and project.py. Here are some examples of porting: - https://github.com/frescobaldi/python-poppler-qt5/pull/41 - https://github.com/GauiStori/PyQt-Qwt/pull/14 - https://github.com/qgis/QGIS/pull/45128 - https://github.com/kovidgoyal/calibre/commit/7a4b3f61ff24f8c3 - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964127#51 You can also look at what QScintilla2 does, it is developed by the same person as SIP and PyQt so it will always use the best practice: https://www.riverbankcomputing.com/software/qscintilla/download Alternatively, if your project is a complex one and has more than just a SIP binding, you may use sipbuild Python API directly. I have some examples of this too: - https://github.com/veusz/veusz/pull/545 - https://github.com/wxWidgets/Phoenix/pull/1916 By the way, wxpysip.py with my patch from the last link is the best approximation of old sip tool that I know of. But it is recommended to use the sip-build tool because sipbuild API is not stable and breaks from time to time. -- Dmitry Shachnev
Bug#998561: marked as pending in sip4
Control: tag -1 pending Hello, Bug #998561 in sip4 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/sip4/-/commit/c4fba96da08000fad9479f05afa548c4550b85da Add a patch to make the parser not break on py_ssize_t_clean directive. Closes: #998561. Thanks Jochen Sprickerhof! (this message was generated automatically) -- Greetings https://bugs.debian.org/998561
