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

Revert "Add more mirrors" #16973

Merged

Conversation

findepi
Copy link
Member

@findepi findepi commented Apr 12, 2023

This reverts commit 8bfe02a.

It was causing build problems of two kinds

  1. These repositories sometimes appear not correctly signed.
#11 33.78 E: The repository 'https://mirror.kumi.systems/ubuntu jammy InRelease' is not signed.
#11 33.78 E: Failed to fetch https://mirror.kumi.systems/ubuntu/dists/jammy/InRelease  502  Bad Gateway [IP: 135.181.208.35 443]
#11 33.78 E: The repository 'https://mirror.kumi.systems/ubuntu jammy-updates InRelease' is not signed.
#11 33.78 E: Failed to fetch https://mirror.kumi.systems/ubuntu/dists/jammy-updates/InRelease  502  Bad Gateway [IP: 135.181.208.35 443]
#11 33.78 E: The repository 'https://mirror.kumi.systems/ubuntu jammy-backports InRelease' is not signed.
#11 33.78 E: Failed to fetch https://mirror.kumi.systems/ubuntu/dists/jammy-backports/InRelease  502  Bad Gateway [IP: 135.181.208.35 443]
#11 33.78 E: The repository 'https://mirror.kumi.systems/ubuntu jammy-security InRelease' is not signed.
#11 33.78 E: Failed to fetch https://mirror.kumi.systems/ubuntu/dists/jammy-security/InRelease  502  Bad Gateway [IP: 135.181.208.35 443]
#11 33.78 E: The repository 'https://mirror.kumi.systems/ubuntu-ports jammy InRelease' is not signed.
#11 33.78 E: Failed to fetch https://mirror.kumi.systems/ubuntu-ports/dists/jammy/InRelease  502  Bad Gateway [IP: 135.181.208.35 443]
#11 33.78 E: The repository 'https://mirror.kumi.systems/ubuntu-ports jammy-updates InRelease' is not signed.
#11 33.78 E: Failed to fetch https://mirror.kumi.systems/ubuntu-ports/dists/jammy-updates/InRelease  502  Bad Gateway [IP: 135.181.208.35 443]
#11 33.78 E: Failed to fetch https://mirror.kumi.systems/ubuntu-ports/dists/jammy-backports/InRelease  502  Bad Gateway [IP: 135.181.208.35 443]
#11 33.78 E: The repository 'https://mirror.kumi.systems/ubuntu-ports jammy-backports InRelease' is not signed.
#11 33.78 E: Failed to fetch https://mirror.kumi.systems/ubuntu-ports/dists/jammy-security/InRelease  502  Bad Gateway [IP: 135.181.208.35 443]
#11 33.78 E: The repository 'https://mirror.kumi.systems/ubuntu-ports jammy-security InRelease' is not signed.
  1. These repositories sometimes appear to suffer from concurrency
    issues.
E: Failed to fetch https://mirror.kumi.systems/ubuntu/dists/jammy-updates/main/binary-amd64/by-hash/SHA256/e982b491ee116748562a4208918ced995d019a31bef367749e76ba53b86c3e66  File has unexpected size (1245184 != 1255827). Mirror sync in progress? [IP: 86.106.183.57 443]

Fixes #16972
Reverts part of #16098

This reverts commit 8bfe02a.

It was causing build problems of two kinds

1) These repositories sometimes appear not correctly signed.

    trinodb#11 33.78 E: The repository 'https://mirror.kumi.systems/ubuntu jammy InRelease' is not signed.
    trinodb#11 33.78 E: Failed to fetch https://mirror.kumi.systems/ubuntu/dists/jammy/InRelease  502  Bad Gateway [IP: 135.181.208.35 443]
    trinodb#11 33.78 E: The repository 'https://mirror.kumi.systems/ubuntu jammy-updates InRelease' is not signed.
    trinodb#11 33.78 E: Failed to fetch https://mirror.kumi.systems/ubuntu/dists/jammy-updates/InRelease  502  Bad Gateway [IP: 135.181.208.35 443]
    trinodb#11 33.78 E: The repository 'https://mirror.kumi.systems/ubuntu jammy-backports InRelease' is not signed.
    trinodb#11 33.78 E: Failed to fetch https://mirror.kumi.systems/ubuntu/dists/jammy-backports/InRelease  502  Bad Gateway [IP: 135.181.208.35 443]
    trinodb#11 33.78 E: The repository 'https://mirror.kumi.systems/ubuntu jammy-security InRelease' is not signed.
    trinodb#11 33.78 E: Failed to fetch https://mirror.kumi.systems/ubuntu/dists/jammy-security/InRelease  502  Bad Gateway [IP: 135.181.208.35 443]
    trinodb#11 33.78 E: The repository 'https://mirror.kumi.systems/ubuntu-ports jammy InRelease' is not signed.
    trinodb#11 33.78 E: Failed to fetch https://mirror.kumi.systems/ubuntu-ports/dists/jammy/InRelease  502  Bad Gateway [IP: 135.181.208.35 443]
    trinodb#11 33.78 E: The repository 'https://mirror.kumi.systems/ubuntu-ports jammy-updates InRelease' is not signed.
    trinodb#11 33.78 E: Failed to fetch https://mirror.kumi.systems/ubuntu-ports/dists/jammy-updates/InRelease  502  Bad Gateway [IP: 135.181.208.35 443]
    trinodb#11 33.78 E: Failed to fetch https://mirror.kumi.systems/ubuntu-ports/dists/jammy-backports/InRelease  502  Bad Gateway [IP: 135.181.208.35 443]
    trinodb#11 33.78 E: The repository 'https://mirror.kumi.systems/ubuntu-ports jammy-backports InRelease' is not signed.
    trinodb#11 33.78 E: Failed to fetch https://mirror.kumi.systems/ubuntu-ports/dists/jammy-security/InRelease  502  Bad Gateway [IP: 135.181.208.35 443]
    trinodb#11 33.78 E: The repository 'https://mirror.kumi.systems/ubuntu-ports jammy-security InRelease' is not signed.

2) These repositories sometimes appear to suffer from concurrency
   issues.

    E: Failed to fetch https://mirror.kumi.systems/ubuntu/dists/jammy-updates/main/binary-amd64/by-hash/SHA256/e982b491ee116748562a4208918ced995d019a31bef367749e76ba53b86c3e66  File has unexpected size (1245184 != 1255827). Mirror sync in progress? [IP: 86.106.183.57 443]
@findepi findepi merged commit 13e1819 into trinodb:master Apr 12, 2023
@findepi findepi deleted the findepi/revert-add-more-mirrors-b8e1c8 branch April 12, 2023 12:59
@github-actions github-actions bot added this to the 413 milestone Apr 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

Flaky docker build: "File has unexpected size"
3 participants