[Apt-listbugs-commits] [SCM] apt-listbugs development tree branch, master, updated. apt-listbugs/0.1.5-9-g93ed433

[Francesco Poli (wintermute)]

The following commit has been merged in the master branch:
commit 93ed4332f8550eb0bad408555b3aa9b935caf816
Author: Francesco Poli (wintermute) <invernomuto at paranoici.org>
Date:   Mon Oct 31 10:57:15 2011 +0100

    explain a workaround for the "affects" issue

diff --git a/debian/README.Debian b/debian/README.Debian
index 3967d0a..01156d1 100644
--- a/debian/README.Debian
+++ b/debian/README.Debian
@@ -169,6 +169,16 @@ A/a3. And there's no way for apt-listbugs to distinguish between
 scenario 0 and scenario 1, either. Hence, apt-listbugs currently
 ignores the "affects" field in any case.
 
+There's a way to work around the lack of version tracking info
+for the "affects" field: whenever you find yourself in scenario 1,
+file a dummy bug report against package A, marking it as found in
+version a1 and as blocked by the actual bug report (the one assigned
+to package B). A descriptive bug report title, citing the interaction
+with package B, is recommended, in order to let users quickly see
+whether they should worry about the issue.
+Anyway, please take into account that this strategy is sub-optimal
+and may annoy some package maintainers!
+
 Everything said so far holds for the apt-listbugs "apt" command.
 The other apt-listbugs commands ("list" and "rss") should behave
 consistently, or otherwise they will produce misleading output.

-- 
apt-listbugs development tree