[GH-ISSUE #7190] [Bug] AUR b2sum doesn't match #3181

New issue

Closed

opened 2026-03-23 21:28:09 +00:00 by mirror · 1 comment

mirror commented

2026-03-23 21:28:09 +00:00

Owner

Originally created by @dernikolas on GitHub (Jan 11, 2025).
Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/7190

Bug Description

When I try to install AppFlowy via the AUR (yay) this error occurs (it was German, I translated)

==> Checking source files with b2sums...
    LICENSE ... Sucess
    AppFlowy-0.8.0-linux-x86_64.deb ... ABORTED
==> ERROR: One or more files did not pass the validity check!
 -> Error downloading sources: /home/nikolas/.cache/yay/appflowy-bin 
         context: exit status 1

It was already commented at the appflowy-bin AUR page

How to Reproduce

Do yay -S appflowy-bin

Expected Behavior

AppFlowy get`s installed/updated

Operating System

CachyOS (Arch based) Linux

AppFlowy Version(s)

0.8.0

Screenshots

No response

Additional Context

No response

Originally created by @dernikolas on GitHub (Jan 11, 2025). Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/7190 ### Bug Description When I try to install AppFlowy via the AUR (yay) this error occurs (it was German, I translated) ``` ==> Checking source files with b2sums... LICENSE ... Sucess AppFlowy-0.8.0-linux-x86_64.deb ... ABORTED ==> ERROR: One or more files did not pass the validity check! -> Error downloading sources: /home/nikolas/.cache/yay/appflowy-bin context: exit status 1 ``` It was already commented at the appflowy-bin [AUR page](https://aur.archlinux.org/packages/appflowy-bin#comment-1006192) ### How to Reproduce 1. Do `yay -S appflowy-bin` ### Expected Behavior AppFlowy get`s installed/updated ### Operating System CachyOS (Arch based) Linux ### AppFlowy Version(s) 0.8.0 ### Screenshots _No response_ ### Additional Context _No response_

mirror closed this issue

2026-03-23 21:28:09 +00:00

mirror commented

2026-03-23 21:28:10 +00:00

Author

Owner

@khorshuheng commented on GitHub (Jan 12, 2025):

We don't maintain the AUR package, so we won't be able to fix this on our end.

@khorshuheng commented on GitHub (Jan 12, 2025): We don't maintain the AUR package, so we won't be able to fix this on our end.