We are creating "module-$name-$stream-$version-build" tags. When building from "master" branch, we can have maximum name of a module 14 characters long. When building from "f26" and similar, it can be 17 characters.
Is that enough for module name? If not, what can we do? We can start using the 8 characters long hash in the tag name instead of version like "20170323193611". This can give as 6 more characters for name (23 altogether). We could change the "module-" prefix, to something like "fm-", this could give as 4 more characters...
Thoughts?
"shared-userspace" module is hitting this, but it is not blocking the Karsten working on it, because he can use "f26" or similar branch for his builds instead of the "master" branch. With "f26", he is not hitting this limit.
This is very similar to the kernel build issue we had.
Sooner or later you will have really-really-long-stream-names where no microoptimization like shortening the word "module" would help you. Consider doing the same we did with dist tags. Maybe even use the same string (prefix + short hash).
+1 here. I think we should compute the hash the same way as we compute the %dist tag and use "module-%s" % hexdigets[:16]. Note that this has to be done in pdc-updater and should just work on MBS side...
"module-%s" % hexdigets[:16]
Metadata Update from @jkaluza: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
This issue has been migrated to Fedora Forge: https://forge.fedoraproject.org/koji/mbs/issues/477
Please continue any further discussion there.