0.3: Testing VDR 1.7.20 - problems with dist-upgrade

  • Some of the channels in my area doesn't have sound because of AAC-LATM so I really want to test the new VDR version with yaVDR 0.3.


    I already wrote some feedback here and here, but I will also put my experiences to this forum:


    I have an up-to date yavdr 0.3 with almost everything working (except aac on some channels) I added the main and the vdr-testing ppas to the repos.


    Then I tried to do a sudo apt-get update && apt-get dist-upgrade round, but I got the following message:


    Code
    The following packages will be REMOVED:
      libtntnet8 yavdr-essential yavdr-startup yavdr-utils
    The following NEW packages will be installed:
      libcxxtools7 libproc-processtable-perl libtntnet9


    and some of the packages to be upgraded.


    I run it, but first I got this error:

    Code
    dpkg-divert: mismatch on package
      when removing `diversion of /etc/firefox/profile/prefs.js to /etc/firefox/profile/prefs.js.dontremove by yavdr-startup


    I found a solution here


    Code
    sudo dpkg-divert --remove /etc/firefox/profile/prefs.js


    after that I got the following error:

    Code
    dpkg: error processing /var/cache/apt/archives/libcxxtools7_2.0+r1231-3yavdr3~lucid_i386.deb (--unpack):
     trying to overwrite '/usr/lib/libcxxtools.so.7.0.0', which is also in package libcxxtools6 0:2.0+r1201-1yavdr1


    Here I am now. Pls help.

    Hardware: Antec Fusion 430, Asus M2A-VM HDMI, AMD Athlon64 X2 4050E, GeForce GT 240, 2GB RAM, 4GB SSD, 320GB HDD, ASUS MYCINEMA-P7131, Technisat SkyStar HD 2

  • benoe


    Did you follow at all, what seahawk1986 did recommend in yaVDR blog from Bugtracker:

    Code
    sudo apt-get update && sudo apt-get dist-upgrade
    sudo dpkg --remove libcxxtools6
    sudo dpkg --remove libcxxtools6 libtntnet8
    sudo apt-get update && sudo apt-get dist-upgrade
    sudo apt-get install libtntnet9 && sudo apt-get dist-upgrade
    sudo apt-get install -f
    sudo apt-get update && sudo apt-get dist-upgrade


    Regards
    fnu

    HowTo: APT pinning

  • yes, but yavdr-essential is not there after, and when I want to install:


    Code
    The following packages have unmet dependencies:  yavdr-essential: Depends: yavdr-startup but it is not going to be installed                   Depends: yavdr-utils but it is not going to be installed



    Yavdr-startup is depends on yavdr-utils only.


    When trying to install yavdr-utils:

    Code
    The following packages have unmet dependencies:  yavdr-utils: Depends: libtntnet8 but it is not going to be installed



    when trying to install libtntnet8:

    Code
    The following extra packages will be installed:  libcxxtools6The following packages will be REMOVED:  libtntnet9 tntnet tntnet-runtimeThe following NEW packages will be installed:  libcxxtools6 libtntnet8



    error:

    Code
    dpkg: error processing /var/cache/apt/archives/libcxxtools6_2.0+r1201-1yavdr1_i386.deb (--unpack): trying to overwrite '/usr/lib/libcxxtools-http.so.7.0.0', which is also in package libcxxtools7 0:2.0+r1231-3yavdr3~lucid



    this last one looks very familiar to me :)

    Hardware: Antec Fusion 430, Asus M2A-VM HDMI, AMD Athlon64 X2 4050E, GeForce GT 240, 2GB RAM, 4GB SSD, 320GB HDD, ASUS MYCINEMA-P7131, Technisat SkyStar HD 2

  • benoe


    Which PPA repositories did you add and how have you done it? And which ones are active now?


    Could you please show:

    Code
    #\> apt-cache policy libtntnet8 libtntnet9 vdr yavdr-essential


    Regards
    fnu

    HowTo: APT pinning

    Einmal editiert, zuletzt von fnu ()

  • I tried a switch from yaVDR 0.3a with current updates to the unstable-PPA within a VM.
    The solution in the Bugreport is based on a normal Lucid system without the packages from (un)stable-yavdr PPAs.

    apt-cache policy libtntnet8 libtntnet9 vdr yavdr-essential libcxxtools6 libcxxtools7



    There is a colliding dependency by yavdr-utls, which wants to install libcxxtools6 whereas other packages as vdr-plugin-live do require libcxxtools7.

    yaVDR-Dokumentation (Ceterum censeo enchiridia esse lectitanda.)

  • Code
    cat /etc/apt/sources.list.d/yavdr.listdeb http://ppa.launchpad.net/yavdr/stable-vdr/ubuntu lucid maindeb http://ppa.launchpad.net/yavdr/stable-xbmc/ubuntu lucid maindeb http://ppa.launchpad.net/yavdr/stable-yavdr/ubuntu lucid maindeb http://ppa.launchpad.net/yavdr/main/ubuntu lucid maindeb http://ppa.launchpad.net/yavdr/testing-vdr/ubuntu lucid main




    Code
    apt-cache policy libtntnet8 libtntnet9 vdr yavdr-essentiallibtntnet8:  Installed: 2.0-1yavdr2  Candidate: 2.0-1yavdr2  Version table: *** 2.0-1yavdr2 0        500 http://ppa.launchpad.net/yavdr/stable-vdr/ubuntu/ lucid/main Packages        100 /var/lib/dpkg/status     1.6.3-4 0        500 http://hu.archive.ubuntu.com/ubuntu/ lucid/universe Packageslibtntnet9:  Installed: (none)  Candidate: 2.0+rev.1295-0yavdr3~lucid  Version table:     2.0+rev.1295-0yavdr3~lucid 0        500 http://ppa.launchpad.net/yavdr/main/ubuntu/ lucid/main Packages        100 /var/lib/dpkg/statusvdr:  Installed: 1.7.20-8yavdr1~lucid  Candidate: 1.7.20-8yavdr1~lucid  Version table: *** 1.7.20-8yavdr1~lucid 0        500 http://ppa.launchpad.net/yavdr/testing-vdr/ubuntu/ lucid/main Packages        100 /var/lib/dpkg/status     1.7.16-24yavdr1 0        500 http://ppa.launchpad.net/yavdr/stable-vdr/ubuntu/ lucid/main Packages     1.6.0-9ubuntu2 0        500 http://hu.archive.ubuntu.com/ubuntu/ lucid/universe Packagesyavdr-essential:  Installed: (none)  Candidate: 0.3.0.2089-1yavdr1  Version table:     0.3.0.2089-1yavdr1 0        500 http://ppa.launchpad.net/yavdr/stable-yavdr/ubuntu/ lucid/main Packages

    Hardware: Antec Fusion 430, Asus M2A-VM HDMI, AMD Athlon64 X2 4050E, GeForce GT 240, 2GB RAM, 4GB SSD, 320GB HDD, ASUS MYCINEMA-P7131, Technisat SkyStar HD 2

  • At the moment it is not possible to use yaVDR 0.3 together with the unstable- or testing-PPAs.
    A plain Lucid installation + main + testing-vdr (or even unstable-vdr) should work (at least it does on my primary VDR). If you want to test a more recent version of VDR/yaVDR give yaVDR 0.4pre1 (caution: alpha release) a try.

    yaVDR-Dokumentation (Ceterum censeo enchiridia esse lectitanda.)

  • At the moment it is not possible to use yaVDR 0.3 together with the unstable- or testing-PPAs.
    A plain Lucid installation + main + testing-vdr (or even unstable-vdr) should work (at least it does on my primary VDR). If you want to test a more recent version of VDR/yaVDR give yaVDR 0.4pre1 (caution: alpha release) a try.


    Do you have any information when it will be fixed?
    I'm very satisfied with the current setup except the AAC sound issue.
    Btw, I'm also trying 0.4pre1, but I have different problems what I will write down in another thread.

    Hardware: Antec Fusion 430, Asus M2A-VM HDMI, AMD Athlon64 X2 4050E, GeForce GT 240, 2GB RAM, 4GB SSD, 320GB HDD, ASUS MYCINEMA-P7131, Technisat SkyStar HD 2

  • Do you have any information when it will be fixed?


    Only "It's done when it's done"... but fnu told me he would have a look at it.

    yaVDR-Dokumentation (Ceterum censeo enchiridia esse lectitanda.)

  • Do you have any information when it will be fixed?


    Well, it hasn't ever been planned to be an upgrade for yaVDR 0.3 and be aware, it hasn't indeed been advertised as an upgrade for yaVDR 0.3 in our blog.


    It has rather been an update for all the experienced people out there using the Lucid repositories building VDR machines on their own manner. Doesn't mean you're not experienced, but right know you have to decide between using yaVDR 0.3 or "ppa:yavdr/testing-vdr" && "ppa:yavdr/main" on your own responsibility.


    Do not ever use "ppa:yavdr/testing-vdr" with yaVDR 0.3, we won't ever take care if these packages do run with yaVDR 0.3 nor if all dependencies are working, they do just run with Ubuntu 10.04 (lucid). Bottomline we even don't guarantee this for "ppa:yavdr/testing-vdr", whereas please remind, it's name is testing, not stable.


    But we feel that some of you might want to use the newer versions out there with yaVDR 0.3, so we will have a look to resolve at least the dependencies, but there could still some problems kept in the packages of this testing repository.


    So, please be patient, stay tuned and don't forget yaVDR's future is 0.4!


    Regards
    fnu

    HowTo: APT pinning


  • Well, it hasn't ever been planned to be an upgrade for yaVDR 0.3 and be aware, it hasn't indeed been advertised as an upgrade for yaVDR 0.3 in our blog.


    I only started to test it with 0.3, because you announced it on the web page: "Packages for Ubuntu Lucid (yaVDR 0.3) and Ubuntu Natty (yaVDR 0.4) are now available, but most of them are untested" and was glad that I could solve the aac issue with the current setup, but also want to help you testing it. Otherwise I wouldn't even try, or at least wouldn't report there and here.


    It has rather been an update for all the experienced people out there using the Lucid repositories building VDR machines on their own manner. Doesn't mean you're not experienced, but right know you have to decide between using yaVDR 0.3 or "ppa:yavdr/testing-vdr" && "ppa:yavdr/main" on your own responsibility.


    I tought the opposite, that there is yavdr, the main project, and there is an option, with less attention, for users who want install yavdr on their average desktop machines. Maybe I wasn't just prudent enough in this matter.



    Do not ever use "ppa:yavdr/testing-vdr" with yaVDR 0.3, we won't ever take care if these packages do run with yaVDR 0.3 nor if all dependencies are working, they do just run with Ubuntu 10.04 (lucid).


    Good to know that, as I wrote, I tought the opposite.



    Bottomline we even don't guarantee this for "ppa:yavdr/testing-vdr", whereas please remind, it's name is testing, not stable.


    This, I'm aware of. (testing is testing, not stable :) )



    But we feel that some of you might want to use the newer versions out there with yaVDR 0.3, so we will have a look to resolve at least the dependencies, but there could still some problems kept in the packages of this testing repository.


    Thanks.



    So, please be patient, stay tuned and don't forget yaVDR's future is 0.4!


    Regards
    fnu


    I know the future is 0.4, but right now it is not working for me as it should.
    But I'm also not in a hurry, I could totally accept the "when it is done" method, righ now I satisfied with my current setup, as I wrote already.

    Hardware: Antec Fusion 430, Asus M2A-VM HDMI, AMD Athlon64 X2 4050E, GeForce GT 240, 2GB RAM, 4GB SSD, 320GB HDD, ASUS MYCINEMA-P7131, Technisat SkyStar HD 2

  • Hi benoe,
    could you give the new Packages in testing-vdr/yaVDR for yaVDR 0.3 a try?


    /etc/apt/sources.list.d/yavdr.list

    Code
    deb http://ppa.launchpad.net/yavdr/main/ubuntu lucid main
    deb http://ppa.launchpad.net/yavdr/testing-vdr/ubuntu lucid main
    deb http://ppa.launchpad.net/yavdr/testing-xbmc/ubuntu lucid main
    deb http://ppa.launchpad.net/yavdr/testing-yavdr/ubuntu lucid main


    Code
    sudo apt-get update
    sudo dpkg --remove libcxxtools6 libtntnet8 tntnet tntnet-runtime vdr-plugin-live yavdr-utils yavdr-essential yavdr-startup
    sudo apt-get dist-upgrade
    sudo apt-get install vdr-plugin-live yavdr-essential
    sudo apt-get autoremove
    sudo apt-get install vdr-addon-noad


    On my VM I had to change the frontend to xine and switch back to vdr-sxfe in order to see vdr-sxfe again - could you check if testing-packages do work for you?

    yaVDR-Dokumentation (Ceterum censeo enchiridia esse lectitanda.)

  • Thanks, the upgrade went well!


    only one error appeared after dpkg --remove:


    Code
    dpkg-divert: mismatch on package
      when removing `diversion of /etc/firefox/profile/prefs.js to /etc/firefox/profile/prefs.js.dontremove by yavdr-startup'
      found `diversion of /etc/firefox/profile/prefs.js to /etc/firefox/profile/prefs.js.dontremove by yavdr-utils'
    dpkg: error processing yavdr-utils (--remove):
     subprocess installed post-removal script returned error exit status 2


    but I solved with this:

    Code
    sudo dpkg-divert --remove /etc/firefox/profile/prefs.js


    and after that two of the config files got replaced(or asked if I want to replace): order.conf and tntnet.conf



    I only tried the result with xbmc frontend, and the channels that didn't have sound before now have.


    So thanks for all your effort!

    Hardware: Antec Fusion 430, Asus M2A-VM HDMI, AMD Athlon64 X2 4050E, GeForce GT 240, 2GB RAM, 4GB SSD, 320GB HDD, ASUS MYCINEMA-P7131, Technisat SkyStar HD 2

  • only one error appeared after dpkg --remove:


    According to fnu this error can be ignored so you don't have to do "dpkg-divert --remove /etc/firefox/profile/prefs.js".

    yaVDR-Dokumentation (Ceterum censeo enchiridia esse lectitanda.)

  • When you described your problem for the first time it truly did. When I tried it today within a VM it was not necessary to do so anymore.

    yaVDR-Dokumentation (Ceterum censeo enchiridia esse lectitanda.)

  • I only tried the result with xbmc frontend, and the channels that didn't have sound before now have.


    Just for our curiousity and to confirm the issue, your VDR is now running with VDR 1.7.20 from our testing repositories? Means, the case could be seen as solved?


    Regards
    fnu


    Btw.: The elaborated above mentioned procedure does imply, that you have installed yaVDR 0.3 with all updates from the stable repositories, I should had mentioned this to seahawk1986, sorry ...

    HowTo: APT pinning

    Einmal editiert, zuletzt von fnu ()


  • Just for our curiousity and to confirm the issue, your VDR is now running with VDR 1.7.20 from our testing repositories? Means, the case could be seen as solved?


    Regards
    fnu


    Btw.: The elaborated above mentioned procedure does imply, that you have installed yaVDR 0.3 with all updates from the stable repositories, I should had mentioned this to seahawk1986, sorry ...


    Yes, I had an up-to-date yavdr 0.3 system and also a disk-level backup of it when I started the upgrade process seahawk1986 mentioned.

    Hardware: Antec Fusion 430, Asus M2A-VM HDMI, AMD Athlon64 X2 4050E, GeForce GT 240, 2GB RAM, 4GB SSD, 320GB HDD, ASUS MYCINEMA-P7131, Technisat SkyStar HD 2

    Einmal editiert, zuletzt von benoe ()

  • Yes, I had an up-to-date yavdr 0.3 system and also a disk-level backup of it when I started the upgrade process seahawk1986 mentioned.

    Could you please tell me what you mean by "disk-level backup" ?


    Does the testing repo contain the packages of yavdr 0.4 with the new features like the channelpedia?


    Are you running on a 32 bit architecture and is the resulting system that you could stable?


    Thanks in advance for the information.

  • Does the testing repo contain the packages of yavdr 0.4 with the new features like the channelpedia?


    At the moment testing-yavdr contains only a part of yaVDR 0.4pre1 new Webfrontend. As far as I can see within my VM installation there is no Channelpedia. It's far from stable as the Packages in unstable/testing-vdr are only intended to be used by experienced users of a "normal" Ubuntu with vdr-packages from the yaVDR-PPA.
    There seems to be a problem when using streamdev-client, too (at least in my VM it doesn't recieve any channels).

    yaVDR-Dokumentation (Ceterum censeo enchiridia esse lectitanda.)

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!