June 2015 - rel-eng - Fedora Mailing-Lists

Re: #6177: Git-process-request not processing request

by Fedora Release Engineering

#6177: Git-process-request not processing request ---------------------+----------------------- Reporter: misc | Owner: rel-eng@… Type: defect | Status: new Milestone: | Component: other Resolution: | Keywords: Blocked By: | Blocking: ---------------------+----------------------- Changes (by zbyszek): * cc: zbyszek (added) Comment: Ping! -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6177#comment:1> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

8 years, 5 months

1
0
0 / 0

#6192: Issues with Vagrant boxes need fixing

by Fedora Release Engineering

#6192: Issues with Vagrant boxes need fixing -----------------------------+------------------------ Reporter: purpleidea | Owner: rel-eng@… Type: defect | Status: new Milestone: Fedora 22 Final | Component: koji Keywords: vagrant, urgent | Blocked By: Blocking: | -----------------------------+------------------------ See: https://bugzilla.redhat.com/show_bug.cgi?id=1225630 and: https://bugzilla.redhat.com/show_bug.cgi?id=1225624 -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6192> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

8 years, 5 months

1
2
0 / 0

[Fedocal] Reminder meeting : Fedora Release Engineering

by Dennis Gilmore

Dear all, You are kindly invited to the meeting: Fedora Release Engineering on 2015-06-08 from 15:30:00 to 16:30:00 UTC At fedora-meeting-1(a)irc.freenode.net The meeting will be about: Fedora Release Engineering weekly meeting Source: https://apps.fedoraproject.org/calendar/meeting/2026/

8 years, 5 months

1
0
0 / 0

Re: #6149: Fedora secondary arches .composeinfos are missing and need to be made

by Fedora Release Engineering

#6149: Fedora secondary arches .composeinfos are missing and need to be made ---------------------+------------------------ Reporter: alemay | Owner: pbrobinson Type: task | Status: new Milestone: | Component: other Resolution: | Keywords: Blocked By: | Blocking: testing ---------------------+------------------------ Changes (by pbrobinson): * owner: rel-eng@… => pbrobinson -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6149#comment:3> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

8 years, 6 months

1
0
0 / 0

#6190: Blocked packages can still appear in updates and updates-testing repos

by Fedora Release Engineering

#6190: Blocked packages can still appear in updates and updates-testing repos -----------------------------+------------------------ Reporter: kalev | Owner: rel-eng@… Type: task | Status: new Milestone: Fedora 22 Final | Component: koji Keywords: | Blocked By: Blocking: | -----------------------------+------------------------ Looks like packages that have gotten blocked in the f22 tag can still show up in the updates and updates-testing repos if they are tagged as such. As an example, ghc-shakespeare-text is blocked in f22: {{{ $ koji list-pkgs --show-blocked --package ghc-shakespeare-text Package Tag Extra Arches Owner ----------------------- ----------------------- ---------------- --------------- ghc-shakespeare-text trashcan mathstuf ghc-shakespeare-text f17 mathstuf ghc-shakespeare-text f18 mathstuf ghc-shakespeare-text f22 mathstuf [BLOCKED] ghc-shakespeare-text f22-updates mathstuf ghc-shakespeare-text f21-beta mathstuf ghc-shakespeare-text f23 mathstuf [BLOCKED] ghc-shakespeare-text f22-Alpha mathstuf ghc-shakespeare-text f22-Beta mathstuf }}} But it still shows up in the repos: - http://dl.fedoraproject.org/pub/fedora/linux/updates/22/x86_64/g/ghc- shakespeare-text-1.1.0-3.fc22.x86_64.rpm - http://dl.fedoraproject.org/pub/fedora/linux/updates/testing/22/x86_64/g /ghc-shakespeare-text-1.1.0-3.fc22.x86_64.rpm -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6190> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

8 years, 6 months

1
1
0 / 0

#6191: ExtUtils-CBuilder-0.280223.tar.gz missing in look-aside cache

by Fedora Release Engineering

#6191: ExtUtils-CBuilder-0.280223.tar.gz missing in look-aside cache -----------------------------+------------------------ Reporter: ppisar | Owner: rel-eng@… Type: defect | Status: new Milestone: Fedora 22 Final | Component: koji Keywords: | Blocked By: Blocking: | -----------------------------+------------------------ I uploaded !ExtUtils-CBuilder-0.280223.tar.gz for perl-!ExtUtils-CBuilder package by fedpkg tool. It did not report any issue but consecutive source download fails: {{{ $ fedpkg sources Downloading ExtUtils-CBuilder-0.280223.tar.gz % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 curl: (22) The requested URL returned error: 404 Not Found Could not execute sources: Command '['curl', '-H', 'Pragma:', '-o', './ExtUtils-CBuilder-0.280223.tar.gz', '-R', '-S', '--fail', 'http://pkgs.fedoraproject.org/repo/pkgs/perl-ExtUtils-CBuilder/ExtUtils- CBuilder-0.280223.tar.gz/54269e7cb7a5d995d28fc46933c6e045/ExtUtils- CBuilder-0.280223.tar.gz']' returned non-zero exit status 22 }}} The issue is the [http://pkgs.fedoraproject.org/repo/pkgs/perl-ExtUtils- CBuilder/ExtUtils- CBuilder-0.280223.tar.gz/54269e7cb7a5d995d28fc46933c6e045/] directory on the server is empty. I cannot reupload it as it fedpkg reports the file is already there. It prevents me from building the package. -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6191> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

8 years, 6 months

1
8
0 / 0

#6187: glibc32 should be tagged as f23-build

by Fedora Release Engineering

#6187: glibc32 should be tagged as f23-build -----------------------------+------------------------ Reporter: mjw | Owner: rel-eng@… Type: defect | Status: new Milestone: Fedora 23 Alpha | Component: koji Keywords: | Blocked By: Blocking: | -----------------------------+------------------------ Without this package builds, like valgrind, requiring (fake) 32bit glibc libraries on 64bit arches that are multilib cannot be build because their BuildRequires fail. -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6187> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

8 years, 6 months

1
2
0 / 0

Prioritizing FAD Goals and Deliverables

by Adam Miller

Hello all, There was previously some good discussion around FAD Goals and Deliverables[0]. I was hoping that we could start to get priorities lined up. I had an idea about "Current Gen Tooling" vs "Next Gen Tooling" objectives and kind of changed that table in the wiki[1] to reflect. (If there are objections on that please let me know, it just made sense in my head). What I would like to propose is that we select 3 top priority items from the "Current Gen" list as well as 3 top priority items from the "Next Gen" list, then scope those items out somewhere (maybe even just on this wiki page) with enough detail that it's clear to everyone what the problem is and what the deliverable will be. From there I think we can order the remaining items in a list of "Nice to Haves" if there is enough time. When we meet for the FAD, focus on the prioritized and scoped out items and if we just kick butt and knock them all out then move on to the "Nice to Have" list. Here's my vote(s) for top 3 in each and why: Current Gen: - Working pungi4: Why? This will give us a lot of near-term wins for making rel-eng build/compose operations parallel by being able to farm them out to builders in koji - stage koji needs to be and then get it setup/deployed, ansiblized. Why? Right now it's very difficult to properly test new versions of the tools because there's not a proper staging/testing evironment - rawhide looking like a TC/RC Why? Making these align will allow for the rel-eng process and tooling to be identical between Rawhide/TC/RC where as of today that is not the case Next Gen: - define what composedb should be Why? I keep hearing about this mythical thing and the problems it will solve, would love to see it's ideas/requirements put down on paper so we can start working on it. - koji 2.0 Draft document Why? This is another space where there is this mythical thing people talk about that will solve a bunch of problems. Would love to see it come to fruition - Content Generators for Koji Why? This to me seems like something that will open up Koji 1.x for more flexibility and allow Rel-Eng to iterate and deliver newer build types/artifacts while we work towards Koji 2.x (which I think should also support the metadata format as defined by content generators for migration and compatibility reasons) Thoughts? I look forward to feedback and if anyone thinks I'm running around in crazy-town please let me know. It just seemed like the old idea gathering thread went stale and now would be a good time to start prioritizing and scoping. Thank you, -AdamM [0] - https://lists.fedoraproject.org/pipermail/rel-eng/2015-May/020075.html [1] - https://fedoraproject.org/wiki/FAD_Release_Tools_and_Infrastructure_2015#...

8 years, 6 months

3
2
0 / 0

Re: #6172: Grant admin permission on staging Koji to mizdebsk

by Fedora Release Engineering

#6172: Grant admin permission on staging Koji to mizdebsk ------------------------------+----------------------- Reporter: mizdebsk | Owner: rel-eng@… Type: task | Status: new Milestone: Fedora 22 Final | Component: koji Resolution: | Keywords: Blocked By: | Blocking: ------------------------------+----------------------- Comment (by pingou): That's because there are no rel-eng people monitoring pkgdb in stg, should the package be added to pkgdb? Do you need this one in particular? -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6172#comment:7> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

8 years, 6 months

1
0
0 / 0

Re: #6172: Grant admin permission on staging Koji to mizdebsk

by Fedora Release Engineering

#6172: Grant admin permission on staging Koji to mizdebsk ------------------------------+----------------------- Reporter: mizdebsk | Owner: rel-eng@… Type: task | Status: new Milestone: Fedora 22 Final | Component: koji Resolution: | Keywords: Blocked By: | Blocking: ------------------------------+----------------------- Comment (by mizdebsk): Replying to [comment:5 pingou]: > Replying to [comment:4 mizdebsk]: > > Replying to [comment:3 ausil]: > > > That should all be done from staging pkgdb. > > > > Then can you point me to documentation how to request new package in staging pkgdb, or in case such documentation is missing, explain it yourself? > > Well, it works just like the production pkgdb: go to: https://admin.stg.fedoraproject.org/pkgdb/ click on the big blue button: `Request new package` that should bring you to https://admin.stg.fedoraproject.org/pkgdb/request/package/ and enter the information :) I've already done that, but there was no response in 12 days (request ID 11, status "pending"). https://apps.stg.fedoraproject.org/datagrepper/id?id=2015-d1dd5184-c99f- 4dfb-ac1b-1a107bc852bf -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6172#comment:6> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

8 years, 6 months

1
0
0 / 0

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

rel-eng June 2015