Marcus Meissner composed on 2017-04-16 14:52 (UTC+0200):
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
I don't understand what I'm looking at. It looks like: 1-osc = command 2-triggerreason = subcommand 3-openSUSE_Tumbleweed = ? reponame ? 4-x86_64 = arch What is Base:System/hello>? # Base:System/hello> osc triggerreason openSUSE_Tumbleweed x86_64 -bash: Base:System/hello: No such file or directory # osc triggerreason openSUSE_Tumbleweed x86_64 package is not specified. :-(
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-- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation)
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org