RPI dependency issues with latest php7.0 7.0.30-0+deb9u1 (and their dependent packages)

    • OMV 4.x
    • Resolved
    • Update
    • This is... ugly but seems to have worked.

      apt-get install php7.0-common=7.0.30-0+deb9u1 openmediavault openmediavault-flashmemory openmediavault-netatalk openmediavault-omvextrasorg php-bcmath php-cgi php-fpm php-mbstring php-pam php-xml php7.0-bcmath=7.0.30-0+deb9u1 php7.0-cgi=7.0.30-0+deb9u1 php7.0-cli=7.0.30-0+deb9u1 php7.0-fpm=7.0.30-0+deb9u1 php7.0-json=7.0.30-0+deb9u1 php7.0-mbstring=7.0.30-0+deb9u1 php7.0-opcache=7.0.30-0+deb9u1 php7.0-readline=7.0.30-0+deb9u1 php7.0-xml=7.0.30-0+deb9u1

      Basically, I started with a forced version of php7.0-common, said 'no', got the list of packages that would have been removed and tossed them in with forced version on all the php7.0-* packages. This could probably be pared down to just the php7.0 packages.
    • I guess I will have to find an rpi.

      cskrat wrote:

      This is... ugly but seems to have worked.
      That is fine too. You are just overriding the pinning by specifying all the dependencies.
      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!
    • cskrat wrote:

      This is... ugly but seems to have worked.

      apt-get install php7.0-common=7.0.30-0+deb9u1 openmediavault openmediavault-flashmemory openmediavault-netatalk openmediavault-omvextrasorg php-bcmath php-cgi php-fpm php-mbstring php-pam php-xml php7.0-bcmath=7.0.30-0+deb9u1 php7.0-cgi=7.0.30-0+deb9u1 php7.0-cli=7.0.30-0+deb9u1 php7.0-fpm=7.0.30-0+deb9u1 php7.0-json=7.0.30-0+deb9u1 php7.0-mbstring=7.0.30-0+deb9u1 php7.0-opcache=7.0.30-0+deb9u1 php7.0-readline=7.0.30-0+deb9u1 php7.0-xml=7.0.30-0+deb9u1

      Basically, I started with a forced version of php7.0-common, said 'no', got the list of packages that would have been removed and tossed them in with forced version on all the php7.0-* packages. This could probably be pared down to just the php7.0 packages.

      Sounds like a plan.

      There is one question remaining: After this forced installation of the packages, are many others like Python, libraries, ... marked for "auto-removal" at next "apt autoremove"? That was reported on my system: Link to Post

      So with next "apt autoremove" after this workaround, there would be a big hole in the system? ;(
    • Had to add from your list some packages like "openmediavault-docker-gui" or "php-curl", as they were on the "will be removed"-list. So looks like it is always a bit different for each installation:

      Source Code

      1. apt-get install php7.0-common=7.0.30-0+deb9u1 openmediavault openmediavault-flashmemory openmediavault-netatalk openmediavault-omvextrasorg php-bcmath php-cgi php-fpm php-mbstring php-pam php-xml php7.0-bcmath=7.0.30-0+deb9u1 php7.0-cgi=7.0.30-0+deb9u1 php7.0-cli=7.0.30-0+deb9u1 php7.0-fpm=7.0.30-0+deb9u1 php7.0-json=7.0.30-0+deb9u1 php7.0-mbstring=7.0.30-0+deb9u1 php7.0-opcache=7.0.30-0+deb9u1 php7.0-readline=7.0.30-0+deb9u1 php7.0-xml=7.0.30-0+deb9u1 openmediavault-docker-gui php-curl php7.0-curl=7.0.30-0+deb9u1
    • Just found out, that there is a thread, similar to this here with more people having trouble and another approach: Link to Post

      ryecoaaron wrote:

      The following lines are causing the php packages to pinned at 10 in /etc/apt/preferences.d/99raspberrypiorg which won't let them be upgraded.
      Package: *
      Pin: release n=stretch, origin archive.raspberrypi.org
      Pin-Priority: 10
      Not sure why. I commented them out and everything upgrades fine but you risk installing packages from the raspberry pi repo (raspbian). Those lines look fine to me but the origin is being ignored. I will have to figure out why.
      commenting out the lines and using an apt-get upgrade seems to do the job. However lot of packages are updated, makes me feel a bit worried, that it might be "too much".

      The post was edited 1 time, last by MrTestOne ().

    • MrTestOne wrote:

      Just found out, that there is a thread, similar to this here with more people having trouble and another approach: Link to Post
      Yep, I was posting on that one too. I just need to figure out the right pinning line since this is the problem on both of these threads.
      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!
    • Change the following lines in /etc/apt/preferences.d/99raspberrypiorg

      from Pin: release n=stretch, origin archive.raspberrypi.org

      to Pin: release o=Raspberry Pi Foundation,a=stable,n=stretch, origin archive.raspberrypi.org


      or just use this command:

      sudo sed -i "s/Pin: release n=stretch, origin archive.raspberrypi.org/Pin: release o=Raspberry Pi Foundation,a=stable,n=stretch, origin archive.raspberrypi.org/g" /etc/apt/preferences.d/99raspberrypiorg
      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!
    • MrTestOne wrote:

      However lot of packages are updated, makes me feel a bit worried, that it might be "too much".
      What is a lot? If they are all php7.0 packages then that makes sense. php7.0-curl 7.0.30 requires php7.0-common 7.0.30 which then upgrades the rest of the php7.0-* 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!
    • luckily i still have the log. Looks a bit more than just PHP:

      Source Code

      1. root@NAS2:~# sudo apt-get upgrade
      2. Reading package lists... Done
      3. Building dependency tree
      4. Reading state information... Done
      5. Calculating upgrade... Done
      6. The following packages have been kept back:
      7. hostapd
      8. The following packages will be upgraded:
      9. base-files ca-certificates device-tree-compiler dirmngr dpkg dpkg-dev gnupg
      10. gnupg-agent gnupg2 gpgv imagemagick-6-common libasound2 libasound2-data
      11. libbluetooth3 libcairo2 libcups2 libdpkg-perl libgcrypt20 libmagic-mgc libmagic1
      12. libmagickcore-6.q16-3 libmagickwand-6.q16-3 libnss-myhostname libpam-modules
      13. libpam-modules-bin libpam-runtime libpam-systemd libpam0g libperl5.24 libsoup2.4-1
      14. libsystemd0 libudev1 libxapian30 patch perl perl-base perl-modules-5.24
      15. php7.0-bcmath php7.0-cgi php7.0-cli php7.0-common php7.0-curl php7.0-fpm php7.0-json
      16. php7.0-mbstring php7.0-opcache php7.0-readline php7.0-xml sunxi-tools systemd
      17. systemd-sysv udev
      18. 52 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
      19. Need to get 30.7 MB of archives.
      20. After this operation, 604 kB of additional disk space will be used.
      21. Do you want to continue? [Y/n] y
      Display All
    • tkaiser wrote:

      Can this be enrolled to all RPi installations somehow?
      It would have to be in an omv-extras package update. I was looking at a good place to put it.
      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!
    • This issue affects the omv-extras repo pinning as well. So, people have two options:

      apt-get update
      apt-get install openmediavault-omvextrasorg=4.1.9

      -or-

      wget -O - http://omv-extras.org/install | bash
      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!
    • MrTestOne wrote:

      even though it is just somehow a walkaround. However it feels to be solid enough.
      Installing the new version of omv-extras isn't a workaround. It is the proper fix. Unfortunately, the pinning problem also prevents omv-extras from being updated from the 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!
    • ryecoaaron wrote:

      Installing the new version of omv-extras isn't a workaround. It is the proper fix. Unfortunately, the pinning problem also prevents omv-extras from being updated from the web interface.
      Hmm... that would justify touching again the OMV4 image for RPi and fixing the apt pinning in the first place? I'll have a look whether I have the SD card with the image still somewhere. Can adjust the file but not test (no RPi around any more).
    • tkaiser wrote:

      that would justify touching again the OMV4 image for RPi and fixing the apt pinning in the first place? I'll have a look whether I have the SD card with the image still somewhere. Can adjust the file but not test (no RPi around any more).
      If you want to. I can test but it is such a small change that I'm not too worried.
      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 can test but it is such a small change that I'm not too worried.
      Not worried either since this is the only change. But just to be sure at least booting of the image should be confirmed: OMV_4_Raspberry_Pi_2_3_3Plus.img.xz

      Do you take care that pinning also gets fixed when upgrading from OMV 3 to 4 with the RPi image? I believe we already talked about that but back then with the wrong outcome?
    • tkaiser wrote:

      But just to be sure at least booting of the image should be confirmed:
      I will test it later tonight when I get home (unless someone else does it first).

      tkaiser wrote:

      Do you take care that pinning also gets fixed when upgrading from OMV 3 to 4 with the RPi image? I believe we already talked about that but back then with the wrong outcome?
      If the 3.x image has the same pinnings as the 4.x image (don't remember), then the user will have to fix those pinnings. Pushing a new release of the 3.x version of omv-extras will require manual installation of omv-extras otherwise.
      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!