#4187: F12 ppc/ppc64 buildroot brooken due to jna-3.2.7-5.fc12
by Fedora Release Engineering
#4187: F12 ppc/ppc64 buildroot brooken due to jna-3.2.7-5.fc12
--------------------+-------------------------------------------------------
Reporter: ellert | Owner: rel-eng(a)lists.fedoraproject.org
Type: task | Status: new
Milestone: | Component: koji
Keywords: |
--------------------+-------------------------------------------------------
The jna-3.2.7-5.fc12 has wrongfully disabled the build on ppc and ppc64,
which was present in the previous version jna-3.2.4-3.fc12.
This causes broken buildroots for java packages on F12 ppc and ppc64:
DEBUG util.py:268: netbeans-platform-6.7.1-2.fc12.noarch from build has
depsolving problems
DEBUG util.py:268: --> Missing Dependency: jna >= 3.0.9 is needed by
package netbeans-platform-6.7.1-2.fc12.noarch (build)
DEBUG util.py:268: Error: Missing Dependency: jna >= 3.0.9 is needed by
package netbeans-platform-6.7.1-2.fc12.noarch (build)
Could we get the previous version back in the buildroot until the
maintainer fixes this so that other packages can by built.
See also: https://bugzilla.redhat.com/show_bug.cgi?id=640005
Looking in koji it looks like someone tried to fix it, but that that build
suffered from the same broken buildroot problem:
http://koji.fedoraproject.org/koji/buildinfo?buildID=198491
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/4187>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
13 years, 7 months
#4190: jna buildroot override request
by Fedora Release Engineering
#4190: jna buildroot override request
---------------------+------------------------------------------------------
Reporter: lfarkas | Owner: rel-eng(a)lists.fedoraproject.org
Type: task | Status: new
Milestone: | Component: koji
Keywords: |
---------------------+------------------------------------------------------
the previous version of jna that had a ppc build (jna-3.2.4-3.fc12) should
be tagged into the F12 buildroot as a buildroot override, since otherwise
i can't build newer jna version with this older jna version satisfying the
needed dependency from
netbeans-platform.
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/4190>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
13 years, 7 months
Re: #4167: Create Final Release Candidate (RC): Spins
by Fedora Release Engineering
#4167: Create Final Release Candidate (RC): Spins
------------------------------+---------------------------------------------
Reporter: jkeating | Owner: rel-eng(a)lists.fedoraproject.org
Type: task | Status: new
Milestone: Fedora 14 Final | Component: other
Resolution: | Keywords: release-task
------------------------------+---------------------------------------------
Changes (by robatino):
* cc: adamwill, rhe, robatino (added)
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/4167#comment:1>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
13 years, 7 months
Creating QA test images -- SOP?
by James Laska
Greetings folks,
I've noticed that the QA test images created by rel-eng are layed out
differently on the server depending on who creates the images. This
isn't something that users of the ISO images see, but I was curious if
this indicated a process document (or SOP) was in need of update to
ensure that images are created in a consistent format each milestone for
mirrors. For example ...
One format ...
* /pub/alt/stage/14.TC1/$basearch/${os,iso}
* /pub/alt/stage/branched-9-2.1/$basearch/{os,iso}
* /pub/alt/stage/rawhide-testing/$basearch/{os,iso}
Another format (includes "Fedora" flavor in path) ...
* /pub/alt/stage/14-Beta.RC3/Fedora/$basearch/${os,iso}
* /pub/alt/stage/14-Alpha.RC3/Fedora/$basearch/${os,iso}
Not a big difference of course, I recognized the difference while
updating my script which monitors for, and downloads ISOs (which may
eventually be used by AutoQA).
What is the expected path for the images?
/pub/alt/stage/%{name}/%{flavor}/%{basearch} ?
* Where name is something like, "$version-$milestone-$count" ?
* Where flavor in [Fedora, Live]
Thanks,
James
13 years, 7 months
Fedora 14 Schedule
by John Poelstra
*REMINDER*
The Final Test Compose is scheduled for this coming TUESDAY, not the
traditional Thursday to align with the adjusted final freeze and final
RC compose dates for Fedora 14
Start End Name
Mon 11-Oct Mon 11-Oct Submit Installer Builds for Final TC Compose
Mon 11-Oct Fri 15-Oct Daily Review & Notification of Open Final
Blocker Bugs
Tue 12-Oct Tue 12-Oct Create 'Final' Test Compose (TC)
Fri 15-Oct Fri 15-Oct Final Blocker Meeting (f14blocker) #4
Mon 18-Oct Mon 18-Oct Final Change Deadline
Mon 18-Oct Mon 18-Oct Final Blocker Meeting (f14blocker)--Blocks RC
Compose
Mon 18-Oct Mon 18-Oct Submit Installer Builds for Final RC Compose
Tue 19-Oct Thu 21-Oct Compose 'Final' RC
Tue 19-Oct Tue 02-Nov Final Infrastructure Change Freeze
Wed 20-Oct Wed 20-Oct Enable Fedora 14 Updates
Thu 21-Oct Thu 21-Oct Deliver RC to QA for Testing
Tue 26-Oct Tue 26-Oct Fedora 14 Final Go/No-Go Meeting (17:00 US Eastern)
13 years, 7 months
Re: #4186: Create tickets and plan tasks for EOL
by Fedora Release Engineering
#4186: Create tickets and plan tasks for EOL
------------------------------+---------------------------------------------
Reporter: jkeating | Owner: rel-eng(a)lists.fedoraproject.org
Type: task | Status: new
Milestone: Fedora 14 Final | Component: other
Resolution: | Keywords: release-task
------------------------------+---------------------------------------------
Changes (by jkeating):
* summary: Create tickets and paln tasks for EOL => Create tickets and
plan tasks for EOL
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/4186#comment:1>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
13 years, 7 months