Latest versions (xbmc/vdr/vnsi) - Better to upgrade to Lucid (new yavdr)?

Hi.
I'm a bit lost and my german isn't the best...

Can someone confirm if this setup is OK to get the latest versions of the xbmc/vdr/vnsi builds?

Based on yavdr 0.1.1 I've added these repositories:

deb http://ppa.launchpad.net/henningpingel/xbmc/ubuntu karmic main
deb http://ppa.launchpad.net/the-vdr-team/unstable-plugins/ubuntu karmic main


(with:
deb http://ppa.launchpad.net/the-vdr-team/vdr-ubuntu-karmic/ubuntu karmic main
deb http://ppa.launchpad.net/the-vdr-team/ppa/ubuntu karmic main
deb http://ppa.launchpad.net/the-vdr-team/yavdr/ubuntu karmic main )

Until now, all upgrades were OK (apt-get update,upgrade and dist-upgrade). But lately I'm having problems like:

>sudo apt-get upgrade


Reading package lists...
Building dependency tree...
Reading state information...
The following packages have been kept back:
  xbmc-bin xbmc-data xbmc-skin-confluence xbmc-skin-pm3-hd xbmc-web
0 upgraded, 0 newly installed, 0 to remove and 5 not upgraded.

Reasons are:

>sudo apt-get install xbmc


Reading package lists...
Building dependency tree...
Reading state information...
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:
  xbmc: Depends: xbmc-data (= pvr-testing-36~yavdr-karmic30871+6) but pvr-testing-35~yavdr-karmic30240+2 is to be installed
        Depends: xbmc-web (= pvr-testing-36~yavdr-karmic30871+6) but pvr-testing-35~yavdr-karmic30240+2 is to be installed

and

>sudo apt-get install xbmc-bin


Reading package lists...
Building dependency tree...
Reading state information...
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:
  xbmc-bin: Depends: libvdpau1 but it is not installable

I'm afraid I'm caught into some "dependency-hell".

My main goal is latest VNSI & XBMC... what can I do?

Much appriciated hepi, thank you. Will check this thread regularly.

Zitat

Originally posted by Mac Gyver
have du added the repositorys before running dist-upgrade? as far as i know added repos get disabled by dist upgrade.

greetings
macgyver

The repos are still there (etc/apt/sources.list.d folder) at the moment:

deb http://ppa.launchpad.net/henningpingel/xbmc/ubuntu karmic main
deb http://ppa.launchpad.net/the-vdr-team/unstable-plugins/ubuntu karmic main
deb http://ppa.launchpad.net/ubuntu-wine/ppa/ubuntu karmic main
deb http://ppa.launchpad.net/the-vdr-team/vdr-ubuntu-karmic/ubuntu karmic main
deb http://ppa.launchpad.net/the-vdr-team/ppa/ubuntu karmic main
deb http://ppa.launchpad.net/the-vdr-team/yavdr/ubuntu karmic main

Now I removed hepi's repo (no held back upgrades) but ... I don't wanna do that!

Would it be better if I make a clean install of the new yavdr version (lucid)? In general, are you all developing on lucid? Difference in updates/packages?

Thanks for taking your time with this...

Anyway, I tried adding svn ppa, but no updates are installed ("Reasons" in the first post). These are kept back (on apt-get upgrade):

xbmc
xbmc-bin
xbmc-data
xbmc-skin-confluence
xbmc-skin-pm3-hd
xbmc-web
yavdr-essential

..."dist-upgrade" installed yavdr-essential.

and running "apt-get install xbmc-bin" produces the same error about libvdpau1.

I'm not exactly sure what you mean (I'm not an expert at linux), but I tried to install new nvidia drivers, but had some problems with updating. Similar errors about libvdpau1 ... it seems that there is clash between the driver and vdpau.
I already tried anything I could find on this topic, but no success yet. Do you have any ideas that I can try?

"Solved" by clean install of yaVDR v0.2 ... updates work.