On 06/11/2015 05:01 AM, Peter Robinson wrote:
On Thu, Jun 11, 2015 at 8:08 AM, Miroslav Suchy
<msuchy(a)redhat.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> Dne 28.5.2015 v 20:29 Dennis Gilmore napsal(a):
>>>> and have it work across rhel and fedora builders in fedora. the
>>>> solution
>>>>>> really needs to be a combination of things. I think the
>>>>>> koji code needs to assume that there could be multiple
>>>>>> possible backends, so we can set yum, yum- deprecated, dnf.
>>>>>> but additionally mock needs to really know that if the host
>>>>>> is f22 or newer or rhel8(big assumption here) or newer and
>>>>>> you say yum is the
>>>> The decision of mock is config driven. And mock ships different
>>>> config for different distribution.
>>>>>> backend you mean yum-deprecated. I am assuming
>>>>>> yum-deprectaed will be in one of RHEL or EPEL.
>>>>
>>>> DNF (with yum-deprecated) is in EPEL (however just EPEL7), but
>>>> there is no dnf-plugins-core, which is needed too.
>>>>
>>>>
>>>> Can you or somebody else from rel-engs alter my patch or come
>>>> with different solution? I would like to remind that according
>>>>
https://fedorahosted.org/rel-eng/ticket/6162 we have just 3
>>>> weeks to do that in F23 time-frame. Then it will be again too
>>>> late, and you will have to target for F24.
>>
https://fedoraproject.org/wiki/FAD_Release_Tools_and_Infrastructure_20
> 15#Deliverables
>> it is one of the deliverables for the FAD next week. we do want a
>> solution. I will try comeup with something I see as a workable
>> option. but someone else is free to do something also. Thank you
>> for taking a stab at it
>
> AFAIK the FAD is over, so do you have some solution?
Still in process, there's a full understanding of the problem and Mike
is working on the final implementation. There should be patches posted
for review in the next week or so.
Sorry for the delay, I meant to finish these up last week.
Patches posted to koj-devel
https://lists.fedorahosted.org/pipermail/koji-devel/2015-June/000034.html
One thing I'm not sure about is the releasever issue.
https://bugzilla.redhat.com/show_bug.cgi?id=1173107
I have currently worked around it by setting
config_opts['releasever'] = 'NULL'
in site-defaults.cfg
Do we expect dnf to fix this bug, or will we be forced to work around it
in a more permanent fashion?