+ Repo Generation

+ ---------------

+ 

+ The way that Koji handles repo generation has changed significantly.

+ For full details, please see the release notes and :doc:`../repo_generation`.

+ 

+ The following kojira configuration options are no longer used and have no analog

+ in the new system:

+ 

+ * ``queue_file``

+ * ``ignore_tags``

+ * ``no_repo_effective_age``

+ * ``repo_tasks_limit``

+ 

+ We recommend you remove these settings from ``kojira.conf``.

+ Kojira will warn at startup if they are present.

+ 

+ Additionally, these kojira configuration options have moved into the hub config:

+ 

+ * ``max_repo_tasks`` -> ``MaxRepoTasks``

+ * ``max_repo_tasks_maven`` -> ``MaxRepoTasksMaven``

+ * ``debuginfo_tags`` -> ``DebuginfoTags``

+ * ``source_tags`` -> ``SourceTags``

+ * ``separate_source_tags`` -> ``SeparateSourceTags``

+ 

+ Admins that relied on these kojira options should now set the corresponding hub options and remove

+ the old kojira ones.

+ For the latter three, note that there are now other ways to control these repo options.

+ 

+ Finally, if you have systems outside of Koji that rely on Koji keeping particular tag repos up to

+ date, you may need to take extra steps to ensure regeneration.

+ If the tag sees regular build use within Koji, then that might trigger regens often enough.

+ If not, there are two options:

+ 

+ * set ``repo.auto=True`` for the tag in question

+ * have the external system create a repo request via the api

+ 

+ Again, for full details, please see the release notes and :doc:`../repo_generation`.

+ 

+ 

+ CLI option ``--bundle-format`` for kiwi. For possible values look at `kiwi docs`_.