Dear visitor, welcome to VDR Portal. If this is your first visit here, please read the Help. It explains in detail how this page works. To use all features of this page, you should consider registering. Please use the registration form, to register here or read more information about the registration process. If you are already registered, please login here.
|
|
Source code |
1 2 3 |
sudo untie-packages sudo apt-get remove xbmc* sudo apt-get install python-software-properties |
|
|
Source code |
1 |
#deb http://ppa.launchpad.net/yavdr/stable-xbmc/ubuntu lucid main |
|
|
Source code |
1 2 3 |
sudo add-apt-repository ***musst Du Dir mal raussuchen*** sudo apt-get update sudo apt-get install xbmc |
|
|
Source code |
1 |
Ubuntu users: Beta1 available soon at the XBMC Unstable PPA. |
|
|
Source code |
1 2 3 4 |
xbmc 2:11.0~git20111222.22ad8e4-0ubuntu1~ppa1~oneiric Cory Fields (2011-12-28) xbmc 2:11.0~git20111222.22ad8e4-0ubuntu1~ppa1~natty Cory Fields (2011-12-28) xbmc 2:11.0~git20111222.22ad8e4-0ubuntu1~ppa1~maverick Cory Fields (2011-12-28) xbmc 2:11.0~git20111222.22ad8e4-0ubuntu1~ppa1~lucid Cory Fields (2011-12-28) |

|
|
Source code |
1 2 3 4 5 |
#Abhängigkeiten von yaVDR lösen: sudo untie-packages sudo apt-get remove xbmc* sudo apt-get install python-software-properties |
|
|
Source code |
1 2 3 |
# deb http://ppa.launchpad.net/yavdr/stable-xbmc/ubuntu natty main # deb-src http://ppa.launchpad.net/yavdr/stable-xbmc/ubuntu natty main |
|
|
Source code |
1 2 3 |
sudo add-apt-repository ppa:team-xbmc/unstable sudo apt-get update sudo apt-get install xbmc |
|
|
Source code |
1 |
sudo apt-get update && sudo apt-get dist-upgrade |
This post has been edited 3 times, last edit by "Dr. n00b" (Feb 13th 2012, 8:46pm)
Die Frage ist, wie kommt man wieder zurück, wenn es bei yaVDR irgendwann vielleicht eine bessere XBMC Version gibt? Wie sieht es mit VDR Updates nach einem untie-packages aus?
Kann man einfach auf die alten apt sources zurück und tut dann yavdr essential und/oder xbmc de- und dann wieder neuinstallieren?
Updates der einzelnen Pakete sollten danach ja ankommen, nur zusätzlich aufgenommene Pakete im yavdr-essential werden halt nicht automatisch installiert werden.
Quoted
Möchte man Plugins, die vom Paket yavdr-essential gefordert werden, unbedingt komplett deinstallieren, so muss man die Abhängigkeiten in yaVDR erst mit sudo untie-packages lösen (untie-packages ist ein spezielles Skript, welches yaVDR für solche Sonderfälle mitbringt). Damit werden die Abhängigkeiten auf das Paket yavdr-essential gelöst und nachfolgend das Paket deinstalliert. Dies ist eine Notlösung, weil man von nun an nicht mehr profitiert von Änderungen an yavdr-essential, die man sonst per Update bekommen würde.
Nach austauschen von XBMC mit einem XBMC aus anderer Quelle müsste man per aptitude install yavdr-essential das wieder herstellen können - Es ist einfach nur einfacher das XBMC weg und ein anderes zu installieren als es "in-place" zu ändern (möglicherweise machen Abhängigkeiten einen anderen Weg auch unmöglich, ich erinner mich nicht mehr)
|
|
Source code |
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 |
root@yaVDR:/home/user# aptitude install yavdr-essential
The following NEW packages will be installed:
yavdr-essential{b}
0 packages upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 1.762 B of archives. After unpacking 32,8 kB will be used.
The following packages have unmet dependencies:
yavdr-essential: Hängt ab von: xbmc-addon-xvdr which is a virtual package.
The following actions will resolve these dependencies:
Keep the following packages at their current version:
1) yavdr-essential [Not Installed]
Accept this solution? [Y/n/q/?] Y
No packages will be installed, upgraded, or removed.
0 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B of archives. After unpacking 0 B will be used.
|
|
|
Source code |
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 |
Feb 18 11:48:56 ubuntu vdr: [5567] executing command '/usr/share/vdr/menuorg-appswitcher standalone=yes app=xbmc &> /dev/null ' Feb 18 11:48:57 ubuntu vdr: [5711] dbus2vdr: new message, object /Remote, interface de.tvdr.vdr.remote, member Disable Feb 18 11:48:57 ubuntu vdr: [5711] dbus2vdr: 1 idle message handler, reusing 0x7195a50 Feb 18 11:48:57 ubuntu vdr: [6908] dbus2vdr message handler thread started (pid=5567, tid=6908) Feb 18 11:48:57 ubuntu vdr: [6908] dbus2vdr: moving message handler 0x7195a50 from active to finished Feb 18 11:48:57 ubuntu vdr: [6908] dbus2vdr message handler thread ended (pid=5567, tid=6908) Feb 18 11:48:57 ubuntu vdr: [5681] [xine..put] Closing connection 0 Feb 18 11:48:57 ubuntu vdr: [6893] Text2Skin: menu display update thread ended (pid=5567, tid=6893) Feb 18 11:48:57 ubuntu init: vdr-frontend main process (6770) terminated with status 1 Feb 18 11:48:58 ubuntu init: xbmc main process (6910) terminated with status 1 Feb 18 11:48:58 ubuntu vdr: [5711] dbus2vdr: new message, object /Remote, interface de.tvdr.vdr.remote, member Enable Feb 18 11:48:58 ubuntu vdr: [5711] dbus2vdr: 1 idle message handler, reusing 0x7195a50 Feb 18 11:48:58 ubuntu vdr: [6935] dbus2vdr message handler thread started (pid=5567, tid=6935) Feb 18 11:48:58 ubuntu vdr: [6935] dbus2vdr: moving message handler 0x7195a50 from active to finished Feb 18 11:48:58 ubuntu vdr: [6935] dbus2vdr message handler thread ended (pid=5567, tid=6935) Feb 18 11:48:59 ubuntu XBMC: XBMC exit with exit status 1, , ENV: TERM=linux#012EXIT_STATUS=1#012PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/sbin:/sbin:/bin#012PWD=/#012JOB=xbmc#012RESULT=failed#012SHLVL=1#012PROCESS=main#012UPSTART_INSTANCE=#012UPSTART_EVENTS=stopped#012UPSTART_JOB=xbmc-exit#012INSTANCE=#012DISPLAY=:1#012_=/usr/bin/env . Feb 18 11:48:59 ubuntu vdr: [5681] [xine..put] Client 0 connected: 127.0.0.1:34810 Feb 18 11:48:59 ubuntu vdr: [5681] loading /var/lib/vdr/plugins/xineliboutput/allowed_hosts.conf Feb 18 11:48:59 ubuntu vdr: [5681] [xine..put] cxSocket: setsockopt(SO_SNDBUF): got 262142 bytes Feb 18 11:48:59 ubuntu vdr: [5681] [xine..put] Client connection 0 closed Feb 18 11:48:59 ubuntu vdr: [5681] [xine..put] Closing connection 0 Feb 18 11:48:59 ubuntu /usr/bin/signal-event.real[6947]: processing signal reset-display-rate Feb 18 11:48:59 ubuntu /usr/bin/signal-event.real[6947]: processing action /usr/share/yavdr/events/reset-display-rate/10_reset-display-rate reset-display-rate Feb 18 11:48:59 ubuntu /usr/bin/signal-event.real[6947]: finished processing signal reset-display-rate Feb 18 11:49:00 ubuntu vdr: [5681] [xine..put] Client 0 connected: 127.0.0.1:34811 Feb 18 11:49:00 ubuntu vdr: [5681] loading /var/lib/vdr/plugins/xineliboutput/allowed_hosts.conf Feb 18 11:49:00 ubuntu vdr: [5681] [xine..put] cxSocket: setsockopt(SO_SNDBUF): got 262142 bytes Feb 18 11:49:00 ubuntu vdr: [5681] [xine..put] Client 1 connected: 127.0.0.1:34812 Feb 18 11:49:00 ubuntu vdr: [5681] loading /var/lib/vdr/plugins/xineliboutput/allowed_hosts.conf Feb 18 11:49:00 ubuntu vdr: [5681] [xine..put] cxSocket: setsockopt(SO_SNDBUF): got 262142 bytes Feb 18 11:49:00 ubuntu vdr: [5681] [xine..put] Data connection (TCP) requested Feb 18 11:49:00 ubuntu vdr: [5681] [xine..put] cBackgroundWriterI initialized (buffer 2048 kb) Feb 18 11:49:00 ubuntu vdr: [5681] [xine..put] cTcpWriter initialized (buffer 2048 kb) Feb 18 11:49:00 ubuntu vdr-sxfe[6938]: [6965] [console] read_key: read(stdin) failed: no stdin |