Comment 5 for bug 1915202

Facundo, Thank you for explaining, I understand now.

The cause is, our migration code does a silly temporary flow that has never been fixed:

1. Create the charm with minimal metadata (so that it is valid to create revisions)
2. Process revisions, which includes creating in snaprevs, and accumulating charm metadata.
3. Update the now complete charm metadata.

Reordering these parts to be more sensible should be relatively easy, but has never been prioritized. There are a few drivers for it though, this bug is now an extra one. More as it happens.