Skip to content

🔄 Package: Move update-notifier removal into the packaging playbook#257

Merged
mbercx merged 1 commit intomainfrom
ref/update-notifier
Apr 22, 2026
Merged

🔄 Package: Move update-notifier removal into the packaging playbook#257
mbercx merged 1 commit intomainfrom
ref/update-notifier

Conversation

@mbercx
Copy link
Copy Markdown
Collaborator

@mbercx mbercx commented Apr 22, 2026

Removing the update-notifier package during GUI customisation had the side-effect of invalidating apt state in a way that could surface later in the same provisioning run — the ensure-apt-pip refresh honoured cache_valid_time: 86400 and skipped re-updating, so subsequent tasks occasionally failed to find standard packages like ubuntu-desktop-minimal, which would break provisioning even if they had already been installed.

Move the purge out of local/tasks/customise-gui.yml and into playbook-package.yml, where it now runs right after the VM reload and before the disk cleanup. This keeps the Software Updater popup off the shipped image (the only place it actually matters — dev VMs re-provisioned locally can still show it, which is not an issue) without touching apt state mid-build.

@mbercx mbercx force-pushed the ref/update-notifier branch 2 times, most recently from 3f81117 to 84fd628 Compare April 22, 2026 05:18
Removing the `update-notifier` package during GUI customisation had the
side-effect of invalidating apt state in a way that could surface later in the
same provisioning run — the `ensure-apt-pip` refresh honoured `cache_valid_time:
86400` and skipped re-updating, so subsequent tasks occasionally failed to find
standard packages like `ubuntu-desktop-minimal`, which would break provisioning
even if they had already been installed.

Move the purge out of `local/tasks/customise-gui.yml` and into
`playbook-package.yml`, where it now runs right after the VM reload and before
the disk cleanup. This keeps the Software Updater popup off the shipped image
(the only place it actually matters — dev VMs re-provisioned locally can still
show it, which is not an issue) without touching apt state mid-build.
@mbercx
Copy link
Copy Markdown
Collaborator Author

mbercx commented Apr 22, 2026

CI failing again because of PseudoDojo 🙄

Strangely enough: transient issue seems more prevalent for AMD64? May be a coincidence.

@mbercx mbercx force-pushed the ref/update-notifier branch from 84fd628 to 24e7c11 Compare April 22, 2026 05:50
@mbercx mbercx enabled auto-merge (rebase) April 22, 2026 05:50
@mbercx mbercx merged commit f1a18e6 into main Apr 22, 2026
4 checks passed
@mbercx mbercx deleted the ref/update-notifier branch April 22, 2026 05:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant