Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I am in the process of setting up a new CentOS 7 machine - actually testing everything on a VMWare virtual machine and a test PC while I wait for my new workstation to arrive on the truck. I am at the point of attempting to install the 32 bit version of wine. I built the RPMs last February on a CentOS 7 64 bit machine, installed them on a couple of CentOS 7 64 bit machines and archived them for future use. When I issue the command "yum localinstall *" in the directory containing the wine32 RPM files I observer each file being "Examined" and then get a message "Error: nothing to do."
I am going back through the build process on a 64 bit machine (and building a 32 bit CentOS machine in case that does not work.) So far, I have built one RPM. When I attempt to localinstall it I observe
Code:
[root@vmCentOS7Mate Desktop]# yum localinstall chrpath-0.13-14.el7.centos.i686.rpm
Loaded plugins: fastestmirror, priorities
Examining chrpath-0.13-14.el7.centos.i686.rpm: chrpath-0.13-14.el7.centos.i686
chrpath-0.13-14.el7.centos.i686.rpm: does not update installed package.
Nothing to do
[root@vmCentOS7Mate Desktop]# yum erase chrpath
Loaded plugins: fastestmirror, priorities
Resolving Dependencies
--> Running transaction check
---> Package chrpath.i686 0:0.13-14.el7.centos will be erased
--> Finished Dependency Resolution
Dependencies Resolved
================================================================================
Package Arch Version Repository Size
================================================================================
Removing:
chrpath i686 0.13-14.el7.centos installed 47 k
Transaction Summary
================================================================================
Remove 1 Package
Installed size: 47 k
Is this ok [y/N]: y
Downloading packages:
Running transaction check
Running transaction test
Transaction test succeeded
Running transaction
Erasing : chrpath-0.13-14.el7.centos.i686 1/1
Verifying : chrpath-0.13-14.el7.centos.i686 1/1
Removed:
chrpath.i686 0:0.13-14.el7.centos
Complete!
[root@vmCentOS7Mate Desktop]# yum localinstall chrpath-0.13-14.el7.centos.i686.rpm
Loaded plugins: fastestmirror, priorities
Examining chrpath-0.13-14.el7.centos.i686.rpm: chrpath-0.13-14.el7.centos.i686
Nothing to do
This is similar to the response I get when I attempt to localinstall my once working RPM collection. All I can gather from the man page is that localinstall seems to have been obsoleted by install (which I guess will look in the repos for dependencies).
Bottom line, can anyone tell me what is going on? I would hope to get some sort of meaningful error message rather than nothing to do.
Yes it WAS installed but I uninstalled it. After this I could not reinstall it from the local RPM file. yum install *.rpm does not work. That was the original issue. Incidentaly I can install the local RPM file with rpm -i after uninstalling the installed version as described in the original post.
In reading the man page about yum it seems that "localinstall" is the same as "install" these days so either option will do the identical thing.
I tried yum install chrpath-0.13-14.el7 but that does not work. The package in question is NOT in any of the repos I have setup. That is why I am trying to install my own RPM. It is a 32 bit package which I need to install.
I am installing from a directory on MY (/home/ken) Desktop - running as root in the terminal. Sorry for the confusion. I really meant to say repos that I am pointing to (with entries in /etc/yum.repos.d). No local repo setup.
also the "root" desktop folder is not the same as the normal user desktop
if the rpm is in
/home/Your-User-Name/Desktop
then as a NORMAL user ~/Desktop is that folder
Then if you become root the ROOTS "~/Desktop is now
/root/Desktop
also SElinux might be throwing a temper tantrum seeing as you are trying to use the "mostly decorative" Desktop folder to install software from
check the systemD log
Thanks John VV but please stand by for a short while on my question. I stepped back to the first snapshot of my VM build. Just CentOS 7 minimal, yum priorities, my desired repos (base, updates, extras, centosplus, CR, epel, nux-dextop) and vim (need to learn vi some day I guess).
Starting with that configuration I then added my desktop "X Windows system" and mate-desktop-environment and set the VM to boot to gui. At this point I copied my wine RPM files to a folder on MY Desktop, opened a terminal on MY Desktop, cd to the folder with the RPMs, su and yum localinstall *. It worked fine! I think something I upgraded or installed after the initial install has caused the issue. I am starting over with a new VM following my build notes and I will see if I can determine when I broke the process I will post my findings tomorrow. I have to play with my new toy a little - Dell Precision T3260 with 32 GB RAM and (as soon as I install it) a 240 GB PCIs 3.0 4 lane M.2 SSS which is supposed to be fast!!!
And if it is necessary to install 32 bit wine early in the build process - and comment out wine* and a couple of other package families in yum.conf before updating... I need to decide if I want to keep the new workstation "pure 64 bit" and run my legacy Windoze programs (only 4 I think) from a VM or on the workstation as well.
What happens, exactly, when you try "yum install *.rpm"? Just saying, "Does not work," isn't going to get you much useful help.
If you need to reinstall a package, just use "yum reinstall /path/to/whatever.rpm ...".
"yum localinstall" is deprecated because "yum install" now does exactly the same thing when given a path to an RPM file rather than just a package name.
[root@vmCentOS7Mate Desktop]# yum localinstall chrpath-0.13-14.el7.centos.i686.rpm
Loaded plugins: fastestmirror, priorities
Examining chrpath-0.13-14.el7.centos.i686.rpm: chrpath-0.13-14.el7.centos.i686
Nothing to do
yum install displays exactly the same thing. "Nothing to do" is about as useful as "Does not work" I don't think I need to reinstall the package as I have uninstalled it in the prior step. I have managed to get the packages to install. I am going back through the process to see if I can figure out why and why not.
That said - when it rains it pours. I am starting the build on my new PC and I just found out that Clonezilla will not recognize my PCIe "drive". I am downloading the latest version to see if that helps. Having a snapshot of my OS partition has saved me too many times to go forward without this capability.
[root@vmCentOS7Mate Desktop]# yum localinstall chrpath-0.13-14.el7.centos.i686.rpm
Loaded plugins: fastestmirror, priorities
Examining chrpath-0.13-14.el7.centos.i686.rpm: chrpath-0.13-14.el7.centos.i686
Nothing to do
yum install displays exactly the same thing. "Nothing to do" is about as useful as "Does not work" I don't think I need to reinstall the package as I have uninstalled it in the prior step. I have managed to get the packages to install. I am going back through the process to see if I can figure out why and why not.
A specific message, any specific message, is vastly more informative than, "Does not work." I don't know how you uninstalled that package, but yum still finds it in your RPM database in /var/lib/rpm, and I'd wager quite a bit that "rpm -qi chrpath" will show it as installed. Does "rpm -V chrpath" indicate that something is wrong with the installation? If so, "yum reinstall ..." would correct that.
I snagged the latest copy of Clonzilla and can snapshot my super fast PCIe "drive" as I build my new machine. So now after spending more than half an hour on the phone with Dell - 4 transfers - trying to find the part number for a second hard drive carrier and if one was supposed to be in the new PC - finally ended up with tech support for Latin America(?) I am back to the 32 bit wine question...
Starting all over again from a snapshot of the VM, here is the whole process (+ a yum clean all just for the halibut)
Code:
[root@vmCentOS7Mate crap]# rpm -qi chrpath
Name : chrpath
Version : 0.13
Release : 14.el7.centos
Architecture: i686
Install Date: Tue 24 Jan 2017 03:55:20 PM EST
Group : Development/Tools
Size : 48450
License : GPL+
Signature : (none)
Source RPM : chrpath-0.13-14.el7.centos.src.rpm
Build Date : Mon 08 Feb 2016 09:38:11 PM EST
Build Host : vmCentOS7Mate-2
Relocations : (not relocatable)
URL : ftp://ftp.hungry.com/pub/hungry/chrpath/
Summary : Modify rpath of compiled programs
Description :
chrpath allows you to modify the dynamic library load path (rpath) of
compiled programs. Currently, only removing and modifying the rpath
is supported.
[root@vmCentOS7Mate crap]# yum erase chrpath
Loaded plugins: fastestmirror, priorities
Resolving Dependencies
--> Running transaction check
---> Package chrpath.i686 0:0.13-14.el7.centos will be erased
--> Finished Dependency Resolution
Dependencies Resolved
================================================================================
Package Arch Version Repository Size
================================================================================
Removing:
chrpath i686 0.13-14.el7.centos installed 47 k
Transaction Summary
================================================================================
Remove 1 Package
Installed size: 47 k
Is this ok [y/N]: y
Downloading packages:
Running transaction check
Running transaction test
Transaction test succeeded
Running transaction
Warning: RPMDB altered outside of yum.
Erasing : chrpath-0.13-14.el7.centos.i686 1/1
Verifying : chrpath-0.13-14.el7.centos.i686 1/1
Removed:
chrpath.i686 0:0.13-14.el7.centos
Complete!
[root@vmCentOS7Mate crap]# rpm -qi chrpath
package chrpath is not installed
[root@vmCentOS7Mate crap]# yum clean all
Loaded plugins: fastestmirror, priorities
Cleaning repos: base centosplus cr epel extras nux-dextop updates
Cleaning up everything
Cleaning up list of fastest mirrors
[root@vmCentOS7Mate crap]# yum install chrpath-0.13-14.el7.centos.i686.rpm
Loaded plugins: fastestmirror, priorities
Examining chrpath-0.13-14.el7.centos.i686.rpm: chrpath-0.13-14.el7.centos.i686
Error: Nothing to do
For no good reason I also tried
Code:
[root@vmCentOS7Mate crap]# yum reinstall chrpath-0.13-14.el7.centos.i686.rpm
Loaded plugins: fastestmirror, priorities
Examining chrpath-0.13-14.el7.centos.i686.rpm: chrpath-0.13-14.el7.centos.i686
Error: Nothing to do
Ken
p.s. I found the drive caddy on evilbay for $6 US - better than the "about $20" Dell quoted - although they gave me the wrong part #.
Well, that's just bizarre. Even if the package were still installed, "yum install chrpath-0.13-14.el7.centos.i686.rpm" should be reporting "does not update installed package" before saying, "Nothing to do." You might get something more useful with the "-v" option, though at this point I doubt it. Does "rpm -qip chrpath-0.13-14.el7.centos.i686.rpm" report information consistent with that RPM? About the only other thing I can suggest is to run "rpm --rebuilddb", but yum should be complaining if the RPM database were damaged.
Red Hat does not provide a 32-bit version of RHEL-7, so perhaps you have stumbled across a bug in the CentOS 32-bit build modifications. I don't have a 32-bit version of the OS installed anywhere, so it's hard for me to test that.
It certainly is bizarre. I have successfully installed wine-32 bit on my VM by using a copy of the VM saved a few days ago. I have also installed wine-32 bit on my new computer - twice actually. I determined that one of my Clonezilla snapshots grabbed the wrong partitions so I decided to TEST by snapshot/backup process - imagine that I restored the pre-gui snapshot, installed X Windows system and mate-desktop-environment again an just now completed installing my homemade wine. NO problems. I need to remember to exclude wine* and a couple of other things from /etc/yum.conf before I go forward.
I do need to see if it is an issue with a later version of CentOS 7.x But not right now. DOSbox is complaining about a couple of needed libraries so I am tracking them down. They ARE on my VM. Need to see what package they came from. Actually I think I will Clonzilla snapshot my working wine system and then enable the CR repo and move up to current.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
I will post my findings tomorrow. I have to play with my new toy a little - Dell Precision T3260 with 32 GB RAM and (as soon as I install it) a 240 GB PCIs 3.0 4 lane M.2 SSS which is supposed to be fast!!!
I don't think I need to reinstall the package as I have uninstalled it in the prior step. I have managed to get the packages to install. I am going back through the process to see if I can figure out why and why not.
