Briefly describe your issue below:
Everytime I goto apt-get upgrade or even parrot upgrade it wants to downgrade my vagrant which makes my metasploitable3 vm unusable. How can I fix this if possible? Upgrade everything then just reinstall manually the latest vagrant?
What version of Parrot are you running? (include version, edition, and architecture)
Linux parrot 4.19.0-parrot1-20t-amd64 #1 SMP Parrot 4.19.20-2parrot1.20t (2019-03-09) x86_64 GNU/Linux What method did you use to install Parrot? (Debian Standard / Debian GTK / parrot-experimental)
Debian Standard Configured to multiboot with other systems? (yes / no)
Hell no. F windows If there are any similar issues or solutions, link to them below:
Cant find anything related. If there are any error messages or relevant logs, post them below:
TL;DR apt is used nowadays with common commands of the apt package and it does pretty much the same. It was introduced essentially as something more user-friendly for the front-end users.
Using the command sudo parrot-upgrade or even sudo apt update && sudo apt dist-upgrade both still give me this and want to downgrade vagrant? Any way to add an exclusion? Metasploitable3 requires updated version of vagrant.
The following packages will be DOWNGRADED:
vagrant
0 upgraded, 0 newly installed, 1 downgraded, 0 to remove and 0 not upgraded.
Need to get 479 kB of archives.
After this operation, 114 MB disk space will be freed.
Get:1 http://ftp.osuosl.org/pub/parrotos parrot/main amd64 vagrant all 2.2.3+dfsg-1 [479 kB]
Fetched 479 kB in 2s (256 kB/s)
dpkg: warning: downgrading vagrant from 1:2.2.4 to 2.2.3+dfsg-1
(Reading database … 509492 files and directories currently installed.)
Preparing to unpack …/vagrant_2.2.3+dfsg-1_all.deb …
Unpacking vagrant (2.2.3+dfsg-1) over (1:2.2.4) …
Setting up vagrant (2.2.3+dfsg-1) …
Processing triggers for man-db (2.8.5-2) …
Scanning processes…
Scanning processor microcode…
Scanning linux images…