Comment 4 for bug 535368

Right, there were some transient problems here. 'apt-get dist-upgrade' may well help. There isn't much more we can do - this is basically due to previous versions of the parted packaging (way back in 2000) using libparted0, more recent versions declaring a Conflicts against libparted0, and then upstream recently deciding to go back to libparted.so.0 as the SONAME again so we had to reuse an old package name. Lacking a time machine, there isn't very much we can do to make this smoother - we just had to jump as hard as possible and try to land in one piece.

Mark: While I haven't done a detailed simulation, I don't think that adding even more Conflicts and Replaces would really help here. In fact, they'd probably make the problem worse. Run-time library packages are not normally supposed to conflict with other run-time library packages - the fact that there's a one-way conflict in this case is a historical aberration that shouldn't be perpetuated.

Currently, the following binaries in the archive are still built against older versions of libparted:

  libvirt-bin/powerpc (1.8)
  libvirt-bin/sparc (1.8)
  kvpm/ia64 (1.8)
  partitionmanager/ia64 (2.1)
  python-parted/sparc (2.1)
  python-parted-dbg/sparc (2.1)

I'm actively working on all of these (I may just remove the ia64 binaries, as I think KDE is too broken on ia64 right now to be able to build them). Once we have all these upgraded, we can remove the old libparted binaries from the archive, and I think that will clue apt into the fact that it's supposed to prefer the new ones.