Welcome!
Important information
-- Spectre and Meltdown vulnerabilities
-- Change in MX sources

News
-- MX Linux on social media: here
-- Mepis support still here

Current releases
-- MX-17.1 Final release info here
-- antiX-17 release info here

New users
-- Please read this first, and don't forget to add system and hardware information to posts!
-- Here are the Forum Rules

Package-Rebuild request virtualbox-ext-pack_5.2.10 with a polite hint

Message
Author
User avatar
fehlix
Forum Guide
Forum Guide
Posts: 2065
Joined: Wed Apr 11, 2018 5:09 pm

Package-Rebuild request virtualbox-ext-pack_5.2.10 with a polite hint

#1 Post by fehlix » Mon May 14, 2018 10:30 am

Package-Rebuild request virtualbox-ext-pack_5.2.10
As found by @stsoh within another thread
viewtopic.php?f=108&t=44743&start=30#p447116
we have a installation error due to a checksum missmatch.

Our current „meta“-downloader package virtualbox-ext-pack_5.2.10-1~mx17+1_all.deb
refere to the Oracle packge without a subversion. The sha256sum used is from an older subversion.

Package-Hint: To avoid future installation errors due to checksum-missmatch
better include full subversion within the download name of vbox-ext-package.
Without subversion it always points to latest one.
And we never know when Oracle will fire out a newer subversion next time!
Gigabyte Z77M-D3H, Intel Xeon E3-1240 V2 (Quad core), 32GB RAM,
GeForce GTX 770, Samsung SSD 850 EVO 500GB, Seagate Barracuda 4TB

User avatar
stsoh
Forum Regular
Forum Regular
Posts: 415
Joined: Sun Aug 20, 2017 10:11 am

Re: Package-Rebuild request virtualbox-ext-pack_5.2.10 with a polite hint

#2 Post by stsoh » Mon May 14, 2018 10:34 am

dev team is working on vb 5.2.12, so it doesn't matter after overwrite by newer version.
MX-17.1_x64 Horizon, G41M-P33 Combo(MS-7592), Pentium E5400 (min/max: 1203/2700 MHz), 8Gb RAM (800 MT/s),
Intel 4 Series Integrated Graphics, Realtek PCIe Fast RTL8101/2/6E, PCI Gigabit RTL8169 Ethernets.

User avatar
fehlix
Forum Guide
Forum Guide
Posts: 2065
Joined: Wed Apr 11, 2018 5:09 pm

Re: Package-Rebuild request virtualbox-ext-pack_5.2.10 with a polite hint

#3 Post by fehlix » Mon May 14, 2018 10:42 am

stsoh wrote:
Mon May 14, 2018 10:34 am
dev team is working on vb 5.2.12, so it doesn't matter after overwrite by newer version.
Well, it might matter, as one might choose to stay with the older 5.2.10 version.
In addition the checksum-mismatch might happen also with 5.2.12 if we don't use subversion number with the ext-package downloader.
Gigabyte Z77M-D3H, Intel Xeon E3-1240 V2 (Quad core), 32GB RAM,
GeForce GTX 770, Samsung SSD 850 EVO 500GB, Seagate Barracuda 4TB

User avatar
Stevo
Forum Veteran
Forum Veteran
Posts: 16608
Joined: Fri Dec 15, 2006 8:07 pm

Re: Package-Rebuild request virtualbox-ext-pack_5.2.10 with a polite hint

#4 Post by Stevo » Mon May 14, 2018 12:56 pm

We plan to replace 5.2.10 in the test repo with the new & improved 5.2.12. You can get it early here, too: https://drive.google.com/open?id=1aZqot ... 0f3NUxHvw5 Just upgrade the virtualbox, -qt, and -dkms packages, then install the guest-iso and ext-pack packages.

User avatar
fehlix
Forum Guide
Forum Guide
Posts: 2065
Joined: Wed Apr 11, 2018 5:09 pm

Re: Package-Rebuild request virtualbox-ext-pack_5.2.10 with a polite hint

#5 Post by fehlix » Mon May 14, 2018 2:26 pm

Thanks, Stevo! I downloaded this....but...
Nevertheless, I do feel I still need to rephrase my request like this:

Request:
Please change the deb-package for virtualbox-ext-pack to include Oracle‘s build-number within file name of the downloaded extension pack.

Why?
Without the build-number the installation of the deb-package will fail next time Oracle rebuilds and publishes the extension pack with a new build number.
The sha256sum of the new build will not match the older one.
This missing build number was exactly the reason for the installation error of the 5.10 version!

How?
You simply would only need to change the postinst file to include Oracle‘s build number.
For example:
Within the version you are going to send to main do
change within the virtualbox-ext-pack_5.2.12-1~mx17+1_all.deb
the beginning of postinst from

Code: Select all

#!/bin/sh
set -e

version=5.2.12
hash=4c36d129f17dcab2bb37292022f1b1adfefa5f32a3161b0d5d40784bc8acf4d0
file=Oracle_VM_VirtualBox_Extension_Pack-$version.vbox-extpack
to include Oracle‘s build number like this

Code: Select all

#!/bin/sh
set -e

version=5.2.12
build=122591
hash=4c36d129f17dcab2bb37292022f1b1adfefa5f32a3161b0d5d40784bc8acf4d0
file=Oracle_VM_VirtualBox_Extension_Pack-$version-$build.vbox-extpack
Do you see the difference and the reason for the potential installation error next time the build number changes ?
Gigabyte Z77M-D3H, Intel Xeon E3-1240 V2 (Quad core), 32GB RAM,
GeForce GTX 770, Samsung SSD 850 EVO 500GB, Seagate Barracuda 4TB

User avatar
Stevo
Forum Veteran
Forum Veteran
Posts: 16608
Joined: Fri Dec 15, 2006 8:07 pm

Re: Package-Rebuild request virtualbox-ext-pack_5.2.10 with a polite hint

#6 Post by Stevo » Mon May 14, 2018 2:37 pm

If they do change the file from the current version, won't that change the hash?

User avatar
fehlix
Forum Guide
Forum Guide
Posts: 2065
Joined: Wed Apr 11, 2018 5:09 pm

Re: Package-Rebuild request virtualbox-ext-pack_5.2.10 with a polite hint

#7 Post by fehlix » Mon May 14, 2018 2:57 pm

Stevo wrote:
Mon May 14, 2018 2:37 pm
If they do change the file from the current version, won't that change the hash?
The new build will have a new checksum, right. But they keep the old too.
I tried to explain it here already: viewtopic.php?f=108&t=44743&start=30#p447116 Have a look into the directory list and into SHA256SUMS.
They keep the old build available and do have the old and the new file and hashsum within the SHA267SUMS-file.
The file without the build-number is always a hard-link to the latest build!
Thats why better to include the build bumber to avoid the hash-mismatch error, if you have more than one build!
Gigabyte Z77M-D3H, Intel Xeon E3-1240 V2 (Quad core), 32GB RAM,
GeForce GTX 770, Samsung SSD 850 EVO 500GB, Seagate Barracuda 4TB

User avatar
stsoh
Forum Regular
Forum Regular
Posts: 415
Joined: Sun Aug 20, 2017 10:11 am

Re: Package-Rebuild request virtualbox-ext-pack_5.2.10 with a polite hint

#8 Post by stsoh » Mon May 14, 2018 3:00 pm

i just did mxpi upgrade vb 5.2.12 but what i saw on the console was different, runs on vb 5.2.10 instead. :confused:

Code: Select all

Preparing to unpack .../0-virtualbox-qt_5.2.10-dfsg-2~mx17+1_amd64.deb ...
Unpacking virtualbox-qt (5.2.10-dfsg-2~mx17+1) over (5.2.10-dfsg-2~mx17+1) ...
Preparing to unpack .../1-virtualbox_5.2.10-dfsg-2~mx17+1_amd64.deb ...
Unpacking virtualbox (5.2.10-dfsg-2~mx17+1) over (5.2.10-dfsg-2~mx17+1) ...
Preparing to unpack .../2-virtualbox-dkms_5.2.10-dfsg-2~mx17+1_all.deb ...
You do not have the required permissions to view the files attached to this post.
MX-17.1_x64 Horizon, G41M-P33 Combo(MS-7592), Pentium E5400 (min/max: 1203/2700 MHz), 8Gb RAM (800 MT/s),
Intel 4 Series Integrated Graphics, Realtek PCIe Fast RTL8101/2/6E, PCI Gigabit RTL8169 Ethernets.

User avatar
fehlix
Forum Guide
Forum Guide
Posts: 2065
Joined: Wed Apr 11, 2018 5:09 pm

Re: Package-Rebuild request virtualbox-ext-pack_5.2.10 with a polite hint

#9 Post by fehlix » Mon May 14, 2018 3:49 pm

stsoh wrote:
Mon May 14, 2018 3:00 pm
i just did mxpi upgrade vb 5.2.12 but what i saw on the console was different, runs on vb 5.2.10 instead. :confused:
@stsoh: You can select Utah mxrepo server as it seems the repos have not been properly synced yet !
But you are right MXPI shows already version show 5.2.12 even if having selected
another local mirror, which than causes this conflict! I've checked and had the same here in europe!
Potentially one of those package-list of not-yet-synced mirrors mystics! :bagoverhead:
Gigabyte Z77M-D3H, Intel Xeon E3-1240 V2 (Quad core), 32GB RAM,
GeForce GTX 770, Samsung SSD 850 EVO 500GB, Seagate Barracuda 4TB

User avatar
stsoh
Forum Regular
Forum Regular
Posts: 415
Joined: Sun Aug 20, 2017 10:11 am

Re: Package-Rebuild request virtualbox-ext-pack_5.2.10 with a polite hint

#10 Post by stsoh » Mon May 14, 2018 4:23 pm

just upgraded, works fine. :happy:
MX-17.1_x64 Horizon, G41M-P33 Combo(MS-7592), Pentium E5400 (min/max: 1203/2700 MHz), 8Gb RAM (800 MT/s),
Intel 4 Series Integrated Graphics, Realtek PCIe Fast RTL8101/2/6E, PCI Gigabit RTL8169 Ethernets.

Post Reply

Return to “Package Requests/Status - MX 17”