#4791: install of buildroot failed but install started
----------------------+-----------------------------------------------------
Reporter: mmaslano | Owner: rel-eng(a)lists.fedoraproject.org
Type: task | Status: new
Milestone: | Component: koji
Keywords: |
----------------------+-----------------------------------------------------
The installation of buildroot failed, see:
http://koji.fedoraproject.org/koji/getfile?taskID=3149029&name=root.log
But build phase started, see:
http://koji.fedoraproject.org/koji/getfile?taskID=3149029&name=build.log
I'd like to point out that this bug is serious. Imagine, that you have
package in C, which is checking by configure installed packages. In
buildroot they are missing, but install could be successful because
configure detect available packages and use available. Therefore you can
have in specfile --with-selinux, but build could be done without SElinux
support.
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/4791>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
#4823: Buildroot overrides for bouncycastle-mail-1.46-1.el6
---------------------+------------------------------------------------------
Reporter: s4504kr | Owner: rel-eng(a)lists.fedoraproject.org
Type: task | Status: new
Milestone: | Component: koji
Keywords: |
---------------------+------------------------------------------------------
I want to request a buildroot overirdes for the package bouncycastle-
mail-1.46-1.el6 to the dist-6E-epel tag
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/4823>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
#4786: update mock in koji
----------------------+-----------------------------------------------------
Reporter: mmaslano | Owner: rel-eng(a)lists.fedoraproject.org
Type: task | Status: new
Milestone: | Component: koji
Keywords: |
----------------------+-----------------------------------------------------
Could you please update to new mock 1.1.11? It does solve build failures
with pty/tty devices.
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/4786>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
#4056: Update sigul systems
----------------------+-----------------------------------------------------
Reporter: jkeating | Owner: rel-eng(a)lists.fedoraproject.org
Type: task | Status: new
Milestone: | Component: other
Keywords: |
----------------------+-----------------------------------------------------
there is new python-nss stuff we should built up and look at. Might also
setup a staging environment on el6 and see if things work (better?) there.
Also need to make a change to the user environment so that v3 sigs are
preferred by default.
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/4056>
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
#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
#4714: Release Final: Update PackageDB to point to the release repos for the App
DB
-----------------------------+----------------------------------------------
Reporter: ausil | Owner: rel-eng(a)lists.fedoraproject.org
Type: task | Status: new
Milestone: Fedora 15 Final | Component: koji
-----------------------------+----------------------------------------------
Release Final: Update PackageDB to point to the release repos for the App
DB
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/4714>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project