Why are krename and kwinstyle-crystal always updated? (just curious)
Yasuhiko, (all), I've notice when doing updates (dupes for TW) or just checking with "zypper lu", kde3-krename and kde3-kwinstyle-crystal are always being updated, e.g. today: v | kde3 | kde3-krename | 3.0.14-4.190 | 3.0.14-4.191 v | kde3 | kde3-kwinstyle-crystal | 1.0.7-6.98 | 1.0.7-6.99 It is really just a curiosity as why a rebuild on those two packages always seems to be triggered. Other than the standard BuildRequires in the specs, they don't seem to have anything else in common. If it was a BuildRequires change, then a rebuild would be triggered on most packages... If you know, drop a reply, don't spend time chasing it down, it's not that important. -- David C. Rankin, J.D.,P.E.
The root cause is that the compilation date/time is included in the binary. Open Build Service always rebuilds the dependent packages if any package changes. However, if the build results are exactly the same, it will be considered unaffected and will not be published. But if the compilation date/time is included in the binary, it means that the binary will always change every time. https://build.opensuse.org/public/build/KDE:KDE3/openSUSE_Tumbleweed/x86_64/... https://build.opensuse.org/public/build/KDE:KDE3/openSUSE_Tumbleweed/x86_64/... Let's see the build logs in OBS. The comparison process is performed near the end, and you can see that the date/time appear here. Thanks, On Mon, 22 Jul 2024 19:39:25 -0500 "David C. Rankin" <drankinatty@gmail.com> wrote:
Yasuhiko, (all),
I've notice when doing updates (dupes for TW) or just checking with "zypper lu", kde3-krename and kde3-kwinstyle-crystal are always being updated, e.g. today:
v | kde3 | kde3-krename | 3.0.14-4.190 | 3.0.14-4.191 v | kde3 | kde3-kwinstyle-crystal | 1.0.7-6.98 | 1.0.7-6.99
It is really just a curiosity as why a rebuild on those two packages always seems to be triggered. Other than the standard BuildRequires in the specs, they don't seem to have anything else in common. If it was a BuildRequires change, then a rebuild would be triggered on most packages...
If you know, drop a reply, don't spend time chasing it down, it's not that important.
-- David C. Rankin, J.D.,P.E.
-- Yasuhiko Kamata <belphegor@belbel.or.jp>
Ok, fixed both. On Tue, 23 Jul 2024 10:43:49 +0900 Yasuhiko Kamata <belphegor@belbel.or.jp> wrote:
The root cause is that the compilation date/time is included in the binary.
Open Build Service always rebuilds the dependent packages if any package changes. However, if the build results are exactly the same, it will be considered unaffected and will not be published.
But if the compilation date/time is included in the binary, it means that the binary will always change every time.
https://build.opensuse.org/public/build/KDE:KDE3/openSUSE_Tumbleweed/x86_64/... https://build.opensuse.org/public/build/KDE:KDE3/openSUSE_Tumbleweed/x86_64/...
Let's see the build logs in OBS. The comparison process is performed near the end, and you can see that the date/time appear here.
Thanks,
On Mon, 22 Jul 2024 19:39:25 -0500 "David C. Rankin" <drankinatty@gmail.com> wrote:
Yasuhiko, (all),
I've notice when doing updates (dupes for TW) or just checking with "zypper lu", kde3-krename and kde3-kwinstyle-crystal are always being updated, e.g. today:
v | kde3 | kde3-krename | 3.0.14-4.190 | 3.0.14-4.191 v | kde3 | kde3-kwinstyle-crystal | 1.0.7-6.98 | 1.0.7-6.99
It is really just a curiosity as why a rebuild on those two packages always seems to be triggered. Other than the standard BuildRequires in the specs, they don't seem to have anything else in common. If it was a BuildRequires change, then a rebuild would be triggered on most packages...
If you know, drop a reply, don't spend time chasing it down, it's not that important.
-- David C. Rankin, J.D.,P.E.
-- Yasuhiko Kamata <belphegor@belbel.or.jp>
-- Yasuhiko Kamata <belphegor@belbel.or.jp>
participants (2)
-
David C. Rankin -
Yasuhiko Kamata