Hi, G. Milde wrote: > Package: ttf-opensymbol > Version: 2.2.1-5 > Severity: normal > > > After the update of ttf-opensymbol 2.0.3-2 -> 2.2.1-4 the postrm script
Uh. A upgrade from *2.0.3-2*? What? Etch does contain 2.0.4. If you upgrade from sarge+bpo (which would contain 2.0.3-6~bpo.4, so even something newer than you have), skipping releases are not supported. Upgrade to etch and then to sid if you want. In any case, I don't think we should add the conflicts. IMHO it's a fontconfig bug that fc-cache fails and they should fix this. ttf-opensymbol (just as any other font package) just runs fc-cache. > The deadlock could be left with updating fontconfig > > [AKTUALISIERUNG] fontconfig 2.3.2-7 -> 2.4.2-1.2 > [AKTUALISIERUNG] fontconfig-config 2.4.1-2 -> 2.4.2-1.2 > [AKTUALISIERUNG] libfontconfig1 2.4.1-2 -> 2.4.2-1.2 Again, from which interesting system are you upgrading? fontconfig | 2.3.1-2 | oldstable | source, alpha, arm, hppa, i386, ia64, m68k, mips, mipsel, powerpc, s390, sparc fontconfig | 2.4.2-1.2 | etch-m68k | source, m68k fontconfig | 2.4.2-1.2 | stable | source, alpha, amd64, arm, hppa, i386, ia64, mips, mipsel, powerpc, s390, sparc hppa, i386, ia64, mips, mipsel, powerpc, s390, sparc fontconfig | 2.4.2-1.2 | unstable | source, alpha, amd64, arm, hppa, hurd-i386, i386, ia64, m68k, mips, mipsel, powerpc, s390, sparc > so I assume a conflict with fontconfig <= 2.3.2 might solve the problem. And would make a sarge backport (which is being worked on) not possible without removing this dependency again. Gr��e/Regards, Ren� -- .''`. Ren� Engelhard -- Debian GNU/Linux Developer : :' : http://www.debian.org | http://people.debian.org/~rene/ `. `' [EMAIL PROTECTED] | GnuPG-Key ID: 248AEB73 `- Fingerprint: 41FA F208 28D4 7CA5 19BB 7AD9 F859 90B0 248A EB73
signature.asc
Description: Digital signature
