Upgrading via Apper (ex-KPackageKit) becomes impossible on ArchLinux after a few packages moved to the extra repository from community. Pacman handles this by presenting a simple Y/n question to the user, of which Apper doesn't seem capable of.
In case it's an Apper bug, then sorry for the noise, but please do let me know and I'll file it at bugs.kde.org.
(In reply to comment #0)
> by presenting a simple Y/n question to the user
What is the question you're asking the user?
pacman asks for confirmation.
:: Replace farsight2 with extra/farstream? [Y/n] y
:: Replace telepathy-farsight with extra/telepathy-farstream? [Y/n] y
:: Replace telepathy-qt4 with extra/telepathy-qt? [Y/n] y
I don't know the specifics as how it computes the replacement packages, but it looks that farsight2 was simply removed from the repos and the only package that was able to satisfy some dependency was extra/farstream. (And so on for the other ones.)
(In reply to comment #2)
> :: Replace farsight2 with extra/farstream? [Y/n] y
> :: Replace telepathy-farsight with extra/telepathy-farstream? [Y/n] y
> :: Replace telepathy-qt4 with extra/telepathy-qt? [Y/n] y
How do you decide if it's safe to say 'y' for each entry?
I just blindly hit y!
But it's because the changes seem harmless, and - I haven't tried, but saying no would mean using a package no longer maintained: http://www.archlinux.org/packages/?q=farsight2 vs. http://www.archlinux.org/packages/extra/x86_64/farstream/ .
These moves are not too common, but happen frequently enough that they're not surprising. (As Arch developers come and go, packages and projects get more or less care.)
(In reply to comment #4)
> I just blindly hit y!
Right, so that's what PackageKit should do under the scenes. Just make the default answer to be y, or provide a way to set the answer in the pacman API. This probably means somebody familiar with pacman should patch the PackageKit backend.
I've tried to add Jonathan Conder to the cc list, but bugzilla wasn't cooperating :)
We moved the upstream bugtracker to GitHub a long time ago. If this issue still affects you please re-create the issue here: https://github.com/hughsie/PackageKit/issues
Sorry for the impersonal message, and fingers crossed your issue no longer happens. Thanks.