I have been working with the upstream Akira application developers. We have landed a snapcraft.yaml in the upstream project. It’s build successfully but requires access to dbus.
human review required due to 'deny-connection' constraint (interface attributes) declaration-snap-v2_slots_connection (dbus-akira, dbus)
Please can we have auto-connection for this dbus interface?
I think you aren’t asking for auto-connection but rather use of the well-known name, which is handled by the ‘connection’ constraint, not ‘auto-connection’. I’ve granted that and the snap now passes automated review.
If you also meant auto-connection, can you please describe which consuming snaps (plugs) should connect to the akira dbus slot and why?
Duh, sorry. My bad. Yes, you’re right.