It's being installed both from the real and fake cron modules, and for some reason the fake module is being installed by the real one, meaning any binding of the real module results in MetadataModule being installed twice and failing with a duplicate key error.
It's being installed both from the real and fake cron modules, and for some reason the fake module is being installed by the real one, meaning any binding of the real module results in MetadataModule being installed twice and failing with a duplicate key error.