El 2/3/25 a las 20:10, Santiago Vila escribió:
and the output which follows should also be changed because otherwise
this is what it may happen:
libgsettings-qt-dev:amd64 1.0.0-2 -> 1.0.0-1+b1
libgsettings-qt1:amd64 1.0.0-2 -> 1.0.0-1+b1
linux-libc-dev 6.12.17-1 -> 6.12.16-1
that's weird because the arrow (->) represents time which is better
to consider as always going forward.
Note: I've fixed that in the MR and now the output for the above
test case is like this:
the following packages differ between the last bad and first good timestamp:
libgsettings-qt-dev:amd64 1.0.0-1+b1 -> 1.0.0-2
libgsettings-qt1:amd64 1.0.0-1+b1 -> 1.0.0-2
linux-libc-dev 6.12.16-1 -> 6.12.17-1
(btw: I'm trying to avoid code duplication, so I hope you
like the v[::-1] trick :-)
Now I'm going to see if I can test (and fix if required)
the code following that. i.e. the "try to figure out the
exact package that introduce the break" part.
Thanks.
