Bug#973095: ros-angles: FTBFS: make[5]: *** No rule to make target 'gmock/libgmock.a', needed by 'devel/lib/angles/utest'. Stop.

2020-11-03 Thread Timo Röhling
Control: reassign -1 cmake-extras Control: reassign 973291 cmake-extras Control: merge -1 973291 Control: affects -1 + src:ros-angles src:ros-rospack Dear cmake-extras maintainers, I believe bugs #973095 and #973291 can be traced back to your package: > During a rebuild of all packages in sid,

Bug#973290: ros-ros ftbfs in unstable with python3.9

2020-11-03 Thread Timo Röhling
Control: reassign -1 cmake-extras Control: merge 973291 -1 Control: affects 973291 + src:ros-ros Hi Matthias, On Wed, 28 Oct 2020 09:45:53 +0100 Matthias Klose wrote: > to reproduce, you can use the repositories found at: > > deb [trusted=yes] http://people.debian.org/~doko/tmp/python3.9 ./ >

Bug#973095: ros-angles: FTBFS: make[5]: *** No rule to make target 'gmock/libgmock.a', needed by 'devel/lib/angles/utest'. Stop.

2020-11-05 Thread Timo Röhling
Control: tags -1 + patch After some further digging, I found the problem: -- Could NOT find PkgConfig (missing: PKG_CONFIG_EXECUTABLE) -- Using /usr/src/googletest/googlemock/ as gmock source directory CMake Warning at /usr/share/cmake/GMock/GMockConfig.cmake:68 (message):   Could not detect

Bug#980371: libjsonp-java 1.1.2-1 breaks antlr4-maven-plugin

2021-01-18 Thread Timo Röhling
tion unstable dpkg-buildpackage: info: source changed by Timo Röhling dpkg-source --before-build . dpkg-buildpackage: info: host architecture amd64 debian/rules clean dh clean --buildsystem=maven dh_auto_clean -O--buildsystem=maven bash -c "for dir in \$(find . -name target -type

Bug#988512: CAcert class 3 validates

2021-06-14 Thread Timo Röhling
-- ⢀⣴⠾⠻⢶⣦⠀ ╭╮ ⣾⠁⢠⠒⠀⣿⡁ │ Timo Röhling │ ⢿⡄⠘⠷⠚⠋⠀ │ 9B03 EBB9 8300 DF97 C2B1 23BF CC8C 6BDD 1403 F4CA │ ⠈⠳⣄ ╰╯ signature.asc Description: PGP signature

Bug#933100: Bug has been fixed in upstream since 0.9.0

2021-06-21 Thread Timo Röhling
-- ⢀⣴⠾⠻⢶⣦⠀ ╭╮ ⣾⠁⢠⠒⠀⣿⡁ │ Timo Röhling │ ⢿⡄⠘⠷⠚⠋⠀ │ 9B03 EBB9 8300 DF97 C2B1 23BF CC8C 6BDD 1403 F4CA │ ⠈⠳⣄ ╰╯ signature.asc Description: PGP signature

Bug#897707: Should this package be removed from Debian?

2021-06-21 Thread Timo Röhling
. Cheers Timo -- ⢀⣴⠾⠻⢶⣦⠀ ╭╮ ⣾⠁⢠⠒⠀⣿⡁ │ Timo Röhling │ ⢿⡄⠘⠷⠚⠋⠀ │ 9B03 EBB9 8300 DF97 C2B1 23BF CC8C 6BDD 1403 F4CA │ ⠈⠳⣄ ╰╯ signature.asc Description

Bug#988310: ssl-cert: diff for NMU version 1.1.0+nmu1

2021-06-06 Thread Timo Röhling
Control: tags 988310 + patch Control: tags 988310 + pending I've prepared an NMU for ssl-cert (versioned as 1.1.0+nmu1) and uploaded it to NEW. Cheers Timo -- ⢀⣴⠾⠻⢶⣦⠀ ╭╮ ⣾⠁⢠⠒⠀⣿⡁ │ Timo Röhling

Bug#988310: ssl-cert: make-ssl-cert uses same filename for template and output

2021-06-06 Thread Timo Röhling
that he has to pass *two* arguments. I'll prepare an NMU and upload it shortly. Cheers Timo -- ⢀⣴⠾⠻⢶⣦⠀ ╭────╮ ⣾⠁⢠⠒⠀⣿⡁ │ Timo Röhling │ ⢿⡄⠘⠷⠚⠋⠀ │ 9B03 EBB9 8300 DF97 C2B1 23BF

Bug#990409: ca-cacert: should this package be removed?

2021-06-28 Thread Timo Röhling
. Cheers Timo [1] https://bugs.debian.org/988512 [2] http://www.cacert.org/index.php?id=3 -- ⢀⣴⠾⠻⢶⣦⠀ ╭╮ ⣾⠁⢠⠒⠀⣿⡁ │ Timo Röhling │ ⢿⡄⠘⠷⠚⠋⠀ │ 9B03 EBB9 8300 DF97 C2B1 23BF CC8C 6BDD 1403 F4CA

Bug#952950: nss: Replace PKCS11 headers provided by OASIS

2021-04-01 Thread Timo Röhling
On Tue, 23 Mar 2021 00:44:07 +0100 Bastian Germann wrote: On Tue, 23 Mar 2021 00:18:08 +0100 Bastian Germann wrote:> Upstream had a discussion about the license at > https://phabricator.services.mozilla.com/D63241 and with OASIS at > https://markmail.org/thread/4juvugfvj45iyrmp As far as I

Bug#952950: nss: Replace PKCS11 headers provided by OASIS

2021-04-01 Thread Timo Röhling
On Tue, 23 Mar 2021 00:44:07 +0100 Bastian Germann wrote: As far as I can see, the license for NSS's PKCS#11 headers is MPL 2.0 (DFSG-free) and not the OASIS IPR. Well, I can see from the discussion you linked that the OASIS IPR license is intended to apply to their work products, and not the

Bug#952950: nss: Replace PKCS11 headers provided by OASIS

2021-02-13 Thread Timo Röhling
On Mon, 2 Mar 2020 17:16:09 +0800 Alvin Chen wrote: > You can use an alternative header like p11-kit which is licensed under > a more liberal license. I had a look at the PKCS #11 headers; the biggest problem is that NSS uses version 3.00 while the p11-kit headers have been forked at 2.40 and not

Bug#994419: libgtest-dev: missing dependency on libgmock-dev

2021-09-16 Thread Timo Röhling
heers Timo -- ⢀⣴⠾⠻⢶⣦⠀ ╭╮ ⣾⠁⢠⠒⠀⣿⡁ │ Timo Röhling │ ⢿⡄⠘⠷⠚⠋⠀ │ 9B03 EBB9 8300 DF97 C2B1 23BF CC8C 6BDD 1403 F4CA │ ⠈⠳⣄ ╰╯ gbp:info: Building with (

Bug#994419: libgtest-dev: missing dependency on libgmock-dev

2021-09-16 Thread Timo Röhling
rgets will not be imported") endif() to the end of GTestConfig.cmake. Cheers Timo -- ⢀⣴⠾⠻⢶⣦⠀ ╭╮ ⣾⠁⢠⠒⠀⣿⡁ │ Timo Röhling │ ⢿⡄⠘⠷⠚⠋⠀ │ 9B03 EBB9 8300 DF97 C2B1 23BF CC8C 6BDD

Bug#994419: libgtest-dev: missing dependency on libgmock-dev

2021-09-16 Thread Timo Röhling
. -- ⢀⣴⠾⠻⢶⣦⠀ ╭╮ ⣾⠁⢠⠒⠀⣿⡁ │ Timo Röhling │ ⢿⡄⠘⠷⠚⠋⠀ │ 9B03 EBB9 8300 DF97 C2B1 23BF CC8C 6BDD 1403 F4CA │ ⠈⠳⣄ ╰╯ cmake_minimum_required(VERSION 3.21) project(googletest_breakage) find_package(GTest REQUIRED

Bug#994419: libgtest-dev: missing dependency on libgmock-dev

2021-09-16 Thread Timo Röhling
the extra dependency, and does not even need any downstream changes with GTest users. Unfortunately, Google does not seem very eager to merge my PR. -- ⢀⣴⠾⠻⢶⣦⠀ ╭╮ ⣾⠁⢠⠒⠀⣿⡁ │ Timo Röhling │ ⢿⡄⠘⠷⠚⠋⠀ │ 9B03 EBB9

Bug#994419: libgtest-dev: missing dependency on libgmock-dev

2021-09-16 Thread Timo Röhling
Forgot the URL. Sorry for all the noise. I promise to stop sending further emails now ;) https://github.com/google/googletest/pull/3376 -- ⢀⣴⠾⠻⢶⣦⠀ ╭╮ ⣾⠁⢠⠒⠀⣿⡁ │ Timo Röhling │ ⢿⡄⠘⠷⠚⠋⠀ │ 9B03 EBB9 8300

Bug#994419: libgtest-dev: missing dependency on libgmock-dev

2021-09-16 Thread Timo Röhling
for dependencies by default. It's building with CMake 3.18.4, which does not trigger the bug. -- ⢀⣴⠾⠻⢶⣦⠀ ╭╮ ⣾⠁⢠⠒⠀⣿⡁ │ Timo Röhling │ ⢿⡄⠘⠷⠚⠋⠀ │ 9B03 EBB9 8300 DF97 C2B1 23BF CC8C 6BDD 1403 F4CA

Bug#994419: libgtest-dev: missing dependency on libgmock-dev

2021-09-17 Thread Timo Röhling
Hi Steven, On Thu, 16 Sep 2021 08:15:31 +0200 Timo Röhling wrote: One alternative solution would be to patch the upstream CMake files and export GMock independently with their own GMockConfig.cmake and GMockTargets.cmake. Then, for backwards compatibility, you could add something like

Bug#990409: ca-cacert: should this package be removed?

2021-08-11 Thread Timo Röhling
valuable elsewhere. Cheers Timo -- ⢀⣴⠾⠻⢶⣦⠀ ╭╮ ⣾⠁⢠⠒⠀⣿⡁ │ Timo Röhling │ ⢿⡄⠘⠷⠚⠋⠀ │ 9B03 EBB9 8300 DF97 C2B1 23BF CC8C 6BDD 1403 F4CA

Bug#996956: libbenchmark-dev: libbenchmark_main.a has no actual object code

2021-10-21 Thread Timo Röhling
cc-ar) Cheers Timo -- ⢀⣴⠾⠻⢶⣦⠀ ╭────╮ ⣾⠁⢠⠒⠀⣿⡁ │ Timo Röhling │ ⢿⡄⠘⠷⠚⠋⠀ │ 9B03 EBB9 8300 DF97 C2B1 23BF CC8C 6BDD 1403 F4CA │ ⠈⠳⣄ ╰╯ signature.asc Description: PGP signature

Bug#996956: libbenchmark-dev: libbenchmark_main.a has no actual object code

2021-10-21 Thread Timo Röhling
builds. Cheers Timo -- ⢀⣴⠾⠻⢶⣦⠀ ╭────╮ ⣾⠁⢠⠒⠀⣿⡁ │ Timo Röhling │ ⢿⡄⠘⠷⠚⠋⠀ │ 9B03 EBB9 8300 DF97 C2B1 23BF CC8C 6BDD 1403 F4CA │ ⠈⠳⣄ ╰╯ signature.asc Description: PGP signature

Bug#996799: twitterwatch: unusable with tweepy version 4

2021-10-18 Thread Timo Röhling
the package work again. Cheers Timo PS. You may also want to update d/watch to point to the new upstream repository at https://gitlab.com/chaica/twitterwatch -- ⢀⣴⠾⠻⢶⣦⠀ ╭╮ ⣾⠁⢠⠒⠀⣿⡁ │ Timo Röhling

Bug#996800: retweet: unusable with tweepy version 4

2021-10-18 Thread Timo Röhling
main.py:53 to make it work again. Cheers Timo PS. You may also want to update d/watch to point to the new upstream repository at https://gitlab.com/chaica/retweet -- ⢀⣴⠾⠻⢶⣦⠀ ╭╮ ⣾⠁⢠⠒⠀⣿⡁ │ Timo Röhling

Bug#996801: db2twitter: unusable with tweepy version 4

2021-10-18 Thread Timo Röhling
-- ⢀⣴⠾⠻⢶⣦⠀ ╭╮ ⣾⠁⢠⠒⠀⣿⡁ │ Timo Röhling │ ⢿⡄⠘⠷⠚⠋⠀ │ 9B03 EBB9 8300 DF97 C2B1 23BF CC8C 6BDD 1403 F4CA │ ⠈⠳⣄ ╰╯ signature.asc Description: PGP signature

Bug#1001002: marked as pending in hg-git

2021-12-06 Thread Timo Röhling
Control: tag -1 pending Hello, Bug #1001002 in hg-git 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:

Bug#997504: terminator: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13

2021-11-05 Thread Timo Röhling
() #33 0x0044bd4d in ?? () #34 0x005e8209 in Py_BytesMain () #35 0x77c58e4a in __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6 #36 0x005e810a in _start () Cheers Timo -- ⢀⣴⠾⠻⢶⣦⠀ ╭───────

Bug#994419: fixed in googletest 1.11.0-2

2021-11-05 Thread Timo Röhling
Hi Steve, On Sun, 19 Sep 2021 19:20:43 + Debian FTP Masters wrote: googletest (1.11.0-2) unstable; urgency=medium . [ Timo Röhling ] * [d803038] Separate GTest and GMock targets in CMake (Closes: #994419) . Shouldn't we also fix this in Bullseye via stable-updates? Cheers Timo

Bug#997846: marked as pending in httpbin

2021-12-11 Thread Timo Röhling
Control: tag -1 pending Hello, Bug #997846 in httpbin 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:

Bug#933100: marked as pending in hg-git

2021-07-18 Thread Timo Röhling
Control: tag -1 pending Hello, Bug #933100 in hg-git 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:

Bug#1006066: marked as pending in hg-git

2022-02-21 Thread Timo Röhling
Control: tag -1 pending Hello, Bug #1006066 in hg-git 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:

Bug#1052910: marked as pending in exhale

2023-10-11 Thread Timo Röhling
Control: tag -1 pending Hello, Bug #1052910 in exhale 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:

Bug#1052766: marked as pending in python-pytest-flake8

2023-10-15 Thread Timo Röhling
Control: tag -1 pending Hello, Bug #1052766 in python-pytest-flake8 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:

Bug#1054830: python-laspy: FTBFS: make: *** [debian/rules:11: binary] Error 25

2023-10-27 Thread Timo Röhling
CHANGELOG.rst && PYTHONPATH=/<>/.pybuild/cpython3_3.11_laspy/build python3.11 -m sphinx -b html . /<>/debian/python-laspy-doc/usr/share/doc/python-laspy-doc/html Cheers Timo -- ⢀⣴⠾⠻⢶⣦⠀ ╭────────╮ ⣾⠁⢠⠒⠀⣿⡁ │ Timo Röhling

Bug#1051435: upstream fix committed

2023-09-19 Thread Timo Röhling
Control: tags -1 + patch fixed-upstream Hi again, On Wed, 13 Sep 2023 16:17:59 +0200 Timo Röhling wrote: Unfortunately, this bug is *not* resolved; it looks like this is not a false positive but the subclass case which is explicitly mentioned in the documentation: Upstream has fixed

Bug#1052904: marked as pending in pytest-mock

2023-10-13 Thread Timo Röhling
Control: tag -1 pending Hello, Bug #1052904 in pytest-mock 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:

Bug#1052742: marked as pending in fastdds

2023-10-24 Thread Timo Röhling
Control: tag -1 pending Hello, Bug #1052742 in fastdds 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:

Bug#1054163: marked as pending in fastdds

2023-10-24 Thread Timo Röhling
Control: tag -1 pending Hello, Bug #1054163 in fastdds 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:

Bug#1050506: [Pkg-cmake-team] Bug#1050506: Could NOT find EXPAT (missing: EXPAT_LIBRARY) (found version "2.5.0")

2023-08-25 Thread Timo Röhling
VERSION that fixes your problem? Also, why do you think this is a CMake issue and not a VTK issue? I see the error originating in VTK's FindEXPAT.cmake in VTK, not the one shipped in CMake. Cheers Timo -- ⢀⣴⠾⠻⢶⣦⠀ ╭╮ ⣾⠁⢠⠒⠀⣿⡁ │ Timo Röhling

Bug#1005500: NMU upload pending

2022-04-21 Thread Timo Röhling
Hi, I took the liberty to massage the PR to apply cleanly to version 2.4.8 and uploaded the fix. Cheers Timo -- ⢀⣴⠾⠻⢶⣦⠀ ╭╮ ⣾⠁⢠⠒⠀⣿⡁ │ Timo Röhling │ ⢿⡄⠘⠷⠚⠋⠀ │ 9B03 EBB9 8300 DF97 C2B1 23BF CC8C

Bug#1011793: closing 1011793

2022-06-23 Thread Timo Röhling
close 1011793 0.18.0~b1-1 thanks The bug in Python seems to be resolved, the package no longer FTBFS. -- ⢀⣴⠾⠻⢶⣦⠀ ╭────────────────────────────────────────────────────╮

Bug#1011443: faker,ruby-faker: error when trying to install together

2022-07-05 Thread Timo Röhling
-- ⢀⣴⠾⠻⢶⣦⠀ ╭╮ ⣾⠁⢠⠒⠀⣿⡁ │ Timo Röhling │ ⢿⡄⠘⠷⠚⠋⠀ │ 9B03 EBB9 8300 DF97 C2B1 23BF CC8C 6BDD 1403 F4CA │ ⠈⠳⣄ ╰╯ signature.asc Description: PGP signature

Bug#1013704: closing 1013704

2022-07-01 Thread Timo Röhling
close 1013704 1.5.26+ds-1 thanks Hi, I believe this bug has been fixed with the new upstream version. Cheers Timo -- ⢀⣴⠾⠻⢶⣦⠀

Bug#1011714: gitless: FTBFS: ValueError: invalid argument: 'file || path'

2022-06-22 Thread Timo Röhling
s is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log an

Bug#1004587: marked as pending in pyglet

2022-07-06 Thread Timo Röhling
Control: tag -1 pending Hello, Bug #1004587 in pyglet 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:

Bug#1004587: closed by Debian FTP Masters (reply to Timo Röhling ) (Bug#1004587: fixed in pyglet 1.5.26+ds-1)

2022-07-06 Thread Timo Röhling
-- ⢀⣴⠾⠻⢶⣦⠀ ╭╮ ⣾⠁⢠⠒⠀⣿⡁ │ Timo Röhling │ ⢿⡄⠘⠷⠚⠋⠀ │ 9B03 EBB9 8300 DF97 C2B1 23BF CC8C 6BDD 1403 F4CA │ ⠈⠳⣄ ╰╯ signature.asc Description: PGP signature

Bug#1011714: marked as pending in python-pygit2

2022-06-22 Thread Timo Röhling
Control: tag -1 pending Hello, Bug #1011714 in python-pygit2 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:

Bug#1015060: closing 1015060

2022-08-01 Thread Timo Röhling
close 1015060 0.2.4.7-0.2 thanks The bug has been fixed but was not properly marked as closed in the .changes file. -- ⢀⣴⠾⠻⢶⣦⠀

Bug#1021882: marked as pending in ros2-rosidl

2022-10-16 Thread Timo Röhling
Control: tag -1 pending Hello, Bug #1021882 in ros2-rosidl 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:

Bug#1021882: marked as pending in ros2-rosidl

2022-10-16 Thread Timo Röhling
Control: tag -1 pending Hello, Bug #1021882 in ros2-rosidl 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:

Bug#1020118: reassign 1020118 to python3-ament-flake8, reassign 1020128 to python3-ament-flake8 ...

2022-09-18 Thread Timo Röhling
reassign 1020118 python3-ament-flake8 0.13.1-2 reassign 1020128 python3-ament-flake8 0.13.1-2 forcemerge 1020118 1020128 affects 1020118 src:ros2-ament-cmake-ros affects 1020118 src:ros2-ament-cmake-index retitle 1020118 python3-ament-flake8: incompatible with flake8 >= 5.0.0 close 1020118

Bug#993515: bullseye is not affected

2022-10-14 Thread Timo Röhling
Control: tags -1 + bookworm sid As bullseye is not affected as it will never upgrade to glibc 2.34, I'm setting release tags to exclude this bug from stable and allow the bug to be archived. Cheers Timo -- ⢀⣴⠾⠻⢶⣦⠀ ╭╮ ⣾⠁⢠⠒⠀⣿⡁ │ Timo

Bug#1013495: asio: FTBFS: dh_auto_test: error: make -j8 check "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2

2022-07-31 Thread Timo Röhling
with libssl-dev 3.0.5-1 works fine). Cheers Timo -- ⢀⣴⠾⠻⢶⣦⠀ ╭╮ ⣾⠁⢠⠒⠀⣿⡁ │ Timo Röhling │ ⢿⡄⠘⠷⠚⠋⠀ │ 9B03 EBB9 8300 DF97 C2B1 23BF CC8C 6BDD 1403 F4CA

Bug#993515: catch: FTBFS with glibc 2.34 - are Tags: fixed-upstream, patch correct and if yes any chance to upload this soon?

2022-08-08 Thread Timo Röhling
it shortly. Cheers Timo -- ⢀⣴⠾⠻⢶⣦⠀ ╭╮ ⣾⠁⢠⠒⠀⣿⡁ │ Timo Röhling │ ⢿⡄⠘⠷⠚⠋⠀ │ 9B03 EBB9 8300 DF97 C2B1 23BF CC8C 6BDD 1403 F4CA

Bug#1017596: openrct2: FTBFS with warnings as errors

2022-08-18 Thread Timo Röhling
:75:98: /usr/include/c++/12/streambuf:493:30: error: potential null pointer dereference [-Werror=null-dereference] 493 | egptr() const { return _M_in_end; } | ^ cc1plus: all warnings being treated as errors make[3]: *** [CMakeFiles/openrct2.dir/build.

Bug#1012898: assimp: diff for NMU version 5.2.4~ds0-1.1

2022-08-08 Thread Timo Röhling
I've prepared an NMU for assimp (versioned as 5.2.4~ds0-1.1) and uploaded it to DELAYED/2, going with the minimally invasive patch proposed by Pino Toscano. Cheers -- ⢀⣴⠾⠻⢶⣦⠀ ╭╮ ⣾⠁⢠⠒⠀⣿⡁ │ Timo Röhling

Bug#1026021: pytest-forked: FTBFS with pytest 7.2

2022-12-22 Thread Timo Röhling
, so I'm fine waiting for upstream to have a proper release soon(ish). Cheers Timo -- ⢀⣴⠾⠻⢶⣦⠀ ╭╮ ⣾⠁⢠⠒⠀⣿⡁ │ Timo Röhling │ ⢿⡄⠘⠷⠚⠋⠀ │ 9B03 EBB9 8300 DF97 C2B1 23BF CC8C 6BDD 1403 F4CA

Bug#1026705: python-pecan: FTBFS: E AttributeError: 'code' object has no attribute 'co_endlinetable'

2022-12-28 Thread Timo Röhling
s bug comes from python3-kajiki and is fixed in the latest upstream release 0.9.2 Cheers Timo -- ⢀⣴⠾⠻⢶⣦⠀ ╭╮ ⣾⠁⢠⠒⠀⣿⡁ │ Timo Röhling │ ⢿⡄⠘⠷⠚⠋⠀ │ 9B03 EBB9 8300 DF97 C2B1 23BF CC8C 6BDD 1403 F4CA │ ⠈⠳⣄ ╰╯ signature.asc Description: PGP signature

Bug#1027751: marked as pending in pytest

2023-01-02 Thread Timo Röhling
Control: tag -1 pending Hello, Bug #1027751 in pytest 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:

Bug#1027751: need to properly depend on python3-exceptiongroup

2023-01-02 Thread Timo Röhling
thon bug, because dh-python generates the wrong dependency as long as Python 3.10 is still in the archive ;) The dependency python3-exceptiongroup was added with pytest 7.2.0, btw (I fixed the affected version). Cheers Timo -- ⢀⣴⠾⠻⢶⣦⠀ ╭─────

Bug#1027909: marked as pending in golang-github-libgit2-git2go

2023-01-05 Thread Timo Röhling
Control: tag -1 pending Hello, Bug #1027909 in golang-github-libgit2-git2go 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:

Bug#1027947: python3-setuptools-scm: needs depend on python3-tomli during Python 3.11 transition

2023-01-04 Thread Timo Röhling
Package: python3-setuptools-scm Version: 7.1.0-1 Severity: serious Justification: missing dependency causes FTBFS in unrelated packages -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer, python3-setuptools-scm has a 'python3-tomli || python3 (>> 3.11)' dependency, which breaks

Bug#1026021: pytest-forked: FTBFS with pytest 7.2

2023-01-02 Thread Timo Röhling
* Timo Röhling [2022-12-22 20:17]: No problem. I found your PR in the mean time (better than my hotfix btw), and pytest still has a few other regressions anyway, so I'm fine waiting for upstream to have a proper release soon(ish). Any progress with the release? The other pytest regressions

Bug#1026207: python-ase: autopkgtest regression because test functions return values

2022-12-16 Thread Timo Röhling
Source: python-ase Version: 3.22.1-2 Severity: serious Control: affects -1 src:pytest -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainers, the autopkgtest of your package started failing because some of the tests return values. This has always been incorrect (tests are expected to

Bug#1026210: scipy: autopkgtest regression due to invalid test function returns

2022-12-16 Thread Timo Röhling
Source: scipy Version: 1.8.1-14 Severity: serious Control: affects -1 src:pytest -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainers, the autopkgtest of your package started failing because some of the tests return values. This has always been incorrect (tests are expected to

Bug#1026024: specutils: FTBFS, ModuleNotFoundError: No module named 'asdf_astropy.io'

2022-12-13 Thread Timo Röhling
Source: specutils Version: 1.9.0-2 Severity: serious Tags: ftbfs -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer, your package has a FTBFS regression, presumably because of a missing dependency. Relevant build log excerpt: dh_auto_test -O--buildsystem=pybuild I: pybuild

Bug#1026021: pytest-forked: FTBFS with pytest 7.2

2022-12-13 Thread Timo Röhling
Source: pytest-forked Version: 1.4.0-1 Severity: serious Tags: ftbfs patch -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer, your package FTBFS with pytest 7.2; the test summary has been augmented with a reason, which is not captured by test_xfail_behavior.py: Relevant excerpt

Bug#1026020: python3-starlette: starlette.testclient requires module httpx

2022-12-13 Thread Timo Röhling
Package: python3-starlette Version: 0.23.1-1 Severity: serious Control: affects -1 src:ormar -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer, your package does not depend on python3-httpx, which causes the build (and the autopkgtest) of src:ormar to fail. Presumbably, this

Bug#1026155: python3-trio: MultiError implementation conflicts with BaseExceptionGroup backport in Python 3.10

2022-12-15 Thread Timo Röhling
Package: python3-trio Version: 0.21.0-1 Severity: serious Tags: fixed-upstream Control: affects -1 src:ipykernel -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer, your package conflicts with the BaseExceptionGroup backport from python3-exceptiongroup, which will cause ipykernel

Bug#1026690: marked as pending in pyglet

2022-12-21 Thread Timo Röhling
Control: tag -1 pending Hello, Bug #1026690 in pyglet 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:

Bug#1026660: closing 1026660

2022-12-21 Thread Timo Röhling
close 1026660 4.2.0-1 thanks Hi Lucas, this is already fixed by the recent upload of the new upstream release. Cheers Timo -- ⢀⣴⠾⠻⢶⣦⠀

Bug#1023806: marked as pending in hg-git

2022-12-09 Thread Timo Röhling
Control: tag -1 pending Hello, Bug #1023806 in hg-git 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:

Bug#1024786: marked as pending in aionotify

2022-12-10 Thread Timo Röhling
Control: tag -1 pending Hello, Bug #1024786 in aionotify 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:

Bug#1025018: marked as pending in python-aiomeasures

2022-12-10 Thread Timo Röhling
Control: tag -1 pending Hello, Bug #1025018 in python-aiomeasures 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:

Bug#1026012: astropy-healpix: FTBFS because of failing test suite

2022-12-13 Thread Timo Röhling
Source: astropy-healpix Version: 0.6-1 Severity: serious Tags: ftbfs -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainers, the new python-hypothesis 6.60 apparently exposed a bug in your package, causing it to FTBFS and fail the autopkgtest. Relevant excerpt from the build log:

Bug#1023767: neomutt: unable to find gpgme-config

2022-11-23 Thread Timo Röhling
-- ⢀⣴⠾⠻⢶⣦⠀ ╭╮ ⣾⠁⢠⠒⠀⣿⡁ │ Timo Röhling │ ⢿⡄⠘⠷⠚⠋⠀ │ 9B03 EBB9 8300 DF97 C2B1 23BF CC8C 6BDD 1403 F4CA │ ⠈⠳⣄ ╰╯ signature.asc Description: PGP signature

Bug#1023767: neomutt: unable to find gpgme-config

2022-11-22 Thread Timo Röhling
). I have built neomutt with your patch and can confirm that the GPGme integration works as expected. Cheers Timo -- ⢀⣴⠾⠻⢶⣦⠀ ╭╮ ⣾⠁⢠⠒⠀⣿⡁ │ Timo Röhling │ ⢿⡄⠘⠷⠚⠋⠀ │ 9B03 EBB9 8300 DF97 C2B1 23BF CC8C 6BDD

Bug#1029503: spirv-cross: new upstream release breaks API

2023-01-23 Thread Timo Röhling
Source: spirv-cross Version: 2021.01.15+1.3.236.0-1 Severity: serious Tags: ftbfs -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear co-maintainers, the recent upload of spirv-cross 2021.01.15+1.3.236.0-1 has incompatible API changes which break reverse dependencies, notably src:filament.

Bug#1029282: marked as pending in hg-git

2023-01-20 Thread Timo Röhling
Control: tag -1 pending Hello, Bug #1029282 in hg-git 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:

Bug#1029302: python-mox: obsolete, rc-buggy, should be removed

2023-01-20 Thread Timo Röhling
Source: python-mox Version: 0.7.8-5 Severity: serious User: debian...@lists.debian.org Usertags: proposed-removal -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi, python3-mox has no reverse dependencies, last upstream activity is from 2018, the package is RC-buggy and there are plenty of

Bug#1029302: python-mox: obsolete, rc-buggy, should be removed

2023-01-20 Thread Timo Röhling
to reassign and retitle it. Cheers Timo -- ⢀⣴⠾⠻⢶⣦⠀ ╭╮ ⣾⠁⢠⠒⠀⣿⡁ │ Timo Röhling │ ⢿⡄⠘⠷⠚⠋⠀ │ 9B03 EBB9 8300 DF97 C2B1 23BF CC8C 6BDD 1403 F4CA

Bug#1026549: bug 1026549 is forwarded to https://github.com/pytest-dev/pytest-xprocess/issues/117, tagging 1026549

2023-01-28 Thread Timo Röhling
-pytest-xprocess/-/merge_requests/1 Unless advised otherwise, I intend to upload the updated package tomorrow. I have no objections. Happy bug squashing! Cheers Timo -- ⢀⣴⠾⠻⢶⣦⠀ ╭╮ ⣾⠁⢠⠒⠀⣿⡁ │ Timo Röhling

Bug#1023767: neomutt: unable to find gpgme-config

2022-11-09 Thread Timo Röhling
Source: neomutt Version: 20220429+dfsg1-4 Severity: serious Tags: ftbfs fixed-upstream -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainers, neomutt fails to build with the recent libgpgme-dev update that dropped the gpgme-config executable.

Bug#1030233: marked as pending in python-hypothesis

2023-02-01 Thread Timo Röhling
Control: tag -1 pending Hello, Bug #1030233 in python-hypothesis 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:

Bug#1031435: python-inotify: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13

2023-02-17 Thread Timo Röhling
work around it? Cheers Timo -- ⢀⣴⠾⠻⢶⣦⠀ ╭────╮ ⣾⠁⢠⠒⠀⣿⡁ │ Timo Röhling │ ⢿⡄⠘⠷⠚⠋⠀ │ 9B03 EBB9 8300 DF97 C2B1 23BF CC8C 6BDD 1403 F4CA │ ⠈⠳⣄ ╰╯

Bug#1030493: marked as pending in python-patch

2023-02-06 Thread Timo Röhling
Control: tag -1 pending Hello, Bug #1030493 in python-patch 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:

Bug#1040576: python-mongomock: implicitly depends on python3-pkg-resources

2023-07-07 Thread Timo Röhling
Source: python-mongomock Version: 4.1.2-1 Severity: serious -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer, your package implicitly depends on python3-pkg-resources for its autopkgtest, which used to be provided through python3-pytest. However, pytest has dropped that

Bug#1040578: python-molotov: implicitly depends on python3-pkg-resources

2023-07-07 Thread Timo Röhling
Source: python-molotov Version: 2.1-5 Severity: serious -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer, your package implicitly depends on python3-pkg-resources for its autopkgtest, which used to be provided through python3-pytest. However, pytest has dropped that dependency,

Bug#1040581: mdp: implicitly depends on python3-py

2023-07-07 Thread Timo Röhling
Source: mdp Version: 3.6-2 Severity: serious -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer, your package implicitly depends on python3-py for its autopkgtest, which used to be provided by python3-pytest. However, pytest has dropped that dependency, breaking your autopkgtest

Bug#1040571: segno: implicitly depends on python3-pkg-resources

2023-07-07 Thread Timo Röhling
Source: segno Version: 1.5.2-2 Severity: serious -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer, your package implicitly depends on python3-pkg-resources for its autopkgtest, which used to be provided through python3-pytest. However, pytest has dropped that dependency,

Bug#1040573: python-screed: implicitly depends on python3-pkg-resources

2023-07-07 Thread Timo Röhling
Source: python-screed Version: 1.0.5-4 Severity: serious -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer, your package implicitly depends on python3-pkg-resources for its autopkgtest, which used to be provided through python3-pytest. However, pytest has dropped that dependency,

Bug#1040574: python-qrcode: implicitly depends on python3-pkg-resources

2023-07-07 Thread Timo Röhling
Source: python-qrcode Version: 7.4.2-2 Severity: serious -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer, your package implicitly depends on python3-pkg-resources for its autopkgtest, which used to be provided through python3-pytest. However, pytest has dropped that dependency,

Bug#1040580: oz: implicitly depends on python3-py

2023-07-07 Thread Timo Röhling
Source: oz Version: 0.17.0-5.1 Severity: serious -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer, your package implicitly depends on python3-py for its autopkgtest, which used to be provided by python3-pytest. However, pytest has dropped that dependency, breaking your

Bug#1040583: execnet: implicitly depends on python3-py

2023-07-07 Thread Timo Röhling
* Scott Talbert [2023-07-07 14:40]: On Fri, 7 Jul 2023, Timo Röhling wrote: Source: execnet Version: 1.9.0-2 Severity: serious -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 [Scott: Apologies that I missed this earlier, and thanks for fixing apipkg so quickly] Hey Timo, I already fixed

Bug#1040568: weresync: implicitly depends on python3-py

2023-07-07 Thread Timo Röhling
Source: weresync Version: 1.0.9-2 Severity: serious -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer, your package implicitly depends on python3-py for its autopkgtest, which used to be provided by python3-pytest. However, pytest has dropped that dependency, breaking your

Bug#1040579: python-gflanguages: implicitly depends on python3-pkg-resources

2023-07-07 Thread Timo Röhling
Source: python-gflanguages Version: 0.4.0-2 Severity: serious -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer, your package implicitly depends on python3-pkg-resources for its autopkgtest, which used to be provided through python3-pytest. However, pytest has dropped that

Bug#1040583: execnet: implicitly depends on python3-py

2023-07-07 Thread Timo Röhling
Source: execnet Version: 1.9.0-2 Severity: serious -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 [Scott: Apologies that I missed this earlier, and thanks for fixing apipkg so quickly] Dear maintainer, your package implicitly depends on python3-py for its autopkgtest, which used to be

Bug#1040574: marked as pending in python-qrcode

2023-07-12 Thread Timo Röhling
Control: tag -1 pending Hello, Bug #1040574 in python-qrcode 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:

Bug#1040576: marked as pending in python-mongomock

2023-07-12 Thread Timo Röhling
Control: tag -1 pending Hello, Bug #1040576 in python-mongomock 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:

  1   2   >