rpm -ivh file.rpm throws error already installed [closed]

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
-1
down vote

favorite












I uninstalled gitlab using gitlab ctl uninstall, removed /etc/gitlab, /var/opt/gitlab,/var/log/gitlab. After that I erased rpm using rpm -e file.rpm. Now when I am installing a new file.rpm, it throws an error already installed.







share|improve this question













closed as unclear what you're asking by Jeff Schaller, G-Man, Kiwy, Thomas, dr01 May 17 at 10:31


Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, it’s hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.


















    up vote
    -1
    down vote

    favorite












    I uninstalled gitlab using gitlab ctl uninstall, removed /etc/gitlab, /var/opt/gitlab,/var/log/gitlab. After that I erased rpm using rpm -e file.rpm. Now when I am installing a new file.rpm, it throws an error already installed.







    share|improve this question













    closed as unclear what you're asking by Jeff Schaller, G-Man, Kiwy, Thomas, dr01 May 17 at 10:31


    Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, it’s hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
















      up vote
      -1
      down vote

      favorite









      up vote
      -1
      down vote

      favorite











      I uninstalled gitlab using gitlab ctl uninstall, removed /etc/gitlab, /var/opt/gitlab,/var/log/gitlab. After that I erased rpm using rpm -e file.rpm. Now when I am installing a new file.rpm, it throws an error already installed.







      share|improve this question













      I uninstalled gitlab using gitlab ctl uninstall, removed /etc/gitlab, /var/opt/gitlab,/var/log/gitlab. After that I erased rpm using rpm -e file.rpm. Now when I am installing a new file.rpm, it throws an error already installed.









      share|improve this question












      share|improve this question




      share|improve this question








      edited May 10 at 7:17









      Kusalananda

      102k13199315




      102k13199315









      asked May 8 at 16:11









      User860788

      295




      295




      closed as unclear what you're asking by Jeff Schaller, G-Man, Kiwy, Thomas, dr01 May 17 at 10:31


      Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, it’s hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.






      closed as unclear what you're asking by Jeff Schaller, G-Man, Kiwy, Thomas, dr01 May 17 at 10:31


      Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, it’s hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.






















          2 Answers
          2






          active

          oldest

          votes

















          up vote
          2
          down vote













          If you don't care about the vestigal remains of your old gitlab installation, you can use rpm -Uvh /path/to/the.rpm.






          share|improve this answer





















          • But this will upgrade right? I want fresh installation.
            – User860788
            May 9 at 1:26










          • Run rpm -qa | grep rpmname. It's possible your system thinks it's still installed; possibly because your rpm -e failed.
            – DopeGhoti
            May 9 at 15:50

















          up vote
          2
          down vote



          accepted










          I fixed it using rpm -Uvh filename.rpm. It got upgraded. There was an error while using rpm -e filename. Only filename should be given and not with .rpm extension.






          share|improve this answer






























            2 Answers
            2






            active

            oldest

            votes








            2 Answers
            2






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes








            up vote
            2
            down vote













            If you don't care about the vestigal remains of your old gitlab installation, you can use rpm -Uvh /path/to/the.rpm.






            share|improve this answer





















            • But this will upgrade right? I want fresh installation.
              – User860788
              May 9 at 1:26










            • Run rpm -qa | grep rpmname. It's possible your system thinks it's still installed; possibly because your rpm -e failed.
              – DopeGhoti
              May 9 at 15:50














            up vote
            2
            down vote













            If you don't care about the vestigal remains of your old gitlab installation, you can use rpm -Uvh /path/to/the.rpm.






            share|improve this answer





















            • But this will upgrade right? I want fresh installation.
              – User860788
              May 9 at 1:26










            • Run rpm -qa | grep rpmname. It's possible your system thinks it's still installed; possibly because your rpm -e failed.
              – DopeGhoti
              May 9 at 15:50












            up vote
            2
            down vote










            up vote
            2
            down vote









            If you don't care about the vestigal remains of your old gitlab installation, you can use rpm -Uvh /path/to/the.rpm.






            share|improve this answer













            If you don't care about the vestigal remains of your old gitlab installation, you can use rpm -Uvh /path/to/the.rpm.







            share|improve this answer













            share|improve this answer



            share|improve this answer











            answered May 8 at 16:20









            DopeGhoti

            40k54779




            40k54779











            • But this will upgrade right? I want fresh installation.
              – User860788
              May 9 at 1:26










            • Run rpm -qa | grep rpmname. It's possible your system thinks it's still installed; possibly because your rpm -e failed.
              – DopeGhoti
              May 9 at 15:50
















            • But this will upgrade right? I want fresh installation.
              – User860788
              May 9 at 1:26










            • Run rpm -qa | grep rpmname. It's possible your system thinks it's still installed; possibly because your rpm -e failed.
              – DopeGhoti
              May 9 at 15:50















            But this will upgrade right? I want fresh installation.
            – User860788
            May 9 at 1:26




            But this will upgrade right? I want fresh installation.
            – User860788
            May 9 at 1:26












            Run rpm -qa | grep rpmname. It's possible your system thinks it's still installed; possibly because your rpm -e failed.
            – DopeGhoti
            May 9 at 15:50




            Run rpm -qa | grep rpmname. It's possible your system thinks it's still installed; possibly because your rpm -e failed.
            – DopeGhoti
            May 9 at 15:50












            up vote
            2
            down vote



            accepted










            I fixed it using rpm -Uvh filename.rpm. It got upgraded. There was an error while using rpm -e filename. Only filename should be given and not with .rpm extension.






            share|improve this answer



























              up vote
              2
              down vote



              accepted










              I fixed it using rpm -Uvh filename.rpm. It got upgraded. There was an error while using rpm -e filename. Only filename should be given and not with .rpm extension.






              share|improve this answer

























                up vote
                2
                down vote



                accepted







                up vote
                2
                down vote



                accepted






                I fixed it using rpm -Uvh filename.rpm. It got upgraded. There was an error while using rpm -e filename. Only filename should be given and not with .rpm extension.






                share|improve this answer















                I fixed it using rpm -Uvh filename.rpm. It got upgraded. There was an error while using rpm -e filename. Only filename should be given and not with .rpm extension.







                share|improve this answer















                share|improve this answer



                share|improve this answer








                edited May 10 at 7:31









                Debian_yadav

                8342522




                8342522











                answered May 10 at 5:46









                User860788

                295




                295












                    Popular posts from this blog

                    How to check contact read email or not when send email to Individual?

                    Bahrain

                    Postfix configuration issue with fips on centos 7; mailgun relay