June 2017 - rel-eng - Fedora Mailing-Lists

[releng] Issue #6144: Document the semantics of "comps"

by Dennis Gilmore

The issue: `Document the semantics of "comps"` of project: `releng` has been assigned to `ausil` by ausil. https://pagure.io/releng/issue/6144

6 years, 10 months

1
0
0 / 0

[releng] Issue #6477: Clarify in documentation who is authorized to retire the package

by Dennis Gilmore

The issue: `Clarify in documentation who is authorized to retire the package` of project: `releng` has been assigned to `kellin` by ausil. https://pagure.io/releng/issue/6477

6 years, 10 months

1
0
0 / 0

[releng] Issue #342: Build a 'test' compose automatically when installer-related packages change

by Dennis Gilmore

The issue: `Build a 'test' compose automatically when installer-related packages change` of project: `releng` has been assigned to `mohanboddu` by ausil. https://pagure.io/releng/issue/342

6 years, 10 months

1
0
0 / 0

[releng] Issue #6236: Branched critpath generation tracebacks

by Dennis Gilmore

The issue: `Branched critpath generation tracebacks` of project: `releng` has been assigned to `kellin` by ausil. https://pagure.io/releng/issue/6236

6 years, 10 months

1
0
0 / 0

[releng] Issue #6770: ABRT back in Fedora 26

by Matej Habrnal

mhabrnal reported a new issue against the project: `releng` that you are following: `` You've temporarily removed ABRT from Fedora 26 Alfa release because of hawkey dependency and service migration from abrt-ccpp.service to abrt-journal-core.service (see https://bugzilla.redhat.com/show_bug.cgi?id=1436941) ABRT package is now ready (abrt-2.10.2-2.fc26) to be returned back to Fedora release. It has no dependency to hawkey and also spec files contains scriplets which do the migration from abrt-ccpp.service to abrt-journal-core.service. Making the ticket just for sure :) `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/6770

6 years, 10 months

2
3
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: 0ed61d7441eddf96e6a98de4f10f4675268c7888b6d2b8a405b8c21fe6c92d23 Version: 25.137 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, 10 months

2
1
0 / 0

[pungi-fedora] PR #251: Fedora-Modular-Rawhide: Add nodejs-8 and switch back to gather_method='deps'

by Jan Kaluža

jkaluza opened a new pull-request against the project: `pungi-fedora` that you are following: `` Fedora-Modular-Rawhide: Add nodejs-8 and switch back to gather_method='deps' `` To reply, visit the link below or just reply to this email https://pagure.io/pungi-fedora/pull-request/251

6 years, 10 months

2
1
0 / 0

[releng] Issue #5886: need method for distributing urgent fixes... urgently

by Matthew Miller

mattdm added a new comment to an issue you are following: `` @alsadi Well, there's always a balance. We wouldn't want to make things _worse_ by pushing out a bad fix too quickly. The sudo update is an interesting example here. It's obviously a security fix, but the issue it corrects is an escalation from limited sudo privileges to full-root equivalent. In the default configuration in Fedora, we give full-root equivalent to members of the `wheel` group, and nothing else — in other words, unless you've got a special configuration, the issue doesn't matter. Meanwhile, it turns out that the initial fix was incomplete — see https://bugzilla.redhat.com/show_bug.cgi?id=1459152. It isn't in this case, but _could_ have been that the quick fix makes things worse. A bad update to sudo could even lock legitimate users out of their systems. Yes, we need to get updates out quickly... but we also need to make sure that they're _good_ updates. I don't think loosening the amount of required QA is the answer. `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/5886

6 years, 10 months

1
0
0 / 0

[releng] Issue #6826: Please tag piwik for f25-infra

by Ricky Elrod

codeblock reported a new issue against the project: `releng` that you are following: `` We need `piwik` in the Infrastructure repo for F25. This is now done using koji tags, so we need this package added to the list so I can build it. /cc @smooge `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/6826

6 years, 10 months

2
3
0 / 0

using include statements in pungi-fedora

by Dusty Mabe

I've been told recently that we can use include statements within pungi to include variables/definitions in other files into our current configuration file we are working on. Can we start to use this model for our pungi-fedora repo? One example is that the fedora-atomic.conf file has a bunch of configuration at the top of it that is very cryptic to know what's relevant to atomic host image/iso creation and what is not. It would be much better if, for a particular branch, we can have a file that has most common definitions in it for all pungi configs for that branch. Then we can make the individual pungi configs much more lightweight and less confusing. If this is acceptable we can start with the Rawhide branch and when we branch for future releases this will propagate. Thoughts? Dusty

6 years, 10 months

2
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

rel-eng June 2017