April 2016 - rel-eng - Fedora Mailing-Lists

#6401: Unblock Koji for (unretired) surf and add f24 branch

by Fedora Release Engineering

#6401: Unblock Koji for (unretired) surf and add f24 branch -----------------------------+------------------------ Reporter: ngompa | Owner: rel-eng@… Type: task | Status: new Milestone: Fedora 24 Alpha | Component: koji Keywords: | Blocked By: Blocking: | -----------------------------+------------------------ Surf was unretired last week^1^ by me^2^, so I need Koji unblocked for surf and I need the F24 branch created in dist-git. I've already committed changes to master^3^, so it can be branched from master. 1: https://bugzilla.redhat.com/show_bug.cgi?id=1327911 2: https://admin.fedoraproject.org/pkgdb/package/rpms/surf/ 3: http://pkgs.fedoraproject.org/cgit/rpms/surf.git/commit/?id=78934f0d0dfc3... -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6401> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

8 years

1
2
0 / 0

#6396: critpath needs help

by Fedora Release Engineering

#6396: critpath needs help -----------------------------+------------------------ Reporter: kevin | Owner: rel-eng@… Type: task | Status: new Milestone: Fedora 24 Final | Component: koji Keywords: | Blocked By: Blocking: | -----------------------------+------------------------ When we setup critpath it was a collection of packages that were critical to the things we were shipping, so we could have higher requirements on these things in the updates system and possibly someday run more tests on them, etc. Right now: * Updating critpath is broken. The script that pulls packages from comps doesn't work and depends on yum. * Updating critpath is manual. It takes someone to remember to do it, which no one does. * Updating critpath hasn't happened in a long time. (due to the above) * critpath reflects the critical packages... as of Fedora 20 (before we started doing the products). So, we have critpath groups for all the desktops that were on the install dvd (which we no longer make) and nothing at all for cloud or server or atomic or docker or anything related to those. So, we need to: * Fix generation of packages for critpath. * Fix the data it uses so it reflects the things we actually want to be critpath. * Automate it so it updates without humans being involved. -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6396> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

8 years

1
3
0 / 0

Re: #4986: Create a 'Deliverables' page / SOP listing exactly what images, torrent files, signatures, checksums etc should be provided with (pre)-releases

by Fedora Release Engineering

#4986: Create a 'Deliverables' page / SOP listing exactly what images, torrent files, signatures, checksums etc should be provided with (pre)-releases -----------------------+----------------------- Reporter: adamwill | Owner: rel-eng@… Type: task | Status: new Milestone: | Component: other Resolution: | Keywords: Blocked By: | Blocking: -----------------------+----------------------- Changes (by acarter): * cc: acarter (added) -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/4986#comment:16> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

8 years

1
0
0 / 0

#6400: Updates stuck in "This update is currently locked and cannot be modified" state

by Fedora Release Engineering

#6400: Updates stuck in "This update is currently locked and cannot be modified" state --------------------+------------------------ Reporter: ellert | Owner: rel-eng@… Type: task | Status: new Milestone: | Component: mash Keywords: | Blocked By: Blocking: | --------------------+------------------------ A large set of updates submitted to f22-updates-testing and f23-updates- testing during one day 6 days ago are stuck in the locked state in bodhi and never get pushed. Updates submitted to these repos after the affected updates have been successfully pushed. The affected f22-update-testing updates are: * python-justbytes-0.7-1.fc22 * tellico-2.3.11-1.fc22 * sssd-1.13.4-1.fc22 * php-league-climate-3.2.1-1.fc22 * armadillo-6.700.4-1.fc22 * R-qtl-1.39.5-1.fc22 * golang-github-go-tomb-tomb-0-0.6.git14b3d72.fc22 * rasdaemon-0.5.8-2.fc22 * zanata-python-client-1.5.0-2.fc22 * libkml-1.3.0-2.fc22 * gcstar-1.7.1-1.fc22 * youtube-dl-2016.04.13-2.fc22 * davix-0.6.3-1.fc22 * pythia8-8.2.15-2.fc22 * python-debian-0.1.27-3.fc22 * golang-github-smartystreets-goconvey-1.6.1-0.1.gitbf58a9a.fc22 * php-horde-Horde-Css-Parser-1.0.10-1.fc22 * apigen-4.1.2-2.fc22 * golang-github-smartystreets-assertions-1.6.0-0.1.git287b434.fc22 * recoll-1.21.6-1.fc22 * fedfind-2.4.5-1.fc22 The affected f23-update-testing updates are: * python-justbytes-0.7-1.fc23 * gstreamer1-plugins-bad-free-1.6.4-1.fc23 * gstreamer1-plugins-good-1.6.4-1.fc23 * gstreamer1-plugins-base-1.6.4-1.fc23 * gstreamer1-1.6.4-1.fc23 * rubygem-github-linguist-4.8.3-1.fc23 * ascend-0.9.10-7.20151003svn3100.fc23 * golang-github-docker-go-units-0.2.0-3.fc23 * libteam-1.24-1.fc23 * tellico-2.3.11-1.fc23 * pydot-1.0.28-11.fc23 * sssd-1.13.4-1.fc23 * php-akamai-open-edgegrid-client-0.4.4-1.fc23 * php-league-climate-3.2.1-1.fc23 * armadillo-6.700.4-1.fc23 * R-qtl-1.39.5-1.fc23 * golang-github-go-tomb-tomb-0-0.6.git14b3d72.fc23 * rasdaemon-0.5.8-2.fc23 * eclipse-egit-4.3.0-1.fc23 eclipse-egit-github-4.3.0-1.fc23 eclipse- jgi... * zanata-python-client-1.5.0-2.fc23 * libkml-1.3.0-2.fc23 * gcstar-1.7.1-1.fc23 * youtube-dl-2016.04.13-2.fc23 * rubygem-flexmock-2.0.5-1.fc23 * davix-0.6.3-1.fc23 * rubygem-byebug-8.2.4-1.fc23 * pythia8-8.2.15-2.fc23 * python-debian-0.1.27-3.fc23 * golang-github-smartystreets-goconvey-1.6.1-0.1.gitbf58a9a.fc23 * php-horde-Horde-Css-Parser-1.0.10-1.fc23 * apigen-4.1.2-2.fc23 * python-networkx-1.9.1-5.fc23 * golang-github-smartystreets-assertions-1.6.0-0.1.git287b434.fc23 * recoll-1.21.6-1.fc23 * os-autoinst-4.3-7.20160408gitff760a3.fc23 openqa-4.3-24.20160408git45e... * fedfind-2.4.5-1.fc23 For four of these updates the problem was reported in a bodhi issue ticket 3 days ago: https://github.com/fedora-infra/bodhi/issues/828 For a fifth one, a second bodhi issue ticket was filed yesterday: https://github.com/fedora-infra/bodhi/issues/830 No response was yet received on these tickets. -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6400> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

8 years

1
2
0 / 0

Fedora Atomic Host Two Week Release Announcement

by noreply＠fedoraproject.org

A new update of Fedora Cloud Atomic Host has been released and can be downloaded at: Images can be found here: https://getfedora.org/en/cloud/download/atomic.html Respective signed CHECKSUM files can be found here: https://alt.fedoraproject.org/pub/alt/atomic/stable/Cloud-Images/x86_64/I... https://alt.fedoraproject.org/pub/alt/atomic/stable/Cloud_Atomic/x86_64/i... Thank you, Fedora Release Engineering

8 years

1
0
0 / 0

Re: #4986: Create a 'Deliverables' page / SOP listing exactly what images, torrent files, signatures, checksums etc should be provided with (pre)-releases

by Fedora Release Engineering

#4986: Create a 'Deliverables' page / SOP listing exactly what images, torrent files, signatures, checksums etc should be provided with (pre)-releases -----------------------+----------------------- Reporter: adamwill | Owner: rel-eng@… Type: task | Status: new Milestone: | Component: other Resolution: | Keywords: Blocked By: | Blocking: -----------------------+----------------------- Comment (by ausil): pungi does not actually have everything. it does not define where the content ships, or what is to be shipped as a torrent etc. we need to have both the what we build and the where and how we ship it. -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/4986#comment:15> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

8 years

1
0
0 / 0

Re: #4986: Create a 'Deliverables' page / SOP listing exactly what images, torrent files, signatures, checksums etc should be provided with (pre)-releases

by Fedora Release Engineering

#4986: Create a 'Deliverables' page / SOP listing exactly what images, torrent files, signatures, checksums etc should be provided with (pre)-releases -----------------------+----------------------- Reporter: adamwill | Owner: rel-eng@… Type: task | Status: new Milestone: | Component: other Resolution: | Keywords: Blocked By: | Blocking: -----------------------+----------------------- Comment (by ralph): On PDC, two things: - PDC stores the list of things that we actually did produce (by way of importing the metadata output from pungi). - When we first started looking at it, we were thinking about also storing the list of things we *should* produce in a compose as well (which would meet the criteria for this ticket). While the PDC authors were originally receptive to that idea, it seems there is concern out there that the scope of PDC is growing too large and so pushing for an expansion to handle this case may meet with opposition from upstream. Another idea: since we keep our pungi config public here https://pagure.io/pungi-fedora/raw/master/f/fedora.conf and since it actually defines what we will try to produce, we could build separate tooling around it that reads it in and parses it to produce a list of expected outputs. (And we could go back in the git history to figure out what we intended to produce at some date in the past.) -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/4986#comment:14> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

8 years

1
0
0 / 0

Re: #4986: Create a 'Deliverables' page / SOP listing exactly what images, torrent files, signatures, checksums etc should be provided with (pre)-releases

by Fedora Release Engineering

#4986: Create a 'Deliverables' page / SOP listing exactly what images, torrent files, signatures, checksums etc should be provided with (pre)-releases -----------------------+----------------------- Reporter: adamwill | Owner: rel-eng@… Type: task | Status: new Milestone: | Component: other Resolution: | Keywords: Blocked By: | Blocking: -----------------------+----------------------- Comment (by acarter): I understand from DGilmore that there are in fact things that we're shipping that aren't on that list (see today's flurry around Live USB amongst others). Jan, please just keep us updated on the discussion and if you want to propose how we should handle this in the future, I think we'd all be on board to make it happen :) -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/4986#comment:13> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

8 years

1
0
0 / 0

Invitation: Fedora Release Tools Demo (Live Broadcast) @ Thu Apr 21, 2016 12pm - 1pm (acarter@redhat.com)

by Amanda Carter

You have been invited to the following event. Title: Fedora Release Tools Demo (Live Broadcast) Hangout: The hangout will be broadcast live & posted: http://www.youtube.com/watch?v=ivZqOR82ocQ Q&A - #fedora-meeting -- Purpose: The purpose of a demo is to show our stakeholders what we completed this iteration, get feedback from them about the changes & set some context and expectation with them about our direction. Demo agenda & previous demos can be viewed here: http://taiga.fedorainfracloud.org/project/acarter-fedora-docker-atomic-to... Highlights today: * OSBS + registry deployment in stage (building & pulling Cockpit image) * OStree builds in Pungi When: Thu Apr 21, 2016 12pm - 1pm Eastern Time Where: Hangout on Air / YouTube live stream Calendar: acarter(a)redhat.com Who: * acarter(a)redhat.com - organizer * rbarlow(a)redhat.com * twaugh(a)redhat.com * mmcgrath(a)redhat.com * dperpeet(a)redhat.com * server(a)lists.fedoraproject.org * rel-eng(a)lists.fedoraproject.org * desktop(a)lists.fedoraproject.org * kasingh(a)redhat.com * rcm-tools(a)redhat.com * sgallagh(a)redhat.com * aos-devel * cloud(a)lists.fedoraproject.org Event details: https://www.google.com/calendar/event?action=VIEW&eid=dHMxNWN2ajBiNjNmYjY... Invitation from Google Calendar: https://www.google.com/calendar/ You are receiving this courtesy email at the account rel-eng(a)lists.fedoraproject.org because you are an attendee of this event. To stop receiving future updates for this event, decline this event. Alternatively you can sign up for a Google account at https://www.google.com/calendar/ and control your notification settings for your entire calendar. Forwarding this invitation could allow any recipient to modify your RSVP response. Learn more at https://support.google.com/calendar/answer/37135#forwarding

8 years

1
0
0 / 0

Re: #3624: compress fullfilelist and update only on-demand

by Fedora Release Engineering

#3624: compress fullfilelist and update only on-demand --------------------------+----------------------- Reporter: mmcgrath | Owner: rel-eng@… Type: enhancement | Status: new Milestone: | Component: other Resolution: | Keywords: Blocked By: | Blocking: --------------------------+----------------------- Comment (by kevin): It should be perfectly easy to run hardlink locally as desired. -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/3624#comment:9> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

8 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

rel-eng April 2016