• Logo
    Ubuntu project
  • documentation.ubuntu.com
  • More resources
    • Discourse
    • Matrix
    • GitHub
Contents Menu Expand Light mode Dark mode Auto light/dark, in light mode Auto light/dark, in dark mode Skip to content
Ubuntu project documentation
Ubuntu project documentation
  • How Ubuntu is made
    • Governance
      • Ethos
        • Ubuntu Code of Conduct
        • Diversity policy
        • Our Mission
      • Peers
    • Key concepts
      • Ubuntu releases
      • Upstream and downstream
      • Supported architectures
      • Launchpad
      • Package archive
      • Package format
      • Package lifecycle
      • Version string format
      • Patches
      • Phased updates
      • DEP 3 - patch file headers
      • Debian policy
      • debian/ directory
      • Filesystem hierarchy standard
    • Process overviews
      • Release cycle
      • Freezes
      • Freeze exceptions
      • Merges & syncs
      • Transitions
      • Backports
      • Automatic package testing: autopkgtest
      • Sponsorship
      • Proposed migration
        • Failure to Build From Source (FTBFS)
        • Autopkgtest regressions
        • Issues preventing migration
        • Special migration cases
      • Stable Release Updates
      • Main Inclusion Review (MIR)
        • MIR roles and steps
        • Process states
        • MIR exception - font packages
        • MIR exception - OEM packages
        • MIR - re-reviews
        • MIR - Rust code in main
    • List of releases
  • Contributors
    • Getting started
      • Set up for Ubuntu development
      • Get the source of a package
    • Triaging bugs
      • Bug types
      • Bug status
      • Bug importance
      • Bug responses
      • Assign a bug to a package
    • QA and testing
      • Report a bug
      • Application testing
      • Manual ISO testing
      • Hardware testing
      • Upgrade testing
      • Pre-release testing
    • Debugging
      • Debug an Apport crash
    • Fixing bugs
      • Get a new upstream version
      • Extract packages
      • Install built packages
      • Fix a bug in a package
      • Build packages in a PPA
      • Build packages locally
      • Propose changes
      • Run package tests
      • Bug fixing checklist
    • Patching
      • Make changes to a package
      • Manage patches
      • Work with Debian patches
      • Commit changes
      • Submit a merge proposal
      • Dual maintenance with Salsa and git-ubuntu
    • Merging
      • Preliminary steps
      • Merge process
      • Fix the changelog
      • Upload a PPA
      • Test the new build
      • git-ubuntu merge proposal
      • Merge manually
      • Merge cheat sheet
    • New packages
      • Create a new package
      • Upload packages to a PPA
      • Request an SRU
    • Check accessibility
    • Find a sponsor
    • Request an upload
    • Request a sync
    • Contribute docs
    • Advanced tasks
      • Check publication history
      • Checking reverse dependencies
      • Review a merge proposal
      • Sponsor an upload
      • Sponsor a sync
      • Resolve a migration issue
      • +1 Maintenance
      • +1 Maintenance report template
      • Request a package removal
      • Request a freeze exception
      • MIR bug request template
      • Use MIR templates
    • Set up a mirror
      • Mirror scripts
      • Push mirroring
  • Maintainers
    • Uploader tasks
      • Sponsoring
      • How to update seeds
      • How to work with the upload queue
    • Handling MIR reviews
      • MIR reviewer's template
    • SRU tasks
      • How to review an SRU
    • Archive Admin tasks
      • NEW review
      • Remove a package
      • Package overrides
      • Priority mismatches
      • Signing bootloaders
      • Change phasing on delivering SRU updates
      • i386
      • Archive-related services
      • Check contributions to AA process and documentation
  • Who makes Ubuntu
    • Councils and Boards
      • Community Council
      • Technical Board
      • Membership Board
      • Developer Membership Board
        • DMB meetings
        • DMB restaffing
        • DMB rules
      • Conflict resolution
      • Delegation
    • Roles and responsibilities
      • About the uploaders role
        • Uploaders service level agreement
      • About the MIR role
        • MIR team weekly status meeting
        • MIR Service Level Objectives
      • About the SRU role
        • SRU service level agreement
      • Archive Administration
      • The Release Team
    • Ubuntu Developers
      • Ubuntu Prospective Developers
      • Ubuntu Contributing Developers
      • Per-Package Uploaders
      • Package Set uploaders
      • Delegated Developers
      • MOTU
      • SRU Developers
      • Core Developers
      • Developer Membership application process
        • DMB application knowledge requirements
        • Aspects of a good DMB application
    • Specialist teams
      • The Bug Squad
      • Ubuntu Bug Control
  • Glossary
  • Staging/preview area
    • Ubuntu Membership Board
      • Ubuntu development
      • DMB knowledge base
      • Ubuntu membership
        • Membership perks
        • Membership requirements
        • Membership application process
    • Seeds
    • Seed management
    • Germinate
    • New packages
    • The Package Archive
    • Partner archive
    • Archive Admin museum
    • Content that doesn’t belong to AA
Back to top
Contribute to this page

Archive-related services¶

Note

This page is a seed which will document which services are where, and how they work. The previous list is being replaced as services are migrated to become charmed hosted services.

This page documents the services used by the Archive Administrators and how they work.

List of services on ubuntu-archive-toolbox¶

Seeds/germinate¶

Debian auto-import¶

When the next version of Ubuntu is in full development, we will automatically pull some packages from Debian unstable into the new series’ -proposed pocket. Importantly, we’re only importing the sources, and rebuild the binaries from scratch.

The service is set up on the ubuntu-archive-toolbox machine, as a cronjob running every 6 hours. The script itself is auto-sync in the ubuntu-archive-tool repo.

Packages eligible for the sync are any package that doesn’t have Ubuntu-specific changes. The heuristic is based on version number: if it contains ubuntu, it is considered to have a delta.

In addition to delta-containing packages, some packages are entirely exluded from the sync through the sync-blocklist.

Disabling auto-import¶

To disable auto-import, the usual procedure is to edit the ubuntu-archive-toolbox crontab to add a --dry-run parameter to the appropriate line, e.g.

# Before
0 5,11,17,23 * * *      PYTHONPATH=/home/ubuntu-archive/python auto-sync --log-directory ~/public_html/auto-sync --batch
# After
0 5,11,17,23 * * *      PYTHONPATH=/home/ubuntu-archive/python auto-sync --dry-run --log-directory ~/public_html/auto-sync --batch

This allows for the continuing generation of logs, potentially useful for monitoring.

phased-updater¶

Bugpatterns (related to Error tracker)¶

Team-to-package mapping¶

Component-mismatches¶

OEM meta packageset sync¶

Cleaning buildd builders¶

Permission report¶

Packageset report¶

Auto-accept¶

Transition tracker (ben)¶

Debugging broken jobs on ubuntu-archive-toolbox¶

Copyright © 2025 CC-BY-SA, Canonical Ltd.
Last updated on Aug 27, 2025
Contents
  • Archive-related services
    • List of services on ubuntu-archive-toolbox
      • Seeds/germinate
      • Debian auto-import
        • Disabling auto-import
      • phased-updater
      • Bugpatterns (related to Error tracker)
      • Team-to-package mapping
      • Component-mismatches
      • OEM meta packageset sync
      • Cleaning buildd builders
      • Permission report
      • Packageset report
      • Auto-accept
      • Transition tracker (ben)
    • Debugging broken jobs on ubuntu-archive-toolbox