On Sat, Sep 4, 2021 at 6:17 PM Jason Craig <os-dev@jacraig.com> wrote:
On 9/4/2021 8:39, Neal Gompa wrote:
On Sat, Sep 4, 2021 at 6:19 AM munix9 <munix9@googlemail.com> wrote:
Hi,
since recently a current rpmlint under Factory/TW on OBS leads to the fact that a final compare finds a difference and thus a new release is created, because the timing of rpmlint differs from the old build. Is this intentional and reasonable? ...
Yes, with how build-compare works today, it is. I certainly won't accept any bug reports caused by build-compare in upstream rpmlint.
New releases being created with no change whatsoever, only dependent on fractions of a second difference in rpmlint run time is "intentional and reasonable"? I can't speak to intent but that doesn't sound reasonable to me.
build-compare shouldn't be comparing the output of rpmlint that way in the first place. Since rpmlint is a standard Python application, build-compare should import rpmlint and do its own representation of the output in a more machine-friendly form. The time it takes to run through the package can also vary on a variety of factors, so using that as a knob to trigger publishing rebuilds is stupid. -- 真実はいつも一つ！/ Always, there's only one truth!