Your message dated Wed, 10 Apr 2013 23:27:56 +0200 with message-id <[email protected]> and subject line Re: Bug#705080: libpango1.0-0: version conflict between i386 package and "all" arch package renders both un-updateable has caused the Debian Bug report #705080, regarding libpango1.0-0: version conflict between i386 package and "all" arch package renders both un-updateable to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 705080: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=705080 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: libpango1.0-0 Severity: important Dear Maintainer, Unfortunately, the latest update to libpango1.0-0 did not end up fixing the issue I was having previously, and creates a new problem on top of that as now the "all" arch package and the i386 package are no longer equivalent versions and therefore cannot be co-installed. As such, all of the new packages that the "all" arch is supposed to be a transitional package for are also no longer at matching versions in amd64 and i386, making it impossible to co-install them. This is the output from Aptitude when trying to update libpango1.0-0 (for "all" arch, on an amd64 system): The following NEW packages will be installed: libpango-1.0-0{ab} libpango-1.0-0:i386{ab} libpangocairo-1.0-0{ab} libpangocairo-1.0-0:i386{ab} libpangoft2-1.0-0{ab} libpangoft2-1.0-0:i386{ab} libpangox-1.0-0:i386{a} libpangoxft-1.0-0{ab} libpangoxft-1.0-0:i386{ab} The following packages will be upgraded: libpango1.0-0{b} libpango1.0-0:i386{b} 2 packages upgraded, 9 newly installed, 0 to remove and 21 not upgraded. Need to get 1,940 kB of archives. After unpacking 1,578 kB will be used. The following packages have unmet dependencies: libpangoxft-1.0-0 : Breaks: libpangoxft-1.0-0:i386 (!= 1.32.5-3) but 1.32.5-4 is to be installed. libpangoxft-1.0-0:i386 : Breaks: libpangoxft-1.0-0 (!= 1.32.5-4) but 1.32.5-3 is to be installed. libpango1.0-dev : Depends: libpango1.0-0 (= 1.32.5-1) but 1.32.5-3 is to be installed. libpango-1.0-0 : Breaks: libpango-1.0-0:i386 (!= 1.32.5-3) but 1.32.5-4 is to be installed. libpango-1.0-0:i386 : Breaks: libpango-1.0-0 (!= 1.32.5-4) but 1.32.5-3 is to be installed. libpangocairo-1.0-0 : Breaks: libpangocairo-1.0-0:i386 (!= 1.32.5-3) but 1.32.5-4 is to be installed. libpangocairo-1.0-0:i386 : Breaks: libpangocairo-1.0-0 (!= 1.32.5-4) but 1.32.5-3 is to be installed. libpangoft2-1.0-0 : Breaks: libpangoft2-1.0-0:i386 (!= 1.32.5-3) but 1.32.5-4 is to be installed. libpangoft2-1.0-0:i386 : Breaks: libpangoft2-1.0-0 (!= 1.32.5-4) but 1.32.5-3 is to be installed. libpango1.0-0 : Conflicts: libpango1.0-0:i386 but 1.32.5-4 is to be installed. libpango1.0-0:i386 : Breaks: libpango1.0-0 (!= 1.32.5-4) but 1.32.5-3 is to be installed. The output from Aptitude is similar if I try to update libpango1.0-0:i386. I don't understand why the i386 packages on my multiarch system aren't properly recognizing the "all" arch transitional package as being installed and insisting on trying to install the package from the i386 arch. I will have to try to investigate this further and see if I can't figure out why this is not working as it should be. -- System Information: Debian Release: 7.0 APT prefers experimental APT policy: (650, 'experimental'), (650, 'unstable'), (600, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.8-trunk-amd64 (SMP w/2 CPU cores) Locale: LANG=en_CA.utf8, LC_CTYPE=en_CA.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash
--- End Message ---
--- Begin Message ---Version: 1.32.5-4 On 04/10/2013 10:08 PM, Alex Vanderpol wrote: > Actually, this was an update from version 1.32.5-1, I had downgraded back to > it > after the issues I had with missing modules (which it turns out are built-in > now) and the issue with i386 arch packages dependent on libpango1.0-0 not > recognizing the "all" arch package on my amd64 system. > > However, since the only arch that was updated to 1.32.5-4 was the i386 arch, > the > amd64 arch packages were all still version 1.32.5-3, thus the conflict. > > I suppose I should have just waited, it appears the amd64 arch packages were > just lagging behind the i386 arch packages, and had I been more patient, I > would > not have had this issue. I'm sorry for bothering you. No problem. Closing the bug. Emilio
--- End Message ---
