Re: Please review: MBS platform definition for EPEL8

[Merlin Mathesius]

On Thu, Oct 24, 2019 at 4:51 PM Mohan Boddu  wrote:

> Thanks for the info, I renamed the tags and updated the tickets.
>

Thank you for noticing the discrepancy and making the corrections.

Now we should definitely be good to import the virtual module definitions.

Why is naming so hard?
>

Because communication is hard!

On Thu, Oct 24, 2019 at 4:58 PM Merlin Mathesius 
> wrote:
>
>>
>>
>> On Thu, Oct 24, 2019 at 3:32 PM Mohan Boddu  wrote:
>>
>>> Hi,
>>>
>>> I created the tags as module-epel8-build and
>>> module-epel8-playground-build just to be consistent with the naming, so you
>>> need to change the config for koji_tag part.
>>>
>>> And may be also change the "stream" in the yaml file to epel8 and
>>> epel8-playground and change the name of the platform to platform-epel8 and
>>> platform-epel8-playground, again just for consistency.
>>>
>>> Other than that, its LGTM.
>>>
>>
>> Thanks for taking a look.
>>
>> There was discussion about the "el8" vs "epel8" naming during the
>> preliminary review and discussion. It should be "el8" to work correctly
>> with RHEL 8 as explained in Petr's comment at
>> https://pagure.io/Fedora-Infra/ansible/pull-request/40#comment-96326.
>>
>> But yeah, it keeps tripping me up, too!
>>
>>
>>> On Thu, Oct 24, 2019 at 3:43 PM Merlin Mathesius 
>>> wrote:
>>>
 Now that the build tags have been created (thanks, Mohan!), we should
 be ready to add the virtual platform module definitions for EPEL-8 to
 Fedora staging MBS.

 I have attached a revised patch that includes both the el8 and
 el8-playground definitions in a single patch file. Aside from the combined
 patch, the only difference from the previous separate patches is the
 addition of the 'default_modules_scm_url' and 'use_default_modules'
 settings to enable ursa prime.

 Thanks.

 Merlin


 On Wed, Oct 2, 2019 at 5:07 PM Merlin Mathesius 
 wrote:

>
>
> On Wed, Oct 2, 2019 at 12:41 PM Matt Prahl  wrote:
>
>> Hi Merlin,
>> I can't think of anything that you need to do before merging and
>> deploying them as long as the Koji tags mentioned in the modulemd files 
>> are
>> all set.
>>
>
> Of course. We need the module-el8-build
> and module-el8-playground-build tags. I just created
> https://pagure.io/releng/issue/8865 for that.
>
> Thanks, Matt!
>
> On Wed, Oct 2, 2019 at 12:12 PM Merlin Mathesius 
>> wrote:
>>
>>> Hi, Matt, Jan,
>>>
>>> Could one of you provide some input here?
>>>
>>> We're looking to add the virtual platform module definitions for
>>> EPEL-8 to Fedora staging MBS. Is there anything specific that needs to
>>> happen before merging and deploying them?
>>>
>>> If you'd like to review the definitions, the patches are re-attached
>>> to this message so you don't need to go digging.
>>>
>>> Merlin
>>>
>>> On Tue, Oct 1, 2019 at 11:43 AM Kevin Fenzi  wrote:
>>>
 On Mon, Sep 30, 2019 at 02:14:14PM -0500, Merlin Mathesius wrote:
 > Hi, all,
 >
 > Since folks seem to be happy with the el8 platform virtual module
 > definitions, can they be merged and deployed to staging--or does
 something
 > else need to happen first? (Of course, any module builds based on
 > platform:el8* won't be usable until there are corresponding pungi
 configs.)

 I'm not entirely sure. :)

 Can we ask some of the mbs folks what all is needed here?

 kevin
 ___
 infrastructure mailing list --
 infrastructure@lists.fedoraproject.org
 To unsubscribe send an email to
 infrastructure-le...@lists.fedoraproject.org
 Fedora Code of Conduct:
 https://docs.fedoraproject.org/en-US/project/code-of-conduct/
 List Guidelines:
 https://fedoraproject.org/wiki/Mailing_list_guidelines
 List Archives:
 https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org

>>>
>>
>> --
>>
>> Matt Prahl
>>
>> Senior Software Engineer, PnT DevOps
>>
>> Red Hat 
>>
>> Westford, MA
>>
>> mpr...@redhat.com
>> M: 802-999-0972 IM: mprahl
>> 
>>
> ___
 infrastructure mailing list -- infrastructure@lists.fedoraproject.org
 To unsubscribe send an email to
 infrastructure-le...@lists.fedoraproject.org
 Fedora Code of Conduct:
 https://docs.fedoraproject.org/en-US/project/code-of-conduct/
 List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
 List Archives:
 https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org

>>> 

Re: Please review: MBS platform definition for EPEL8

[Mohan Boddu]

Thanks for the info, I renamed the tags and updated the tickets.

Why is naming so hard?

On Thu, Oct 24, 2019 at 4:58 PM Merlin Mathesius 
wrote:

>
>
> On Thu, Oct 24, 2019 at 3:32 PM Mohan Boddu  wrote:
>
>> Hi,
>>
>> I created the tags as module-epel8-build and
>> module-epel8-playground-build just to be consistent with the naming, so you
>> need to change the config for koji_tag part.
>>
>> And may be also change the "stream" in the yaml file to epel8 and
>> epel8-playground and change the name of the platform to platform-epel8 and
>> platform-epel8-playground, again just for consistency.
>>
>> Other than that, its LGTM.
>>
>
> Thanks for taking a look.
>
> There was discussion about the "el8" vs "epel8" naming during the
> preliminary review and discussion. It should be "el8" to work correctly
> with RHEL 8 as explained in Petr's comment at
> https://pagure.io/Fedora-Infra/ansible/pull-request/40#comment-96326.
>
> But yeah, it keeps tripping me up, too!
>
>
>> On Thu, Oct 24, 2019 at 3:43 PM Merlin Mathesius 
>> wrote:
>>
>>> Now that the build tags have been created (thanks, Mohan!), we should be
>>> ready to add the virtual platform module definitions for EPEL-8 to Fedora
>>> staging MBS.
>>>
>>> I have attached a revised patch that includes both the el8 and
>>> el8-playground definitions in a single patch file. Aside from the combined
>>> patch, the only difference from the previous separate patches is the
>>> addition of the 'default_modules_scm_url' and 'use_default_modules'
>>> settings to enable ursa prime.
>>>
>>> Thanks.
>>>
>>> Merlin
>>>
>>>
>>> On Wed, Oct 2, 2019 at 5:07 PM Merlin Mathesius 
>>> wrote:
>>>


 On Wed, Oct 2, 2019 at 12:41 PM Matt Prahl  wrote:

> Hi Merlin,
> I can't think of anything that you need to do before merging and
> deploying them as long as the Koji tags mentioned in the modulemd files 
> are
> all set.
>

 Of course. We need the module-el8-build and module-el8-playground-build
 tags. I just created https://pagure.io/releng/issue/8865 for that.

 Thanks, Matt!

 On Wed, Oct 2, 2019 at 12:12 PM Merlin Mathesius 
> wrote:
>
>> Hi, Matt, Jan,
>>
>> Could one of you provide some input here?
>>
>> We're looking to add the virtual platform module definitions for
>> EPEL-8 to Fedora staging MBS. Is there anything specific that needs to
>> happen before merging and deploying them?
>>
>> If you'd like to review the definitions, the patches are re-attached
>> to this message so you don't need to go digging.
>>
>> Merlin
>>
>> On Tue, Oct 1, 2019 at 11:43 AM Kevin Fenzi  wrote:
>>
>>> On Mon, Sep 30, 2019 at 02:14:14PM -0500, Merlin Mathesius wrote:
>>> > Hi, all,
>>> >
>>> > Since folks seem to be happy with the el8 platform virtual module
>>> > definitions, can they be merged and deployed to staging--or does
>>> something
>>> > else need to happen first? (Of course, any module builds based on
>>> > platform:el8* won't be usable until there are corresponding pungi
>>> configs.)
>>>
>>> I'm not entirely sure. :)
>>>
>>> Can we ask some of the mbs folks what all is needed here?
>>>
>>> kevin
>>> ___
>>> infrastructure mailing list --
>>> infrastructure@lists.fedoraproject.org
>>> To unsubscribe send an email to
>>> infrastructure-le...@lists.fedoraproject.org
>>> Fedora Code of Conduct:
>>> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>>> List Guidelines:
>>> https://fedoraproject.org/wiki/Mailing_list_guidelines
>>> List Archives:
>>> https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
>>>
>>
>
> --
>
> Matt Prahl
>
> Senior Software Engineer, PnT DevOps
>
> Red Hat 
>
> Westford, MA
>
> mpr...@redhat.com
> M: 802-999-0972 IM: mprahl
> 
>
 ___
>>> infrastructure mailing list -- infrastructure@lists.fedoraproject.org
>>> To unsubscribe send an email to
>>> infrastructure-le...@lists.fedoraproject.org
>>> Fedora Code of Conduct:
>>> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>>> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>>> List Archives:
>>> https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
>>>
>> ___
>> infrastructure mailing list -- infrastructure@lists.fedoraproject.org
>> To unsubscribe send an email to
>> infrastructure-le...@lists.fedoraproject.org
>> Fedora Code of Conduct:
>> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>> List Archives:
>> 

Re: [PATCH 1/2] bodhi-pungi: F32 will be the next "branched"

[Dusty Mabe]

Thanks! pushed!

On 10/24/19 5:10 PM, Rick Elrod wrote:
> +1 for the same reason.
> 
> -re
> 
> On 2019-10-24 16:23, Mohan Boddu wrote:
>> Since rawhide is not uses pungi, I think we are okay with this change.
>>
>> +1 LGTM
>>
>> On Thu, Oct 24, 2019 at 4:13 PM Mohan Boddu  wrote:
>>>
>>> No, with rawhide gating we are using bodhi to push rawhide builds as
>>> updates, I think it might call it and cause some issues.
>>>
>>> On Thu, Oct 24, 2019 at 4:05 PM Dusty Mabe  wrote:



 On 10/24/19 4:02 PM, Mohan Boddu wrote:
> Just wondering, doesn't it affect rawhide composes, since rawhide is 
> still 32?
>

 IIUC the first time this will take any effect is when we start calling 
 bodhi with '32'
 as the number (i.e. after we have branched and rawhide is now 33).

 Dusty

>> ___
>> infrastructure mailing list -- infrastructure@lists.fedoraproject.org
>> To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
>> Fedora Code of Conduct: 
>> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>> List Archives: 
>> https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
>>
> ___
> infrastructure mailing list -- infrastructure@lists.fedoraproject.org
> To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
> 
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org

Re: FBR: Update releases.json to make f31 active and no retirement

[Mikolaj Izdebski]

+1

On Thu, Oct 24, 2019 at 10:53 PM Mohan Boddu  wrote:
>
> Hi,
>
> Another FBR to update releases.json to make sure retirement is not allowed
>
> diff --git a/roles/pkgdb-proxy/files/pkgdb-gnome-software-collections.json
> b/roles/pkgdb-proxy/files/pkgdb-gnome-software-collections
> index aac977e..9e0cbf2 100644
> --- a/roles/pkgdb-proxy/files/pkgdb-gnome-software-collections.json
> +++ b/roles/pkgdb-proxy/files/pkgdb-gnome-software-collections.json
> @@ -12,14 +12,14 @@
>"version": "devel"
>  },
>  {
> -  "allow_retire": true,
> +  "allow_retire": false,
>"branchname": "f31",
>"date_created": "2014-05-14 12:36:15",
>"date_updated": "2018-08-14 17:07:23",
>"dist_tag": ".fc31",
>"koji_name": "f31",
>"name": "Fedora",
> -  "status": "Under Development",
> +  "status": "Active",
>"version": "31"
>  },
>  {
> ___
> infrastructure mailing list -- infrastructure@lists.fedoraproject.org
> To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org

Re: [PATCH] new-updates-sync: sync multiarch silverblue ostree content

[Dusty Mabe]

Thanks! Fixed the syntax error and pushed!

On 10/24/19 5:06 PM, Rick Elrod wrote:
> +1 after the syntax fix I mentioned inline.
> 
> -re
> 
> On 2019-10-24 15:56, Dusty Mabe wrote:
>> ---
>>   roles/bodhi2/backend/files/new-updates-sync | 10 ++
>>   1 file changed, 6 insertions(+), 4 deletions(-)
>>
>> diff --git a/roles/bodhi2/backend/files/new-updates-sync 
>> b/roles/bodhi2/backend/files/new-updates-sync
>> index d08c89301..9ad7628b8 100755
>> --- a/roles/bodhi2/backend/files/new-updates-sync
>> +++ b/roles/bodhi2/backend/files/new-updates-sync
>> @@ -25,8 +25,9 @@ RELEASES = {'f31': {'topic': 'fedora',
>>   'modules': ['fedora', 'fedora-secondary'],
>>   'repos': {'updates': {
>>   'from': 'f31-updates',
>> -'ostrees': [{'ref': 
>> 'fedora/31/x86_64/updates/silverblue',
>> - 'dest': OSTREEDEST}],
>> +'ostrees': [{'ref': 
>> 'fedora/31/%(arch)s/updates/silverblue',
>> + 'dest': OSTREEDEST,
>> + 'arches': ['x86_64', 'ppc64le', 
>> 'aarch64']},
> 
> I think this is missing another ] at the end before the comma (to match 
> with the [ after 'ostrees':
> 
>>   'to': [{'arches': ['x86_64', 'armhfp', 'aarch64', 
>> 'source'],
>>   'dest': os.path.join(FEDORADEST, '31', 
>> 'Everything')},
>>  {'arches': ['ppc64le', 's390x'],
>> @@ -34,8 +35,9 @@ RELEASES = {'f31': {'topic': 'fedora',
>> ]},
>> 'updates-testing': {
>>   'from': 'f31-updates-testing',
>> -'ostrees': [{'ref': 
>> 'fedora/31/x86_64/testing/silverblue',
>> - 'dest': OSTREEDEST}],
>> +'ostrees': [{'ref': 
>> 'fedora/31/%(arch)s/testing/silverblue',
>> + 'dest': OSTREEDEST,
>> + 'arches': ['x86_64', 'ppc64le', 
>> 'aarch64']},
> 
> Same here.
> 
>>   'to': [{'arches': ['x86_64', 'aarch64', 'armhfp', 
>> 'source'],
>>   'dest': os.path.join(FEDORADEST, 
>> 'testing', '31', 'Everything')},
>>  {'arches': ['ppc64le', 's390x'],
>>
> ___
> infrastructure mailing list -- infrastructure@lists.fedoraproject.org
> To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
> 
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org

Re: [PATCH 2/2] bodhi-pungi: enable aarch64 and ppc64le for silverblue updates

[Rick Elrod]

+1

-re

On 2019-10-24 15:51, Mohan Boddu wrote:

+1 LGTM

On Thu, Oct 24, 2019 at 3:36 PM Dusty Mabe  wrote:


---
  roles/bodhi2/backend/templates/pungi.rpm.conf.j2 | 4 ++--
  1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/roles/bodhi2/backend/templates/pungi.rpm.conf.j2 
b/roles/bodhi2/backend/templates/pungi.rpm.conf.j2
index 28b524a10..640ddf058 100644
--- a/roles/bodhi2/backend/templates/pungi.rpm.conf.j2
+++ b/roles/bodhi2/backend/templates/pungi.rpm.conf.j2
@@ -193,8 +193,8 @@ ostree = {
  "ostree_ref": "fedora/[[ release.version_int 
]]/${basearch}/testing/silverblue",
  [% endif %]
  "tag_ref": False,
-"arches": ["x86_64"],
-"failable": ["x86_64"]
+"arches": ["x86_64", "ppc64le", "aarch64" ],
+"failable": ["x86_64", "ppc64le", "aarch64" ]
  },
  ]
  }
--
2.20.1
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org

___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org


___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org

Re: [PATCH 1/2] bodhi-pungi: F32 will be the next "branched"

[Rick Elrod]

+1 for the same reason.

-re

On 2019-10-24 16:23, Mohan Boddu wrote:

Since rawhide is not uses pungi, I think we are okay with this change.

+1 LGTM

On Thu, Oct 24, 2019 at 4:13 PM Mohan Boddu  wrote:


No, with rawhide gating we are using bodhi to push rawhide builds as
updates, I think it might call it and cause some issues.

On Thu, Oct 24, 2019 at 4:05 PM Dusty Mabe  wrote:




On 10/24/19 4:02 PM, Mohan Boddu wrote:

Just wondering, doesn't it affect rawhide composes, since rawhide is still 32?



IIUC the first time this will take any effect is when we start calling bodhi 
with '32'
as the number (i.e. after we have branched and rawhide is now 33).

Dusty


___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org


___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org

Re: [PATCH] new-updates-sync: sync multiarch silverblue ostree content

[Rick Elrod]

+1 after the syntax fix I mentioned inline.

-re

On 2019-10-24 15:56, Dusty Mabe wrote:

---
  roles/bodhi2/backend/files/new-updates-sync | 10 ++
  1 file changed, 6 insertions(+), 4 deletions(-)

diff --git a/roles/bodhi2/backend/files/new-updates-sync 
b/roles/bodhi2/backend/files/new-updates-sync
index d08c89301..9ad7628b8 100755
--- a/roles/bodhi2/backend/files/new-updates-sync
+++ b/roles/bodhi2/backend/files/new-updates-sync
@@ -25,8 +25,9 @@ RELEASES = {'f31': {'topic': 'fedora',
  'modules': ['fedora', 'fedora-secondary'],
  'repos': {'updates': {
  'from': 'f31-updates',
-'ostrees': [{'ref': 
'fedora/31/x86_64/updates/silverblue',
- 'dest': OSTREEDEST}],
+'ostrees': [{'ref': 
'fedora/31/%(arch)s/updates/silverblue',
+ 'dest': OSTREEDEST,
+ 'arches': ['x86_64', 'ppc64le', 
'aarch64']},


I think this is missing another ] at the end before the comma (to match 
with the [ after 'ostrees':



  'to': [{'arches': ['x86_64', 'armhfp', 'aarch64', 
'source'],
  'dest': os.path.join(FEDORADEST, '31', 
'Everything')},
 {'arches': ['ppc64le', 's390x'],
@@ -34,8 +35,9 @@ RELEASES = {'f31': {'topic': 'fedora',
]},
'updates-testing': {
  'from': 'f31-updates-testing',
-'ostrees': [{'ref': 
'fedora/31/x86_64/testing/silverblue',
- 'dest': OSTREEDEST}],
+'ostrees': [{'ref': 
'fedora/31/%(arch)s/testing/silverblue',
+ 'dest': OSTREEDEST,
+ 'arches': ['x86_64', 'ppc64le', 
'aarch64']},


Same here.


  'to': [{'arches': ['x86_64', 'aarch64', 'armhfp', 
'source'],
  'dest': os.path.join(FEDORADEST, 'testing', 
'31', 'Everything')},
 {'arches': ['ppc64le', 's390x'],


___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org

Re: Please review: MBS platform definition for EPEL8

[Merlin Mathesius]

On Thu, Oct 24, 2019 at 3:32 PM Mohan Boddu  wrote:

> Hi,
>
> I created the tags as module-epel8-build and
> module-epel8-playground-build just to be consistent with the naming, so you
> need to change the config for koji_tag part.
>
> And may be also change the "stream" in the yaml file to epel8 and
> epel8-playground and change the name of the platform to platform-epel8 and
> platform-epel8-playground, again just for consistency.
>
> Other than that, its LGTM.
>

Thanks for taking a look.

There was discussion about the "el8" vs "epel8" naming during the
preliminary review and discussion. It should be "el8" to work correctly
with RHEL 8 as explained in Petr's comment at
https://pagure.io/Fedora-Infra/ansible/pull-request/40#comment-96326.

But yeah, it keeps tripping me up, too!


> On Thu, Oct 24, 2019 at 3:43 PM Merlin Mathesius 
> wrote:
>
>> Now that the build tags have been created (thanks, Mohan!), we should be
>> ready to add the virtual platform module definitions for EPEL-8 to Fedora
>> staging MBS.
>>
>> I have attached a revised patch that includes both the el8 and
>> el8-playground definitions in a single patch file. Aside from the combined
>> patch, the only difference from the previous separate patches is the
>> addition of the 'default_modules_scm_url' and 'use_default_modules'
>> settings to enable ursa prime.
>>
>> Thanks.
>>
>> Merlin
>>
>>
>> On Wed, Oct 2, 2019 at 5:07 PM Merlin Mathesius 
>> wrote:
>>
>>>
>>>
>>> On Wed, Oct 2, 2019 at 12:41 PM Matt Prahl  wrote:
>>>
 Hi Merlin,
 I can't think of anything that you need to do before merging and
 deploying them as long as the Koji tags mentioned in the modulemd files are
 all set.

>>>
>>> Of course. We need the module-el8-build and module-el8-playground-build
>>> tags. I just created https://pagure.io/releng/issue/8865 for that.
>>>
>>> Thanks, Matt!
>>>
>>> On Wed, Oct 2, 2019 at 12:12 PM Merlin Mathesius 
 wrote:

> Hi, Matt, Jan,
>
> Could one of you provide some input here?
>
> We're looking to add the virtual platform module definitions for
> EPEL-8 to Fedora staging MBS. Is there anything specific that needs to
> happen before merging and deploying them?
>
> If you'd like to review the definitions, the patches are re-attached
> to this message so you don't need to go digging.
>
> Merlin
>
> On Tue, Oct 1, 2019 at 11:43 AM Kevin Fenzi  wrote:
>
>> On Mon, Sep 30, 2019 at 02:14:14PM -0500, Merlin Mathesius wrote:
>> > Hi, all,
>> >
>> > Since folks seem to be happy with the el8 platform virtual module
>> > definitions, can they be merged and deployed to staging--or does
>> something
>> > else need to happen first? (Of course, any module builds based on
>> > platform:el8* won't be usable until there are corresponding pungi
>> configs.)
>>
>> I'm not entirely sure. :)
>>
>> Can we ask some of the mbs folks what all is needed here?
>>
>> kevin
>> ___
>> infrastructure mailing list -- infrastructure@lists.fedoraproject.org
>> To unsubscribe send an email to
>> infrastructure-le...@lists.fedoraproject.org
>> Fedora Code of Conduct:
>> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>> List Guidelines:
>> https://fedoraproject.org/wiki/Mailing_list_guidelines
>> List Archives:
>> https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
>>
>

 --

 Matt Prahl

 Senior Software Engineer, PnT DevOps

 Red Hat 

 Westford, MA

 mpr...@redhat.com
 M: 802-999-0972 IM: mprahl
 

>>> ___
>> infrastructure mailing list -- infrastructure@lists.fedoraproject.org
>> To unsubscribe send an email to
>> infrastructure-le...@lists.fedoraproject.org
>> Fedora Code of Conduct:
>> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>> List Archives:
>> https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
>>
> ___
> infrastructure mailing list -- infrastructure@lists.fedoraproject.org
> To unsubscribe send an email to
> infrastructure-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
>
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct: 

FBR: Update releases.json to make f31 active and no retirement

[Mohan Boddu]

Hi,

Another FBR to update releases.json to make sure retirement is not allowed

diff --git a/roles/pkgdb-proxy/files/pkgdb-gnome-software-collections.json
b/roles/pkgdb-proxy/files/pkgdb-gnome-software-collections
index aac977e..9e0cbf2 100644
--- a/roles/pkgdb-proxy/files/pkgdb-gnome-software-collections.json
+++ b/roles/pkgdb-proxy/files/pkgdb-gnome-software-collections.json
@@ -12,14 +12,14 @@
   "version": "devel"
 },
 {
-  "allow_retire": true,
+  "allow_retire": false,
   "branchname": "f31",
   "date_created": "2014-05-14 12:36:15",
   "date_updated": "2018-08-14 17:07:23",
   "dist_tag": ".fc31",
   "koji_name": "f31",
   "name": "Fedora",
-  "status": "Under Development",
+  "status": "Active",
   "version": "31"
 },
 {
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org

Re: Please review: MBS platform definition for EPEL8

[Mohan Boddu]

Hi,

I created the tags as module-epel8-build and
module-epel8-playground-build just to be consistent with the naming, so you
need to change the config for koji_tag part.

And may be also change the "stream" in the yaml file to epel8 and
epel8-playground and change the name of the platform to platform-epel8 and
platform-epel8-playground, again just for consistency.

Other than that, its LGTM.

On Thu, Oct 24, 2019 at 3:43 PM Merlin Mathesius 
wrote:

> Now that the build tags have been created (thanks, Mohan!), we should be
> ready to add the virtual platform module definitions for EPEL-8 to Fedora
> staging MBS.
>
> I have attached a revised patch that includes both the el8 and
> el8-playground definitions in a single patch file. Aside from the combined
> patch, the only difference from the previous separate patches is the
> addition of the 'default_modules_scm_url' and 'use_default_modules'
> settings to enable ursa prime.
>
> Thanks.
>
> Merlin
>
>
> On Wed, Oct 2, 2019 at 5:07 PM Merlin Mathesius 
> wrote:
>
>>
>>
>> On Wed, Oct 2, 2019 at 12:41 PM Matt Prahl  wrote:
>>
>>> Hi Merlin,
>>> I can't think of anything that you need to do before merging and
>>> deploying them as long as the Koji tags mentioned in the modulemd files are
>>> all set.
>>>
>>
>> Of course. We need the module-el8-build and module-el8-playground-build
>> tags. I just created https://pagure.io/releng/issue/8865 for that.
>>
>> Thanks, Matt!
>>
>> On Wed, Oct 2, 2019 at 12:12 PM Merlin Mathesius 
>>> wrote:
>>>
 Hi, Matt, Jan,

 Could one of you provide some input here?

 We're looking to add the virtual platform module definitions for EPEL-8
 to Fedora staging MBS. Is there anything specific that needs to happen
 before merging and deploying them?

 If you'd like to review the definitions, the patches are re-attached to
 this message so you don't need to go digging.

 Merlin

 On Tue, Oct 1, 2019 at 11:43 AM Kevin Fenzi  wrote:

> On Mon, Sep 30, 2019 at 02:14:14PM -0500, Merlin Mathesius wrote:
> > Hi, all,
> >
> > Since folks seem to be happy with the el8 platform virtual module
> > definitions, can they be merged and deployed to staging--or does
> something
> > else need to happen first? (Of course, any module builds based on
> > platform:el8* won't be usable until there are corresponding pungi
> configs.)
>
> I'm not entirely sure. :)
>
> Can we ask some of the mbs folks what all is needed here?
>
> kevin
> ___
> infrastructure mailing list -- infrastructure@lists.fedoraproject.org
> To unsubscribe send an email to
> infrastructure-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines:
> https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
>

>>>
>>> --
>>>
>>> Matt Prahl
>>>
>>> Senior Software Engineer, PnT DevOps
>>>
>>> Red Hat 
>>>
>>> Westford, MA
>>>
>>> mpr...@redhat.com
>>> M: 802-999-0972 IM: mprahl
>>> 
>>>
>> ___
> infrastructure mailing list -- infrastructure@lists.fedoraproject.org
> To unsubscribe send an email to
> infrastructure-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
>
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org

Re: [PATCH 1/2] bodhi-pungi: F32 will be the next "branched"

[Mohan Boddu]

Since rawhide is not uses pungi, I think we are okay with this change.

+1 LGTM

On Thu, Oct 24, 2019 at 4:13 PM Mohan Boddu  wrote:
>
> No, with rawhide gating we are using bodhi to push rawhide builds as
> updates, I think it might call it and cause some issues.
>
> On Thu, Oct 24, 2019 at 4:05 PM Dusty Mabe  wrote:
> >
> >
> >
> > On 10/24/19 4:02 PM, Mohan Boddu wrote:
> > > Just wondering, doesn't it affect rawhide composes, since rawhide is 
> > > still 32?
> > >
> >
> > IIUC the first time this will take any effect is when we start calling 
> > bodhi with '32'
> > as the number (i.e. after we have branched and rawhide is now 33).
> >
> > Dusty
> >
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org

Re: [PATCH 1/2] bodhi-pungi: F32 will be the next "branched"

[Mohan Boddu]

No, with rawhide gating we are using bodhi to push rawhide builds as
updates, I think it might call it and cause some issues.

On Thu, Oct 24, 2019 at 4:05 PM Dusty Mabe  wrote:
>
>
>
> On 10/24/19 4:02 PM, Mohan Boddu wrote:
> > Just wondering, doesn't it affect rawhide composes, since rawhide is still 
> > 32?
> >
>
> IIUC the first time this will take any effect is when we start calling bodhi 
> with '32'
> as the number (i.e. after we have branched and rawhide is now 33).
>
> Dusty
>
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org

Re: [PATCH] new-updates-sync: sync multiarch silverblue ostree content

[Mohan Boddu]

+1 LGTM

On Thu, Oct 24, 2019 at 3:57 PM Dusty Mabe  wrote:
>
> ---
>  roles/bodhi2/backend/files/new-updates-sync | 10 ++
>  1 file changed, 6 insertions(+), 4 deletions(-)
>
> diff --git a/roles/bodhi2/backend/files/new-updates-sync 
> b/roles/bodhi2/backend/files/new-updates-sync
> index d08c89301..9ad7628b8 100755
> --- a/roles/bodhi2/backend/files/new-updates-sync
> +++ b/roles/bodhi2/backend/files/new-updates-sync
> @@ -25,8 +25,9 @@ RELEASES = {'f31': {'topic': 'fedora',
>  'modules': ['fedora', 'fedora-secondary'],
>  'repos': {'updates': {
>  'from': 'f31-updates',
> -'ostrees': [{'ref': 
> 'fedora/31/x86_64/updates/silverblue',
> - 'dest': OSTREEDEST}],
> +'ostrees': [{'ref': 
> 'fedora/31/%(arch)s/updates/silverblue',
> + 'dest': OSTREEDEST,
> + 'arches': ['x86_64', 'ppc64le', 
> 'aarch64']},
>  'to': [{'arches': ['x86_64', 'armhfp', 'aarch64', 
> 'source'],
>  'dest': os.path.join(FEDORADEST, '31', 
> 'Everything')},
> {'arches': ['ppc64le', 's390x'],
> @@ -34,8 +35,9 @@ RELEASES = {'f31': {'topic': 'fedora',
>]},
>'updates-testing': {
>  'from': 'f31-updates-testing',
> -'ostrees': [{'ref': 
> 'fedora/31/x86_64/testing/silverblue',
> - 'dest': OSTREEDEST}],
> +'ostrees': [{'ref': 
> 'fedora/31/%(arch)s/testing/silverblue',
> + 'dest': OSTREEDEST,
> + 'arches': ['x86_64', 'ppc64le', 
> 'aarch64']},
>  'to': [{'arches': ['x86_64', 'aarch64', 'armhfp', 
> 'source'],
>  'dest': os.path.join(FEDORADEST, 'testing', 
> '31', 'Everything')},
> {'arches': ['ppc64le', 's390x'],
> --
> 2.20.1
> ___
> infrastructure mailing list -- infrastructure@lists.fedoraproject.org
> To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org

Re: [PATCH 1/2] bodhi-pungi: F32 will be the next "branched"

[Dusty Mabe]

On 10/24/19 4:02 PM, Mohan Boddu wrote:
> Just wondering, doesn't it affect rawhide composes, since rawhide is still 32?
> 

IIUC the first time this will take any effect is when we start calling bodhi 
with '32'
as the number (i.e. after we have branched and rawhide is now 33).

Dusty
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org

Re: [PATCH 1/2] bodhi-pungi: F32 will be the next "branched"

[Mohan Boddu]

Just wondering, doesn't it affect rawhide composes, since rawhide is still 32?

On Thu, Oct 24, 2019 at 3:36 PM Dusty Mabe  wrote:
>
> Now that f31 is go we can use the final location for ostree repo input.
> Bump the variable so that it will only look at branched for f32.
> ---
>  roles/bodhi2/backend/templates/pungi.rpm.conf.j2 | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/roles/bodhi2/backend/templates/pungi.rpm.conf.j2 
> b/roles/bodhi2/backend/templates/pungi.rpm.conf.j2
> index 688badeee..28b524a10 100644
> --- a/roles/bodhi2/backend/templates/pungi.rpm.conf.j2
> +++ b/roles/bodhi2/backend/templates/pungi.rpm.conf.j2
> @@ -179,8 +179,8 @@ ostree = {
>  # In the case of testing, also inject the last stable 
> updates
>  "https://kojipkgs{{ env_suffix 
> }}.fedoraproject.org/compose/updates/f[[ release.version_int 
> ]]-updates/compose/Everything/$basearch/os/",
>  [% endif %]
> -# For f31 the compose location is going to be under 
> /compose/branched/
> -[% if release.version_int == 31 %]
> +# For F32 the compose location is going to be under 
> /compose/branched/
> +[% if release.version_int == 32 %]
>  "https://kojipkgs{{ env_suffix 
> }}.fedoraproject.org/compose/branched/latest-Fedora-[[ release.version_int 
> ]]/compose/Everything/$basearch/os/"
>  [% else %]
>  "https://kojipkgs{{ env_suffix 
> }}.fedoraproject.org/compose/[[ release.version_int ]]/latest-Fedora-[[ 
> release.version_int ]]/compose/Everything/$basearch/os/"
> --
> 2.20.1
> ___
> infrastructure mailing list -- infrastructure@lists.fedoraproject.org
> To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org

[PATCH] new-updates-sync: sync multiarch silverblue ostree content

[Dusty Mabe]

---
 roles/bodhi2/backend/files/new-updates-sync | 10 ++
 1 file changed, 6 insertions(+), 4 deletions(-)

diff --git a/roles/bodhi2/backend/files/new-updates-sync 
b/roles/bodhi2/backend/files/new-updates-sync
index d08c89301..9ad7628b8 100755
--- a/roles/bodhi2/backend/files/new-updates-sync
+++ b/roles/bodhi2/backend/files/new-updates-sync
@@ -25,8 +25,9 @@ RELEASES = {'f31': {'topic': 'fedora',
 'modules': ['fedora', 'fedora-secondary'],
 'repos': {'updates': {
 'from': 'f31-updates',
-'ostrees': [{'ref': 
'fedora/31/x86_64/updates/silverblue',
- 'dest': OSTREEDEST}],
+'ostrees': [{'ref': 
'fedora/31/%(arch)s/updates/silverblue',
+ 'dest': OSTREEDEST,
+ 'arches': ['x86_64', 'ppc64le', 
'aarch64']},
 'to': [{'arches': ['x86_64', 'armhfp', 'aarch64', 
'source'],
 'dest': os.path.join(FEDORADEST, '31', 
'Everything')},
{'arches': ['ppc64le', 's390x'],
@@ -34,8 +35,9 @@ RELEASES = {'f31': {'topic': 'fedora',
   ]},
   'updates-testing': {
 'from': 'f31-updates-testing',
-'ostrees': [{'ref': 
'fedora/31/x86_64/testing/silverblue',
- 'dest': OSTREEDEST}],
+'ostrees': [{'ref': 
'fedora/31/%(arch)s/testing/silverblue',
+ 'dest': OSTREEDEST,
+ 'arches': ['x86_64', 'ppc64le', 
'aarch64']},
 'to': [{'arches': ['x86_64', 'aarch64', 'armhfp', 
'source'],
 'dest': os.path.join(FEDORADEST, 'testing', 
'31', 'Everything')},
{'arches': ['ppc64le', 's390x'],
-- 
2.20.1
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org

FBR new-updates-sync: sync multiarch silverblue ostree content

[Dusty Mabe]

[PATCH] new-updates-sync: sync multiarch silverblue ostree content
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org

Re: [PATCH 2/2] bodhi-pungi: enable aarch64 and ppc64le for silverblue updates

[Mohan Boddu]

+1 LGTM

On Thu, Oct 24, 2019 at 3:36 PM Dusty Mabe  wrote:
>
> ---
>  roles/bodhi2/backend/templates/pungi.rpm.conf.j2 | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/roles/bodhi2/backend/templates/pungi.rpm.conf.j2 
> b/roles/bodhi2/backend/templates/pungi.rpm.conf.j2
> index 28b524a10..640ddf058 100644
> --- a/roles/bodhi2/backend/templates/pungi.rpm.conf.j2
> +++ b/roles/bodhi2/backend/templates/pungi.rpm.conf.j2
> @@ -193,8 +193,8 @@ ostree = {
>  "ostree_ref": "fedora/[[ release.version_int 
> ]]/${basearch}/testing/silverblue",
>  [% endif %]
>  "tag_ref": False,
> -"arches": ["x86_64"],
> -"failable": ["x86_64"]
> +"arches": ["x86_64", "ppc64le", "aarch64" ],
> +"failable": ["x86_64", "ppc64le", "aarch64" ]
>  },
>  ]
>  }
> --
> 2.20.1
> ___
> infrastructure mailing list -- infrastructure@lists.fedoraproject.org
> To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org

Re: Please review: MBS platform definition for EPEL8

[Merlin Mathesius]

Now that the build tags have been created (thanks, Mohan!), we should be
ready to add the virtual platform module definitions for EPEL-8 to Fedora
staging MBS.

I have attached a revised patch that includes both the el8 and
el8-playground definitions in a single patch file. Aside from the combined
patch, the only difference from the previous separate patches is the
addition of the 'default_modules_scm_url' and 'use_default_modules'
settings to enable ursa prime.

Thanks.

Merlin


On Wed, Oct 2, 2019 at 5:07 PM Merlin Mathesius  wrote:

>
>
> On Wed, Oct 2, 2019 at 12:41 PM Matt Prahl  wrote:
>
>> Hi Merlin,
>> I can't think of anything that you need to do before merging and
>> deploying them as long as the Koji tags mentioned in the modulemd files are
>> all set.
>>
>
> Of course. We need the module-el8-build and module-el8-playground-build
> tags. I just created https://pagure.io/releng/issue/8865 for that.
>
> Thanks, Matt!
>
> On Wed, Oct 2, 2019 at 12:12 PM Merlin Mathesius 
>> wrote:
>>
>>> Hi, Matt, Jan,
>>>
>>> Could one of you provide some input here?
>>>
>>> We're looking to add the virtual platform module definitions for EPEL-8
>>> to Fedora staging MBS. Is there anything specific that needs to happen
>>> before merging and deploying them?
>>>
>>> If you'd like to review the definitions, the patches are re-attached to
>>> this message so you don't need to go digging.
>>>
>>> Merlin
>>>
>>> On Tue, Oct 1, 2019 at 11:43 AM Kevin Fenzi  wrote:
>>>
 On Mon, Sep 30, 2019 at 02:14:14PM -0500, Merlin Mathesius wrote:
 > Hi, all,
 >
 > Since folks seem to be happy with the el8 platform virtual module
 > definitions, can they be merged and deployed to staging--or does
 something
 > else need to happen first? (Of course, any module builds based on
 > platform:el8* won't be usable until there are corresponding pungi
 configs.)

 I'm not entirely sure. :)

 Can we ask some of the mbs folks what all is needed here?

 kevin
 ___
 infrastructure mailing list -- infrastructure@lists.fedoraproject.org
 To unsubscribe send an email to
 infrastructure-le...@lists.fedoraproject.org
 Fedora Code of Conduct:
 https://docs.fedoraproject.org/en-US/project/code-of-conduct/
 List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
 List Archives:
 https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org

>>>
>>
>> --
>>
>> Matt Prahl
>>
>> Senior Software Engineer, PnT DevOps
>>
>> Red Hat 
>>
>> Westford, MA
>>
>> mpr...@redhat.com
>> M: 802-999-0972 IM: mprahl
>> 
>>
>
From 83b8950c65621fd8dcee02548c7c53d7f5b28cd9 Mon Sep 17 00:00:00 2001
From: Merlin Mathesius 
Date: Thu, 24 Oct 2019 14:25:12 -0500
Subject: [PATCH] Adding EL8 and EL8 playground platforms

Signed-off-by: Merlin Mathesius 
---
 .../platform-el8-playground.yaml  | 25 +++
 .../default-modules.staging/platform-el8.yaml | 25 +++
 2 files changed, 50 insertions(+)
 create mode 100644 roles/mbs/common/files/default-modules.staging/platform-el8-playground.yaml
 create mode 100644 roles/mbs/common/files/default-modules.staging/platform-el8.yaml

diff --git a/roles/mbs/common/files/default-modules.staging/platform-el8-playground.yaml b/roles/mbs/common/files/default-modules.staging/platform-el8-playground.yaml
new file mode 100644
index 0..f5f214c0d
--- /dev/null
+++ b/roles/mbs/common/files/default-modules.staging/platform-el8-playground.yaml
@@ -0,0 +1,25 @@
+document: modulemd
+version: 1
+data:
+  name: platform
+  stream: el8-playground
+  version: 1
+  context: 
+  summary: EPEL 8 playground base
+  description: EPEL 8 playground base
+  license:
+module: [MIT]
+  profiles:
+buildroot:
+  rpms: [bash, bzip2, coreutils, cpio, diffutils, epel-release, epel-rpm-macros, fedpkg-minimal, findutils, gawk, gcc, gcc-c++, grep, gzip, info, make, patch, redhat-release, redhat-release-everything, redhat-release-server, redhat-rpm-config, rpm-build, sed, shadow-utils, tar, unzip, util-linux, util-linux-ng, which, xz]
+srpm-buildroot:
+  rpms: [bash, epel-release, epel-rpm-macros, fedpkg-minimal, git, gnupg, make, redhat-release, redhat-release-everything, redhat-release-server, redhat-rpm-config, rpm-build, shadow-utils]
+  xmd:
+mbs:
+  buildrequires: {}
+  commit: el8
+  requires: {}
+  koji_tag: module-el8-playground-build
+  mse: TRUE
+  default_modules_scm_url: https://pagure.io/modularity/fedora-stg-module-defaults.git
+  use_default_modules: TRUE
diff --git a/roles/mbs/common/files/default-modules.staging/platform-el8.yaml b/roles/mbs/common/files/default-modules.staging/platform-el8.yaml
new file mode 100644
index 0..df02347a1
--- /dev/null
+++ b/roles/mbs/common/files/default-modules.staging/platform-el8.yaml

[PATCH 2/2] bodhi-pungi: enable aarch64 and ppc64le for silverblue updates

[Dusty Mabe]

---
 roles/bodhi2/backend/templates/pungi.rpm.conf.j2 | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/roles/bodhi2/backend/templates/pungi.rpm.conf.j2 
b/roles/bodhi2/backend/templates/pungi.rpm.conf.j2
index 28b524a10..640ddf058 100644
--- a/roles/bodhi2/backend/templates/pungi.rpm.conf.j2
+++ b/roles/bodhi2/backend/templates/pungi.rpm.conf.j2
@@ -193,8 +193,8 @@ ostree = {
 "ostree_ref": "fedora/[[ release.version_int 
]]/${basearch}/testing/silverblue",
 [% endif %]
 "tag_ref": False,
-"arches": ["x86_64"],
-"failable": ["x86_64"]
+"arches": ["x86_64", "ppc64le", "aarch64" ],
+"failable": ["x86_64", "ppc64le", "aarch64" ]
 },
 ]
 }
-- 
2.20.1
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org

FBR: updates Silverblue in bodhi pungi config

[Dusty Mabe]

[PATCH 1/2] bodhi-pungi: F32 will be the next "branched"
[PATCH 2/2] bodhi-pungi: enable aarch64 and ppc64le for silverblue

Now that F31 is a go we need to do a few things. One of them
is enabling other architectures, which was done in rawhide and f31.
This propagates it into bodhi.

___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org

[PATCH 1/2] bodhi-pungi: F32 will be the next "branched"

[Dusty Mabe]

Now that f31 is go we can use the final location for ostree repo input.
Bump the variable so that it will only look at branched for f32.
---
 roles/bodhi2/backend/templates/pungi.rpm.conf.j2 | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/roles/bodhi2/backend/templates/pungi.rpm.conf.j2 
b/roles/bodhi2/backend/templates/pungi.rpm.conf.j2
index 688badeee..28b524a10 100644
--- a/roles/bodhi2/backend/templates/pungi.rpm.conf.j2
+++ b/roles/bodhi2/backend/templates/pungi.rpm.conf.j2
@@ -179,8 +179,8 @@ ostree = {
 # In the case of testing, also inject the last stable 
updates
 "https://kojipkgs{{ env_suffix 
}}.fedoraproject.org/compose/updates/f[[ release.version_int 
]]-updates/compose/Everything/$basearch/os/",
 [% endif %]
-# For f31 the compose location is going to be under 
/compose/branched/
-[% if release.version_int == 31 %]
+# For F32 the compose location is going to be under 
/compose/branched/
+[% if release.version_int == 32 %]
 "https://kojipkgs{{ env_suffix 
}}.fedoraproject.org/compose/branched/latest-Fedora-[[ release.version_int 
]]/compose/Everything/$basearch/os/"
 [% else %]
 "https://kojipkgs{{ env_suffix 
}}.fedoraproject.org/compose/[[ release.version_int ]]/latest-Fedora-[[ 
release.version_int ]]/compose/Everything/$basearch/os/"
-- 
2.20.1
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org

Re: FBR: Update koji-sidetag-plugin on Koji hub

[Clement Verna]

+1 too

On Thu, 24 Oct 2019 at 21:07, Pierre-Yves Chibon 
wrote:

> On Thu, Oct 24, 2019 at 03:30:50PM +0200, Mikolaj Izdebski wrote:
> > In order to fix issue 8322 [1] python2-koji-sidetag-plugin-hub needs
> > to be updated. This would be done with the following commands:
> >
> > $ koji move epel7-infra-stg epel7-infra
> koji-sidetag-plugin-0.1-2.el7.infra
> >
> > [root@batcave01]# ansible koji -m package -a
> > 'name=python2-koji-sidetag-plugin-hub state=latest update_cache=yes
> > update_only=yes'
> >
> > [root@batcave01]# ansible koji -m service -a 'name=httpd state=reloaded'
>
> +1 for me, and thanks for looking at this!
>
> Pierre
> ___
> infrastructure mailing list -- infrastructure@lists.fedoraproject.org
> To unsubscribe send an email to
> infrastructure-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
>
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org

Re: FBR: Update koji-sidetag-plugin on Koji hub

[Stephen John Smoogen]

+1 and thank you

On Thu, 24 Oct 2019 at 09:31, Mikolaj Izdebski  wrote:
>
> In order to fix issue 8322 [1] python2-koji-sidetag-plugin-hub needs
> to be updated. This would be done with the following commands:
>
> $ koji move epel7-infra-stg epel7-infra koji-sidetag-plugin-0.1-2.el7.infra
>
> [root@batcave01]# ansible koji -m package -a
> 'name=python2-koji-sidetag-plugin-hub state=latest update_cache=yes
> update_only=yes'
>
> [root@batcave01]# ansible koji -m service -a 'name=httpd state=reloaded'
>
> [1] https://pagure.io/fedora-infrastructure/issue/8322
> ___
> infrastructure mailing list -- infrastructure@lists.fedoraproject.org
> To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org



-- 
Stephen J Smoogen.
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org

Re: FBR: Update koji-sidetag-plugin on Koji hub

[Pierre-Yves Chibon]

On Thu, Oct 24, 2019 at 03:30:50PM +0200, Mikolaj Izdebski wrote:
> In order to fix issue 8322 [1] python2-koji-sidetag-plugin-hub needs
> to be updated. This would be done with the following commands:
> 
> $ koji move epel7-infra-stg epel7-infra koji-sidetag-plugin-0.1-2.el7.infra
> 
> [root@batcave01]# ansible koji -m package -a
> 'name=python2-koji-sidetag-plugin-hub state=latest update_cache=yes
> update_only=yes'
> 
> [root@batcave01]# ansible koji -m service -a 'name=httpd state=reloaded'

+1 for me, and thanks for looking at this!

Pierre
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org

Re: FBR: F31 Final is GO, bodhi config changes

[Mikolaj Izdebski]

+1

On Thu, Oct 24, 2019 at 8:35 PM Mohan Boddu  wrote:
>
> Also, one more simple FBR,
>
> Disabling branched compose
>
> diff --git a/roles/releng/files/branched b/roles/releng/files/branched
> index 966f5c3..1f52f56 100644
> --- a/roles/releng/files/branched
> +++ b/roles/releng/files/branched
> @@ -1,3 +1,3 @@
>  # branched compose
>  MAILTO=releng-c...@lists.fedoraproject.org
> -15 7 * * * root TMPDIR=`mktemp -d /tmp/branched.XX` && cd $TMPDIR
> && git clone https://pagure.io/pungi-fedora.git && cd pungi-fedora &&
> git checkout f31 && /usr/local/bin/lock-wrapper branched-compose
> "PYTHONMALLOC=debug LANG=en_US.UTF-8 ./nightly.sh" && sudo -u ftpsync
> /usr/local/bin/update-fullfiletimelist -l
> /pub/fedora-secondary/update-fullfiletimelist.lock -t /pub fedora
> fedora-secondary
> +#15 7 * * * root TMPDIR=`mktemp -d /tmp/branched.XX` && cd
> $TMPDIR && git clone https://pagure.io/pungi-fedora.git && cd
> pungi-fedora && git checkout f31 && /usr/local/bin/lock-wrapper
> branched-compose "PYTHONMALLOC=debug LANG=en_US.UTF-8 ./nightly.sh" &&
> sudo -u ftpsync /usr/local/bin/update-fullfiletimelist -l
> /pub/fedora-secondary/update-fullfiletimelist.lock -t /pub fedora
> fedora-secondary
>
> I am currently running a branched compose, so that the RC and branched
> compose will have the same content.
>
> Once the run is done, I will push all these changes and then either
> run full updates push or let the automated pushes take care of it
> based on the timing.
>
> I cannot run f31 stable updates push yet, since it might screw up the
> silverblue refs if branched is completed after the f31 stable updates
> push.
>
> Thanks.
>
> On Thu, Oct 24, 2019 at 2:27 PM Mikolaj Izdebski  wrote:
> >
> > +1
> >
> > On Thu, Oct 24, 2019 at 7:51 PM Mohan Boddu  wrote:
> > >
> > > Hi,
> > >
> > > Now that F31 is GO, I would like the make the necessary changes to
> > > bodhi configs.
> > >
> > > "vars/all/Frozen.yaml" 1L, 15C written
> > > [mohanboddu@batcave01 ansible][PROD]$ git diff
> > > diff --git a/vars/all/00-FedoraCycleNumber.yaml
> > > b/vars/all/00-FedoraCycleNumber.yaml
> > > index 22476b0..4bd0d46 100644
> > > --- a/vars/all/00-FedoraCycleNumber.yaml
> > > +++ b/vars/all/00-FedoraCycleNumber.yaml
> > > @@ -1 +1 @@
> > > -FedoraCycleNumber: 30
> > > +FedoraCycleNumber: 31
> > > diff --git a/vars/all/FedoraBranched.yaml b/vars/all/FedoraBranched.yaml
> > > index 42ac534..0bbcc1d 100644
> > > --- a/vars/all/FedoraBranched.yaml
> > > +++ b/vars/all/FedoraBranched.yaml
> > > @@ -1 +1 @@
> > > -FedoraBranched: True
> > > +FedoraBranched: False
> > > diff --git a/vars/all/FedoraBranchedBodhi.yaml
> > > b/vars/all/FedoraBranchedBodhi.yaml
> > > index 380f61d..76ba14d 100644
> > > --- a/vars/all/FedoraBranchedBodhi.yaml
> > > +++ b/vars/all/FedoraBranchedBodhi.yaml
> > > @@ -1,2 +1,2 @@
> > >  #options are: prebeta, postbeta, current
> > > -FedoraBranchedBodhi: postbeta
> > > +FedoraBranchedBodhi: current
> > > diff --git a/vars/all/FedoraPreviousPrevious.yaml
> > > b/vars/all/FedoraPreviousPrevious.yaml
> > > index a8e3d3b..a061e04 100644
> > > --- a/vars/all/FedoraPreviousPrevious.yaml
> > > +++ b/vars/all/FedoraPreviousPrevious.yaml
> > > @@ -1 +1 @@
> > > -FedoraPreviousPrevious: False
> > > +FedoraPreviousPrevious: True
> > > diff --git a/vars/all/Frozen.yaml b/vars/all/Frozen.yaml
> > > index 97d3bc3..7578a88 100644
> > > --- a/vars/all/Frozen.yaml
> > > +++ b/vars/all/Frozen.yaml
> > > @@ -1 +1 @@
> > > -Frozen: True
> > > +Frozen: False
> > > diff --git a/vars/all/RelEngFrozen.yaml b/vars/all/RelEngFrozen.yaml
> > > index bd7553f..72af779 100644
> > > --- a/vars/all/RelEngFrozen.yaml
> > > +++ b/vars/all/RelEngFrozen.yaml
> > > @@ -1 +1 @@
> > > -RelEngFrozen: True
> > > +RelEngFrozen: False
> > >
> > > Thanks.
> > > ___
> > > infrastructure mailing list -- infrastructure@lists.fedoraproject.org
> > > To unsubscribe send an email to 
> > > infrastructure-le...@lists.fedoraproject.org
> > > Fedora Code of Conduct: 
> > > https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> > > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> > > List Archives: 
> > > https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
> > ___
> > infrastructure mailing list -- infrastructure@lists.fedoraproject.org
> > To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
> > Fedora Code of Conduct: 
> > https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> > List Archives: 
> > https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
> ___
> infrastructure mailing list -- infrastructure@lists.fedoraproject.org
> To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
> Fedora Code of 

Re: FBR: F31 Final is GO, bodhi config changes

[Clement Verna]

On Thu, 24 Oct 2019 at 20:32, Mohan Boddu  wrote:

> On Thu, Oct 24, 2019 at 2:04 PM Clement Verna 
> wrote:
> >
> >
> >
> > On Thu, 24 Oct 2019 at 19:57, Mohan Boddu  wrote:
> >>
> >> Hi,
> >>
> >> Now that F31 is GO, I would like the make the necessary changes to
> >> bodhi configs.
> >>
> >> "vars/all/Frozen.yaml" 1L, 15C written
> >> [mohanboddu@batcave01 ansible][PROD]$ git diff
> >> diff --git a/vars/all/00-FedoraCycleNumber.yaml
> >> b/vars/all/00-FedoraCycleNumber.yaml
> >> index 22476b0..4bd0d46 100644
> >> --- a/vars/all/00-FedoraCycleNumber.yaml
> >> +++ b/vars/all/00-FedoraCycleNumber.yaml
> >> @@ -1 +1 @@
> >> -FedoraCycleNumber: 30
> >> +FedoraCycleNumber: 31
> >> diff --git a/vars/all/FedoraBranched.yaml b/vars/all/FedoraBranched.yaml
> >> index 42ac534..0bbcc1d 100644
> >> --- a/vars/all/FedoraBranched.yaml
> >> +++ b/vars/all/FedoraBranched.yaml
> >> @@ -1 +1 @@
> >> -FedoraBranched: True
> >> +FedoraBranched: False
> >> diff --git a/vars/all/FedoraBranchedBodhi.yaml
> >> b/vars/all/FedoraBranchedBodhi.yaml
> >> index 380f61d..76ba14d 100644
> >> --- a/vars/all/FedoraBranchedBodhi.yaml
> >> +++ b/vars/all/FedoraBranchedBodhi.yaml
> >> @@ -1,2 +1,2 @@
> >>  #options are: prebeta, postbeta, current
> >> -FedoraBranchedBodhi: postbeta
> >> +FedoraBranchedBodhi: current
> >> diff --git a/vars/all/FedoraPreviousPrevious.yaml
> >> b/vars/all/FedoraPreviousPrevious.yaml
> >> index a8e3d3b..a061e04 100644
> >> --- a/vars/all/FedoraPreviousPrevious.yaml
> >> +++ b/vars/all/FedoraPreviousPrevious.yaml
> >> @@ -1 +1 @@
> >> -FedoraPreviousPrevious: False
> >> +FedoraPreviousPrevious: True
> >> diff --git a/vars/all/Frozen.yaml b/vars/all/Frozen.yaml
> >> index 97d3bc3..7578a88 100644
> >> --- a/vars/all/Frozen.yaml
> >> +++ b/vars/all/Frozen.yaml
> >> @@ -1 +1 @@
> >> -Frozen: True
> >> +Frozen: False
> >
> >
> > I think this is the Frozen variable for the infra, and if I am correct
> that should stay set to True. But I am might be wrong :-)
> Even I thought of the same and checked for it and the only place that
> is using it is:
>
> https://infrastructure.fedoraproject.org/cgit/ansible.git/tree/roles/koji_hub/templates/hub.conf.j2#n149
> Which is not related to infra.
>

Cool thanks for checking


> >
> >>
> >> diff --git a/vars/all/RelEngFrozen.yaml b/vars/all/RelEngFrozen.yaml
> >> index bd7553f..72af779 100644
> >> --- a/vars/all/RelEngFrozen.yaml
> >> +++ b/vars/all/RelEngFrozen.yaml
> >> @@ -1 +1 @@
> >> -RelEngFrozen: True
> >> +RelEngFrozen: False
> >
> >
> > One question otherwise looks good, so +1
> >
> >>
> >>
> >> Thanks.
> >> ___
> >> infrastructure mailing list -- infrastructure@lists.fedoraproject.org
> >> To unsubscribe send an email to
> infrastructure-le...@lists.fedoraproject.org
> >> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> >> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> >> List Archives:
> https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
> >
> > ___
> > infrastructure mailing list -- infrastructure@lists.fedoraproject.org
> > To unsubscribe send an email to
> infrastructure-le...@lists.fedoraproject.org
> > Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> > List Archives:
> https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
> ___
> infrastructure mailing list -- infrastructure@lists.fedoraproject.org
> To unsubscribe send an email to
> infrastructure-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
>
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org

Re: FBR: F31 Final is GO, bodhi config changes

[Mohan Boddu]

Also, one more simple FBR,

Disabling branched compose

diff --git a/roles/releng/files/branched b/roles/releng/files/branched
index 966f5c3..1f52f56 100644
--- a/roles/releng/files/branched
+++ b/roles/releng/files/branched
@@ -1,3 +1,3 @@
 # branched compose
 MAILTO=releng-c...@lists.fedoraproject.org
-15 7 * * * root TMPDIR=`mktemp -d /tmp/branched.XX` && cd $TMPDIR
&& git clone https://pagure.io/pungi-fedora.git && cd pungi-fedora &&
git checkout f31 && /usr/local/bin/lock-wrapper branched-compose
"PYTHONMALLOC=debug LANG=en_US.UTF-8 ./nightly.sh" && sudo -u ftpsync
/usr/local/bin/update-fullfiletimelist -l
/pub/fedora-secondary/update-fullfiletimelist.lock -t /pub fedora
fedora-secondary
+#15 7 * * * root TMPDIR=`mktemp -d /tmp/branched.XX` && cd
$TMPDIR && git clone https://pagure.io/pungi-fedora.git && cd
pungi-fedora && git checkout f31 && /usr/local/bin/lock-wrapper
branched-compose "PYTHONMALLOC=debug LANG=en_US.UTF-8 ./nightly.sh" &&
sudo -u ftpsync /usr/local/bin/update-fullfiletimelist -l
/pub/fedora-secondary/update-fullfiletimelist.lock -t /pub fedora
fedora-secondary

I am currently running a branched compose, so that the RC and branched
compose will have the same content.

Once the run is done, I will push all these changes and then either
run full updates push or let the automated pushes take care of it
based on the timing.

I cannot run f31 stable updates push yet, since it might screw up the
silverblue refs if branched is completed after the f31 stable updates
push.

Thanks.

On Thu, Oct 24, 2019 at 2:27 PM Mikolaj Izdebski  wrote:
>
> +1
>
> On Thu, Oct 24, 2019 at 7:51 PM Mohan Boddu  wrote:
> >
> > Hi,
> >
> > Now that F31 is GO, I would like the make the necessary changes to
> > bodhi configs.
> >
> > "vars/all/Frozen.yaml" 1L, 15C written
> > [mohanboddu@batcave01 ansible][PROD]$ git diff
> > diff --git a/vars/all/00-FedoraCycleNumber.yaml
> > b/vars/all/00-FedoraCycleNumber.yaml
> > index 22476b0..4bd0d46 100644
> > --- a/vars/all/00-FedoraCycleNumber.yaml
> > +++ b/vars/all/00-FedoraCycleNumber.yaml
> > @@ -1 +1 @@
> > -FedoraCycleNumber: 30
> > +FedoraCycleNumber: 31
> > diff --git a/vars/all/FedoraBranched.yaml b/vars/all/FedoraBranched.yaml
> > index 42ac534..0bbcc1d 100644
> > --- a/vars/all/FedoraBranched.yaml
> > +++ b/vars/all/FedoraBranched.yaml
> > @@ -1 +1 @@
> > -FedoraBranched: True
> > +FedoraBranched: False
> > diff --git a/vars/all/FedoraBranchedBodhi.yaml
> > b/vars/all/FedoraBranchedBodhi.yaml
> > index 380f61d..76ba14d 100644
> > --- a/vars/all/FedoraBranchedBodhi.yaml
> > +++ b/vars/all/FedoraBranchedBodhi.yaml
> > @@ -1,2 +1,2 @@
> >  #options are: prebeta, postbeta, current
> > -FedoraBranchedBodhi: postbeta
> > +FedoraBranchedBodhi: current
> > diff --git a/vars/all/FedoraPreviousPrevious.yaml
> > b/vars/all/FedoraPreviousPrevious.yaml
> > index a8e3d3b..a061e04 100644
> > --- a/vars/all/FedoraPreviousPrevious.yaml
> > +++ b/vars/all/FedoraPreviousPrevious.yaml
> > @@ -1 +1 @@
> > -FedoraPreviousPrevious: False
> > +FedoraPreviousPrevious: True
> > diff --git a/vars/all/Frozen.yaml b/vars/all/Frozen.yaml
> > index 97d3bc3..7578a88 100644
> > --- a/vars/all/Frozen.yaml
> > +++ b/vars/all/Frozen.yaml
> > @@ -1 +1 @@
> > -Frozen: True
> > +Frozen: False
> > diff --git a/vars/all/RelEngFrozen.yaml b/vars/all/RelEngFrozen.yaml
> > index bd7553f..72af779 100644
> > --- a/vars/all/RelEngFrozen.yaml
> > +++ b/vars/all/RelEngFrozen.yaml
> > @@ -1 +1 @@
> > -RelEngFrozen: True
> > +RelEngFrozen: False
> >
> > Thanks.
> > ___
> > infrastructure mailing list -- infrastructure@lists.fedoraproject.org
> > To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
> > Fedora Code of Conduct: 
> > https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> > List Archives: 
> > https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
> ___
> infrastructure mailing list -- infrastructure@lists.fedoraproject.org
> To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org

Re: The packages app has a short runway

[Neal Gompa]

On Thu, Oct 24, 2019 at 2:13 PM Clement Verna  wrote:
>
>
>
> On Thu, 24 Oct 2019 at 18:07, Randy Barlow  
> wrote:
>>
>> Greetings!
>>
>> The packages app is running on Fedora 30, and its dependencies are not
>> available in Fedora 31+ as I understand it.
>>
>> This means it has about 7 months before we need to do something about
>> it, or shut it off.
>>
>> Do we know if it can run on RHEL 7?
>
>
> The packages app (https://apps.fedoraproject.org/packages/) was originally 
> running on RHEL6, I tried to move it to RHEL 7 but they were some 
> dependencies missing there so we decided to move it to Fedora. I don't 
> remember which dependencies were missing tho. One of the pain point is that 
> the frontend is rendered using moksha/tosca widgets 
> (http://toscawidgets.org/) and this is pretty much a dead upstream project. 
> Removing these dependencies is not going to be trivial.
>

There appears to be work starting on a brand new implementation:
https://github.com/xsuchy/fedora-packages-ng

This version looks like it'll be Python 3 compatible, though it is quite new.

-- 
真実はいつも一つ！/ Always, there's only one truth!
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org

Re: FBR: F31 Final is GO, bodhi config changes

[Mikolaj Izdebski]

+1

On Thu, Oct 24, 2019 at 7:51 PM Mohan Boddu  wrote:
>
> Hi,
>
> Now that F31 is GO, I would like the make the necessary changes to
> bodhi configs.
>
> "vars/all/Frozen.yaml" 1L, 15C written
> [mohanboddu@batcave01 ansible][PROD]$ git diff
> diff --git a/vars/all/00-FedoraCycleNumber.yaml
> b/vars/all/00-FedoraCycleNumber.yaml
> index 22476b0..4bd0d46 100644
> --- a/vars/all/00-FedoraCycleNumber.yaml
> +++ b/vars/all/00-FedoraCycleNumber.yaml
> @@ -1 +1 @@
> -FedoraCycleNumber: 30
> +FedoraCycleNumber: 31
> diff --git a/vars/all/FedoraBranched.yaml b/vars/all/FedoraBranched.yaml
> index 42ac534..0bbcc1d 100644
> --- a/vars/all/FedoraBranched.yaml
> +++ b/vars/all/FedoraBranched.yaml
> @@ -1 +1 @@
> -FedoraBranched: True
> +FedoraBranched: False
> diff --git a/vars/all/FedoraBranchedBodhi.yaml
> b/vars/all/FedoraBranchedBodhi.yaml
> index 380f61d..76ba14d 100644
> --- a/vars/all/FedoraBranchedBodhi.yaml
> +++ b/vars/all/FedoraBranchedBodhi.yaml
> @@ -1,2 +1,2 @@
>  #options are: prebeta, postbeta, current
> -FedoraBranchedBodhi: postbeta
> +FedoraBranchedBodhi: current
> diff --git a/vars/all/FedoraPreviousPrevious.yaml
> b/vars/all/FedoraPreviousPrevious.yaml
> index a8e3d3b..a061e04 100644
> --- a/vars/all/FedoraPreviousPrevious.yaml
> +++ b/vars/all/FedoraPreviousPrevious.yaml
> @@ -1 +1 @@
> -FedoraPreviousPrevious: False
> +FedoraPreviousPrevious: True
> diff --git a/vars/all/Frozen.yaml b/vars/all/Frozen.yaml
> index 97d3bc3..7578a88 100644
> --- a/vars/all/Frozen.yaml
> +++ b/vars/all/Frozen.yaml
> @@ -1 +1 @@
> -Frozen: True
> +Frozen: False
> diff --git a/vars/all/RelEngFrozen.yaml b/vars/all/RelEngFrozen.yaml
> index bd7553f..72af779 100644
> --- a/vars/all/RelEngFrozen.yaml
> +++ b/vars/all/RelEngFrozen.yaml
> @@ -1 +1 @@
> -RelEngFrozen: True
> +RelEngFrozen: False
>
> Thanks.
> ___
> infrastructure mailing list -- infrastructure@lists.fedoraproject.org
> To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org

Re: FBR: F31 Final is GO, bodhi config changes

[Mohan Boddu]

On Thu, Oct 24, 2019 at 2:04 PM Clement Verna  wrote:
>
>
>
> On Thu, 24 Oct 2019 at 19:57, Mohan Boddu  wrote:
>>
>> Hi,
>>
>> Now that F31 is GO, I would like the make the necessary changes to
>> bodhi configs.
>>
>> "vars/all/Frozen.yaml" 1L, 15C written
>> [mohanboddu@batcave01 ansible][PROD]$ git diff
>> diff --git a/vars/all/00-FedoraCycleNumber.yaml
>> b/vars/all/00-FedoraCycleNumber.yaml
>> index 22476b0..4bd0d46 100644
>> --- a/vars/all/00-FedoraCycleNumber.yaml
>> +++ b/vars/all/00-FedoraCycleNumber.yaml
>> @@ -1 +1 @@
>> -FedoraCycleNumber: 30
>> +FedoraCycleNumber: 31
>> diff --git a/vars/all/FedoraBranched.yaml b/vars/all/FedoraBranched.yaml
>> index 42ac534..0bbcc1d 100644
>> --- a/vars/all/FedoraBranched.yaml
>> +++ b/vars/all/FedoraBranched.yaml
>> @@ -1 +1 @@
>> -FedoraBranched: True
>> +FedoraBranched: False
>> diff --git a/vars/all/FedoraBranchedBodhi.yaml
>> b/vars/all/FedoraBranchedBodhi.yaml
>> index 380f61d..76ba14d 100644
>> --- a/vars/all/FedoraBranchedBodhi.yaml
>> +++ b/vars/all/FedoraBranchedBodhi.yaml
>> @@ -1,2 +1,2 @@
>>  #options are: prebeta, postbeta, current
>> -FedoraBranchedBodhi: postbeta
>> +FedoraBranchedBodhi: current
>> diff --git a/vars/all/FedoraPreviousPrevious.yaml
>> b/vars/all/FedoraPreviousPrevious.yaml
>> index a8e3d3b..a061e04 100644
>> --- a/vars/all/FedoraPreviousPrevious.yaml
>> +++ b/vars/all/FedoraPreviousPrevious.yaml
>> @@ -1 +1 @@
>> -FedoraPreviousPrevious: False
>> +FedoraPreviousPrevious: True
>> diff --git a/vars/all/Frozen.yaml b/vars/all/Frozen.yaml
>> index 97d3bc3..7578a88 100644
>> --- a/vars/all/Frozen.yaml
>> +++ b/vars/all/Frozen.yaml
>> @@ -1 +1 @@
>> -Frozen: True
>> +Frozen: False
>
>
> I think this is the Frozen variable for the infra, and if I am correct that 
> should stay set to True. But I am might be wrong :-)
Even I thought of the same and checked for it and the only place that
is using it is:
https://infrastructure.fedoraproject.org/cgit/ansible.git/tree/roles/koji_hub/templates/hub.conf.j2#n149
Which is not related to infra.
>
>>
>> diff --git a/vars/all/RelEngFrozen.yaml b/vars/all/RelEngFrozen.yaml
>> index bd7553f..72af779 100644
>> --- a/vars/all/RelEngFrozen.yaml
>> +++ b/vars/all/RelEngFrozen.yaml
>> @@ -1 +1 @@
>> -RelEngFrozen: True
>> +RelEngFrozen: False
>
>
> One question otherwise looks good, so +1
>
>>
>>
>> Thanks.
>> ___
>> infrastructure mailing list -- infrastructure@lists.fedoraproject.org
>> To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
>> Fedora Code of Conduct: 
>> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>> List Archives: 
>> https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
>
> ___
> infrastructure mailing list -- infrastructure@lists.fedoraproject.org
> To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org

Re: The packages app has a short runway

[Clement Verna]

On Thu, 24 Oct 2019 at 18:07, Randy Barlow 
wrote:

> Greetings!
>
> The packages app is running on Fedora 30, and its dependencies are not
> available in Fedora 31+ as I understand it.
>
> This means it has about 7 months before we need to do something about
> it, or shut it off.
>
> Do we know if it can run on RHEL 7?
>

The packages app (https://apps.fedoraproject.org/packages/) was originally
running on RHEL6, I tried to move it to RHEL 7 but they were some
dependencies missing there so we decided to move it to Fedora. I don't
remember which dependencies were missing tho. One of the pain point is that
the frontend is rendered using moksha/tosca widgets (
http://toscawidgets.org/) and this is pretty much a dead upstream project.
Removing these dependencies is not going to be trivial.


> ___
> infrastructure mailing list -- infrastructure@lists.fedoraproject.org
> To unsubscribe send an email to
> infrastructure-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
>
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org

Re: FBR: F31 Final is GO, bodhi config changes

[Stephen John Smoogen]

+1

On Thu, 24 Oct 2019 at 14:04, Clement Verna  wrote:
>
>
>
> On Thu, 24 Oct 2019 at 19:57, Mohan Boddu  wrote:
>>
>> Hi,
>>
>> Now that F31 is GO, I would like the make the necessary changes to
>> bodhi configs.
>>
>> "vars/all/Frozen.yaml" 1L, 15C written
>> [mohanboddu@batcave01 ansible][PROD]$ git diff
>> diff --git a/vars/all/00-FedoraCycleNumber.yaml
>> b/vars/all/00-FedoraCycleNumber.yaml
>> index 22476b0..4bd0d46 100644
>> --- a/vars/all/00-FedoraCycleNumber.yaml
>> +++ b/vars/all/00-FedoraCycleNumber.yaml
>> @@ -1 +1 @@
>> -FedoraCycleNumber: 30
>> +FedoraCycleNumber: 31
>> diff --git a/vars/all/FedoraBranched.yaml b/vars/all/FedoraBranched.yaml
>> index 42ac534..0bbcc1d 100644
>> --- a/vars/all/FedoraBranched.yaml
>> +++ b/vars/all/FedoraBranched.yaml
>> @@ -1 +1 @@
>> -FedoraBranched: True
>> +FedoraBranched: False
>> diff --git a/vars/all/FedoraBranchedBodhi.yaml
>> b/vars/all/FedoraBranchedBodhi.yaml
>> index 380f61d..76ba14d 100644
>> --- a/vars/all/FedoraBranchedBodhi.yaml
>> +++ b/vars/all/FedoraBranchedBodhi.yaml
>> @@ -1,2 +1,2 @@
>>  #options are: prebeta, postbeta, current
>> -FedoraBranchedBodhi: postbeta
>> +FedoraBranchedBodhi: current
>> diff --git a/vars/all/FedoraPreviousPrevious.yaml
>> b/vars/all/FedoraPreviousPrevious.yaml
>> index a8e3d3b..a061e04 100644
>> --- a/vars/all/FedoraPreviousPrevious.yaml
>> +++ b/vars/all/FedoraPreviousPrevious.yaml
>> @@ -1 +1 @@
>> -FedoraPreviousPrevious: False
>> +FedoraPreviousPrevious: True
>> diff --git a/vars/all/Frozen.yaml b/vars/all/Frozen.yaml
>> index 97d3bc3..7578a88 100644
>> --- a/vars/all/Frozen.yaml
>> +++ b/vars/all/Frozen.yaml
>> @@ -1 +1 @@
>> -Frozen: True
>> +Frozen: False
>
>
> I think this is the Frozen variable for the infra, and if I am correct that 
> should stay set to True. But I am might be wrong :-)
>
>>
>> diff --git a/vars/all/RelEngFrozen.yaml b/vars/all/RelEngFrozen.yaml
>> index bd7553f..72af779 100644
>> --- a/vars/all/RelEngFrozen.yaml
>> +++ b/vars/all/RelEngFrozen.yaml
>> @@ -1 +1 @@
>> -RelEngFrozen: True
>> +RelEngFrozen: False
>
>
> One question otherwise looks good, so +1
>
>>
>>
>> Thanks.
>> ___
>> infrastructure mailing list -- infrastructure@lists.fedoraproject.org
>> To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
>> Fedora Code of Conduct: 
>> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>> List Archives: 
>> https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
>
> ___
> infrastructure mailing list -- infrastructure@lists.fedoraproject.org
> To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org



-- 
Stephen J Smoogen.
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org

Re: FBR: F31 Final is GO, bodhi config changes

[Clement Verna]

On Thu, 24 Oct 2019 at 19:57, Mohan Boddu  wrote:

> Hi,
>
> Now that F31 is GO, I would like the make the necessary changes to
> bodhi configs.
>
> "vars/all/Frozen.yaml" 1L, 15C written
> [mohanboddu@batcave01 ansible][PROD]$ git diff
> diff --git a/vars/all/00-FedoraCycleNumber.yaml
> b/vars/all/00-FedoraCycleNumber.yaml
> index 22476b0..4bd0d46 100644
> --- a/vars/all/00-FedoraCycleNumber.yaml
> +++ b/vars/all/00-FedoraCycleNumber.yaml
> @@ -1 +1 @@
> -FedoraCycleNumber: 30
> +FedoraCycleNumber: 31
> diff --git a/vars/all/FedoraBranched.yaml b/vars/all/FedoraBranched.yaml
> index 42ac534..0bbcc1d 100644
> --- a/vars/all/FedoraBranched.yaml
> +++ b/vars/all/FedoraBranched.yaml
> @@ -1 +1 @@
> -FedoraBranched: True
> +FedoraBranched: False
> diff --git a/vars/all/FedoraBranchedBodhi.yaml
> b/vars/all/FedoraBranchedBodhi.yaml
> index 380f61d..76ba14d 100644
> --- a/vars/all/FedoraBranchedBodhi.yaml
> +++ b/vars/all/FedoraBranchedBodhi.yaml
> @@ -1,2 +1,2 @@
>  #options are: prebeta, postbeta, current
> -FedoraBranchedBodhi: postbeta
> +FedoraBranchedBodhi: current
> diff --git a/vars/all/FedoraPreviousPrevious.yaml
> b/vars/all/FedoraPreviousPrevious.yaml
> index a8e3d3b..a061e04 100644
> --- a/vars/all/FedoraPreviousPrevious.yaml
> +++ b/vars/all/FedoraPreviousPrevious.yaml
> @@ -1 +1 @@
> -FedoraPreviousPrevious: False
> +FedoraPreviousPrevious: True
> diff --git a/vars/all/Frozen.yaml b/vars/all/Frozen.yaml
> index 97d3bc3..7578a88 100644
> --- a/vars/all/Frozen.yaml
> +++ b/vars/all/Frozen.yaml
> @@ -1 +1 @@
> -Frozen: True
> +Frozen: False
>

I think this is the Frozen variable for the infra, and if I am correct that
should stay set to True. But I am might be wrong :-)


> diff --git a/vars/all/RelEngFrozen.yaml b/vars/all/RelEngFrozen.yaml
> index bd7553f..72af779 100644
> --- a/vars/all/RelEngFrozen.yaml
> +++ b/vars/all/RelEngFrozen.yaml
> @@ -1 +1 @@
> -RelEngFrozen: True
> +RelEngFrozen: False
>

One question otherwise looks good, so +1


>
> Thanks.
> ___
> infrastructure mailing list -- infrastructure@lists.fedoraproject.org
> To unsubscribe send an email to
> infrastructure-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
>
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org

Working on adding ansible-report to our ansible repo

[Clement Verna]

Hi all,

Tomorrow I am planning to work on the following ticket (
https://pagure.io/fedora-infrastructure/issue/8157 ). If there are people
interested to work on this with me or just to tag along I will be starting
to work on that in #fedora-admin at 12:00 UTC.

Thanks
Clément
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org

The packages app has a short runway

[Randy Barlow]

Greetings!

The packages app is running on Fedora 30, and its dependencies are not
available in Fedora 31+ as I understand it.

This means it has about 7 months before we need to do something about
it, or shut it off.

Do we know if it can run on RHEL 7?


signature.asc
Description: This is a digitally signed message part
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org

FBR: Update koji-sidetag-plugin on Koji hub

[Mikolaj Izdebski]

In order to fix issue 8322 [1] python2-koji-sidetag-plugin-hub needs
to be updated. This would be done with the following commands:

$ koji move epel7-infra-stg epel7-infra koji-sidetag-plugin-0.1-2.el7.infra

[root@batcave01]# ansible koji -m package -a
'name=python2-koji-sidetag-plugin-hub state=latest update_cache=yes
update_only=yes'

[root@batcave01]# ansible koji -m service -a 'name=httpd state=reloaded'

[1] https://pagure.io/fedora-infrastructure/issue/8322
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org

Re: My self introduction

[Benson Muite]

Welcome!

On 10/24/19 2:41 PM, Álvaro Castillo wrote:

Good morning,

My name is Alvaro Castillo, I'm 25 years old. I'm from Canary Islands, 
but currently, I'm

m living in Mallorca (Spain).

I have a blog https://echemosunbitstazo.es 
 where I write howtos, articles and 
more about operative systems world and web development like PHP, 
Python, JS... or system shell scripts likes as Bash or Python.


I've worked with Ansible, IDM (Red Hat Identity Management), KVM, 
VMware Virtual Center, Nagios, Red Hat Enterprise Linux, Commvault and 
much more.


Actually, I work in RIU Hotels & Resorts as system administrator.

I hope collaborate with this fantastic community. My username is 
sincorchetes.


Cheers!


___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org

My self introduction

[Álvaro Castillo]

Good morning,

My name is Alvaro Castillo, I'm 25 years old. I'm from Canary Islands, but
currently, I'm
m living in Mallorca (Spain).

I have a blog https://echemosunbitstazo.es where I write howtos, articles
and more about operative systems world and web development like PHP,
Python, JS... or system shell scripts likes as Bash or Python.

I've worked with Ansible, IDM (Red Hat Identity Management), KVM, VMware
Virtual Center, Nagios, Red Hat Enterprise Linux, Commvault and much more.

Actually, I work in RIU Hotels & Resorts as system administrator.

I hope collaborate with this fantastic community. My username is
sincorchetes.

Cheers!
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org