From e667e4dcaf534838510d9e2a7e7356be4fd55414 Mon Sep 17 00:00:00 2001 From: Paul Gevers Date: Sat, 3 Mar 2018 22:43:48 +0100 Subject: [PATCH] doc: Initial version for piuparts solutions --- doc/solutions-to-common-policy-issues.rst | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/doc/solutions-to-common-policy-issues.rst b/doc/solutions-to-common-policy-issues.rst index b5f0586..d3ce926 100644 --- a/doc/solutions-to-common-policy-issues.rst +++ b/doc/solutions-to-common-policy-issues.rst @@ -103,3 +103,16 @@ non-obvious issues: then libfoo2 depends on libfoo-data v2, then libfoo1 will become uninstallable as libfoo-data v2 will "shadow" libfoo-data v1. +Britney complains about "Piupart" +--------------------------------- + +Britney can be configured to take the results of piuparts (package +installation, upgrading and removal testing suite) into account. Currently this +policy is only taking into account the piuparts result for installing and +purging the package in the source suite and the target suite (so no upgrade +test). As with the other policies, a regression means that the package passes +in the target suite, but fails in the source suite. Unless this is a bug in +piuparts, the package needs to be fixed first to install and purge cleanly in +the non-interactive debconf state. An URL to the relevant piuparts results is +provided in the excuses. +