ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Solved ScreenConnect agent on Fedora fails rpm install

    IT Discussion
    screenconnect fedora 28 connectwise control
    8
    27
    2.8k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • D
      dyasny @JaredBusch
      last edited by

      @JaredBusch said in ScreenConnect agent on Fedora fails rpm install:

      @dyasny yum/dnf does not magically resolve dependencies.

      The RPM has to have them noted.

      Yup, only the rpm command will try to install and fail, while the yum command will resolve the deps.

      JaredBuschJ 1 Reply Last reply Reply Quote 0
      • JaredBuschJ
        JaredBusch @dyasny
        last edited by

        @dyasny said in ScreenConnect agent on Fedora fails rpm install:

        @JaredBusch said in ScreenConnect agent on Fedora fails rpm install:

        @dyasny yum/dnf does not magically resolve dependencies.

        The RPM has to have them noted.

        Yup, only the rpm command will try to install and fail, while the yum command will resolve the deps.

        Only if the deps are defined in the RPM package.

        D 1 Reply Last reply Reply Quote 0
        • Reid CooperR
          Reid Cooper
          last edited by

          YUM or DNF is the better way to go, but yeah, if the RPM doesn't have any deps, they won't do anything special compared to just installing with the RPM command. I would agree, a better practice to use them, but remember that they might not have any dependencies to check against.

          1 Reply Last reply Reply Quote 0
          • D
            dyasny @JaredBusch
            last edited by

            @JaredBusch said in ScreenConnect agent on Fedora fails rpm install:

            Only if the deps are defined in the RPM package.

            You really cannot distinguish between an RPM packaging format and the rpm command?

            travisdh1T 1 Reply Last reply Reply Quote 0
            • travisdh1T
              travisdh1 @dyasny
              last edited by

              @dyasny said in ScreenConnect agent on Fedora fails rpm install:

              @JaredBusch said in ScreenConnect agent on Fedora fails rpm install:

              Only if the deps are defined in the RPM package.

              You really cannot distinguish between an RPM packaging format and the rpm command?

              Wha? I think @JaredBusch can distinguish between the two just fine.

              D 1 Reply Last reply Reply Quote 0
              • D
                dyasny @travisdh1
                last edited by

                @travisdh1 said in ScreenConnect agent on Fedora fails rpm install:

                Wha? I think @JaredBusch can distinguish between the two just fine.

                He's skipping from installing packages using the rpm command to the specifics of formatting the dependency chain in an RPM package declaration. Two very different things right there

                1 Reply Last reply Reply Quote 0
                • JaredBuschJ
                  JaredBusch
                  last edited by JaredBusch

                  @JaredBusch said in ScreenConnect agent on Fedora fails rpm install:

                  rpm -U ConnectWiseControl.ClientSetup.rpm

                  ConnectWise Control version 19.0.23234.7027 resolved the failure to update. but they neglected to remove the old screenconnect version as the new install is named connectwisecontrol

                  bc755dec-f586-4439-a406-222af7737ed0-image.png

                  1 Reply Last reply Reply Quote 3
                  • 1
                  • 2
                  • 2 / 2
                  • First post
                    Last post