If you don’t have the sudo utility installed, log on as superuser (“root”) and run the commands without sudo.
Note: click here for detailed instructions on how to install the NX Client, NX Node and NX Server packages. The NX service can be controlled by the command /usr/NX/bin/nxserver --status|–start|–stop|–restart. Additional commands are available to configure the server. Try /usr/NX/bin/nxserver --help for more information. Please, don’t forget to download and read the NX Server Administrator’s Guide available here.
I don’t see anything wrong with your commands, but I might just use the method given by the Nomachine folks instead.
Why do you not show the complete output of that zypper command so we can see for ourselves what the error is. Only copy/paste a few lines more and we have all in one.
When I get a “file not found” error on any program, I either:
. tear my hear out and redress my typo;
. or do not understand it and the do an ls -l of the file to see for myself.
You did not report one of the possibilties above. Why do we not see the output of
ls -l /local/install_rpm/nxclient-3.5.0-7.x86_64.rpm
to prove that you are correct and zypper is wrong?
(BTW, most systems do not have a /local).
linux:/local/zypper_install # ls -al
total 4568
drwxr-xr-x 2 root root 4096 May 4 22:27 .
drwxr-xr-x 4 root root 4096 May 4 21:56 ..
-rw-r--r-- 1 root root 4665824 Apr 25 18:56 nxclient-3.5.0-7.x86_64.rpm
linux:/local/zypper_install #
linux:/local/zypper_install # zypper --help
Usage:
zypper --global-options] <command> --command-options] [arguments]
Global Options:
--help, -h Help.
....
....
....
Querying:
info, if Show full information for specified packages.
....
....
....
Type 'zypper help <command>' to get command-specific help.
linux:/local/zypper_install #
linux:/local/zypper_install # zypper info ./nxclient-3.5.0-7.x86_64.rpm
Loading repository data...
Reading installed packages...
package './nxclient-3.5.0-7.x86_64.rpm' not found.
linux:/local/zypper_install #
Which proves that I did not ask this for nothing. The error is not as you told “file not found”, but “package not found”. Which may point to something quite different like: the file is there, but it does not contain a true RPM package.
On 2012-05-05 12:26, hcvv wrote:
>
> Which proves that I did not ask this for nothing. The error is not as
> you told “file not found”, but “package not found”. Which may point to
> something quite different like: the file is there, but it does not
> contain a true RPM package.
No, zypper is trying to find that exact package remotely in the configured
repos. I don’t know if you can do that directly on a local file, but the
trick is to create a local repository of type “directory”, containing the
directory, and then try again.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)
Do you think that NoMachine company provides false RPM package?
Or do you think that the “zypper info option” is inappropriate for a RPM package in a zypper script ?
This package install fine with yast2 (right click on the file and choose “open with” -> “install / remove”)
I just want to automate this task without using “rpm -i” which is supposed a bad way ?
-i, --install <package> <package> … ] ]
Install an RPM package. The package can be a single short package name (e.g. gvim) which will be installed with dependency checking, or the full path to an rpm package (e.g /tmp/gvim.rpm) which will be installed without dependency checking.
IIRC I installed RPMs from the command line using YaST this way (did not have any need for it for a long time).
linux:/local/zypper_install # zypper -vvv info ./nxclient-3.5.0-7.x86_64.rpm
Verbosity: 3
Non-option program arguments: './nxclient-3.5.0-7.x86_64.rpm'
Initializing Target
Checking whether to refresh metadata for PLEASE_TRY_AGAIN
Checking whether to refresh metadata for Updates for openSUSE 12.1 12.1-1.4
Checking whether to refresh metadata for nVidia Graphics Drivers
Checking whether to refresh metadata for local_zypper_install
Checking whether to refresh metadata for libdvdcss repository
Checking whether to refresh metadata for Packman Repository
Checking whether to refresh metadata for openSUSE-12.1-Non-Oss
Checking whether to refresh metadata for openSUSE-12.1-Oss
Loading repository data...
Reading installed packages...
Force resolution: No
package './nxclient-3.5.0-7.x86_64.rpm' not found.
linux:/local/zypper_install #
linux:/local/zypper_install # zypper -v in ./nxclient-3.5.0-7.x86_64.rpm
Verbosity: 1
Non-option program arguments: './nxclient-3.5.0-7.x86_64.rpm'
'./nxclient-3.5.0-7.x86_64.rpm' looks like an RPM file. Will try to download it.
Initializing Target
Checking whether to refresh metadata for PLEASE_TRY_AGAIN
Checking whether to refresh metadata for Updates for openSUSE 12.1 12.1-1.4
Checking whether to refresh metadata for Plain RPM files cache
Checking whether to refresh metadata for nVidia Graphics Drivers
Checking whether to refresh metadata for local_zypper_install
Checking whether to refresh metadata for libdvdcss repository
Checking whether to refresh metadata for Packman Repository
Checking whether to refresh metadata for openSUSE-12.1-Non-Oss
Checking whether to refresh metadata for openSUSE-12.1-Oss
Loading repository data...
Reading installed packages...
Force resolution: No
Selecting 'nxclient-3.5.0-7.x86_64' from repository 'Plain RPM files cache' for installation.
Resolving package dependencies...
Force resolution: No
The following NEW package is going to be installed:
nxclient 3.5.0-7
1 new package to install.
Overall download size: 4.5 MiB. After the operation, additional 10.3 MiB will be used.
Continue? [y/n/?] (y): ^C ^C
linux:/local/zypper_install #
info (if) [options] <name> …
Displays detailed informaion about the specified packages.
For each specified package, zypper finds the best available version in defined repositories and shows information for this package.
From the man page of course (including the typo).
Thus info gives information about packages (defined by* <name>*) residing in repos known by *zyppper. *Nothing about giving it a file name as parameter, independent of the fact if that file contains an RPM or not.
install (in) [options] <name|capability|rpm_file_uri> …
Install or update packages.
Again from the man page.
Thus in install you can give it an <rpm_file_uri>.
Thus I do not understand you when you say:
Seems I can install it but not info it
Or didn’t you check the the man page before you tried? Well, some people live by trial and error. But they then read the man page after getting the error.
You say I’m stupid: You are right.
You say I’m lazy: You’re wrong.
From the link in the man page which delighted you (man zypper) :
All URIs require a scheme identifier (like http or file). The parts following the scheme are scheme-specific, as you can see from the above example. Various applications can ease the use of URIs, e.g. by providing input fields to fill (like in YaST’s Repository Management module), or by guessing omitted components (like Zypper treating file or directory paths as dir URIs).
…
…
Local Files
dir:/directory/name
file:/directory/name
…
…
If you look at my screenshot in one of my previous thread, zypper can install the rpm file with the command "zypper install …"
linux:/local/zypper_install # zypper -v in ./nxclient-3.5.0-7.x86_64.rpm
Verbosity: 1
Non-option program arguments: ‘./nxclient-3.5.0-7.x86_64.rpm’
‘./nxclient-3.5.0-7.x86_64.rpm’ looks like an RPM file. Will try to download it.
Initializing Target
Checking whether to refresh metadata for PLEASE_TRY_AGAIN
…
…
Selecting ‘nxclient-3.5.0-7.x86_64’ from repository ‘Plain RPM files cache’ for installation.
…
…
The following NEW package is going to be installed:
nxclient 3.5.0-7
1 new package to install.
Overall download size: 4.5 MiB. After the operation, additional 10.3 MiB will be used.
Continue? [y/n/?] (y): ^C ^C
linux:/local/zypper_install #
But is unable to give any information on the package named by its full name. "zypper info …"
linux:/local/zypper_install # zypper -vvv info ./nxclient-3.5.0-7.x86_64.rpm
Verbosity: 3
Non-option program arguments: ‘./nxclient-3.5.0-7.x86_64.rpm’
Initializing Target
Checking whether to refresh metadata for PLEASE_TRY_AGAIN
…
…
Loading repository data…
Reading installed packages…
Force resolution: No
package ‘./nxclient-3.5.0-7.x86_64.rpm’ not found.
linux:/local/zypper_install #
I will continue searching, trying and failing after dinner and give you news as soon as I got something new.
I can not completely follow all what you say (you were away for two days and now I should restudy the whole thread, but i have lack of time), but I see that:
you post computer output beteen QUOTE tags instead of CODE tags (which you did allright earlier).
that you still try to feed* zypper info* with a file name of an RPM where you should give it a package name (and it will only report something usefull if the package is available in one of your active repos, or installed).
If you have it installed or it is in one or more of your active repos
zypper info nxclient
should give you what you want. At least it will produce what it does on my system:
boven:~ # zypper info nxclient
Loading repository data...
Reading installed packages...
package 'nxclient' not found.
boven:~ #
# zypper info nxclient
Retrieving repository 'Updates for openSUSE 12.1 12.1-1.4' metadata [done]
Building repository 'Updates for openSUSE 12.1 12.1-1.4' cache [done]
Loading repository data...
Reading installed packages...
Information for package nxclient:
Repository: @System
Name: nxclient
Version: 3.5.0-7
Arch: x86_64
Vendor: NoMachine
Installed: Yes
Status: up-to-date
Installed Size: 10.3 MiB
Summary: NX Client
Description:
NoMachine NX is a fast and scalable terminal server system based on the
X11 protocol. NX lets you work fluently even across slow links like modems
and provides a full set of administration tools that make it a complete
desktop virtualization solution for your organization.
This package contains the graphical front-end used to access X, RDP and RFB
sessions on a remote NX Server. It also includes NX X compression libraries
and utilities needed by both NX Client and Server.
Baseline:
nx-X11: 3.5.0-1
nxauth: 3.5.0-1
nxwin: 3.5.0-2
nxssh: 3.5.0-2
nxcomp: 3.5.0-2
nxesd: 3.5.0-2
nxkill: 3.5.0-1
nxservice: 3.5.0-2
nxcompsh: 3.5.0-1
nx-X11-compat: 3.5.0-1
