ausil added a new comment to an issue you are following:
``
I am going to close this as fixed.
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/6027
ausil added a new comment to an issue you are following:
``
lets get this fixed before Alpha. I think we should do this on one of the bodhi backend boxes. or we should integrate the functionality into the nightly composes. it would mean daily updates however
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/6040
The status of the issue: `handle packages that are retired only in Branched but not Rawhide` of project: `releng` has been updated to: Closed as Fixed by ausil.
https://pagure.io/releng/issue/6047
The status of the issue: `extend srpm-excluded-arch.py so it can read srpms from multiple dirs` of project: `releng` has been updated to: Closed as Fixed by ausil.
https://pagure.io/releng/issue/6064
ausil added a new comment to an issue you are following:
``
@sharkcz is anything needed here still? if so please send in a PR. I am assuming its been fixed.
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/6064
The issue: `Cleanup pending updates from Bodhi for retired packages` of project: `releng` has been assigned to `rbarlow` by ausil.
https://pagure.io/releng/issue/6067
ralph reported a new issue against the project: `releng` that you are following:
``
This is related to #6658 but is different.
Through discussions with @puiterwijk in and audit of the MBS code, we are trying to reduce the permissions required by the module-build-service, so that it poses less of a risk.
In order to do that (for [mbs#333](https://pagure.io/fm-orchestrator/issue/333)) we need a new tag created that has the full package list for Fedora, but which should not inherit from an existing Fedora tag.
Let's call the new tag `module-package-list` (which describes precisely what it is for).
# Why we need a tag with the full package list
Current, MBS runs with admin permissions. When it tags builds into tags that it has created, it does so with `force=True` which automatically adds the package to the package list of the tag first, before tagging the build.
We want to remove `force=True` because it is too heavy handed.
We could dynamically add packages to the package list of the new module tag every time a new build comes along, but that requires elevated permissions.
Instead, if we have a master tag with a full package list of every package in Fedora, and if our new modules tags inherit from that tag, then we don't have to worry about the package list or have any special rights to manipulate it (good).
# Why the new tag should not inherit from an existing tag.
*If* we made this new tag inherit from the rawhide tag, then it would automatically get the nice package list that we need.
However, we need to ensure that the new tag does not accidentally provide any `BuildRequires` which are not explicitly specified by the module being built. If a `BuildRequires` is absent, we want the build to fail to ensure modules are really isolated from one another.
Therefore, we need this new tag to *not* inherit from any other tags.
Once created, we will need to patch [this script](https://infrastructure.fedoraproject.org/cgit/ansible.git/tree/roleā¦ to automatically populate the package list of this new tag, while not contributing any builds.
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/6663
ausil merged a pull-request against the project: `pungi-fedora` that you are following.
Merged pull-request:
``
Branching f26 from rawhide
``
https://pagure.io/pungi-fedora/pull-request/149
The issue: `f26: New deliverables for Python Clasroom Lab` of project: `releng` has been assigned to `mohanboddu` by mohanboddu.
https://pagure.io/releng/issue/6665
walters added a new comment to an issue you are following:
``
A while ago I was advocating for this but I no longer do so. Instead I suggest doing "pinned TLS" to a centralized metadata server, and use mirrors for *content*. See also https://fedorahosted.org/fedora-infrastructure/ticket/5372
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/133