Learning from the future of component repositories

• We consider quality issues that can arise in future evolutions of software repositories.
• We define a class of such issues that is amenable to automatic verification.
• Two relevant instances of such a class are identified: outdated and challenged components.
• We validate our findings on real-world repositories.

An important aspect of the quality assurance of large component repositories is to ensure the logical coherence of component metadata, and to this end one needs to identify incoherences as early as possible. Some relevant classes of problems can be formulated in term of properties of the future repositories into which the current repository may evolve. However, checking such properties on all possible future repositories requires a way to construct a finite representation of the infinite set of all potential futures. A class of properties for which this can be done is presented in this work.We illustrate the practical usefulness of the approach with two quality assurance applications: (i) establishing the amount of “forced upgrades” induced by introducing new versions of existing components in a repository, and (ii) identifying outdated components that are currently not installable and need to be upgraded in order to become installable again. For both applications we provide experience reports obtained on the Debian free software distribution.