[mk01]

(22nd Nov, 2013 01:22 AM)zilexa Wrote:  The modified Amber skin has a different version number compared to the original one and it also seems slower so I am using the original Amber skin. I don't think it is a good idea to release a modded Amber skin because you have to update it everytime the Amber skin is updated.
Is it possible to run XBian-Config as an addon in just any skin? Because now I do not have XBian Config in XBMC

@zilexa

@belese is looking for a solution how to do that.

On XBian add-on repo, both versions are available. modded and upstream. upstream (original) is also faster now as the last modded version from @Fred is version 0.4.x (I suppose) and since then Amber was much more optimized (current version is 1.2.5 or something).

---

(22nd Nov, 2013 03:03 AM)CurlyMo Wrote:  What dazzles me is that since we have the devel, staging, and stable repo's, the stable repo still contains packages that are buggy. Shouldn't those be in devel or staging?

@CurlyMo

can you please list the packages? what was confirmed in b2 test thread was considered stable and moved to new repository - if you provide list of bugged packages I can compare if all was moved with the correct version.

of course let's exclude packages with NEW bugs found after release.

changes to packages AFTER testing period were limited to control file(s) to help with the dependencies problems during upgrades from Alpha5 release and xbian-update change (noatime rootfs remount fstab record), which unfortunately caused the "smb mounts removal" bug from the past to reappear.

other changes / fixes / new functions implemented in packages after B2 test are all placed in devel repo.

if there are other bugs please report (best) at github.

---

(23rd Nov, 2013 04:14 AM)calisro Wrote:  

(22nd Nov, 2013 03:42 AM)IriDium Wrote:  Can you post the output from dmesg.

I couldn't get the thing to boot to get a dmesg.

@calisro

can you provide archived (zip, rar, tar.gz) /boot partition (accessed from win / linux / other pc) after you fail to boot? would be interesting to look at.

isn't it possible the apt (dpkg) process during your apt-get upgrade run fails? (as few reports with dpkg being killed during OOM situation on 256MB models?)