[Solved] Cannot upgrade VDR 2.4.6 to VDR 2.4.7 and Plugins

  • Hi all,

    I have Yavdr based on Ansible:


    Quote

    Distributor ID: Ubuntu

    Description: Ubuntu 20.04.2 LTS

    Release: 20.04

    Codename: focal


    I can see that I can upgrade VDR 2.4.6 and its plugins to VDR 2.4.7 but apt-get upgrade reports that the update will not be performed.

    Here is the output of the command:




    What I am doing wrong?

    How to update VDR and the plugins to the newer version?

    Thank you.

    YaVDR Ansible VM (VDR 2.4.0) as a VNSI Server and Streamdev Server. DD CINE S2 + 2 x DD Duoflex S2 (6 tuners)

    Modified Reelbox AVG II with working display: Gigabyte C1037UN-EU + EHD + 4GB ram + 32GB SSD. Streamdev client only.BM2LTS
    VDR1- ASUS AT3IONTI, 4gb RAM, 32GB SSD, MCE Remote, Custom case, YAVDR 0.6.2

    VDR2- ASUS AT5IONTI, 4gb RAM, 128GB SSD, MCE Remote, D-Vine 5 HTPC Case, YAVDR Ansible, Ubuntu 20.04.2

    4 x KODI (Libreelec) - Asus AT3IONTI, 2gb RAM, 32gb SSD, MCE Remote @ Nokia dBox1 case

    Raspberry PI3 b Plus - MLD (experimental)

    UNRAID - 80 TB storage, Supermicro X10SRL -F + Xeon E5-2680 v3 + 128 GB ECC Ram.

  • Please show the output of apt policy vdr and sudo apt install --dry-run vdr

    yaVDR-Dokumentation (Ceterum censeo enchiridia esse lectitanda.)

  • Thank you, Seahawk.

    Here is the output:


    YaVDR Ansible VM (VDR 2.4.0) as a VNSI Server and Streamdev Server. DD CINE S2 + 2 x DD Duoflex S2 (6 tuners)

    Modified Reelbox AVG II with working display: Gigabyte C1037UN-EU + EHD + 4GB ram + 32GB SSD. Streamdev client only.BM2LTS
    VDR1- ASUS AT3IONTI, 4gb RAM, 32GB SSD, MCE Remote, Custom case, YAVDR 0.6.2

    VDR2- ASUS AT5IONTI, 4gb RAM, 128GB SSD, MCE Remote, D-Vine 5 HTPC Case, YAVDR Ansible, Ubuntu 20.04.2

    4 x KODI (Libreelec) - Asus AT3IONTI, 2gb RAM, 32gb SSD, MCE Remote @ Nokia dBox1 case

    Raspberry PI3 b Plus - MLD (experimental)

    UNRAID - 80 TB storage, Supermicro X10SRL -F + Xeon E5-2680 v3 + 128 GB ECC Ram.

  • I think this happens because you used apt upgrade instead of apt dist-upgrade resp. apt full-upgrade - although I am not completely sure which package would be removed by updating the packages (maybe the virtual vdr-abi package?).

    Code
    1. upgrade (apt-get(8))
    2. upgrade is used to install available upgrades of all packages currently installed on
    3. the system from the sources configured via sources.list(5). New packages will be
    4. installed if required to satisfy dependencies, but existing packages will never be
    5. removed. If an upgrade for a package requires the remove of an installed package the
    6. upgrade for this package isn't performed.
    7. full-upgrade (apt-get(8))
    8. full-upgrade performs the function of upgrade but will remove currently installed
    9. packages if this is needed to upgrade the system as a whole.

    yaVDR-Dokumentation (Ceterum censeo enchiridia esse lectitanda.)

  • If I understand correctly I need to perform apt dist-upgrade

    What is strange is that I was successfully upgrading available packages in the system up to this moment with apt-get upgrade. The problem occurred once VDR 2.4.7 and the respective plugins came available (for upgrade) and I got message that they are not going to be upgraded by a reason unknown to my knowledge.

    I am a little bit hesitant to perform apt-dist upgrade if you think there is a risk to break something as this system is my main living-room one and the family is using it all the time, and it is working very stable and reliable.


    Edited: Just performed apt upgrade instead of apt-get upgrade

    This time it worked:


    All packages updated correctly. Here is the output from vdr -V


    Thank you.

    YaVDR Ansible VM (VDR 2.4.0) as a VNSI Server and Streamdev Server. DD CINE S2 + 2 x DD Duoflex S2 (6 tuners)

    Modified Reelbox AVG II with working display: Gigabyte C1037UN-EU + EHD + 4GB ram + 32GB SSD. Streamdev client only.BM2LTS
    VDR1- ASUS AT3IONTI, 4gb RAM, 32GB SSD, MCE Remote, Custom case, YAVDR 0.6.2

    VDR2- ASUS AT5IONTI, 4gb RAM, 128GB SSD, MCE Remote, D-Vine 5 HTPC Case, YAVDR Ansible, Ubuntu 20.04.2

    4 x KODI (Libreelec) - Asus AT3IONTI, 2gb RAM, 32gb SSD, MCE Remote @ Nokia dBox1 case

    Raspberry PI3 b Plus - MLD (experimental)

    UNRAID - 80 TB storage, Supermicro X10SRL -F + Xeon E5-2680 v3 + 128 GB ECC Ram.

    The post was edited 2 times, last by Alexandro77 ().

  • I am a little bit hesitant to perform apt-dist upgrade if you think there is a risk to break something as this system is my main living-room one and the family is using it all the time, and it is working very stable and reliable.

    On Ubuntu apt dist-upgrade simply updates all packages within the release (instead of upgrading to a newer stable release like in Debian). The thing you don't want to do for a yaVDR installation is calling do-release-upgrade without checking if there is a working upgrade path and yavdr packages for the newer version.

    yaVDR-Dokumentation (Ceterum censeo enchiridia esse lectitanda.)

  • Great. Thank you once again.

    All packages upgraded successfully and the system is working as it should.

    YaVDR Ansible VM (VDR 2.4.0) as a VNSI Server and Streamdev Server. DD CINE S2 + 2 x DD Duoflex S2 (6 tuners)

    Modified Reelbox AVG II with working display: Gigabyte C1037UN-EU + EHD + 4GB ram + 32GB SSD. Streamdev client only.BM2LTS
    VDR1- ASUS AT3IONTI, 4gb RAM, 32GB SSD, MCE Remote, Custom case, YAVDR 0.6.2

    VDR2- ASUS AT5IONTI, 4gb RAM, 128GB SSD, MCE Remote, D-Vine 5 HTPC Case, YAVDR Ansible, Ubuntu 20.04.2

    4 x KODI (Libreelec) - Asus AT3IONTI, 2gb RAM, 32gb SSD, MCE Remote @ Nokia dBox1 case

    Raspberry PI3 b Plus - MLD (experimental)

    UNRAID - 80 TB storage, Supermicro X10SRL -F + Xeon E5-2680 v3 + 128 GB ECC Ram.