#3802: Symlink for latest branched and rawhide mash
--------------------+-------------------------------------------------------
Reporter: jlaska | Owner: rel-eng(a)lists.fedoraproject.org
Type: task | Status: new
Milestone: | Component: mash
Keywords: |
--------------------+-------------------------------------------------------
== Problem Space ==
Currently, the [http://fedoraproject.org/wiki/Critical_Path_Packages
Critical Path Packages] wiki page links to most recently branched and
rawhide critpath.txt files. However, depending on the status of the
compose/mash/pungi, or the timing of the branched schedule, these log
files may not be available. In order to eliminate confusion and 404 links
from the wiki, it would be helpful to provide a link to an ''always''
available critpath.log URL.
== Proposal ==
Create a symlink for the latest successful branched and rawhide
pungi/mash/compose. This symlink will be referenced when directing users
to the latest definition of the critical path. For example:
* http://kojipkgs.fedoraproject.org/mash/rawhide-latest ->
http://kojipkgs.fedoraproject.org/mash/rawhide-20100618/
* http://kojipkgs.fedoraproject.org/mash/branched-latest ->
http://kojipkgs.fedoraproject.org/mash/branched-20100518/
The symlink would be updated upon successful mashing of rawhide or
branched.
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/3802>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
#5109: Change live media dirs to i386 to avoid confusion
----------------------------+------------------------
Reporter: kevin | Owner: rel-eng@…
Type: task | Status: new
Milestone: Fedora 17 Beta | Component: koji
Keywords: | Blocked By:
Blocking: |
----------------------------+------------------------
See: https://fedorahosted.org/fesco/ticket/602
We would like to change the dir that live media are in from i686 to i386,
and the iso images themselves to be i386 instead of i686.
This would reflect that they are all 32bit images.
If there's some reason we shouldn't/can't do this, feel free to reopen the
fesco ticket for more discussion.
Thanks.
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5109>
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
#4987: Not able to mark fedora-review as '+' in bugzilla
--------------------+-------------------------------------------------------
Reporter: mmorsi | Owner: rel-eng(a)lists.fedoraproject.org
Type: task | Status: new
Milestone: | Component: other
Keywords: |
--------------------+-------------------------------------------------------
I have approved two packages for Fedora in bugzilla, rubygem-idn and
rubygem-addressable but am not able to select '+' as an option for the
fedora-review field. This has worked for me in the past and I was
wondering if anything was changed / broken and if anything had to be done
to resolve this.
https://bugzilla.redhat.com/show_bug.cgi?id=728088https://bugzilla.redhat.com/show_bug.cgi?id=588428
Thank you greatly.
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/4987>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
#5008: problem setting cvs flag - new package request
------------------+------------------------
Reporter: jcm | Owner: rel-eng@…
Type: task | Status: new
Milestone: | Component: git
Keywords: | Blocked By:
Blocking: |
------------------+------------------------
NOTE: Trying to get this out in time for the holidays so folks can test :)
Hello everyone!
I have a new package request that has been reviewed, and I've added the
SCM boilerplate text:
https://bugzilla.redhat.com/show_bug.cgi?id=769832
I can't set the flag for you to review for some reason. Could you look
into fixing this for me? This package will replace module-init-tools in
a future Fedora release, and I am packaging it and preparing it now. It
is parallel installable at this time, and won't deprecate anything yet
without some co-ordination between everyone who is involved :)
Appreciate any help. I hope to get some initial rawhide packages built
over the holidays if you can resolve getting branches setup.
Jon.
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5008>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
#5045: Remove junk branches
--------------------+------------------------
Reporter: ellert | Owner: rel-eng@…
Type: task | Status: new
Milestone: | Component: git
Keywords: | Blocked By:
Blocking: |
--------------------+------------------------
Hi.
I seem to have managed to create new remote branches for two of my
packages. I don't know how it happened - I probably misspelled something
and didn't notice at the time.
I have tried to figure out how to remove them, but have not been
successful.
Could I ask for someone to remove them, or tell me the right commands so
that I can do it myself?
The branches are called "15" and "16" (without the f) in the packages
globus-io and globus-gridftp-server-control.
Mattias
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5045>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
#4682: need empty updates-debuginfo repos created too
---------------------+------------------------------------------------------
Reporter: mdomsch | Owner: rel-eng(a)lists.fedoraproject.org
Type: task | Status: new
Milestone: | Component: other
Keywords: |
---------------------+------------------------------------------------------
At the branchpoint, the rel-eng SOP includes creating empty
updates/{newversion}/{arch}/ repositories, and creating empty
updates/testing/{newversion}/{arch}/ repositories. However, corresponding
debuginfo repositories in updates/ are not created, while they are in
updates/testing/.
updates/testing/15/SRPMS/repodata
updates/testing/15/i386/debug/repodata
updates/testing/15/i386/repodata
updates/testing/15/x86_64/debug/repodata
updates/testing/15/x86_64/repodata
updates/15/i386/repodata
updates/15/SRPMS/repodata
updates/15/x86_64/repodata
MirrorManager returns an (empty) metalink document for non-existant
requested repositories. Yum requests these debuginfo repositories as well,
and doesn't like it when it gets back this (empty) metalink document. See
bug https://bugzilla.redhat.com/show_bug.cgi?id=679783
Please adjust the SOP to ensure that empty
updates/{newversion}/{arch}/debug/ repositories are created at the same
time updates/{newversion}/{arch} repositories are created.
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/4682>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project