- CheckMates
- :
- Products
- :
- General Topics
- :
- CPUSE packaging issue
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Are you a member of CheckMates?
×- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
CPUSE packaging issue
Looks like CPUSE build 2113 has a minor packaging issue:
LabSC> installer agent install /home/admin/DeploymentAgent_000002113_1.tgz
INFO Installing Deployment Agent package - /home/admin/DeploymentAgent_000002113_1.tgz ...
INFO After the installation is complete, the Deployment Agent restarts and the CLISH session is terminated
Interactive mode is enabled. Press CTRL + C to exit (This will not stop the operation)
ERROR Installation failed. Error: File is not a DA package.
LabSC> exit
[Expert@LabSC:0]# gunzip DeploymentAgent_000002113_1.tgz
[Expert@LabSC:0]# file DeploymentAgent_000002113_1.tar
DeploymentAgent_000002113_1.tar: gzip compressed data, from Unix, last modified: Thu Sep 9 10:56:58 2021
[Expert@LabSC:0]# mv DeploymentAgent_000002113_1.tar DeploymentAgent_000002113_1.tgz
[Expert@LabSC:0]# clish
LabSC> installer agent install /home/admin/DeploymentAgent_000002113_1.tgz
INFO Installing Deployment Agent package - /home/admin/DeploymentAgent_000002113_1.tgz ...
INFO After the installation is complete, the Deployment Agent restarts and the CLISH session is terminated
Interactive mode is enabled. Press CTRL + C to exit (This will not stop the operation)
INFO Installation succeeded. Leaving CLISH
Specifically, it looks like it's a TGZ which is then gzipped again. The hash on the download page is correct for the version of the package which can be installed. The package as downloaded to my machine instead has this hash:
~/Downloads> md5 DeploymentAgent_000002113_1.tgz
MD5 (DeploymentAgent_000002113_1.tgz) = d9856795377944b9f21759e07f98b086
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi
Can you please specify which browser (including version) was used to download the package from the SK?
Thanks
Boaz
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Originally saw it on Edge on Windows 10. I don't have that machine immediately handy, but can post its version later.
Just tried downloading it again in Safari 15.0 (16612.1.29.41.4, 16612), and saw the same behavior.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Bob,
Was this file downloaded from sk92449?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Yes. I also just downloaded R80.40 jumbo 125 from sk165456 with the same instance of Safari (haven't even quit and relaunched it), and it was not double-zipped.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I just tested this with Edge and Chrome. Both downloads yielded a valid file with the correct md5:
md5sum DeploymentAgent_000002113_1.tgz
fe2aec8f07d975edaba486465353daf1 DeploymentAgent_000002113_1.tgz
[2021-09-30 17:06.05] /drives/c/Users/owoloch/Downloads
➤ md5sum DeploymentAgent_000002113_1\ \(1\).tgz
fe2aec8f07d975edaba486465353daf1 DeploymentAgent_000002113_1 (1).tgz
[2021-09-30 17:24.36] /drives/c/Users/owoloch/Downloads
➤ file DeploymentAgent_000002113_1.tgz
DeploymentAgent_000002113_1.tgz: gzip compressed data, last modified: Thu Sep 9 10:56:58 2021, from Unix
[2021-09-30 17:24.40] /drives/c/Users/owoloch/Downloads
➤ gunzip DeploymentAgent_000002113_1.tgz
[2021-09-30 17:25.34] /drives/c/Users/owoloch/Downloads
➤ gunzip DeploymentAgent_000002113_1.tar
gunzip: DeploymentAgent_000002113_1.tar: unknown suffix - ignored
[2021-09-30 17:25.41] /drives/c/Users/owoloch/Downloads
➤ file DeploymentAgent_000002113_1.tar
DeploymentAgent_000002113_1.tar: POSIX tar archive (GNU)
Can you test again to rule out a temporary glitch on the DownloadCenter?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Sorry, spent the last two solid days troubleshooting something completely unrelated.
Just tested again, and now I get a file with the correct hash. I wonder what could cause an issue like that. Maybe a CDN node somewhere got a weird copy?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
As far as I know, the download center only does storage and delivery. The files are not processed after being uploaded.
