New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
mender-connect master: depend on mender 3.2 #1522
mender-connect master: depend on mender 3.2 #1522
Conversation
@lluiscampos, Let me know if you want to start the integration pipeline by mentioning me and the command "start pipeline". |
Following MEN-5203, the upcoming mender-connect releases will depend on mender 3.2 or newer. Changelog: Title Signed-off-by: Lluis Campos <lluis.campos@northern.tech>
67307b2
to
8804fa1
Compare
@@ -1,5 +1,7 @@ | |||
require mender-connect.inc | |||
|
|||
RDEPENDS_${PN} = "glib-2.0 mender-client (>= 2.5)" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Very often, we just copy the old file. How is the best way to remember to remove this? A task set for Mender 3.2?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, I thought about that too. I am creating a reminder task, good idea!
Bu the way, I also considered to leave the inc
with the dependency on mender-client (>= 2.5)
and update only the master recipe... but decided for this approach which is more verbose but cleaner in my opinion.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Created MEN-5229 👍
@mender-test-bot start pipeline 🚢 |
Hello 😸 I created a pipeline for you here: Pipeline-409711160 Build Configuration Matrix
|
Following MEN-5203, the upcoming mender-connect releases will depend on
mender 3.2 or newer.
Changelog: Title