June 2017 - rel-eng - Fedora Mailing-Lists

[releng] Issue #6868: Extend tag configuration for f26-modularity

by Petr Šabata

psabata reported a new issue against the project: `releng` that you are following: `` To make the `f26-modularity`-based repository usable for `buildinstall` pungi phase, we need two additional changes to the tag configuration: * the `build` group needs to be defined; it should include the usual set -- `koji add-group f26-modularity build && koji add-group-pkg f26-modularity build bash bzip2 coreutils cpio diffutils fedora-release findutils gawk gcc gcc-c++ grep gzip info make patch redhat-rpm-config rpm-build sed shadow-utils tar unzip util-linux which xz` * dnf should be used to install this group -- `koji edit-tag -x mock.package_manager=dnf f26-modularity` This is a followup for https://pagure.io/releng/issue/6696. I've tested these changes in staging and it works as expected. Thanks! `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/6868

6 years, 1 month

4
10
0 / 0

[releng] PR #6861: Remove unused functions.

by Ralph Bean

ralph opened a new pull-request against the project: `releng` that you are following: `` Remove unused functions. `` To reply, visit the link below or just reply to this email https://pagure.io/releng/pull-request/6861

6 years, 1 month

2
2
0 / 0

[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, 1 month

4
29
0 / 0

[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, 2 months

6
17
0 / 0

[releng] Issue #6863: Separate Subpackage and Source Debuginfo releng review

by Mark Wielaard

mjw reported a new issue against the project: `releng` that you are following: `` https://fedoraproject.org/wiki/Changes/SubpackageAndSourceDebuginfo is a system wide change proposal for f27. All code is in rawhide already, but the feature isn't enable by default. Packages wishing to have a separate debugsource package and sub-debuginfo packages need to explicitly define one (or both) of the following in their spec file: %global _debugsource_packages 1 %global _debuginfo_subpackages 1 This might need some release engineering magic to make sure the created <package>-debugsource and <subpackage>-debuginfo packages end up in the [fedora-debuginfo] repository. There is some more background information on the various debuginfo improvements in the current rawhide rpmbuild and which macros packages can use in the spec files in this fedora devel mailinglist message: https://lists.fedorahosted.org/archives/list/devel@lists.fedoraproject.or... Depending on feedback on that we could enable one or both settings by default for the mass rebuild. Although that can also be done afterwards. Or if any issues are found we could keep it off by default and let packages explicitly opt-in. `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/6863

6 years, 2 months

6
14
0 / 0

[releng] Issue #6853: Go 1.9 mass rebuild

by Jakub Čajka

jcajka reported a new issue against the project: `releng` that you are following: `` Rebuild will be done with pre-release version of Go("GC")1.9. I will perform prior local scratch rebuilds to catch and fix possible issue early on. All other details and list of affected packages is included in the change proposal https://fedoraproject.org/wiki/Changes/golang1.9. `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/6853

6 years, 2 months

2
2
0 / 0

Fedora Atomic Host Two Week Release Announcement

by noreply＠fedoraproject.org

A new Fedora Atomic Host update is available via an OSTree commit: Commit: 3fd888c674c6d69907eabc665103341e01ebe3a04c3876af6cac673b0bf43662 Version: 25.122 Existing systems can be upgraded in place via e.g. `atomic host upgrade` or `atomic host deploy`. Corresponding image media for new installations can be downloaded from: https://getfedora.org/en/atomic/download/ Respective signed CHECKSUM files can be found here: https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-25-2017... https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-25-2017... For direct download, the "latest" targets are always available here: https://getfedora.org/atomic_iso_latest https://getfedora.org/atomic_qcow2_latest https://getfedora.org/atomic_raw_latest https://getfedora.org/atomic_vagrant_libvirt_latest https://getfedora.org/atomic_vagrant_virtualbox_latest Filename fetching URLs are available here: https://getfedora.org/atomic_iso_latest_filename https://getfedora.org/atomic_qcow2_latest_filename https://getfedora.org/atomic_raw_latest_filename https://getfedora.org/atomic_vagrant_libvirt_latest_filename https://getfedora.org/atomic_vagrant_virtualbox_latest_filename For more information about the latest targets, please reference the Fedora Cloud Wiki space. https://fedoraproject.org/wiki/Cloud#Quick_Links Do note that it can take some of the mirrors up to 12 hours to "check-in" at their own discretion. Thank you, Fedora Release Engineering

6 years, 2 months

2
2
0 / 0

[releng] Issue #6854: Proposed f27 change: remove krb5-appl

by Robbie Harwood

rharwood reported a new issue against the project: `releng` that you are following: `` As per [sgallagh's suggestion](https://lists.fedoraproject.org/archives/list/devel@lists.fed..., I would like to have src:krb5-appl (builds krb5-appl-clients and krb5-appl-servers) removed from the distribution for fedora27. The change proposal is [here](https://fedoraproject.org/wiki/Changes/Remove_krb5-appl). I do not believe this affects any other packages. Thanks! `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/6854

6 years, 2 months

2
2
0 / 0

[releng] Issue #6867: F27 proposed change review: Remove SSH-1 from OpenSSH clients

by Jakub Jelen

jjelen reported a new issue against the project: `releng` that you are following: `` Before sending the change proposal to FESCo I was asked to fill a ticket here. https://fedoraproject.org/wiki/Changes/Remove_SSH-1_from_OpenSSH Please, let me know if this is going to affect you in any way (I hope you are not using SSH-1 anymore). Regards, Jakub `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/6867

6 years, 2 months

3
3
0 / 0

[releng] Issue #6869: F27 proposed change review: Samba AD

by Alexander Bokovoy

abbra reported a new issue against the project: `releng` that you are following: `` Please review the following F27 change request: https://fedoraproject.org/wiki/Changes/Samba_AD `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/6869

6 years, 2 months

2
2
0 / 0

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

rel-eng June 2017