03:24 <whitequark> thats CSS flexbox I think

03:24 <whitequark> there is no JS calculations of height

12:07 <DocScrutinizer05> whitequark: aah, ok. Well I have no idea what's wrong, but I see it fails. Prolly a real bug in Konqueror then?

12:09 <whitequark> yes

12:09 <whitequark> flexbox is a farily new feature

12:09 <DocScrutinizer05> aah that explains it

21:24 <DocScrutinizer05> any help with rsync anybody? rsync throws error >> cannot delete non-empty directory: usr/lib/osso-chess-ui \n could not make way for new symlink: usr/lib/osso-chess-ui<< after on source a dir got moved and replaced by a symlink

22:23 <mth> you have added a flag to delete destination files that no longer exist in the source dir?

22:24 <mth> help text lists "--force force deletion of directories even if not empty", but I guess that would be suppressing a symptom rather than fixing an underlying problem

23:08 <DocScrutinizer05> mth: the params are rsync -vaRzx --fake-super -- forgot what they stand for, I read the man page only so often

23:12 <mth> none of those flags imply deletion of files that don't exist at the source, I think

23:18 <DocScrutinizer05> well, that's actually the idea to keep files

23:19 <DocScrutinizer05> however when a dir gets replaced by moving it elsewhere and creating a symlink to the new path in old position, I think rsync is handling that in a pretty nonsensical way and I don't know how to handle it any better

23:22 <DocScrutinizer05> probably when a root node of a directory tree gets removed and rsync isn't supposed to delete (recursively), all the child elements should get moved to ./lost+found/* or something like that, on destination

23:23 <DocScrutinizer05> maybe I could move on to delete on destination option now, since I got btrfs on destination fs

23:24 <DocScrutinizer05> actually that's implementing a scheme that'closer to the intended

23:24 <DocScrutinizer05> actually that's implementing a scheme that's way closer to the intended

23:25 <DocScrutinizer05> the "don't delete on destination" was only half assed effort to keep backups when the source gets corrupted

23:26 <DocScrutinizer05> it wouldn't help at all when files get truncated or crippled

23:26 <DocScrutinizer05> btrfs copy-on-write is exactly what I want

23:28 <DocScrutinizer05> thanks for pointing me into right direction. I'll add the delete option to rsync and wrap the whole script into snapper calls

23:32 <DocScrutinizer05> hmm, maybe rsync has a way to rename destination objects from * to *-$postfix, instead of deleting resp overwriting them?

23:36 <mth> yes, there is --backup, which can be used to create backup files with a suffix or move backup files to a separte dir

23:36 <mth> I never used that, but the man page explains it

23:37 <DocScrutinizer05> hmmm >> --backup With this option, preexisting destination files are renamed as each file is transferred or deleted. <<

23:37 <DocScrutinizer05> aah yep, you already said that

23:46 <DocScrutinizer05> I'll try a -b --del --suffix=BACKUP`date +%Y%m%d` for now

23:50 <DocScrutinizer05> hmm, still "cannpt delete non-empty dir..."

23:50 <DocScrutinizer05> I guess --delete-before is worth a try then