#4883: unblock scantailor for rawhide
--------------------+-------------------------------------------------------
Reporter: xhorak | Owner: rel-eng(a)lists.fedoraproject.org
Type: task | Status: new
Milestone: | Component: koji
Keywords: |
--------------------+-------------------------------------------------------
package scantailor was blocked for rawhide, I'd like to have it unblocked
to supply updates for this package.
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/4883>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
#3740: fix critpath generation to be per branch and properly import into pkgdb
---------------------+------------------------------------------------------
Reporter: notting | Owner: rel-eng(a)lists.fedoraproject.org
Type: task | Status: new
Milestone: | Component: koji
Keywords: |
---------------------+------------------------------------------------------
As I understand it, critical path generation should work like this:
{{{
* Lists are generated at rawhide, branched, or updates compose time
* These lists are synced into pkgdb for that branch
* bodhi then reads these from pkgdb
}}}
Where are we currently? For the first item, we only generate critpath
during rawhide/branched compose.
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/3740>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
#4988: Package not being pushed to updates-testing
--------------------+-------------------------------------------------------
Reporter: dbhole | Owner: rel-eng(a)lists.fedoraproject.org
Type: defect | Status: new
Milestone: | Component: koji
Keywords: |
--------------------+-------------------------------------------------------
Hi,
https://admin.fedoraproject.org/updates/FEDORA-2011-16438/icedtea-
web-1.1.4-3.fc16 says that the update was pushed to updates-testing on the
25th. However I don't see it on any of the mirrors even though those
mirrors seem to have items on them that were pushed after the 25th.
Is this a bug, or just expected delay?
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/4988>
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
#4722: Create tickets and plan tasks for EOL
-----------------------------+----------------------------------------------
Reporter: ausil | Owner: rel-eng(a)lists.fedoraproject.org
Type: task | Status: new
Milestone: Fedora 15 Final | Component: koji
-----------------------------+----------------------------------------------
Create tickets and plan tasks for EOL
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/4722>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
#4719: Propose Schedule for Next Release
-----------------------------+----------------------------------------------
Reporter: ausil | Owner: rel-eng(a)lists.fedoraproject.org
Type: task | Status: new
Milestone: Fedora 15 Final | Component: koji
-----------------------------+----------------------------------------------
Propose Schedule for Next Release
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/4719>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
#4994: Make it clear in releng SOPs that branching must be complete prior to Alpha
compose
----------------------+-----------------------------------------------------
Reporter: adamwill | Owner: rel-eng(a)lists.fedoraproject.org
Type: task | Status: new
Milestone: | Component: other
Keywords: |
----------------------+-----------------------------------------------------
I'm working through the F16 QA retrospective:
https://fedoraproject.org/wiki/Fedora_16_QA_Retrospective
One of the notes there from jlaska reads:
jlaska - Alpha branch - Unclear when the F16 branch was completed as not
all tasks in the Mass_Branching_SOP were completed. The SOP either needs
to be followed or updated.
MirrorManager was not updated to add a fedora-16 repo tag, therefore,
TC1 installations could not find a repository to install from (RHBZ
#727428)
TC1 images were built with Version=16-Alpha.TC1 specified as the
--version argument to pungi. This results in a file /.buildstamp in the
install image with an incorrect version (Version=16-Alpha.TC1) that is
used as the $releasever variable for yum. The net result is that there are
no yum repos that match repo=16-Alpha.TC1&arch=x86_64. The version needs
to be an integer, or MirrorManager redirects need to be established prior
to compose.
The fedora-release package was not properly updated to include
[fedora] with enabled=1. As a result, TC1 images included a fedora-release
package that didn't enable the Fedora 16 repos.
The fedora-release package was not updated to include the Fedora 16
release name Verne. This is a minor issue, but results in login prompts
claiming the system is Rawhide. Recommend updating (or creating) the
existing Mass_Branching_SOP to document expected results when updating
fedora-release
adamw - seems branching may not actually have been completed by time
of TC1 delivery, even. Perhaps appropriate releng SOPs should be updated
to clarify that branching - or at least some specified subset of branching
tasks - must be completed before Alpha TC1 delivery
Due to all of those issues, it seems like releng should have an SOP for
all the various tasks involved in branching, and the relationships between
releng SOPs should make it clear that all the branching tasks have to be
completed before an Alpha compose is attempted.
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/4994>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
#5001: Block some GNOME java packages from rawhide
----------------------+---------------------------------------------
Reporter: nsoranzo | Owner: rel-eng@…
Type: task | Status: new
Milestone: | Component: koji
Keywords: |
----------------------+---------------------------------------------
The following packages are dead upstream, orphaned since F16 and
deprecated for rawhide:
cairo-java
glib-java
libgconf-java
libglade-java
libgnome-java
libgtk-java
libvte-java
The only package still requiring them is frysk.
Please block them from rawhide.
Thanks,
Nicola
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5001>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
#5005: Retire rubygem-multimap
---------------------+---------------------------------------------
Reporter: mmorsi | Owner: rel-eng@…
Type: task | Status: new
Milestone: | Component: koji
Keywords: | Blocking:
Blocked By: |
---------------------+---------------------------------------------
We've received word from the upstream project that it is dead / deprecated
(the one other package depending on it has been updated).
Could you please block further builds on this package starting in rawhide
/ F17.
Thank you
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5005>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project