nextcloud / nextcloud/files_mindmap
integrity problem - signature.json
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 197
- Forks
- 52
- Avg merge
- 22h 14m
- Merged PRs (30d)
- 13
Description
Similar to issue #123 I got a problem after installing version 0.0.22 on an NC 19,0,1 server. The integrity check before installing the app was ok, afterwards it says
`Technical information
The following list covers which files have failed the integrity check. Please read
the previous linked documentation to learn more about the errors and how to fix
them.
Results
- core
- EXTRA_FILE
- core/img/filetypes/mindmap.svg
- EXTRA_FILE
Raw output
Array
(
[core] => Array
(
[EXTRA_FILE] => Array
(
[core/img/filetypes/mindmap.svg] => Array
(
[expected] =>
[current] => b0484953431f937d2f10f8a8e526498763275691bda9252179c5b386ed94fbff95cc635022940b32f10c52afc15112774c158464b4853b4224ff9a7b8f650d0c
)
)
)
)`
I found out that the file mindmap.svg has been copied to ./core/img/filetypes/ by the installation script but it seems to me that the ./core/signature.json file has not been updated accordingly and I have no clue if this is possible at all or how to do this...
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Compare core/img/filetypes/mindmap.svg with core/signature.json and inspect the installation script that copies the file. Determine how the package integrity data is generated or updated, then reproduce the installation and confirm the integrity check no longer reports EXTRA_FILE.
Written by the indexing model from the issue text.
Assessment
- Domain
- release
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100