June 2017 - rel-eng - Fedora Mailing-Lists

[Fedocal] Reminder meeting : Fedora Release Engineering

by ausil＠fedoraproject.org

Dear all, You are kindly invited to the meeting: Fedora Release Engineering on 2017-06-12 from 09:30:00 to 10:30:00 US/Central At fedora-meeting-2(a)irc.freenode.net The meeting will be about: Fedora Release Engineering weekly meeting Source: https://apps.fedoraproject.org/calendar/meeting/5873/

6 years, 10 months

1
0
0 / 0

[releng] Issue #6834: opt to arg parse remnants in sign script

by Jon Disnard

parasense reported a new issue against the project: `releng` that you are following: `` I was doing a --write-all for thing thing I was signing, and looks liek somebody converted to arg parse, but forgot a reference to optparse. Trivial fix. Here is the diff. diff --git a/scripts/sigulsign_unsigned.py b/scripts/sigulsign_unsigned.py index c9dff3a..0bbce56 100755 --- a/scripts/sigulsign_unsigned.py +++ b/scripts/sigulsign_unsigned.py @@ -223,7 +223,7 @@ def writeRPMs(status, kojihelper, batch=None): Returns status, increased by one in case of failure""" # Check to see if we want to write all, or just the unsigned. - if opts.write_all: + if args.write_all: rpms = rpmdict.keys() else: if batch is None: PR incoming. `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/6834

6 years, 10 months

2
2
0 / 0

[releng] PR #6835: fix missing migration from opt to arg parser

by Jon Disnard

parasense opened a new pull-request against the project: `releng` that you are following: `` fix missing migration from opt to arg parser `` To reply, visit the link below or just reply to this email https://pagure.io/releng/pull-request/6835

6 years, 10 months

2
1
0 / 0

[releng] Issue #6821: Create new side-tag and build-root f27-perl

by Jitka Plesnikova

jplesnik reported a new issue against the project: `releng` that you are following: `` With respect to perl upgrade <https://fedoraproject.org/wiki/Changes/perl5.26>, I request for new side-tag, target, and build-root inheriting from current rawhide. Preferred name is f27-perl. `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/6821

6 years, 10 months

2
7
0 / 0

[releng] Issue #6780: FLIBS: bogus 'authorative-source-url' in layered images

by Micah Abbott

miabbott reported a new issue against the project: `releng` that you are following: `` Originally filed as atomic-wg#272. Finally routed here via help from @ttomecek and @kevin --- I pulled the `cockpit`, `etcd`, and `flannel` images from `registry.fedoraproject.org` and found that they all have a label named `authorative-source-url` in their metadata. Unfortunately, this label is set to `registry.example.com` ``` # atomic info registry.fedoraproject.org/f25/flannel | grep auth authoritative-source-url: registry.example.com # atomic info registry.fedoraproject.org/f25/etcd | grep auth authoritative-source-url: registry.example.com # atomic info registry.fedoraproject.org/f25/cockpit | grep auth authoritative-source-url: registry.example.com ``` I checked their Dockerfiles in dist-git and didn't see the label defined there, so I'm guessing this is getting injected as part of the build process. `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/6780

6 years, 10 months

2
1
0 / 0

[releng] Issue #6617 `consider cron script for bodhi updates pushes`

by Kevin Fenzi

kevin reported a new issue against the project: `releng` that you are following: `` Right now we have a list of releng folks that trade off weekly handling bodhi updates pushes. Because all these folks are in different locations and have different workdays and business, updates pushes happen as they are able throughout the day. Additionally some folks are able to push on weekends and holidays and others are not. Since we no longer need a human release engineer to sign packages before pushing updates, we should consider moving this to just a cron script that runs at the same time every day. This would have the advantage of making the pushes much more predictable and would also save time of busy release engineers. The script would need to have a bit of error handling and check for existing lock files and error out if any exist. It would also need to be adjustable during freezes to not push the stable updates for the frozen release. Any issues or problems would need to follow a process of filing a ticket on the issue and all release engineers communicating on that ticket so no one is duplicating efforts. `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/6617

6 years, 10 months

4
5
0 / 0

[releng] Issue #6827: RFE: kojira to create src repos

by Igor Gnatenko

ignatenkobrain reported a new issue against the project: `releng` that you are following: `` kojira supports `--with-src` option and I think we don't use it now.. So now I have to download 60G of SRPMs just to generate source repo locally =( That would be awesome if you will set up kojira to generate source rpms repo along with normal ones, so we will be able to consume it without needing to download thousands of SRPM. `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/6827

6 years, 10 months

2
5
0 / 0

[releng] Issue #6819: RFE: arch-dependent SRPMs

by Igor Gnatenko

ignatenkobrain reported a new issue against the project: `releng` that you are following: `` As of now we publish only one version of src.rpm which was built on random architecture in koji which is enough for end-users to get source code and do something with it. However, there are more use-cases for SRPMs like getting its requires remotely (what yum-builddep/dnf-builddep and other tools are doing). For example, people report bugs like https://bugzilla.redhat.com/show_bug.cgi?id=1402784. In base-runtime we query for runtime and build dependencies for packages recursively and we have to regenerate SRPMs for architecture we are looking for the dependencies, so either we should take all srpms and regenerate them for each architecture (which is not really fast) or try-and-guess which packages use %ifarch or similar. I would like to ask releng to find solution how to share srpms which are different on different architectures. Thanks in advance! `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/6819

6 years, 10 months

2
3
0 / 0

[releng] Issue #6830: please retire nuvolaplayer for f25 branch

by Martin Gansser

martinkg reported a new issue against the project: `releng` that you are following: `` please retire nuvolaplayer for f25 branch. I could retire nuvolaplayer for rawhide and f26 but f25 fails. https://admin.fedoraproject.org/pkgdb/package/rpms/nuvolaplayer/ $ pkgdb-cli orphan --retire nuvolaplayer f25 No `dead.package` for nuvolaplayer on f25, please use `fedpkg retire` $ fedpkg retire "Renamed to nuvolaruntime" dead.package found, package probably already retired - will not remove files from git or overwrite existing dead.package file Everything up-to-date FAS password for user martinkg: Could not execute retire: Authentication failed I think i added the correct FAS password, but it fails always. `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/6830

6 years, 10 months

2
2
0 / 0

[releng] Issue #6825: Grant jkaluza the "infra" permission in koji.

by Ralph Bean

ralph reported a new issue against the project: `releng` that you are following: `` jkaluza has to ask for someone with the infra permission to regularly tag builds into the epel7-infra tag for him in order to deploy the module-build-service (today, he bothers pingou, mizdebsk, and putierwijk to do this). This makes things slow. I'm requesting that we give jkaluza the "infra" permission in koji which will let him do this himself. `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/6825

6 years, 10 months

4
5
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

rel-eng June 2017