-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
rpm package: Some files have not passed the integrity check. #31703 #32078
Comments
GitMate.io thinks possibly related issues are #24652 (Some files have not passed the integrity check), #31703 (rpm package: Some files have not passed the integrity check.), #30332 (failed the integrity check), #23615 (some files have not passed the integrity check - .htaccess), and #24698 (Some files have not passed the integrity check -- INVALID_HASH). |
Yes, its the same issue as 31703, which was closed by an automated process. |
ownCloud has an own signature system which checks the integrity of the files. this is useful to detect whenever people to manual upgrades and forget for example to delete old files, or only partially updated files. this also means that any patching of the source files will cause integrity check. a better approach would be sending a PR with the proposed change in the occ command so we can put it in the next release and remove the need for patching |
also: sorry that we missed your other report. I'll tag this here as bug as we could say it's a bug in the occ command |
My point is that a rpm package from the owncloud project is shipped with a modified version of the occ command, which trips the signature check. I think the file which is now on github (and passes the signture checks) will work on FC28. That same file is also in the tar.bz2 file included in the src.rpm. I don't see anything obvious in the owncloud-files.spec file which hints at the file being altered. Perhaps its the rpm build process changing it? If that's the case then we may need to patch the signature list (included in the rpm) so it matches the file signature altered by the rpm build process. Links to the patches: https://www.eijk.nu/owncloud-files.spec.diff |
okay, then this is likely a bug @crrodriguez can you have a look ? |
@crrodriguez any update ? |
fixed in owncloud/administration@2dfa790 |
the 10.0.9 RPM file contains two files failing the integrity check: Technical informationThe following list covers which files have failed the integrity check. Please read Results
Raw outputArray
) |
@crrodriguez can you recheck or is it a mirror issue ? |
any update? |
looks like its fixed in owncloud-files-10.0.10-1.1.noarch |
@svde yes, should be fixed there already, packages of !current release are not fixed. |
created new issue because you have an automated process to close issues
I'm running owncloud on fedora 28, using the pachaes from the owncloud repo. It complains with:
Some files have not passed the integrity check. Further information on how to resolve this issue can be found in our documentation. (List of invalid files… / Rescan…)
and
The difference in the file is not significant:
The offending file (/var/www/html/owncloud/occ) does verify fine with rpm, which means that it's untouched. I'd like to understand why a file which doesn't pass ownclouds own integrity check is put into the rpm package provided by the owncloud project (https://download.owncloud.org/download/repositories/stable/owncloud/index.html). Would it be possible to exclude this file from the integrity checks in the rpm package?
The text was updated successfully, but these errors were encountered: