mirrorball /

Filename Size Date modified Message
127 B
167 B
2.5 KB
11.1 KB
1.1 KB
1.7 KB
1.5 KB
6.7 KB
Mirrorball README

= Introduction =

Mirrorball is a tool for importing external projects with two main
 o  updatebot: a maintenance tool for automatically processing updates
 o  scripts for initial import and for resolving maintenance exceptions

Mirrorball is a toolkit, not a product.  When mirrorball finds an
exceptional case, it drops you into a debugger.  This is not a bug
in mirrorball; it is an opportunity to use the data structures in
mirrorball to understand what caused the exception and determine
the best way to resolve it.  Automating (or partially automating)
exception handling is good; adding debugging output with potential
solutions is good, but the debugger is part of the toolkit.  It is
common when using the scripts for initial import and resolving
exceptions during maintenance to add breakpoints to the scripts
and verify what they are going to do in the debugger, and then
let the scripts continue and do the work.

To successfully use mirrororball, you need to understand its theory
of operation.  Mirrorball synchronizes sources of package data,
including packages and advisories, with associated Conary repositories.
It uses Conary and rMake as the main underlying tools to drive the
process of converting upstream packages into content in a Conary

Mirrorball has two main ways of representing upstream package state
in a Conary repository.  In the first ("latest"), if the latest
versions of upstream packages differ from what is in the Conary
repository, mirrorball represents the latest state of the upstream
packages in the Conary repository.  In the second ("ordered"),
mirrorball represents a view of the entire history of the upstream
package source in the Conary repository.

Using the "latest" model is easiest; it can often be done without
writing new code in mirrorball.  It requires a source of packages
that it recognizes (for example, a yum repository of RPMs), a
configuration that tells it what to do with the packages, and
a conary repository to put the packages into.  (It also requires
a source of packages to use for building, and the bootstrap
process of making this source available is an advanced topic.)

Using the "ordered" model is more demanding.  In order to represent
all the packages in the historical record, it needs a source of
data for the ordering.  One potential source of data is errata
advisories with dates attached to them somehow.  In order to use
such advisories, code has to be written to import critical data
into mirrorball's "errata" representation.  Then the import process
has to create a complete ordering representing the entire history,
validate that history, warn about conditions in the history that
require manual adjustment, and then apply all history past the
current state of the repository to the repository.

In both models, there are multiple configuration files that need
to be written: essentially, one for each tool used.  These will
include conary configuration (e.g. flavors, superclass packages,
installLabelPath, buildLabel), rmake configuration (e.g. rmakeUrl,
resolveTroves, defaultBuildReqs), and elements of mirrorball per
say (e.g. errata sources and updatebot configuration)

In both models, there are bootstrap requirements: Conary packages
representing sufficient binaries to build with in a repository,
and all necessary Conary superclass and factory packages in the
repository.  Mirrorball does not automatically create these things;
creating the prerequisites for the platform is the responsibility
of the packager.

This document is meant as a guide to get people up and running with a
working updatebot configuration and some basic usage information to get
people started.  It is currently insufficient, so after reading this
document, join #conary on irc.freenode.net and ask for help.

* Setting up updatebot to work in your environment.
* How to do:
 o build packages
 o import new packages
 o build groups
 o update a platform

= Setting up UpdateBot =

First thing you will need is a few checked out mercurial repositories or
to have these modules installed on your system.

Clone the following repositories from hg.rpath.com to ~/hg. (all
scripts currently assume that checkouts are in ~/hg)
* mirrorball
* conary
* rmake
* rpath-xmllib

The test suite unfortunately cannot be run outside of rPath, as it
depends on rPath-internal modules.

Once you have cloned and built the required modules you should be about
ready to run the various UpdateBot scripts.

= A quick walk-through of the mirrorball repository =

* aptmd - module for parsing apt repository metdata. This module
currently only implements parsing Packages.tgz and Sources.tgz.
* commands - the beginning of an actual bot command rather than using the
scripts that will be talked about later.
* extra - various misc. files.
* pylint - directory for running pylint (running make in this directory
  will run pylint on all source directories with the correct config).
* repomd - module for parsing yum repository meta data.
* rpmutils - module containing utilities for dealing with rpms.
* scripts - directory containing scripts for maintaining platforms.
* test - directory containing the testsuite for updatebot
* updatebot - main module

= Scripts/HowTo =

Currently all scripts are hard coded to a specific platform. You will
need to change the path to updatebotrc for the platform that you want to
use. (NOTE: in the updatebotrc for the platform you will need to change
the configPath to point at your checkout).

* buildgroups - build source group in all configured flavors
* buildpackages - build list of packages in all configured contexts
* checkoutall.py - checks out all source components included in the
* findbinaries.py - search a label for all of the binary packages that
  where generated from the latest versions of all source troves
  generated by updatebot.
* hardlink.py - Note that this is not our code. Used in the mirror
  scripts to hard link trees and save space.  Licensed under the GPL.
* import.py - make sure all packages specified in the config are imported
  and built.
* pkgsource.py - loads all metadata from the repository and lets you
  interactively navigate through pkgSource datastructures.
* sync-opensuse.sh - used to keep the OpenSuSE mirror in sync.
* sync-ubuntu.sh - used to keep the Ubuntu mirror in sync.
* updatelicense.py - checks out all sources in a top level group and makes
  sure the license block on the recipe exists.
* update.py - update a platform (update packages, build packages, build
  groups, send advisories)
Tip: Filter by directory path e.g. /media app.js to search for public/media/app.js.
Tip: Use camelCasing e.g. ProjME to search for ProjectModifiedEvent.java.
Tip: Filter by extension type e.g. /repo .js to search for all .js files in the /repo directory.
Tip: Separate your search with spaces e.g. /ssh pom.xml to search for src/ssh/pom.xml.
Tip: Use ↑ and ↓ arrow keys to navigate and return to view the file.
Tip: You can also navigate files with Ctrl+j (next) and Ctrl+k (previous) and view the file with Ctrl+o.
Tip: You can also navigate files with Alt+j (next) and Alt+k (previous) and view the file with Alt+o.