Bug#1066032: marked as done (pygobject: FTBFS on armhf: time_t build test failure)

2024-05-04 Thread Debian Bug Tracking System
Your message dated Sat, 04 May 2024 16:50:02 +
with message-id 
and subject line Bug#1066032: fixed in gobject-introspection 1.80.1-2
has caused the Debian Bug report #1066032,
regarding pygobject: FTBFS on armhf: time_t build test failure
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1066032: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066032
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pygobject
Version: 3.47.0-3
Severity: serious
Tags: unstable trixie ftbfs
User: debian-...@lists.debian.org
Usertags: time-t

Although Debian has not yet gotten to pygobject in the time_t
transition for armel/armhf, Ubuntu has and experienced a build test
failure in test_gi.py for the test_time_t tests which I believe are
using functions in glib2.0. I assume Debian also experiences this
issue.

Test log excerpt

tests/test_gi.py ... [ 21%]
.
--- stderr ---
Fatal Python error: Aborted

Current thread 0xf785e020 (most recent call first):
  File "/<>/tests/test_gi.py", line 579 in test_time_t_in
  File "/usr/lib/python3.12/unittest/case.py", line 589 in _callTestMethod
  File "/usr/lib/python3.12/unittest/case.py", line 634 in run
  File "/usr/lib/python3.12/unittest/case.py", line 690 in __call__
  File "/usr/lib/python3/dist-packages/_pytest/unittest.py", line 338 in runtest
  File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 170 in
pytest_runtest_call
  File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 102
in _multicall
  File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 119
in _hookexec
  File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 501 in __call__
  File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 263 in 
  File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 342 in from_call
  File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 262 in
call_runtest_hook
  File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 223 in
call_and_report
  File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 134 in
runtestprotocol
  File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 115 in
pytest_runtest_protocol
  File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 102
in _multicall
  File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 119
in _hookexec
  File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 501 in __call__
  File "/usr/lib/python3/dist-packages/_pytest/main.py", line 352 in
pytest_runtestloop
  File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 102
in _multicall
  File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 119
in _hookexec
  File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 501 in __call__
  File "/usr/lib/python3/dist-packages/_pytest/main.py", line 327 in _main
  File "/usr/lib/python3/dist-packages/_pytest/main.py", line 273 in
wrap_session
  File "/usr/lib/python3/dist-packages/_pytest/main.py", line 320 in
pytest_cmdline_main
  File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 102
in _multicall
  File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 119
in _hookexec
  File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 501 in __call__
  File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py",
line 175 in main
  File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py",
line 198 in console_main
  File "/usr/lib/python3/dist-packages/pytest/__main__.py", line 7 in 
  File "", line 88 in _run_code
  File "", line 198 in _run_module_as_main

Full build log
==
https://launchpad.net/ubuntu/+source/pygobject/3.47.0-3build1/+latestbuild/armhf

Originally reported at https://launchpad.net/bugs/2056753

Thank you,
Jeremy Bícha
--- End Message ---
--- Begin Message ---
Source: gobject-introspection
Source-Version: 1.80.1-2
Done: Jeremy Bícha 

We believe that the bug you reported is fixed in the latest version of
gobject-introspection, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1066...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jeremy Bícha  (supplier of updated gobject-introspection 
package)

(This message was 

Bug#1066032: marked as done (pygobject: FTBFS on armhf: time_t build test failure)

2024-03-18 Thread Debian Bug Tracking System
Your message dated Tue, 19 Mar 2024 00:38:35 +
with message-id 
and subject line Bug#1066032: fixed in gobject-introspection 1.80.0-2
has caused the Debian Bug report #1066032,
regarding pygobject: FTBFS on armhf: time_t build test failure
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1066032: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066032
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pygobject
Version: 3.47.0-3
Severity: serious
Tags: unstable trixie ftbfs
User: debian-...@lists.debian.org
Usertags: time-t

Although Debian has not yet gotten to pygobject in the time_t
transition for armel/armhf, Ubuntu has and experienced a build test
failure in test_gi.py for the test_time_t tests which I believe are
using functions in glib2.0. I assume Debian also experiences this
issue.

Test log excerpt

tests/test_gi.py ... [ 21%]
.
--- stderr ---
Fatal Python error: Aborted

Current thread 0xf785e020 (most recent call first):
  File "/<>/tests/test_gi.py", line 579 in test_time_t_in
  File "/usr/lib/python3.12/unittest/case.py", line 589 in _callTestMethod
  File "/usr/lib/python3.12/unittest/case.py", line 634 in run
  File "/usr/lib/python3.12/unittest/case.py", line 690 in __call__
  File "/usr/lib/python3/dist-packages/_pytest/unittest.py", line 338 in runtest
  File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 170 in
pytest_runtest_call
  File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 102
in _multicall
  File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 119
in _hookexec
  File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 501 in __call__
  File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 263 in 
  File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 342 in from_call
  File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 262 in
call_runtest_hook
  File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 223 in
call_and_report
  File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 134 in
runtestprotocol
  File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 115 in
pytest_runtest_protocol
  File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 102
in _multicall
  File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 119
in _hookexec
  File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 501 in __call__
  File "/usr/lib/python3/dist-packages/_pytest/main.py", line 352 in
pytest_runtestloop
  File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 102
in _multicall
  File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 119
in _hookexec
  File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 501 in __call__
  File "/usr/lib/python3/dist-packages/_pytest/main.py", line 327 in _main
  File "/usr/lib/python3/dist-packages/_pytest/main.py", line 273 in
wrap_session
  File "/usr/lib/python3/dist-packages/_pytest/main.py", line 320 in
pytest_cmdline_main
  File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 102
in _multicall
  File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 119
in _hookexec
  File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 501 in __call__
  File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py",
line 175 in main
  File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py",
line 198 in console_main
  File "/usr/lib/python3/dist-packages/pytest/__main__.py", line 7 in 
  File "", line 88 in _run_code
  File "", line 198 in _run_module_as_main

Full build log
==
https://launchpad.net/ubuntu/+source/pygobject/3.47.0-3build1/+latestbuild/armhf

Originally reported at https://launchpad.net/bugs/2056753

Thank you,
Jeremy Bícha
--- End Message ---
--- Begin Message ---
Source: gobject-introspection
Source-Version: 1.80.0-2
Done: Simon McVittie 

We believe that the bug you reported is fixed in the latest version of
gobject-introspection, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1066...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Simon McVittie  (supplier of updated gobject-introspection 
package)

(This message was 

Bug#1066032: marked as done (pygobject: FTBFS on armhf: time_t build test failure)

2024-03-18 Thread Debian Bug Tracking System
Your message dated Mon, 18 Mar 2024 13:50:23 +
with message-id 
and subject line Bug#1066032: fixed in gobject-introspection 1.78.1-18
has caused the Debian Bug report #1066032,
regarding pygobject: FTBFS on armhf: time_t build test failure
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1066032: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066032
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pygobject
Version: 3.47.0-3
Severity: serious
Tags: unstable trixie ftbfs
User: debian-...@lists.debian.org
Usertags: time-t

Although Debian has not yet gotten to pygobject in the time_t
transition for armel/armhf, Ubuntu has and experienced a build test
failure in test_gi.py for the test_time_t tests which I believe are
using functions in glib2.0. I assume Debian also experiences this
issue.

Test log excerpt

tests/test_gi.py ... [ 21%]
.
--- stderr ---
Fatal Python error: Aborted

Current thread 0xf785e020 (most recent call first):
  File "/<>/tests/test_gi.py", line 579 in test_time_t_in
  File "/usr/lib/python3.12/unittest/case.py", line 589 in _callTestMethod
  File "/usr/lib/python3.12/unittest/case.py", line 634 in run
  File "/usr/lib/python3.12/unittest/case.py", line 690 in __call__
  File "/usr/lib/python3/dist-packages/_pytest/unittest.py", line 338 in runtest
  File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 170 in
pytest_runtest_call
  File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 102
in _multicall
  File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 119
in _hookexec
  File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 501 in __call__
  File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 263 in 
  File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 342 in from_call
  File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 262 in
call_runtest_hook
  File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 223 in
call_and_report
  File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 134 in
runtestprotocol
  File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 115 in
pytest_runtest_protocol
  File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 102
in _multicall
  File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 119
in _hookexec
  File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 501 in __call__
  File "/usr/lib/python3/dist-packages/_pytest/main.py", line 352 in
pytest_runtestloop
  File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 102
in _multicall
  File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 119
in _hookexec
  File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 501 in __call__
  File "/usr/lib/python3/dist-packages/_pytest/main.py", line 327 in _main
  File "/usr/lib/python3/dist-packages/_pytest/main.py", line 273 in
wrap_session
  File "/usr/lib/python3/dist-packages/_pytest/main.py", line 320 in
pytest_cmdline_main
  File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 102
in _multicall
  File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 119
in _hookexec
  File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 501 in __call__
  File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py",
line 175 in main
  File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py",
line 198 in console_main
  File "/usr/lib/python3/dist-packages/pytest/__main__.py", line 7 in 
  File "", line 88 in _run_code
  File "", line 198 in _run_module_as_main

Full build log
==
https://launchpad.net/ubuntu/+source/pygobject/3.47.0-3build1/+latestbuild/armhf

Originally reported at https://launchpad.net/bugs/2056753

Thank you,
Jeremy Bícha
--- End Message ---
--- Begin Message ---
Source: gobject-introspection
Source-Version: 1.78.1-18
Done: Simon McVittie 

We believe that the bug you reported is fixed in the latest version of
gobject-introspection, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1066...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Simon McVittie  (supplier of updated gobject-introspection 
package)

(This message was