assert release coverage
Open, LowPublic


When new tarballs get added to release bundles (frameworks/plasma/apps) they happen to get forgotten or not noticed and subsequently not integrated into neon.

There should be technology which regularly makes sure that all tarballs published on were actually integrated into our user repo.

Easiest approach is probably have a job that runs weekly (?) and gets a list of all tarballs published in the latest stable dir of $release_bundle and then foreaches that it has a source package in user repo of suitable version (excluding epoch and revision).

Also needs:

  • mapping hash from tarball name to repo name (maybe not needed?)
  • exclusion list (do we still have kde4 stuff which needs excluding in applications?)

Related Objects

sitter created this task.Jan 7 2019, 2:26 PM
sitter triaged this task as Low priority.