Raphael Hertzog writes:
> On Fri, 10 Feb 2012, David Kalnischkies wrote:
>> I am not sure through if this is really a bug in dpkg, given that arch:all is
>> to be interpreted as arch:native in multiarch, so on an amd64 system a
>> flip from arch:amd64 to arch:all is not really a flip (and therefo
On Fri, 2012-02-10 at 01:56:02 +0100, David Kalnischkies wrote:
> Sometimes packages change their arch from arch:any to arch:all (or v.v.).
> This used to be no problem for packages where any was the native arch and
> this is still the case, but if it is a foreign arch dpkg refuses to install
> the
On Fri, 10 Feb 2012, David Kalnischkies wrote:
> I am not sure through if this is really a bug in dpkg, given that arch:all is
> to be interpreted as arch:native in multiarch, so on an amd64 system a
> flip from arch:amd64 to arch:all is not really a flip (and therefore works)
> while arch:i386 to
Hi list of dpkg-glory,
Sometimes packages change their arch from arch:any to arch:all (or v.v.).
This used to be no problem for packages where any was the native arch and
this is still the case, but if it is a foreign arch dpkg refuses to install
the new arch:all version with the following error
4 matches
Mail list logo