[MDEV-29303] MariaDB apt repo's are all broken Created: 2022-08-15  Updated: 2022-08-18  Resolved: 2022-08-18

Status: Closed
Project: MariaDB Server
Component/s: Packaging, Repositories
Affects Version/s: None
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Niels Hendriks Assignee: Daniel Bartholomew
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Duplicate
is duplicated by MDEV-29304 Package Repositories Wiped Closed
is duplicated by MDEV-29305 yum.mariadb.org/ mirrors appear to be... Closed

 Description   

Hello,

Not sure if this is the right place to report this.
Since last night the apt repositories are broken for MariaDB, at least for Debian 10/11.

I have tried several mirrors:

deb https://ftp.nluug.nl/db/mariadb/repo/10.6/debian bullseye main
 
deb https://mirror.serverion.com/mariadb/repo/10.6/debian bullseye main
 
deb https://mariadb.mirror.wearetriple.com/repo/10.6/debian bullseye main
 
deb http://ams2.mirrors.digitalocean.com/mariadb/repo/10.6/debian bullseye main

With all of these repo's when we do an `apt update` or `apt-get update` we get:

Err:10 http://ams2.mirrors.digitalocean.com/mariadb/repo/10.6/debian bullseye Release
 
  404  Not Found [IP: 2606:4700:3036::ac43:9447 80]
 
Reading package lists... Done
 
E: The repository 'http://ams2.mirrors.digitalocean.com/mariadb/repo/10.6/debian bullseye Release' does not have a Release file.
 
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
 
N: See apt-secure(8) manpage for repository creation and user configuration details.

Now it seems we can ignore the Release file warning by changing the apt config to:

deb [allow-insecure=yes] http://ams2.mirrors.digitalocean.com/mariadb/repo/10.6/debian bullseye main

This will make the error change into this:

Err:12 http://ams2.mirrors.digitalocean.com/mariadb/repo/10.6/debian bullseye/main amd64 Packages
 
  404  Not Found [IP: 2606:4700:3034::6815:1d0d 80]
 
Ign:13 http://ams2.mirrors.digitalocean.com/mariadb/repo/10.6/debian bullseye/main Translation-en_US
 
Ign:14 http://ams2.mirrors.digitalocean.com/mariadb/repo/10.6/debian bullseye/main Translation-en
 
Reading package lists... Done
 
W: The repository 'http://ams2.mirrors.digitalocean.com/mariadb/repo/10.6/debian bullseye Release' does not have a Release file.
 
N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.
 
N: See apt-secure(8) manpage for repository creation and user configuration details.
 
E: Failed to fetch http://ams2.mirrors.digitalocean.com/mariadb/repo/10.6/debian/dists/bullseye/main/binary-amd64/Packages  404  Not Found [IP: 2606:4700:3034::6815:1d0d 80]
 
E: Some index files failed to download. They have been ignored, or old ones used instead.

This is probably related to the new MariaDB release. We've had the same issue the last few MariaDB releases but usually another repo would still work. Now we tried like 5 different mirrors and none of them work.

I'm not sure if this is the correct place to report this. If not, could someone point me in the right direction?

 Comments   
Comment by Ian Gilfillan [ 2022-08-15 ]

Primary mirrors should be working again, secondary mirrors will start to update according to their schedules over the next few hours.

Comment by Niels Hendriks [ 2022-08-16 ]

Cheers, seems to be working again. We did notice a failure for MariaDB 10.2, but those are mainly stale mirrors we still have in our sources.list even though we no longer actively use MariaDB 10.2.

Comment by Ian Gilfillan [ 2022-08-16 ]

Note that MariaDB 10.2 is EOL: https://mariadb.org/about/#maintenance-policy

Comment by Daniel Bartholomew [ 2022-08-18 ]

This was related to some mirror update issues with this week's round of maintenance updates. All mirrors should be be good now (assuming they've updated in the past couple of days).

Generated at Thu Feb 08 10:07:29 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.