On 09/08/2016 04:15 PM, David Runge wrote: > So... is there any way to get the package updated now?
I have no idea, I was just speculating as to the causes. And I speculate that the package was not properly purged from community, and the AUR configuration thinks it is still there and thus should not be allowed to be updated by a non-TU. You *will* need a TU to un-blacklist the package, whyever it happened. -- Eli Schwartz
