Ubuntu-Archive/error-tracker
1
0
Fork 0
mirror of https://github.com/ubuntu/error-tracker.git synced 2025-10-26 09:05:11 +01:00
Code Issues Projects Releases Packages Wiki Activity
No description
85 commits 10 branches 25 tags 636 KiB
Find a file
Exact
Florent 'Skia' Jacquet 15a6dfc784 README: document opening a new series
2025-10-20 15:17:03 +02:00
.github/workflows .github: release: try to add 'latest' 2025-08-27 16:14:35 +02:00
charms charms: update READMEs with sparse but accurate information 2025-09-23 11:02:30 +02:00
src retracer: add 'resolute' 2025-10-20 12:06:29 +02:00
.gitignore Initial commit 2024-11-05 18:16:09 +02:00
LICENSE Initial commit 2024-11-05 18:16:09 +02:00
pyproject.toml Fix some linting issues and ignore others 2025-08-14 14:03:06 +02:00
README.md README: document opening a new series 2025-10-20 15:17:03 +02:00
renovate.json Add renovate.json 2024-12-17 15:42:28 +00:00

README.md

error-tracker

Code behind https://errors.ubuntu.com

Dependencies

sudo apt install python3-amqp python3-cassandra apport-retrace ubuntu-dbgsym-keyring

Documentation

Opening a new series

Many components of the Error Tracker need to be made aware of the new release.

Retracers

The retracers need to have a configuration in ./src/retracer/config. See 7fdd31c97e for an example commit.

Daisy and Web frontend

There are still many places where the series are hardcoded. While an effort is ongoing to change that, the best that can be done for now, is to search the repo for both previous series codename (like questing) as well as version number (like 25.10).

Deployment

In addition to changes to this repo, all the deployment machines need to be updated with the SRU'd distro-info-data. This should in principle be automatic if some sort of unattended upgrades are configured, but better double check as all is currently under change, and still has a lot of legacy.

Archives and design

Here is some archive documentation for you. New and up-to-date one hasn't started yet, but the old things are still pretty much accurate, except when it comes to deployment and infrastructure.