Skip to content

docs: add update_output.txt line type explanations to proposed-migration #722

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
rkratky wants to merge 1 commit into
base: main
Choose a base branch
from
+11 −0
Open

docs: add update_output.txt line type explanations to proposed-migration #722

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions docs/.custom_wordlist.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,6 +3,7 @@ ABIs
Ayatana
allowlist
apport
baz
archs
auditable
autobuilders
Expand Down Expand Up @@ -163,6 +164,7 @@ rasdaemon
recompiles
repo
retracer
recurse
RFPs
Rockcraft
Rosbrook
Expand Down
9 changes: 9 additions & 0 deletions .../how-ubuntu-is-made/processes/proposed-migration/issues-preventing-migration.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -183,6 +183,15 @@ If the package, as shown in [update_excuses](https://ubuntu-archive-team.ubuntu.

### Parse the {file}`update_output.txt` file

The {file}`update_output.txt` file is the complete output of the proposed-migration scripts as they recurse through candidate packages. It is terse, but understanding its line types helps:

@utkarsh2102 utkarsh2102 Jul 27, 2026

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

what d'you mean by "complete output"?


* **`trying:`** — the script is evaluating whether this package can migrate.
* **`accepted:`** — the package (or group) appears to make things better and is accepted into the release pocket.
* **`skipped:`** — the package makes things worse and is not accepted.
* **`recur:`** — shows the recursion path. For example, `recur: [foo bar] baz` means "having already found that foo and bar make things better, now trying baz to see what happens, even though it breaks things."

After all candidates have been tried, the script compares the total number of broken packages before and after. If the result is better, the changes are accepted; otherwise they are discarded.

Using the {pkg}`exim4` package as an example.

1. Find the package in [update output.txt](https://ubuntu-archive-team.ubuntu.com/proposed-migration/update_output.txt):
Expand Down
Loading