Opened 7 years ago
Closed 7 years ago
#17932 closed defect (fixed)
Unable to upgrade VirtualBox from 5.2.16 to 5.2.18 -> fixed
Reported by: | Sharath Chandramouli | Owned by: | |
---|---|---|---|
Component: | other | Version: | VirtualBox 5.2.18 |
Keywords: | Cc: | ||
Guest type: | all | Host type: | Linux |
Description
Unable to upgrade the VirtualBox software from 5.2.16 to 5.2.18.
OS: Linux Mint 18.3 'Sylvia'
How to reproduce:
Assuming VirtualBox 5.2.16 is already installed,
- sudo apt update
- sudo apt upgrade
The output says:
Err:1 https://download.virtualbox.org/virtualbox/debian xenial/contrib amd64 virtualbox-5.2 amd64 5.2.18-124319~Ubuntu~xenial
404 Not Found
E: Failed to fetch https://download.virtualbox.org/virtualbox/debian/pool/contrib/v/virtualbox-5.2/virtualbox-5.2_5.2.18-124319~Ubuntu~xenial_amd64.deb 404 Not Found
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?
Change History (5)
follow-up: 2 comment:1 by , 7 years ago
comment:2 by , 7 years ago
Replying to socratis:
Duplicate of #17929.
The files are there if you want to update manually...
The intent of raising this defect is to resolve the '404 Page not found' issue for Ubuntu based upgrade system. It would be great if somebody makes the update file available in the APT software repository location.
follow-up: 4 comment:3 by , 7 years ago
Something went south during the update, that's why it's a duplicate. The developers are aware of the issue. The issue arises from the fact that anything that has a symlink doesn't work, i.e. all the repos.
comment:4 by , 7 years ago
Replying to socratis:
Something went south during the update, that's why it's a duplicate. The developers are aware of the issue. The issue arises from the fact that anything that has a symlink doesn't work, i.e. all the repos.
Understood. Thanks for the update.
comment:5 by , 7 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Summary: | Unable to upgrade VirtualBox from 5.2.16 to 5.2.18 → Unable to upgrade VirtualBox from 5.2.16 to 5.2.18 -> fixed |
Should be working now. Sorry for the inconvenience.
Duplicate of #17929.
The files are there if you want to update manually...