Hi,
Our latest release on meta-cassini depends on specific commits from the master-next branch, which was previously compatible with the whinlatter release (in particular: fix: circular task dependency with meta-mender and meta-secure-core by Lorac · Pull Request #2304 · mendersoftware/meta-mender · GitHub).
As there was no official whinlatter branch, we used the master-next branch (similarly to what we did for the walnascar release). However, I noticed today that the branch appears to have been force-pushed, and this specific commit is no longer present.
Would it be possible to restore this commit, or suggest an alternative we should use? Also, could you please clarify whether force-pushing to the master-next branch is expected going forward?
Thank you for your help.
Best regards,
Emek
Hi @ememarar,
Thanks for reaching out! I’m sorry for the unpleasant surprise, but there are essentially no guarantees given for the master-next branch of meta-mender. This branch will occasionally rebase or be force-pushed.
If you need release branches besides the LTS ones, please get in touch with requirements and use case, then we can maybe figure something out, be it either a coordinated branch, or a branch which you host yourself, or, or, or…
Greetz,
Josef
Aah that’s pity. We don’t require a big support to be honest. We’ve been using that branch (master-next) since styhead (almost 1.5 years) and it was working for us with few fixes over here and there. Is there any branch (or commit on master branch) that is compatible or close to whinlatter?
Hi @ememarar,
The closest probably is whinlatter support by aduskett · Pull Request #2383 · mendersoftware/meta-mender · GitHub. Depending on what kind of fixes or adjustments you did/need it might be worth looking into how we can make this a bit more formally almost-supported, but as long as stuff just happens somewhere, invisible to us and on master-next, its obviously beyond control and support.
Greetz,
Josef