python-paho-mqtt: update to version 1.2
PATCH 1/1 python-paho-mqtt: update to version 1.2
---
.../python/{python-paho-mqtt_1.1.bb => python-paho-mqtt_1.2.bb} | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
rename meta-python/recipes-devtools/python/{python-paho-mqtt_1.1.bb => python-paho-mqtt_1.2.bb} (68%)meta-python/recipes-devtools/python/python-paho-mqtt_1.2.bb renamed from meta-python/recipes-devtools/python/python-paho-mqtt_1.1.bb +2 -2
@@ -11,5 +11,5 @@ RDEPENDS_${PN} = "\ python-threading \ " -SRC_URI[md5sum] = "a6407b74eb5e5411e157be1de5c11366" -SRC_URI[sha256sum] = "0f7a629efe6e3a2c61b59d3550aa9f2c4529b5689a65fde45e6f1ac36b9a261e" +SRC_URI[md5sum] = "241150b3fcb920ddca4d33181f3238b1" +SRC_URI[sha256sum] = "9100a6aa706ab699d414ec02705a21eb66f436184691d0bf1f2a85a6213c6c1f"
Signature · 1 line
2.7.4
Patchwork not picking changes from the ML Was: [oe] [meta-python][PATCH] python-paho-mqtt: update to version 1.2
Quoted 1 line · Derek Straka
Signed-off-by Derek Straka <[email protected]>
It's not your fault Derek, but most of the patches from today and based on the pings from today also some earlier patches didn't make it into patchwork. This one is the only exception.
Michael, Jose: are you aware of some issues with patchwork? Could it be caused by the default Reply-to change from yesterday (or day before during OEDAM)?
I know only about issues processing merged changes:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=10967
https://bugzilla.yoctoproject.org/show_bug.cgi?id=10759
And also UI issue in patchwork that paging doesn't work, e.g.:
https://patchwork.openembedded.org/bundle/jama/master-next/?submitter=&state=&q=&archive=both
shows that there are 5 pages of changes (which should be in most cases marked as accepted by the hook above), but clicking on 2nd page produces link which drops the query parameters:
https://patchwork.openembedded.org/bundle/jama/master-next/?page=2
so it says "No patches to display"
Regards,
Quoted 28 lines
--- .../python/{python-paho-mqtt_1.1.bb => python-paho-mqtt_1.2.bb} | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) rename meta-python/recipes-devtools/python/{python-paho-mqtt_1.1.bb => python-paho-mqtt_1.2.bb} (68%)meta-python/recipes-devtools/python/python-paho-mqtt_1.2.bb renamed from meta-python/recipes-devtools/python/python-paho-mqtt_1.1.bb +2
-2@@ -11,5 +11,5 @@ RDEPENDS_${PN} = "\ python-threading \ " -SRC_URI[md5sum] = "a6407b74eb5e5411e157be1de5c11366" -SRC_URI[sha256sum] = "0f7a629efe6e3a2c61b59d3550aa9f2c4529b5689a65fde45e6f1ac36b9a261e" +SRC_URI[md5sum] = "241150b3fcb920ddca4d33181f3238b1" +SRC_URI[sha256sum] = "9100a6aa706ab699d414ec02705a21eb66f436184691d0bf1f2a85a6213c6c1f"Signature · 7 lines
2.7.4 -- _______________________________________________ Openembedded-devel mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Signature · 1 line
Martin 'JaMa' Jansa jabber: [email protected]
Re: Patchwork not picking changes from the ML Was: [oe] [meta-python][PATCH] python-paho-mqtt: update to version 1.2
I've seen several issues with hooks. I was working on them yesterday and will continue today.
These are currently managed by hand but we are moving them into configuration management which should help keep them working consistently.
Quoted 70 lines · Martin Jansa
Quoted 1 line · Derek Straka
Signed-off-by Derek Straka <[email protected]>It's not your fault Derek, but most of the patches from today and based on the pings from today also some earlier patches didn't make it into patchwork. This one is the only exception.
Michael, Jose: are you aware of some issues with patchwork? Could it be caused by the default Reply-to change from yesterday (or day before during OEDAM)?
I know only about issues processing merged changes:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=10967
https://bugzilla.yoctoproject.org/show_bug.cgi?id=10759And also UI issue in patchwork that paging doesn't work, e.g.:
https://patchwork.openembedded.org/bundle/jama/
master-next/?submitter=&state=&q=&archive=both
shows that there are 5 pages of changes (which should be in most cases marked as accepted by the hook above), but clicking on 2nd page produces link which drops the query parameters:
https://patchwork.openembedded.org/bundle/jama/master-next/?page=2
so it says "No patches to display"Regards,
Quoted 2 lines
---
.../python/{python-paho-mqtt_1.1.bb => python-paho-mqtt_1.2.bb}| 4 ++--
Quoted 2 lines
1 file changed, 2 insertions(+), 2 deletions(-) rename meta-python/recipes-devtools/python/{python-paho-mqtt_1.1.bb =>python-paho-mqtt_1.2.bb} (68%)
Review
Quoted 2 lines
(quoted diff) +0
-0b/meta-python/recipes-devtools/python/python-paho-mqtt_1.2.bb
meta-python/recipes-devtools/python/python-paho-mqtt_1.2.bb RDEPENDS_${PN} = "\ · line 15
Quoted 12 lines
similarity index 68%
rename from meta-python/recipes-devtools/python/python-paho-mqtt_1.1.bb rename to meta-python/recipes-devtools/python/python-paho-mqtt_1.2.bb index b8f5f3f..c8acfc5 100644meta-python/recipes-devtools/python/python-paho-mqtt_1.2.bb renamed from meta-python/recipes-devtools/python/python-paho-mqtt_1.1.bb +0
-2@@ -11,5 +11,5 @@ RDEPENDS_${PN} = "\ python-threading \ " -SRC_URI[md5sum] = "a6407b74eb5e5411e157be1de5c11366" -SRC_URI[sha256sum] = "0f7a629efe6e3a2c61b59d3550aa9f
2c4529b5689a65fde45e6f1ac36b9a261e"meta-python/recipes-devtools/python/python-paho-mqtt_1.2.bb RDEPENDS_${PN} = "\ · line 15
Quoted 2 lines
meta-python/recipes-devtools/python/python-paho-mqtt_1.2.bb renamed from meta-python/recipes-devtools/python/python-paho-mqtt_1.1.bb +2
-0+SRC_URI[md5sum] = "241150b3fcb920ddca4d33181f3238b1" +SRC_URI[sha256sum] = "9100a6aa706ab699d414ec02705a21
eb66f436184691d0bf1f2a85a6213c6c1f"Quoted 8 lines
--
2.7.4--
_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-devel--
Martin 'JaMa' Jansa jabber: [email protected]--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: Patchwork not picking changes from the ML Was: [oe] [meta-python][PATCH] python-paho-mqtt: update to version 1.2
Martin - No problem. I'll resend the patches.
Michael - Would it be worth waiting before I resend the change sets? It looks like at least a subset of them have made it through.
Thanks.
-Derek
Quoted 78 lines · Michael Halstead
I've seen several issues with hooks. I was working on them yesterday and will continue today.
These are currently managed by hand but we are moving them into configuration management which should help keep them working consistently.
Quoted 70 lines · Martin Jansa
Quoted 1 line · Derek Straka
Signed-off-by Derek Straka <[email protected]>It's not your fault Derek, but most of the patches from today and based on the pings from today also some earlier patches didn't make it into patchwork. This one is the only exception.
Michael, Jose: are you aware of some issues with patchwork? Could it be caused by the default Reply-to change from yesterday (or day before during OEDAM)?
I know only about issues processing merged changes:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=10967
https://bugzilla.yoctoproject.org/show_bug.cgi?id=10759And also UI issue in patchwork that paging doesn't work, e.g.:
https://patchwork.openembedded.org/bundle/jama/master-next/?
submitter=&state=&q=&archive=both
shows that there are 5 pages of changes (which should be in most cases marked as accepted by the hook above), but clicking on 2nd page produces link which drops the query parameters:
https://patchwork.openembedded.org/bundle/jama/master-next/?page=2
so it says "No patches to display"Regards,
Quoted 2 lines
---
.../python/{python-paho-mqtt_1.1.bb => python-paho-mqtt_1.2.bb}| 4 ++--
Quoted 2 lines
1 file changed, 2 insertions(+), 2 deletions(-) rename meta-python/recipes-devtools/python/{python-paho-mqtt_1.1.bb=> python-paho-mqtt_1.2.bb} (68%)
Review
Quoted 2 lines
(quoted diff) +0
-0bb b/meta-python/recipes-devtools/python/python-paho-mqtt_1.2.bb
meta-python/recipes-devtools/python/python-paho-mqtt_1.2.bb RDEPENDS_${PN} = "\ · line 15
Quoted 12 lines
similarity index 68%
rename from meta-python/recipes-devtools/python/python-paho-mqtt_1.1.bb rename to meta-python/recipes-devtools/python/python-paho-mqtt_1.2.bb index b8f5f3f..c8acfc5 100644meta-python/recipes-devtools/python/python-paho-mqtt_1.2.bb renamed from meta-python/recipes-devtools/python/python-paho-mqtt_1.1.bb +0
-2@@ -11,5 +11,5 @@ RDEPENDS_${PN} = "\ python-threading \ " -SRC_URI[md5sum] = "a6407b74eb5e5411e157be1de5c11366" -SRC_URI[sha256sum] = "0f7a629efe6e3a2c61b59d3550aa9
f2c4529b5689a65fde45e6f1ac36b9a261e"meta-python/recipes-devtools/python/python-paho-mqtt_1.2.bb RDEPENDS_${PN} = "\ · line 15
Quoted 2 lines
meta-python/recipes-devtools/python/python-paho-mqtt_1.2.bb renamed from meta-python/recipes-devtools/python/python-paho-mqtt_1.1.bb +2
-0+SRC_URI[md5sum] = "241150b3fcb920ddca4d33181f3238b1" +SRC_URI[sha256sum] = "9100a6aa706ab699d414ec02705a2
1eb66f436184691d0bf1f2a85a6213c6c1f"Quoted 8 lines
--
2.7.4--
_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-devel--
Martin 'JaMa' Jansa jabber: [email protected]--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: Patchwork not picking changes from the ML Was: [oe] [meta-python][PATCH] python-paho-mqtt: update to version 1.2
On Feb 22, 2017 1:56 PM, "Derek Straka" <[email protected]> wrote:
Martin - No problem. I'll resend the patches.
Michael - Would it be worth waiting before I resend the change sets? It looks like at least a subset of them have made it through.
Please wait while I make sure this problem is correctly resolved before re-sending. I'll e-mail once we're ready.
Thanks.
-Derek
Quoted 79 lines · Michael Halstead
I've seen several issues with hooks. I was working on them yesterday and will continue today.
These are currently managed by hand but we are moving them into configuration management which should help keep them working consistently.
Quoted 60 lines · Martin Jansa
Quoted 1 line · Derek Straka
Signed-off-by Derek Straka <[email protected]>It's not your fault Derek, but most of the patches from today and based on the pings from today also some earlier patches didn't make it into patchwork. This one is the only exception.
Michael, Jose: are you aware of some issues with patchwork? Could it be caused by the default Reply-to change from yesterday (or day before during OEDAM)?
I know only about issues processing merged changes:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=10967
https://bugzilla.yoctoproject.org/show_bug.cgi?id=10759And also UI issue in patchwork that paging doesn't work, e.g.:
https://patchwork.openembedded.org/bundle/jama/master-next/?
submitter=&state=&q=&archive=both
shows that there are 5 pages of changes (which should be in most cases marked as accepted by the hook above), but clicking on 2nd page produces link which drops the query parameters:
https://patchwork.openembedded.org/bundle/jama/master-next/?page=2
so it says "No patches to display"Regards,
Quoted 2 lines
---
.../python/{python-paho-mqtt_1.1.bb => python-paho-mqtt_1.2.bb}| 4 ++--
Quoted 2 lines
1 file changed, 2 insertions(+), 2 deletions(-) rename meta-python/recipes-devtools/python/{python-paho-mqtt_1.1.bb=> python-paho-mqtt_1.2.bb} (68%)
Review
Quoted 2 lines
(quoted diff) +0
-0b b/meta-python/recipes-devtools/python/python-paho-mqtt_1.2.bb
meta-python/recipes-devtools/python/python-paho-mqtt_1.2.bb RDEPENDS_${PN} = "\ · line 15
Quoted 12 lines
similarity index 68%
rename from meta-python/recipes-devtools/python/python-paho-mqtt_1.1.bb rename to meta-python/recipes-devtools/python/python-paho-mqtt_1.2.bb index b8f5f3f..c8acfc5 100644meta-python/recipes-devtools/python/python-paho-mqtt_1.2.bb renamed from meta-python/recipes-devtools/python/python-paho-mqtt_1.1.bb +0
-2@@ -11,5 +11,5 @@ RDEPENDS_${PN} = "\ python-threading \ " -SRC_URI[md5sum] = "a6407b74eb5e5411e157be1de5c11366" -SRC_URI[sha256sum] = "0f7a629efe6e3a2c61b59d3550aa9
f2c4529b5689a65fde45e6f1ac36b9a261e"meta-python/recipes-devtools/python/python-paho-mqtt_1.2.bb RDEPENDS_${PN} = "\ · line 15
Quoted 2 lines
meta-python/recipes-devtools/python/python-paho-mqtt_1.2.bb renamed from meta-python/recipes-devtools/python/python-paho-mqtt_1.1.bb +2
-0+SRC_URI[md5sum] = "241150b3fcb920ddca4d33181f3238b1" +SRC_URI[sha256sum] = "9100a6aa706ab699d414ec02705a2
1eb66f436184691d0bf1f2a85a6213c6c1f"Quoted 8 lines
--
2.7.4--
_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-develQuoted 10 lines
--
Martin 'JaMa' Jansa jabber: [email protected]--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core
Quoted 3 lines
Michael: one syntax error in patchwork code was pulled into production yesterday. This is the cause for missing patches. The error is fixed in the Yocto repo now, please perform a server code update ASAP.
Leo and I pulled changes and restarted so this should be in place now.
Re: Patchwork not picking changes from the ML Was: [oe] [meta-python][PATCH] python-paho-mqtt: update to version 1.2
In reply to Michael HalsteadQuoted 5 lines · Michael Halstead
I've seen several issues with hooks. I was working on them yesterday and will continue today.
These are currently managed by hand but we are moving them into configuration management which should help keep them working consistently.
Michael: one syntax error in patchwork code was pulled into production yesterday. This is the cause for missing patches. The error is fixed in the Yocto repo now, please perform a server code update ASAP.
Martin: I will look at the UI issue you are describing and file a bug if needed.
Quoted 96 lines
On Feb 22, 2017 12:47 PM, "Martin Jansa" <[email protected] <mailto:[email protected]>> wrote:
On Wed, Feb 22, 2017 at 12:45:36PM -0500, Derek Straka wrote: > Signed-off-by: Derek Straka <[email protected] <mailto:[email protected]>> It's not your fault Derek, but most of the patches from today and based on the pings from today also some earlier patches didn't make it into patchwork. This one is the only exception. Michael, Jose: are you aware of some issues with patchwork? Could it be caused by the default Reply-to change from yesterday (or day before during OEDAM)? I know only about issues processing merged changes: https://bugzilla.yoctoproject.org/show_bug.cgi?id=10967 <https://bugzilla.yoctoproject.org/show_bug.cgi?id=10967> https://bugzilla.yoctoproject.org/show_bug.cgi?id=10759 <https://bugzilla.yoctoproject.org/show_bug.cgi?id=10759> And also UI issue in patchwork that paging doesn't work, e.g.: https://patchwork.openembedded.org/bundle/jama/master-next/?submitter=&state=&q=&archive=both <https://patchwork.openembedded.org/bundle/jama/master-next/?submitter=&state=&q=&archive=both> shows that there are 5 pages of changes (which should be in most cases marked as accepted by the hook above), but clicking on 2nd page produces link which drops the query parameters: https://patchwork.openembedded.org/bundle/jama/master-next/?page=2 <https://patchwork.openembedded.org/bundle/jama/master-next/?page=2> so it says "No patches to display" Regards, > --- > .../python/{python-paho-mqtt_1.1.bb <http://python-paho-mqtt_1.1.bb> => python-paho-mqtt_1.2.bb <http://python-paho-mqtt_1.2.bb>} | 4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-) > rename meta-python/recipes-devtools/python/{python-paho-mqtt_1.1.bb <http://python-paho-mqtt_1.1.bb> => python-paho-mqtt_1.2.bb <http://python-paho-mqtt_1.2.bb>} (68%) > > diff --git a/meta-python/recipes-devtools/python/python-paho-mqtt_1.1.bb <http://python-paho-mqtt_1.1.bb> b/meta-python/recipes-devtools/python/python-paho-mqtt_1.2.bb <http://python-paho-mqtt_1.2.bb> > similarity index 68% > rename from meta-python/recipes-devtools/python/python-paho-mqtt_1.1.bb <http://python-paho-mqtt_1.1.bb> > rename to meta-python/recipes-devtools/python/python-paho-mqtt_1.2.bb <http://python-paho-mqtt_1.2.bb> > index b8f5f3f..c8acfc5 100644 > --- a/meta-python/recipes-devtools/python/python-paho-mqtt_1.1.bb <http://python-paho-mqtt_1.1.bb> > +++ b/meta-python/recipes-devtools/python/python-paho-mqtt_1.2.bb <http://python-paho-mqtt_1.2.bb> > @@ -11,5 +11,5 @@ RDEPENDS_${PN} = "\ > python-threading \ > " > > -SRC_URI[md5sum] = "a6407b74eb5e5411e157be1de5c11366" > -SRC_URI[sha256sum] = "0f7a629efe6e3a2c61b59d3550aa9f2c4529b5689a65fde45e6f1ac36b9a261e" > +SRC_URI[md5sum] = "241150b3fcb920ddca4d33181f3238b1" > +SRC_URI[sha256sum] = "9100a6aa706ab699d414ec02705a21eb66f436184691d0bf1f2a85a6213c6c1f" > -- > 2.7.4 > > -- > _______________________________________________ > Openembedded-devel mailing list > [email protected] <mailto:[email protected]> > http://lists.openembedded.org/mailman/listinfo/openembedded-devel <http://lists.openembedded.org/mailman/listinfo/openembedded-devel> -- Martin 'JaMa' Jansa jabber: [email protected] <mailto:[email protected]> -- _______________________________________________ Openembedded-core mailing list [email protected] <mailto:[email protected]> http://lists.openembedded.org/mailman/listinfo/openembedded-core <http://lists.openembedded.org/mailman/listinfo/openembedded-core>
Signature · 1 line
Jose Lamego | OTC Embedded Platforms & Tools | GDC
Re: Patchwork not picking changes from the ML
Quoted 8 lines · Jose Lamego
Quoted 5 lines · Michael Halstead
I've seen several issues with hooks. I was working on them yesterday and will continue today.
These are currently managed by hand but we are moving them into configuration management which should help keep them working consistently.
Quoted 6 lines
Michael: one syntax error in patchwork code was pulled into production yesterday. This is the cause for missing patches. The error is fixed in the Yocto repo now, please perform a server code update ASAP.
Martin: I will look at the UI issue you are describing and file a bug if needed.
Would it perhaps make sense to reply to the original author with an email confirming that his patch is now in Patchwork? It should include a link to the patch series, too.
This could have several advantages:
* submitters not aware of Patchwork or whether their target currently uses it learn about it and then can follow the progress of their patch
* everyone gets a confirmation that the submission made it through the various mail servers and Patchwork itself
It still relies on the original submitter to watch out for breakages in the processes, but I guess that can't be avoided with an asynchronous, mail-based process.
Signature · 6 lines
Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter.
Re: Patchwork not picking changes from the ML
Quoted 27 lines · Patrick Ohly
Quoted 8 lines · Jose Lamego
Quoted 5 lines · Michael Halstead
I've seen several issues with hooks. I was working on them yesterday and will continue today.
These are currently managed by hand but we are moving them into configuration management which should help keep them working consistently.
Quoted 6 lines
Michael: one syntax error in patchwork code was pulled into production yesterday. This is the cause for missing patches. The error is fixed in the Yocto repo now, please perform a server code update ASAP.
Martin: I will look at the UI issue you are describing and file a bug if needed.
Would it perhaps make sense to reply to the original author with an email confirming that his patch is now in Patchwork? It should include a link to the patch series, too.
This could have several advantages:
* submitters not aware of Patchwork or whether their target currently uses it learn about it and then can follow the progress of their patch
* everyone gets a confirmation that the submission made it through the various mail servers and Patchwork itself
Quoted 4 lines
It still relies on the original submitter to watch out for breakages in the processes, but I guess that can't be avoided with an asynchronous, mail-based process.
I would love to see this added to the process - +1 :-)
Signature · 4 lines
------------------------------------------------------------ Gary Thomas | Consulting for the MLB Associates | Embedded world ------------------------------------------------------------
Re: Patchwork not picking changes from the ML
Quoted 28 lines · Gary Thomas
Quoted 27 lines · Patrick Ohly
Quoted 8 lines · Jose Lamego
Quoted 5 lines · Michael Halstead
I've seen several issues with hooks. I was working on them yesterday and will continue today.
These are currently managed by hand but we are moving them into configuration management which should help keep them working consistently.
Quoted 6 lines
Michael: one syntax error in patchwork code was pulled into production yesterday. This is the cause for missing patches. The error is fixed in the Yocto repo now, please perform a server code update ASAP.
Martin: I will look at the UI issue you are describing and file a bug if needed.
Would it perhaps make sense to reply to the original author with an email confirming that his patch is now in Patchwork? It should include a link to the patch series, too.
This could have several advantages:
* submitters not aware of Patchwork or whether their target currently uses it learn about it and then can follow the progress of their patch
* everyone gets a confirmation that the submission made it through the various mail servers and Patchwork itself
Quoted 6 lines
Quoted 4 lines
It still relies on the original submitter to watch out for breakages in the processes, but I guess that can't be avoided with an asynchronous, mail-based process.
I would love to see this added to the process - +1 :-)
Let me clarify that my original proposal was to reply only to the original author. That was meant to keep noise down on the list. However, perhaps it should also go to the list?
Then others can help check that Patchwork works, as the original author might not be aware that a response is missing. It also tells everyone the relevant link in Patchwork.
Signature · 6 lines
Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter.
Re: Patchwork not picking changes from the ML
Quoted 8 lines · Patrick Ohly
Let me clarify that my original proposal was to reply only to the original author. That was meant to keep noise down on the list. However, perhaps it should also go to the list?
Then others can help check that Patchwork works, as the original author might not be aware that a response is missing. It also tells everyone the relevant link in Patchwork.
As long as patchworks ignores the email it sends, that's not a terrible idea.
Ross
Re: Patchwork not picking changes from the ML
Quoted 7 lines · Ross
On 24 February 2017 at 16:27, Patrick Ohly <[email protected] <mailto:[email protected]>> wrote:
Let me clarify that my original proposal was to reply only to the original author. That was meant to keep noise down on the list. However, perhaps it should also go to the list?
Quoted 6 lines
Then others can help check that Patchwork works, as the original author might not be aware that a response is missing. It also tells everyone the relevant link in Patchwork.
As long as patchworks ignores the email it sends, that's not a terrible idea.
I'd be happy either way, as long as I (as the poster) get some sort of feedback that the patch has been received and queued.
Thanks for improving this system :-)
Signature · 4 lines
------------------------------------------------------------ Gary Thomas | Consulting for the MLB Associates | Embedded world ------------------------------------------------------------
Re: Patchwork not picking changes from the ML
In reply to Patrick OhlyQuoted 36 lines · Patrick Ohly
Quoted 28 lines · Gary Thomas
Quoted 27 lines · Patrick Ohly
Quoted 8 lines · Jose Lamego
Quoted 5 lines · Michael Halstead
I've seen several issues with hooks. I was working on them yesterday and will continue today.
These are currently managed by hand but we are moving them into configuration management which should help keep them working consistently.
Quoted 6 lines
Michael: one syntax error in patchwork code was pulled into production yesterday. This is the cause for missing patches. The error is fixed in the Yocto repo now, please perform a server code update ASAP.
Martin: I will look at the UI issue you are describing and file a bug if needed.
Would it perhaps make sense to reply to the original author with an email confirming that his patch is now in Patchwork? It should include a link to the patch series, too.
This could have several advantages:
* submitters not aware of Patchwork or whether their target currently uses it learn about it and then can follow the progress of their patch
* everyone gets a confirmation that the submission made it through the various mail servers and Patchwork itselfQuoted 6 lines
Quoted 4 lines
It still relies on the original submitter to watch out for breakages in the processes, but I guess that can't be avoided with an asynchronous, mail-based process.
I would love to see this added to the process - +1 :-)
Quoted 8 lines
Let me clarify that my original proposal was to reply only to the original author. That was meant to keep noise down on the list. However, perhaps it should also go to the list?
Then others can help check that Patchwork works, as the original author might not be aware that a response is missing. It also tells everyone the relevant link in Patchwork.
There is a filed request to enable email notifications in patchwork:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=7684
this notifications will let users (both submitter and CC'ed-users) know through an email about any patch status change (including "New"). Users will be able to opt-out of such notifications.
However, this do not covers the case when submitter is not registered as a Patchwork user. So, there might be a one-time-only email notification to this kind of submitter, as Patrick suggests.
If I don't get any objections for this, I'll file a request in bugzilla next week.
Signature · 1 line
Jose Lamego | OTC Embedded Platforms & Tools | GDC