Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Integrity check fail after updating 10.0.3 -> 10.0.4 #30229

Closed
sagamusix opened this issue Jan 22, 2018 · 4 comments
Closed

Integrity check fail after updating 10.0.3 -> 10.0.4 #30229

sagamusix opened this issue Jan 22, 2018 · 4 comments

Comments

@sagamusix
Copy link

sagamusix commented Jan 22, 2018

I am using the ownCloud 10 debian package repository.
After updating from 10.0.3 to 10.0.4, a stray file is reported in the integrity check:

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
=======
- market
	- EXTRA_FILE
		- README.md

Raw output
==========
Array
(
    [market] => Array
        (
            [EXTRA_FILE] => Array
                (
                    [README.md] => Array
                        (
                            [expected] => 
                            [current] => b53ebb407cb90a5cf9e28463013f38e6aec3d39b4281187366e02b5fd014be144216a088fc50851635acc50cb71c92ad2407b21e8a4f3433b0f73a32ea066c97
                        )

                )

        )

)
@DeepDiver1975
Copy link
Member

quickfix:
rm apps/market/README.txt

@DeepDiver1975
Copy link
Member

@crrodriguez looks like there is some cleanup during migration missing ....

@ownclouders
Copy link
Contributor

Hey, this issue has been closed because the label status/STALE is set and there were no updates for 7 days. Feel free to reopen this issue if you deem it appropriate.

(This is an automated comment from GitMate.io.)

@lock
Copy link

lock bot commented Jul 31, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Jul 31, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants