| Summary: | changing state of patch fails? | ||
|---|---|---|---|
| Product: | [Yocto Project Subprojects] Patchwork/Patchtest | Reporter: | Patrick Ohly <patrick.ohly> |
| Component: | Patchwork | Assignee: | Jose Lamego <jose.a.lamego> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Medium | CC: | bluelightning, leonardo.sandoval.gonzalez |
| Version: | unspecified | ||
| Target Milestone: | 2.3 M3 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |
|
Description
Patrick Ohly
2017-01-26 07:26:38 UTC
I'm looking into this. Issue is present at Series view only. Patches status and bundles can be edited at patch view. Two patches were developed and can be seen at: https://lists.yoctoproject.org/pipermail/yocto/2017-January/034255.html https://lists.yoctoproject.org/pipermail/yocto/2017-January/034256.html these will be tested in patchwork-staging before implementing in production. I prepared a version 2 of the patches (fixing some javascript syntax errors), but the POST method used to update the patch status seems to be blocked by the nginx server (used both at patchwork-staging and production. I will consult Michael H. for options. Version 2 of patches were successfully implemented in patchwork-staging and can be seen at: https://lists.yoctoproject.org/pipermail/yocto/2017-February/034396.html https://lists.yoctoproject.org/pipermail/yocto/2017-February/034396.html |