[opensuse-factory] packages with no changelog entries repeatedly rebuilt
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? -- "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
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
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
On Sun, Apr 16, 2017 at 10:47:59AM -0400, Felix Miata wrote:
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:
so usually: osc triggerreason PROJECT PACKAGE REPOSITORY ARCH so the package hello in Base:System: osc triggerreason Base:System hello openSUSE_Tumbleweed x86_64 What package in which project is affected? Ciao, Marcus -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Marcus Meissner composed on 2017-04-16 17:20 (UTC-+0200):
On Sun, Apr 16, 2017 at 10:47:59AM -0400, Felix Miata wrote:
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:
so usually: osc triggerreason PROJECT PACKAGE REPOSITORY ARCH
so the package hello in Base:System:
osc triggerreason Base:System hello openSUSE_Tumbleweed x86_64
What package in which project is affected?
Good questions: # zypse esr | egrep -v 'trans|build|randi' il | firefox-esr | package | 17.0.11-1.37 | x86_64 | (System Packages) vl | firefox-esr | package | 17.0.11-1.41 | x86_64 | MozillaLegacy vl | firefox-esr | package | 31.8.0-1.22 | x86_64 | MozillaLegacy vl | firefox-esr | package | 38.8.0-1.14 | x86_64 | MozillaLegacy vl | firefox-esr | package | 45.8.0-1.3 | x86_64 | Mozilla vl | firefox-esr | package | 52.0.2-1.2 | x86_64 | Mozilla # osc triggerreason mozilla:legacy firefox-esr MozillaLegacy x86_64 https://api.opensuse.org mozilla:legacy firefox-esr MozillaLegacy x86_64 Server returned an error: HTTP Error 404: Not Found Error getting trigger reason for project 'mozilla:legacy' package 'firefox-esr' mozilla:legacy/firefox-esr -- "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
On 16.04.17 16:47 Felix Miata wrote: [stripped long quote]
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>?
Marcus already has a checked out copy of that project so this is his his prompt (Base:Systems is the folder named after the project, hello is the subfolder named after the package). osc behaves differently (if you want) depending on if you are in a checked out copy or not. If your are, you may omit some arguments. The same package source is built for more than one combination of architecture (32bit / 64 bit) and openSUSE version, so these are your arguments 3 and 4. Johannes
participants (3)
-
Felix Miata
-
Johannes Kastl
-
Marcus Meissner