[releng] Issue #7924: Whitelist "-devel" modules in
fxx-modular-updates-candidate tags
by Matt Prahl
mprahl reported a new issue against the project: `releng` that you are following:
``
* Describe the issue
The Modularity Working Group has requested that MBS provide "-devel" modules which are modules that contain all the filtered out RPMs from that module that would be shipped.
I can't find a ticket requesting this, but it was implemented in this PR:
https://pagure.io/fm-orchestrator/pull-request/1062
MBS in stage (not deployed in production) currently fails because the Koji content generator build for the "-devel" module (e.g. "testmodule-devel") is not whitelisted in the `fxx-modular-updates-candidate` tags. Could you please take the current list of modules we whitelist and also whitelist their "-devel" counterparts?
I'm tagging @sgallagh @psabata @jkaluza to provide context here if needed.
* When do you need this? (YYYY/MM/DD)
By November 30th, but earlier would be appreciated.
* When is this no longer needed or useful? (YYYY/MM/DD)
N/A
* If we cannot complete your request, what is the impact?
We cannot provide the "-devel" modules the the Modularity Working Group requested and we would need to add code in MBS to make this configurable.
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7924
5 years, 6 months
[releng] Issue #7113: proposal to run bodhi updates pungi composes with
`--no-label`
by Dusty Mabe
dustymabe reported a new issue against the project: `releng` that you are following:
``
We have just started running bodhi updates via pungi (woo!!). One of the reasons the Atomic team has been helping drive this initiative is so that we can get better versioning of our ostrees output by fedora (via pungi).
When we started doing the runs we added a label to them of the form: `Update-20171025.1312`. Which translates into an ostree version of `27_Update.20171025.1312`. The atomic working group had previously got together and [decided](https://pagure.io/atomic-wg/issue/229) that a versioning scheme like `27.2017025.0` would be what we went with for better versioning for ostrees. This scheme was discussed with releng (including dennis) and also added as an RFE to pungi, which was implemented by @lsedlar in [PR](https://pagure.io/pungi/pull-request/592).
With the updates run we can get the desired version if we provide `--no-label` to pungi instead of actually giving it a label. This warrants the question: "what is the value of the label for an updates run?". Do we need it? What is it used for?
If we don't need it then I'd love to just use `--no-label`. If we do need it then we'll have to implement another smart versioning macro for ostrees in pungi.
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7113
5 years, 6 months
[releng] Issue #7277: Remove development/26 and development/27
by Adrian Reber
adrian reported a new issue against the project: `releng` that you are following:
``
I just changed mirrormanager to point to releases/27 also for the category "Fedora Secondary Arches". The following directories could now be deleted on the master mirror:
* fedora/linux/development/27/
* fedora-secondary/development/26/
* fedora-secondary/development/27/
The last one (fedora-secondary/development/27/) needs probably another hour before it can be deleted. But once all mirrorlist servers have the latest information the directories above are no longer necessary from mirrormanager's point of view.
Also see email thread on mirror-admin: https://lists.fedoraproject.org/archives/list/mirror-admin@lists.fedorapr...
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7277
5 years, 6 months
[releng] Issue #7266: Cloud and Docker nightly composes are not
garbage-collected
by Adam Williamson
adamwill reported a new issue against the project: `releng` that you are following:
``
There appears to be no garbage collection in place for the Cloud and Docker post-release nightly composes. AFAICT, every single one of these that has ever been built still exists in https://kojipkgs.fedoraproject.org/compose .
Other nightly composes - the Rawhide and Branched nightlies, and the two-week Atomic nightlies - *are* garbage collected. Two-week Atomic nightly composes still exist back to October 2017, but there certainly were older ones that are now gone. Rawhide and Branched seem to be cleaned about every two weeks.
@mohanboddu
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7266
5 years, 6 months
[releng] Issue #7249: Changes/glibc 2.27, gcc 8.0, binutils 2.30
by Carlos O'Donell
codonell reported a new issue against the project: `releng` that you are following:
``
All Fedora releases must be released using a released and supported version of the core toolchain involving glibc, gcc, and binutils.
The Fedora toolchain team is responsible for ensuring that Fedora Rawhide stabilizes static linking, code generation, and library ABI, before a Fedora release, or that after the branch that the Fedora release is rebased (a very small rebase) to the final released version. This is a requirement for Fedora to inherit the ABI and API guarantees provided by upstream. If a mass rebuild is required by binutils, gcc, glibc or other components, the Fedora toolcahin team will ensure coordination with release engineering such that a mass rebuild uses the released version of all components and fix any last minute ABI or code-generation changes.
As of 2018-01-08 the Fedora toolchain team is requesting a mass rebuild for the Fedora 28 release.
Reasons given:
* Enable Intel CET for current and all future revisions of Fedora (compile with CET turned on).
* Test coverage of flags injection for Annobin, getting as much of the distribution built with annotated binaries for security hardening checking.
Change page for review: https://fedoraproject.org/wiki/Changes/Annobin
Owner: Nick Clifton <nickc(a)redhat.com>
Change page for review: https://fedoraproject.org/wiki/Changes/GLIBC227
Owner: Carlos O'Donell <carlos(a)redhat.com>
Change page for review: https://fedoraproject.org/wiki/Changes/GCC8
Owner: Jakub Jelínek <jakub(a)redhat.com>
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7249
5 years, 6 months