On Sun, Apr 16, 2017 at 06:07:48AM -0400, Felix Miata wrote:
Are there valid reasons to rebuild packages every 8-12 weeks even though no changes show up in their changelogs? If there are, what are some of them?
You can check on why a rebuild happened by using: osc triggerreason probably meta information of a dependency changed. So for Base:System/hello Base:System/hello> osc triggerreason openSUSE_Tumbleweed x86_64 meta change changed keys: added glibc-devel/shadow/libacl-devel/system-user-bin/libapparmor1 added glibc-devel/shadow/libacl-devel/system-user-bin/libicu57_1 added glibc-devel/shadow/libacl-devel/system-user-bin/libicu57_1-ledata added glibc-devel/shadow/libacl-devel/system-user-bin/libpsl5 added glibc-devel/shadow/libacl-devel/system-user-bin/libsasl2-3 added glibc-devel/shadow/libacl-devel/system-user-bin/timezone md5sum rpm-build/libacl-devel/system-user-bin/libapparmor1 removed rpm-build/libacl-devel/system-user-bin/libicu57_1 removed rpm-build/libacl-devel/system-user-bin/libicu57_1-ledata md5sum rpm-build/libacl-devel/system-user-bin/libpsl5 md5sum rpm-build/libacl-devel/system-user-bin/libsasl2-3 removed rpm-build/libacl-devel/system-user-bin/timezone Due to some other rebuilt packages, here glibc-devel mostly. Ciao, Marcus -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org