Differences between revisions 51 and 52
Revision 51 as of 2016-06-05 15:24:47
Size: 5707
Editor: PaulWise
Comment: update BTS stuff
Revision 52 as of 2016-08-14 09:52:44
Size: 5741
Editor: PaulWise
Comment: debchange hardcodes suite names.
Deletions are marked like this. Additions are marked like this.
Line 120: Line 120:
debchange hardcodes suite names.

Extending Debian repos

We want (761348) to enable:

  • Automatic enumeration of suites for a repository
  • Automatic enumeration of repositories for a distro

This page is for exploring the existing solutions, existing hardcoding and requirements for services.

Existing solutions


Has the same problems as hardcoding elsewhere but better than hardcoding in lots of places.






Has a configuration file listing all suites with metadata about all of them.

Existing hardcoding


All the info.


Name of all suites in the archive, with explicit mappings from "symbolic" names (stable, testing, ...) to "absolute" names (wheezy, jessie, ...). Bonus point: metadata about both current and past releases (on archive.d.o), such as when the releases happened, their version numbers, etc.

Ideally, the above info should be available for all archives, and in particular also for the security archive. Bonus point: having a single central place that gather together information from all relevant archives (the main one, security, what else?).


Encodes codename combinations like squeeze2bpo2wheezy in a configuration file.


Has hostgroups for each Debian release that is currently in use.


www.d.o apache2 config hard-codes codename/version mapping and arch association mapping.


  • bin/gen-DSA: hard-codes mappings from oldstable/stable/testing to codenames.
  • security-tracker code: cf. 783491


Has architectures, sections hard-coded, including non-US.

parts/7release-notes hard-codes which release notes to build and which release to use for trunk.

=== bugs.debian.org ==

@gTags in /srv/bugs.debian.org/etc/config on bugs-master.debian.org has a list of releases and their -ignore tags.


english/releases/*/release.data has architectures, install manual languages and release notes languages.

english/releases/Makefile and english/Bugs/pkgreport-opts.inc have lists of releases.

*/ports/index.wml has which architectures are official and which are not, would be better to use the data from the archive re officialness.

*/distrib/archive.wml has which releases are on archive.debian.org, would be better to automatically update that info.


Hardcodes various info about the releases. Hardcodes list of Linux architectures from dpkg.


Hardcoded release name, symbolic name references, architectures, and sorting of releases. Also information about what a partial release (like -updates and -security) does sort-of overlay.



The qadb apt database hard-codes which suites are actively updated.


Hardcodes the names of backports suites.


Hardcodes the list of all official and unofficial architecture Debian names.


  • Hardcodes Ubuntu release names.
  • Hardcodes architecture list of several distribution (including Debian)

Section descriptions

Various packages hardcode section descriptions.


chdist hardcodes architecture lists. debchange hardcodes suite names.


Hardcodes suite to version, codename and architecture list mappings.


Hardcodes suite to codename mappings, -pu codenames, codenames that binNMUs can be done in.


Hardcodes list of architectures that have ever been on ftp.d.o.


Hardcodes the codename of Debian testing on the d-i daily builds directories like this:


The base for this is in


and there are multiple places in here which hard-code release name, architecture names etc.



Want squeeze2bpo2wheezy to not be magically deleted just because jessie became stable. When new stable releases are done, new piuparts suites (like wheezy2bpo2jessie) should be created, not old ones reused.

Single source of data

For some purposes it would be interesting to have a single source of all metadata (on a per-repo basis and also on a global distro-wide basis) so that full apt metadata doesn't need to be downloaded if it isn't needed. This could also be easier to parse in some cases.

Know which suites are partial

Knowing what suites are "partial" (i.e. don't have a full set of packages) and what parent suite they are associated with (to get the remaining packages) is important for example to be able to do proper dependency analysis on a partial suite by trying to look up missing packages in the parent suite.

Know the order of suites

packages.d.o, sources.d.n etc need to know what order to display suites in.

Know the activity status of suites

sources.d.n etc need to know if suites will ever be updated again.