Gesendet: Donnerstag, 10. Juni 2021 um 13:34 Uhr Von: "Gerald Pfeifer" <gp@suse.com> An: factory@lists.opensuse.org Betreff: Re: Verification of the correct rpmlint-mini in a project
On Thu 2021-06-10, Dominique Leuenberger / DimStar wrote:
On Thu, 2021-06-10 at 11:04 +0200, Jan Engelhardt wrote:
Whenever glibc or gcc changes though, most things rebuild, and that should be sufficient number of times. Correct is: whenever glibc or gcc have major updates, we trigger a full rebuld. Or when the release mamnagers have other reasons to do full rebuilds (errors included)
Otherwise we'd have had 7 full rebuilds for glibc alone in 2021:
And as a user I am grateful we did not. :)
And I did not count, but the number of times in the last half year, year a `zypper dup` pulled in more than 600MB, or more than 1GB, felt high already. So definitely happy about the release managers limiting that.
Gerald
I want to add that I prefer such rebuildings (as a minimum) for all failed packages, updated packages and packages with dependencies to such updated packages (not for all). The background is that I was allowed to see many broken (and additionally old) packages, which were able to build after a manual rebuild. Additionally there were others (without any automatical rebuild) which a new rebuild has included additional packages for Python 3.9. That wasn't done before. So you were not able to use these packages with Python 3.9 until now. But I agree that it is not necessary for all packages (without any reason). Best regards, Sarah