Lubuntu
/
britney2-ubuntu
mirror of https://github.com/lubuntu-team/britney2-ubuntu.git
8
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
britney2-ubuntu fork which runs on ci.lubuntu.me
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
667 Commits
1 Branch
0 Tags
2.4 MiB
 
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '117a5c2166'
${ noResults }
Go to file
Niels Thykier 117a5c2166
Write a short incomplete README 		9 years ago
doc Fixed a typo in the doxygen.conf file 13 years ago
installability Remove unused named parameter 9 years ago
policies Optimise a few hints.search calls 9 years ago
.gitignore Add a .gitignore file. 17 years ago
BUGS At this point, we could schedule a periodic diff between the original excuses and the new ones; everything seems to be the same (excluding the usual bugs in the 17 years ago
INSTALL INSTALL: Update dependency for Python 3 9 years ago
LICENSE Initial import, excuses generation almost working. 19 years ago
README.md Write a short incomplete README 9 years ago
TODO TODO: fix typoes; thanks, Julien Cristau 14 years ago
britney.conf Add present-and-installable constraints support 9 years ago
britney.py Make Faux packages default to non-free 9 years ago
britney_nobreakall.conf Update britney_nobreakall.conf 9 years ago
britney_util.py britney.py: Support compressed Packages/Sources 9 years ago
completer.py Remove unused assignments/parameters 10 years ago
consts.py Drop now unused register_reverses and RDEPENDS 9 years ago
excuse.py excuse: present dependency info in a machine parseable way 9 years ago
hints.py Move some of the hint parsing into hints.py 9 years ago
migrationitem.py Use python3-style super() 10 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 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 daye with its primary source suite (e.g. Debian unstable).

Quick setup guide

TODO: Write a quick setup guide (once mirror layout has been tested)

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:

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