Failed to install. Broken dependency with python 2.6

Bug #338966 reported by Matt Layman
2
Affects Status Importance Assigned to Milestone
python-imdbpy (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: python-imdbpy

Binary package hint: python-imdbpy

$ sudo apt-get install python-imdbpy
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:
  python-imdbpy: Depends: python (< 2.6) but 2.6.1-0ubuntu3 is to be installed
E: Broken packages

$ apt-cache policy python-imdbpy
python-imdbpy:
  Installed: (none)
  Candidate: 3.8-1
  Version table:
     3.8-1 0
        500 http://us.archive.ubuntu.com jaunty/universe Packages

$ lsb_release -rd
Description: Ubuntu jaunty (development branch)
Release: 9.04

I attempted to install this from a fully updated Jaunty alpha system.

Tags: python2.6

Related branches

Revision history for this message
David Futcher (bobbo) wrote :

I'm not sure why, but Launchpad hasn't automatically closed this bug. This should be fixed as of the latest uploaded version.

Revision history for this message
Matt Layman (mblayman) wrote : Re: [Bug 338966] Re: Failed to install. Broken dependency with python 2.6

On Sat, Mar 7, 2009 at 4:04 PM, David Futcher <email address hidden>wrote:

> I'm not sure why, but Launchpad hasn't automatically closed this bug.
> This should be fixed as of the latest uploaded version.
>
> --
> Failed to install. Broken dependency with python 2.6
> https://bugs.launchpad.net/bugs/338966
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “python-imdbpy” source package in Ubuntu: New
>
> Bug description:
> Binary package hint: python-imdbpy
>
> Binary package hint: python-imdbpy
>
> $ sudo apt-get install python-imdbpy
> 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:
> python-imdbpy: Depends: python (< 2.6) but 2.6.1-0ubuntu3 is to be
> installed
> E: Broken packages
>
> $ apt-cache policy python-imdbpy
> python-imdbpy:
> Installed: (none)
> Candidate: 3.8-1
> Version table:
> 3.8-1 0
> 500 http://us.archive.ubuntu.com jaunty/universe Packages
>
> $ lsb_release -rd
> Description: Ubuntu jaunty (development branch)
> Release: 9.04
>
> I attempted to install this from a fully updated Jaunty alpha system.
>

Is it because this is related to python-imdbpy and not python-clutter? I
created two separate bugs with identical bug titles, but they affected
different packages. The python-clutter one was marked Fixed Released
automatically.

Revision history for this message
David Futcher (bobbo) wrote :

Think I have worked it out. The python-imdbpy source package (which this bug is reported under) only exists in Dapper. The bug should have been reported under the imdbpy source package, which builds the binary package python-imdbpy. Therefore I have fixed this (I uploaded a fixed imdbpy sourcepackage), so will mark it as fixed. Please try to see if you can replicate this bug on a fully updated Jaunty to make sure I haven't messed anything up here.

Changed in python-imdbpy:
status: New → Fix Released
Revision history for this message
Matt Layman (mblayman) wrote :

I have attempted to replicate the bug on an up-to-date Jaunty machine and I can confirm that it is no longer an issue. On behalf of the Entertainer Media Center developers, thanks for fixing this.

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.