I also wonder why your pull automagically triggered src-o-org-forwarder doing the "SR"?
That's because Factory is not yet using the git workflow. Changes to Factory should be submitted "as…
Hi @WernerFink
Factory has not been migrated to the git workflow, yet. So you should handle this change in the same way that https://build.opensuse.org/request/show/1305216 was done.
So, openSUSE:Factory has not been migrated to the git workflow, yet. That means this update should be submitted first to the devel project and from there via classic SR to openSUSE:Factory.
In…
df1a350b25
Merge pull request 'Update to Factory version' (#1) from mlin7442/python-Flask-Babel:update_factory_ver into leap-16.0
ba418bd1e6
Merge pull request 'Change the openSUSE autoinstallation IDs (bsc#1249399)' (#1) from lslezak/agama-products:leap-16.0 into leap-16.0
Ideally, the change would land in factory branch, first, and then the leap-16.0 branch would be updated to the exact same git hash that is in factory...
But the factory branch is behind,…
All leap-16.0 branches created.
As for Flask-Babel, once the changes land in Factory, and once the factory branch in pool gets synced, please open a normal PR to sync leap-16.0 with…