Re: #4015: Create Beta Test Compose (TC)
by Fedora Release Engineering
#4015: Create Beta Test Compose (TC)
-----------------------------+----------------------------------------------
Reporter: jkeating | Owner: rel-eng(a)lists.fedoraproject.org
Type: task | Status: new
Milestone: Fedora 14 Beta | Component: other
Resolution: | Keywords: release-task
-----------------------------+----------------------------------------------
Comment (by adamwill):
clarification to my comment: I forgot that 14.17 has an *incorrect* fix
for 627401. So 14.17 is no good for the TC either. We'll need a 14.18
build with the correct 627401 fix.
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/4015#comment:6>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
13 years, 8 months
Re: #4015: Create Beta Test Compose (TC)
by Fedora Release Engineering
#4015: Create Beta Test Compose (TC)
-----------------------------+----------------------------------------------
Reporter: jkeating | Owner: rel-eng(a)lists.fedoraproject.org
Type: task | Status: new
Milestone: Fedora 14 Beta | Component: other
Resolution: | Keywords: release-task
-----------------------------+----------------------------------------------
Comment (by jlaska):
Replying to [comment:4 adamwill]:
> I wasn't aware there were test images that needed testing :/ Obviously
we should have done something to communicate this. Since 627401 will
clearly be a Beta blocker, I'd say we should go with 14.17 for the TC, and
then we can probably get the update approved based on TC testing.
I've supplied the karma needed based on newgle's testing of the pre-beta
anaconda-14.17-1 (see
https://admin.fedoraproject.org/updates/anaconda-14.17-1.fc14). Well done
newgle! :)
However, I am still concerned that we won't get very far beyond the
installer without the fix for bug#627401. I'd prefer having as few
roadblocks in the way of validating systemd operates correctly.
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/4015#comment:5>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
13 years, 8 months
Re: #4015: Create Beta Test Compose (TC)
by Fedora Release Engineering
#4015: Create Beta Test Compose (TC)
-----------------------------+----------------------------------------------
Reporter: jkeating | Owner: rel-eng(a)lists.fedoraproject.org
Type: task | Status: new
Milestone: Fedora 14 Beta | Component: other
Resolution: | Keywords: release-task
-----------------------------+----------------------------------------------
Comment (by adamwill):
I wasn't aware there were test images that needed testing :/ Obviously we
should have done something to communicate this. Since 627401 will clearly
be a Beta blocker, I'd say we should go with 14.17 for the TC, and then we
can probably get the update approved based on TC testing.
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/4015#comment:4>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
13 years, 8 months
Re: #4015: Create Beta Test Compose (TC)
by Fedora Release Engineering
#4015: Create Beta Test Compose (TC)
-----------------------------+----------------------------------------------
Reporter: jkeating | Owner: rel-eng(a)lists.fedoraproject.org
Type: task | Status: new
Milestone: Fedora 14 Beta | Component: other
Resolution: | Keywords: release-task
-----------------------------+----------------------------------------------
Comment (by jkeating):
I'm unclear on what anaconda version we should include in this test
compose. There is a build that is newer than what was in Alpha, and I
created test images for it for QA testing, however it has yet to be marked
stable. Should I include this testing build, a newer build, revert to the
alpha build...?
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/4015#comment:3>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
13 years, 8 months
#4085: Please move nss fc13 Bodhi update testing
by Fedora Release Engineering
#4085: Please move nss fc13 Bodhi update testing
------------------------+---------------------------------------------------
Reporter: emaldonado | Owner: rel-eng(a)lists.fedoraproject.org
Type: task | Status: new
Milestone: | Component: koji
Keywords: |
------------------------+---------------------------------------------------
I added a missing package, nss-util-3.12.7-2.fc13, to the bodhi nss
request:
https://admin.fedoraproject.org/updates/nss-3.12.7-4.fc13,nss-
util-3.12.7-2.fc13,nss-
softokn-3.12.7-3.fc13,nspr-4.8.6-1.fc13?_csrf_token=d4a722c8c5d684369e516bd6b502139fc81cec61
That pushed it back to pending. Could you move it to testing so it get
needed karma and we can have it ready for Firefox 3.6.9? Thanks.
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/4085>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
13 years, 8 months
#4088: Override tag request for rubygem-ruby-debug-base
by Fedora Release Engineering
#4088: Override tag request for rubygem-ruby-debug-base
---------------------+------------------------------------------------------
Reporter: mtasaka | Owner: rel-eng(a)lists.fedoraproject.org
Type: task | Status: new
Milestone: | Component: koji
Keywords: |
---------------------+------------------------------------------------------
Hello.[[BR]]
[[BR]]
I plan to import rubygem-ruby-debug as well as rubygem-ruby-debug-base. As
rubygem-ruby-debug has BR: rubygem-ruby-debug-base, the following packages
need to be in buildroot.[[BR]]
Please make the following pkgs tagged as override, thanks.[[BR]]
[[BR]]
rubygem-ruby-debug-base-0.10.4-0.1.rc1.fc14[[BR]]
rubygem-ruby-debug-base-0.10.4-0.1.rc1.fc13[[BR]]
rubygem-ruby-debug-base-0.10.4-0.1.rc1.fc12[[BR]]
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/4088>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
13 years, 8 months
#4086: Build Root Override: F13, F14
by Fedora Release Engineering
#4086: Build Root Override: F13, F14
---------------------+------------------------------------------------------
Reporter: stahnma | Owner: rel-eng(a)lists.fedoraproject.org
Type: task | Status: new
Milestone: | Component: koji
Keywords: |
---------------------+------------------------------------------------------
Can you add rubygem-shoulda latest build to the BR for override. I would
like to build a package that requires that package.
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/4086>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
13 years, 8 months
#4081: Include rails packages in F14 build root for chain-build
by Fedora Release Engineering
#4081: Include rails packages in F14 build root for chain-build
--------------------+-------------------------------------------------------
Reporter: mmorsi | Owner: rel-eng(a)lists.fedoraproject.org
Type: task | Status: new
Milestone: | Component: koji
Keywords: |
--------------------+-------------------------------------------------------
We are updating to Rails 2.3.8 on F14. There are six packages that need to
be pushed, but can't currently be built due to interdependencies (that is
build dependencies). I've pushed all to the f14-updates git repo, but due
to the following dependencies, fedpkg build is currently failing:
rubygem-activesupport builds fine, doesn't depend on anything thats not
there
rubygem-activerecord depends on activesupport (all dependencies are for
the same version, eg ar-2.3.8 depends on as-2.3.8)
rubygem-activeresource depends on activesupport
rubygem-actionpack depends on both activesupport and activerecord
rubygem-actionmailer depends on actionpack
rubygem-rails depends on all five of the previous rpms
So from what I understand
1. rubygem-activesupport needs to be added to the build root.
2. Then I can build rubygem-activerecord and rubygem-activeresource (is
this a regular build or chain-build?)
3. Then those need to be added to the build root
4. Then I can build rubygem-actionpack
5. Then that can be added to the build root
6. Then I can build rubygem-actionmailer
7. Then that can be added to the build root
8. Then I can build rubygem-rails and submit all the packages to Fedora 14
updates via bodhi
Is this correct? Could someone start by adding activesupport to the build
root so I can build the next two packages. After that shall I continue
using this ticket or open another to add those to the build root? How long
would adding each to the buildroot take (as it needs to be done four
seperate times). Thanks alot.
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/4081>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
13 years, 8 months
Re: #4014: Warn about Beta Freeze
by Fedora Release Engineering
#4014: Warn about Beta Freeze
-----------------------------+----------------------------------------------
Reporter: jkeating | Owner: rel-eng(a)lists.fedoraproject.org
Type: task | Status: closed
Milestone: Fedora 14 Beta | Component: other
Resolution: fixed | Keywords: release-task
-----------------------------+----------------------------------------------
Changes (by jkeating):
* status: new => closed
* resolution: => fixed
Comment:
John sent out the warnings.
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/4014#comment:1>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
13 years, 8 months