(28th Jul, 2013 04:05 AM)f1vefour Wrote: [ -> ]If you do this be sure to comment out the repo you add from Koenkk's Beta1.1 upgrade before upgrading to Beta2.
xbian-update support upgrades from alpha5/beta1/beta1.1 to beta2 directly. this one by one approach is not needed.
since beta2, xbian-update is able (and will be able for future versions as well) to update the same version over and over again.
so for instance you have already few days old beta2 installation, you can reinstall xbian-update over again.
btw: as of today I finished with changes I wanted to have in beta2, only fixes will come if needed.
also I was testing updates from beta1, 1.1 as well. I had myself some issues to perform the updates and fixes followed.
I would appreciate some testing, specially upgrades from what-ever version - the more "unclean", the better.
in will also double check the public 1.1 image, with all the post I was going through after two weeks, I'm not quite sure it is as it was supposed to be.
I will be very happy if we deploy beta2 as soon as possible. more or less also from the aspect that many fixes to beta1.1 are not possible only via packages update, because there is too much dependency to xbian-update magic, so it's like fixing bug means installing beta2.
(27th Jul, 2013 05:30 PM)sir106 Wrote: [ -> ]but the instructions on the first page told to upgrade also xbian-update...
how is this done or isn't this needed?
dist-upgrade is very very bad to be honest, dist-upgrade tries to keep the distro at the factory (or actual) APT status, what means actually downgrade to debian wheezy with all the sysvinit environment - which is not compatible with recent versions of xbian-packages.
prior betas xbian-update was handled somehow specially, but we put much effort into making the xbian-update package workings as much as general packages and updates to them.
so don't take any special steps, just update what is available, including xbian-update .
(27th Jul, 2013 09:34 AM)sir106 Wrote: [ -> ]2nd REBOOT: stuck on init process
what did I do wrong?
I have to admit, the initramfs stage freeze, or later "loading…" freeze was more or less caused by me. I didn't realize that one small settings file I was using personally for months in not on stock xbian releases and made some scripts and initramfs image dependent on it.
so I didn't realize this mistake until I tried clean img update. then realized quickly and put this file into xbian-update for update.
(23rd Jul, 2013 10:44 PM)IriDium Wrote: [ -> ]What size are the snapshots? I've a feeling that 30 daily and 50 weekly may be too much for the standard 2GB install.
Can we get a list and version of what packages SHOULD be installed after the upgrade. Tnx
snapshot has no additional size, until you make change on the actual state of filesystem.
then, the size of snapshot is the size of the change you actually did. the difference between it's state and your actual.
5 weekly should be, if there is 50, it's typo. it can be much today, because with each update try we put more let's say 70mb to all existing snapshots.
usually, on well running system it stabilizes on some maximum, which is not so much over the size of actual filesystems. let's say +30%.
you can edit /etc/cron.daily/xbian…. /etc/cron.weekly/xbian…. scripts and adjust the numbers. during the next snapshoting, all other snapshots will be destroyed.
(22nd Jul, 2013 12:50 AM)IriDium Wrote: [ -> ]apt-get install xbian-update : returned errors. Tried --reinstall and then upgrade. Seemed to work. System rebooted. Xbian screen stuck on SD card resize.
this was the problem i described earlier. unfortunately the packages affected were on the repo for few days until I realized.