| 2012-07-06 22:19:33 |
Michael Rawson |
bug |
|
|
added bug |
| 2012-07-12 09:50:38 |
Sergey "Shnatsel" Davidoff |
bug task added |
|
aptdaemon |
|
| 2012-07-12 09:52:39 |
Sergey "Shnatsel" Davidoff |
bug task added |
|
packagekit (Ubuntu) |
|
| 2012-07-12 09:52:59 |
Launchpad Janitor |
packagekit (Ubuntu): status |
New |
Confirmed |
|
| 2012-07-12 13:47:28 |
Matthias Klumpp |
packagekit (Ubuntu): status |
Confirmed |
Invalid |
|
| 2012-07-12 13:47:46 |
Matthias Klumpp |
bug |
|
|
added subscriber Matthias Klumpp |
| 2012-07-12 14:54:46 |
Sergey "Shnatsel" Davidoff |
bug task added |
|
aptdaemon (Ubuntu) |
|
| 2012-07-12 16:24:20 |
Sergey "Shnatsel" Davidoff |
description |
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? :D
Seriously, in event of...whatever this is, shouldn't the database script move on to the next item rather than stopping entirely? |
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.
Does not happen with packagekit-backend-aptcc but happens with python-aptdaemon.pkcompat |
|
| 2012-07-12 16:28:03 |
Sergey "Shnatsel" Davidoff |
summary |
dbbuild fails with "could not be resolved" |
python-aptdaemon.pkcompat cannot resolve some packages |
|
| 2012-09-30 12:32:32 |
Sebastian Heinlein |
aptdaemon: status |
New |
Incomplete |
|
| 2012-09-30 12:32:34 |
Sebastian Heinlein |
aptdaemon (Ubuntu): status |
New |
Incomplete |
|
