Have Grp.FindPreferredPkg return very foreign pkgs as last resort

Usually this method will return the package in the most preferred
architecture (e.g. native) as that is usually what the user talks about
and also information wise for our internal usage the most dense.

Early on in parsing Packages files through it can happen that we
encounter stanzas about packages in architectures we are not even
configured to know about – we have to collect them anyhow as we might be
requested to show info about them or they could be in the status file
and we can't ignore stanzas in the status file… trouble is that this
method used to not return anything if only such an architecture was
present if we later discover other architectures which causes Provides
and Conflicts which are added lazily on discovery of an architecture
to not be added correctly.

The result is like in the testcase that apt could be instructed to
install a package without respecting its negative dependencies, which is
bad even if its discovered by dpkg and refused. It does only happen with
unknown architectures through which mostly happens if you are unlucky
(amd64 users tend to be very lucky as that sorts early) and use
flat-style repositories containing multiple architectures.

Reported-By: Tianyu Chen (billchenchina) on IRC

1 files changed, 1 insertions, 1 deletions

diff --git a/doc/examples/configure-index b/doc/examples/configure-index
index 6a168192c..0d4dd31a5 100644
--- a/doc/examples/configure-index
+++ b/doc/examples/configure-index
@@ -540,7 +540,7 @@ DPkg
 
    // controls if apt will apport on the first dpkg error or if it 
    // tries to install as many packages as possible
-   StopOnError "true";
+   StopOnError "<BOOL>";
 
    Progress-Fancy {
       progress-fg "<STRING>";