mirror of
https://github.com/cypht-org/cypht.git
synced 2026-04-24 20:46:04 +03:00
[GH-ISSUE #1853] 🐛 [Bug] ARM64 v2.6.0 image ss 2.5.2 #726
Labels
No labels
2fa
I18N
PGP
Security
Security
account
advanced_search
advanced_search
announcement
api_login
authentication
awaiting feedback
blocker
bug
bug
bug
calendar
config
contacts
core
core
devops
docker
docs
duplicate
dynamic_login
enhancement
epic
feature
feeds
framework
github
github
gmail_contacts
good first issue
help wanted
history
history
imap
imap_folders
inline_message
installation
keyboard_shortcuts
keyboard_shortcuts
ldap_contacts
mobile
need-ssh-access
new module set
nux
pop3
profiles
pull-request
question
refactor
release
research
saved_searches
smtp
strategic
tags
tests
themes
website
wordpress
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/cypht#726
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Marsu31 on GitHub (Feb 8, 2026).
Original GitHub issue: https://github.com/cypht-org/cypht/issues/1853
Originally assigned to: @IrAlfred on GitHub.
🐛 Bug
When entering the application an information message says:
You are currently running Cypht version 2.5.2. A higher version (2.6.0) is available.
Version & Environment
Rev: image: cypht/cypht:2.6.0
OS: DietPi v10.0.1 (on Rock Pi S)
I suspect a really bad version in the sources (it is really a v2.5.2 version) because I have a problem with sieve filter that I thought has been corrected in v2.6.0. Indeed, the list gives 0 filter instead of 7.
Regards
@IrAlfred commented on GitHub (Feb 9, 2026):
Related to https://github.com/cypht-org/cypht/issues/1838
@IrAlfred commented on GitHub (Feb 9, 2026):
Hello @Marsu31,
Please make sure the sieve filter issue is not related to your current setup.
Provide more details about the original sieve filter problem?
With that information, I can locate the relevant pull request where the fix was implemented and investigate further.