Integrity check fails when updating from 9.0.{0,1} to 9.0.3 #358

Closed
PVince81 opened this Issue Jul 4, 2016 · 3 comments

Projects

None yet

1 participant

@PVince81
Contributor
PVince81 commented Jul 4, 2016

Update from 9.0.0 or 9.0.1 to 9.0.3 using a local update server that delivers 9.0.3.

The 9.0.3 version will have integrity check failures that don't disappear on rescan:

- core
    - INVALID_HASH
        - 3rdparty/sabre/dav/composer.json
        - 3rdparty/sabre/dav/lib/CalDAV/Plugin.php
        - 3rdparty/sabre/dav/lib/DAV/Version.php
        - 3rdparty/sabre/dav/lib/DAV/CorePlugin.php
        - 3rdparty/sabre/dav/lib/CardDAV/Backend/PDO.php
        - 3rdparty/sabre/dav/CHANGELOG.md
        - 3rdparty/composer/LICENSE
        - 3rdparty/composer/installed.json
        - 3rdparty/composer/autoload_classmap.php
        - 3rdparty/composer.lock
        - 3rdparty/composer.json

However updating from 9.0.2 to 9.0.3 works fine.

Unfortunately we can't make the updater force to go to 9.0.2 first due to encryption issues #350

@VicDeo @DeepDiver1975

@PVince81 PVince81 added this to the 9.0.4 milestone Jul 4, 2016
@PVince81
Contributor
PVince81 commented Jul 4, 2016

As discussed on IRC, @VicDeo said this is a regression.

@PVince81 PVince81 referenced this issue in owncloud/QA Jul 4, 2016
Open

Automated tests for updater app #268

@PVince81
Contributor
PVince81 commented Jul 4, 2016

Raised owncloud/QA#268 to have this covered by automated tests

@PVince81
Contributor

We merged the revert => close

@PVince81 PVince81 closed this Jul 12, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment