Page 1 of 1

[Fixed] Broken Fedora repository for VirtualBox-5.2-5.2.34_133893_fedora29-1.x86_64.rpm

Posted: 16. Oct 2019, 14:49
by birdie

Code: Select all

[MIRROR] VirtualBox-5.2-5.2.34_133893_fedora29-1.x86_64.rpm: Downloading successful, but checksum doesn't match. Calculated: 530912a82d80da3426d1c2e91a4fd597d86522476f4b93973cbd6e84d8fff74d(sha256)  Expected: e855e2233dabdd741c308feffa469e353c17878c01b9954adb955c3cec6c456e(sha256) 
[MIRROR] VirtualBox-5.2-5.2.34_133893_fedora29-1.x86_64.rpm: Downloading successful, but checksum doesn't match. Calculated: 530912a82d80da3426d1c2e91a4fd597d86522476f4b93973cbd6e84d8fff74d(sha256)  Expected: e855e2233dabdd741c308feffa469e353c17878c01b9954adb955c3cec6c456e(sha256) 
[MIRROR] VirtualBox-5.2-5.2.34_133893_fedora29-1.x86_64.rpm: Downloading successful, but checksum doesn't match. Calculated: 530912a82d80da3426d1c2e91a4fd597d86522476f4b93973cbd6e84d8fff74d(sha256)  Expected: e855e2233dabdd741c308feffa469e353c17878c01b9954adb955c3cec6c456e(sha256) 
[MIRROR] VirtualBox-5.2-5.2.34_133893_fedora29-1.x86_64.rpm: Downloading successful, but checksum doesn't match. Calculated: 530912a82d80da3426d1c2e91a4fd597d86522476f4b93973cbd6e84d8fff74d(sha256)  Expected: e855e2233dabdd741c308feffa469e353c17878c01b9954adb955c3cec6c456e(sha256) 
[FAILED] VirtualBox-5.2-5.2.34_133893_fedora29-1.x86_64.rpm: No more mirrors to try - All mirrors were already tried without success                                                         

The downloaded packages were saved in cache until the next successful transaction.
You can remove cached packages by executing 'dnf clean packages'.
Error: Error downloading packages:
  Cannot download VirtualBox-5.2-5.2.34_133893_fedora29-1.x86_64.rpm: All mirrors were tried
Please fix.

Re: Broken Fedora repository for VirtualBox-5.2-5.2.34_133893_fedora29-1.x86_64.rpm

Posted: 16. Oct 2019, 15:02
by gilesc
Same for Centos 7:

Code: Select all

# yum update VirtualBox-5.2
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
 * base: mirror.as29550.net
 * epel: mirror.hostnet.nl
 * extras: mirror.netweaver.uk
 * updates: centos.mirrors.nublue.co.uk
Resolving Dependencies
--> Running transaction check
---> Package VirtualBox-5.2.x86_64 0:5.2.32_132073_el7-1 will be updated
---> Package VirtualBox-5.2.x86_64 0:5.2.34_133893_el7-1 will be an update
--> Finished Dependency Resolution

Dependencies Resolved

=========================================================================================================================================================
 Package Arch Version Repository                         Size
=========================================================================================================================================================
Updating:
 VirtualBox-5.2 x86_64 5.2.34_133893_el7-1 virtualbox                         71 M

Transaction Summary
=========================================================================================================================================================
Upgrade  1 Package

Total download size: 71 M
Is this ok [y/d/N]: y
Downloading packages:
VirtualBox-5.2-5.2.34_133893_e FAILED ======================================= ]  13 MB/s |  70 MB 00:00:00 ETA
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/VirtualBox-5.2-5.2.34_133893_el7-1.x86_64.rpm: [Errno -1] Package does not match intended download. Suggestion: run yum --enablerepo=virtualbox clean metadata
Trying other mirror.


Error downloading packages:
  VirtualBox-5.2-5.2.34_133893_el7-1.x86_64: [Errno 256] No more mirrors to try.

Following suggestion doesn't work...

Re: Broken Fedora repository for VirtualBox-5.2-5.2.34_133893_fedora29-1.x86_64.rpm

Posted: 16. Oct 2019, 15:26
by Martin
Wait a few hours for the uploads and mirror resyncs to be finished.

Re: Broken Fedora repository for VirtualBox-5.2-5.2.34_133893_fedora29-1.x86_64.rpm

Posted: 17. Oct 2019, 06:53
by socratis
birdie wrote:Please fix.
gilesc wrote:Following suggestion doesn't work...
https://download.virtualbox.org/virtual ... /repodata/ seems to be up-to-date.

It would be nice if you could confirm that it's fixed now, but since I know the case first hand, I'm marking this as [Fixed] no matter... ;)