Difference between revisions of "Packaging"

Revision as of 22:14, 18 December 2015

Current State of Packaging

For documentation and discussion. Design is still in flux.

Repositories and Distributions

We have one apt repository at https://apt.galliumos.org/ which serves three "distributions" (confusing name, but there it is).

We have a second apt repository at https://apt-dev.galliumos.org/ which will be retired.

The current distributions are:

• vivid-galliumos ("release" or "stable")
  • priority pinned at 9999
  • trumps Canonical's vivid repodist for all package versions
  • trumps GalliumOS's vivid-galliumos-prerelease repodist only with newer versions
  • this repodist contains fully released packages
  • this is the only default repodist, installed by galliumos-base
• vivid-galliumos-prerelease ("prerelease", "staging", or "unstable")
  • priority pinned at 9999
  • trumps Canonical's vivid repodist for all package versions
  • trumps GalliumOS's vivid-galliumos repodist only with newer versions
  • this repodist contains prerelease packages (expected to be stable and ready for general use)
• vivid-galliumos-testing ("testing", "experimental", "current", or "development")
  • priority pinned at 10090
  • trumps all other repodists (Canonical and GalliumOS) for all package versions
  • this repodist contains testing packages (very possibly broken, not ready for general use)

Packages

Our package version naming convention descends from upstream Ubuntu packages, where applicable. Ubuntu's package versioning works like this:

Sample Package Version Strings

• 3.2.1 Packages from original sources, without Debian or Canonical patches
• 3.2.1-1 Packages patched by Debian (v1) but not Canonical
• 3.2.1-0ubuntu1 Packages patched by Canonical (v1) but not Debian (Canonical adds the implicit zero)
• 3.2.1-1ubuntu2 Packages patched by Debian (v1) and Canonical (v2)

GalliumOS Package Version Strings

Our version string might include a galliumosN tag (N=version), depending on the source of the packaged material:

• Original to us e.g galliumos-base
  • 3.2.1, no tag needed
• From original sources, not patched by us
  • 3.2.1, no changes; reuse the version from the original source
• From original sources, and patched by us
  • 3.2.1  ?? becomes 3.2.1galliumos1 or 3.2.1-galliumos1 ?? TBD!
• From Debian or Canonical (patched or not), not patched by us
  • 3.2.1, no changes; reuse the upstream version string
  • 3.2.1-4
• From Debian (patched or not), and patched by us
  • 3.2.1-4 becomes 3.2.1-4galliumos1, add our tag.
  • 3.2.1 becomes 3.2.1-0galliumos1, add the implicit -0 first, if necessary!
• From Canonical (patched or not), and patched by us
  • 3.2.1  ?? becomes 3.2.1galliumos1 or 3.2.1-galliumos1 ?? TBD!
• From Canonical via Debian (patched or not), and patched by us
  • 3.2.1-0ubuntu1 becomes 3.2.1-0ubuntu1-galliumos1, just add a hyphen and our tag
  • 3.2.1-4ubuntu1 becomes 3.2.1-4ubuntu1-galliumos1

The hyphenation rules are due to Debian's complicated sort logic. See below for a demonstration.

   # These version strings are Debian-ordered from oldest to newest
   #
   3.2.1
   3.2.1-0galliumos1
   3.2.1-1
   3.2.1-1galliumos1
   3.2.1-1ubuntu1
   3.2.1-1ubuntu2
   3.2.1-2galliumos1
   3.2.1-10
   3.2.1-10galliumos1
   3.2.1-10galliumos1
   3.2.1-galliumos1               ## TBD
   3.2.1galliumos1                ## TBD
   3.2.1galliumos2                ## TBD
   3.2.1galliumos10               ## TBD
   3.2.1-0-galliumos1             ## ambiguous; do not use
   3.2.1-0-ubuntu1                ## ambiguous; do not use
   3.2.1-0-ubuntu0-galliumos1     ## ambiguous; do not use
   3.2.1-0-ubuntu1-galliumos1     ## ambiguous; do not use
   3.2.1-1-galliumos1             ## ambiguous; do not use
   3.2.1-1ubuntu1-galliumos1
   3.2.1-1ubuntu2-galliumos1
   3.2.1-1ubuntu2-galliumos2
   3.2.1-1ubuntu2-galliumos10
   3.2.1-1ubuntu10-galliumos1
   3.2.1-10-galliumos1            ## ambiguous; do not use
   3.2.1.1

Package Version Discrepancies!

We have some existing packages which do not follow this naming convention, and are versioned ahead of their upstreams (e.g. our 3.2.2 to 3.2.1 upstream). This causes a few issues:

1. It's confusing for us and gives users the impression that our code is a release ahead of the upstream.
2. When the upstream releases a 3.2.2, it will have different code than our 3.2.2.
3. debootstrap builds will fail to update to our pkgs when version numbers collide.

Package Version Corrections

This is easy to fix! We just need to push corrected pkg versions to the stable repodist (`vivid-galliumos`), and remove the old versions from the same repodist.

However, when users run apt-get upgrade, they will be prompted to confirm "DOWNGRADED" packages. We'll need to emphasize that this is expected in the BETA2 release announcement.

Deviant package versions

These packages are currently problematically versioned: