The patchwork post-receive git hook automatically updates a patch status to Accepted when it gets pushed to master. The hook stopped working apparently after enabling it for all projects, from previous configuration that only included oe-core.
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.