old Conflicts cause libparted0 upgrade problems

Bug #535368 reported by Tony Mugan
60
This bug affects 11 people
Affects Status Importance Assigned to Milestone
parted (Ubuntu)
Fix Released
High
Colin Watson
Lucid
Fix Released
High
Colin Watson

Bug Description

Binary package hint: gparted

There is a missing dependency

tony@lucid:~$ sudo apt-get install parted
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
  parted: Depends: libparted0 (>= 2.2-1) but it is not going to be installed
E: Broken packages

ProblemType: Bug
Architecture: amd64
Date: Wed Mar 10 08:50:25 2010
DistroRelease: Ubuntu 10.04
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha amd64 (20100224.1)
NonfreeKernelModules: nvidia
Package: gparted (not installed)
ProcEnviron:
 LANG=en_AU.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-16.24-generic
SourcePackage: gparted
Uname: Linux 2.6.32-16-generic x86_64

Related branches

Andreas Olsson (andol)
Changed in gparted (Ubuntu):
status: New → Incomplete
status: Incomplete → Confirmed
Revision history for this message
Andreas Olsson (andol) wrote :

I can confirm the same problems, with the same involved versions.

For me the problem was solved by explicitly asking for the package libparted0 to be installed, causing the removal of the packages libparted-2.1-0 and libparted1.8-12.

Looks like the result of the package name change, which happened with parted 2.2-1. I guess apt couldn't manage to figure out that upgrade on its own.

affects: gparted (Ubuntu) → parted (Ubuntu)
Revision history for this message
Mark Schmidt (schmidtm) wrote :

I can confirm this too. This also prevents udisks, partitionmanager and kvpm from being updated on my system.

Revision history for this message
Mark Schmidt (schmidtm) wrote :

Installing libparted0 by hand removes libparted-2.1-0 and libparted1.8-12 so there should be a konflicts and replaces in the dependency list of libparted0 for those versions too

Revision history for this message
Colin Watson (cjwatson) wrote :

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.

Revision history for this message
svaens (svaens) wrote :

I'm glad it wasn't just me! Good luck dev guys!

Revision history for this message
Arjan (iafilius) wrote : Re: [Bug 535368] Re: gparted will not install on lucid Alpha3

Hi,

a work-around for me.
What worked for me is just a:

sudo apt-get install libparted0
and then installed the latest 2.2 version

which let me then install libvirt-bin again afterwards.

This was good enough for me to get virt-manager/libvirt-bin/kvm going

Regards,

On Fri, 2010-03-12 at 06:39 +0000, svaens wrote:

> I'm glad it wasn't just me! Good luck dev guys!
>

Colin Watson (cjwatson)
summary: - gparted will not install on lucid Alpha3
+ old Conflicts cause libparted0 upgrade problems
Colin Watson (cjwatson)
Changed in parted (Ubuntu Lucid):
status: Confirmed → Triaged
importance: Undecided → High
milestone: none → ubuntu-10.04
assignee: nobody → Colin Watson (cjwatson)
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package parted - 2.2-5ubuntu1

---------------
parted (2.2-5ubuntu1) lucid; urgency=low

  * Resynchronise with Debian. Remaining changes:
    - gptsync.dpatch: On Intel Mac systems, write a synced MBR rather than a
      protective MBR.
    - Add -fno-stack-protector on sparc.
    - loop-partitions.dpatch: Loop devices can only have one partition, so
      don't generate device names such as "/dev/loop0p1".
    - udevadm-settle.dpatch: Run 'udevadm settle' either side of rereading
      the partition table, to avoid a variety of races.
    - dmraid.dpatch: Ensure that device-mapper devices for dmraid arrays do
      not have extra nodes created needlessly, as well as making sure that
      partition nodes for dmraid devices are not probed.
    - put-back-BLKPG.patch: Upstream removed the code using the new BLKPG
      ioctls instead of the old BLKRRPART ioctl to update the in-kernel
      partition table. This patch reverses that change.
    - error-check-BLKPG.patch: Add error checking to the BLKPG code to fix
      up the old BLKPG code to satisfy upstream.
    - extended-geom.patch: Always allow at least two sectors for extended
      boot record.

parted (2.2-5) unstable; urgency=low

  * Fix brown-paper-bag build error in kFreeBSD patch.

parted (2.2-4) unstable; urgency=low

  * Policy version 3.8.4: no changes required.
  * Merge from maint-1.8 branch:
    - Version libparted[12] conflicts/replaces in preparation for
      upstream-maintained sonames in 2.2 and newer.
  * Rename libparted0 to libparted0debian1 (LP: #535368), and also
    libparted0-dbg to libparted0debian1-dbg in case anything is relying on
    those package names matching. This is unfortunate, but is needed to
    work around historical unversioned Conflicts on libparted0, libparted1,
    and libparted2, which would break upgrades from lenny. Add a dummy
    libparted0 package to provide smooth upgrades from earlier 2.2-*
    versions.

parted (2.2-3) unstable; urgency=low

  * Restore GNU/kFreeBSD support (closes: #575007).
  * Don't rebuild autotools files during the build.
  * Guard against FreeBSD kern.geom.conftxt not being newline-terminated.
  * Fix FreeBSD support for file devices.
  * Add GPT device naming support on kFreeBSD (thanks, Robert Millan;
    closes: #548436).
  * Strings from struct ata_params are not guaranteed to be null terminated
    (thanks, Aurelien Jarno; closes: #559645).

parted (2.2-2) unstable; urgency=low

  * Upload to unstable.
 -- Colin Watson <email address hidden> Tue, 06 Apr 2010 12:38:46 +0100

Changed in parted (Ubuntu Lucid):
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.