LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Installation Error: invalide signature

I cannot install Labview community on my Fedora 34 machines. The error seems to be related to an invalid package manifest.

Procedures:

- Downloaded Labview Community Edition

- Mounted at /mnt/test

- run sudo sh ./INSTALL

- answered y to all prompts

- got the following error:

labview-2020-community-exe: LabVIEW Community Edition Executable
[Ynasq?] Y
error: labview-2020-core-20.0.1-1.x86_64.rpm: invalid signature tag Archivesize (1046)
error: labview-2020-core-20.0.1-1.x86_64.rpm: not an rpm package (or package manifest)

- tried to install that rpm separately, all to no avail

- chose s (skip) so I could continue the install

- got the following error at the end:

Preparing for installing NI Example Finder (LabVIEW 2020)...
NI System Configuration Runtime is required for installing NI Example Finder.
Proceed with installing NI Example Finder along with NI System Configuration Runtime? [Ynq] y
Installing NI System Configuration Runtime...
error: Failed dependencies:
nicurli >= 20.0.0 is needed by ni-wsrepl-20.0.0.49152-0+f0.x86_64
Installation of NI Example Finder (LabVIEW 2020) is aborted because the
installation of the NI System Configuration Runtime failed.

- Tried various different ways of installing packages separately but could not install

System setup/details:

+ Fedora 34, Kernel 5.11.19-300.fc34.x86_64
+ First installation of any NI product
+ AMD Threadripper 1950X, 32MB RAM, NVidia 1080

 

I apologize in advance if there is any really dummy mistake from my end (e.g. trying to install incompatible versions), but I am a newbie to Labview and did go through foruns, google, etc., prior to posting this. Yet, I was not able to find a similar error. The full installation thread is posted below in case it is useful.
Thanks,
Paulo

 

❯ bash INSTALL

LabVIEW 2020 SP1 for GNU/Linux

Copyright (c) 2020, National Instruments Corporation. The source code of this
product is unpublished, unlicensed, and a proprietary trade secret of National
Instruments Corporation. Decompilation or other reduction of this object code
to human-readable form is prohibited by the license agreement between National
Instruments Corporation and the lawful user or possessor of this copy.

Restricted Rights Legend

Use, duplication, or disclosure by the United States Government is subject to
restrictions set forth in subparagraph (c)(1)(ii) of the Rights in Technical
Data and Computer Software Clause at DFARS 252.227-7013 and FAR 52.227-19 (c).

National Instruments Corporation
11500 N. Mopac Expwy.
Austin, Texas 78759
U.S.A.


By installing LabVIEW software packages, you agree to the terms of the included
NI Software License Agreement (LICENSE.txt). Type 'v' to view the agreement,
'y' to consent to the agreement, or 'n' to decline the agreement and skip
LabVIEW installation. [Vynq] y

NOTE: LabVIEW will install by default in /usr/local/natinst/LabVIEW-2020-64, or
in the natinst/LabVIEW-2020-64 subdirectory if you specify an alternate location.

Preparing for installation...
C runtime library (glibc) version: 2.33.
Red Hat Package Manager (RPM) version: 4.16.1.3.
Please indicate whether you would like to install the following components:

labview-2020-rte: LabVIEW Run-Time Engine
[Ynasq?] Y
labview-2020-exe-libs: LabVIEW Executables - Libraries
[Ynasq?] Y
labview-2020-community: LabVIEW Community Edition
[Ynasq?] Y
labview-2020-community-exe: LabVIEW Community Edition Executable
[Ynasq?] Y
error: labview-2020-core-20.0.1-1.x86_64.rpm: invalid signature tag Archivesize (1046)
error: labview-2020-core-20.0.1-1.x86_64.rpm: not an rpm package (or package manifest)
[Ynasq?] s
Skipping LabVIEW installation.
No LabVIEW packages were selected.


Preparing for installing NI Example Finder (LabVIEW 2020)...
NI System Configuration Runtime is required for installing NI Example Finder.
Proceed with installing NI Example Finder along with NI System Configuration Runtime? [Ynq] y
Installing NI System Configuration Runtime...
error: Failed dependencies:
nicurli >= 20.0.0 is needed by ni-wsrepl-20.0.0.49152-0+f0.x86_64
Installation of NI Example Finder (LabVIEW 2020) is aborted because the
installation of the NI System Configuration Runtime failed.

LabVIEW installation complete.

================================================================================

To install the latest NI-VISA and NI-488.2, visit
http://www.ni.com/en-us/support/downloads/drivers/download.ni-linux-device-drivers.html


Installation complete.

 

0 Kudos
Message 1 of 6
(2,466 Views)

I guess this link will get you started.

Bill
CLD
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.
Humble author of the CLAD Nugget.
0 Kudos
Message 2 of 6
(2,406 Views)

Bill,

Thanks for your reply and for taking the time to help me.

The link shows compatibility with RHEL 8 and CentOS 8, which (very roughly speaking) are similar to Fedora 28. I tried many different ways of installing the community edition, including installation on a brand new VM F33, on a brand new VM F34, but the installation always give me the same error in the middle of the installation:

...
labview-2020-community-exe: LabVIEW Community Edition Executable
[Ynasq?] y
error: labview-2020-core-20.0.1-1.x86_64.rpm: invalid signature tag Archivesize (1046)
error: labview-2020-core-20.0.1-1.x86_64.rpm: not an rpm package (or package manifest)
...

...and then fail at the end.
Interestingly enough, I downloaded the LabView runtime engine and it installed in both Fedora 33 and Fedora 34 VMs and bare metal. Thus, the problem is really restricted to that specific component.
I will try a VM with CentOS, but it seems an overkill.
In case I figure out the issue I'll definitely post it here.
Paulo

0 Kudos
Message 3 of 6
(2,351 Views)

@paulo.costa wrote:

Bill,

Thanks for your reply and for taking the time to help me.

The link shows compatibility with RHEL 8 and CentOS 8, which (very roughly speaking) are similar to Fedora 28. I tried many different ways of installing the community edition, including installation on a brand new VM F33, on a brand new VM F34, but the installation always give me the same error in the middle of the installation:

...
labview-2020-community-exe: LabVIEW Community Edition Executable
[Ynasq?] y
error: labview-2020-core-20.0.1-1.x86_64.rpm: invalid signature tag Archivesize (1046)
error: labview-2020-core-20.0.1-1.x86_64.rpm: not an rpm package (or package manifest)
...

...and then fail at the end.
Interestingly enough, I downloaded the LabView runtime engine and it installed in both Fedora 33 and Fedora 34 VMs and bare metal. Thus, the problem is really restricted to that specific component.
I will try a VM with CentOS, but it seems an overkill.
In case I figure out the issue I'll definitely post it here.
Paulo


Sorry, I'd offer more help, but I totally suck at anything LINUX-related.  😞

Bill
CLD
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.
Humble author of the CLAD Nugget.
0 Kudos
Message 4 of 6
(2,347 Views)

Pretty late to the game, but I had the exact same problem trying to install onto Fedora 34, with the same result. I even tried installing the packages independently (without ./INSTALL) with no real success. 

 

Works just fine on a CentOS 8 VM though, so that might be the best solution for anyone else with this problem.

0 Kudos
Message 5 of 6
(2,107 Views)

It is caused by a bug present in  rpm 4.16 which is present in fedora 34. I upgraded to rpm 4.17 and the installation is successful.
Rpm 4.17 is backported from fedora 35 srpms.
I think the easiest thing is to upgrade fedora 34 to 35

0 Kudos
Message 6 of 6
(1,814 Views)