kevin added a new comment to an issue you are following:
``
Sure, makes sense.
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/6805
The status of the issue: `split fedora_koji and fedora_ftp storage volumes` of project: `releng` has been updated to: Closed as Duplicate by kevin.
https://pagure.io/releng/issue/6805
dustymabe added a new comment to an issue you are following:
``
I'd say close so there is one less place for you to come back to.. People who want to follow can do so over there.
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/6805
churchyard opened a new pull-request against the project: `releng` that you are following:
``
Update the tracker bug for F31FTBFS
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/pull-request/8574
ignatenkobrain reported a new issue against the project: `releng` that you are following:
``
It seems that 80+ modules are in "build" state right now in MBS. Is anybody looking into this?
I am missing all of my modules for F32…
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/8719
mizdebsk reported a new issue against the project: `releng` that you are following:
``
Please consider turning on [nosync setting in mock](https://github.com/rpm-software-management/mock/wiki/Feature-nosync) on Koji builders. This was brought up in [Removal of GCC from the buildroot](https://lists.fedoraproject.org/archives/list/devel@lists.fedora… thread on devel mailing list in July.
Nosync aims to improve performance of dnf phase in mock. It achieves this by disabling fsync calls. Fsync calls are not ignored during rpmbuild phase. For more information see upstream documentation linked above.
I temporarily enabled nosync in staging Koji to estimate its effect on build performance. Results will be posted below in separate comments.
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7909
ngompa reported a new issue against the project: `releng` that you are following:
``
Recently, we stopped producing [the Cloud repo tree](https://pagure.io/pungi-fedora/pull-request/577) as part of composes to speed things up and reduce the number of useless deliverables.
I suggest we also stop producing the Workstation repo tree for composes, as we don't use it or need it. Today, for the Workstation Edition, we produce two main artifacts: the live ISO and the branded netinstall ISO.
As far as I'm aware, the branded net install ISO differs from the main Fedora netinstall ISO only in branding and defaults through the anaconda productimg embedded within. It uses the `Everything` repo tree like the regular netinstall ISO, and is functionally similar to the regular netinstall ISO.
Since the Workstation netinstall doesn't need it, and we don't produce a Workstation install DVD ISO, I do not see a reason to keep producing the Workstation repo tree. Not producing the tree would help reduce the compose time significantly, too.
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7403