In regards to the aforementioned issue, we believe this is due to
local Redis instance going away for a short time. This is not a
common occurrence, and so this should not affect users most of the
time. That being said, we will be accounting for this in our code to
rid users of receiving the error
Hi AURers,
I've got a bit of a status update for all of you users regarding the
state of the newly released >= v6.0.0 aurweb.
It took a matter of days to get several quirks worked out, which were
a result of a few reasons:
- AUR historical database state not seen on local systems which the
port w
