Summary: | akonadictl fsck: optional show metadata for affected items to aid user to fix up things manually | ||
---|---|---|---|
Product: | [Frameworks and Libraries] Akonadi | Reporter: | Martin Steigerwald <Martin> |
Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED INTENTIONAL | ||
Severity: | normal | CC: | dvratil |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Other | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Martin Steigerwald
2018-01-29 17:10:10 UTC
This should be optional for privacy reasons. (i.e. when sharing with other users or in a bug report for help). Metadata for mail probably should include Message-Id. This would be a major effort and something that's not easily achievable with the current architecture. "akonadictl fsck" is a service inside the akonadiserver and therefore it has no knowledge about the payload format - IOW it does not understand "MIME" or "iCal" or "vCard" formats, it simply sees the payload as a binary blob. At the same time, this tool cannot be easily re-implemented outside of the akonadiserver (so that it would be able to understand payload formats) because it directly interacts with the SQL database, which cannot be safely done from outside of the akonadiserver process. Okay, Dan. Considering your comment I think it is not beneficial to keep this bug report open. akonadictl fsck appears to be a developer tool and maybe users should not even use it. That leaves that Akonadi shall be able to fix up inconsistencies by itself, or avoid creating inconsistencies in the first place by using atomic operations and roll-back but that is for other bug reports. |