[mk01]

Dear users,

XBian Beta2 has been released but be aware this is only upgrade instruction and not an full installation process.


NOTE: this memo is not relevant for users already on Beta2 as part of the testing process


before you start double check /etc/apt/sources.list file (this is valid for all XBian versions - Alpha5, Beta1X). remove ALL XBian related lines and replace with this one

Code:

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

All packages are accessible to apt and xbian-config. upgrade process was tested for releases Alpha5, Beta1 (without hotfix and also for hotfix 1.1 and 1.2).
because of many changes in dependencies, apt will not include all packages needed for Beta2 for upgrade (those will be listed as Kept Back packages). for best experience is therefore needed to follow some steps manually. log into your XBian install via ssh and run these commands:

Terminal

sudo -i
apt-get clean; apt-get update; apt-get upgrade

this will install any upstream package updates.

after this step finishes proceed to next step without doing reboot between them (PLEASE CONTINUE READING also red colored text below BEFORE you run upgrade process).

Terminal

apt-get install xbian-update

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 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.

for future updates you can use XBIAN-CONFIG within XBMC and "Update all" (or XBIAN-CONFIG in ssh console and UPDATES). with Beta2, "Kept Back" packages will no longer be ignored while updating through this components.

to speed up the process, stop XBMC before. by QUIT from XBMC menu, or "stop xbmc" from console. all the commands 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.

---

IF YOU GET INTO ANY TROUBLES DURING THE ABOVE STEPS, READ BELOW.

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 error (and even more conflicts), but as this is not yet installed, we need to correct this manually (code to be executed is right below). Already existing installations with Beta2 or Beta1.2 hotfix should be fine.

Code:

sudo -i
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.

---

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

---

[CurlyMo]

What is miss in the instructions is that people should change:

Code:

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

into

Code:

deb http://xbian.brantje.com/ stable main

[Smultie]

It automatically happened on my install CurlyMo.

[mk01]

wheezy (and other debian future releases) is kept and working and will be supported also in future.

it is linked to stable.

[PicatriX]

First of all, thanks for your effort on Xbian...using it from the first release, never got a problem since now...
Trying to upgrade from 1.0 beta 1.2 on apt-get upgrade I´ve got:

Terminal

Preparing to replace xbian-package-zram-swap 1.0-3.7 (using .../xbian-package-zram-swap_1.0-4.6_armhf.deb) ...
Unpacking replacement xbian-package-zram-swap ...
Setting up xbian-package-zram-swap (1.0-4.6) ...
Processing triggers for xbian-package-zram-swap ...
stop: Unknown instance:

Also tried apt-get install xbian-update, but got:

Terminal

The following packages have unmet dependencies:
xbian-package-initramfs-tools : Breaks: xbian-package-kernel (< 1.3-5.5) but 1.2-1 is to be installed
xbian-update : Depends: ir-keytable but it is not installable
Depends: lsof but it is not installable
Depends: update-notifier-common but it is not installable
Depends: unattended-upgrades but it is not installable
PreDepends: openbsd-inetd but it is not installable
Breaks: xbian-package-samba (< 2.0.0-3) but 1.0 is to be installed
Breaks: xbian-package-config-shell (< 2.1.6-48b) but 2.1.3-3 is to be installed
Breaks: xbian-package-config-xbmc (< 1.1.4-1) but 1.1-2 is to be installed
Breaks: xbian-package-kernel (< 1.3-5.5) but 1.2-1 is to be installed
Breaks: xbian-package-usbmount (< 1.0.4-7) but 1.0-4.1 is to be installed
Breaks: xbian-package-xbmc (< 2.9-10.9)
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.

After this, no reboot is possible on my 512MB Raspberry...

Thanks in advance for any hint / help, I´ve got the working 1.0 beta 1.2 Clonezilla image to restore from ;-) so I can test possible solutions...
Best Regards
Andrea

[CurlyMo]

There is no such thing as Beta1.2 but only a Beta1.1 and Beta2. Might not solve your issue though

[PicatriX]

Sorry, I mean I was upgrading from Beta1 hotfix 1.2... http://forum.xbian.org/thread-1718.html

[wind-rider]

Can you explain why it isn't a good idea to use 'apt-get dist-upgrade' to work around the kept-back packages?

[f1vefour]

(16th Nov, 2013 11:43 PM)wind-rider Wrote:  Can you explain why it isn't a good idea to use 'apt-get dist-upgrade' to work around the kept-back packages?

You just manually install kept back packages.

Terminal

sudo apt-get install kept-back-package1 kept-back-package2 kept-back-package3

[mk01]

(16th Nov, 2013 10:24 PM)PicatriX Wrote:  

Terminal

Processing triggers for xbian-package-zram-swap ...
stop: Unknown instance:

Also tried apt-get install xbian-update, but got:

Terminal

The following packages have unmet dependencies:
xbian-package-initramfs-tools : Breaks: xbian-package-kernel (< 1.3-5.5) but 1.2-1 is to be installed
xbian-update : Depends: ir-keytable but it is not installable
Depends: lsof but it is not installable
Depends: update-notifier-common but it is not installable
Depends: unattended-upgrades but it is not installable
PreDepends: openbsd-inetd but it is not installable
Breaks: xbian-package-samba (< 2.0.0-3) but 1.0 is to be installed
Breaks: xbian-package-config-shell (< 2.1.6-48b) but 2.1.3-3 is to be installed
Breaks: xbian-package-config-xbmc (< 1.1.4-1) but 1.1-2 is to be installed
Breaks: xbian-package-kernel (< 1.3-5.5) but 1.2-1 is to be installed
Breaks: xbian-package-usbmount (< 1.0.4-7) but 1.0-4.1 is to be installed
Breaks: xbian-package-xbmc (< 2.9-10.9)
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.

@PicatriX
the first output is not a problem and can be ignored.

this second one is caused by held packages as said on last line. for this case applies the second red colored paragraph in section "TROUBLES" in opening post. solution for this should be to list all held packages as arguments to "apt-get install xbian-update …", in your case specifically

Code:

apt-get install xbian-update xbian-package-xbmc xbian-package-usbmount xbian-package-kernel xbian-package-config-xbmc xbian-package-config-shell xbian-package-samba

---

(16th Nov, 2013 11:43 PM)wind-rider Wrote:  Can you explain why it isn't a good idea to use 'apt-get dist-upgrade' to work around the kept-back packages?

@wind-rider

dist-upgrade is supposed to deal with this kind of dependencies. but there was bug in APT on Wheezy7.1 (reported on Debian's bugtrack as well) which was under some circumstances ignoring manually installed upstart and upon dist-upgrade process was forcing it's removal, practically causing uninstall of all xbian packages - because trying to install sysvinit back, breaking dependencies for xbian-update package.

I don't know if the fix was already included in dpkg / apt included in Wheezy 7.2 released on Oct-17 so we better stick to this method. You can run dist-upgrade and check what is offered by APT as solution and simply not continue if APT is warning you about that you probably don't know what you are doing, but we had some individual cases during Beta2 testing when users in this case confirmed with "Yes, I know what I'm doing!" and completely destroyed their installations.

[pit79]

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.
*** 15update-stamp (Y/I/N/O/D/Z) [default=N] ? y
Installing new version of config file /etc/apt/apt.conf.d/15update-stamp ...
Selecting previously unselected package ufsutils.
(Reading database ... 30778 files and directories currently installed.)
Unpacking ufsutils (from .../ufsutils_8.2-3_armhf.deb) ...
Processing triggers for man-db ...
Setting up ufsutils (8.2-3) ...
(Reading database ... 30798 files and directories currently installed.)
Preparing to replace xbian-package-usbmount 1.0-0.6 (using .../xbian-package-usb mount_1.0.5_all.deb) ...
Unpacking replacement xbian-package-usbmount ...
Setting up xbian-package-usbmount (1.0.5) ...
(Reading database ... 30802 files and directories currently installed.)
Preparing to replace xbian-package-zram-swap 1.0-3.1 (using .../xbian-package-zr am-swap_1.0-4.6_armhf.deb) ...
Unpacking replacement xbian-package-zram-swap ...
Setting up xbian-package-zram-swap (1.0-4.6) ...
Processing triggers for xbian-package-zram-swap ...
Selecting previously unselected package xbian-package-upstart-xbmc-bridge.
(Reading database ... 30802 files and directories currently installed.)
Unpacking xbian-package-upstart-xbmc-bridge (from .../xbian-package-upstart-xbmc -bridge_1.1.0-4_armhf.deb) ...
Setting up xbian-package-upstart-xbmc-bridge (1.1.0-4) ...
Selecting previously unselected package unattended-upgrades.
(Reading database ... 30806 files and directories currently installed.)
Unpacking unattended-upgrades (from .../unattended-upgrades_0.79.5+rpi1_all.deb) ...
Processing triggers for man-db ...
Setting up unattended-upgrades (0.79.5+rpi1) ...
insserv: warning: script 'lirc' missing LSB tags and overrides
Selecting previously unselected package kpartx.
(Reading database ... 30836 files and directories currently installed.)
Unpacking kpartx (from .../kpartx_0.4.9+git0.4dfdaf2b-7~deb7u1_armhf.deb) ...
Processing triggers for man-db ...
Setting up kpartx (0.4.9+git0.4dfdaf2b-7~deb7u1) ...
Selecting previously unselected package libapt-pkg-perl.
(Reading database ... 30846 files and directories currently installed.)
Unpacking libapt-pkg-perl (from .../libapt-pkg-perl_0.1.26+b1_armhf.deb) ...
Processing triggers for man-db ...
Setting up libapt-pkg-perl (0.1.26+b1) ...
Selecting previously unselected package apt-show-versions.
(Reading database ... 30876 files and directories currently installed.)
Unpacking apt-show-versions (from .../apt-show-versions_0.20_all.deb) ...
Processing triggers for man-db ...
Setting up apt-show-versions (0.20) ...
** initializing cache. This may take a while **
(Reading database ... 30892 files and directories currently installed.)
Preparing to replace xbian-package-config-xbmc 1.1-2 (using .../xbian-package-co nfig-xbmc_1.1.4-3_armhf.deb) ...
Unpacking replacement xbian-package-config-xbmc ...
Preparing to replace xbian-package-config-shell 2.1.3-3 (using .../xbian-package -config-shell_2.1.6-51a_armhf.deb) ...
Unpacking replacement xbian-package-config-shell ...
Setting up xbian-package-config-shell (2.1.6-51a) ...
Create subvolume '/tmp/btrfs-snap/data'
Create subvolume '/tmp/btrfs-snap/data/@'
dpkg: considering deconfiguration of xbian-update, which would be broken by inst allation of xbian-package-xbmc ...
dpkg: no, xbian-update is essential, will not deconfigure
it in order to enable installation of xbian-package-xbmc
dpkg: error processing /var/cache/apt/archives/xbian-package-xbmc_2.9-10.13_armh f.deb (--unpack):
installing xbian-package-xbmc would break existing software
dpkg: considering deconfiguration of xbian-package-xbmc, which would be broken b y installation of xbian-update ...
dpkg: yes, will deconfigure xbian-package-xbmc (broken by xbian-update)
(Reading database ... 30939 files and directories currently installed.)
Preparing to replace xbian-update 1.0-1.1 (using .../xbian-update_1.0.2-8e_armhf .deb) ...
De-configuring xbian-package-xbmc ...
Unpacking replacement xbian-update ...
Replacing files in old package upstart ...
Replacing files in old package base-files ...
Selecting previously unselected package xbian-package-xbmc-scripts.
Unpacking xbian-package-xbmc-scripts (from .../xbian-package-xbmc-scripts_1.0.1- 13c_armhf.deb) ...
Replacing files in old package xbian-package-xbmc ...
Processing triggers for xbian-package-initramfs-tools ...
Errors were encountered while processing:
/var/cache/apt/archives/xbian-package-xbmc_2.9-10.13_armhf.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

Any help ?

P.S after shutdown -r now rpi start into recovery mode it means sdcard is corrupted ?

[mk01]

for sure it is not corrupted.

just initramfs was installed without appropriate kernel package (installation interrupted).

you should be able to boot if you replace files in /boot with files inside this archive http://xbian.brantje.com/others/boot.xbian.zip .

[JD2k3]

(17th Nov, 2013 05:21 AM)pit79 Wrote:  Errors were encountered while processing:
/var/cache/apt/archives/xbian-package-xbmc_2.9-10.13_armhf.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

Any help ?

P.S after shutdown -r now rpi start into recovery mode it means sdcard is corrupted ?

I had the same error but fixed it by adding the following two packages to the apt-get install line:

libhal-storage1
libhal1

This continued the installation for me

[PicatriX]

@mk01:
thanks, reverted back to working beta1.2, followed your instructions for upgrading to beta 2, it seems that all went ok, new beta 2 ssh menu options visible, asking to reboot and then not at all ... tried to overwrite boot files with the ones you provided, but no way, no boot anymore...

I kept the "old" version of '/etc/apt/apt.conf.d/15update-stamp' asking "N" (default) to question...maybe is that the problem?

thanks for your patience...

[mk01]

@PicatriX,

no, the Y/N is not relevant there.

no boot anymore means nothing on the screen? even not blinking cursor on black background?