GNOME Bugzilla – Bug 794613
Updating gstreamer version in custom.py doesn't cause rebuild
Last modified: 2018-03-23 06:16:38 UTC
Ever since we started defining the version for gstreamer recipes in recipes/custom.py, updating that version doesn't trigger a rebuild. This means if you rebuild, say, a gst-plugins-bad-1.0, if gstreamer-1.0 was already built as a previous version, the configure will fail. The workaround is to issue `buildone` on all recipes. This is especially bad because this means the recipes won't get rebuilt and updated to the actual code in git while packaging.
We should check whether our binary releases have plugin versions as 1.14 or not. This might have caused them to not have the latest code.
(In reply to Nirbheek Chauhan from comment #1) > We should check whether our binary releases have plugin versions as 1.14 or > not. This might have caused them to not have the latest code. I checked all the 1.14 binary releases for all the platforms. The gstreamer versions looked correct. I verified by checking the version in all the pkgconfig files.
Created attachment 370045 [details] [review] cerbero: Check built version while loading recipe If the built version of a recipe is different than the current version, reset the status and force a rebuild.
Attachment 370045 [details] pushed as 8e084f9 - cerbero: Check built version while loading recipe
When I do release builds, I do a full wipe first.