openmediavault-transmissionbt fails to install on Raspberry Pi due to dependencies.

    • OMV 1.0
    • Resolved

    This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

    • openmediavault-transmissionbt fails to install on Raspberry Pi due to dependencies.

      Hello everyone.

      I'm trying to install openmediavault-transmissionbt on OMV 1.0.29 on a Raspberry Pi.

      The installation fails due to dependencies not being installed; it appears transmission-deamon and transmission-cli are not going to be installed.
      If I add these 2 packages to then another dependency is missing (transmission-common), well, the necessary version is missing.

      Source Code

      1. root@pi:~# apt-get install openmediavault-transmissionbt
      2. Reading package lists... Done
      3. Building dependency tree
      4. Reading state information... Done
      5. Some packages could not be installed. This may mean that you have
      6. requested an impossible situation or if you are using the unstable
      7. distribution that some required packages have not yet been created
      8. or been moved out of Incoming.
      9. The following information may help to resolve the situation:
      10. The following packages have unmet dependencies:
      11. openmediavault-transmissionbt : Depends: transmission-daemon but it is not going to be installed
      12. Depends: transmission-cli but it is not going to be installed
      13. E: Unable to correct problems, you have held broken packages.
      Display All


      If I add these 2 packages to then another dependency is missing (transmission-common), well, the necessary version is missing.

      Source Code

      1. root@pi:~# apt-get install openmediavault-transmissionbt transmission-daemon transmission-cli
      2. Reading package lists... Done
      3. Building dependency tree
      4. Reading state information... Done
      5. Some packages could not be installed. This may mean that you have
      6. requested an impossible situation or if you are using the unstable
      7. distribution that some required packages have not yet been created
      8. or been moved out of Incoming.
      9. The following information may help to resolve the situation:
      10. The following packages have unmet dependencies:
      11. transmission-cli : Depends: transmission-common (= 2.82-1.1) but it is not going to be installed
      12. transmission-daemon : Depends: transmission-common (= 2.82-1.1) but it is not going to be installed
      13. E: Unable to correct problems, you have held broken packages.
      Display All


      If I then look for the package version on the Wheezy repository I can see it's an older version.

      Source Code

      1. root@pi:~# apt-cache madison transmission-common
      2. transmission-common | 2.52-3+nmu2 | http://mirrordirector.raspbian.org/raspbian/ wheezy/main armhf Packages


      Now, I can see the available version is 2.52-3 while the required one is 2.82-1.1.
      I have then tried to add Jessie repository which I know having more up-to-date packages; at least this is the repo I had been using to get transmission up and running on RaspBMC.

      After this change I can find a more recent version of the package (2.84-0.1) but apparently this is way too recent for the plugin.

      Source Code

      1. root@pi:~# apt-get install openmediavault-transmissionbt transmission-daemon transmission-cli transmission-common
      2. Reading package lists... Done
      3. Building dependency tree
      4. Reading state information... Done
      5. Some packages could not be installed. This may mean that you have
      6. requested an impossible situation or if you are using the unstable
      7. distribution that some required packages have not yet been created
      8. or been moved out of Incoming.
      9. The following information may help to resolve the situation:
      10. The following packages have unmet dependencies:
      11. transmission-cli : Depends: transmission-common (= 2.82-1.1) but 2.84-0.1 is to be installed
      12. transmission-daemon : Depends: transmission-common (= 2.82-1.1) but 2.84-0.1 is to be installed
      13. E: Unable to correct problems, you have held broken packages.
      Display All


      Unfortunately no-one of the 2 repositories offer the version 2.82.1.1

      Source Code

      1. root@pi:~# apt-cache madison transmission-common
      2. transmission-common | 2.84-0.1 | http://mirrordirector.raspbian.org/raspbian/ jessie/main armhf Packages
      3. transmission-common | 2.52-3+nmu2 | http://mirrordirector.raspbian.org/raspbian/ wheezy/main armhf Packages


      Can somebody offer any advice or help please?

      Thank you.
    • I made armhf transmission packages on the RPi and they are in the testing repo. Enable the testing repo on the Primary tab of omv-extras and it should find the packages.
      omv 4.1.13 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.13
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • ryecoaaron wrote:

      I made armhf transmission packages on the RPi and they are in the testing repo. Enable the testing repo on the Primary tab of omv-extras and it should find the packages.
      I have the same problem but I don't understand the solution. How exactly do I "enable the testing repo on the primary tab of omv-extras"? I am on a headless raspberry pi via ssh, so I am restricted to console.
    • sieste wrote:

      How exactly do I "enable the testing repo on the primary tab of omv-extras"? I am on a headless raspberry pi via ssh, so I am restricted to console.
      Why can't you use the OMV web interface?
      omv 4.1.13 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.13
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • TobyMacdonnell wrote:

      Frustrating when all tutorials don't have this problem.
      If you used the RPi image on sourceforge, you wouldn't have this problem. It is jessie as well.
      omv 4.1.13 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.13
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • Some packages could not be installed. This may mean that you have
      requested an impossible situation or if you are using the unstable
      distribution that some required packages have not yet been created
      or been moved out of Incoming.
      The following information may help to resolve the situation:

      The following packages have unmet dependencies:
      openmediavault : Depends: php5-fpm but it is not installable
      Depends: php5-cgi but it is not installable
      Depends: php5-cli (>= 5.6) but it is not installable
      Depends: php5-pam but it is not going to be installed
      E: Unable to correct problems, you have held broken packages.
      dpkg-query: package 'openmediavault' is not installed and no information is available
      Use dpkg --info (= dpkg-deb --info) to examine archive files,
      and dpkg --contents (= dpkg-deb --contents) to list their contents.
      /usr/sbin/dpkg-reconfigure: openmediavault is not installed
      ./two.sh: 47: ./two.sh: omv-initsystem: not found

      This is what I get... every time...
    • TobyMacdonnell wrote:

      The following packages have unmet dependencies:

      openmediavault : Depends: php5-fpm but it is not installable
      Depends: php5-cgi but it is not installable
      Depends: php5-cli (>= 5.6) but it is not installable
      Depends: php5-pam but it is not going to be installed
      E: Unable to correct problems, you have held broken packages.
      Have you managed to fix the problem? I'm having the same currently