[opensuse-buildservice] ensuring build order for nightly builds
Hi opensuse-buildservice, we're building our Osmocom binary releases and nightly packages using the openSUSE build service. https://build.opensuse.org/project/show/network:osmocom:nightly Today, a user has reported a crash using our nightly package build. It turns out that an ABI incompatibility was introduced in our libosmo-mgcp-client package (from osmo-mgw) yesterday. Everything would be in order if the osmo-msc package had been rebuilt after / using the updated libosmo-mgcp-client package, but apparently the osmo-msc package available in the nightly feed was built using the previous day's libosmo-mgcp-client headers. Thus the feed offered packages that were ABI-incompatible, leading to an obscure crash. Looking at the build timestamps, both builds were apparently started at 1:29 AM, which would explain that the osmo-msc build did not have the finished osmo-mgw build available yet. https://build.opensuse.org/package/show/network:osmocom:nightly/osmo-mgw https://build.opensuse.org/package/show/network:osmocom:nightly/osmo-msc The osmo-msc package's control file includes the line Depends: osmocom-nightly, libosmo-mgcp-client6 (= 1.7.0.89.8667d) which I assume should prevent this from happening. Also, https://en.opensuse.org/openSUSE:Build_Service_FAQ says "The OBS guarantees consistent builds of packages, this means it rebuilds all packages if a depended package did change." What are we doing wrong / should we be doing to improve? Can you help us preventing ABI breakage in our nightly builds? Thanks! ~N -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Sep 07 2020, Neels Hofmeyr wrote:
Looking at the build timestamps, both builds were apparently started at 1:29 AM, which would explain that the osmo-msc build did not have the finished osmo-mgw build available yet. https://build.opensuse.org/package/show/network:osmocom:nightly/osmo-mgw https://build.opensuse.org/package/show/network:osmocom:nightly/osmo-msc
Where did you get the 1:29 timestamp? In the repositories I checked, the osmo-msc package has always been built only after the build of oscm-mgw package was complete. Andreas. -- Andreas Schwab, schwab@linux-m68k.org GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1 "And now for something completely different." -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Mon, Sep 07, 2020 at 06:38:59PM +0200, Andreas Schwab wrote:
https://build.opensuse.org/package/show/network:osmocom:nightly/osmo-mgw https://build.opensuse.org/package/show/network:osmocom:nightly/osmo-msc
Where did you get the 1:29 timestamp? In the repositories I checked,
In that link above, I hover the mouse over the "about 13 hours ago". What's the proper place to examine build times? On Mon, Sep 07, 2020 at 10:00:02PM +0200, Jan Engelhardt wrote:
On Monday 2020-09-07 17:41, Neels Hofmeyr wrote:
The osmo-msc package's control file includes the line Depends: osmocom-nightly, libosmo-mgcp-client6 (= 1.7.0.89.8667d) which I assume should prevent this from happening.
However, I find no such dependency for the RPM build.
Does that hint at a fault in our source packages? Or does it mean that .deb should work correctly and .rpm don't? Thanks, ~N -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Wednesday 2020-09-09 16:08, Neels Hofmeyr wrote:
On Mon, Sep 07, 2020 at 06:38:59PM +0200, Andreas Schwab wrote:
https://build.opensuse.org/package/show/network:osmocom:nightly/osmo-mgw https://build.opensuse.org/package/show/network:osmocom:nightly/osmo-msc
Where did you get the 1:29 timestamp? In the repositories I checked,
In that link above, I hover the mouse over the "about 13 hours ago". What's the proper place to examine build times?
01:29+0000 was the time of commit (as shown by `osc log`); it does not have to correspond to build-started time or build-finished time.
On Mon, Sep 07, 2020 at 10:00:02PM +0200, Jan Engelhardt wrote:
On Monday 2020-09-07 17:41, Neels Hofmeyr wrote:
The osmo-msc package's control file includes the line Depends: osmocom-nightly, libosmo-mgcp-client6 (= 1.7.0.89.8667d) which I assume should prevent this from happening.
However, I find no such dependency for the RPM build.
Does that hint at a fault in our source packages? Or does it mean that .deb should work correctly and .rpm don't?
Yes, a fault in your packaging. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Monday 2020-09-07 17:41, Neels Hofmeyr wrote:
we're building our Osmocom binary releases and nightly packages using the openSUSE build service.
Today, a user has reported a crash using our nightly package build. It turns out that an ABI incompatibility was introduced in our libosmo-mgcp-client package (from osmo-mgw) yesterday. Everything would be in order if the osmo-msc package had been rebuilt after / using the updated libosmo-mgcp-client package, [...]
The osmo-msc package's control file includes the line Depends: osmocom-nightly, libosmo-mgcp-client6 (= 1.7.0.89.8667d) which I assume should prevent this from happening.
However, I find no such dependency for the RPM build. So even though the rebuilds happened and happened in order, a user could install a newer msc and retain an earlier libosmo-mgcp-client6. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
participants (3)
-
Andreas Schwab -
Jan Engelhardt -
Neels Hofmeyr