You are not logged in.
I can update my system fine with pacman, and yaourt. If I try to use powerpill or bauerbill I just get bunch of warning on local packages being ahead of repo versions, and an error on one, zsh-syntax-highlighting, the community packages.
error: could not parse package description file 'zsh-syntax-highlighting-0.4.1-1/desc'
from db 'community'
I tried running pacman -Syy through all 4 applications, and uninstalling zsh-syntax-highlighting, powerpill and bauerbill, with no luck so far. When I reinstalled them the issue just came back.
Anyone have any ideas?
Last edited by zerophase (2016-06-12 17:12:40)
Offline
What's in that file?
Offline
I don't know. It's just theming for zsh. I can't find /desc with locate.
Offline
It would be in /var/lib/pacman/local/zsh-syntax-highlighting-0.4.1-1/
Offline
It doesn't show up there.
I do see it showing up in the abs folder. Go ahead an delete it from there?
Offline
There's no desc file in that dir? And reinstalling zsh-syntax-highlighting doesn't create it?
The ABS should be irrelevant here.
Offline
Yeah, that desc file doesn’t exist. And reinstalling doesn't create it. Isn't desc a file in the repo?
Last edited by zerophase (2016-06-11 13:50:07)
Offline
I'm getting the same error.
Is this something to do with /var/lib/pacman/sync/community.db ?
cat /var/lib/pacman/sync/community.db | gunzip - 1>/dev/null
gzip: stdin: unexpected end of file
Offline
I'm getting the same error.
Is this something to do with /var/lib/pacman/sync/community.db ?cat /var/lib/pacman/sync/community.db | gunzip - 1>/dev/null
gzip: stdin: unexpected end of file
Does that command you put in fix the issue?
Offline
I was having this issue but changing my default mirror fixed it.
Edit: well, not this exact issue as I don't use powerpill or bauerbill but i was getting the error
error: could not parse package description file 'zsh-syntax-highlighting-0.4.1-1/desc' from db 'community'
and that was solved by changing mirrors.
Last edited by Ziusudra (2016-06-12 11:11:42)
Offline
Fixed it just had to update all of the rsync servers in use. Odd considering all of the old rsync servers were considered up to date.
Offline
Sorry for not replying.
I did a: pacman -Syy to re-sync the database files just now and no longer get this issue.
Thanks
Offline