Let's try to summarize the big picture as of now.

* Important to fix

Bug 1185760 - Default pmlogger config depends on pmcd but doesn't ensure it is running

This might lead to random failures to start pmlogger on boot.  The fix is simple.

* Important to understand

Bug 1182184 - reduced installation footprint for minimal pcp applications

This doesn't affect Cockpit directly, but it risks the ability of Cockpit to be installed and enabled by default and we must make sure that we don't get stuck in the tarpit of discussions here.

* UX degradation

Bug 1185764 - pmlogger.service status does not reflect reality 
Bug 1185755 - "systemctl start pmlogger" does nothing unless pmlogger.service is also enabled

This means that Cockpit can not use the normal tools for maintaining the status of the pmlogger service and we must either invent new and inconsistent tools just for pmlogger or (more likely) fail to offer any.

* Fixed via hacks in Cockpit

Bug 1185749 - Need to run pmcd at least once before pmval -L will work
Bug 1187588 - PM_CONTEXT_LOCAL crashes process when /etc/pcp.conf is unreadable

These shouldn't affect Cockpit, but the workarounds make Cockpit dependent on PCP internals.

* Potential intergration blockers

Bug 1182184 - reduced installation footprint for minimal pcp applications

This doesn't affect Cockpit directly, but they risk the ability of Cockpit to be installed and enabled by default.

> * Potential intergration blockers

Sorry, I forgot to remove this duplicate paragraph.

Reviewing the original BZ list, we're all done here - or as done as we're ever likely to be.  From memory there remains one other Cockpit threaded-crash BZ still WIP on the Cockpit side, but I think we're finished with all the PCP issues.