FBR: Apply MBS PR#1185 to fix Module Stream Expansion with new platform streams

[Jan Kaluža]

Hi,

Mohan filled MBS issue https://pagure.io/fm-orchestrator/issue/1184 and asked us to fix and deploy that during the freeze to unblock him. I therefore want to ask for +1 to deploy this small patch (already merged upstream): https://pagure.io/fm-orchestrator/pull-request/1185#request_diff .

I think the issue is well described in the PR, unit-test and MBS issue tracker, so I won't repeat myself here. I hope that's OK.

Regards,
Jan Kaluza

[Mikolaj Izdebski]

+1

On Wed, Mar 27, 2019 at 7:02 AM Jan Kaluža  wrote:
> Hi,
>
> Mohan filled MBS issue https://pagure.io/fm-orchestrator/issue/1184 and asked us to fix and deploy that during the freeze to unblock him. I therefore want to ask for +1 to deploy this small patch (already merged upstream): https://pagure.io/fm-orchestrator/pull-request/1185#request_diff .
>
> I think the issue is well described in the PR, unit-test and MBS issue tracker, so I won't repeat myself here. I hope that's OK.
>
> Regards,
> Jan Kaluza
> _______________________________________________
> infrastructure mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: https://lists.fedoraproject.org/archives/list/[e-mail]...

[Stephen John Smoogen]

On Wed, 27 Mar 2019 at 02:02, Jan Kaluža  wrote:
> Hi,
>
> Mohan filled MBS issue https://pagure.io/fm-orchestrator/issue/1184 and asked us to fix and deploy that during the freeze to unblock him. I therefore want to ask for +1 to deploy this small patch (already merged upstream): https://pagure.io/fm-orchestrator/pull-request/1185#request_diff .
>
> I think the issue is well described in the PR, unit-test and MBS issue tracker, so I won't repeat myself here. I hope that's OK.

I don't see this causing a breakage now, but I am wondering if the
test is 'fragile' because once those versions are EOL, then won't it
break because various tools (pdc/bodhi) may return something up the
stack that you can't build against it anyway?
> Regards,
> Jan Kaluza
> _______________________________________________
> infrastructure mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: https://lists.fedoraproject.org/archives/list/[e-mail]...

[Jan Kaluža]

> On Wed, 27 Mar 2019 at 02:02, Jan Kaluža <jkaluza(a)redhat.com&gt; wrote:
>
> I don't see this causing a breakage now, but I am wondering if the
> test is 'fragile' because once those versions are EOL, then won't it
> break because various tools (pdc/bodhi) may return something up the
> stack that you can't build against it anyway?

I'm not sure we have addressed this issue generally. Grepping the code for "EOL" and similar things only shows that you cannot submit module once it is EOL, but I was not able to find out any code which would prevent you to building module against EOLed module.

I will ask Matt Prahl who should know more and create ticket to address that if it's needed.

But I think it is not blocker for this FBR.

Regards,
Jan Kaluza

[Kevin Fenzi]

+1

kevin

[Mohan Boddu]

LGTM +1

On Wed, Mar 27, 2019 at 1:29 PM Kevin Fenzi  wrote:
> +1
>
> kevin
>
> infrastructure mailing list -- [e-mail]
> To unsubscribe send an email to
> [e-mail]
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/[e-mail]...