[mk01]

@Roxxor

.xbmc removal is too big stuff to start with. somehow Gotham introduced this bolackscreens via guisettings.xml incompatibility during it's version progressing.

it started back with 13.0 Betas, continued for sure with 13.0 FINAL. don't remember this anymore with 13.2 - although 13.2 is 13.2, right? so no progressing anymore.

My long story short: even when we got used to that with v13, IT IS a BUG. it should not be considered NORMAL (like to expect this as part of XBMC upgrade process - no). I don't remmber it from 11 or 11 -> Frodo. .... if this should ever repeat again, start with guisettings.xml rm.

Any other removal / reconfiguration I would personally consider as FAIL. Not that it simply couldn't happen, sure it can. But should be in detail reviewed, problem found and fixed.

---

(22nd Nov, 2014 11:59 AM)f1vefour Wrote:  I would think it would default to merging the new fstab instead of overwriting it.

@mk01 Any ideas?

@f1vefour

actually the idea of fstab update code was to touch/update xbian's lines only - meaning resulted fstab should be NO replace. it should preserve user lines.

BUT CurlyMoo was reporting SMB mounts being lost on xbian-update updates regularly. some bugs in that update code we found, probably not all. Maybe he stopped reporting that only because it was too much workload (not because it was fixed).

BUT2, I would need EXACT copy of fstab which will get messed. As on casual look the code should do what intended.

BUT3, ok, found it. can we do a test run ?

Code:

cd /tmp
touch /run/noreboot
wget http://ivka57.dyndns-ip.com/-/xbian-update1.0.2-122.deb
dpkg -i --force-all xbian-update1.0.2-122.deb