rel-eng April 2017

rel-eng@lists.fedoraproject.org

10 participants
161 discussions

[releng] Issue #5665: Providing a master CHECKSUMS file for boot.fpo
by Dennis Gilmore 25 Apr '17

25 Apr '17

The status of the issue: `Providing a master CHECKSUMS file for boot.fpo` of project: `releng` has been updated to: Closed as Insufficient data by ausil. https://pagure.io/releng/issue/5665

1 0

[releng] Issue #5665: Providing a master CHECKSUMS file for boot.fpo
by Kaitlyn Carcia 25 Apr '17

25 Apr '17

katec added a new comment to an issue you are following: `` Closed since we are unclear about what's being asked for here. `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/5665

1 0

[releng] Issue #4986: Create a 'Deliverables' page / SOP listing exactly what images, torrent files, signatures, checksums etc should be provided with (pre)-releases
by Kaitlyn Carcia 25 Apr '17

25 Apr '17

The issue: `Create a 'Deliverables' page / SOP listing exactly what images, torrent files, signatures, checksums etc should be provided with (pre)-releases` of project: `releng` has been assigned to `kellin` by katec. https://pagure.io/releng/issue/4986

1 0

[releng] Issue #4986: Create a 'Deliverables' page / SOP listing exactly what images, torrent files, signatures, checksums etc should be provided with (pre)-releases
by Kaitlyn Carcia 25 Apr '17

25 Apr '17

katec added a new comment to an issue you are following: `` Needs to be in PDC to help maintainability. `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/4986

1 0

[releng] Issue #4084: mulilibbed packages could be inconsistet in the updates and updates-testing repos compared to the Release tree repo
by Kaitlyn Carcia 25 Apr '17

25 Apr '17

katec added a new comment to an issue you are following: `` Not a trivial fix even with signed repos, also not high priority. (Would need to be addressed in Mash, Koji, Bodhi today). If we move everything to dist-repos in the future, we would only have to fix it there and teach pungi and bodhi how to use it. `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/4084

1 0

Re: Pagure on dist-git, the state of things
by Paul W. Frields 25 Apr '17

25 Apr '17

Just making sure the whole original message made it to rel-eng list. Reply-to is set to infra@ so we can keep discussion in one place. On Thu, Apr 20, 2017 at 12:08:35PM -0500, Dennis Gilmore wrote: > Can you please report this to releng also? > > Dennis > > > El jue, 20-04-2017 a las 15:45 +0200, Pierre-Yves Chibon escribió: > > Good Morning Everyone, > > > > I figured it has been a while since I reported progress on making pagure a > > front-end for dist-git. > > > > So here is a small status update. > > > > What works: > > - Well currently pagure is working as a front-end for dist-git in stg: > > https://src.stg.fedoraproject.org/pagure/ > > - Hosting repos, browsing them, creating PR works all fine (w/ one , see > > below) > > - Features we want to exclude have been turned off (no user management on the > > pagure side) > > > > What does not work: > > - Syncing the ACLs from pkgdb to gitolite takes ~3 minutes in prod, in stg, the > > updated script in stg (which sync the ACLs from pkgdb to gitolite and pagure) > > runs in ~30/35 minutes (if it doesn't crash, which my last run just did) > > This is a blocker since it means it takes 30 to 35 minutes for someone to get > > access to their git repo or (worse) their fork > > - This pagure instance has the same issue as the main one, including a heisenbug > > we're trying to track but have had no luck reproducing so far :( > > > > What needs to be done: > > - Fix the sync script > > - Make it *way* faster than it is > > - Make it creates the project on pagure using the releng user rather than > > relying on the first contributor it finds in the list of maintainers > > - Make fedmsg-genacls be triggered on pagure's fork fedmsg message so that we > > re-generate the gitolite configuration file when someone forks a project > > (and thus give them access to their fork) > > - Once above is done: call for more testers > > > > In the future: > > - I think we will want to deprecate pkgdb entirely, so while the work above is > > important, ideally it won't be there for too long. > > - With pkgdb out of the loop, we'll need to figure some things out: > > - Where/How to store the contact info for bugzilla > > - Not sure relying on pagure's ACLs there is the way to go since we would > > loose a level of granularity in the ACLs that I know people like and ask > > for (having commit w/o being on the CC list in bugzilla or being on the CC > > list w/o being a packager) > > - How/when to require people be part of the packager group in FAS? > > - Since one of the idea of pagure is to make it easier for "drive-by" > > contribution to spec files, requiring to be a packager should only be > > there for maintainers, but pagure doesn't have this level of > > information/requirement, so we would need to find something or some place > > to add this requirement or see if that requirement still stands > > > > This is all I can think of for now, I'll update this thread if I come up with > > more ideas/challenges. > > > > > > Have a nice day, > > Pierre

1 0

[releng] Issue #6760: Adding pkgdb2 to epel7-infra
by Pierre-YvesChibon 24 Apr '17

24 Apr '17

pingou reported a new issue against the project: `releng` that you are following: `` Hi, Would it be possible to add the package: pkgdb2 to the koji tag epel7-infra? Thanks :) `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/6760

2 2

Fedora Release Engineering meeting summary for 2017-04-24
by Mohan Boddu 24 Apr '17

24 Apr '17

====================================== #fedora-meeting-2: RELENG (2017-04-24) ====================================== Meeting started by mboddu at 14:33:38 UTC. The full logs are available athttps://meetbot.fedoraproject.org/fedora-meeting-2/2017-04-24/releng.2017… . Meeting summary --------------- * init process (mboddu, 14:33:38) * #6756 "ActionNotAllowed" when attempting "koji untag-build f27" (mboddu, 14:37:55) * LINK: https://pagure.io/releng/issue/6756 (mboddu, 14:38:03) * current state is that users can not untag builds from rawhide, and need to file a releng issue to untag builds (dgilmore, 14:54:53) * ACTION: investigate adjusting hub policy to allow users to untag builds (dgilmore, 14:55:23) * LINK: https://infrastructure.fedoraproject.org/cgit/ansible.git/tree/roles/koji_h… (nirik, 14:55:50) * possible other solutions are a microservice to allow users request untagging of builds, that enforces policy. (dgilmore, 14:56:04) * ACTION: document and communicate the current status with devel@ (dgilmore, 14:56:39) * the f27 tag was limited in permsisons when we enabled autosigning to ensure only signed builds make it into rawhide (dgilmore, 14:57:41) * likely worth filing some RFE's with koji to have finer graied controls (dgilmore, 14:58:48) * #6739 F26 Alpha image paths and CHECKSUM files changed partially from underscore to dash (mboddu, 15:02:26) * LINK: https://pagure.io/releng/issue/6739 (mboddu, 15:02:32) * ACTION: Kellin will document the right values to be used for Alpha/Beta configs and for GA config (mboddu, 15:07:57) * #6663 Create another new tag for Modularity (mboddu, 15:08:19) * LINK: https://pagure.io/releng/issue/6663 (mboddu, 15:08:30) * ACTION: jkaluza to reach out to koji devs to get the conversation started on figuing out how to drop the permissions of module builds and management (dgilmore, 15:28:40) * LINK: https://fedoraproject.org/wiki/Releases/26/Schedule (dgilmore, 15:34:47) * Open Floor (dgilmore, 15:37:02) * LINK: https://koji.fedoraproject.org/koji/channelinfo?channelID=9 (dgilmore, 15:44:10) * ARMv7 virt builders have been live in prod for nearly a week (mboddu, 15:46:31) * Old arm builders will be disabled today (mboddu, 15:46:53) Meeting ended at 15:48:48 UTC. Action Items ------------ * investigate adjusting hub policy to allow users to untag builds * document and communicate the current status with devel@ * Kellin will document the right values to be used for Alpha/Beta configs and for GA config * jkaluza to reach out to koji devs to get the conversation started on figuing out how to drop the permissions of module builds and management Action Items, by person ----------------------- * jkaluza * jkaluza to reach out to koji devs to get the conversation started on figuing out how to drop the permissions of module builds and management * Kellin * Kellin will document the right values to be used for Alpha/Beta configs and for GA config * **UNASSIGNED** * investigate adjusting hub policy to allow users to untag builds * document and communicate the current status with devel@ People Present (lines said) --------------------------- * dgilmore (113) * mboddu (41) * nirik (37) * pbrobinson (22) * jkaluza (21) * contyk (7) * masta (6) * zodbot (6) * puiterwijk (5) * Kellin (3) * sharkcz (1) * tyll (0) * pingou (0) * maxamillion (0) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

1 0

[releng] Issue #5805: add index.asc files for cloud images for virt-builder
by Brian Stinson 24 Apr '17

24 Apr '17

bstinson added a new comment to an issue you are following: `` We have a script that walks a directory and generates the virt-builder index format from any of the images it finds: http://cloud.centos.org/centos/7/images/image-index `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/5805

1 0

[releng] Issue #5843: Create koji plugin to allow building only from whitelisted git branches
by Pierre-YvesChibon 24 Apr '17

24 Apr '17

pingou added a new comment to an issue you are following: `` > @pingou Thank you for omitting the second half of my response That's just because I pretty much had to take a break after reading the first part. That's what I do when I encounter such strong language. > Can't we just have it so that private branches can only be used for scratch builds? If you're willing to work on it and get it accepted upstream, I'm sure this would satisfy all parties involved and solve all three tickets related to this. `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/5843

1 0

← Newer
1
2
3
4
5
6
7
8
9
...
17
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

rel-eng April 2017