After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 747514 - cerbero: Fix recipe status reset for git repositories
cerbero: Fix recipe status reset for git repositories
Status: RESOLVED OBSOLETE
Product: GStreamer
Classification: Platform
Component: cerbero
git master
Other All
: Normal normal
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2015-04-08 15:12 UTC by Robert Swain
Modified: 2018-11-03 10:18 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Robert Swain 2015-04-08 15:12:45 UTC 
Tests show that cerbero seems to reset the status of a recipe based, partially, upon what is fetched from a git repository rather than the HEAD commit hash.

This means that recipe build states get reset unnecessarily when the recipe points to a specific commit and the branch to which that commit belongs is updated. It also means that recipe build states are not updated if the specific commit pointed to is changed within that which is fetched.

Also, I changed the commit hash pointed to by a recipe and I expected that changing the recipe would trigger a rebuild (after running fetch-package --reset-rdeps --full-reset <package>) but it did not. It had even changed the commit that was checked out.
Comment 1 GStreamer system administrator 2018-11-03 10:18:57 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/gstreamer/cerbero/issues/13.