Re: dpkg: native package in rc state prevents installation of m-a:foreign counterpart
On Sun, Jul 22, 2012 at 05:51:08AM +0200, Guillem Jover wrote:
> On Sat, 2012-07-21 at 22:30:30 -0500, Jonathan Nieder wrote:
> > Guillem Jover wrote:
> > > On Sun, 2012-07-22 at 04:37:02 +0200, Arno Schuring wrote:
> >
> > >> dpkg: error processing /var/cache/apt/archives/libwine_1.4.1-2_i386.deb
> > [...]
> > >> rc libwine:amd64 1.4.1-1.2 Windows API implementation - library
> > >> ii libwine:i386 1.4.1-1.2 Windows API implementation - library
> > [...]
> > > Yes, that's on purpose, otherwise the database could end up with
> > > multiple instances of non-coinstallable packages, which would break
> > > lots of internal and external assumptions.
> >
> > How does crossgrading normally work?
>
> Cross-grading happens whenever a new package instance is installed
> with a different architecture from the current single instance, as
> long as both old and new are not M-A:same, or they switch from
> non-M-A:same to M-A:same or the reverse.
>
> > If Arno had not had libwine:i386 installed, would the upgrade have worked?
>
> Yeah (assuming not-installed == not-present), that would have been a
> cross-grade. Because the old one is M-A:same and the new one is
> M-A:foreign.
Corect me if I'm wrong but your saying the following work:
foo:i386 same 1.2-3 -> foo:i386 foreign 1.2-4
foo:amd64 same 1.2-3 -> foo:i386 foreign 1.2-4
foo:i386 same 1.2-3 -> foo:amd64 foreign 1.2-4
foo:amd64 same 1.2-3 -> foo:amd64 foreign 1.2-4
But not:
foo:amd64 same 1.2-3 -\
-> foo:i386 foreign 1.2-4
foo:i386 same 1.2-3 -/
MfG
Goswin
Reply to: