[Pkg-ime-devel] Bug#704705: Bug#704705: ibus: cannot use with both Mozilla i386 apps and emacs

[Osamu Aoki]

Hi,

On Sat, Apr 06, 2013 at 09:42:33PM +0200, Toni Mueller wrote:
> 
> Hi,
> 
> On Sun, Apr 07, 2013 at 03:17:16AM +0900, Osamu Aoki wrote:
> > On Sat, Apr 06, 2013 at 04:37:51PM +0200, Toni Mueller wrote:
> > > ii  libgtk2.0-0:i386                     2.24.10-2               i386
> > > ii  libjasper1:amd64                     1.900.1-13              amd64
> > > ii  libjasper1:i386                      1.900.1-13              i386
> > > 
> > > libjasper1 1.900.1-14 is in unstable, not in testing.
> > 
> > For you case of experimental and unstable mixture, issue may be slightly
> > different in terms of exact version.  What are "apt-cache policy ..."
> > for these?
> 
> I have:
> 
> $ apt-cache policy libgtk2.0-0
> libgtk2.0-0:
>   Installed: 2.24.10-2
>   Candidate: 2.24.10-2
>   Version table:
>  *** 2.24.10-2 0
>         990 http://http.debian.net/debian/ wheezy/main amd64 Packages
>         990 http://http.debian.net/debian/ testing/main amd64 Packages
>         100 /var/lib/dpkg/status
> $ apt-cache policy libjasper1
> libjasper1:
>   Installed: 1.900.1-13
>   Candidate: 1.900.1-13
>   Version table:
>      1.900.1-14 0
>         100 http://http.debian.net/debian/ unstable/main amd64 Packages
>  *** 1.900.1-13 0
>         990 http://http.debian.net/debian/ wheezy/main amd64 Packages
>         990 http://http.debian.net/debian/ testing/main amd64 Packages

Having both testing and wheezy is waste of time.  You can remove one of
them from APT lines.

>         100 /var/lib/dpkg/status

I see you have mostly testing with some unstable just like me.  

> I actually tried to pin things that way to generally prefer packages
> from Wheezy, but for all IMEs, prefer packages from unstable.
> 
> > > Maybe I have a problem there, with libcolord1...
> > 
> > If you used dpkg libcolord1:i386 required by libgtk-3-0:i386 may be
> > missing.
> 
> FWIW, it looks like I created a mess, again. See:
> 
> $ dpkg -l libcolord1
> Desired=Unknown/Install/Remove/Purge/Hold
> | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
> |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
> ||/ Name                                 Version                 Architecture
> +++-====================================-=======================-============
> ii  libcolord1:amd64                     0.1.21-1                amd64
> ii  libcolord1:i386                      0.1.21-1                i386

Now it looks good.  Good luck with fixing other gliches.
 
> > > dpkg refuses to install anything. But I had to use --force-overwrite plenty
> > > of times, anyway.
> > 
> > OOps, that is risky.
> 
> [OT] I had no viable alternative to reach Wheezy, because on every other
> package, dpkg refused to downgrade w/o it, due to some checksum mismatch
> or so, usually even only in /usr/share/doc/<pkg>/copyright & friends (I
> had inadvertantly pulled in too much from unstable already).

If you were tracking unstable like me and decided to move mostly to
wheezy, simplest thing to do is remove and reinstall after using wheezy
only apt line.  Then re-enable unstable with apt preference 100 just
like you did.  That is what I usually do sometime ... 

Osamu