Your message dated Sat, 27 Dec 2025 19:08:30 -0300 with message-id <176687331085.321599.14177483755682589976@debian> and subject line python-molotov: autopkgtest failure on 32-bit and riscv64 has caused the Debian Bug report #1102543, regarding python-molotov: autopkgtest failure on 32-bit and riscv64 to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 1102543: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1102543 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Source: python-molotov Version: 2.7-2 Severity: serious https://tracker.debian.org/pkg/python-molotov Issues preventing migration: ∙ ∙ autopkgtest for python-molotov/2.7-2: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Pass, riscv64: Regression or new test ♻, s390x: Pass riscv64 is a timeout and this binary-all package might not be in a good shape on 32-bit. I would restrict the autopkgtest to the non-failing architectures.
--- End Message ---
--- Begin Message ---Version: 2.7-3 Hi, this bug was fixed. I forgot add it chanagelog. cheers, Emmanuel Arias ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ [email protected] ⢿⡄⠘⠷⠚⠋⠀ OpenPGP: 13796755BBC72BB8ABE2AEB5 FA9DEC5DE11C63F1 ⠈⠳⣄
--- End Message ---
