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?
eg. https://build.opensuse.org/package/live_build_log/home:munix9/android-tools/...
[ 400s] rpmlint.log files differ: [ 400s] --- /tmp/tmp.yUsDRbZz79 2021-09-04 10:10:33.236000000 +0000 [ 400s] +++ /tmp/tmp.CRk2h2aSLQ 2021-09-04 10:10:33.236000000 +0000 [ 400s] @@ -13,7 +13,7 @@ [ 400s] /opt/testing/share/rpmlint/security.toml [ 400s] /opt/testing/share/rpmlint/users-groups.toml [ 400s] /opt/testing/share/rpmlint/world-writable-whitelist.toml [ 400s] - 4 packages and 0 specfiles checked; 0 errors, 0 warnings, 0 badness; has taken 2.1 s [ 400s] + 4 packages and 0 specfiles checked; 0 errors, 0 warnings, 0 badness; has taken 2.2 s
Yes, with how build-compare works today, it is. I certainly won't accept any bug reports caused by build-compare in upstream rpmlint. -- 真実はいつも一つ！/ Always, there's only one truth!