Bug 911270 - 0install should be updated to version 1.14 at least because of PackageKit API incompatibility
Summary: 0install should be updated to version 1.14 at least because of PackageKit API...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: zeroinstall-injector
Version: 18
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Michel Lind
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-02-14 16:00 UTC by Mildred
Modified: 2013-03-26 16:40 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-03-16 01:35:27 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Mildred 2013-02-14 16:00:10 UTC
Description of problem: 0install fails when it needs to rely on PackageKit because it can't talk with it. The API has changed. The new API is incompatible with the previous one.

Version-Release number of selected component (if applicable):
zeroinstall-injector-1.13-1.fc18.noarch

How reproducible: always

Steps to Reproduce:
1. 0alias 0compile http://0install.net/2006/interfaces/0compile.xml
2. 0compile autocompile http://mildred.fr/2012/0install/Trojita.xml
  
Actual results:
Can't satisfy dependency for http://gfxmonk.net/dist/0install/qmake-qt4.xml (which requires PackageKit)

Expected results:
Dependency satisfied

Additional info:
A stack trace can be triggered by running 0install run http://gfxmonk.net/dist/0install/qmake-qt4.xml (although I don't know what it is supposed to do). The error is:

DBusException: org.freedesktop.DBus.Error.UnknownMethod: No such method `GetTid'

It has been reported on the 0install mailing list and the version 1.14 supports the new PackageKit API: http://thread.gmane.org/gmane.comp.file-systems.zero-install.devel/6629

Comment 2 Michel Lind 2013-03-06 07:48:26 UTC
Apologies; an F18 build has been done but not yet pushed. Could you verify that this work?

http://koji.fedoraproject.org/koji/buildinfo?buildID=398264

Will push the update in a few minutes, please up-karma it then if it works for you.

Comment 3 Fedora Update System 2013-03-06 08:47:23 UTC
zeroinstall-injector-2.0-1.fc17 has been submitted as an update for Fedora 17.
https://admin.fedoraproject.org/updates/zeroinstall-injector-2.0-1.fc17

Comment 4 Fedora Update System 2013-03-06 08:47:49 UTC
zeroinstall-injector-2.0-1.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/zeroinstall-injector-2.0-1.fc18

Comment 5 Fedora Update System 2013-03-06 08:48:03 UTC
zeroinstall-injector-2.0-1.el6 has been submitted as an update for Fedora EPEL 6.
https://admin.fedoraproject.org/updates/zeroinstall-injector-2.0-1.el6

Comment 6 Fedora Update System 2013-03-06 22:57:46 UTC
Package zeroinstall-injector-2.0-1.fc17:
* should fix your issue,
* was pushed to the Fedora 17 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing zeroinstall-injector-2.0-1.fc17'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-3488/zeroinstall-injector-2.0-1.fc17
then log in and leave karma (feedback).

Comment 7 Fedora Update System 2013-03-16 01:35:29 UTC
zeroinstall-injector-2.0-1.fc18 has been pushed to the Fedora 18 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 8 Fedora Update System 2013-03-16 01:38:12 UTC
zeroinstall-injector-2.0-1.fc17 has been pushed to the Fedora 17 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 9 Fedora Update System 2013-03-26 16:40:48 UTC
zeroinstall-injector-2.0-1.el6 has been pushed to the Fedora EPEL 6 stable repository.  If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.