On Tue, May 12, 2009 at 11:19 AM, Luca Capello <[email protected]> wrote: > Package: python-ecore > Version: 0.2.1-2 > Severity: important > User: [email protected] > Usertags: package-dependencies > > Hi there! > > Since the last E17 libraries upload (0.9.9.060-1), python-ecore cannot > be installed anymore: > ===== > (sid-amd64)r...@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)r...@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-0.9.9.050a, 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. Regards, Albin -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
