diffoscope is marked for autoremoval from testing

2025-01-19 Thread Debian testing autoremoval watch
diffoscope 285 is marked for autoremoval from testing on 2025-02-18 It (build-)depends on packages with these RC bugs: 1091009: gnumeric: FTBFS: failed tests https://bugs.debian.org/1091009 1091430: pyside2: pyside2 FTBFS with Python 3.13 as default https://bugs.debian.org/1091430 1092080: pysid

Bug#1093412: Regression in tests with new faketime [and 1 more messages]

2025-01-19 Thread James Addison
On Sun, 19 Jan 2025 at 22:13, Ian Jackson wrote: > [ ... snip ... ] > So the upstream default has changed. This happened in 2d941a894f4d > "fixes #374 fix compiling without FAKE_STAT". The commit message does > not indicate that this change was intentional. > > I will revert this change in sid a

Bug#1093412: Regression in tests with new faketime

2025-01-19 Thread James Addison
On Sun, 19 Jan 2025 at 19:31, Ian Jackson wrote: > > Ian Jackson writes ("Re: Bug#1093412: Regression in tests with new faketime"): > > Why are we passing NO_FAKE_STAT here? > > > > Maybe the problem is that faketime isn't honouring NO_FAKE_STAT. > > I will see if I can confirm... > > (I should sa

Bug#1093412: Regression in tests with new faketime [and 1 more messages]

2025-01-19 Thread Ian Jackson
Ian Jackson writes ("Re: Bug#1093412: Regression in tests with new faketime"): > Why are we passing NO_FAKE_STAT here? I UTSL and in reprotest/build.py I see: # faketime's manpages are stupidly misleading; it also modifies file timestamps. # this is only mentioned in the README. we do no

Bug#1093412: Regression in tests with new faketime

2025-01-19 Thread Ian Jackson
Ian Jackson writes ("Re: Bug#1093412: Regression in tests with new faketime"): > Why are we passing NO_FAKE_STAT here? > > Maybe the problem is that faketime isn't honouring NO_FAKE_STAT. > I will see if I can confirm... (I should say, thanks for the lead!) -- Ian JacksonThese opinions are

Bug#1093412: Regression in tests with new faketime

2025-01-19 Thread Ian Jackson
James Addison writes ("Bug#1093412: Regression in tests with new faketime"): > Furthermore: performing a copy operation on a file from the source > when using faketime in debian:unstable appears to reduce the mtime of > the file by the delta duration each time a copy operation occurs: > > $ stat

Bug#1093412: Regression in tests with new faketime

2025-01-19 Thread James Addison
Package: reprotest Followup-For: Bug #1093412 X-Debbugs-Cc: ijack...@chiark.greenend.org.uk On Sun, 19 Jan 2025 16:26:27 +, I wrote: > The timestamps on files that are simply copied from the src package > into the binary package appear to have 331 hours _subtracted_ from > their original mtime

Bug#1093412: Regression in tests with new faketime

2025-01-19 Thread James Addison
Package: reprotest Followup-For: Bug #1093412 X-Debbugs-Cc: ijack...@chiark.greenend.org.uk Attached is diffoscope output for comparative reprotest-0.7.29 builds using Debian testing and stable respectively, both with faketime enabled with a +331h delta. The timestamps on files that are simply co

Bug#1093412: Regression in tests with new faketime

2025-01-19 Thread James Addison
Package: reprotest Followup-For: Bug #1093412 X-Debbugs-Cc: ijack...@chiark.greenend.org.uk When building reprotest-0.7.29 on debian:testing, with autopkgtests disabled and regardless of whether faketime is used, I am currently able to reliably repeat build a deb file with hash: $ DEB_BUILD_OPT

Bug#1093484: diffoscope: crash when processing IDEA CE distributions

2025-01-19 Thread Julien Plissonneau Duquène
Package: diffoscope Version: 285 Severity: normal X-Debbugs-Cc: sre4e...@free.fr Dear Maintainers, While trying to compare two versions of the IDEA CE upstream distribution diffoscope failed with the following errors: $