On Wed, Feb 15, 2017 at 2:14 PM, Kevin Fenzi <kevin(a)scrye.com> wrote:
On Tue, 14 Feb 2017 18:49:11 +0100
Igor Gnatenko <ignatenkobrain(a)fedoraproject.org> wrote:
> Hi,
>
> I've tried to poke on #fedora-releng, but unfortunately I still don't
> have answer for question: "What needs to be done in order to start
> using rich dependencies?".
>
> It's almost 4 releases when we have support for modern features, but
> we can't use it because releng tools are not ready. I'm ready to help
> as much as I can from DNF side, just let me know overview.
Well, I think the main reason there's no clear answer is that there is
no clear answer. :)
Disclaimer: I am not in charge of anything and the below is just my
understanding of current status of things. Dennis should feel free to
correct me. :)
Right now the thing blocking rich deps is that bodhi uses mash. mash in
turn uses yum and errors on rich deps. So, one answer could be "port
mash to dnf".
However. There has been work ongoing to move what mash does into a koji
feature called 'koji signed repos'. This would allow bodhi to fire off
koji jobs instead of calling mash. So another answer might be "help fix
koji signed repos and port it to dnf". This however might be a pretty
big job as the patches aren't merged yet and tying this to koji means
it likely has to be python2 which might mean it's very difficult to
port to dnf.
There's python2-dnf and python2-hawkey for using DNF and Hawkey/libdnf
APIs with Python 2. So aside from Koji currently having a terrible
requirement of supporting Python 2.4, it should be fine.
--
真実はいつも一つ!/ Always, there's only one truth!