britney2-ubuntu fork which runs on ci.lubuntu.me

Go to file

Iain Lane 6f0196fedf Allow piuparts policy to be disabled by config		5 years ago
britney2	Implement Ubuntu component relationship constraints (ogre model)	5 years ago
ci	run coverage even if tests fail	5 years ago
doc	document allow-smooth-update hint	5 years ago
tests	Implement Ubuntu component relationship constraints (ogre model)	5 years ago
.codeclimate.yml	.codeclimate.yml: Update thresholds for maintainability	6 years ago
.coveragerc	Update coveragerc to exclude sitecustomize.py	7 years ago
.dockerignore	travis: Build Debian stable docker image and use it for testing	7 years ago
.gitignore	Update .gitignore	7 years ago
.gitlab-ci.yml	ci: switch sid tests to bullseye and allow failure	5 years ago
.travis.yml	.travis.yml: Use master branch for brtiney2-tests	7 years ago
Dockerfile	Migrate to pycodestyle and setup a basic config file	6 years ago
LICENSE	Initial import, excuses generation almost working.	19 years ago
Makefile	Add Makefile to generate documentation	7 years ago
README.md	Move install+config docs from README to doc/setting-up-britney.rst	7 years ago
TODO	TODO: fix typoes; thanks, Julien Cristau	14 years ago
britney.conf	Give standard priviledges to sramacher	5 years ago
britney.conf.template	Add support for partial source suites via options	6 years ago
britney.py	Allow piuparts policy to be disabled by config	5 years ago
britney_nobreakall.conf	britney*.conf: update autopktest output file for multi-instance support in britney1	6 years ago
setup.cfg	Migrate to pycodestyle and setup a basic config file	6 years ago

README.md

Britney - Keeps suites installable and up to date

Britney is a program to compute an update of a Debian-based package suite by feeding it updates from (one or more) source-suite(s). A few known use cases:

Debian uses it to update testing based on unstable
Ubuntu uses it to update their latest development suite using a "hidden" -proposed-updates suite as source

Britney's primary goal is too keep packages in the target suite installable (e.g. Debian testing) while keeping it up to date with its primary source suite (e.g. Debian unstable).

Installing, configuring and using Britney

Please see [doc/setting-up-britney.rst].

Migration items

Britney generally works with a "migration item", which is a group of binary packages (and possibly a source package). Packages are bundled into these migration items under the following rules:

"source migration": An update of the source package. This will include all the binary packages built from that source version (regardless of architecture).
- Can contain binaries built from earlier source version depending on the setting of "IGNORE_CRUFT"
- Britney refers to these as "${SOURCE_NAME}"
"binary migration": An update of binary packages on a given architecture to an existing source package in the target suite.
- Two common cases: Built for the first time on a new architecture and binNMUs
- Britney refers to all cases of these as "{SOURCE_NAME}/{ARCHITECTURE}"
"removal item": A removal of a source or binary package.
- Note that it is only possible to trigger "source" removals via hints. Binary removals are items generated by Britney to clean up the target suite.
- Britney refers to these as "-{SOURCE_NAME}" or "-{BINARY_NAME}/${ARCHITECTURE}" depending on the case.

Migration rules (excuses/policies)

Britney applies a number of policies to migration items before attempting to migrate them to the target suite. These policies can "reject" a package and prevent it from migrating. Some policies/built-in rules:

Age policy: Lets source migrations age a bit before they are allowed to migrate
- Supports variable length based on package urgency
RC Bug policy: Rejects packages with regressions in RC bugs
- Requires an external tool to keep the bug lists up to date
Keeps architectures in sync: Source migrations updating existing packages only occur if architectures are up to date
- Can be configured to ignore certain architectures.