Re: Pinging spin or labs maintainers in failed composes tickets
On 11. 05. 20 20:03, Miro Hrončok wrote: On 11. 05. 20 19:53, Mohan Boddu wrote: Sorry for the late reply, compose-tracker uses the toml file https://pagure.io/releng/compose-tracker/blob/master/f/compose_tracker.py#_151 And the PR is merged and it should work. Thanks for confirmation. It worked \o/ https://pagure.io/releng/failed-composes/issue/1425 -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Re: Pinging spin or labs maintainers in failed composes tickets
On 11. 05. 20 19:53, Mohan Boddu wrote: Sorry for the late reply, compose-tracker uses the toml file https://pagure.io/releng/compose-tracker/blob/master/f/compose_tracker.py#_151 And the PR is merged and it should work. Thanks for confirmation. -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Re: Pinging spin or labs maintainers in failed composes tickets
Sorry for the late reply, compose-tracker uses the toml file https://pagure.io/releng/compose-tracker/blob/master/f/compose_tracker.py#_151 And the PR is merged and it should work. On Mon, May 11, 2020 at 1:19 PM Miro Hrončok wrote: > > On 11. 05. 20 18:23, Ankur Sinha wrote: > > On Mon, May 11, 2020 17:34:57 +0200, Miro Hrončok wrote: > >> On 11. 05. 20 16:48, Ankur Sinha wrote: > >> Thanks. > >> > >> https://koji.fedoraproject.org/koji/packageinfo?packageID=23843 says > >> "Fedora-Python-Classroom-Live" > >> > >> kickstarts have: > >> > >> fedora-arm-python-classroom.ks > >> fedora-live-python-classroom.ks > >> fedora-python-classroom-common.ks > >> fedora-python-classroom-gnome-common.ks > >> fedora-python-classroom-vagrant.ks > >> > >> So this does not really help me :( > > > > The complete name is a "pretty name", defined here: > > https://pagure.io/pungi-fedora/blob/master/f/fedora.conf#_623 > > > > The main file that is used for the image is > > `fedora-live-python-classroom.ks`. It'll include the other ones: > > https://pagure.io/fedora-kickstarts/blob/master/f/fedora-live-python-classroom.ks > > > > Perhaps best to open a PR using "python-classroom.x86_64" and let releng > > correct it if needed when they review it? > > https://pagure.io/fedora-kickstarts/pull-request/641 > > > (I looked around, but couldn't find the script that uses the toml file. > > That would've told us exactly what needs to be used) > > Thanks for looking. > > -- > Miro Hrončok > -- > Phone: +420777974800 > IRC: mhroncok > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Re: Pinging spin or labs maintainers in failed composes tickets
On 11. 05. 20 18:23, Ankur Sinha wrote: On Mon, May 11, 2020 17:34:57 +0200, Miro Hrončok wrote: On 11. 05. 20 16:48, Ankur Sinha wrote: Thanks. https://koji.fedoraproject.org/koji/packageinfo?packageID=23843 says "Fedora-Python-Classroom-Live" kickstarts have: fedora-arm-python-classroom.ks fedora-live-python-classroom.ks fedora-python-classroom-common.ks fedora-python-classroom-gnome-common.ks fedora-python-classroom-vagrant.ks So this does not really help me :( The complete name is a "pretty name", defined here: https://pagure.io/pungi-fedora/blob/master/f/fedora.conf#_623 The main file that is used for the image is `fedora-live-python-classroom.ks`. It'll include the other ones: https://pagure.io/fedora-kickstarts/blob/master/f/fedora-live-python-classroom.ks Perhaps best to open a PR using "python-classroom.x86_64" and let releng correct it if needed when they review it? https://pagure.io/fedora-kickstarts/pull-request/641 (I looked around, but couldn't find the script that uses the toml file. That would've told us exactly what needs to be used) Thanks for looking. -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Re: Pinging spin or labs maintainers in failed composes tickets
On Mon, May 11, 2020 17:34:57 +0200, Miro Hrončok wrote: > On 11. 05. 20 16:48, Ankur Sinha wrote: > Thanks. > > https://koji.fedoraproject.org/koji/packageinfo?packageID=23843 says > "Fedora-Python-Classroom-Live" > > kickstarts have: > > fedora-arm-python-classroom.ks > fedora-live-python-classroom.ks > fedora-python-classroom-common.ks > fedora-python-classroom-gnome-common.ks > fedora-python-classroom-vagrant.ks > > So this does not really help me :( The complete name is a "pretty name", defined here: https://pagure.io/pungi-fedora/blob/master/f/fedora.conf#_623 The main file that is used for the image is `fedora-live-python-classroom.ks`. It'll include the other ones: https://pagure.io/fedora-kickstarts/blob/master/f/fedora-live-python-classroom.ks Perhaps best to open a PR using "python-classroom.x86_64" and let releng correct it if needed when they review it? (I looked around, but couldn't find the script that uses the toml file. That would've told us exactly what needs to be used) -- Thanks, Regards, Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London signature.asc Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Re: Pinging spin or labs maintainers in failed composes tickets
On 11. 05. 20 16:48, Ankur Sinha wrote: Hi Miro, On Mon, May 11, 2020 10:29:32 +0200, Miro Hrončok wrote: Hello again. Please, what is the TOM section for the Python Classroom Lab? I can't see one here at the moment: https://pagure.io/fedora-kickstarts/blob/master/f/maintainers.toml So, I think you'll have to add a new one. I'd added one for the CompNeuro lab image recently: https://pagure.io/fedora-kickstarts/c/547c84c8481651582cfa501ca2a2bf53a3fe4d64?branch=master I *think* the section name uses the name of the kickstart file. Thanks. https://koji.fedoraproject.org/koji/packageinfo?packageID=23843 says "Fedora-Python-Classroom-Live" kickstarts have: fedora-arm-python-classroom.ks fedora-live-python-classroom.ks fedora-python-classroom-common.ks fedora-python-classroom-gnome-common.ks fedora-python-classroom-vagrant.ks So this does not really help me :( -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Re: Pinging spin or labs maintainers in failed composes tickets
Hi Miro, On Mon, May 11, 2020 10:29:32 +0200, Miro Hrončok wrote: > Hello again. Please, what is the TOM section for the Python Classroom Lab? I can't see one here at the moment: https://pagure.io/fedora-kickstarts/blob/master/f/maintainers.toml So, I think you'll have to add a new one. I'd added one for the CompNeuro lab image recently: https://pagure.io/fedora-kickstarts/c/547c84c8481651582cfa501ca2a2bf53a3fe4d64?branch=master I *think* the section name uses the name of the kickstart file. -- Thanks, Regards, Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London signature.asc Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Re: Pinging spin or labs maintainers in failed composes tickets
On 25. 03. 20 23:39, Miro Hrončok wrote: On 25. 03. 20 21:51, Mohan Boddu wrote: Hi all, As discussed in the spins list [1], we are adding the ability to ping maintainers of spins or labs in compose failure tickets [2]. I made a list of maintainers [3] from the existing kickstart files, please create PR's to fedora-kickstarts repo [4] if any changes are needed to the list. We are hoping that it will be very helpful to all the spins, labs and any other variant maintainers to get notified if they image build failed and provides an easy way to find and debug the issue. This sounds great. How would I add myself for the Python Classroom Lab? E.g. what should I call the TOML section for that? Hello again. Please, what is the TOM section for the Python Classroom Lab? -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Re: Pinging spin or labs maintainers in failed composes tickets
On 25. 03. 20 21:51, Mohan Boddu wrote: Hi all, As discussed in the spins list [1], we are adding the ability to ping maintainers of spins or labs in compose failure tickets [2]. I made a list of maintainers [3] from the existing kickstart files, please create PR's to fedora-kickstarts repo [4] if any changes are needed to the list. We are hoping that it will be very helpful to all the spins, labs and any other variant maintainers to get notified if they image build failed and provides an easy way to find and debug the issue. This sounds great. How would I add myself for the Python Classroom Lab? E.g. what should I call the TOML section for that? -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Pinging spin or labs maintainers in failed composes tickets
Hi all, As discussed in the spins list [1], we are adding the ability to ping maintainers of spins or labs in compose failure tickets [2]. I made a list of maintainers [3] from the existing kickstart files, please create PR's to fedora-kickstarts repo [4] if any changes are needed to the list. We are hoping that it will be very helpful to all the spins, labs and any other variant maintainers to get notified if they image build failed and provides an easy way to find and debug the issue. Thanks, Mohan Boddu Fedora Release Engineering. [1] https://lists.fedoraproject.org/archives/list/sp...@lists.fedoraproject.org/thread/K5VFSTEBBQUGNBFPBDTEQJ6HWESTLMWG/ [2] https://pagure.io/releng/failed-composes/issues [3] https://pagure.io/fedora-kickstarts/blob/master/f/maintainers.toml [4] https://pagure.io/fedora-kickstarts/ ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
