On Wed, 2017-02-15 at 19:37 -0600, Dennis Gilmore wrote:
On Wed, 2017-02-15 at 12:14 -0700, Kevin Fenzi 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.
>
> So, there's no simple, clear answer. I'd say it's a good topic for
> the
> next meeting if you can make it and we can try and figure out the
> best
> way forward.
We have a requirement to continue to support yum for the forseable
future. anything we have shipped that uses yum to do depsolving needs
to continue to do so. the cutoff point will be when RHEL7 goes EOL.
so
the yum requirement will not go away. using signed repos I think is
the
more preferable way forward. I would like to see mash go away. I
would
like to see all things that do multilib use a single shared library
for
it, so we have one codepath to maintain. while python-multilib has a
python3 sub-package it is not useful as it requires that it is passed
a
yum repo object. I do wonder if at some people we just need to port
yum
to python3 or at least some of it.
Can you explain more about signed repos,
pull-requests which I should
look on, which projects I should start porting to DNF.
What's the problem having 2 branches with yum (for RHEL7) and dnf (for
all Fedora's) ?
Regarding yum/python3 sentence note that:
1) DNF is python2-compatible
2) Even with python3, yum will crash on rich dependencies
3) Yum is getting only bugfixes and basically all big development has
been stopped
4) DNF is Yum on python3
I would like to see our longstanding bugs in dnf fixed
https://bugzilla.redhat.com/show_bug.cgi?id=1303978
https://bugzilla.redhat.com/show_bug.cgi?id=1379252
https://bugzilla.redhat.com/show_bug.cgi?id=1032541
Thanks
Dennis
_______________________________________________
rel-eng mailing list -- rel-eng(a)lists.fedoraproject.org
To unsubscribe send an email to rel-eng-leave(a)lists.fedoraproject.org
--
-Igor Gnatenko