packagekit errors

justin-8 · 2016-02-11 09:13:38

I'm trying to use gnome-packagekit, and I have the infinality repos enabled. I was getting this error http://i.imgur.com/bO73fsg.png

So I tried commenting out all the relevant lines in pacman.conf, and the error remained. So I ran `sudo rm -rf /var/lib/pacman/sync/*` to clear the sync databases, but the error remains. `pacman -Sy` still works as expected and all the databases say up to date, but package kit still complains about the no longer installed repo for infinality.

So does anyone know how to fix this? or even just where packagekit thinks it is reading pacman configurations from? becuase it doesn't seem to be the same place as pacman.

Last edited by justin-8 (2016-02-11 09:14:08)

ayekat · 2016-02-11 09:43:04

Could you please post your pacman.conf for a start?

justin-8 · 2016-02-11 22:50:09

Of course, here it is: https://paste.ee/r/rybPr

Trilby · 2016-02-11 23:59:19

You should probably remove the relevant package(s) from that repo as well, or you'll end up with partial upgrades. Then clear your cache as it might be checking a cached package file ready for installation.

justin-8 · 2016-02-12 00:36:33

I disabled it for testing, not permanently. The problem is that packagekit still complains about repos that are no longer enabled.

As I put in the original post, I also cleared /var/lib/pacman/sync which has the package databases. pacman works as expected, no extraneous databases, just packagekit complains about it.

I also tried to remove /var/cache/packagekit and it gets recreated on next run, but it doesn't seem to actually update, it continues with the same errors regardless.

Trilby · 2016-02-12 00:50:39

So you aren't going to try my suggestions? Clearing the sync databases does not get rid of all the data about the packges. They are still installed, and they are still cached. But if you think you know what the problem is, I'll leave you to fix it.

justin-8 · 2016-02-12 03:13:06

The packages being installed doesn't affect the state of the databases. But to humour the suggestion, I tried it and have the same issue. Since it is to do with the package databases, and not another package.

Package info stored in the pacman database doesn't include where it is installed from, the packages from infinality such as ttf-caladea-ib-20130214-6 have their data in /var/lib/pacman/local/ttf-caladea-ib-20130214-6, none of which describes the repository; as you would expect. Without a repo it is treated the same as any AUR package, and would not be 'partial' since they would get included when I update AUR packages instead. They would just show as an orphan package in `pacman -Qm`.

So please don't make terrible suggestions, acting like you understand the problem when you clearly do not, then get snappy when someone notices that they are useless.

Arch Linux

#1 2016-02-11 09:13:38

packagekit errors

#2 2016-02-11 09:43:04

Re: packagekit errors

#3 2016-02-11 22:50:09

Re: packagekit errors

#4 2016-02-11 23:59:19

Re: packagekit errors

#5 2016-02-12 00:36:33

Re: packagekit errors

#6 2016-02-12 00:50:39

Re: packagekit errors

#7 2016-02-12 03:13:06

Re: packagekit errors

Board footer