-those tested by upstream, and moreover, the actual versions might change
-frequently between to subsequent uploads of a package. Currently a change in a
-dependency that introduces an incompatibility cannot be detected reliably
-(before users have filed a bug report) -- even if upstream provides a testsuite
-that would have caught the breakage. Although there are archive-wide QA efforts
-(e.g. constantly rebuilding all packages) these tests can only detect API/ABI
-breakage or functionality tested during build-time checks -- they are not
-exhaustive for the aforementioned reasons.
+those tested by upstream, and moreover, the actual versions of dependencies
+might change frequently between to subsequent uploads of a package. Currently
+a change in a dependency that introduces an incompatibility cannot be detected
+reliably (before users have filed a bug report) -- even if upstream provides a
+test suite that would have caught the breakage. Although there are archive-wide
+QA efforts (e.g. constantly rebuilding all packages) these tests can only
+detect API/ABI breakage or functionality tested during build-time checks --
+they are not exhaustive for the aforementioned reasons.