[Pkg-e-devel] Bug#528339: [pkg-fso-maint] Bug#528339: python-ecore: not installable because of missing E17 dependencies

Albin Tonnerre albin.tonnerre at gmail.com
Tue May 12 20:06:30 UTC 2009

On Tue, May 12, 2009 at 11:19 AM, Luca Capello <luca at pca.it> wrote:
> Package: python-ecore
> Version: 0.2.1-2
> Severity: important
> User: pkg-fso-maint at lists.alioth.debian.org
> Usertags: package-dependencies
> Hi there!
> Since the last E17 libraries upload (, python-ecore cannot
> be installed anymore:
> =====
> (sid-amd64)root at gismo:/$ apt-get install python-ecore
> [...]
> The following packages have unmet dependencies:
>  python-ecore: Depends: libecore-evas0 but it is not installable
>                Depends: libecore-fb0 but it is not installable
>                Depends: libecore-x0 but it is not installable
>                Depends: libecore0 but it is not installable
> E: Broken packages
> (sid-amd64)root at gismo:/$
> =====
> This because the new libecore* packages have changed their name:

Indeed, but they've been broken for far longer than the last upload, as
libecore0 moved to libecore-, in december. Nikita uploaded
updated python-* to pkg-fso, that's why the issue hasn't showed up
until now.
I'll update python-* during the weekend if I have some time to merge
nikita's work

> Strangely enough, while other E17 libraries from the same snapshot
> provides the old libraries names (e.g. libevas-svn-01 -> libevas0),

libevas is a special case, it contains file whose name do not change
between versions. the conflict/replaces is here only to ensure that
only of the packages containing those files is installed at a time

> this
> is not the case for the ecore ones.
> While a better thing would have
> been to file this bug to ecore instead, I guess that there is a specific
> reason for this situation.

Why would it have been better ? it's not a bug in ecore, python-ecore is
actually outdated.


More information about the Pkg-e-devel mailing list