February 2016 - rel-eng - Fedora mailing-lists

#6210: new build of fedora:{21, 22} docker images needed for CVE-2015-1793
by Fedora Release Engineering 14 Nov '16

14 Nov '16

#6210: new build of fedora:{21,22} docker images needed for CVE-2015-1793 ------------------+------------------------ Reporter: lsm5 | Owner: rel-eng@… Type: task | Status: new Milestone: | Component: koji Keywords: | Blocked By: Blocking: | ------------------+------------------------ The fedora docker images are affected by CVE-2015-1793. Please see: https://github.com/docker-library/official-images/issues/878 and https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2015-1793 for details. Need new builds of these images to take care of it. (Looks like the rawhide image is affected too) -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6210> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 2

#6219: Need updated cloud images for Fedora 22
by Fedora Release Engineering 14 Nov '16

14 Nov '16

#6219: Need updated cloud images for Fedora 22 -----------------------------+------------------------ Reporter: kushal | Owner: rel-eng@… Type: task | Status: new Milestone: Fedora 22 Final | Component: other Keywords: | Blocked By: Blocking: | -----------------------------+------------------------ Hi, I have tested the following tree with the formal tests. Please do a release of the updated cloud images from this tree. http://alt.fedoraproject.org/pub/alt/stage/22-20150720/Cloud- Images/x86_64/Images/ -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6219> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 3

#6252: please create a rawhide and f23 side tag for llvm updates
by Fedora Release Engineering 14 Nov '16

14 Nov '16

#6252: please create a rawhide and f23 side tag for llvm updates -----------------------------+------------------------ Reporter: airlied | Owner: rel-eng@… Type: task | Status: new Milestone: Fedora 23 Final | Component: git Keywords: | Blocked By: Blocking: | -----------------------------+------------------------ Hi guys, I want to update llvm to 3.7 in rawhide and f23, but I'd like to build all the deps in a side tag first to make sure. Can you create two tags? Dave. -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6252> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 8

#6355: Latest createImage task used old spin-kickstarts commit
by Fedora Release Engineering 14 Nov '16

14 Nov '16

#6355: Latest createImage task used old spin-kickstarts commit -----------------------------+------------------------ Reporter: jlebon | Owner: rel-eng@… Type: task | Status: new Milestone: Fedora 24 Alpha | Component: koji Keywords: | Blocked By: Blocking: | -----------------------------+------------------------ The latest Fedora Cloud Atomic 23 image released yesterday was produced from an out of date kickstart file. The associated koji task is: http://koji.fedoraproject.org/koji/taskinfo?taskID=13102744 Judging by the name of the ks file ("fedora-cloud-atomic-2878aa0.ks"), it seems like it used commit 2878aa0 of the spin-kickstarts repo, which is *not* the current HEAD (current HEAD is 6641de0, committed 5 days ago). -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6355> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 1

#6344: Strange issue on php-JsonSchema-1.6.1-1.fc22
by Fedora Release Engineering 14 Nov '16

14 Nov '16

#6344: Strange issue on php-JsonSchema-1.6.1-1.fc22 -----------------------------+------------------------ Reporter: remi | Owner: rel-eng@… Type: task | Status: new Milestone: Fedora 24 Alpha | Component: koji Keywords: | Blocked By: Blocking: | -----------------------------+------------------------ Yesterday, I received a bodhi notification: php-JsonSchema-1.6.1-1.fc22 ejected from the push because u"Cannot find relevant tag for php-JsonSchema-1.6.1-1.fc22. None of ['f22-updates- testing', 'f22-updates-testing-pending'] are in [u'epel7-testing- candidate', u'dist-6E-epel-testing-candidate', u'dist-5E-epel-testing- candidate', u'f22-updates-candidate', u'f23-updates-candidate', u'f21 -updates-candidate']." According to http://koji.fedoraproject.org/koji/buildinfo?buildID=713713 Pakage is tag f22-updates-testing According to https://bodhi.fedoraproject.org/updates/FEDORA-2016-59f94c4aea Update is "locked" and pending. Can you please check ? -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6344> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 6

#6184: suitesparse can't be installed in ppc64 el6 buildroots
by Fedora Release Engineering 07 Nov '16

07 Nov '16

#6184: suitesparse can't be installed in ppc64 el6 buildroots -----------------------------+------------------------ Reporter: rmattes | Owner: rel-eng@… Type: defect | Status: new Milestone: Fedora 23 Final | Component: epel Keywords: | Blocked By: Blocking: | -----------------------------+------------------------ I'm running into trouble building GeographicLib in epel6. GeographicLib requires octave, which in turn requires suitesparse. It looks like suitesparse was in epel for a while, but got absorbed into rhel at some point and blocked from the buildroots. Since centos doesn't provide ppc64 packages, the ppc64 octave package in epel now has missing dependencies on suitesparse libraries and can't be installed in koji. What's the best way forward for this issue? Is it to: - Unblock the epel6 suitesparse and make it exclusivearch ppc64? - Rebuild all of the dependencies of suitesparse to excludearch ppc64? - Make octave-GeographicLib excludearch ppc64 and ignore the issue entirely? Please advise. -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6184> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 3

#6348: Missing suitesparse-3.4.0-9.el6 ppc64 package
by Fedora Release Engineering 07 Nov '16

07 Nov '16

#6348: Missing suitesparse-3.4.0-9.el6 ppc64 package --------------------+------------------------ Reporter: ellert | Owner: rel-eng@… Type: task | Status: new Milestone: | Component: epel Keywords: | Blocked By: Blocking: | --------------------+------------------------ The octave package is not installable in EPEL 6 ppc64: https://kojipkgs.fedoraproject.org//work/tasks/1598/12901598/root.log {{{ DEBUG util.py:399: Error: Package: 6:octave-3.4.3-1.el6.ppc64 (build) DEBUG util.py:399: Requires: libamd.so.2()(64bit) DEBUG util.py:399: Error: Package: 6:octave-3.4.3-1.el6.ppc64 (build) DEBUG util.py:399: Requires: libcolamd.so.2()(64bit) DEBUG util.py:399: Error: Package: 6:octave-3.4.3-1.el6.ppc64 (build) DEBUG util.py:399: Requires: libcamd.so.2()(64bit) DEBUG util.py:399: Error: Package: 6:octave-3.4.3-1.el6.ppc64 (build) DEBUG util.py:399: Requires: libumfpack.so.5()(64bit) DEBUG util.py:399: Error: Package: 6:octave-3.4.3-1.el6.ppc64 (build) DEBUG util.py:399: Requires: libcholmod.so.1()(64bit) DEBUG util.py:399: Error: Package: 6:octave-3.4.3-1.el6.ppc64 (build) DEBUG util.py:399: Requires: libccolamd.so.2()(64bit) DEBUG util.py:399: Error: Package: 6:octave-3.4.3-1.el6.ppc64 (build) DEBUG util.py:399: Requires: libcxsparse.so.2()(64bit) }}} On x86_64 and i686 these are provided by suitesparse-3.4.0-9.el6. The suitesparse package is provided by RHEL, but it seems to be missing for ppc64. There is an older version suitesparse-3.4.0-2.el6 provided by EPEL, but since this has a lower NVR than the RHEL version it is not used in the koji build roots. This was the version that was used to build the octave package for EPEL 6 ppc64. It looks like when the suitesparse package started being provided by RHEL 6 and the EPEL 6 package was retired, the ppc64 version of the package got lost. -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6348> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 5

#6313: atomic host: reorienting ostree commits to match 2 week cadence
by Fedora Release Engineering 14 Oct '16

14 Oct '16

#6313: atomic host: reorienting ostree commits to match 2 week cadence -----------------------------+------------------------ Reporter: walters | Owner: rel-eng@… Type: task | Status: new Milestone: Fedora 23 Final | Component: other Keywords: | Blocked By: Blocking: | -----------------------------+------------------------ Current as I understand it, we have a "two week" process for images (cloud, ISO etc.), but the OSTree commits are made at the default Fedora at-most-once-a-day cadence. I would like to propose doing only one released OSTree commit matching the two week release. Meaning `atomic host upgrade` would exactly what the images give. The advantage of this is predictability. NOTE: we need an exception for critical async security errata. The /testing/ ref though would continue at its current rate - and ideally go even faster. I would be a lot happier if we skipped the manual once-a-day RPM signing and did direct Koji -> /testing/. -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6313> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 17

#6195: Signed commits for ostree / Project Atomic
by Fedora Release Engineering 03 Oct '16

03 Oct '16

#6195: Signed commits for ostree / Project Atomic -----------------------------+------------------------ Reporter: mattdm | Owner: rel-eng@… Type: enhancement | Status: new Milestone: Fedora 23 Alpha | Component: other Keywords: | Blocked By: Blocking: | -----------------------------+------------------------ As Atomic moves from experimental to something users will actually depend on, we need to get this right. It's my understanding that the current workflow doesn't make it easy (the signing needs to happen in a place different from what we're used to). I don't know the specifics, but as Dennis says, "we should figure something out. I just do not know what a good answer is". The same thing might let us also sign RPM repo metadata. -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6195> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 2

#6267: sign ostree commits
by Fedora Release Engineering 03 Oct '16

03 Oct '16

#6267: sign ostree commits -----------------------------+------------------------ Reporter: walters | Owner: rel-eng@… Type: task | Status: new Milestone: Fedora 23 Final | Component: koji Keywords: | Blocked By: Blocking: | -----------------------------+------------------------ This has been discussed several times. AIUI it is blocked on a Fedora policy of not doing detached signatures. As downstream Red Hat Enterprise Linux and its associated PST are OK with detached signatures, I think Fedora should as well. The GPG signature would have helped mitigate https://git.fedorahosted.org/cgit/spin- kickstarts.git/commit/?id=1e408e111008f539c89212a9ca9bb955e2c4f823 for example. -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6267> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 11

#6350: integrate atomic (host and other) CI/CD into Fedora
by Fedora Release Engineering 02 Oct '16

02 Oct '16

#6350: integrate atomic (host and other) CI/CD into Fedora -----------------------------+------------------------ Reporter: walters | Owner: rel-eng@… Type: task | Status: new Milestone: Fedora 24 Alpha | Component: other Keywords: | Blocked By: Blocking: | -----------------------------+------------------------ Breaking out from: https://fedorahosted.org/rel-eng/ticket/6313 Let's define a system and process for CD (Continuous Delivery) that bypasses manual integration via Koji/Bodhi and ships as quickly as possible to a small audience on dl.fedoraproject.org. Specifically, use rpmdistro-gitoverlay to mirror upstream sources that we know have been peer reviewed already, and build/ship them automatically. Also generate a devel/ ostree ref based on this content, and potentially images. Integrate pull request testing into this too. Resources required: - OpenStack tenant resources - Ability to write to dl.fedoraproject.org somewhere -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6350> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 9

#6304: ability to test spin-kickstars by doing throw away image builds in koji
by Fedora Release Engineering 12 Sep '16

12 Sep '16

#6304: ability to test spin-kickstars by doing throw away image builds in koji -----------------------------+------------------------ Reporter: dustymabe | Owner: rel-eng@… Type: task | Status: new Milestone: Fedora 23 Final | Component: koji Keywords: | Blocked By: Blocking: | -----------------------------+------------------------ It would be nice to be able to create image builds in koji that are throw away builds that are purely used for testing of changes to kickstart files etc.. The idea is that we would use these as a way to test our changes before officially commiting them to the spin-kickstarts repo. Having this ability would mean it is much easier for contributors to test changes and thus more likely to submit fixes and or suggestions back. We can currently do an image build on our own machines but it does take some setup and it is not the same environment as the one in koji. So, while we can test on our own machines, is it a valid test? Not really. I would love this functionality. I know it might not technically be possible right now to do, but we shouldn't ignore its value and should perhaps take steps to get there. -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6304> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 12

#6200: Cannot mirror Fedora drpms using OpenAFS
by Fedora Release Engineering 27 Jun '16

27 Jun '16

#6200: Cannot mirror Fedora drpms using OpenAFS -----------------------------+------------------------ Reporter: tc01 | Owner: rel-eng@… Type: task | Status: new Milestone: Fedora 22 Final | Component: other Keywords: meeting | Blocked By: Blocking: | -----------------------------+------------------------ I had (mistakenly) filed this against infrastructure: https://fedorahosted.org/fedora-infrastructure/ticket/4798 To summarize: we'd like to run a Fedora mirror in an OpenAFS cell, but the drpms/ directory is far larger than the 64K slot limit in OpenAFS and, as a result, cannot mirror them. We are currently just excluding the drpms, which works, but I'd like to be able to mirror them if possible. A couple of possible fixes are mentioned in the discussion on that ticket; keeping fewer drpms, or organizing the drpms into alphabetical subdirectories instead of one giant drpms/ directory. How does rel-eng feel about this? Is this something that could be fixed in some way or should we merely continue to exclude the drpms? Thanks in advance. -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6200> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 6

#6333: delete errant rhos-8.0-rhel-7 from erlang dist-git
by Fedora Release Engineering 27 Jun '16

27 Jun '16

#6333: delete errant rhos-8.0-rhel-7 from erlang dist-git ----------------------+------------------------ Reporter: jeckersb | Owner: rel-eng@… Type: task | Status: new Milestone: | Component: git Keywords: | Blocked By: Blocking: | ----------------------+------------------------ I accidentally pushed a rhos-8.0-rhel-7 branch to the fedora remote on the erlang repo, and the commit hook won't let me delete it by pushing an empty ref overtop. Please delete this branch manually (or better, tell me how to delete it if I can do it myself! http://pkgs.fedoraproject.org/cgit/rpms/erlang.git/log/?h=rhos-8.0-rhel-7 Thanks! -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6333> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 2

#6261: Create secondary release staging SOP
by Fedora Release Engineering 27 Jun '16

27 Jun '16

#6261: Create secondary release staging SOP -----------------------------+------------------------ Reporter: till | Owner: rel-eng@… Type: task | Status: new Milestone: Fedora 23 Final | Component: other Keywords: | Blocked By: Blocking: | -----------------------------+------------------------ Should be similar to the one for primary I guess: https://fedoraproject.org/wiki/Stage_final_release_for_mirrors It came up when I noticed that the CHECKSUM files for secondary test releases are not signed: https://dl.fedoraproject.org/pub/fedora- secondary/releases/test/23_Alpha/Server/ppc64le/iso/Fedora-Server-23 -ppc64le-CHECKSUM -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6261> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 1

#6289: Add license information to new sphinx docs
by Fedora Release Engineering 10 Apr '16

10 Apr '16

#6289: Add license information to new sphinx docs -----------------------------+------------------------ Reporter: till | Owner: rel-eng@… Type: task | Status: new Milestone: Fedora 22 Final | Component: other Keywords: | Blocked By: Blocking: | -----------------------------+------------------------ With the conversion from the wiki to sphinx, the license information of the content got lost. The wiki contains the statement {{{Content is available under Attribution-Share Alike 3.0 Unported unless otherwise noted.}}}. -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6289> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 3

#6334: script needed for openh264
by Fedora Release Engineering 22 Mar '16

22 Mar '16

#6334: script needed for openh264 -----------------------------+------------------------ Reporter: ausil | Owner: rel-eng@… Type: task | Status: new Milestone: Fedora 24 Alpha | Component: koji Keywords: | Blocked By: Blocking: | -----------------------------+------------------------ a basic outline of the steps needed koji move-pkg <source tag> <dest-tag> list the latest rpms in the tag sign the rpms something like "NSS_HASH_ALG_SUPPORT=+MD5 sigul sign-rpms --v3-signature --store-in-koji fedora-24 /mnt/koji/packages/openh264/1.5.2/0.3.git21e44bd.fc24/*/*rpm -o tmp/signed/" import the signatures into koji "koji import-sig tmp/signed/*" write out the signed rpms mash the repo sign the repo metadata tar up the repo create email attching the tarball and send it to the folks over at cisco. -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6334> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 2

#6286: Please sign all RC and TC images
by Fedora Release Engineering 19 Mar '16

19 Mar '16

#6286: Please sign all RC and TC images -------------------------+------------------------ Reporter: genodeftest | Owner: rel-eng@… Type: enhancement | Status: new Milestone: | Component: koji Keywords: | Blocked By: Blocking: | -------------------------+------------------------ Current situation: TC and RC images are provided on an server that does not force encryption ( http://dl.fedoraproject.org/pub/alt/stage/ ) and does not provide any signatures (see e.g. http://dl.fedoraproject.org/pub/alt/stage/23_RC10/Workstation/x86_64/iso/ ). Attacker model: * many government intelligence agencies including (but not limited to) NSA and GCHQ * some companies * criminals have an interest to intrude PCs of most people in the world. Especially testers (often software developers themselves) are at risk for being attacked since they are a high-value target for redistributing malware. Having unsigned software to download is one way to make this possible. Please provide Signatures for all RC and TC images in the future. -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6286> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 10

#6339: Please drop epel-rpm-macros from buildsys group
by Fedora Release Engineering 18 Mar '16

18 Mar '16

#6339: Please drop epel-rpm-macros from buildsys group -----------------------------+------------------------ Reporter: remi | Owner: rel-eng@… Type: task | Status: new Milestone: Fedora 24 Alpha | Component: koji Keywords: | Blocked By: Blocking: | -----------------------------+------------------------ This package brings a very low benefit and create very bad issues. Broken SCL build: https://bugzilla.redhat.com/1301358 Even if SCL are not allowed in Fedora, this is a huge blocker for some of us (working on RHSCL or CentOS-SCL) More, the spec file in EPEL can now be incompatible with RHEL / CentOS build system (where these macros don't exists). If really you want such things, please open a RH bug to have them include upstream. Having such workaround only in EPEL seems a terrible bad idea. -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6339> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 5

#6262: drop rawhide-stable tag and consider master branch to be always stable
by Fedora Release Engineering 10 Mar '16

10 Mar '16

#6262: drop rawhide-stable tag and consider master branch to be always stable -------------------------+------------------------ Reporter: till | Owner: rel-eng@… Type: enhancement | Status: new Milestone: | Component: other Keywords: meeting | Blocked By: Blocking: | -------------------------+------------------------ Since we require patch reviews for the rel-eng pagure repo and use it for running buildbranched/buildrawhide, we can IMHO drop using the rawhide- stable tag and just consider the master branch to be always stable enough to run the scripts from it directly. AFAICS only ansible needs to be adjusted to change the crontab to not checkout rawhide-stable but master for primary and secondaries systems. -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6262> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 2

#6346: Don't include 32-bit krb5-server{,-ldap} in 64-bit trees
by Fedora Release Engineering 10 Mar '16

10 Mar '16

#6346: Don't include 32-bit krb5-server{,-ldap} in 64-bit trees -----------------------------+------------------------ Reporter: rharwood | Owner: rel-eng@… Type: task | Status: new Milestone: Fedora 24 Alpha | Component: mash Keywords: | Blocked By: Blocking: | -----------------------------+------------------------ The plugins in krb5-server and krb5-server-ldap are only used by the KDC, so there's no point in including versions of them that don't match architecture of the KDC binary. To that end, could we stop distributing the 32bit version of krb5-server and krb5-server-ldap (i.e. krb5-server.i686, krb5-server.s390, krb5-server.ppc) in the 64-bit tree? Thanks! -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6346> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 1

#6342: Broken dependencies - stable release not in repository after 5 days
by Fedora Release Engineering 03 Mar '16

03 Mar '16

#6342: Broken dependencies - stable release not in repository after 5 days ---------------------+------------------------ Reporter: ondrejj | Owner: rel-eng@… Type: defect | Status: new Milestone: | Component: koji Keywords: | Blocked By: Blocking: | ---------------------+------------------------ According to bodhi, python-configargparse package should be in stable repository 2 days ago and has been released 5 days ago, but still not in testing and/or stable repositories for Fedora 23. https://bodhi.fedoraproject.org/updates/FEDORA-2016-291dc1c23f [root@work ~]# dnf --disablerepo=\* --enablerepo=updates --enablerepo =updates-testing list python2-configargparse Last metadata expiration check performed 0:31:50 ago on Wed Jan 27 09:19:09 2016. Installed Packages python2-configargparse.noarch 0.9.3-3.fc23 @updates [root@work ~]# Should be version 0.10. -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6342> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 2

#6302: Please whitelist nosync for multilib
by Fedora Release Engineering 03 Mar '16

03 Mar '16

#6302: Please whitelist nosync for multilib ----------------------+------------------------ Reporter: msimacek | Owner: rel-eng@… Type: task | Status: new Milestone: | Component: mash Keywords: | Blocked By: Blocking: | ----------------------+------------------------ nosync is a small library used by mock. It is installed in /usr/lib/nosync/nosync.so, because it's supposed to be used only via LD_PRELOAD (mock first copies it to buildroot). It seems that mash doesn't recognize it as multilib, because it's not in standard library location. Could it be whitelisted for being multilib? See also: https://bugzilla.redhat.com/show_bug.cgi?id=1283736 -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6302> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 2

#6353: Please add Astronomy Spin
by Fedora Release Engineering 01 Mar '16

01 Mar '16

#6353: Please add Astronomy Spin -----------------------------+------------------------ Reporter: lupinix | Owner: rel-eng@… Type: task | Status: new Milestone: Fedora 24 Alpha | Component: koji Keywords: | Blocked By: Blocking: | -----------------------------+------------------------ The Astronomy Spin was proposed and accepted as a change for Fedora 24: https://fedoraproject.org/wiki/Changes/Astronomy_Spin As the kickstart should be ready (fedora-live-astronomy_kde.ks in spin-kickstarts git repo) I request to add it to the nightly composes and include it into the Fedora 24 release process. Do you need any additional info? Thank you very much in advance :) -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6353> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 1

[Fedocal] Reminder meeting : Fedora Release Engineering
by Dennis Gilmore 29 Feb '16

29 Feb '16

Dear all, You are kindly invited to the meeting: Fedora Release Engineering on 2016-02-29 from 10:30:00 to 11:30:00 US/Central 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/

2 1

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

rel-eng February 2016