Difference between revisions of "Fedora/Firefox Repository Setup for Nightly and Beta builds"
Line 58: | Line 58: | ||
* 0.2 - Cleaned-up release | * 0.2 - Cleaned-up release | ||
* 0.3 - Scripts delivered to Armen | * 0.3 - Scripts delivered to Armen | ||
− | |||
== Project Plan == | == Project Plan == | ||
Line 95: | Line 94: | ||
[http://vbluzmans.wordpress.com/2010/11/05/in-quest-of-building-firefoxfedora-repository/ Building Firefox/Fedora Repo] | [http://vbluzmans.wordpress.com/2010/11/05/in-quest-of-building-firefoxfedora-repository/ Building Firefox/Fedora Repo] | ||
− | |||
* 0.2 - Cleaned-up release | * 0.2 - Cleaned-up release | ||
Line 102: | Line 100: | ||
=== Progress made on 0.2 Milestone === | === 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 ==== | ==== Tarin ==== | ||
[http://tarinc.wordpress.com/2010/11/25/release-0-2-update/ Release 0.2 Update] | [http://tarinc.wordpress.com/2010/11/25/release-0-2-update/ Release 0.2 Update] | ||
− | |||
− | |||
* 0.3 - Scripts delivered to Armen | * 0.3 - Scripts delivered to Armen | ||
Line 161: | Line 160: | ||
Vitaly - Figure out signing of public keys - password: senecaCdot | Vitaly - Figure out signing of public keys - password: senecaCdot | ||
Eugene - make a spec file by the end of the day | Eugene - make a spec file by the end of the day | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
'''October 12th 2010 Notes''' | '''October 12th 2010 Notes''' |
Revision as of 05:12, 12 December 2010
Contents
Project Name
Repository Setup for Mozilla Nightly and 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.
Project Leaders
- Brett van Gennip - bvangennip@learn.senecac.on.ca
Eugene KhabianRemoved- Vitalijs Bluzmans - vbluzmans@learn.senecac.on.ca
- Tarinur Choudhury - trchoudhury@learn.senecac.on.ca
Responsibilities
- SPEC File Formation & Desktop Integration - Tarinur
- Repository Configuration - Vitaly
- Testing Minefield with SELinux and Fedora 13 - Brett
Project Contributor(s)
- Chris Tyler
- Armen Zambrano Gasparnian
Project 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
Fully 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.
Please see blog for more details:
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 Nightly Repository.
Please see blog for more details:
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.
Our repository is located at Nightly Repository.
Please see blog for more details:
- 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
- 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 19th, 2010
Brett's Log -
After further thinking about SELinux and how it works with minefield. I have concluded that it is no longer an issue with current versions. I plan on trying to find at which version the error was fixed by browsing the build logs.
Vitaly and I also made a discovery to how to run Firefox and minefield Simultaneously. Simply by creating a new profile and running your initial firefox with the -P <profile-name> and -no-remote command. If you do not have a profile you can add one by running --profilemanager.
Therefore, by running:
run firefox 3.6.3 stable firefox -p firefox -no-remote
then, run minefield:
./firefox -p nightly
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: senecaCdot Eugene - make a spec file by the end of the day
October 12th 2010 Notes
- BUGZILLA - 600317
lists.fedoraproject.org/mailman/listinfo
Problem -->
When you download the nightlies you get a set of source code. This is inconvenient and adds another step for people to start testing the nighties and Beta versions of the software.
WE NEED betas to co-exist with the firefox Original working package.
Day One Notes - October 8th 2010
Project:
Repository Setup for Mozilla Nightlies and Betas
Many web developers want access to the latest Firefox pre-releases, including the nightly builds and beta releases. Mozilla's build team wants to make these accessible as parallel-installable binaries, released through a Fedora-compatible repository. This project involves setting this up.
Subprojects:
- Build configuration for the RPM files.
- Repository configuration RPMs.
- Getting SELinux to work with the nightlies.
Website --> Firefox Nightlies
point 1 install repositories installing a YUM system to grab Point 2 installation of the Repositories point 3 create account on bugzilla
2 repositories for x86 and 64-bit --> producting the rpms
Creating spec files for nightlies ...
pull in nightly build and package
automate it using a script from the website
repository setup -> signing it -->
create the rpm for the repo
seperate nightlies and beta?? AND x86 and 64-bit ??
--> Problem --> Getting SELinux to work with the nightlies.