Changes

Jump to: navigation, search

Fedora/Firefox Repository Setup for Nightly and Beta builds

903 bytes added, 06:15, 12 December 2010
no edit summary
== Project Name ==
Repository Setup for Mozilla Nightlies Nightly and Betas - Firefox Versions (4, 3.6)Beta builds
== Project Description ==
Automating the process of RPM building and repository updates for 32 Bit and 64 Bit Firefox beta and nightly builds on Fedora systems of different architectures. Architectures such as Firefox (4, 3.6) Beta's and Nightlies.
== Project Leaders ==
*Brett van Gennip- bvangennip@learn.senecac.on.ca*Yauheni <s>Eugene Khabian (Eugene MIA) If your still around please contact us.</s> - Removed*Vitalijs Bluzmans- vbluzmans@learn.senecac.on.ca*Tarinur Choudhury- trchoudhury@learn.senecac.on.ca
== Responsibilities ==
* SPEC File Formation & Desktop Integration - Tarinur is Taking this responsibility.
* Repository Configuration - Vitaly
* Testing Minefield with SELinux and Fedora 13 - Brett
*Armen Zambrano Gasparnian
== Project News Details == * Target: Current supported Fedora releases (Fedora 13 and Fedora 14) Approach to packaging:# Pull from a standard URL (as of now http://nightly.mozilla.org/)# Package that binary nightly/beta as an RPM# Add to a repository and regenerate/update metadata Approach to repo access:# Make a repo "release" RPM that provides .repo file and public key Approach to SELinux:# Modify the RPM packaging to setup SELinux appropriately#* File labels and policy need to be managed in the RPM package Installation locations:* Must not conflict with distro-provided install locations* Should be in the standard path* Should start up with a --profile-manager* Should appear in the graphical menus, with a different name than the stable release* Make appear on the GUI menus - Minefield (Firefox nightly) - Firefox (Developer Preview) == Deployment == * Deploy on HW in CDOT initially (Chile)* Deliver scripts to Armen for deployment on Mozilla infrastructure == Release Targets == * 0.1 - Proof of concept* 0.2 - Cleaned-up release* 0.3 - Scripts delivered to Armen == Project Plan == * 0.1 - Proof of concept
* November 6th, 2010Fully working proof of concept including early mock up of nightly RPM and repository installation RPM.
'''=== Progress made on 0.1 Milestone:'''===
Please see our latest blog posts on the status of milestone 0.1. This wiki will feature a brief overview of how the project is progressing.
==== Brett van Gennip - Testing Minefield with SELinux and Fedora 13====
Brett had downloaded Minefield and attempted to replicate the error message that was coming up for people. Overall, he had no success making the error message show up which proved to be a bit of an issue to how he can understand the issue. Certain things came up such as: while running firefox, Minefield would not open. While running Minefield, firefox would not open. At no point was he able to run both at the same time. Overall, he plans to speak with people on IRC to try to make some sense of these issues.
[http://brettvangennip.wordpress.com/2010/11/05/0-1-repository-setup-for-firefox-nightly-and-betas/ Minefield and Firefox]
==== Tarin - RPM Building and Repository Setup====
Tarin had setup the Repository and made it so that you are able to download the nightly via iraq.proximity.on.ca repository. He has also packaged the nightlies in an RPM format. Which means that he has created a SPEC file for the RPM to work with Fedora 1x machines in both 32 bit and 64 bit architectures. Our repository is located at [http://iraq.proximity.on.ca/ffrepo/ Nightly Repository].
[http://tarinc.wordpress.com/2010/11/05/milestone-1-continued/ Milestone 1 Continued]
==== Vitaly - Building Firefox/Fedora Repository====
Vitaly had setup the Repository on one of the servers in Seneca's open source room locations. He had proceeded in creating a script that will automate the process of setting up the repo's into the directory for which they are to be downloaded from.
[http://vbluzmans.wordpress.com/2010/11/05/in-quest-of-building-firefoxfedora-repository/ Building Firefox/Fedora Repo]
* 0.2 - Cleaned-up release
 
Finalize spec files and implement automation.
 
=== Progress made on 0.2 Milestone ===
 
Please see our latest blog posts on the status of milestone 0.2. This wiki will feature a brief overview of how the project is progressing.
 
==== Tarin ====
[http://tarinc.wordpress.com/2010/11/25/release-0-2-update/ Release 0.2 Update]
 
* 0.3 - Scripts delivered to Armen
 
=== Progress made on 0.3 Milestone ===
 
Please see our latest blog posts on the status of milestone 0.3. This wiki will feature a brief overview of how the project is progressing.
 
== Project News ==
 
''' November 12th, 2010 '''
 
- EUGENE IS Back -
 
STATUS:
 
(BRETT)
 
setup a different profile for
 
That i run firefox and minefield together the way i just describe it.
 
what does he want ? can we do it or is the builders Responsibility to figure it out... or does it even matter
 
TARIN > It sounds like it is related to profiles
 
TARIN IS Compiling 32 bit minefield on Chile
TARIN IS Compiling 64 bit minefield on IRAQ
 
Problems :
* REVISIT SPEC FILE - Figure out how to make it more Vitaly - Figure out signing of public keys - password: senecaCdotEugene - make a spec file by the end of the day  '''October 12th 2010 Notes'''
* BUGZILLA - 600317
* '''Day One Notes - October 8th 2010'''
Project:
Repository Setup for Mozilla Nightlies and Betas
--> Problem --> Getting SELinux to work with the nightlies.
 
 
 
== Project Details ==
 
* Target: Current Fedora releases (right now that's
 
Approach to packaging:
# Pull from a standard URL (as of now http://nightly.mozilla.org/) (armenzg-TODO: get fixed URL to latest)
# Package that binary nightly/beta as an RPM
# Add to a repository and regenerate/update metadata
 
Approach to repo access:
# Make a repo "release" RPM that provides .repo file and public key
 
Approach to SELinux:
# Modify the RPM packaging to setup SELinux appropriately
#* File labels and policy need to be managed in the RPM package
 
Installation locations:
* Must not conflict with distro-provided install locations
* Should be in the standard path
* Should start up with a --profile-manager
* Should appear in the graphical menus, with a different name than the stable release
* Make appear on the GUI menus - Minefield (Firefox nightly) - Firefox (Developer Preview)
 
== Deployment ==
 
* Deploy on HW in CDOT initially (which machine?)
* Deliver scripts to Armen for deployment on Mozilla infra
 
== Release Targets ==
 
* 0.1 - Proof of concept
* 0.2 - Cleaned-up release
* 0.3 - Scripts delivered to Armen
 
== Division of Labour ==
 
 
 
== Project Plan ==
 
* 0.1 - Proof of concept
 
Setup any package to be acquired from our repository
Installing the repository VIA an RPM
 
 
* 0.2 - Cleaned-up release
 
Manual creation of the SPEC file with the BETA Version to create a functional RPM
After tested and satisfied with the results TEST with NIGHTLY Packages
 
* 0.3 - Scripts delivered to Armen
1
edit

Navigation menu