[Bug 1021960] Re: dbbuild fails with "could not be resolved"

2012-07-12 Thread Sergey "Shnatsel" Davidoff
** Description changed: - sudo ./dbbuild -d /var/cache/lsc-vala.db + sudo ./dbbuild -d /var/cache/lsc-vala.db Collecting app-install data... Querying PackageKit... ** (dbbuild:28222): ERROR **: dbbuild.vala:207: Error: Package name ardour-i686 could not be resolved. - What do I do?

[Bug 1021960] Re: dbbuild fails with "could not be resolved"

2012-07-12 Thread Sergey "Shnatsel" Davidoff
Mattias, thanks a lot for clearing that up! I've erroneously tracked down python-aptdaemon.pkcompat to packagekit ubuntu package and thus marked it affected. Reassigned to aptdaemon package now :) I've hit up the aptcc changelog linked above and it seems it did improve greatly since last time I ch

[Bug 1021960] Re: dbbuild fails with "could not be resolved"

2012-07-12 Thread Sergey "Shnatsel" Davidoff
** Also affects: aptdaemon (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1021960 Title: dbbuild fails with "could not be resolved" To manage not

Re: [Bug 1021960] Re: dbbuild fails with "could not be resolved"

2012-07-12 Thread Stephen Smally
I never used Xapian, so i don't know how to implement a database with it, also there are no bindings... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1021960 Title: dbbuild fails with "could not be

[Bug 1021960] Re: dbbuild fails with "could not be resolved"

2012-07-12 Thread Matthias Klumpp
Oh, btw: It appears that you're creating a completely new SQL db from raw data... It would probably make more sense and be a little bit faster to use the original Xapian database, as discussed in our AppStream[1] meeting. Unfortunately, the generator code to build the DB from AppStream XML or Ap

[Bug 1021960] Re: dbbuild fails with "could not be resolved"

2012-07-12 Thread Matthias Klumpp
Hi! That is not the fault of PackageKit, the compat layer is wrong and Ubuntu does some extremely crappy things, e.g. forcing the PyApt-backend in Ubuntu-Drivers, which is totally broken and has been removed (again) from distribution. (We weren't able to ship it in Debian with RC bugs) Btw, Aptd

[Bug 1021960] Re: dbbuild fails with "could not be resolved"

2012-07-12 Thread Sergey "Shnatsel" Davidoff
By the way I've got the same error for package "qtodo", see bug 1023808 So maybe this bug is not exclusive to multiarch. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1021960 Title: dbbuild fails wi

[Bug 1021960] Re: dbbuild fails with "could not be resolved"

2012-07-12 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: packagekit (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1021960 Title:

[Bug 1021960] Re: dbbuild fails with "could not be resolved"

2012-07-12 Thread Sergey "Shnatsel" Davidoff
Ubuntu uses python-aptdaemon.pkcompat by default instead; it bridges PackageKit interfaces into much more modern AptDaemon. See https://launchpad.net/aptdaemon for advantages over packagekit-backend- aptcc So it seems that that's a bug in python-aptdaemon.pkcompat now. ** Also affects: aptdaemon