#1107: auto-cleanup rawhide trees
-------------------------+--------------------------------------------------
Reporter: notting | Owner: rel-eng(a)lists.fedoraproject.org
Type: enhancement | Status: new
Milestone: | Component: koji
Keywords: |
-------------------------+--------------------------------------------------
Rawhide tree expiry is manual at the moment, unless I missed something.
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/1107>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
#2025: Too hard to build dependent packages in stable
-------------------------+--------------------------------------------------
Reporter: hadess | Owner: rel-eng(a)lists.fedoraproject.org
Type: enhancement | Status: new
Milestone: | Component: koji
Keywords: |
-------------------------+--------------------------------------------------
It's too complicated, human-dependent, and time-consuming to build
interdependent package updates in stable releases.
Two cases:
* gstreamer and gstreamer-plugins-base are released at the same time, and
so are pre-releases of those. They soft-depend on each other (gstreamer
can be updated on its own). It's currently not possible for me to offer
both pre-releases of gstreamer and gsteamer-plugins-base without either:
1. asking for a package to be tagged into the build roots
2. pushing gstreamer into stable (takes a few days at best), and push the
gstreamer-plugins-base package separately
* gnome-bluetooth and gnome-phone-manager, where I need to ask for gnome-
bluetooth to be pushed into the buildroot tree. Sometimes that just
doesn't work (as could have been seen in
http://admin.fedoraproject.org/updates/F11/FEDORA-2009-7140 /
https://fedorahosted.org/rel-eng/ticket/1945 and
http://koji.fedoraproject.org/koji/buildinfo?buildID=112091 )
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/2025>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
#859: updates-newkey doesn't have group_gz member
-------------------------------------+--------------------------------------
Reporter: james(a)fedoraproject.org | Owner: rel-eng(a)lists.fedoraproject.org
Type: task | Status: new
Milestone: | Component: koji
Keywords: |
-------------------------------------+--------------------------------------
I assume the createrepo instance that generates the Fedora 9 updates-
newkey/updates-testing-newkey is the RHEL-5 version?
Can we change this to be the Fedora 9 version so that we'll get group_gz
as well as group (ie. comps.xml.gz as well as comps.xml). This makes for
much less data to download, to get group information.
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/859>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
#1939: New wine subpackages which need to be copied to x86_64
------------------+---------------------------------------------------------
Reporter: awjb | Owner: rel-eng(a)lists.fedoraproject.org
Type: task | Status: new
Milestone: | Component: koji
Keywords: |
------------------+---------------------------------------------------------
There will be two more subpackages for wine which need to be copied to the
x86_64 repo (see
https://koji.fedoraproject.org/koji/taskinfo?taskID=1427810)
wine-alsa
wine-oss
Please adjust the scripts accordingly. Thanks!
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/1939>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
#2012: Build root isolation
----------------------+-----------------------------------------------------
Reporter: stransky | Owner: rel-eng(a)lists.fedoraproject.org
Type: task | Status: new
Milestone: | Component: koji
Keywords: |
----------------------+-----------------------------------------------------
Please isolate buildroot from
http://koji.fedoraproject.org/koji/taskinfo?taskID=1534857
I need to check the build error (It's produced by koji only, local builds
went fine).
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/2012>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
#1960: include distro and content tags in repomd.xml
---------------------+------------------------------------------------------
Reporter: skvidal | Owner: rel-eng(a)lists.fedoraproject.org
Type: task | Status: new
Milestone: | Component: koji
Keywords: |
---------------------+------------------------------------------------------
In recentish (f10 and up) createrepos you can include distro and content
tags in the repomd.xml. This lets you specify what distro the repo is for
and what content the repo has (updates, source, debuginfo, i386, etc, etc)
We should get see about adding this.
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/1960>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
#106: F9 Postmortem follow-up
-------------------------------------------------+--------------------------
Reporter: John Poelstra <poelstra(a)redhat.com> | Owner: rel-eng(a)lists.fedoraproject.org
Type: task | Status: new
Milestone: | Component: koji
-------------------------------------------------+--------------------------
{{{
Here are some ideas that came out of an internal meeting for Fedora 10
1) Reduce the number of manual steps necessary to compose a
release--Jesse should not have to stay up all night to get the release
out the door
a) enumerate current steps
b) identify steps that can be reduced
c) target steps to be reduced for Fedora 10
d) expand existing documentation so that more people can participate
in compose process
2) Build system enhancements (plague) and make it less fragile
3) Finish pyjigdo so hand-editing of jigdo files isn't necessary
4) Finish signing server
5) Integrate delta packages as early as possible in cycle--complete
integration with build system
6) Automated tree validation after compose (dgregor's checktree and
treediff scripts as a short-term solution?)
7) More focus on secondary architectures working
8) More days of "installable rawhide"
a) tooling?
b) easy way to collect metrics?
}}}
--
Ticket URL: <http://fedorahosted.org/rel-eng/ticket/106>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
#2022: Request buildroot overrides for ghc-editline on koji for F-11 and F-10
---------------------+------------------------------------------------------
Reporter: s4504kr | Owner: rel-eng(a)lists.fedoraproject.org
Type: task | Status: new
Milestone: | Component: koji
Keywords: |
---------------------+------------------------------------------------------
Hallo,
I want to create an update which contains the packages kaya and the
new dependency ghc-editline.
Unfortunately, I can't make a build on koji for F-11 and F-10 because the
package ghc-editline-devel is unknown for koji.
On #fedora-devel I have got the adive to request a so called buildroot
overrides.
It will be nice, if you can help me.
Best Regards:
Jochen Schmitt
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/2022>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
#2003: Need F11 build root update
----------------------+-----------------------------------------------------
Reporter: dledford | Owner: rel-eng(a)lists.fedoraproject.org
Type: task | Status: new
Milestone: | Component: koji
Keywords: |
----------------------+-----------------------------------------------------
I need libibumad-1.3.2-2.fc11 put into the build root.
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/2003>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project