The pool repo already exists: https://src.opensuse.org/pool/python-Flask-Babel
@dgarcia Could you please submit your diff to openSUSE:Factory (using the normal Factory process)? Then, once the…
dgarcia/python-Flask-Babel#factory
This one is problematic. We need to get the pool repo created, first.
@dgarcia Have you already submitted this one to openSUSE:Factory ?
And it looks like 44020f580d is the current state of devel, but not factory. So if I followed my normal workflow to create the missing leap-16.0 branch in pool/obs-git-init tool, it would be…
Hm, I looked, but did not find a leap-16.0 branch in https://src.opensuse.org/pool/obs-git-init
@regularhunter This package (weechat) is not alone in having the problem. I'm not sure, but I believe there is a plan to sync up the factory git branch with the state of openSUSE:Factory in git.…
I think the general preference is to use commits from the factory branch also in the leap-16.0 branch, as opposed to building up a parallel history.
In my fork? Certainly.
No, I meant the leap-16.0 branch of pool/chromium is ahead of the factory branch of the same repo. In other words:
factory is at e557e90812 update to…