Fedora/Firefox Repository Setup for Nightly and Beta builds

Project Name

Repository Setup for Mozilla Nightlies and Betas - Firefox Versions (4, 3.6)

Project Description

Automating the process of RPM building and repository updates for Fedora systems of different architectures. Architectures such as Firefox (4, 3.6) Beta's and Nightlies.

Project Leader(s)

• Brett van Gennip
• Yauheni Khabian (Eugene MIA) If your still around please contact us.
• Vitalijs Bluzmans
• Tarinur Choudhury

Project Contributor(s)

• Chris Tyler
• Armen Zambrano Gasparnian

Project Details

point 1 - install repositories - installing a YUM system to grab

Point 2 - installation of the Repositories

point 3 - create account on bugzilla

Project Plan

Goals for each release:

• 0.1

setup any package to be acquired from our repository

Installing the repository VIA an RPM

• 0.2

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

Manual creation of the SPEC file with the NIGHTLY Version to create a functional RPM

• 0.3

Automation of the creation of the SPEC File

Project News

• 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.

October 12 -

• 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.

Solution -->

Add a system (RPM and Repository Setup) for streamlined setup for users to test the firefox software Nightlies and Betas.

project plan

what we need to learn -

   --> REPOSITORY SETUP - WHAT IS IT ?HOW DO WE SET IT UP
   --> SPEC FILE CREATION FOR THE NIGHLTLIES
   --> SELINUX <-- HOW IT WORKS AND HOW WE CAN

resources --

   --> EBOOK
   --> WIKI
   --> PLANETS
       --> FIND PEOPLE THAT MAY BE OF HELP OF SELINUX

• Milestone 1 -

   -> setup any package to be acquired from our repository

• Milestone 2 - RPM Fusion -- a separate reposit

   ->installing the repository VIA an RPM

• Milestone 3 -

   -> 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
   -> Manual creation of the SPEC file with the NIGHTLY Version to create a functional RPM

• Milestone 4 -

   -> Automation of the creation of the SPEC File

Steps needed to take -

   -Need to setup 2 repos - x86 and x86_64 of beta and Nightlies
   -Experimentation with the nightly build and how it works with SELinux

Project sections and Assignments -

   Repository Setup -->                                                       Vitalijs 

   SPEC File Building for Nightlies and Beta's For 64bit and x86 Packages --> Eugene , Tarinur

   Nightly compatibility with SELinux -->                                     Brett , Tarinur

Nightlies are located at Firefox Nightlies

Approach to the Problem

• Target: Current Fedora releases (right now that's

Approach to packaging:

1. Pull from a standard URL (as of now http://nightly.mozilla.org/) (armenzg-TODO: get fixed URL to latest)
2. Package that binary nightly/beta as an RPM
3. Add to a repository and regenerate/update metadata

Approach to repo access:

1. Make a repo "release" RPM that provides .repo file and public key

Approach to SELinux:

1. 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

• SPEC file - Tarinur is Taking this responsibility.
• Repo - Vitaly
• SELinux - Brett
• Desktop integration and testing - Tarinur