On Sun, 26 Jul 2015 18:11:42 +0200 jdd jdd wrote:
zypper couldn't install atom and so didn't install any dependency.
Agreed, but something else not described in Arup's original posts was responsible: On Sun, 26 Jul 2015 12:44:43 +0630 Arup Rakshit wrote:
linux-wzza:/home/arup # zypper in atom.x86_64.rpm Loading repository data... Reading installed packages... '_tmpRPMcache_:atom=0:1.0.2-0.1.fc21' not found in package names. Trying capabilities. No provider of 'atom = 0:1.0.2-0.1.fc21' found.
The package names echoed back in zypper's "package not found" and "no provider" error messages do not make sense: "_tmpRPMcache_:atom=0:1.0.2-0.1.fc21" "atom = 0:1.0.2-0.1.fc21"
Resolving package dependencies...
Nothing to do.
It seems zypper wasn't even looking for "atom." Since it found no provider for these strange things it was looking for, it did nothing.
Installing the dependency wont help zypper but may help rpm
You failed to grasp my earlier point. 'rpm' is the package management engine that is used both by zypper and YaST in the background. Hypothetical example: If you have _one_ dependency for a package, and, if that dependency is _not_ already installed, there are basically three paths you can take to install your package: a. Install the package with YaST. It's dependency will be automatically selected and presented for concurrent installation. b. Install the package with zypper. It's dependency will be automatically selected and presented for concurrent installation. c. Pre-install the dependency using rpm, zypper or YaST (this is silly) but you will then be able to install the package using either rpm, zypper or YaST since, in all three cases, the dependency has already been met. hth & regards, Carl -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org