| 00:04.44 | *** join/#qi-hardware fengling (~fengling@58.135.95.137) |
| 00:43.45 | *** join/#qi-hardware sandeepkr_ (~sandeep@111.235.64.134) |
| 00:48.20 | *** join/#qi-hardware sandeepkr_ (~sandeep@111.235.64.134) |
| 00:51.08 | *** join/#qi-hardware sandeepkr__ (~sandeep@111.235.64.4) |
| 01:06.39 | *** join/#qi-hardware fengling (~fengling@58.135.95.137) |
| 01:21.34 | *** join/#qi-hardware sandeepkr__ (~sandeep@111.235.64.4) |
| 03:24.30 | whitequark | thats CSS flexbox I think |
| 03:24.35 | whitequark | there is no JS calculations of height |
| 03:42.26 | *** join/#qi-hardware sb0 (~lekernel@119.93.93.179) |
| 04:00.51 | *** join/#qi-hardware DocScrutinizer05 (~saturn@openmoko/engineers/joerg) |
| 07:30.10 | *** join/#qi-hardware pcercuei (~paul@137.71.226.54) |
| 07:54.51 | *** join/#qi-hardware sb0 (~lekernel@119.93.93.179) |
| 08:11.16 | *** join/#qi-hardware sb0 (~lekernel@119.93.93.179) |
| 08:22.46 | *** join/#qi-hardware wpwrak (~werner@181.171.122.65) |
| 08:46.25 | *** join/#qi-hardware wpwrak (~werner@181.171.122.65) |
| 12:07.05 | 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.04 | whitequark | yes |
| 12:09.08 | whitequark | flexbox is a farily new feature |
| 12:09.42 | DocScrutinizer05 | aah that explains it |
| 13:06.30 | *** join/#qi-hardware doomlord (~textual@host81-147-72-23.range81-147.btcentralplus.com) |
| 14:30.37 | *** join/#qi-hardware sb0 (~lekernel@119.93.93.179) |
| 15:24.29 | *** join/#qi-hardware kilae (~chatzilla@catv-162-034.tbwil.ch) |
| 17:18.16 | *** join/#qi-hardware wildlander (~wild@unaffiliated/wildlander) |
| 20:11.58 | *** join/#qi-hardware kristianpaul (~kristianp@ec2-52-71-133-242.compute-1.amazonaws.com) |
| 20:11.58 | *** join/#qi-hardware kristianpaul (~kristianp@unaffiliated/kristianpaul) |
| 20:56.53 | *** join/#qi-hardware sandeepkr_ (~sandeep@111.235.64.4) |
| 21:02.03 | *** join/#qi-hardware sandeepkr (~sandeep@111.235.64.4) |
| 21:10.07 | *** join/#qi-hardware wolfspraul (~wolfsprau@bobbin.q-ag.de) |
| 21:24.18 | 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.26 | mth | you have added a flag to delete destination files that no longer exist in the source dir? |
| 22:24.15 | 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.24 | DocScrutinizer05 | mth: the params are rsync -vaRzx --fake-super -- forgot what they stand for, I read the man page only so often |
| 23:12.50 | mth | none of those flags imply deletion of files that don't exist at the source, I think |
| 23:18.04 | DocScrutinizer05 | well, that's actually the idea to keep files |
| 23:19.36 | 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.28 | 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.31 | DocScrutinizer05 | maybe I could move on to delete on destination option now, since I got btrfs on destination fs |
| 23:24.36 | DocScrutinizer05 | actually that's implementing a scheme that'closer to the intended |
| 23:24.45 | DocScrutinizer05 | actually that's implementing a scheme that's way closer to the intended |
| 23:25.30 | DocScrutinizer05 | the "don't delete on destination" was only half assed effort to keep backups when the source gets corrupted |
| 23:26.07 | DocScrutinizer05 | it wouldn't help at all when files get truncated or crippled |
| 23:26.46 | DocScrutinizer05 | btrfs copy-on-write is exactly what I want |
| 23:28.10 | 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.58 | DocScrutinizer05 | hmm, maybe rsync has a way to rename destination objects from * to *-$postfix, instead of deleting resp overwriting them? |
| 23:36.04 | 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.23 | mth | I never used that, but the man page explains it |
| 23:37.12 | DocScrutinizer05 | hmmm >> --backup With this option, preexisting destination files are renamed as each file is transferred or deleted. << |
| 23:37.23 | DocScrutinizer05 | aah yep, you already said that |
| 23:46.37 | DocScrutinizer05 | I'll try a -b --del --suffix=BACKUP`date +%Y%m%d` for now |
| 23:50.29 | DocScrutinizer05 | hmm, still "cannpt delete non-empty dir..." |
| 23:50.59 | DocScrutinizer05 | I guess --delete-before is worth a try then |