libgpod-nogtk can't be upgraded in hardy

Bug #188212 reported by kivan
2
Affects Status Importance Assigned to Milestone
libgpod (Ubuntu)
Fix Released
High
Steve Langasek

Bug Description

libgpod3-nogtk can't be upgraded from version 0.6.0-3 to version 0.6.0-3ubuntu1 because libgpod-common depends on libgpod3. It should depend on libgpod3 | libgpod3-nogtk.

ProblemType: Bug
Architecture: amd64
Date: Sat Feb 2 00:08:35 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/sbin/synaptic
NonfreeKernelModules: nvidia
Package: synaptic 0.61ubuntu4
PackageArchitecture: amd64
ProcCmdline: /usr/sbin/synaptic
ProcCwd: /home/mario
ProcEnviron:
 LANGUAGE=it
 PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/lib/kde4/bin:/home/mario/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
SourcePackage: synaptic
Uname: Linux tanis 2.6.24-5-generic #1 SMP Thu Jan 24 19:29:14 UTC 2008 x86_64 GNU/Linux

Tags: apport-bug
Revision history for this message
Steve Langasek (vorlon) wrote :

libgpod-nogtk depends on libgpod-common, which depends on libgpod-gtk (due to shlibs), which conflicts with libgpod-nogtk.

Since libgpod-common contains binaries that need libgpod itself to run, the circular dependency can't be dropped, but instead libgpod-common needs to be fixed so it can use either variant of the library.

Changed in libgpod:
assignee: nobody → vorlon
importance: Undecided → High
milestone: none → hardy-alpha-6
status: New → Confirmed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package libgpod - 0.6.0-3ubuntu2

---------------
libgpod (0.6.0-3ubuntu2) hardy; urgency=low

  * When running dh_shlibdeps, use libgpod3-nogtk instead of libgpod3;
    this makes libgpod3-nogtk installable again, now that libgpod-common
    no longer depends on a package that conflicts with it. LP: #188212.

 -- Steve Langasek <email address hidden> Thu, 28 Feb 2008 19:40:02 +0000

Changed in libgpod:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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