| Summary: | patchwork: post-receive git hook is not functional | ||
|---|---|---|---|
| Product: | [Yocto Project Subprojects] Patchwork/Patchtest | Reporter: | Jose Lamego <jose.a.lamego> |
| Component: | Patchwork | Assignee: | Jose Lamego <jose.a.lamego> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Undecided | CC: | Martin.Jansa, mhalstead, patrick.ohly |
| Version: | 2.3 | ||
| Target Milestone: | 2.3 M1 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |
|
Description
Jose Lamego
2016-12-02 15:43:39 UTC
It never worked for meta-oe, it maybe marked one patch in 1000. Maybe it doesn't mark patches which are already in some bundle (all meta-oe patches go first to master-next bundle and then they are merged after testing in master-next branch/bundle). So it probably isn't related to enabling it for all projects. Correct, this isn't related to the per-project configuration, but to the post-receive git hook having a hard-coded path to patchwork, which does not reflect the actual path in the production server. We just recently pointed the server to the Yocto-hosted repository [1], and may skipped to update that line. Upon confirmation of that path, I will submit a patch to update the hook. [1] git://git.yoctoproject.org/patchwork After removing [options] default=oe-core from .pwclientrc pwclient exits with the following ConfigParser.NoSectionError: No section: 'base'. I've reverted the change and now oe-core is updating again. What do we try next for the other projects? (In reply to comment #3) > After removing > > [options] > default=oe-core > > from .pwclientrc pwclient exits with the following > > ConfigParser.NoSectionError: No section: 'base'. > > I've reverted the change and now oe-core is updating again. > > What do we try next for the other projects? Thanks Michael. I'm closing this bug now and will track the all-projects enabling request separately. |