beta2

[mk01]

colleagues,

we need to test beta2. to jump on it, edit /etc/apt/sources.list and change

Code:

deb mirror://apt.xbian.org/mirror.txt wheezy main

to

Code:

deb http://xbian.brantje.com/devel wheezy main

then in terminal

Terminal

apt-get clean; apt-get update; apt-get upgrade

this will install any upstream package updates.

after this step finishes run next one without doing reboot between them.

Terminal

apt-get install xbian-update

for future updates you can use XBIAN-CONFIG within XBMC and "Update all".

to speed up the process, stop XBMC before. by QUIT from XBMC menu, or "stop xbmc" from console. all the command should be run with "sudo", or just log as xbian, then type "sudo -i". this will open console with root privileges where sudo before command is not needed anymore.

I can also prepare an image, if really needed (img is at http://xbian.brantje.com/devel/others/xbian.beta2.2013-01-11.7z) . this is still not official release, but another way to test beta2 beside updating via deb packages from A5/B1/B1.1)

impotant info as of Oct-17-2013:
Debian released Wheezy 7.2 update released the day before yesterday will add additional ~30 packages to the update process of Beta2 install with regularly updated XBian / system packages. Could be more for Beta1/Beta1.1 and specially Alpha5. Update process from Alpha5 (and possibly also Beta1 and Beta1.1) will install initscripts package and trigger dpkg configure error and stop on processing updates. Beta2 update package is correcting the specific (and even more conflicts), but as this is not yet installed. so we do it manually by. Already existing installations with Beta2 should be fine. These below a steps needed to solve issue:

Code:

rm -f /etc/init.d/mountall*
insserv -f
apt-get upgrade (again)

apt-get upgrade in step three will start where previous update process stopped - by configuring initscripts package again and this time will finish successfully.
For most simple and automated finish of the update process it is preferred to list all packages reported as "kept back" as parameters to "apt-get install xbian-update" command described on top of this post. It all depends on combination or age of actual installed packages as well on the order in which apt-get will process updates in each specific case. Than means simple "apt-get install xbian-update" can do just fine for one user, but can require explicitly named another package on command line for different user.

This means if apt-get will report:

Code:

xbian-package-lirc, xbian-package-cec and others to upgrade

and

Code:

xbian-package-xbmc, xbian-update, xbian-package-config-shell as "kept back"

proceed better with:

Code:

apt-get install xbian-package-xbmc xbian-update xbian-package-config-shell
instead of simple
apt-get install xbian-update

Beta2 has more changes in the area of update / upgrade implemented which should once and for all make use of command line tools via ssh not needed anymore. xbian-config-shell and -xbmc should then be able to handle updates with more ease.

---

on this question (and similar if encountered)

Code:

Configuration file `/etc/apt/apt.conf.d/15update-stamp'
==> File on system created by you or by a script.
==> File also in package provided by package maintainer.
   What would you like to do about it ?  Your options are:
    Y or I  : install the package maintainer's version
    N or O  : keep your currently-installed version
      D     : show the differences between the versions
      Z     : start a shell to examine the situation
The default action is to keep your current version.

just press Y (or you '-y' command line option to apt-get install)

errors about not being able to start LIRC or RNG-TOOL can be ignored. it is caused by dependency to kernel which is just going to be installed or services which xbian-update package will install later and will be started only after reboot.

mk

---