The following packages will be upgraded: libcairo-gobject2 libcairo-script-interpreter2 libcairo2 libcairo2-dev 4 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. After this operation, 12,3 k B disk space will be freed. [Y/n] Get:1 https://download.01.org/gfx/ubuntu/16.10/main yakkety/main amd64 libcairo2 amd64 1.15.2-0intel1 [568 k B] Err:1 https://download.01.org/gfx/ubuntu/16.10/main yakkety/main amd64 libcairo2 amd64 1.15.2-0intel1 Hash Sum mismatch Hashes of expected file: - SHA26ffe6dd23ed29c03295f86d8aca62981b85cc2dee42ed47f7fd61949b2fa13 - SHAc3d1e510af79c9cdc6b2204e61ec5cbb5f2c23 [weak] - MD5Sum:84bbaf1c1c20554bc033dccb4170095a [weak] - Checksum-File Size:568080 [weak] Hashes of received file: - SHA256:cc21a8a43200a3d35624e0bd23849ca30c50ef255fb37ed7502cfa8c6ca34381 - SHA0e49e1339734a385cbffca29485d6e866643e7 [weak] - MD5Sum:7c853ef25e2ecf23f9774dba49d39a2d [weak] - Checksum-File Size:568080 [weak] Last modification reported: Wed, 0000 Get:2 https://download.01.org/gfx/ubuntu/16.10/main yakkety/main amd64 libcairo-gobject2 amd64 1.15.2-0intel1 [134 k B] Err:2 https://download.01.org/gfx/ubuntu/16.10/main yakkety/main amd64 libcairo-gobject2 amd64 1.15.2-0intel1 Hash Sum mismatch Hashes of expected file: - SHA256:c6b3b0670e833d16bd42355550dd3ceeb1567a540c1d8756da4af8359cca746d - SHA350d583bbebd0d946e243bfa5da3c1b8464271 [weak] - MD5Sum:7fb0231133cee558fa8f7dea48b38b14 [weak] - Checksum-File Size:133758 [weak] Hashes of received file: - SHA256:3d50aa89644a9a79ce8d56a22f33ada99b00aa5634ef306fd07c4994ba7a701e - SHAf5eba1d34782ab2a36ea96cbc0d67fa3b36baf [weak] - MD5Sum:086ef35715963d3c674a5a654d4923bf [weak] - Checksum-File Size:133758 [weak] Last modification reported: Wed, 0000 Fetched 702 k B in 1s (366 k B/s) I think this issue will be fixed soon, but for now you can go to Software & Updates, activate "Other Software" tab and deselect this one https://download.01.org/gfx/ubuntu/16.10/main I just tried it, and it works.When I update suuuuuper old Chromium repositories, I occasionally get that stupid Checksum mismatch from svn.Since the project was only a week old, we ended up deleting and recreating it, but this could have been a lot worse had this been a project with a lot of history.I've dealt with repository corruption before, but some of the behavior I saw when diagnosing the repository really throws me for a loop, and I'm hoping to gain some insight into what might have happened.I have a backup of the repository so I am able to pull whatever information may necessary for diagnosis.We are currently using SCM Manager to host Subversion and Git projects, but we haven't seen anything like this happen since we started using SCM Manager as a source control platform.That's the technical difference, but as far as I can tell, they are semantically the same thing.
But this allowed such manipulation as I described above.
Generally, corrupted revisions fail to be updated to, which is why I'm very confused as to what has happened here.
This is the strangest repository issue I've seen in 6 years, and I'm hoping someone more knowledgeable than I can help me gain insight into what might have gone wrong.
It happens often enough that it's a thing, but uncommonly enough that I forget how to fix it each time.
So, FOR PROSPERITY: Then proooobably what happens was search_downloaded wonky or something such that the hash no longer came to be the correct thing.