How do I know that my rpm installation of a package was succesful?List the commands run by rpm packageCan't...

Is it possible that the shadow of The Moon is a single dot during solar eclipse?

Do household ovens ventilate heat to the outdoors?

What are the end bytes of *.docx file format

I feel like most of my characters are the same, what can I do?

Why do things cool down?

How should errors be reported in scientific libraries?

What is the expected way to acquire costly material components?

What is the word for a person who destroys monuments?

Why can't we use uninitialized local variable to access static content of its type?

Are lay articles good enough to be the main source of information for PhD research?

The 100 soldier problem

Tips for remembering the order of parameters for ln?

Do the villains know Batman has no superpowers?

I reverse the source code, you negate the output!

Is this quote, "just ten trading days represent 63 per cent of the returns of the past 50 years" true?

Delete empty subfolders, keep parent folder

All numbers in a 5x5 Minesweeper grid

Did HaShem ever command a Navi (Prophet) to break a law?

Can one guy with a duplicator initiate a nuclear apocalypse?

As a discovery writer, how to complete unfinished novel (which is highly diverted from original plot ) after a time-gap

Did slaves have slaves?

Why is the stock market so unpredictable?

As an employer, can I compel my employees to vote?

rule-based deletions from string list



How do I know that my rpm installation of a package was succesful?


List the commands run by rpm packageCan't installing RPM package intltool?Yum installation of package specific modulesConflicting answers regarding package from rpm, yum and repoqueryHow to remove an rpm package while keeping certain filesRPM and ISO , package installationHow to get a RPM package name required for FONTS installation on Red Hat Linux?How query custom installed rpm packageHow to set an environment variable during package installationRHEL-7.4 Linux rpm file Installation error






.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}







4















I downloaded the rpm for dos2unix and installed (on RHEL 6, 64 bit) like this



[root@xilinx Downloads]# rpm -ivh dos2unix-5.3.3-5.ram0.98.src.rpm 
1:dos2unix warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
########################################### [100%]
[root@xilinx Downloads]#


But as can be seen I am getting these warnings. Why?



How do I know that my installation of dos2unix was succesful ?



Update



[root@xilinx Downloads]# rpm -ivh dos2unix-5.3.3-5.ram0.98.src.rpm
1:dos2unix warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
########################################### [100%]
[root@xilinx Downloads]#
[root@xilinx Downloads]#
[root@xilinx Downloads]#
[root@xilinx Downloads]#
[root@xilinx Downloads]# rpm -ql dos2unix
package dos2unix is not installed
[root@xilinx Downloads]#


I then tried



[root@xilinx acme]# yum install mock
Loaded plugins: refresh-packagekit, rhnplugin
There was an error parsing the RHN proxy settings.
RHN support will be disabled.
Error: Cannot retrieve repository metadata (repomd.xml) for repository: InstallMedia. Please verify its path and try again
[root@xilinx acme]#









share|improve this question



























  • Did you mean to install the Source RPM? Or did you want to install the binary RPM? Or build the binary RPM from the source RPM?

    – jsbillings
    Jan 25 '14 at 22:51


















4















I downloaded the rpm for dos2unix and installed (on RHEL 6, 64 bit) like this



[root@xilinx Downloads]# rpm -ivh dos2unix-5.3.3-5.ram0.98.src.rpm 
1:dos2unix warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
########################################### [100%]
[root@xilinx Downloads]#


But as can be seen I am getting these warnings. Why?



How do I know that my installation of dos2unix was succesful ?



Update



[root@xilinx Downloads]# rpm -ivh dos2unix-5.3.3-5.ram0.98.src.rpm
1:dos2unix warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
########################################### [100%]
[root@xilinx Downloads]#
[root@xilinx Downloads]#
[root@xilinx Downloads]#
[root@xilinx Downloads]#
[root@xilinx Downloads]# rpm -ql dos2unix
package dos2unix is not installed
[root@xilinx Downloads]#


I then tried



[root@xilinx acme]# yum install mock
Loaded plugins: refresh-packagekit, rhnplugin
There was an error parsing the RHN proxy settings.
RHN support will be disabled.
Error: Cannot retrieve repository metadata (repomd.xml) for repository: InstallMedia. Please verify its path and try again
[root@xilinx acme]#









share|improve this question



























  • Did you mean to install the Source RPM? Or did you want to install the binary RPM? Or build the binary RPM from the source RPM?

    – jsbillings
    Jan 25 '14 at 22:51














4












4








4


0






I downloaded the rpm for dos2unix and installed (on RHEL 6, 64 bit) like this



[root@xilinx Downloads]# rpm -ivh dos2unix-5.3.3-5.ram0.98.src.rpm 
1:dos2unix warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
########################################### [100%]
[root@xilinx Downloads]#


But as can be seen I am getting these warnings. Why?



How do I know that my installation of dos2unix was succesful ?



Update



[root@xilinx Downloads]# rpm -ivh dos2unix-5.3.3-5.ram0.98.src.rpm
1:dos2unix warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
########################################### [100%]
[root@xilinx Downloads]#
[root@xilinx Downloads]#
[root@xilinx Downloads]#
[root@xilinx Downloads]#
[root@xilinx Downloads]# rpm -ql dos2unix
package dos2unix is not installed
[root@xilinx Downloads]#


I then tried



[root@xilinx acme]# yum install mock
Loaded plugins: refresh-packagekit, rhnplugin
There was an error parsing the RHN proxy settings.
RHN support will be disabled.
Error: Cannot retrieve repository metadata (repomd.xml) for repository: InstallMedia. Please verify its path and try again
[root@xilinx acme]#









share|improve this question
















I downloaded the rpm for dos2unix and installed (on RHEL 6, 64 bit) like this



[root@xilinx Downloads]# rpm -ivh dos2unix-5.3.3-5.ram0.98.src.rpm 
1:dos2unix warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
########################################### [100%]
[root@xilinx Downloads]#


But as can be seen I am getting these warnings. Why?



How do I know that my installation of dos2unix was succesful ?



Update



[root@xilinx Downloads]# rpm -ivh dos2unix-5.3.3-5.ram0.98.src.rpm
1:dos2unix warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
########################################### [100%]
[root@xilinx Downloads]#
[root@xilinx Downloads]#
[root@xilinx Downloads]#
[root@xilinx Downloads]#
[root@xilinx Downloads]# rpm -ql dos2unix
package dos2unix is not installed
[root@xilinx Downloads]#


I then tried



[root@xilinx acme]# yum install mock
Loaded plugins: refresh-packagekit, rhnplugin
There was an error parsing the RHN proxy settings.
RHN support will be disabled.
Error: Cannot retrieve repository metadata (repomd.xml) for repository: InstallMedia. Please verify its path and try again
[root@xilinx acme]#






rhel






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Jan 25 '14 at 10:49







gpuguy

















asked Jan 25 '14 at 8:00









gpuguygpuguy

4768 gold badges19 silver badges42 bronze badges




4768 gold badges19 silver badges42 bronze badges
















  • Did you mean to install the Source RPM? Or did you want to install the binary RPM? Or build the binary RPM from the source RPM?

    – jsbillings
    Jan 25 '14 at 22:51



















  • Did you mean to install the Source RPM? Or did you want to install the binary RPM? Or build the binary RPM from the source RPM?

    – jsbillings
    Jan 25 '14 at 22:51

















Did you mean to install the Source RPM? Or did you want to install the binary RPM? Or build the binary RPM from the source RPM?

– jsbillings
Jan 25 '14 at 22:51





Did you mean to install the Source RPM? Or did you want to install the binary RPM? Or build the binary RPM from the source RPM?

– jsbillings
Jan 25 '14 at 22:51










4 Answers
4






active

oldest

votes


















1
















Find out if the rpm's files have been installed:



rpm -ql dos2unix


Regarding your installation, it looks good, the rpm expects a group (mockbuild) and a user that you do not have. Should be fixed by the rpm responsible, but these are warnings only and your installation most probably worked fine.






share|improve this answer


























  • see above updated: says package dos2unix is not installed

    – gpuguy
    Jan 25 '14 at 9:12











  • not sure... the package name may be dos2unix-5.3.3-5. Can you do rpm -qa|grep dos2unix

    – Thorsten Staerk
    Jan 25 '14 at 12:02



















12
















Any time you install an RPM you can check if it's installed using RPM's query switch. You can find our 2 useful pieces of info about an installed package.



However before I get into all that notice the name of the .rpm you installed.



dos2unix-5.3.3-5.ram0.98.src.rpm


Binary RPMS vs. Source RPMs



This is a source RPM, which isn't built software (binary), rather this is a package that you can use to rebuild/recompile the normal .rpm file from. You typically do this using the rpmbuild command:



$ rpmbuild --rebuild dos2unix-5.3.3-5.ram0.98.src.rpm


You can also tell the difference if you list the contents of the package prior to installing it.



$ rpm -qpl dos2unix-5.3.3-5.ram0.98.src.rpm
dos2unix-5.3.3.tar.gz
dos2unix.spec


Notice this .rpm includes a .spec file? That's the "recipe" file for how to compile and install the dos2unix software which is also included in the file, dos2unix-5.3.3.tar.gz.



You can read more about source RPMs (aka. src.rpm or .srpm) files on the rpm.org website in this article titled: Source Package Files and How To Use Them.



So instead you should be installing a package named like this if you truly want to install dos2unix:




  • dos2unix-5.3.3-5.ram0.98.i386.rpm

  • dos2unix-5.3.3-5.ram0.98.x86_64.rpm

  • dos2unix-5.3.3-5.ram0.98.i686.rpm

  • dos2unix-5.3.3-5.ram0.98.noarch.rpm


NOTE: The rest of this post shows how you'd find binary RPM's such as these install on your system.





rpm -qi <...pkg name..>



This will give you standard information about a given package. Version, where it was built, when it was built etc.



$ rpm -qi dos2unix
Name : dos2unix
Version : 6.0.3
Release : 2.fc19
Architecture: x86_64
Install Date: Sat 07 Dec 2013 09:02:59 PM EST
Group : Applications/Text
Size : 184775
License : BSD
Signature : RSA/SHA256, Thu 14 Mar 2013 05:25:00 AM EDT, Key ID 07477e65fb4b18e6
Source RPM : dos2unix-6.0.3-2.fc19.src.rpm
Build Date : Fri 22 Feb 2013 10:50:05 AM EST
Build Host : buildvm-20.phx2.fedoraproject.org
Relocations : (not relocatable)
Packager : Fedora Project
Vendor : Fedora Project
URL : http://waterlan.home.xs4all.nl/dos2unix.html
Summary : Text file format converters
Description :
Convert text files with DOS or Mac line endings to Unix line endings and
vice versa.


rpm -ql <..pkg name..>



You can get the contents of an RPM using the rpm -ql <..pkg name..>.



$ rpm -ql dos2unix
/usr/bin/dos2unix
/usr/bin/mac2unix
/usr/bin/unix2dos
/usr/bin/unix2mac
/usr/share/doc/dos2unix-6.0.3
/usr/share/doc/dos2unix-6.0.3/COPYING.txt
/usr/share/doc/dos2unix-6.0.3/ChangeLog.txt
...


Verifying a package installation



There is a lesser though still useful switch which will allow you to verify the installation of a package. This switch will qualify the files on disk to make sure that their permissions are set correctly, the same as when it was installed, as well as perform a checksum (MD5SUM) of each file to make sure it hasn't been tampered with or changed.



$ rpm -V -v dos2unix
......... /usr/bin/dos2unix
......... /usr/bin/mac2unix
......... /usr/bin/unix2dos
......... /usr/bin/unix2mac
......... /usr/share/doc/dos2unix-6.0.3
......... d /usr/share/doc/dos2unix-6.0.3/COPYING.txt
......... d /usr/share/doc/dos2unix-6.0.3/ChangeLog.txt
......... d /usr/share/doc/dos2unix-6.0.3/NEWS.txt
...


You should only see dots in the left column. If you see letters such as S or M then you know the size or permissions are inconsistent.



excerpt from rpm man page



   S file Size differs
M Mode differs (includes permissions and file type)
5 digest (formerly MD5 sum) differs
D Device major/minor number mismatch
L readLink(2) path mismatch
U User ownership differs
G Group ownership differs
T mTime differs
P caPabilities differ





share|improve this answer




























  • This is all correct. However, the OP is never going to get useful information back from the RPM that was installed because it was a source RPM, not a regular RPM.

    – jsbillings
    Jan 25 '14 at 22:50











  • @jsbillings - OMG, completely missed that, I'll update my A to make mention of it, thanks for pointing that out...

    – slm
    Jan 25 '14 at 22:57











  • @jsbillings - thanks again for pointing this out. I've made changes to the A!

    – slm
    Jan 25 '14 at 23:18



















3
















The ‘mock’ module is responsible to build the source RPMs (SRPMs) under a chroot environment and uses the ‘mockbuild’ user. If the mockbuild user does not exist while installing the source RPM, you will receive the ‘Warning: user mockbuild does not exist. using root‘ error message. In order to fix the warning message, install the ‘mock’ module:



# yum install mock


and create the ‘mockbuild’ user



# useradd -s /sbin/nologin mockbuild


Once done, you should be able to install the required tool under the mockbuild user.



from this source






share|improve this answer

































    0
















    If you want to install a source rpm you need first to build it:



    # rpmbuild --rebuild dos2unix-5.3.3-5.ram0.98.src.rpm


    The mock package is not required to do this, so you can ignore the warnings:



    warning: user mockbuild does not exist - using root
    warning: group mockbuild does not exist - using root


    The rpmbuild will create a binary rpm. The location may vary, eg /usr/src/redhat/RPMS/ or ~/rpmbuild/RPMS (the output of rpmbuild should help with this). The RPM will be in a subdirectory representing your architecture (e.g. x86_64/). You can install normally this rpm:



    # rpm -Uvh /usr/src/redhat/RPMS/x86_64/dos2unix-5.3.3-5.x86_64.rpm


    If there were no errors, you should have the package installed:



    # rpm -q dos2unix
    dos2unix-5.3.3-5





    share|improve this answer






























      Your Answer








      StackExchange.ready(function() {
      var channelOptions = {
      tags: "".split(" "),
      id: "106"
      };
      initTagRenderer("".split(" "), "".split(" "), channelOptions);

      StackExchange.using("externalEditor", function() {
      // Have to fire editor after snippets, if snippets enabled
      if (StackExchange.settings.snippets.snippetsEnabled) {
      StackExchange.using("snippets", function() {
      createEditor();
      });
      }
      else {
      createEditor();
      }
      });

      function createEditor() {
      StackExchange.prepareEditor({
      heartbeatType: 'answer',
      autoActivateHeartbeat: false,
      convertImagesToLinks: false,
      noModals: true,
      showLowRepImageUploadWarning: true,
      reputationToPostImages: null,
      bindNavPrevention: true,
      postfix: "",
      imageUploader: {
      brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
      contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/4.0/"u003ecc by-sa 4.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
      allowUrls: true
      },
      onDemand: true,
      discardSelector: ".discard-answer"
      ,immediatelyShowMarkdownHelp:true
      });


      }
      });















      draft saved

      draft discarded
















      StackExchange.ready(
      function () {
      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f110857%2fhow-do-i-know-that-my-rpm-installation-of-a-package-was-succesful%23new-answer', 'question_page');
      }
      );

      Post as a guest















      Required, but never shown

























      4 Answers
      4






      active

      oldest

      votes








      4 Answers
      4






      active

      oldest

      votes









      active

      oldest

      votes






      active

      oldest

      votes









      1
















      Find out if the rpm's files have been installed:



      rpm -ql dos2unix


      Regarding your installation, it looks good, the rpm expects a group (mockbuild) and a user that you do not have. Should be fixed by the rpm responsible, but these are warnings only and your installation most probably worked fine.






      share|improve this answer


























      • see above updated: says package dos2unix is not installed

        – gpuguy
        Jan 25 '14 at 9:12











      • not sure... the package name may be dos2unix-5.3.3-5. Can you do rpm -qa|grep dos2unix

        – Thorsten Staerk
        Jan 25 '14 at 12:02
















      1
















      Find out if the rpm's files have been installed:



      rpm -ql dos2unix


      Regarding your installation, it looks good, the rpm expects a group (mockbuild) and a user that you do not have. Should be fixed by the rpm responsible, but these are warnings only and your installation most probably worked fine.






      share|improve this answer


























      • see above updated: says package dos2unix is not installed

        – gpuguy
        Jan 25 '14 at 9:12











      • not sure... the package name may be dos2unix-5.3.3-5. Can you do rpm -qa|grep dos2unix

        – Thorsten Staerk
        Jan 25 '14 at 12:02














      1














      1










      1









      Find out if the rpm's files have been installed:



      rpm -ql dos2unix


      Regarding your installation, it looks good, the rpm expects a group (mockbuild) and a user that you do not have. Should be fixed by the rpm responsible, but these are warnings only and your installation most probably worked fine.






      share|improve this answer













      Find out if the rpm's files have been installed:



      rpm -ql dos2unix


      Regarding your installation, it looks good, the rpm expects a group (mockbuild) and a user that you do not have. Should be fixed by the rpm responsible, but these are warnings only and your installation most probably worked fine.







      share|improve this answer












      share|improve this answer



      share|improve this answer










      answered Jan 25 '14 at 8:40









      Thorsten StaerkThorsten Staerk

      2,4221 gold badge14 silver badges24 bronze badges




      2,4221 gold badge14 silver badges24 bronze badges
















      • see above updated: says package dos2unix is not installed

        – gpuguy
        Jan 25 '14 at 9:12











      • not sure... the package name may be dos2unix-5.3.3-5. Can you do rpm -qa|grep dos2unix

        – Thorsten Staerk
        Jan 25 '14 at 12:02



















      • see above updated: says package dos2unix is not installed

        – gpuguy
        Jan 25 '14 at 9:12











      • not sure... the package name may be dos2unix-5.3.3-5. Can you do rpm -qa|grep dos2unix

        – Thorsten Staerk
        Jan 25 '14 at 12:02

















      see above updated: says package dos2unix is not installed

      – gpuguy
      Jan 25 '14 at 9:12





      see above updated: says package dos2unix is not installed

      – gpuguy
      Jan 25 '14 at 9:12













      not sure... the package name may be dos2unix-5.3.3-5. Can you do rpm -qa|grep dos2unix

      – Thorsten Staerk
      Jan 25 '14 at 12:02





      not sure... the package name may be dos2unix-5.3.3-5. Can you do rpm -qa|grep dos2unix

      – Thorsten Staerk
      Jan 25 '14 at 12:02













      12
















      Any time you install an RPM you can check if it's installed using RPM's query switch. You can find our 2 useful pieces of info about an installed package.



      However before I get into all that notice the name of the .rpm you installed.



      dos2unix-5.3.3-5.ram0.98.src.rpm


      Binary RPMS vs. Source RPMs



      This is a source RPM, which isn't built software (binary), rather this is a package that you can use to rebuild/recompile the normal .rpm file from. You typically do this using the rpmbuild command:



      $ rpmbuild --rebuild dos2unix-5.3.3-5.ram0.98.src.rpm


      You can also tell the difference if you list the contents of the package prior to installing it.



      $ rpm -qpl dos2unix-5.3.3-5.ram0.98.src.rpm
      dos2unix-5.3.3.tar.gz
      dos2unix.spec


      Notice this .rpm includes a .spec file? That's the "recipe" file for how to compile and install the dos2unix software which is also included in the file, dos2unix-5.3.3.tar.gz.



      You can read more about source RPMs (aka. src.rpm or .srpm) files on the rpm.org website in this article titled: Source Package Files and How To Use Them.



      So instead you should be installing a package named like this if you truly want to install dos2unix:




      • dos2unix-5.3.3-5.ram0.98.i386.rpm

      • dos2unix-5.3.3-5.ram0.98.x86_64.rpm

      • dos2unix-5.3.3-5.ram0.98.i686.rpm

      • dos2unix-5.3.3-5.ram0.98.noarch.rpm


      NOTE: The rest of this post shows how you'd find binary RPM's such as these install on your system.





      rpm -qi <...pkg name..>



      This will give you standard information about a given package. Version, where it was built, when it was built etc.



      $ rpm -qi dos2unix
      Name : dos2unix
      Version : 6.0.3
      Release : 2.fc19
      Architecture: x86_64
      Install Date: Sat 07 Dec 2013 09:02:59 PM EST
      Group : Applications/Text
      Size : 184775
      License : BSD
      Signature : RSA/SHA256, Thu 14 Mar 2013 05:25:00 AM EDT, Key ID 07477e65fb4b18e6
      Source RPM : dos2unix-6.0.3-2.fc19.src.rpm
      Build Date : Fri 22 Feb 2013 10:50:05 AM EST
      Build Host : buildvm-20.phx2.fedoraproject.org
      Relocations : (not relocatable)
      Packager : Fedora Project
      Vendor : Fedora Project
      URL : http://waterlan.home.xs4all.nl/dos2unix.html
      Summary : Text file format converters
      Description :
      Convert text files with DOS or Mac line endings to Unix line endings and
      vice versa.


      rpm -ql <..pkg name..>



      You can get the contents of an RPM using the rpm -ql <..pkg name..>.



      $ rpm -ql dos2unix
      /usr/bin/dos2unix
      /usr/bin/mac2unix
      /usr/bin/unix2dos
      /usr/bin/unix2mac
      /usr/share/doc/dos2unix-6.0.3
      /usr/share/doc/dos2unix-6.0.3/COPYING.txt
      /usr/share/doc/dos2unix-6.0.3/ChangeLog.txt
      ...


      Verifying a package installation



      There is a lesser though still useful switch which will allow you to verify the installation of a package. This switch will qualify the files on disk to make sure that their permissions are set correctly, the same as when it was installed, as well as perform a checksum (MD5SUM) of each file to make sure it hasn't been tampered with or changed.



      $ rpm -V -v dos2unix
      ......... /usr/bin/dos2unix
      ......... /usr/bin/mac2unix
      ......... /usr/bin/unix2dos
      ......... /usr/bin/unix2mac
      ......... /usr/share/doc/dos2unix-6.0.3
      ......... d /usr/share/doc/dos2unix-6.0.3/COPYING.txt
      ......... d /usr/share/doc/dos2unix-6.0.3/ChangeLog.txt
      ......... d /usr/share/doc/dos2unix-6.0.3/NEWS.txt
      ...


      You should only see dots in the left column. If you see letters such as S or M then you know the size or permissions are inconsistent.



      excerpt from rpm man page



         S file Size differs
      M Mode differs (includes permissions and file type)
      5 digest (formerly MD5 sum) differs
      D Device major/minor number mismatch
      L readLink(2) path mismatch
      U User ownership differs
      G Group ownership differs
      T mTime differs
      P caPabilities differ





      share|improve this answer




























      • This is all correct. However, the OP is never going to get useful information back from the RPM that was installed because it was a source RPM, not a regular RPM.

        – jsbillings
        Jan 25 '14 at 22:50











      • @jsbillings - OMG, completely missed that, I'll update my A to make mention of it, thanks for pointing that out...

        – slm
        Jan 25 '14 at 22:57











      • @jsbillings - thanks again for pointing this out. I've made changes to the A!

        – slm
        Jan 25 '14 at 23:18
















      12
















      Any time you install an RPM you can check if it's installed using RPM's query switch. You can find our 2 useful pieces of info about an installed package.



      However before I get into all that notice the name of the .rpm you installed.



      dos2unix-5.3.3-5.ram0.98.src.rpm


      Binary RPMS vs. Source RPMs



      This is a source RPM, which isn't built software (binary), rather this is a package that you can use to rebuild/recompile the normal .rpm file from. You typically do this using the rpmbuild command:



      $ rpmbuild --rebuild dos2unix-5.3.3-5.ram0.98.src.rpm


      You can also tell the difference if you list the contents of the package prior to installing it.



      $ rpm -qpl dos2unix-5.3.3-5.ram0.98.src.rpm
      dos2unix-5.3.3.tar.gz
      dos2unix.spec


      Notice this .rpm includes a .spec file? That's the "recipe" file for how to compile and install the dos2unix software which is also included in the file, dos2unix-5.3.3.tar.gz.



      You can read more about source RPMs (aka. src.rpm or .srpm) files on the rpm.org website in this article titled: Source Package Files and How To Use Them.



      So instead you should be installing a package named like this if you truly want to install dos2unix:




      • dos2unix-5.3.3-5.ram0.98.i386.rpm

      • dos2unix-5.3.3-5.ram0.98.x86_64.rpm

      • dos2unix-5.3.3-5.ram0.98.i686.rpm

      • dos2unix-5.3.3-5.ram0.98.noarch.rpm


      NOTE: The rest of this post shows how you'd find binary RPM's such as these install on your system.





      rpm -qi <...pkg name..>



      This will give you standard information about a given package. Version, where it was built, when it was built etc.



      $ rpm -qi dos2unix
      Name : dos2unix
      Version : 6.0.3
      Release : 2.fc19
      Architecture: x86_64
      Install Date: Sat 07 Dec 2013 09:02:59 PM EST
      Group : Applications/Text
      Size : 184775
      License : BSD
      Signature : RSA/SHA256, Thu 14 Mar 2013 05:25:00 AM EDT, Key ID 07477e65fb4b18e6
      Source RPM : dos2unix-6.0.3-2.fc19.src.rpm
      Build Date : Fri 22 Feb 2013 10:50:05 AM EST
      Build Host : buildvm-20.phx2.fedoraproject.org
      Relocations : (not relocatable)
      Packager : Fedora Project
      Vendor : Fedora Project
      URL : http://waterlan.home.xs4all.nl/dos2unix.html
      Summary : Text file format converters
      Description :
      Convert text files with DOS or Mac line endings to Unix line endings and
      vice versa.


      rpm -ql <..pkg name..>



      You can get the contents of an RPM using the rpm -ql <..pkg name..>.



      $ rpm -ql dos2unix
      /usr/bin/dos2unix
      /usr/bin/mac2unix
      /usr/bin/unix2dos
      /usr/bin/unix2mac
      /usr/share/doc/dos2unix-6.0.3
      /usr/share/doc/dos2unix-6.0.3/COPYING.txt
      /usr/share/doc/dos2unix-6.0.3/ChangeLog.txt
      ...


      Verifying a package installation



      There is a lesser though still useful switch which will allow you to verify the installation of a package. This switch will qualify the files on disk to make sure that their permissions are set correctly, the same as when it was installed, as well as perform a checksum (MD5SUM) of each file to make sure it hasn't been tampered with or changed.



      $ rpm -V -v dos2unix
      ......... /usr/bin/dos2unix
      ......... /usr/bin/mac2unix
      ......... /usr/bin/unix2dos
      ......... /usr/bin/unix2mac
      ......... /usr/share/doc/dos2unix-6.0.3
      ......... d /usr/share/doc/dos2unix-6.0.3/COPYING.txt
      ......... d /usr/share/doc/dos2unix-6.0.3/ChangeLog.txt
      ......... d /usr/share/doc/dos2unix-6.0.3/NEWS.txt
      ...


      You should only see dots in the left column. If you see letters such as S or M then you know the size or permissions are inconsistent.



      excerpt from rpm man page



         S file Size differs
      M Mode differs (includes permissions and file type)
      5 digest (formerly MD5 sum) differs
      D Device major/minor number mismatch
      L readLink(2) path mismatch
      U User ownership differs
      G Group ownership differs
      T mTime differs
      P caPabilities differ





      share|improve this answer




























      • This is all correct. However, the OP is never going to get useful information back from the RPM that was installed because it was a source RPM, not a regular RPM.

        – jsbillings
        Jan 25 '14 at 22:50











      • @jsbillings - OMG, completely missed that, I'll update my A to make mention of it, thanks for pointing that out...

        – slm
        Jan 25 '14 at 22:57











      • @jsbillings - thanks again for pointing this out. I've made changes to the A!

        – slm
        Jan 25 '14 at 23:18














      12














      12










      12









      Any time you install an RPM you can check if it's installed using RPM's query switch. You can find our 2 useful pieces of info about an installed package.



      However before I get into all that notice the name of the .rpm you installed.



      dos2unix-5.3.3-5.ram0.98.src.rpm


      Binary RPMS vs. Source RPMs



      This is a source RPM, which isn't built software (binary), rather this is a package that you can use to rebuild/recompile the normal .rpm file from. You typically do this using the rpmbuild command:



      $ rpmbuild --rebuild dos2unix-5.3.3-5.ram0.98.src.rpm


      You can also tell the difference if you list the contents of the package prior to installing it.



      $ rpm -qpl dos2unix-5.3.3-5.ram0.98.src.rpm
      dos2unix-5.3.3.tar.gz
      dos2unix.spec


      Notice this .rpm includes a .spec file? That's the "recipe" file for how to compile and install the dos2unix software which is also included in the file, dos2unix-5.3.3.tar.gz.



      You can read more about source RPMs (aka. src.rpm or .srpm) files on the rpm.org website in this article titled: Source Package Files and How To Use Them.



      So instead you should be installing a package named like this if you truly want to install dos2unix:




      • dos2unix-5.3.3-5.ram0.98.i386.rpm

      • dos2unix-5.3.3-5.ram0.98.x86_64.rpm

      • dos2unix-5.3.3-5.ram0.98.i686.rpm

      • dos2unix-5.3.3-5.ram0.98.noarch.rpm


      NOTE: The rest of this post shows how you'd find binary RPM's such as these install on your system.





      rpm -qi <...pkg name..>



      This will give you standard information about a given package. Version, where it was built, when it was built etc.



      $ rpm -qi dos2unix
      Name : dos2unix
      Version : 6.0.3
      Release : 2.fc19
      Architecture: x86_64
      Install Date: Sat 07 Dec 2013 09:02:59 PM EST
      Group : Applications/Text
      Size : 184775
      License : BSD
      Signature : RSA/SHA256, Thu 14 Mar 2013 05:25:00 AM EDT, Key ID 07477e65fb4b18e6
      Source RPM : dos2unix-6.0.3-2.fc19.src.rpm
      Build Date : Fri 22 Feb 2013 10:50:05 AM EST
      Build Host : buildvm-20.phx2.fedoraproject.org
      Relocations : (not relocatable)
      Packager : Fedora Project
      Vendor : Fedora Project
      URL : http://waterlan.home.xs4all.nl/dos2unix.html
      Summary : Text file format converters
      Description :
      Convert text files with DOS or Mac line endings to Unix line endings and
      vice versa.


      rpm -ql <..pkg name..>



      You can get the contents of an RPM using the rpm -ql <..pkg name..>.



      $ rpm -ql dos2unix
      /usr/bin/dos2unix
      /usr/bin/mac2unix
      /usr/bin/unix2dos
      /usr/bin/unix2mac
      /usr/share/doc/dos2unix-6.0.3
      /usr/share/doc/dos2unix-6.0.3/COPYING.txt
      /usr/share/doc/dos2unix-6.0.3/ChangeLog.txt
      ...


      Verifying a package installation



      There is a lesser though still useful switch which will allow you to verify the installation of a package. This switch will qualify the files on disk to make sure that their permissions are set correctly, the same as when it was installed, as well as perform a checksum (MD5SUM) of each file to make sure it hasn't been tampered with or changed.



      $ rpm -V -v dos2unix
      ......... /usr/bin/dos2unix
      ......... /usr/bin/mac2unix
      ......... /usr/bin/unix2dos
      ......... /usr/bin/unix2mac
      ......... /usr/share/doc/dos2unix-6.0.3
      ......... d /usr/share/doc/dos2unix-6.0.3/COPYING.txt
      ......... d /usr/share/doc/dos2unix-6.0.3/ChangeLog.txt
      ......... d /usr/share/doc/dos2unix-6.0.3/NEWS.txt
      ...


      You should only see dots in the left column. If you see letters such as S or M then you know the size or permissions are inconsistent.



      excerpt from rpm man page



         S file Size differs
      M Mode differs (includes permissions and file type)
      5 digest (formerly MD5 sum) differs
      D Device major/minor number mismatch
      L readLink(2) path mismatch
      U User ownership differs
      G Group ownership differs
      T mTime differs
      P caPabilities differ





      share|improve this answer















      Any time you install an RPM you can check if it's installed using RPM's query switch. You can find our 2 useful pieces of info about an installed package.



      However before I get into all that notice the name of the .rpm you installed.



      dos2unix-5.3.3-5.ram0.98.src.rpm


      Binary RPMS vs. Source RPMs



      This is a source RPM, which isn't built software (binary), rather this is a package that you can use to rebuild/recompile the normal .rpm file from. You typically do this using the rpmbuild command:



      $ rpmbuild --rebuild dos2unix-5.3.3-5.ram0.98.src.rpm


      You can also tell the difference if you list the contents of the package prior to installing it.



      $ rpm -qpl dos2unix-5.3.3-5.ram0.98.src.rpm
      dos2unix-5.3.3.tar.gz
      dos2unix.spec


      Notice this .rpm includes a .spec file? That's the "recipe" file for how to compile and install the dos2unix software which is also included in the file, dos2unix-5.3.3.tar.gz.



      You can read more about source RPMs (aka. src.rpm or .srpm) files on the rpm.org website in this article titled: Source Package Files and How To Use Them.



      So instead you should be installing a package named like this if you truly want to install dos2unix:




      • dos2unix-5.3.3-5.ram0.98.i386.rpm

      • dos2unix-5.3.3-5.ram0.98.x86_64.rpm

      • dos2unix-5.3.3-5.ram0.98.i686.rpm

      • dos2unix-5.3.3-5.ram0.98.noarch.rpm


      NOTE: The rest of this post shows how you'd find binary RPM's such as these install on your system.





      rpm -qi <...pkg name..>



      This will give you standard information about a given package. Version, where it was built, when it was built etc.



      $ rpm -qi dos2unix
      Name : dos2unix
      Version : 6.0.3
      Release : 2.fc19
      Architecture: x86_64
      Install Date: Sat 07 Dec 2013 09:02:59 PM EST
      Group : Applications/Text
      Size : 184775
      License : BSD
      Signature : RSA/SHA256, Thu 14 Mar 2013 05:25:00 AM EDT, Key ID 07477e65fb4b18e6
      Source RPM : dos2unix-6.0.3-2.fc19.src.rpm
      Build Date : Fri 22 Feb 2013 10:50:05 AM EST
      Build Host : buildvm-20.phx2.fedoraproject.org
      Relocations : (not relocatable)
      Packager : Fedora Project
      Vendor : Fedora Project
      URL : http://waterlan.home.xs4all.nl/dos2unix.html
      Summary : Text file format converters
      Description :
      Convert text files with DOS or Mac line endings to Unix line endings and
      vice versa.


      rpm -ql <..pkg name..>



      You can get the contents of an RPM using the rpm -ql <..pkg name..>.



      $ rpm -ql dos2unix
      /usr/bin/dos2unix
      /usr/bin/mac2unix
      /usr/bin/unix2dos
      /usr/bin/unix2mac
      /usr/share/doc/dos2unix-6.0.3
      /usr/share/doc/dos2unix-6.0.3/COPYING.txt
      /usr/share/doc/dos2unix-6.0.3/ChangeLog.txt
      ...


      Verifying a package installation



      There is a lesser though still useful switch which will allow you to verify the installation of a package. This switch will qualify the files on disk to make sure that their permissions are set correctly, the same as when it was installed, as well as perform a checksum (MD5SUM) of each file to make sure it hasn't been tampered with or changed.



      $ rpm -V -v dos2unix
      ......... /usr/bin/dos2unix
      ......... /usr/bin/mac2unix
      ......... /usr/bin/unix2dos
      ......... /usr/bin/unix2mac
      ......... /usr/share/doc/dos2unix-6.0.3
      ......... d /usr/share/doc/dos2unix-6.0.3/COPYING.txt
      ......... d /usr/share/doc/dos2unix-6.0.3/ChangeLog.txt
      ......... d /usr/share/doc/dos2unix-6.0.3/NEWS.txt
      ...


      You should only see dots in the left column. If you see letters such as S or M then you know the size or permissions are inconsistent.



      excerpt from rpm man page



         S file Size differs
      M Mode differs (includes permissions and file type)
      5 digest (formerly MD5 sum) differs
      D Device major/minor number mismatch
      L readLink(2) path mismatch
      U User ownership differs
      G Group ownership differs
      T mTime differs
      P caPabilities differ






      share|improve this answer














      share|improve this answer



      share|improve this answer








      edited Jan 25 '14 at 23:18

























      answered Jan 25 '14 at 14:24









      slmslm

      269k75 gold badges583 silver badges729 bronze badges




      269k75 gold badges583 silver badges729 bronze badges
















      • This is all correct. However, the OP is never going to get useful information back from the RPM that was installed because it was a source RPM, not a regular RPM.

        – jsbillings
        Jan 25 '14 at 22:50











      • @jsbillings - OMG, completely missed that, I'll update my A to make mention of it, thanks for pointing that out...

        – slm
        Jan 25 '14 at 22:57











      • @jsbillings - thanks again for pointing this out. I've made changes to the A!

        – slm
        Jan 25 '14 at 23:18



















      • This is all correct. However, the OP is never going to get useful information back from the RPM that was installed because it was a source RPM, not a regular RPM.

        – jsbillings
        Jan 25 '14 at 22:50











      • @jsbillings - OMG, completely missed that, I'll update my A to make mention of it, thanks for pointing that out...

        – slm
        Jan 25 '14 at 22:57











      • @jsbillings - thanks again for pointing this out. I've made changes to the A!

        – slm
        Jan 25 '14 at 23:18

















      This is all correct. However, the OP is never going to get useful information back from the RPM that was installed because it was a source RPM, not a regular RPM.

      – jsbillings
      Jan 25 '14 at 22:50





      This is all correct. However, the OP is never going to get useful information back from the RPM that was installed because it was a source RPM, not a regular RPM.

      – jsbillings
      Jan 25 '14 at 22:50













      @jsbillings - OMG, completely missed that, I'll update my A to make mention of it, thanks for pointing that out...

      – slm
      Jan 25 '14 at 22:57





      @jsbillings - OMG, completely missed that, I'll update my A to make mention of it, thanks for pointing that out...

      – slm
      Jan 25 '14 at 22:57













      @jsbillings - thanks again for pointing this out. I've made changes to the A!

      – slm
      Jan 25 '14 at 23:18





      @jsbillings - thanks again for pointing this out. I've made changes to the A!

      – slm
      Jan 25 '14 at 23:18











      3
















      The ‘mock’ module is responsible to build the source RPMs (SRPMs) under a chroot environment and uses the ‘mockbuild’ user. If the mockbuild user does not exist while installing the source RPM, you will receive the ‘Warning: user mockbuild does not exist. using root‘ error message. In order to fix the warning message, install the ‘mock’ module:



      # yum install mock


      and create the ‘mockbuild’ user



      # useradd -s /sbin/nologin mockbuild


      Once done, you should be able to install the required tool under the mockbuild user.



      from this source






      share|improve this answer






























        3
















        The ‘mock’ module is responsible to build the source RPMs (SRPMs) under a chroot environment and uses the ‘mockbuild’ user. If the mockbuild user does not exist while installing the source RPM, you will receive the ‘Warning: user mockbuild does not exist. using root‘ error message. In order to fix the warning message, install the ‘mock’ module:



        # yum install mock


        and create the ‘mockbuild’ user



        # useradd -s /sbin/nologin mockbuild


        Once done, you should be able to install the required tool under the mockbuild user.



        from this source






        share|improve this answer




























          3














          3










          3









          The ‘mock’ module is responsible to build the source RPMs (SRPMs) under a chroot environment and uses the ‘mockbuild’ user. If the mockbuild user does not exist while installing the source RPM, you will receive the ‘Warning: user mockbuild does not exist. using root‘ error message. In order to fix the warning message, install the ‘mock’ module:



          # yum install mock


          and create the ‘mockbuild’ user



          # useradd -s /sbin/nologin mockbuild


          Once done, you should be able to install the required tool under the mockbuild user.



          from this source






          share|improve this answer













          The ‘mock’ module is responsible to build the source RPMs (SRPMs) under a chroot environment and uses the ‘mockbuild’ user. If the mockbuild user does not exist while installing the source RPM, you will receive the ‘Warning: user mockbuild does not exist. using root‘ error message. In order to fix the warning message, install the ‘mock’ module:



          # yum install mock


          and create the ‘mockbuild’ user



          # useradd -s /sbin/nologin mockbuild


          Once done, you should be able to install the required tool under the mockbuild user.



          from this source







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Apr 29 '15 at 8:33









          MichaelMichael

          1461 silver badge6 bronze badges




          1461 silver badge6 bronze badges


























              0
















              If you want to install a source rpm you need first to build it:



              # rpmbuild --rebuild dos2unix-5.3.3-5.ram0.98.src.rpm


              The mock package is not required to do this, so you can ignore the warnings:



              warning: user mockbuild does not exist - using root
              warning: group mockbuild does not exist - using root


              The rpmbuild will create a binary rpm. The location may vary, eg /usr/src/redhat/RPMS/ or ~/rpmbuild/RPMS (the output of rpmbuild should help with this). The RPM will be in a subdirectory representing your architecture (e.g. x86_64/). You can install normally this rpm:



              # rpm -Uvh /usr/src/redhat/RPMS/x86_64/dos2unix-5.3.3-5.x86_64.rpm


              If there were no errors, you should have the package installed:



              # rpm -q dos2unix
              dos2unix-5.3.3-5





              share|improve this answer
































                0
















                If you want to install a source rpm you need first to build it:



                # rpmbuild --rebuild dos2unix-5.3.3-5.ram0.98.src.rpm


                The mock package is not required to do this, so you can ignore the warnings:



                warning: user mockbuild does not exist - using root
                warning: group mockbuild does not exist - using root


                The rpmbuild will create a binary rpm. The location may vary, eg /usr/src/redhat/RPMS/ or ~/rpmbuild/RPMS (the output of rpmbuild should help with this). The RPM will be in a subdirectory representing your architecture (e.g. x86_64/). You can install normally this rpm:



                # rpm -Uvh /usr/src/redhat/RPMS/x86_64/dos2unix-5.3.3-5.x86_64.rpm


                If there were no errors, you should have the package installed:



                # rpm -q dos2unix
                dos2unix-5.3.3-5





                share|improve this answer






























                  0














                  0










                  0









                  If you want to install a source rpm you need first to build it:



                  # rpmbuild --rebuild dos2unix-5.3.3-5.ram0.98.src.rpm


                  The mock package is not required to do this, so you can ignore the warnings:



                  warning: user mockbuild does not exist - using root
                  warning: group mockbuild does not exist - using root


                  The rpmbuild will create a binary rpm. The location may vary, eg /usr/src/redhat/RPMS/ or ~/rpmbuild/RPMS (the output of rpmbuild should help with this). The RPM will be in a subdirectory representing your architecture (e.g. x86_64/). You can install normally this rpm:



                  # rpm -Uvh /usr/src/redhat/RPMS/x86_64/dos2unix-5.3.3-5.x86_64.rpm


                  If there were no errors, you should have the package installed:



                  # rpm -q dos2unix
                  dos2unix-5.3.3-5





                  share|improve this answer















                  If you want to install a source rpm you need first to build it:



                  # rpmbuild --rebuild dos2unix-5.3.3-5.ram0.98.src.rpm


                  The mock package is not required to do this, so you can ignore the warnings:



                  warning: user mockbuild does not exist - using root
                  warning: group mockbuild does not exist - using root


                  The rpmbuild will create a binary rpm. The location may vary, eg /usr/src/redhat/RPMS/ or ~/rpmbuild/RPMS (the output of rpmbuild should help with this). The RPM will be in a subdirectory representing your architecture (e.g. x86_64/). You can install normally this rpm:



                  # rpm -Uvh /usr/src/redhat/RPMS/x86_64/dos2unix-5.3.3-5.x86_64.rpm


                  If there were no errors, you should have the package installed:



                  # rpm -q dos2unix
                  dos2unix-5.3.3-5






                  share|improve this answer














                  share|improve this answer



                  share|improve this answer








                  edited 54 mins ago









                  jamsandwich

                  31 bronze badge




                  31 bronze badge










                  answered Apr 25 '16 at 14:35









                  mikmik

                  9507 silver badges15 bronze badges




                  9507 silver badges15 bronze badges


































                      draft saved

                      draft discarded



















































                      Thanks for contributing an answer to Unix & Linux Stack Exchange!


                      • Please be sure to answer the question. Provide details and share your research!

                      But avoid



                      • Asking for help, clarification, or responding to other answers.

                      • Making statements based on opinion; back them up with references or personal experience.


                      To learn more, see our tips on writing great answers.




                      draft saved


                      draft discarded














                      StackExchange.ready(
                      function () {
                      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f110857%2fhow-do-i-know-that-my-rpm-installation-of-a-package-was-succesful%23new-answer', 'question_page');
                      }
                      );

                      Post as a guest















                      Required, but never shown





















































                      Required, but never shown














                      Required, but never shown












                      Required, but never shown







                      Required, but never shown

































                      Required, but never shown














                      Required, but never shown












                      Required, but never shown







                      Required, but never shown







                      Popular posts from this blog

                      Taj Mahal Inhaltsverzeichnis Aufbau | Geschichte | 350-Jahr-Feier | Heutige Bedeutung | Siehe auch |...

                      Baia Sprie Cuprins Etimologie | Istorie | Demografie | Politică și administrație | Arii naturale...

                      Ciclooctatetraenă Vezi și | Bibliografie | Meniu de navigare637866text4148569-500570979m