[releng] Issue #6799: [koji] Add configuration for module build service
content generator
by Stanislav Ochotnicky
sochotni reported a new issue against the project: `releng` that you are following:
``
We will need changes/additions to koji configuration to enable imports of Modules through content generator.
Expect future updates once since this is a bit off the top of my head.
1. Add content generator "module-build-service"
2. Add btype "module"
3. Configure whatever user is used by modulebuild service to have permission for the content generator APIs
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/6799
6 years, 8 months
[releng] Issue #6671 `Figure out how to block real builds in koji coming
from forks in pagure`
by Pierre-YvesChibon
pingou reported a new issue against the project: `releng` that you are following:
``
As far as I understood from Patrick the current mechanism for koji to allow/deny building from a source is fairly simple.
With pagure on the top of dist-git, we may need something a little more flexible as we would like to support the following use-cases:
* Builds from main repo proceed as now
* Builds from forks can only be either (or both) of:
* scratch-build
* in a certain tag used for the CI integration (redefining the dist tag to allow building the same package, once for testing and once for real)
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/6671
6 years, 8 months
[releng] Issue #6896: Populate product-version endpoint in PDC
by Ralph Bean
ralph reported a new issue against the project: `releng` that you are following:
``
I'll do this. Filing a ticket to track it.
In PDC, we have the product and release endpoints populated automatically by pdc-updater.
The product-versions endpoint is very similar to the release endpoint, but not quite identical. It is needed by the [greenwave](https://pagure.io/greenwave) prototype.
I'll populate historical information for that endpoint and also patch pdc-updater to keep it up to date in the future.
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/6896
6 years, 8 months
Koji config adjustment
by Pierre-Yves Chibon
Good Morning Everyone,
Trying to finish https://pagure.io/releng/issue/6671 I tried to adjust the koji
configuration as needed.
Attached is the corresponding patch which I would prefer someone with more
knowledge of koji than me to review and/or apply (and even deploy if possible).
Thanks for your help,
Pierre
6 years, 8 months
[releng] Issue #6922: Chanes/aarch64SBCImages
by Peter Robinson
pbrobinson reported a new issue against the project: `releng` that you are following:
``
[edit] aarch64 SBC (Single Board Computer) Disk Images
https://fedoraproject.org/wiki/Changes/aarch64SBCImages
From the change: Release engineering will need to enable building of aarch64 disk images. This is already complete, it was originally done as part of Fedora 26 but the last bits required of the feature didn't quite land in time for F-26 GA. There might well be small tweaks required of kickstarts or pungi configs but those will be done by the feature owners and sent to rel-eng as a pull request.
I don't envision anything particular more than what was put in place for F-26 other than potentially tweaks to the kickstarts.
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/6922
6 years, 8 months
F27 Mass Rebuild
by langdon
As we run up to the F26 release, I know we have a number of things still
in flight for the modular release of Boltron. As it is non-blocking to
the release, we won't be holding the release back to make sure Boltron
goes out, which is fine.
However, I notice that the schedule for the F27 Mass Rebuild is July 12
(the day after tomorrow). I am concerned that if Boltron (or anything
else slips), everyone will have to prioritize F27 Mass Rebuild vs F26
final bits & pieces. Would it make sense to consider pushing the Mass
Rebuild out a week to July 19th? Would there be significant downstream
(in schedule terms) effect?
Langdon
6 years, 8 months
[releng] Issue #6923: spam to kde-owner@lists.fedoraproject.org is
apparently DOS'ing my gmail account
by Rex Dieter
rdieter reported a new issue against the project: `releng` that you are following:
``
A few days ago, I started receiving a large amount of oriental (chinese?) spam mail sent to kde-owner(a)lists.fedoraproject.org (apparently), which was getting sent to rdieter(a)fedoraproject.org and eventually forwarded to @gmail.com.
my gmail account is now being throttled (as far as I can tell) and I'm not receiving much/any legitimate mail :(
Yesterday, I tried adjusting
https://lists.fedoraproject.org/admin/lists/kde.lists.fedoraproject.org/s...
to set "Autorespond to list owner" to use "Respond and discard message ", but it's not working as I expect. The same spam is still showing up in my gmail spam folder, as recently as 90 minutes ago.
Is it possible this is still backlogged somewhere in fedora infra? Any advice or help you can provide to alleviate this problem for me would be appreciated.
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/6923
6 years, 8 months