Hi Jonathan, On 2012-08-03 14:00, Jonathan Nieder wrote:
Hi, Filipus Klutiero wrote:It looks like --add-architecture is not a great solution. After doing that, packages in Synaptic would show with ":amd64" (for example, mesa-utils). I had to remove the architecture, but that wasn't possible until I uninstalled the amd64 package.Can you spell this out for me? What exact symptom did Synaptic show, how did it interfere with work, and is this an important bug that should be fixed in Synaptic?
I didn't know if this is a Synaptic bug, but if add-architecture simply controls the lists of architectures APT fetches indices for, it seems to be. After checking the ITS, this seems related to #666740 and #663365. I'll describe what happens here.
When I open Synaptic after adding the amd64 architecture, nothing has changed. After refreshing APT indices, amd64 packages are added. For example, both "mesa-utils" (i386) and "mesa-utils:amd64" show. This is an awful lot of noise, but probably not a bug strictly speaking. However, after restarting Synaptic, only the amd64 packages show. This is the situation I was describing - only "mesa-utils:amd64" shows. Trying to install that indeed tries to install the amd64 mesa-utils. The i386-specific packages are lost (some architecture-independent packages still display normally).
So to follow up to Ralf's message, Synaptic 0.75.12 does show foreign packages, but, apparently, only these. multiarch was enabled in synaptic 0.75.10:
rebuild with multiarch support