| 00:58.29 | *** join/#maemo-ssu LaoLang_cool (~LaoLang_c@221.226.175.139) |
| 02:52.32 | *** join/#maemo-ssu amiconn_ (quassel@rockbox/developer/amiconn) |
| 05:14.34 | *** join/#maemo-ssu LaoLang_coo_ (~LaoLang_c@221.226.175.139) |
| 05:34.22 | *** join/#maemo-ssu M13 (~Miranda@83.149.37.244) |
| 06:13.46 | *** join/#maemo-ssu angelangle (~root@180.110.241.129) |
| 07:16.18 | Estel_ | kerio, defrag on device with hardware wear leveling? Are You kiding me?;) |
| 07:16.29 | Estel_ | kidding* |
| 07:16.39 | Estel_ | lol @ kiding*. something related to kid, probably |
| 07:17.16 | kerio | Estel_: huh... defrag on ext3, yes |
| 07:17.21 | Estel_ | freemangordon, how is life in CSSUland? |
| 07:17.22 | kerio | aka defrag on a perfect block device |
| 07:17.40 | Estel_ | kerio, Your logical filesystem get fcked up by physical filesystem via hardware wear levelling ;) |
| 07:17.41 | kerio | notice how i said /home and not / |
| 07:17.51 | Estel_ | i.e got spread on eMMC anyway |
| 07:18.22 | kerio | but... it's perfect! :C |
| 07:18.36 | Estel_ | sure, 256 NAND doesn't have hardware wear levelling, so You rely on ubifs for that. but opt and home is on eMMC and hardware wear leveller is implemented transparently |
| 07:19.01 | Estel_ | i.e. no way to turn it off, in the world |
| 07:19.19 | Estel_ | (turning off would be beneficial for TrueCrypt, but You can't do it on eMMC nor SD cards) |
| 07:19.29 | Estel_ | (which is lame, btw) |
| 07:19.40 | kerio | beneficial performance-wise or security-wise? |
| 07:19.48 | Estel_ | security, only |
| 07:20.05 | kerio | well, if there's no way to access the raw flash... |
| 07:20.09 | Estel_ | it's about fact, that if You overwrite You encrypted partition - for any reason - old chunks are still spread on physical device |
| 07:20.48 | Estel_ | if You use same password than before (when re-creating encrypted partition, for example0, You actually aid cryptography |
| 07:20.50 | kerio | hm, i wonder if the emmc supports "discard" |
| 07:20.52 | Estel_ | attack |
| 07:21.11 | Estel_ | of course it's not trivial to retrieve such chunks, and would require physical access to flash |
| 07:21.17 | Estel_ | no, it doesn't |
| 07:21.35 | Estel_ | well, I've mentioned other cases where hardware wear levelling is PITA in TrueCrypt annoucement thread |
| 07:21.38 | Estel_ | in FAQ |
| 07:22.13 | Estel_ | generally, it's nothing critical, just require to avoid doing some things, or, if feel paranoic, overwriting rest of eMMC with 0 or 1, when You're changing truecrypt'ed partitions/containers layout :P |
| 07:22.47 | Estel_ | generally, all of wear-levelling vs TrueCrypt concerns are quite on "paranoia" level, i.e. no need to worry about it if You're encrypting personal photos, etc |
| 07:23.01 | Estel_ | but definitelly worth following if You're oppositionist in Iran, for example |
| 07:23.46 | kerio | [relevant xkcd here] |
| 07:23.54 | Estel_ | especially considering, how Irani fckd' up "web of trust" & gmail, via ssl certificate crisis with digi-something |
| 07:24.27 | Estel_ | and by "fckd up" I don't mean "breakage", rather "fckd in ass" |
| 07:25.09 | Estel_ | it's funny, bTw, that actually, firefox helped to reveal borked certificate authority |
| 07:25.37 | Estel_ | at least this behemot memory usage was used, once, to do good :P (sadly no, as it wasn't related to resources usage, at all) |
| 07:26.21 | *** join/#maemo-ssu freemangordon (~freemango@130-204-50-168.2074221835.ddns.cablebg.net) |
| 07:26.35 | Estel_ | what concerns me, though, is that for 3 days I'm asking merlin1991 about status of busybox-power for CSSU - just about decisions, not implementation status - and reply is just quiet and lonely space |
| 07:27.16 | Estel_ | seems that no other ways, than starting "show" in mailing list/TMO :( |
| 07:27.24 | freemangordon | Estel_: can you imagine merlin1991 is on holiday with very bad internet access? |
| 07:27.30 | Estel_ | sure |
| 07:27.42 | Estel_ | that woudl explain things a lot :) |
| 07:27.47 | freemangordon | well, wait him caome back, ok |
| 07:27.49 | freemangordon | ? |
| 07:27.59 | Estel_ | of course. Wasn't he just back, 2 days ago? |
| 07:28.03 | Estel_ | 3 days ago* |
| 07:28.11 | freemangordon | no, he wasn't, read the logs |
| 07:28.17 | Estel_ | my bad, then :) |
| 07:28.45 | Estel_ | and no worry, I'm just "little" dissapointed, that one CSSU maintainer said one thing, and another one - quite inactive normally, if You ask me - denies it in TMO thread |
| 07:29.00 | Estel_ | resulting in 3 pages of discussion in otherwise productive busybox-power thread |
| 07:29.07 | freemangordon | afaik merlin1991 is in greece, spain, or some other sunny place |
| 07:29.07 | Estel_ | no hostile intentions here, just curious :) |
| 07:29.14 | Estel_ | is jealous |
| 07:29.29 | freemangordon | don't be, it is too hot there :P |
| 07:29.57 | Estel_ | BTW, once You've said that DocScrutinizer05 isn't CSSU maintainer. Few days ago he linked me to garage page, where he is listed as maintainer, said that it's the case for more than a year, or longer |
| 07:30.10 | Estel_ | freemangordon, hehe. We have few rainy dais ahead, here |
| 07:31.26 | freemangordon | that page? https://garage.maemo.org/projects/cssu/ |
| 07:31.34 | Estel_ | what I'm pissed about, is just information havoc. Also, it turned out, that busybox-power isn't "installable from extras without hassle", as it's, in fact, postinst script with binary replacement. *only* other possible - and proper - way would be to add it via CSSU, as it's critical systemk component |
| 07:31.45 | Estel_ | freemangordon, yes |
| 07:31.49 | Estel_ | this page |
| 07:32.01 | kerio | Estel_: well, not really |
| 07:32.04 | freemangordon | well, he is admin on THAT page ;) |
| 07:32.08 | kerio | make a repo, call it "busybox" |
| 07:32.20 | Estel_ | kerio, make a repo? seriously? CSSU is repo for such things :) |
| 07:32.21 | kerio | and make sure the version is higher than the other busyboxen |
| 07:32.28 | Estel_ | and "make a repo" doesn't fail into "installable from extras" |
| 07:32.38 | Estel_ | freemangordon, well, suspected something fishy |
| 07:32.42 | freemangordon | see, I want merlin1991 back before continuing that discussion, ok? |
| 07:32.46 | Estel_ | sure |
| 07:32.52 | Estel_ | wanted to propose exactly same thing |
| 07:32.59 | freemangordon | hold your horses then :P |
| 07:33.01 | Estel_ | no need to add into information mess around CSSU :) |
| 07:33.42 | freemangordon | no need to make unnecesarry noise |
| 07:34.02 | kerio | freemangordon: are you kidding me |
| 07:34.07 | kerio | http://www.youtube.com/watch?v=P7B-AlKTdGQ |
| 07:34.09 | Estel_ | one good thing fromt his whole mess - many people got interested about CSSU and way it's maintained. Maybe, just maybe, ages long idea of "steering group" for cssu will got revived, at some point |
| 07:34.24 | Estel_ | more and more devels and users would benefit from knowing what can be expected, and what not |
| 07:34.53 | freemangordon | but to be clear - CSSU maintainers are MohammadAG(CSSU-T), merlin1991(CSSU-S CSSU-T(backup) and chem|st (CSSU-S) |
| 07:34.53 | Estel_ | kerio, wanna blow up my speakers? |
| 07:35.00 | kerio | about half of RFUS is unnecessary noise |
| 07:35.07 | Estel_ | freemangordon, thanks a lot for that clarification |
| 07:35.22 | Estel_ | chem|st, lol |
| 07:35.24 | kerio | freemangordon: and freemangordon(CSSU-Th)! |
| 07:35.31 | freemangordon | kerio: no |
| 07:35.40 | kerio | :( |
| 07:35.51 | freemangordon | CSSU-thumb is not "official" CSSU |
| 07:36.07 | freemangordon | otherwise, yes, I am the one who upload stuff there :D |
| 07:36.12 | freemangordon | *uploads |
| 07:36.17 | kerio | (: |
| 07:37.22 | freemangordon | the point is - don't put -thumb and CSSU in one place until there is a need to do so ;) |
| 07:38.01 | kerio | Estel_: btw, blowing up speakers is what that song is supposed to do |
| 07:38.04 | kerio | well, kinda |
| 07:42.14 | freemangordon | http://www.youtube.com/watch?v=yLgporKLnpA |
| 07:49.03 | chem|st | Estel_: ? |
| 07:50.09 | Estel_ | chem|st, sorry for pinging, You were only mentioned |
| 07:50.57 | Estel_ | see full context - I was just surprised, as I wasn't aware of You being actively contributing to CSSU in any way, for a long time (haven't confirmed it, just feeling, thus my comment - excuse me if it's not true) |
| 07:51.08 | Estel_ | kerio, see query |
| 07:51.17 | kerio | i lost the query \_o_/ |
| 07:51.25 | kerio | my client is stupid |
| 07:51.34 | kerio | i just hoped it wasn't important |
| 07:55.11 | Estel_ | wasn't at all, will re-send it anyway :P |
| 07:58.55 | Estel_ | freemangordon, fuck! I just noticed that my work on CSSU-T wiki page wasn't saved, what the f? Probably browser hickup |
| 07:59.01 | Estel_ | have backup, will fix it ASAP |
| 07:59.07 | Estel_ | sorry, I was sure it's up and running hapilly |
| 07:59.15 | Estel_ | for a few days, actually |
| 07:59.24 | Estel_ | CSSU-T as in CSSU-Th, sorry |
| 08:12.14 | chem|st | Estel_: well I come from alpha testing and some of the early stages of MohammadAG's stuff past my device like "would someone mind to test that real quick? - reflash" |
| 08:12.42 | chem|st | Estel_: and now I will grow some balls and take over stable! HA |
| 08:14.50 | chem|st | I am not very good in doing bugreports as I like to talk to devils in irc instead of filing it properly... but that is from being used to alpha-testing... there were no such thing as bugtracking apart of a spreadsheet |
| 08:16.41 | chem|st | Estel_: and btw it is again your attitude that makes people mad at you, I for one ignore it for a long time now, but laughing at people whom actually did some more than just talking is nuts |
| 08:17.42 | chem|st | *facepalm* |
| 08:18.27 | Estel_ | chem|st, peace, it wasn't offensive, just stating facts, and only when you've asked :) |
| 08:18.43 | chem|st | you pinged me... |
| 08:19.00 | chem|st | I did not ask! |
| 08:19.04 | Estel_ | I feel it strange, when someone not related to project for a looooong time - and as You said Yourself, You were never really into CSSU thing - is listed as maintainer. that'sd all, it doesn't offend You. |
| 08:19.12 | Estel_ | Until you're (clearly) overreactive about Your ego. |
| 08:19.17 | Estel_ | no, never pinged You |
| 08:19.25 | Estel_ | commented during discussion |
| 08:19.36 | Estel_ | mentioning someone's nick != pinging |
| 08:20.00 | Estel_ | so take a deep breath and relax :) |
| 08:21.25 | Estel_ | BTw, out of curiosity, if You are here, already - once You've mentioned, that You're able to dissasemble and assemble back again n900 in 20 minutes (as answer to me, speaking about time required to put back again flip-flop mechanism of N950 - You though, that I was talking about N900) |
| 08:21.34 | Estel_ | I have asked You - out of curiosity - why it takes You so long? |
| 08:21.47 | Estel_ | you've never answered, though |
| 08:22.01 | Estel_ | i'm just curious, which part is most bitchy for most people (of assembling device) |
| 08:22.48 | Estel_ | as ussually, it takes 5-7 minutes to dissasemble and assemble, including screen (2 minutes depends on screen connector, which can be tricky, even for trained people) |
| 08:23.30 | chem|st | the domesheet is an ass |
| 08:23.44 | chem|st | all the shielding boxes |
| 08:24.27 | DocScrutinizer05 | (([2012-08-31 09:34:53] <freemangordon> but to be clear - CSSU maintainers are MohammadAG(CSSU-T), merlin1991(CSSU-S CSSU-T(backup) and chem|st (CSSU-S))) ---- excatly, and those decide on their peer&steering-group, and - like it or leave it - they don't listen to estel with his bitching |
| 08:24.31 | chem|st | if disassambling does not inlcude those it is those 8 screws off those some clips of and everything back together again |
| 08:24.57 | chem|st | that was what I did after a wheatbeer attack, I'd guess some minutes? |
| 08:25.42 | DocScrutinizer05 | btw my contribution is to constantly dispute with fools who think THEY are steering group and smarter than those who got a word by merit. |
| 08:25.56 | chem|st | DocScrutinizer05: I love you! |
| 08:26.07 | Estel_ | DocScrutinizer05, in fact, I find You mentioning garage page with You being listed as admin - suggesting that it means You're a maintainer - quite cheap |
| 08:26.14 | Estel_ | but as said, I'll leave it until merlin1991 comes back |
| 08:26.44 | DocScrutinizer05 | I give a fuck about your definition of maintainer, it's simply irrelevant to CSSU |
| 08:26.55 | chem|st | I did not follow busybox stuff as I don't give a fuck! |
| 08:27.23 | chem|st | what does it fix? |
| 08:27.25 | Estel_ | he, he, so i;ll gladly reffer to "fortunatelly, DocScrutinizer05 isn't maintainer, so all things presented is his private opinion,only, equal to every ordinary CSSU user" in context of busybox-power |
| 08:27.46 | DocScrutinizer05 | chem|st: ONCE AGAIN SOME FOOLS WANT TO MAKE SOMETHING MANDATORY THAT'S *ALREADY* OPTIONAL, JUST FOR THE "BENEFIT" OF ANOTHER 500K OF ROOTFS EASTED |
| 08:27.48 | Estel_ | chem|st, upstream bugfixes, recent actual busybox version. |
| 08:27.56 | DocScrutinizer05 | chem|st: OOOPS CAPSLOCK, SORRY |
| 08:28.02 | DocScrutinizer05 | dammit |
| 08:28.05 | Estel_ | it isn't optional, and You were delibatery spreading FUD about it. It's *not* easily installable from extras. |
| 08:28.13 | Estel_ | Only one way to replace busybox properly, via package, is CSSU. |
| 08:28.22 | DocScrutinizer05 | bullshit |
| 08:28.23 | Estel_ | package in extras use dirty trick, that replaces binary file via postinst script |
| 08:28.26 | Estel_ | ugly and inneficcient |
| 08:28.32 | Estel_ | no other way, as it's core system package |
| 08:28.36 | DocScrutinizer05 | so why do WE care? |
| 08:28.43 | chem|st | Estel_: that is not realy mandatory if there is nothing in cssu actually needing it capiché? |
| 08:28.47 | Estel_ | You could distribute whole CSSU via "postinst script that replace binaries", but it's *wrong!* and wrong again. |
| 08:29.08 | Estel_ | chem|st, reffer to busybox-power release notes, for lsit of fixed bugs |
| 08:29.10 | Estel_ | list* |
| 08:29.15 | kerio | *capisc' |
| 08:29.17 | DocScrutinizer05 | I could kick you for constant trolling |
| 08:29.28 | Estel_ | we actually have busybox update in CSSU - that adds portrait support to it, sic! |
| 08:29.35 | DocScrutinizer05 | we could roll an estel cssu distro |
| 08:29.37 | chem|st | DocScrutinizer05: don't let me do it° |
| 08:29.41 | chem|st | (TM) |
| 08:29.41 | DocScrutinizer05 | we could eat shit |
| 08:29.54 | Estel_ | DocScrutinizer05, sure, you could kick everyone and feel powewr! But it's pathetic, again, everytime You speak about it, during discussion. |
| 08:29.55 | chem|st | we could make him eat shit o.O |
| 08:29.58 | Estel_ | and speaks poorly about You |
| 08:30.20 | kerio | DocScrutinizer05: it's actually just 300k wasted if you use the thumbified version, btw |
| 08:30.49 | chem|st | Estel_: my browser is stalling... would you mind to state some bugfixes that are really important? |
| 08:30.56 | DocScrutinizer05 | kerio: thanks! and it's even 90mb saved, if we don't use emacs version |
| 08:30.59 | Estel_ | DocScrutinizer05, like it or not, i'mabsolutely sure, that CSSU will progress, witrh thing like busybox-power and - much later - thumb. Well, again, no need to argue, future will tell who was right :) |
| 08:31.21 | Estel_ | chem|st, sorry, read busybox-power logs Yourself, i'm not Your search engine. |
| 08:31.25 | chem|st | DocScrutinizer05: who booted emacs? |
| 08:31.31 | DocScrutinizer05 | Estel_: so what? maybe you're sure the earth is a disk |
| 08:31.34 | DocScrutinizer05 | I don't care |
| 08:31.44 | chem|st | Estel_: FUCK YOU I JUST STATED THAT MY BROWSER STALLED! |
| 08:31.50 | Estel_ | well, CSSu would benefit *much* if You would care, actually, in my opinion ;) |
| 08:32.03 | Estel_ | chem|st, sorry, missunderstanding |
| 08:32.17 | chem|st | Estel_: ok thank so no facts just wishes... |
| 08:32.18 | Estel_ | I though it's my browser stalled -> which busybox power bugfix will help with it |
| 08:32.30 | Estel_ | i.e. as for browser in N900, which is irrelevant |
| 08:32.34 | chem|st | no here... darn ff |
| 08:32.39 | Estel_ | sure, wait a second |
| 08:32.51 | chem|st | updates are progressed for minutes now |
| 08:33.48 | Estel_ | chem|st, from top of my head, swapon finally support priorities properly |
| 08:33.56 | Estel_ | waiting 'till page loads :) |
| 08:34.18 | chem|st | I hate being at work... we have a "no linux" politician upstairs |
| 08:34.25 | Estel_ | (i.e. setting swap priority on stock busybox was ignored, for no reason, as this parameter was listed in -h) |
| 08:34.53 | Estel_ | chem|st, other thing from top of my head - proper shell history handling |
| 08:35.01 | Estel_ | both for multi-instances of x-term |
| 08:35.04 | chem|st | Estel_: you know that stuff in cssu is meant to go to stable some day... |
| 08:35.08 | Estel_ | of course |
| 08:35.12 | DocScrutinizer05 | Estel_: if you still haven't groked it, my contribution to CSSU is exactly what I'm doing all the time: keeping overview of the larger perspective, check for stupid ideas and explain why they won't fly, find better alternatives if the original intention has any inherent value. So basically YOU give me tons of workload |
| 08:35.18 | Estel_ | busybox-power is in fact much older project than CSSU ;) |
| 08:35.25 | DocScrutinizer05 | so what? |
| 08:35.27 | Estel_ | one of msot respected and stable ones |
| 08:35.51 | Estel_ | DocScrutinizer05, it's nice, as my contribution to CSSu is explaining whjy You'r arguments are totally made up, biased, and irrelevant. Happy now? :) |
| 08:35.54 | chem|st | +1 so what? |
| 08:35.59 | Estel_ | and least we have balance in universe |
| 08:36.05 | DocScrutinizer05 | Estel_: WE DON'T NEED bb-p in cssu. ETX |
| 08:36.08 | chem|st | cssu is no fancy "power" playground |
| 08:36.16 | Estel_ | chem|st, as for Your question "chem|st> Estel_: you know that stuff in cssu is meant to go to stable some day..." |
| 08:36.24 | Estel_ | busybox-power is much more stable than cssu-S, anyway :P |
| 08:37.36 | chem|st | *sigh* |
| 08:37.44 | Estel_ | as for other fixes, it's really hard to mention in IRC - just check upstream fixes for busybox, since Maemo's ancient version |
| 08:37.47 | Estel_ | tons and tons of them. |
| 08:37.54 | Estel_ | and I mean only fixes, not enchancements. |
| 08:38.09 | Estel_ | chem|st, busybox-power have -power in name jsut as a kind of pun... |
| 08:38.20 | Estel_ | but I see that both You and DocScrutinizer05 have problem with things having "power" in name, heh? |
| 08:38.42 | chem|st | Estel_: maemo is literally sarge crossed with edge and people try to go wheezy with eating parts of squeeze on the way up |
| 08:38.55 | Estel_ | DocScrutinizer05, speak what You want - I'm absolutely sure that busybox-power *will* be included in CSSU. Wan't to risk bootle of best beer?:) |
| 08:39.05 | Estel_ | hehe |
| 08:39.23 | chem|st | we are trying to let it become squeeze and not sid |
| 08:39.47 | Estel_ | well, the thing is that busybox-power meet every single smallest criteria/requiments to get into CSSU - upstream bugfixes, well tested, actively maintainer over a years, can't be distributed properly outside CSSU |
| 08:40.00 | Estel_ | and DocScrutinizer05 is bitching about it only due to personal prefferences |
| 08:40.06 | Estel_ | thats the point :) |
| 08:40.28 | Estel_ | fortunately, DocScrutinizer05's influence on CSSU is much lower than he like to thing it is, so i'm absolutely sure it will made it into CSSU, very soon. |
| 08:40.43 | chem|st | does it benefit cssu now (I am not asking about later I am asking about now!) |
| 08:40.50 | Estel_ | until that, no much need for arguing, as neither of us (me or DocScrutinizer05) is deciding about it |
| 08:40.54 | Estel_ | sure |
| 08:40.58 | kerio | chem|st: how does MHD benefit cssu? |
| 08:41.06 | Estel_ | but define "benefit" would be great |
| 08:41.12 | Estel_ | as nothing in CSSU benefit CSSU :P |
| 08:41.17 | Estel_ | how portrait support benefit CSSU? |
| 08:41.22 | Estel_ | CSSU is meant to benefit users, not itself |
| 08:41.45 | chem|st | busybox is not a user benefit |
| 08:42.18 | DocScrutinizer05 | Estel_: you're spamming channel with bullshit. Nobody is interested in your delusions, and we're definitely not amused about your lies |
| 08:42.34 | Estel_ | stop speaking about "everybody" or "nobody", speak for Yourself |
| 08:42.45 | Estel_ | chem|st, what? hahaha |
| 08:43.02 | DocScrutinizer05 | so I declare busybox-power as a ban'able subjext in this chan just for you |
| 08:43.05 | Estel_ | busybox-power - even with current, borked implementation via binary replacement - have more users than cssu |
| 08:43.17 | chem|st | Estel_: you really expect me to trust you after all the shit you rolled the past 3 month? |
| 08:43.20 | Estel_ | DocScrutinizer05, sorry, but I have in certain place, what You declare. |
| 08:43.33 | DocScrutinizer05 | :shrug: |
| 08:43.37 | kerio | hm, i don't know if that translates well to english |
| 08:43.39 | DocScrutinizer05 | you've been warnned |
| 08:43.42 | Estel_ | chem|st, you think that I care if You trust me? Nice from You, but, well... |
| 08:43.43 | DocScrutinizer05 | officially |
| 08:44.27 | chem|st | Estel_: you still do not get the difference |
| 08:44.38 | Estel_ | DocScrutinizer05, You're also warned officially. There actually is ongoing process of revieving Your mental ability to be chanop in *any* Maemo channel. Of cours,e due to your constaint threat of kick/ban/whatever pathetic, while You lsoe Your nerves during discussion. |
| 08:44.55 | Estel_ | just for sake of your contributions to being chanop - get a deep breath, go for a walk... |
| 08:45.10 | *** mode/#maemo-ssu [+o DocScrutinizer05] by ChanServ |
| 08:45.13 | Estel_ | and stop this bullshit madness, everyone is free to talk about busybox in context of CSSU. |
| 08:45.27 | *** kick/#maemo-ssu [Estel_!~HaleBopp@openmoko/engineers/joerg] by DocScrutinizer05 (don't threat chanops!) |
| 08:45.50 | *** join/#maemo-ssu BCMM (~ben@unaffiliated/bcmm) |
| 08:45.56 | *** join/#maemo-ssu Estel_ (~Estel@Maemo/Community/council/Estel-) |
| 08:46.28 | Estel_ | DocScrutinizer05, your power abuse speaks poorly about You, and will be reported. I don't expect fast action, but be ensured, that it will be bounced back to You, sooner or later :) |
| 08:46.35 | chem|st | Estel_: nice that was actually the first time DocScrutinizer05 kicked someone while I was live and the item was no spambot... |
| 08:46.44 | *** kick/#maemo-ssu [Estel_!~HaleBopp@openmoko/engineers/joerg] by DocScrutinizer05 (don't threat chanops!) |
| 08:46.57 | chem|st | DocScrutinizer05: stop it please |
| 08:47.07 | DocScrutinizer05 | ok |
| 08:47.29 | *** join/#maemo-ssu Estel_ (~Estel@Maemo/Community/council/Estel-) |
| 08:47.42 | chem|st | Estel_: hope you took a deep breath out there |
| 08:47.58 | Estel_ | why so? This conversation is over, won't waste my fingers on this pathetic guy. |
| 08:48.06 | DocScrutinizer05 | just can't stand that bitchingt anymore, and somebody threating me and ignoring authority of chanops nby "stick it where the sun doesn't shine" makes me angry |
| 08:48.17 | Estel_ | not that it matters, really, he is as powerless, as he think he is powerful. Or even more the former :) |
| 08:48.44 | chem|st | Estel_: DocScrutinizer05 would you both mind to stop trolling now? |
| 08:49.09 | chem|st | setup a channel for it and buy t-shirts... |
| 08:49.47 | chem|st | Estel_: bb-p will be reviewed for sure but by the calcs of now I doubt it being included next week |
| 08:50.00 | DocScrutinizer05 | ooh, cannel named "estel's collected lies performed live"? |
| 08:50.02 | Estel_ | same here, certainly not in next update. |
| 08:50.41 | Estel_ | AFAIK it's being reviewed actually, merlin1991 is jsut on vacation. It's sad that busybox-power thread was filled with lies, that it's not gonna enter cssu, though. |
| 08:50.44 | chem|st | we have a bit of work to do next week so better help with that and put everything else aside for now |
| 08:50.49 | Estel_ | of course You know where those FUD originates ;) |
| 08:51.22 | DocScrutinizer05 | counting up on lie counter |
| 08:51.22 | Estel_ | absolutely agree, no need to haste. All people need is reliable information, and there was much mess about busybox-power state re CSSU. |
| 08:51.41 | Estel_ | OTOh, merlin1991 officially started revieving it something like week ago. |
| 08:51.49 | chem|st | it all stopps at my doorstep, and I prefer shoot'em all and let god sort them out |
| 08:53.29 | *** mode/#maemo-ssu [-o DocScrutinizer05] by ChanServ |
| 08:53.40 | *** join/#maemo-ssu M4rtinK (~M4rtinK@mail.melf.eu) |
| 08:53.41 | DocScrutinizer05 | thanks |
| 08:53.43 | DocScrutinizer05 | forgot |
| 08:54.02 | chem|st | o7 |
| 08:54.55 | DocScrutinizer05 | wondering if I should leave for my last workday at STE, or rather have a coffee and 'enjoy' IRC a bit more |
| 08:55.27 | chem|st | ouhuuu last working day, I'd run for it to get it over with |
| 08:55.39 | chem|st | ff still stalling... |
| 08:55.59 | DocScrutinizer05 | hey, your key is borked? :-D |
| 08:56.00 | chem|st | .net framework assistent |
| 08:56.10 | DocScrutinizer05 | aaah FireFox |
| 08:56.45 | chem|st | my e key is borked, do you know where I can get a domesheet from? |
| 08:57.11 | DocScrutinizer05 | chem|st: estel had the nice idea to start a thread on tmo to spank cssu maintainers and give them "motivation" |
| 08:57.17 | chem|st | and would you mind selling or lending me one of your devices? I do not have any luck with ebay |
| 08:57.30 | chem|st | DocScrutinizer05: ? |
| 08:57.49 | chem|st | DocScrutinizer05: or gimme a hand with ebay? |
| 08:57.50 | Estel_ | in fact, no - I though about getting information about state of CSSu maintaining, how it looks. |
| 08:58.25 | chem|st | Estel_: your intentions are questionable but the outcome is what counts |
| 08:58.43 | Estel_ | it started, when some well known egomaniac linked me to garage page with DocScrutinizer05 mentioned in admin list, suggesting, that it means he is maintainer |
| 08:58.57 | Estel_ | chem|st, I never did it, so I preffer outcome is null ;) |
| 08:59.15 | Estel_ | all after all, I'm sure merlin1991 will clear all this mess upon returning, as some people went too rogue for civilized people's taste. |
| 08:59.43 | Estel_ | ...about stating what cssu will and won't be, authoritary, without being a maintainer. Eh, do we really need to continue it here? :) |
| 08:59.56 | DocScrutinizer05 | Estel_: I suggested you should look at that page and grep it for "joerg" and "estel" |
| 09:00.00 | DocScrutinizer05 | nothing more |
| 09:00.06 | DocScrutinizer05 | lie counter counting up |
| 09:01.34 | DocScrutinizer05 | chem|st: sure, I can help with ebay, I can lend you one of my devices as well. Or you ask our chief contributor Estel_ to actually stand up and *do* something about cssu and lend you one of his devices |
| 09:02.03 | chem|st | Estel_: ? |
| 09:04.34 | chem|st | sighup child problem 4 days ago... so much about stable |
| 09:04.46 | DocScrutinizer05 | Estel_: yes, I'm sure merlin1991 will politely explain to you the 50th time that you don't understand how cssu hierarchy and merit works, and that there's simply no use in you asking "are you maintainer?" since one thing's for sure: YOU are none |
| 09:05.09 | DocScrutinizer05 | chem|st: o.O |
| 09:05.14 | DocScrutinizer05 | how did you tell? |
| 09:05.31 | Estel_ | chem|st, in -devel releasE? |
| 09:05.38 | Estel_ | seriously? |
| 09:06.04 | Estel_ | if it what makes package not OK for CSSU, it would be empty repo. |
| 09:08.59 | Estel_ | DocScrutinizer05, I shouldn't be even speaking with You about all this egomaniac shit You have just done - but, as before - future will tell, who was right, and I'll be glad to mention it - as history - next time You will authoritary declare what will and what won't be in CSSU. More and more you're doing it, the less reliable source of information you become. People will remember that, when busybox-power will enter CSSU. End of topic, I g |
| 09:08.59 | Estel_ | uess? |
| 09:09.56 | DocScrutinizer05 | blablablablablabla |
| 09:10.32 | chem|st | Estel_: fyi - https://garage.maemo.org/projects/cssu-stable/ |
| 09:11.17 | Estel_ | chem|st, it was mentioned, and he is jsut admin on *that* page. |
| 09:11.29 | chem|st | Estel_: and DocScrutinizer05 is not self-assigned... he was asked for |
| 09:11.31 | Estel_ | <freemangordon> but to be clear - CSSU maintainers are MohammadAG(CSSU-T), merlin1991(CSSU-S CSSU-T(backup) and chem|st (CSSU-S) |
| 09:11.57 | Estel_ | well, high time to revoke it, due to his mental state, if he doens't learn to behave... |
| 09:12.10 | Estel_ | but you're biased toward him, so no point in continuing this discussion, I suppose? |
| 09:12.56 | Estel_ | I'm just glad, that despite fact, that we don't like each other (me and You, chem|st), we can have a civil talk, without threats of abusing chanop powers, etc |
| 09:13.15 | Estel_ | It speaks good about You. |
| 09:13.29 | chem|st | Estel_: it is no abuse if you step over the line... |
| 09:13.46 | DocScrutinizer05 | which in my book he just did again |
| 09:13.54 | Estel_ | sorry, "defining" busybox as "ban" topic for certain user, out of ass, is stepping out of the line by chanop, and You know it as well as I. |
| 09:14.10 | chem|st | sometimes you get me quiet close or get me pondering with a silence spell casted on you |
| 09:14.14 | Estel_ | especially during merit discussion, where we can disagree, but we shouldn't abuse power. |
| 09:14.41 | Estel_ | well, I'm glad that reliability wins over personal "dislike" in you, then :) |
| 09:15.34 | Estel_ | as we don't need to agree, just need to be civil while doing so. It's not popularity contest, after all. |
| 09:15.34 | chem|st | Estel_: while you are trolling it is ok with me to make it a no go topic for you, bb is reviewed and will be in the future, for now this discussion about bb chanop and you and me having a beer while chatting is over, do you understand? |
| 09:16.25 | Estel_ | well, for me it isn't, and higher authorities will investigate it - along with other evidence of DocScrutinizer05 abuse (which was already considered valid). |
| 09:16.43 | DocScrutinizer05 | lie counter counting up |
| 09:16.45 | Estel_ | in fact, it's You who keep pinging me, while I'm doing other, productive things ;) |
| 09:17.02 | DocScrutinizer05 | lie counter counting up |
| 09:17.25 | Estel_ | so no problem with FINALLY ending this embarassing and msierable topic. After all *some8 people might think that they're center of universe, which we don't want, eh? ;) |
| 09:17.38 | Estel_ | going back to work |
| 09:17.49 | DocScrutinizer05 | lie counter counting up, i'm afraid |
| 09:18.58 | chem|st | which part of stop it didn't pass your eys? |
| 09:19.11 | chem|st | you too DocScrutinizer05! I am fed now |
| 09:21.53 | chem|st | whohoo apple looses again vs sammy (japan this time) |
| 09:28.20 | kerio | chem|st: what did you eat? |
| 09:28.36 | DocScrutinizer05 | chem|st: I really get fed up with this guy stating lies since a week ar longer now (starting with his claim that merlin allegedly said bb-p will get included in next T...) and ignoring each sane argument why bb-p is not exactly a candidate for cssu at all. Instead he turns discussion into age old BS where he's defining who got 'authority' in cssu, just to continue with insulting me. If all that doesn't seem to make his arguments fly, |
| 09:28.38 | DocScrutinizer05 | <PROTECTED> |
| 09:33.21 | DocScrutinizer05 | chem|st: did he answer your request to lend you a N900? |
| 09:34.26 | DocScrutinizer05 | probably not, since he likes to ignore any request to actually *contribute* to cssu, rtaher than just ranting and claiming he knows better than those in charge to decide |
| 09:35.09 | DocScrutinizer05 | meh, cya |
| 09:36.48 | DocScrutinizer05 | actually my suggestion he should simply stop his bitching if he was concerned about motivation of cssu crew was no kidding. I feel like this guy eats way too much time in my life, and that makes me feel bad about cssu work |
| 09:40.07 | chem|st | thanks |
| 09:40.40 | DocScrutinizer05 | chem|st: /query me re N900 lending |
| 09:40.56 | DocScrutinizer05 | or purchase |
| 09:41.00 | chem|st | DocScrutinizer05: will do |
| 09:41.01 | DocScrutinizer05 | whatever you prefer |
| 09:41.17 | chem|st | will have another try with ebay.de and ebay.us |
| 09:41.48 | chem|st | 2 devices I want one I need... if I get two I can give one to my gf |
| 09:46.02 | DocScrutinizer05 | chem|st: monitor Bluefon24.de offers. They don't have own website it seems, but frequently offer on ebay, under changing names but finally redirecting to bluefon24 |
| 09:46.16 | DocScrutinizer05 | their devices are usually good and with warranty |
| 09:48.48 | kerio | "NOKIA N900 Schwarz" for 189,00€ |
| 09:48.51 | kerio | what's that supposed to be? |
| 09:51.50 | DocScrutinizer05 | a black N900? |
| 09:52.02 | kerio | why is there a "NOKIA N900 Black" for like 50€ more |
| 09:52.03 | DocScrutinizer05 | sounds like Bluefon |
| 09:52.12 | kerio | is that the price for the translation? |
| 09:52.27 | kerio | yeah, yeah, on bluefon24.de |
| 09:55.01 | DocScrutinizer05 | my two devices were 250EUR iirc, dunno why the price tag differs that much with same reseller |
| 09:55.55 | DocScrutinizer05 | anyway both my devices were in "like new" condition, just missing original packaging and accessories except charger |
| 09:56.32 | DocScrutinizer05 | one came with wrong type of battery though ;-D |
| 10:04.02 | kerio | my second n900 was really "like new" |
| 10:06.07 | merlin1991 | moin |
| 10:06.22 | merlin1991 | anybody care to point me the right pages in bb-p madness thread? |
| 10:06.46 | kerio | oh hey, you're back! |
| 10:06.48 | kerio | hi! |
| 10:06.51 | merlin1991 | for now :D |
| 10:07.06 | merlin1991 | I'll be back for real on sunday |
| 10:10.05 | merlin1991 | ... |
| 10:10.17 | DocScrutinizer05 | merlin1991: http://talk.maemo.org/showthread.php?p=1255699#post1255699 |
| 10:14.09 | merlin1991 | did people on tmo go full retard? |
| 10:14.53 | Estel_ | merlin1991, it's all about DocScrutinizer05 popping over there and telling them that busybox-power won't be included, because he doesn't like it ;) |
| 10:15.13 | Estel_ | understand it - informational havoc is worst thing for such situations |
| 10:16.02 | merlin1991 | I don't know where people got the idea that bb-p is going to be included |
| 10:16.31 | Estel_ | we have bb-p that *can't* be distributed properly outside cssu (hackish way of binary replacement via postinst script isn't OK), is maintained constantly over the years. includes upstream bug fixes, etc |
| 10:16.37 | DocScrutinizer05 | yeah, and you're doing your best to run havoc against cssu and info we did or did not give |
| 10:16.39 | Estel_ | i.e. fullfill all things needed for CSSU |
| 10:16.42 | merlin1991 | we had the busybox-power maintainer in here some time ago and discussed possible pitfalls if we update the core busybox package with small changes |
| 10:16.54 | Estel_ | wlel, maybe it's because next CSSU announced update of busybox with Pali's fixes for portrait mode? |
| 10:17.23 | Estel_ | merlin1991, sure, and logical question arised - why cssu update core busybox with small changes, instead of using busybox-power upstream release |
| 10:17.28 | Estel_ | as it's upstream busybox, essentially. |
| 10:17.30 | DocScrutinizer05 | no, it's because YOU made that up, another lie you're not getting tired to spread |
| 10:17.46 | DocScrutinizer05 | merlin1991 never said bb-p will go into cssu |
| 10:17.56 | merlin1991 | we didn't *announce* that, and the target was todo exactly what you said, busybox with Palis 1 liner patch |
| 10:17.59 | Estel_ | DocS, can You shut up, please? We're talking here about things that you, apparently, have no idea about, as shown in TMO thread about bb-p |
| 10:18.01 | Estel_ | thanks in advance |
| 10:18.16 | Estel_ | merlin1991, OK,, understood |
| 10:18.20 | Estel_ | so logical question now, again |
| 10:18.23 | DocScrutinizer05 | 2nd warning about getting rude3 |
| 10:18.38 | Estel_ | if we can update busybox with one liner path for portrait mode support, why can't we merge busybox-p mainstream bugfixes as well? |
| 10:18.46 | Estel_ | <PROTECTED> |
| 10:18.47 | Estel_ | damn space |
| 10:18.57 | kerio | wow, that's not incredibly passive-aggressive at all |
| 10:19.07 | merlin1991 | Estel_: mainstream update is not a "bugfix" as is |
| 10:19.09 | DocScrutinizer05 | and lie counter counting up, though it's maybe just poor style and not a lie when you state I got no clue |
| 10:19.21 | Estel_ | merlin1991, since maemo's ancient version, mainstream busybox got TONS of bugfixes |
| 10:19.23 | merlin1991 | err I meant upstream |
| 10:19.25 | Estel_ | see busybox changelogs |
| 10:19.50 | Estel_ | not to mention that iDon'ts work actually affected upstream too, which we should be proud about. |
| 10:19.51 | *** join/#maemo-ssu LaoLang_cool (~LaoLang_c@221.226.175.139) |
| 10:20.15 | DocScrutinizer05 | merlin1991: better ignore Estel_ just like he ignores me and probably meanwhile chem|st as well, since we have discussed that shit with him ad nauseum already |
| 10:20.21 | Estel_ | people are getting really pissed off, by fact that some things are not included into CSSU just because one random guy opposes it in IRc, without merit reasons |
| 10:20.28 | merlin1991 | Estel_: can you point me to a bugfix in upstream vs maemo that we *need* ? |
| 10:20.36 | Estel_ | busybox power seems to fullfill *all* CSSU criteria requiments |
| 10:20.53 | Estel_ | merlin1991, fix for swapon supporting priorities like it should? |
| 10:20.53 | DocScrutinizer05 | merlin1991: no he can't |
| 10:20.55 | kerio | merlin1991: swapon priorities could be one, but it depends on what "need" means, in the context of CSSU |
| 10:21.02 | kerio | i mean, it's not a user thing |
| 10:21.02 | Estel_ | properly handling shell history for multi-terminal instances? |
| 10:21.27 | Estel_ | + question "do we need upstream bugfixes" is quite ridicolous |
| 10:21.31 | Estel_ | do we need portrait mode in cssu? |
| 10:21.44 | Estel_ | do we need any bugfixes at all? well, it works out of the box, so why cssu? |
| 10:21.48 | DocScrutinizer05 | merlin1991: a user shell is a user domain issue. No need whatsoever to mess with system stuff to fix anything in it |
| 10:22.01 | Estel_ | I absolutely understand freemangordon's point of view noews - it's extremely frustrating how CSSu is maintained |
| 10:22.16 | Estel_ | it seems to be somewhere in-between bleeding-edge updates (portrait) and LTS only shit |
| 10:22.39 | DocScrutinizer05 | if only he'd get proper consequence and start his own cssu project instead of bitching at us |
| 10:23.06 | Estel_ | ok, after calming down a little: |
| 10:23.25 | Estel_ | merlin1991, the problem is, that process of decidi9ng what wil lgo into cssu and what not is totally misty |
| 10:23.30 | Estel_ | not-transparent |
| 10:23.38 | Estel_ | and both suers and devs can't expect what to do |
| 10:24.09 | Estel_ | results: we have things like freemangordon's (and other devs too, if You talk with them unoficially) doubts if it's worht the effort |
| 10:24.13 | Estel_ | worth* |
| 10:24.33 | *** join/#maemo-ssu iDont (~dennis@j138215.upc-j.chello.nl) |
| 10:24.45 | Estel_ | it's ridicolous, if CSSU would be LTs only - in my udnerstanding, LTS is valid only, if You have "normal" updates in-between. LTS "only" is an oxymoron, you can't have every update LTS. |
| 10:24.56 | Estel_ | iDont, ncie to see You, we're discussing bb-p, actually :) |
| 10:25.25 | iDont | Estel_, just read the chanlog, though it would be wise to join :P |
| 10:25.35 | iDont | s/though/thought |
| 10:26.00 | Estel_ | continuing my thoughts about it - it's completely not understandable why bb-p shouldn't be included in CSSu, as it's: |
| 10:26.08 | Estel_ | 1. not distributable via extras by normal means... |
| 10:26.10 | merlin1991 | Estel_: it's actually quite easy regarding bb-p iDont (afaik) never pushed for it to end up in cssu so the whole question is m00t |
| 10:26.15 | *** join/#maemo-ssu MrPingu (~chatzilla@86.92.226.97) |
| 10:26.20 | Estel_ | ( iDont, thanks a lot, it's definitelly good idea :) ) |
| 10:26.30 | Estel_ | merlin1991, developer need to push something? wtf? |
| 10:26.36 | Estel_ | with stick, or shovel? |
| 10:26.41 | Estel_ | I would preffer devels actually coding |
| 10:26.50 | Estel_ | and CSSu maintainers deciding, what may be good for cSSU to include |
| 10:27.12 | DocScrutinizer05 | no, evidently he prefers when HE decides on that |
| 10:27.15 | merlin1991 | iDont: I might be wrong here, but I think you never asked for bb-p in cssu? |
| 10:28.05 | Estel_ | merlin1991, CSSu isn't british queen, where people need to ask for audience :( many times users - including me - asked for busybox-power in CSSU. |
| 10:28.08 | Estel_ | isn't that enough? |
| 10:28.24 | DocScrutinizer05 | no |
| 10:28.30 | Estel_ | also, iDont already mentioned that busybox-power way of replacing busybox is hackish, and proper replacement would require inclusion in CSSU |
| 10:28.34 | DocScrutinizer05 | since users also ask for pink pony |
| 10:28.34 | merlin1991 | Estel_: and about "push" we are short on manpower, so we only include things where we have someone who will take care of it in a cssu sense |
| 10:28.40 | Estel_ | DocSanyway, lets all shut up and let iDont speak ;) |
| 10:28.59 | *** join/#maemo-ssu lizardo (lizardo@nat/indt/x-pdmikdrgrcuwjvqy) |
| 10:29.15 | merlin1991 | iDont: did you actually ask for bb-p inclusion to cssu? |
| 10:29.22 | iDont | merlin1991: one sec, searching chanlog. I somewhat did, but that's a very long time ago (before pushing busybox-power to extras-devel), and before CSSU-s |
| 10:29.27 | Estel_ | merlin1991, understandable. that's why I mentioned "constantly maintained over the years". I'm sure that iDont would hapilly maintain bb-p in CSSU, if agreed to include. |
| 10:30.11 | Estel_ | iDont, but I'm right that binary replacement is hardly "proper" way of distributing it (done as only one alternative for CSSU, that allow easy distribution)? |
| 10:30.28 | Estel_ | i.e. that it's same type of things, that CSSU already includes, like QT and others? |
| 10:30.35 | DocScrutinizer05 | "mainaining bb-p" means also maintaining all initscripts regarding compatibility to bb-p, in CSSU context |
| 10:30.41 | iDont | Estel_: yes, touching another package's binaries is not how Debian intented package management |
| 10:31.03 | Estel_ | DocScrutinizer05, stock maemo's initscripts and cssu ones doesn't have problem with busybox-p |
| 10:31.10 | DocScrutinizer05 | and no, it's obviously not same thing, not even same class of thing |
| 10:31.17 | iDont | aargh, searching chanlog of maemo takes a while :( |
| 10:31.18 | Estel_ | it's absolutely same class of thing. |
| 10:31.29 | Estel_ | iDont, take Your time, no worries |
| 10:32.20 | Estel_ | merlin1991 - short of manpower is actually valid argument to. that's why people interested in CSSU - that can't code - are trying to help as "activists" - by highlighting things that are good candidates for CSSU, collecting opinions, checking if arguments are valid, etc... |
| 10:32.49 | Estel_ | it's absolutely unbearable how DocScrutinizer05 sabotages such efforts, as self-maintained "maintainer" of cssu integrity, but that's different topic |
| 10:32.54 | DocScrutinizer05 | if this guy wouldn't simply answer concerns "X needs attention" with "no, it doesn't, it's OK", his contributions were sometimes a tad usefull |
| 10:33.05 | Estel_ | which I would like to touch later, to not waste iDont time reading about |
| 10:33.43 | Estel_ | (in context of busybox-power, it was about DocScrutinizer05 using "it's properly distributed via extras, which is WRONG and false, totally - but please, lets put it into later time) |
| 10:33.59 | DocScrutinizer05 | pffff |
| 10:34.31 | merlin1991 | Estel_: if you want to deal with stuff later bring them up later, this way it's just a slap into $persons face which they are not *allowed* to react on |
| 10:34.33 | iDont | merlin1991, Estel_, see http://mg.pov.lt/maemo-irclog/%23maemo.2011-04-29.log.html#t2011-04-29T21:48:13, though there wasn't any follow up, and neither did I push for inclusion |
| 10:34.39 | DocScrutinizer05 | merTHANKS |
| 10:34.46 | DocScrutinizer05 | merlin1991: thanks |
| 10:34.51 | DocScrutinizer05 | friggin capslock |
| 10:34.59 | merlin1991 | stop pressing it ;) |
| 10:35.08 | iDont | However, personally, I would like to see busybox-power in CSSU, though it's not up to me to decide |
| 10:35.21 | DocScrutinizer05 | merlin1991: too close to tab |
| 10:36.21 | iDont | I also think we can't really separate the "power" part (i.e. extra features etc) from the upstream part (which I would think suits the CSSU) in busybox-power. |
| 10:36.29 | DocScrutinizer05 | iDont: it comes with rootfs penalty, so making it mandatory is depriving those users from their freedom-of-choice who rather keep those 500k in / free than getting power extensions |
| 10:36.33 | iDont | which could pose to be a problem, regarding inclusion guidelines |
| 10:37.35 | Estel_ | merlin1991, if we care about 500k in rootfs, we should switch to thumb immediatelly, in all cSSU |
| 10:37.39 | Estel_ | this argument is pure sophism |
| 10:37.39 | iDont | DocScrutinizer05, I agree. Personally, I don't think 500K is much, but indeed, there is also something as freedom of choice. Also see what I just typed (re the power part), which causes the substantial increase in binary size |
| 10:37.59 | Estel_ | OTOH, other than CSSU, how can we distribute busybox-poweR? |
| 10:38.06 | Estel_ | as package that replaces binary via script |
| 10:38.14 | Estel_ | thinking like that, we could distribute whole CSSU like that |
| 10:38.16 | Estel_ | in extras. |
| 10:38.19 | Estel_ | iDont, agree? |
| 10:38.26 | Estel_ | merlin1991, I hope You see the point. |
| 10:38.35 | DocScrutinizer05 | iDont: and, as we already discussed last time we chatted here, busybox is a mission-critical component that should see particularly careful and conservative patches, which need particularly close review and tests |
| 10:38.57 | Estel_ | only one argument against busybox-power is 500kb (in fact, less than that) rootfs space, and "compatibility with 3rd party scripts that actually relies on bugs" (sic!), courtesy of DocScrutinizer05 |
| 10:39.00 | Estel_ | which is pure sophism. |
| 10:39.06 | iDont | Estel_, I agree, but we need to weigh the (dis)advantages of busybox-power vs. messy replacement in postinst |
| 10:39.25 | merlin1991 | iDont: actually bb-power could be done in cssu in the planned replacement system, it would conflict with regular busybox and replace it but would be a user choice |
| 10:39.44 | Estel_ | iDont, absolutely correct. But, what disadvantages we have here? where busybox-power presents any regressions? |
| 10:40.14 | kerio | merlin1991: provide/conflict doesn't handle dependencies for versions correctly, iirc |
| 10:40.26 | kerio | so you'd have to add busybox | busybox-power to the metapackage and to the other stuff, for instance |
| 10:40.45 | iDont | merlin1991, but then bb-power would need to depend on CSSU? Also see: http://talk.maemo.org/showpost.php?p=1001182&postcount=12 |
| 10:41.06 | kerio | iDont: well, not really |
| 10:41.27 | kerio | but it would break the non-cssu metapackages, and i doubt they'll let you put a package with "Conflicts: busybox" in extras |
| 10:41.31 | DocScrutinizer05 | lie counter counting up, I never said "3rd party scripts" (what a bullshit in fact), it's about genuine initscripts, which this guy again either ignores or is too dull to grok |
| 10:43.36 | merlin1991 | iDont: well basically it's a question of where you want to see busybox-power, if you want it on *every* device we obviously can't do it via cssu it has to stay in extras then, if you'd like it to be included in cssu we'd probably go with a conflicts: busybox scheme which works fine because the busybox-power package would be in the cssu repo, not in extras |
| 10:46.09 | iDont | merlin1991, when I started busybox-power, I could either make it only available to CSSU users via a clean way (as you describe), or to everyone via binary replacement. I chose the latter, since CSSU was very new then |
| 10:46.35 | iDont | I'm all for freedom-of-choice, and don't want to force busybox-power on anyone just for the sake of it being widely used |
| 10:46.41 | iDont | or something like that |
| 10:47.01 | iDont | Se basically we need to make the same descision regarding distribution again |
| 10:47.13 | merlin1991 | well we could preserve the freedom of choice even within cssu |
| 10:47.58 | iDont | Do you have any figures regarding how widely CSSU is deployed? |
| 10:48.03 | merlin1991 | sadly not |
| 10:49.06 | kerio | iDont: well, people interested in unixy stuff won't have problems with it, i hope |
| 10:51.46 | iDont | Hmm, I'm thinking all possibilities regarding packaging & distribution over, bear with me please |
| 10:51.59 | merlin1991 | iDont: busybox power is your project, we're not going to suddenly include it over your head into cssu because $user wants it there, on the other hand if you wish to see it there we'll use a way to keep freedom of choice |
| 10:52.40 | merlin1991 | and also you have all the time in the world to decide I want this in cssu :) |
| 10:53.54 | chem|st | cssu-extras? |
| 10:54.29 | kerio | you wouldn't even need a separate repo, actually |
| 10:54.54 | merlin1991 | chem|st: yep, it's going to arrive (at some point) |
| 10:56.01 | chem|st | merlin1991: that is what I meant by "give the user a choice and have cssu remain cssu and not a fancy-power-island" |
| 10:56.10 | kerio | just put busybox-power in the repos, but make it Provide and Conflict busybox |
| 10:56.24 | kerio | although maybe the metapackage will get confused if you do so? \_o_/ |
| 10:56.39 | iDont | kerio, IIRC that would break Nokia's metapackage |
| 10:56.49 | kerio | but not the CSSU one, if we change it |
| 10:57.25 | iDont | yes, but then we would need a split package, i.e. busybox-power and busybox-power-cssu, which I would like to avoid |
| 10:57.38 | kerio | i don't know if that would break things wrt the cssu installation though |
| 10:58.04 | iDont | kerio, that's busybox-power's resposibility (to not break anything) ;) |
| 10:58.55 | chem|st | we could have cssu-meta call for busybox >= cssu version and you just need to make sure to have your powerversion higher |
| 10:58.58 | merlin1991 | iDont: cssu removes the nokia metapackage, so in case you choose to push it into cssu you don't have to worry about that part anymore |
| 10:59.17 | iDont | merli1991, but that's the whole issue: that would exclude non-cssu users |
| 10:59.20 | kerio | chem|st: hm, how does Provides work with stuff like that? |
| 10:59.37 | merlin1991 | chem|st: we could simply do cssu-meta depends busyboy >= cssusomething | busybox-power >= somehting |
| 10:59.39 | kerio | does it take the version of the package with the provision? |
| 10:59.45 | chem|st | iDont: nope you still can provide it as a bin-replacement for non-cssu |
| 10:59.45 | merlin1991 | provides is fsckd |
| 11:00.08 | chem|st | merlin1991: I do not want -power in cssu |
| 11:00.20 | merlin1991 | ? |
| 11:00.34 | kerio | chem|st: wait, why? not even as a reference to a cssu-extras project? |
| 11:00.39 | chem|st | merlin1991: I want to provide the option to have -power in cssu just installed without dirty hacking |
| 11:00.43 | iDont | chem|st, I don't see how that's possible without a separate busybox package (one that does binary replacement for non-cssu, and one that does a clean install to /bin/busybox, for CSSU) |
| 11:00.44 | *** join/#maemo-ssu arcean (~arcean@aaeo144.neoplus.adsl.tpnet.pl) |
| 11:01.44 | chem|st | the one in cssu needs to have a higher index |
| 11:02.16 | iDont | that might actually work, in the same way as the -thumb version does now |
| 11:02.20 | *** join/#maemo-ssu ivgalvez (~ivgalvez@89.140.113.138.static.user.ono.com) |
| 11:02.26 | iDont | I haven't thought about that at all |
| 11:02.27 | chem|st | hmm well yes you need two differnt install scripts... |
| 11:02.58 | iDont | that's not an issue for me, as long as the user only sees one package |
| 11:02.58 | chem|st | uh that reminds me of outdated apt right |
| 11:03.31 | chem|st | if they have cssu installed they see the cssu package as the version is higher than in extras |
| 11:03.37 | kerio | now, upgrading from the old-style to the new-style... |
| 11:03.58 | chem|st | kerio: nope old style stays |
| 11:04.01 | kerio | that could be kinda painful |
| 11:04.19 | iDont | merlin1991, do you have any ETA on this cssu-extras repository? |
| 11:04.31 | kerio | chem|st: yeah but if and when we add the good-form busybox-power with the same name, people with the old-style busybox-power will be prompted to upgrade |
| 11:04.37 | kerio | and the new package will conflict with busybox |
| 11:04.46 | MrPingu | Maybe I am too simple why not pushing busybox with CSSU? I mean bbp is just a upstreamed busybox right? |
| 11:04.54 | merlin1991 | iDont: it's not a repository but lives within the cssu repo, and nope no eta |
| 11:04.55 | kerio | MrPingu: oh you |
| 11:05.08 | iDont | merlin1991, doh, of course |
| 11:05.09 | MrPingu | Kerio: Hi :) |
| 11:05.12 | chem|st | nope, as long as the cssu version of bb and bb-p are higher than bb-nokia bb-p |
| 11:05.20 | kerio | iDont: well, for instance busybox-power is already a package in the community-thumb repository |
| 11:05.39 | iDont | kerio, yes :). I completely forgot about the same mechanism for CSSU |
| 11:05.44 | chem|st | kerio: that does not harm does it? |
| 11:05.52 | kerio | chem|st: nope, it's completely unrelated |
| 11:05.59 | kerio | but it *can* be unrelated, it's just the same as extras |
| 11:06.22 | chem|st | kerio: they get prompted for an upgrade that does only provide the right package structure |
| 11:06.23 | kerio | if eventually we decide to make it conflict with busybox, stuff could break wrt metapackage |
| 11:06.26 | iDont | kerio, re upgrading from old busybox-power to cssu busybox-power: busybox-power uninstalls cleanly, so that won't pose to be an issue ;) |
| 11:06.46 | kerio | iDont: yeah but it's uninstalled together with busybox (nokia) |
| 11:06.58 | kerio | meh, i suppose that it would work |
| 11:07.04 | chem|st | kerio: the cssu version will conflict... the extras version not |
| 11:07.26 | chem|st | iDont: would that be suitable for you? |
| 11:07.27 | kerio | bb-p uninstalls, puts old /bin/busybox back, then bb uninstalls, then bb-p new is installed |
| 11:08.04 | iDont | chem|st, most certainly :) |
| 11:08.33 | iDont | I am and always was for freedom-of-choice. I just didn't see a alternative to inclusion in CSSU until now |
| 11:08.43 | chem|st | kerio: bb-p from extras gets a break for cssu installer... |
| 11:08.43 | iDont | an alternative* |
| 11:09.26 | chem|st | and I sidenote |
| 11:09.26 | DocScrutinizer05 | btw just for a tiny bit of self-glorification (to counteract this constant "Doc's not contributing" BS): it's been me who suggested/pushed cssu-s, it's been me who 'invented' optional packages in CSSU |
| 11:09.42 | kerio | chem|st: a break? |
| 11:10.03 | chem|st | DocScrutinizer05: we know... captain obviouse ;) |
| 11:10.03 | kerio | sorry, i can't parse what you just wrote |
| 11:10.09 | chem|st | kerio: sry |
| 11:10.16 | DocScrutinizer05 | not all know that, obviously |
| 11:10.34 | kerio | chem|st: oh, you mean that it would be uninstalled by community-ssu-installer? |
| 11:10.41 | DocScrutinizer05 | there's at least one guy who's constantly insulting me on the basis he never realized it |
| 11:11.23 | chem|st | kerio: cssu installer will install new package of bb, then there will be an upgrade available for bb-p |
| 11:11.36 | chem|st | uh that will brake |
| 11:11.49 | chem|st | iDont: uninstall overwrites bb right |
| 11:11.51 | chem|st | again |
| 11:12.05 | kerio | chem|st: yeah but it gets upgraded right afterwards |
| 11:12.07 | kerio | so it's no big deal |
| 11:12.16 | iDont | chem|st, yes. Everything is restored to pre-bbpower situation |
| 11:12.23 | kerio | besides, uninstall only changes /bin/busybox if it matches the checksum |
| 11:12.30 | kerio | if it's been changed, it's left alone |
| 11:12.51 | chem|st | but there is no pre bb-p situatiuon after installing cssu |
| 11:13.01 | chem|st | ah ok |
| 11:13.04 | chem|st | good |
| 11:13.24 | merlin1991 | chem|st: you also have to think of the update where we introduce anything bb-p realted |
| 11:13.55 | merlin1991 | cssu is "installed" at that point so you do have a situations of bb-p after installing cssu |
| 11:14.16 | chem|st | merlin1991: yes I know |
| 11:14.20 | chem|st | merlin1991: one at a time |
| 11:14.30 | iDont | DocScrutinizer05, well, personally I agree with Estel_. I do think busybox-power would be a good fit for the CSSU. The main counter argument is theoretical breakage, which hasn't been experienced during busybox-power's lifetime. However, I do think that an optional package is always preffered. I just didn't see any way to achieve the latter until now :) |
| 11:14.51 | chem|st | merlin1991: I was thinking of new installation of cssu first - then upgrading |
| 11:14.52 | iDont | preferred* |
| 11:15.26 | iDont | Anyway, we got ourselves a solution now, so we can leave this discussion behind :) |
| 11:15.38 | Estel_ | iDont, that's why I was "advocating" busybox-power for CSSU, considering that devs have better thing to do than "lobbying", even for good case. |
| 11:15.56 | chem|st | the same thing will happen to cameraUI and other shit |
| 11:16.08 | iDont | Estel_, appreciated, though probably not by all ;p |
| 11:16.12 | chem|st | DocScrutinizer05: those ussd stuff patches you were talking about |
| 11:16.57 | chem|st | *# things |
| 11:16.59 | kerio | and the fukken cbsms widged |
| 11:17.01 | MrPingu | I didn't understand that :P I thought: CSSU includes upstreamed busybox -> Done |
| 11:17.06 | chem|st | kerio: +1 |
| 11:17.07 | merlin1991 | iDont: I'm not sure which solution you mean :D |
| 11:17.28 | Estel_ | it's ridicolous, that package need to be "advocated" toget into cssu, BTW, but that's different thing |
| 11:17.46 | Estel_ | MrPingu - busybox-power is upstream busybox |
| 11:18.01 | Estel_ | problem is that some people in CSSU seems to have philosophical problems about "do we need updates at all?" |
| 11:18.13 | MrPingu | Estel_: I am talking about buxybox including in CSSU |
| 11:18.14 | iDont | merlin1991, including a busybox-power variant in CSSU as optional package, in contrast to a completely separate busybox-power-cssu package |
| 11:18.22 | Estel_ | OTOh, people like DocScrutinizer05 are trying to put CSSU into stagnated, LTS-only (oxymoron!) thing |
| 11:18.29 | Estel_ | MrPingu, same here ;) |
| 11:18.55 | chem|st | Estel_: when you keep talking BS like this you will loose your space in this channel... |
| 11:19.03 | MrPingu | Estel_: My thoughts were, |
| 11:19.16 | DocScrutinizer05 | no, it's Estel_ who tries to transform cssu into bleeding-edge for the packages *he* prefers |
| 11:19.18 | MrPingu | Estel_: Why was that oxymoron part needed, really? |
| 11:19.23 | Estel_ | merlin1991, why the hell some things - like portrait support - enter cssu without problems, and some other - essential, clean, and well tested, not distributable via "normal" extras-means - just like busybox-power -have so much trouble doing so?> |
| 11:19.36 | Estel_ | MrPingu, was needed, as there is no such thing as LTS only |
| 11:19.44 | Estel_ | LTS by definition is release *between* normal releases |
| 11:19.58 | Estel_ | there is no such thing as LTS only, but DocScrutinizer05 openyl advocated CSSU becoming one. thats why it's oxymoron. |
| 11:20.28 | Estel_ | LTS only means "stagnation", just with prettier name. LTS, by definition, means to be stable "anchor" between more experimental features. Later, those features enter another LTS. |
| 11:20.34 | Estel_ | aka long-term-support |
| 11:20.35 | chem|st | Estel_: enough! |
| 11:20.36 | MrPingu | Estel_: IMO it wasn't neeeded to, I mean the message is clear even without oxymoron... |
| 11:20.42 | Estel_ | why someone want project to become LTs-only is beyond me |
| 11:20.46 | merlin1991 | Estel_: that's easy to answer, because it was people inside cssu doing portrait |
| 11:20.52 | Estel_ | MrPingu, not for everyone, as it seems :P |
| 11:21.06 | MrPingu | Estel_: It only makes people angry on you... |
| 11:21.06 | Estel_ | thats why freemangordon is thinking if CSSU is worth effort at all, IMO |
| 11:21.25 | Estel_ | merlin1991, so put iDont "inside" CSSU as busybox-power maintainer |
| 11:21.29 | Estel_ | problem solved |
| 11:21.38 | Estel_ | after all, no one in CSSU is maintaining everything |
| 11:21.50 | Estel_ | and IIRC, iDont said aloready dozens of times, that he would hapilly maintain busybox-power for CSSU |
| 11:22.06 | chem|st | Estel_: we just made clear how it is going to happen now you come and want it in another way |
| 11:22.08 | DocScrutinizer05 | [2012-08-31 13:08:33] <iDont> I am and always was for freedom-of-choice. I just didn't see a alternative to inclusion in CSSU until now |
| 11:22.52 | Estel_ | if there is viable alternative to including busybox-power in CSSU, that don't require dirty hacks like binary replacement in posinst, I'm all for it. |
| 11:22.54 | MrPingu | Anway what I wanted to say (don't shoot me, just my thoughts): |
| 11:22.55 | Estel_ | it's CSSU loss, after all |
| 11:23.18 | DocScrutinizer05 | stop suffering *OUR* headaches! |
| 11:23.22 | Estel_ | if only for the reason, that people like me won't need to be frustrated by how CSSU is maintained in long-term :P |
| 11:23.23 | MrPingu | Just put busybox with higher version number in CSSU repo and upgrade seems fine, doesn't it? |
| 11:23.42 | iDont | MrPingu, yes, that's what we're going to do |
| 11:23.43 | MrPingu | Ofcourse that doesn't give users a choice |
| 11:23.57 | chem|st | Estel_: topic is over! bb-p will find its place in cssu-extras... how that is going to happen is not on your call |
| 11:23.58 | *** join/#maemo-ssu andre__ (~andre@ip-89-176-24-140.net.upcbroadband.cz) |
| 11:23.58 | *** join/#maemo-ssu andre__ (~andre@Maemo/community/bugmaster/andre) |
| 11:24.06 | iDont | MrPingu, CSSU will depend on either busybox or busybox-power, so that would give the user freedom of coise |
| 11:24.10 | Estel_ | chem|st, fine, so go away now and let us talk :) |
| 11:24.29 | Estel_ | as we're not even sure if cssu-extras will *ever* happen. |
| 11:24.29 | DocScrutinizer05 | chem|st: that's again a ban'able insult |
| 11:24.42 | DocScrutinizer05 | in my book |
| 11:24.48 | MrPingu | Estel_: That go away part wasn't needed |
| 11:25.22 | MrPingu | Estel_: Don't get angry on me but you say mean things that aren't needed to get the message past |
| 11:25.36 | Estel_ | DocScrutinizer05, so ban me, and stop boring, ok? I'm really tired of Your pathetic, childish behavior with all those "Imma powerful chanop, phe4r me!" idiotic threats. I swear, that it's last time I reffer to it in any way, as it's not even worth lifting single finger. |
| 11:25.40 | DocScrutinizer05 | this guy is trolling every single day for last weeks err months, and using up our time we better spent discussing real stuff |
| 11:26.02 | *** mode/#maemo-ssu [+o merlin1991] by ChanServ |
| 11:26.06 | *** kick/#maemo-ssu [Estel_!~merlin@Maemo/community/cssu/merlin1991] by merlin1991 (Der Kindergarten ist woanders!) |
| 11:26.19 | *** join/#maemo-ssu arcean_ (~arcean@aaeo144.neoplus.adsl.tpnet.pl) |
| 11:26.21 | kerio | woanders? |
| 11:26.22 | *** mode/#maemo-ssu [-o merlin1991] by ChanServ |
| 11:26.24 | ivgalvez | badabum |
| 11:26.28 | chem|st | another place |
| 11:26.29 | merlin1991 | auto kick msg of quassel |
| 11:26.39 | MrPingu | woanders -> Somewhere else ;) |
| 11:26.40 | kerio | meh, it fits |
| 11:27.45 | iDont | merlin1991, to wrap things up on a high level: 1) CSSU metapackage will depend on either busybox or busybox-power 2) I'll create a new , separate busybox-power package for CSSU repo *the way it should have been (i.e. no dirty tricks)* 3) regular busybox-power will remain in maemo's extras for non-cssu users |
| 11:27.56 | MrPingu | iDont: Let's say I have install CSSU-Testing will that mean I get automatically an updated busybox? |
| 11:27.58 | iDont | merlin1991, ack? |
| 11:28.21 | ivgalvez | iDont that sounds great |
| 11:28.30 | merlin1991 | iDont: ack, but for sake of always having proper busybox-power in cssu we have to use a slightly higher verions in cssu ie +proper or whatever :) |
| 11:28.34 | kerio | MrPingu: yes-ish - on the next busybox-power upgrade you'll be prompted (by apt?) to uninstall busybox due to a conflict |
| 11:28.58 | merlin1991 | MrPingu: no won't |
| 11:28.59 | kerio | merlin1991: hm, isn't + for stuff outside of the version number? |
| 11:29.13 | kerio | MrPingu: that is, if you have busybox-power already |
| 11:29.38 | iDont | MrPingu, yes, the end-user won't notice any difference versus the old situation ;) |
| 11:29.42 | chem|st | kerio: no |
| 11:30.08 | MrPingu | You guys are confusing me |
| 11:30.13 | chem|st | kerio: well yes... (need to read all lines...) |
| 11:30.14 | iDont | merlin1991, yes, I'll make sure that the cssu variant will have a modified version string |
| 11:30.27 | chem|st | MrPingu: you won't get bb-p by default on cssu |
| 11:30.51 | *** join/#maemo-ssu LaoLang_cool (~LaoLang_c@221.226.175.139) |
| 11:30.55 | MrPingu | I see |
| 11:31.02 | kerio | iDont: hm, this thing with the names is full of possible pitfalls |
| 11:31.05 | chem|st | if you had bb-p installed you will be prompted for an upgrade |
| 11:31.34 | iDont | kerio, what are your concerns? |
| 11:32.02 | kerio | bb-p-extras and bb-p-cssu are upgraded together, but updating from one of the repos fails |
| 11:32.11 | kerio | and a cssu user ends up with the extras version for a bit |
| 11:32.18 | kerio | it's not fatal by any means, mind you |
| 11:32.20 | kerio | but it's boring |
| 11:32.30 | chem|st | kerio: ? |
| 11:32.47 | kerio | chem|st: extras will have a package called busybox-power too |
| 11:32.51 | iDont | kerio, there will be only one busybox-power package, but there will be two seperate versions of it. The CSSU version will have higher priority over the regular package for non cssu users |
| 11:33.07 | iDont | You can't have non-cssu version and cssu version installed at the same time |
| 11:33.19 | kerio | iDont: yeah but you have to make sure that cssu users' apts will be constantly aware of that |
| 11:33.19 | chem|st | kerio: extras-testing has one extras-devel has one so what? |
| 11:34.07 | *** join/#maemo-ssu arcean (~Arcean@aaeo144.neoplus.adsl.tpnet.pl) |
| 11:34.14 | chem|st | kerio: apt-get update? |
| 11:34.43 | chem|st | I don't get your concern it does not matter if bbp from extras is installed |
| 11:34.56 | DocScrutinizer05 | kerio: that's what merlin1991's pending work about cssu-ham and optional pkgs is all about |
| 11:35.56 | chem|st | if cssu is installed there is the cssu repo with a newer version that will uninstall the hacky one and install a proper bb replacement |
| 11:36.30 | iDont | kerio, think of the -thumb situation. Didn't bb-power's thumb version got installed as an upgrade over the non-thumb version a few days ago, even though it was the same version (minus the -thumb part)? |
| 11:36.52 | iDont | CSSU busybox-power > extras busybox-power |
| 11:37.09 | kerio | iDont: well, that's a good example actually |
| 11:37.15 | kerio | you released an update a few days ago, right? |
| 11:37.23 | iDont | Yes |
| 11:37.23 | kerio | freemangordon didn't immediately release that one too |
| 11:37.35 | kerio | and my apt prompted me to install the one from extras-devel |
| 11:37.40 | kerio | i mean, it's not a big deal |
| 11:37.46 | kerio | but it can happen if the versions aren't in sync |
| 11:38.17 | kerio | (then, when he released the same update too, it prompted me to upgrade to *that* version - the same, but with -thumb0) |
| 11:38.38 | iDont | kerio, that's a very good point indeed. We'll have to make sure CSSU version get's updated _before_ extras' version |
| 11:38.54 | iDont | luckily, that's entirely in our control :) |
| 11:39.52 | kerio | heh, it's the same server, too |
| 12:33.55 | freemangordon | well, what worries me, is the time frame in which "cssu-extras" will be available |
| 12:34.36 | freemangordon | talking started few months ago, but I am not aware of any progress |
| 12:36.10 | freemangordon | merlin1991: so the question about estimated time is pretty reasonable, it does not make sense iDont to write a pile of install scripts if we expect cssu-extras by june 2013 :P |
| 12:37.45 | freemangordon | merlin1991, chem|st: Why obexd and stuff are allowed to enter CSSU(not cssu-extras), but busybox is not? |
| 12:37.57 | iDont | freemangordon, I thought busybox-power would live in relevant cssu repositories, just like busybox-power lives in cssu-thumb? |
| 12:38.01 | iDont | <merlin1991> iDont: it's not a repository but lives within the cssu repo, and nope no eta |
| 12:38.46 | freemangordon | iDont: we need updated HAM in order it to work as planned, otherwise you (or me) should use apt-get to install |
| 12:39.13 | freemangordon | but CSSU's official installer is HAM, not apt-get ;) |
| 12:39.38 | kerio | freemangordon: why? |
| 12:39.45 | kerio | busybox-power would just be a package |
| 12:39.51 | kerio | and it's already installable via HAM |
| 12:39.51 | *** part/#maemo-ssu merlin1991 (~merlin@Maemo/community/cssu/merlin1991) |
| 12:40.01 | *** join/#maemo-ssu merlin1991 (~merlin@Maemo/community/cssu/merlin1991) |
| 12:40.04 | merlin1991 | ffs |
| 12:40.09 | iDont | heh |
| 12:40.09 | freemangordon | merlin1991: hi |
| 12:40.12 | kerio | merlin1991: chat comfortably! anywhere! |
| 12:40.17 | iDont | :-D |
| 12:40.39 | merlin1991 | kerio: it would use conflict: something which in ham only throws the use pc-suite to update error |
| 12:40.48 | kerio | oic |
| 12:40.56 | kerio | ...well, that would've been nicer to know earlier :/ |
| 12:41.16 | kerio | meh, i'm perfectly fine with requiring people to install busybox-power with apt |
| 12:41.25 | kerio | i mean, it's a fucking shell anyway |
| 12:41.55 | freemangordon | kerio: that is not how it should be |
| 12:42.12 | kerio | why not? plenty of packages don't even appear in HAM anyway |
| 12:42.19 | kerio | and i really don't see another way |
| 12:42.21 | iDont | kerio, I'm not, my priorities include not to exclude anyone from using it. Although I prefer apt-get > HAM as well |
| 12:42.23 | kerio | apart from using a separate installer |
| 12:42.25 | *** join/#maemo-ssu MrPingu (~chatzilla@86.92.226.97) |
| 12:42.48 | freemangordon | kerio: because you (and me) have no clue what is the user base |
| 12:42.49 | freemangordon | ;) |
| 12:42.56 | kerio | freemangordon: one could argue that that behaviour in HAM is a bug |
| 12:43.05 | kerio | because what the fuck were they thinking, really |
| 12:43.06 | kerio | :s |
| 12:43.20 | kerio | even **cydia** handles those more gracefully |
| 12:43.45 | freemangordon | irrelevan, we can't tell CSSU users to use apt-get |
| 12:43.54 | freemangordon | irrelevant even |
| 12:45.09 | MrPingu | iDont: Did you manage to fix that bug in bb-p hxka pointed out? |
| 12:45.25 | freemangordon | is afk for a cigarette |
| 12:46.41 | iDont | MrPingu, yes, but I need to test my patch more extensively |
| 12:47.29 | MrPingu | Goed :) |
| 12:48.43 | iDont | Only problem is, that signal handling is a touchy area in shells, and I haven't got any real experience in that area. So therefore the extensive tests (although the patch is relatively small) |
| 12:49.18 | MrPingu | I see :) |
| 12:52.11 | iDont | freemangordon, merlin1991, if I could get any follow up on (the ETA of) cssu-extras, that would be great. No rush though, as the current way of distributing busybox-power does the job fine, dirty or not |
| 12:53.31 | merlin1991 | iDont: I'll let you know as soon as I have anything |
| 12:53.43 | freemangordon | chem|st, merlin1991: I'll rephrase my question - according to what criteria upstream versions of obexd, curl, dosfstools, etc., etc., are good for CSSU, bu upstream version of busybox is not? |
| 12:54.12 | merlin1991 | somebody there who's doing the job :D |
| 12:54.33 | merlin1991 | till now I didn't see much intention from iDont to get busybox into cssu |
| 12:55.03 | freemangordon | iDont: correct? |
| 12:55.04 | merlin1991 | ah you mean why still doing it optional? |
| 12:55.11 | kerio | freemangordon: well, bb-p *adds* a lot of stuff |
| 12:55.20 | freemangordon | kerio: curl too |
| 12:55.38 | freemangordon | NFC for obexd, but almost sure it adds lots of stuff too |
| 12:56.21 | iDont | well, personally I do like to see busybox-power in CSSU. However, I think optional installation is better regarding freedom of choice. Especially since inclusion seems to be so highly controversial |
| 12:56.50 | freemangordon | yeah, controversial :D |
| 12:57.12 | freemangordon | merlin1991: yes, that was my point. |
| 12:57.15 | kerio | oh right, obexd adds a bunch of stuff wrt car integration, right? |
| 12:57.40 | freemangordon | and curl adds only luf knows what :) |
| 12:58.08 | merlin1991 | well curl / obexd are not that important core system component though |
| 12:58.29 | freemangordon | curl no core component? try to remove it :P |
| 12:58.39 | merlin1991 | true though that the why and how is hard to argue |
| 12:59.55 | MrPingu | Actually I agree with freemangordon, if bb-p is good why not include it the simple way? |
| 13:00.18 | freemangordon | merlin1991: we cannot act based on personal preferences though |
| 13:00.28 | merlin1991 | afk, lunch |
| 13:01.09 | kerio | MrPingu: because there's no reason to |
| 13:01.13 | kerio | much like cbsms-widget |
| 13:01.16 | freemangordon | enjoy your meal, gather some power and come back :P |
| 13:01.26 | kerio | although that's a bit different, because it's FUCKING BROKEN AS HELL |
| 13:01.31 | MrPingu | but cbsms has been included... |
| 13:01.38 | kerio | while busybox-power has no known regressions, apart from that minor one |
| 13:01.41 | kerio | MrPingu: in testing |
| 13:01.55 | kerio | and it'll be removed once cssu finds a process to include optional packages |
| 13:01.55 | freemangordon | kerio: and what is the reason for obexd and curl then? |
| 13:01.59 | kerio | freemangordon: beats me |
| 13:02.31 | MrPingu | Yeah but I guess we are always talking about testing? I mean it won't go directly to stable without testing ;) |
| 13:03.11 | MrPingu | freemangordon: completed my argumentation ;) |
| 13:03.33 | freemangordon | see, we should apply the same criteria for all of the packages, fuzzy evaluations like "core system component" are meaningless |
| 13:03.58 | freemangordon | but i'd rather wait merlin1991 back |
| 13:04.43 | kerio | freemangordon: but busybox-power has "power" in its name! |
| 13:05.59 | freemangordon | iDont: I just need straight answer if you want upstream busybox in CSSU or not, i.e. will you maintain it. Forget about freedom of choice for a while :P |
| 13:06.46 | freemangordon | kerio: well, we'll change it to busybox-weakness if needed :P |
| 13:07.02 | chem|st | freemangordon: what are you arguing? |
| 13:07.35 | freemangordon | chem|st: I am trying to find what is the criteria for package inclusion in CSSU, see may question above |
| 13:07.38 | chem|st | freemangordon: if you want something in cssu that needs bbp then depend on it! |
| 13:08.14 | iDont | If CSSU's scope clearly states that upstream components are a valid reason for inclusion in CSSU, then yes, because I'll have a valid argument for inclusion then. |
| 13:08.20 | iDont | ^freemangordon |
| 13:08.38 | freemangordon | chem|st: what in CSSU depends on obexd and curl? |
| 13:08.50 | freemangordon | (upstream versions) |
| 13:08.59 | chem|st | does it add mission critical things? nope |
| 13:09.15 | chem|st | freemangordon: libcurl?! facebooklogin |
| 13:09.28 | freemangordon | chem|st: yes, but why upstream? |
| 13:10.00 | chem|st | freemangordon: cause that was the one working?! |
| 13:10.23 | iDont | But even if upstream versions would be a valid reason, what about the -power part in busybox-power? Will that part be preserved (e.g. the extra features vs. stock BusyBox)? I prefer not create a *new* busybox-power if upstream busybox would be included in CSSU, but without power features |
| 13:10.39 | chem|st | iirc it was looking for a version that has the patch and is working... |
| 13:10.44 | freemangordon | wrong, what is in CSSU is -26, the one we tried was 25 |
| 13:10.59 | freemangordon | (iirc) |
| 13:11.20 | freemangordon | and what about obexd? what is ther system critical functionality it adds? |
| 13:11.25 | chem|st | whoohou 25-26 is what sorry I am so bad in math "1"? |
| 13:11.57 | merlin1991 | freemangordon: the problem with busybox-power is what iDont said, which modules do we compile if we include upstream code? |
| 13:12.15 | chem|st | freemangordon: you start like estel now?! |
| 13:12.28 | merlin1991 | updated obexd has better support for car kits, simple as that |
| 13:12.37 | freemangordon | chem|st: curl (7.26.0-1maemo1+0cssu1) unstable; urgency=high |
| 13:12.40 | merlin1991 | regarding curl, yeah that's vague |
| 13:12.50 | freemangordon | chem|st: naah, dont do that |
| 13:12.55 | chem|st | freemangordon: ;) |
| 13:13.28 | merlin1991 | but usually upstream should be ok, only in case of ie busybox we have the problem of the all in one which yields the question which parts do we really want? |
| 13:13.54 | chem|st | freemangordon: not the upstream fact is slowing the progress... the bare fact that it is compiled with more options |
| 13:13.58 | freemangordon | merlin1991: well, i might be wrong (or simply misunderstood something), but it was told that busybox-power is actually upstream busybox |
| 13:14.08 | kerio | "screw you guys, i'll start my own cssu! with busybox and hookers! in fact, forget cssu and busybox!" |
| 13:14.09 | freemangordon | merlin1991: we had the same for curl iirc |
| 13:14.20 | kerio | freemangordon: busybox is heavily configurable at compile-time |
| 13:14.25 | kerio | to include or exclude modules |
| 13:14.28 | merlin1991 | + nokia patches, yeah but only that busybox has a basillion switches for ./configure |
| 13:14.30 | freemangordon | kerio: ^^^ |
| 13:14.41 | chem|st | freemangordon: nope bbp is upstream + lots of functions activated |
| 13:14.54 | freemangordon | chem|st: aah, ok, my bad then |
| 13:15.11 | freemangordon | then we should remove obexd too |
| 13:15.19 | merlin1991 | ie less is disabled in stock busybox |
| 13:15.56 | freemangordon | as obexd adds carkti supprt, which does not exists in stock obexd |
| 13:16.12 | merlin1991 | well it is there, somehow, mostly broken |
| 13:16.15 | chem|st | freemangordon: stop trolling! |
| 13:16.19 | merlin1991 | it even works with *some* car kits |
| 13:16.28 | freemangordon | chem|st: what? |
| 13:16.46 | chem|st | "remove this and that" it is in there now live with it |
| 13:17.07 | merlin1991 | guys can we get back to ground zero? |
| 13:17.13 | chem|st | please |
| 13:17.50 | chem|st | merlin1991: monday evening ok with you? |
| 13:17.59 | freemangordon | well, I could ban myself easily, no need someone to do it |
| 13:18.00 | chem|st | merlin1991: I will be off all weekend |
| 13:18.03 | *** part/#maemo-ssu freemangordon (~freemango@130-204-50-168.2074221835.ddns.cablebg.net) |
| 13:18.24 | merlin1991 | jesus, has everyone gone mental today? |
| 13:18.31 | chem|st | yes |
| 13:18.36 | merlin1991 | chem|st: should be ok |
| 13:19.48 | iDont | freemangordon, if you're interested, check the OP of busybox-power's thread at TMO. It lists all new applets (tiny implementations of various tools) it introduces vs. the stock busybox package. Besides new applets, it also extends functionality of existing applets (e.g. Ctrl-R reverse history search in shell, swapon with priorities support, and _lots_ more) |
| 13:20.04 | kerio | iDont: he left |
| 13:20.14 | iDont | kerio, woops, missed that |
| 13:20.18 | kerio | he quit irc :s |
| 13:20.21 | iDont | brb |
| 13:20.24 | merlin1991 | just for the record I was actually more talking to chem|st regarding gorund zero |
| 13:21.17 | kerio | ground zero? |
| 13:21.54 | chem|st | ? |
| 13:21.56 | merlin1991 | calm state, common ground, no insulting madness, whatever you wanna call it |
| 13:22.06 | kerio | weed land |
| 13:22.08 | kerio | :D |
| 13:50.43 | *** join/#maemo-ssu freemangordon (~freemango@130-204-50-168.2074221835.ddns.cablebg.net) |
| 13:51.46 | freemangordon | merlin1991: just for the record - I did not quit because your "ground zero" :) |
| 13:52.23 | chem|st | freemangordon: I'm sorry, estel gave me a hard time today... |
| 13:52.55 | *** join/#maemo-ssu arcean_ (~Arcean@aael108.neoplus.adsl.tpnet.pl) |
| 13:53.00 | freemangordon | chem|st: np, I am calm, just keep it in mind I am not Estel ;) |
| 13:53.21 | chem|st | freemangordon: just stop barking about why things ended up being in cssu, they are there now, so it be |
| 13:54.10 | chem|st | I am pretty sure everything needed will get to cssu |
| 13:54.33 | MrPingu | chem|st: I believe it's more like: why are these CSSU why BB-p can't be? |
| 13:54.35 | chem|st | freedom of choice might be a pain in the ass in the ned |
| 13:54.47 | chem|st | end |
| 13:54.50 | freemangordon | chem|st: my point was regarding bb inclusion, I was trying to make an argument, that acording to the criteria applied to those packages, bb should be included too |
| 13:55.19 | freemangordon | I am the last one to ask for package to be removed from CSSU :) |
| 13:56.04 | chem|st | freemangordon: we talked that through now... bb will get upgraded and shipped with but bb-power will be optional iirc |
| 13:56.08 | kerio | i am the first! remove cbsms! |
| 13:56.34 | chem|st | kerio: that brought the whole story of cssu-extras to my attention |
| 13:57.27 | freemangordon | chem|st: bb will get upgraded to upstream and compiled with the same options as stock? I am absolutely ok if that is the case. |
| 13:57.32 | chem|st | so if there will be something rolling into cssu which needs bb-power it is there without hacky binery overwriting |
| 13:57.44 | iDont | chem|st, I actually missed the part that busybox will get upgraded and shipped |
| 13:58.06 | freemangordon | yep, me too :) |
| 13:58.24 | MrPingu | And this makes 3 |
| 13:58.28 | chem|st | ah ok no that was my idea behind it, strap out the power |
| 13:58.56 | freemangordon | I knew it is because of the -power thing :D |
| 13:58.57 | chem|st | upstream is ok if it is working fine but keep the bloat to a minimum |
| 13:59.14 | chem|st | it is not the name^^ |
| 13:59.23 | freemangordon | i know :) |
| 13:59.27 | chem|st | ;) |
| 13:59.55 | chem|st | but what is the difference between upstream and current? |
| 14:00.16 | chem|st | first of all, would it be smaller? |
| 14:00.19 | chem|st | faster? |
| 14:00.21 | freemangordon | current == stock? |
| 14:00.44 | chem|st | I love the "never change a running system" |
| 14:00.46 | MrPingu | http://www.busybox.net/ |
| 14:01.06 | MrPingu | scroll down till you see v1.10 :P |
| 14:01.37 | freemangordon | chem|st: don't know if you are aware, but libcurl in CSSU is around 280k bigger than stock |
| 14:01.56 | freemangordon | which about 100% increase |
| 14:03.07 | chem|st | I know |
| 14:03.12 | freemangordon | (iirc) |
| 14:03.57 | chem|st | ok some critical stuff I just see by scrolling the first 5 versions |
| 14:04.26 | chem|st | it is growing bigger |
| 14:04.43 | chem|st | iDont: would you mind to provide two versions? |
| 14:04.47 | freemangordon | iDont: I will check on the thread what are the additional modules included (i.e. -power stuff :) ) |
| 14:05.40 | MrPingu | chem|st: that list will become big :P |
| 14:05.47 | kerio | freemangordon: btw, the thumbified busybox-power is just 300k bigger than the stock arm busybox :D |
| 14:05.58 | chem|st | well np I guess it is the same source but different compiler flags + different version strings.. |
| 14:06.29 | iDont | chem|st, I don't mind, but is there any real interest in an updated BusyBox shell without power features? AFAIK most busybox-power users install busybox-power for its power features |
| 14:07.08 | chem|st | iDont: I am speaking of a cssu without power version |
| 14:07.23 | chem|st | nevermind |
| 14:07.40 | freemangordon | chem|st: well, if it does not bring harm, why not enable them? |
| 14:07.53 | MrPingu | freemangordon: you were faster |
| 14:08.02 | chem|st | space? |
| 14:08.05 | kerio | freemangordon: because mo money mo problems |
| 14:08.28 | chem|st | and less features means less bugs |
| 14:08.52 | iDont | There used to be two busybox-power versions: one with Nokia's config, and one with an enhanced config. The first was dropped because of a lack of interest. However, this was in mid-2011. |
| 14:08.55 | MrPingu | Some things like colored ls, is nice to have enabled in CSSU version too ver example |
| 14:09.13 | freemangordon | chem|st: yeah, I see the rationale, that is why I said i will check the additional modules |
| 14:09.21 | chem|st | +1 |
| 14:10.10 | freemangordon | chem|st: though 500k is not that much. |
| 14:10.24 | chem|st | the smaller the better, if we get some stuff rolling like "enhancements" people are used to but do not bloat it fine |
| 14:10.45 | merlin1991 | freemangordon: imo we should check what changes libcurl has |
| 14:10.46 | freemangordon | iDont: any chance to split it to /root /opt? or it is a single binary? |
| 14:10.46 | chem|st | freemangordon: take 10 programs that way and you have 5000k |
| 14:10.55 | merlin1991 | because as you said the size increase is huge |
| 14:11.05 | kerio | chem|st: so? 5mb is not a lot either :) |
| 14:11.22 | freemangordon | merlin1991: I asked luf, and iirc he explained there are dependecnies |
| 14:11.24 | iDont | freemangordon, single binary at the moment |
| 14:11.30 | chem|st | kerio: on my 3TB / at home yes... |
| 14:11.37 | kerio | chem|st: i have like 40mb free on / |
| 14:11.40 | freemangordon | iDont: any chance to split it? |
| 14:11.46 | kerio | and that's a very strict estimate |
| 14:11.56 | iDont | freemangordon, that's most certainly possible |
| 14:11.59 | kerio | (ubifs expands as needed, i only have 228mb used or something) |
| 14:11.59 | MrPingu | I used to have 70mb free on / |
| 14:12.07 | chem|st | kerio: and you need how much to do an upgrade? |
| 14:12.11 | kerio | beats me |
| 14:12.18 | kerio | incremental upgrades? not much |
| 14:12.21 | kerio | :D |
| 14:12.39 | kerio | i mean, the only big thing that i installed on / is gcc+libc6-dev+dependencies |
| 14:13.14 | chem|st | so now you have 30MB left and we have a look at some other stuff not being /optificationable |
| 14:13.15 | freemangordon | iDont: I think if it is possible to split it in such a way, that in rootfs to be the only things really needed for boot and the rest to stay in /opt, that would make everyone happy |
| 14:13.37 | freemangordon | chem|st: agree? |
| 14:13.42 | chem|st | freemangordon: that will brake startup stuff |
| 14:13.50 | freemangordon | chem|st: read again :P |
| 14:14.00 | freemangordon | (and excuse my english) |
| 14:14.18 | DocScrutinizer05 | freemangordon: busybox needs to stay in rootfs, needed during early boot. That's the main 8though not only) reason we don't want to make bb-p mandatory |
| 14:14.18 | chem|st | freemangordon: some waky people might like to do waky stuff while booting that it is -power! |
| 14:14.43 | iDont | freemangordon, yes, then we'll have to include two config files in the packaging and compile two separate binaries, I suppose |
| 14:15.09 | chem|st | we build it twice one is cssu (stock config) one is cssu-power |
| 14:15.29 | DocScrutinizer05 | freemangordon: and whole point of busybox is it's a monolithic binary |
| 14:15.41 | DocScrutinizer05 | chem|st: ++ |
| 14:16.00 | freemangordon | DocScrutinizer05: yes, I know, I am trying to find a way to make everyone happy :) |
| 14:16.11 | DocScrutinizer05 | we all do ;-D |
| 14:16.19 | chem|st | have a nice weekend! |
| 14:16.25 | freemangordon | chem|st: bb |
| 14:16.30 | DocScrutinizer05 | well, you too chem|st |
| 14:16.35 | chem|st | hits the road |
| 14:16.43 | *** join/#maemo-ssu ivgalvez (~quassel@41.pool85-49-220.dynamic.orange.es) |
| 14:16.45 | DocScrutinizer05 | celebrates vacancy |
| 14:17.14 | DocScrutinizer05 | duck and cover, now I got 24/7 time for maemo ;-P |
| 14:17.18 | kerio | well, the whole point of busybox is also not to execute a bunch of processes in shell scripts |
| 14:17.46 | DocScrutinizer05 | kerio: that's secondary at best |
| 14:18.11 | freemangordon | DocScrutinizer05: the point was - we could have only one package, which includes two binaries, one of them stays in rootfs (with the essentials needed for boot), the second lives in /opt |
| 14:18.19 | DocScrutinizer05 | the obvious main rationale for busybox been that Nokia tried to conserve as much space in rootfs as possible |
| 14:18.41 | kerio | and we should try to honour that! |
| 14:18.45 | kerio | by enabling thumb binaries! |
| 14:18.49 | kerio | flees |
| 14:18.50 | freemangordon | hehe |
| 14:19.06 | ivgalvez | juas |
| 14:19.27 | DocScrutinizer05 | freemangordon: you (maintainer of bb) could turn it into anything renamed from original busybox name, and keep it in /opt like any other *suer* shell |
| 14:19.31 | DocScrutinizer05 | *user* |
| 14:19.53 | kerio | DocScrutinizer05: i thought the rationale for busybox was that it was used in diablo and then hysterical raisins and then why bother changing |
| 14:19.59 | kerio | diablo and before, i mean |
| 14:20.14 | DocScrutinizer05 | maybe that too :-P |
| 14:20.36 | DocScrutinizer05 | loves hysterical raisins |
| 14:21.26 | freemangordon | DocScrutinizer05: there was a link with changes between stock version and upstream, see chem|st's comment on it: |
| 14:21.28 | freemangordon | 17:02 <chem|st> ok some critical stuff I just see by scrolling the first 5 versions |
| 14:21.29 | freemangordon | <chem|st> it is growing bigger |
| 14:21.58 | kerio | oh lol |
| 14:22.15 | freemangordon | DocScrutinizer05: so lets end that, ok? :) |
| 14:22.42 | DocScrutinizer05 | freemangordon: I'd not deny benefit of getting bugfixes to busybox, esp if they are system critical. But I question sane rationale behind including power extensions |
| 14:22.55 | freemangordon | DocScrutinizer05: chem|st proposed 2 packages, I am trying to reduce that to 1 |
| 14:23.01 | DocScrutinizer05 | good |
| 14:23.10 | freemangordon | without using precious rootfs space |
| 14:23.22 | DocScrutinizer05 | the less the better, it needs very close review since busybox is mission critical |
| 14:23.42 | freemangordon | but of course |
| 14:24.16 | DocScrutinizer05 | isn't it strange how even freemangordon and me could agree on something easily, as long as estel isn't bitching on stuff he doesn't completely understand |
| 14:25.02 | kerio | iDont: did you *disable* something from the upstream busybox? |
| 14:25.17 | freemangordon | iDont: so, I think if you manage to strip -power part in /opt, we can have only 1 package |
| 14:25.42 | iDont | kerio: only if it conflicted with Nokia's configuration |
| 14:25.47 | kerio | k |
| 14:26.14 | iDont | freemangordon, I could give that a shot, I see no reason why that wouldn't work |
| 14:26.31 | kerio | freemangordon: hm, so you have a stock-ish /bin/busybox with the usual commands there, and then /opt/busybox-power/busybox-power that's symlinked from all the other commands? |
| 14:26.44 | freemangordon | though chem|st has his point for those who may want to use some of the -power functionality in early boot |
| 14:26.56 | kerio | freemangordon: well, how early? |
| 14:27.09 | freemangordon | kerio: ask chem|st, not me :D |
| 14:27.10 | kerio | swapon priority would have to be compiled in /bin/busybox, for instance |
| 14:27.40 | iDont | freemangordon, yes, for example Mentalist Tracuer's recovery console relies on some of busybox-power's power features |
| 14:27.43 | DocScrutinizer05 | please keep in mind this whole annoying issue with initscripts depending on this very particular version of busybox cmd syntax *and* output, and semantic |
| 14:28.11 | DocScrutinizer05 | the stuff that estel misquoted as "3rd party scripts" all the time |
| 14:28.16 | kerio | DocScrutinizer05: we've got more than a year of testing with busybox-power, though |
| 14:28.29 | iDont | freemangordon, however, there are also a lot of applets that most certainly won't be used at boot (e.g. httpd) |
| 14:28.30 | kerio | non-rigorous testing, but still |
| 14:29.03 | freemangordon | iDont: you can include know stuff in /rootfs bb, I think there would be no onjections for 100-150k size increase |
| 14:29.18 | freemangordon | s/know/known/ |
| 14:29.27 | freemangordon | DocScrutinizer05: agree? |
| 14:29.30 | DocScrutinizer05 | kerio: this is very core mission critical stuff, you better have rigorous testing for every single possible case/branch |
| 14:30.07 | DocScrutinizer05 | 100k maybe on the tolerable side still, for the benefit to finally close this ticket |
| 14:30.13 | freemangordon | yeah |
| 14:30.17 | kerio | hahaha |
| 14:30.50 | DocScrutinizer05 | but no way to shorcut proper tests and review for any changes in cmd syntax, semantic, output |
| 14:31.05 | DocScrutinizer05 | of any of the already existing cmds |
| 14:31.17 | kerio | but... |
| 14:31.23 | kerio | stuff still works! :c |
| 14:31.59 | DocScrutinizer05 | orly? you tested with unformatted uSD? with 911 calls? with devicelock entere3d 3 times in sequence wrong? etc pp? |
| 14:32.06 | freemangordon | iDont: ok, now we only need merlin1991 to confirm he is ok (though I think he will be) |
| 14:32.21 | freemangordon | DocScrutinizer05: come on man, that is why testing is |
| 14:32.34 | DocScrutinizer05 | kerio: "WFM" never is any near a proper test/review |
| 14:32.35 | kerio | hm, would locking the device require nokia care? |
| 14:33.04 | ivgalvez | DocScrutinizer05 I seriously doubt Nokia did such tests to N900 |
| 14:33.05 | kerio | DocScrutinizer05: WFM is too mainstream |
| 14:33.07 | kerio | http://www.codinghorror.com/blog/2007/03/the-works-on-my-machine-certification-program.html |
| 14:33.17 | ivgalvez | considering the quality of PR1.0 |
| 14:33.22 | DocScrutinizer05 | ivgalvez: you're free to doubt that |
| 14:33.29 | DocScrutinizer05 | I know other companies do |
| 14:33.38 | ivgalvez | for sure... Nasa |
| 14:33.40 | kerio | other companies doubt that nokia did those tests? :o |
| 14:33.41 | ivgalvez | hehe |
| 14:33.45 | DocScrutinizer05 | so *I* doubt Nokia was the only company NOT doing such tests |
| 14:34.04 | freemangordon | DocScrutinizer05: Nokia n900 testing was exactly what we do in CSSU-testing AFAIK |
| 14:34.29 | ivgalvez | CSSU's is better as it's done in the open |
| 14:34.48 | iDont | DocScrutinizer05, what about WFM's from a supposedly large user base? The download count (not [unique] install count) of busybox-power is 265897 according to http://maemo.dadablog.net/AppStats.php?package=busybox-power&os=fremantle |
| 14:34.58 | DocScrutinizer05 | basically yes, but prior to giving some pkg to cssu-t we like devels to evaluate and rule out any obvious path for problems |
| 14:35.08 | freemangordon | but anyway, that is irrelevant, we don't have the resources Nokia had, so have to use whatever we have |
| 14:35.21 | merlin1991 | how do you plan todo the rootfs/opt thingy actually? |
| 14:35.50 | kerio | holy shit, 265k is a lot |
| 14:35.51 | merlin1991 | is it meant to be 2 times busybox one stripped and one full? |
| 14:36.05 | DocScrutinizer05 | yes, and our resources are pretty sufficient to review patches and find out if they change syntax, semantic, or output of a command in busybox. If they do, check if the command is used in initscripts |
| 14:36.23 | DocScrutinizer05 | pretty simple straightforward task, basic sanity checks |
| 14:36.23 | kerio | DocScrutinizer05: that's inefficient |
| 14:36.24 | iDont | merlin1991: two separate config files, tweak debian/rules to spit out two binaries. Only the symlinking has to be figured out AFAICS |
| 14:36.34 | kerio | check if the command is used in initscripts *and then* check if the behaviour changes |
| 14:36.38 | DocScrutinizer05 | kerio: no, that's the *only* efficient way |
| 14:36.49 | iDont | I got to go now, back in about half an hour. I'll stay connected to IRC |
| 14:36.55 | DocScrutinizer05 | well, that way as well can get done |
| 14:37.20 | DocScrutinizer05 | kerio: I don't care what we do first |
| 14:38.24 | DocScrutinizer05 | I thought for a small patchset it would be better to check only the patches if they change syntax etc of command. If you prefer to check for each command used in initscripts if there's a patch for it, you're welcome |
| 14:39.01 | freemangordon | iDont: i have NFC how is the simlinking done, but I suspect it has some relation to the install directory, so I hope there is no "symlining" problem |
| 14:40.23 | DocScrutinizer05 | after all I'd hope no syntax, semantic, or output changes got introduced by any of the patches we include |
| 14:41.31 | freemangordon | the fuck, men, it is symlinking :D |
| 14:41.34 | DocScrutinizer05 | after all busybox *claims* to be bourne shell compatible, so not much room for such changes after all |
| 14:42.39 | freemangordon | DocScrutinizer05: afaik there are lots of bb-p users, if there was some problem, it'd be found by now. I know, I know, WFM :) |
| 14:42.52 | DocScrutinizer05 | I'm mostly concerned about the fact it (has been) *not* completely bourneshell compatible, and that initscripts still rely on that, so if we'd fix any of that, we'd see massive problems eventually |
| 14:43.27 | ivgalvez | But are you referring to actual init scripts existing in PR1.3? |
| 14:43.27 | DocScrutinizer05 | freemangordon: aiui we're preparing even a new version now |
| 14:43.32 | ivgalvez | or personal ones? |
| 14:43.36 | DocScrutinizer05 | that hasn't seen *any* tests so far |
| 14:44.00 | freemangordon | yeah |
| 14:44.01 | DocScrutinizer05 | ivgalvez: referring to probably pre-1.2 official initscripts |
| 14:44.24 | DocScrutinizer05 | though nobody did proper investigations on that lately afaik |
| 14:44.32 | ivgalvez | how could one be running such ancient scripts and CSSU at the same time? |
| 14:44.54 | freemangordon | but it will go through -devel and -thumb, so it will see some testing before entering CSSU-T |
| 14:45.05 | DocScrutinizer05 | it's a known problem of pre-PR1.2 anyway. Since then changing init shell been so publicly deprecated we seen no recent tests on it |
| 14:46.03 | freemangordon | has to go, bbl |
| 14:46.03 | kerio | changed login shells for both user and root |
| 14:46.11 | kerio | no side effects so far |
| 14:46.50 | DocScrutinizer05 | I'm just saying we need to investigate if that problem just vanished without any of us noticing Nokia fixing it, or we simply didn't see it recently because of any other reason, for example nobody dared to mess with that stuff in the way we're going to do when fixing "bugs" in busybox |
| 14:48.17 | kerio | you know how could we test it? |
| 14:48.21 | DocScrutinizer05 | messing around with init shell isn't something you can do sloppy |
| 14:48.25 | kerio | by putting it in a repository dedicated to testing |
| 14:48.32 | kerio | we could call it "testing" |
| 14:48.42 | DocScrutinizer05 | kerio: stop trolling please |
| 14:48.45 | kerio | or maybe "devel" |
| 14:48.46 | kerio | k :c |
| 14:50.35 | DocScrutinizer05 | after all it's basically init scripts that get tailored to fit the existing init shell |
| 14:50.46 | DocScrutinizer05 | not other way round |
| 14:51.07 | kerio | the init shell is /bin/sh |
| 14:51.10 | kerio | well, the preinit |
| 14:51.11 | DocScrutinizer05 | so whatever change in init shell needs to get checked against *all* inti scripts for possible impact |
| 14:51.13 | kerio | #!/bin/sh |
| 14:52.31 | DocScrutinizer05 | you don't do such checks on a "WFM" basis, you need code-coverage-analysis basically, to make sure every single line of "code" in your scripts got run on the new shell and worked as expected |
| 14:53.06 | DocScrutinizer05 | or you do the already semi-sloppy way to just grep in init scripts for the suspicious commands |
| 14:53.54 | DocScrutinizer05 | "WFM" just ensures there's *ONE* working path, by no means it secures *all* possible pathes |
| 14:55.29 | DocScrutinizer05 | and "we don't have the manpower for that" is no valid excuse. IF we wouldn't have enough manpower for that, we mustn't touch the thing at all |
| 14:56.22 | DocScrutinizer05 | after all I still fail to see the really existing and occuring bug all this will fix |
| 14:56.34 | ivgalvez | you are assuming that Maemo should receive code coverage from CSSU |
| 14:56.45 | kerio | DocScrutinizer05: http://busybox.net/ <- check the changelog |
| 14:56.48 | kerio | from 1.10 to 1.20 |
| 14:56.51 | ivgalvez | when you don't even know if it was done in its development at Nokia |
| 14:56.57 | DocScrutinizer05 | so any risk on one side of scale is outweighed by exactly 0 benefit for system on the other |
| 14:57.16 | DocScrutinizer05 | kerio: thanks a lot man, actually a *useful* contribution |
| 14:57.22 | ivgalvez | code coverage outside the Aeronautical world? |
| 14:57.31 | ivgalvez | haven't seen that in my life |
| 14:57.35 | kerio | someone posted it earlier, actually |
| 14:57.48 | kerio | ivgalvez: is "space" in aeronautical? |
| 14:58.06 | ivgalvez | well yes, more or less the same ;) |
| 14:58.33 | kerio | ivgalvez: hm, maybe the military? |
| 14:58.50 | ivgalvez | I've worked for the military industry |
| 14:59.02 | ivgalvez | you don't want to know what kind of tests they do |
| 14:59.06 | ivgalvez | embarrasing |
| 14:59.06 | kerio | DocScrutinizer05: unsurprisingly, there's a ton of bugfixes since the stock busybox we have |
| 14:59.13 | kerio | there's also a ton of improvements |
| 14:59.19 | *** join/#maemo-ssu DocScrutinizer05 (~HaleBopp@openmoko/engineers/joerg) |
| 14:59.24 | DocScrutinizer05 | sorry, reconnect |
| 14:59.27 | kerio | DocScrutinizer05: unsurprisingly, there's a ton of bugfixes since the stock busybox we have |
| 14:59.27 | DocScrutinizer05 | ivgalvez: code coverage is done on every semi-commercial product. N900 is a 100% commercial product, and CSSU is designed to prolongue its life |
| 14:59.28 | kerio | there's also a ton of improvements |
| 14:59.38 | kerio | which is exactly the kind of stuff that you say we should triplecheck |
| 14:59.40 | ivgalvez | I work on commercial products |
| 14:59.50 | ivgalvez | I know people working on commercial products |
| 15:00.59 | ivgalvez | I don't know anyone making code coverage outside the DO178-C |
| 15:01.18 | DocScrutinizer05 | ivgalvez: same here (if you're willing to consider ST-Ericsson modem used in Samsung phones as a commercial product) |
| 15:01.35 | merlin1991 | do178-c? |
| 15:01.36 | DocScrutinizer05 | and they *do* code coverage |
| 15:01.42 | DocScrutinizer05 | in integration |
| 15:01.56 | DocScrutinizer05 | though it should be done by devels actually |
| 15:02.55 | DocScrutinizer05 | we also use test units |
| 15:02.56 | ivgalvez | merlin1991: DO178-C is for certification of software on airbone environments and other critical systems |
| 15:03.09 | DocScrutinizer05 | for each module |
| 15:03.36 | DocScrutinizer05 | which actually are written by devels, since those are supposed to know what to test in their sub-system |
| 15:03.42 | ivgalvez | DocScrutinizer05 a modem is a piece of hardware with very low level software to be integrated in end user products |
| 15:04.00 | ivgalvez | it's not the same kind of product |
| 15:04.03 | DocScrutinizer05 | "very low level software"?? bwahahaha |
| 15:04.22 | ivgalvez | I mean closer to the hardware |
| 15:04.30 | ivgalvez | maybe not well expressed |
| 15:05.04 | ivgalvez | sorry now on meeting |
| 15:05.09 | DocScrutinizer05 | o/ |
| 15:07.12 | iDont | back |
| 15:08.52 | DocScrutinizer05 | kerio: alas this 'changelog' on http://busybox.net/ isn't telling me which patches to review, since I dunno which of them get included to cssu. For sure we don't want to include them all, since then we again hit that "eats MB of rootfs space, and impossible to review all so introduces risk" issue |
| 15:09.45 | kerio | DocScrutinizer05: well, we'd need to grab all the ones that aren't configured away |
| 15:10.12 | kerio | so at the very least anything related to commands that are included with the stock BB |
| 15:10.30 | DocScrutinizer05 | so I think as long as it's freemangordon to review patches and decide which one or 2 packages we actually want to include to fix anticipated problems in busybox-vanilla, I'll just wait for his analysis if those patches change anything on syntax, semantics, or output of any command |
| 15:11.38 | DocScrutinizer05 | once he delivers that list, I'm more than willing to check the changes against current initscripts and give my verdict if I think they are safe or not |
| 15:12.35 | DocScrutinizer05 | (btw something estel happily rejected/ignored to do, when I suggested it to him as a true valuable contribution to cssu+bb topic) |
| 15:13.20 | DocScrutinizer05 | kerio: all on your page regarding what we need to include |
| 15:13.42 | DocScrutinizer05 | what we need to *consider* for inclusion |
| 15:14.29 | DocScrutinizer05 | and it's exactly those patches to commands already included in busybox that need triple check |
| 15:14.38 | kerio | http://i.qkme.me/3qpmrd.jpg |
| 15:15.29 | DocScrutinizer05 | since one or two *additional* commands wouldn't probably have much impact/risk regarding maemo init, since... well they're not used for obvious reasons |
| 15:15.44 | kerio | hehe |
| 15:16.03 | kerio | i just realized that the patches that shouldn't be included carelessly are the ones that are actually needed the most |
| 15:17.01 | DocScrutinizer05 | so, to pick a proper example, if we get an augmented swapon command, we need to review all invocations of swapon in initscripts and related core system stuff, to secure the old syntax is compatible with the new command |
| 15:17.15 | DocScrutinizer05 | kerio: indeed |
| 15:19.33 | DocScrutinizer05 | if however you (hypothetically) would introduce a *new* command "change-swap-prio" then we probably could get away with rationale like >oh well, nobody ever used change-swap-prio so far, so it's probably low risk for init process to enable that command< |
| 15:19.34 | ivgalvez | iDont ping |
| 15:19.44 | ivgalvez | speaking of issues |
| 15:19.48 | iDont | ivgalvez: pong |
| 15:20.10 | ivgalvez | again rebooting the device with bb-p open messed up my history :( |
| 15:21.24 | DocScrutinizer05 | ivgalvez: I guess that's because of busybox, for a number of sound reasons, handles history differently to standard shell? |
| 15:22.59 | iDont | DocScrutinizer05, yes, upstream busybox has proper history saving on shell exit implemented. Maemo's version just overwrites the history file with the current shells' history on exit (e.g. multiple shells open will result in lost commands) |
| 15:23.20 | DocScrutinizer05 | ivgalvez: aiui busybox differs massively from any other standard shell, regarding spawning of new instances for execution of scripts etc, so obviously history semantics are entangled to that |
| 15:25.05 | DocScrutinizer05 | iDont: (losing commands when closing multiple instances) a behaviour pretty much expected for any standard shell |
| 15:26.01 | DocScrutinizer05 | iDont: aiui on busybox you might find yourself actually *not* running multople instances even while you think you do |
| 15:26.20 | freemangordon | DocScrutinizer05: well, I think I have enough stuff in the queue to put bb there as well, I think we can find someone else to do it. Remember, I have to do the same assesmment to do for KP patches ;) |
| 15:26.37 | DocScrutinizer05 | yep |
| 15:26.50 | iDont | DocScrutinizer05: bash does save history from all (parallel) shell instances |
| 15:26.58 | DocScrutinizer05 | I'm all aware of your workload |
| 15:27.04 | *** join/#maemo-ssu mase_76 (~mase76@p5DD3BECB.dip.t-dialin.net) |
| 15:27.31 | DocScrutinizer05 | iDont: oh, it doesnow? not when I checked last time |
| 15:27.46 | iDont | I'm speaking of interactive shells of course |
| 15:28.19 | iDont | it does on my laptop: open two terminal emulators, write some commands in both, close them both, check history |
| 15:28.34 | DocScrutinizer05 | yeah, exactly. each interactive shell overwriting history file of last closing instance with its own one |
| 15:29.12 | iDont | that shouldn't be done, as you'll lose history that way. Bash does not lose history, and so does upstream BusyBox |
| 15:29.17 | DocScrutinizer05 | or you do append to file, probably by handling that in your exit rc files |
| 15:30.11 | DocScrutinizer05 | or you define a prompt commad to write out each single commadline to history file the very moment you fire it up |
| 15:30.30 | DocScrutinizer05 | command* ffs |
| 15:31.22 | DocScrutinizer05 | there's however no IPC between distinct bash instances, regarding history file writing |
| 15:32.55 | iDont | And neither is there any IPC in BusyBox' ash shell. BusyBox' ash appends its history to ~/.ash_history |
| 15:33.12 | iDont | but it can also be configured to write out history after each command (as you stated) |
| 15:33.12 | DocScrutinizer05 | last time I checked I got the impression bash just writes out the internal history buffer to ~/.bash-history on exit |
| 15:34.16 | iDont | ivgalvez, I could configure BusyBox to append each command to the history file, that would solve all history-related issues. That will put some extra strain on the eMMC though |
| 15:34.36 | iDont | although I'm not sure how much (considering it's only a line of text, but it does add up I guess) |
| 15:34.42 | iDont | anyone has some insight on that? |
| 15:34.57 | DocScrutinizer05 | anyway I'd guess that's a question of configuration, done either by shell envs (set --foobar on) or simply via user's ~/.bash-startup |
| 15:35.07 | DocScrutinizer05 | and ~/.bash-exit |
| 15:36.18 | DocScrutinizer05 | iDont: strain to eMMC is last concern here. There are way more rogue things in that respect - after all we got IO buffering as well |
| 15:36.52 | kerio | can't it be configured, anyway? |
| 15:36.54 | kerio | and besides |
| 15:37.00 | kerio | who the fuck actually uses busybox as a login shell? |
| 15:37.36 | DocScrutinizer05 | but, as mentioned, that's just a question of *user* config, since w mustn't change this behaviour for init shell which doesn't have any history for obvious reasons |
| 15:38.03 | DocScrutinizer05 | kerio: trolling again? |
| 15:38.19 | DocScrutinizer05 | who would use anything other than busybox for login shell? |
| 15:38.27 | kerio | me, for instance! |
| 15:38.29 | kerio | i use bash |
| 15:39.43 | ivgalvez | now my history ended up with some random C++ code, I wonder where did it came from |
| 15:40.01 | ivgalvez | iDont maybe that should be configurable then |
| 15:40.03 | DocScrutinizer05 | sounds like a busybox bug |
| 15:40.47 | ivgalvez | kerio: most embedded systems use bb |
| 15:40.56 | ivgalvez | I use it in STB for example |
| 15:40.57 | kerio | ivgalvez: i am aware of that :) |
| 15:40.58 | iDont | ivgalvez, at the moment it's only configurable at compile time |
| 15:41.18 | ivgalvez | :( |
| 15:41.23 | kerio | ivgalvez: the n900 is quite the powerful embedded system though :) |
| 15:41.29 | DocScrutinizer05 | pretty bad |
| 15:42.07 | DocScrutinizer05 | iDont: so could we get rid of any history handling in bb binary, and just handle that in the appropriate scripts? |
| 15:43.02 | DocScrutinizer05 | kerio: FSCK yeah! it's more powerfull than the laptop I used when I bought my first N900 |
| 15:43.02 | iDont | busybox disables history handling completely when the shell is not interactive. History handling (and all its related compile-time configuration) should therefore be irrelevant to scripts |
| 15:43.20 | iDont | unless those scripts start with #!/bin/sh -i, which I highly doubt |
| 15:43.38 | kerio | any script writer relying on shell history should be shot |
| 15:44.51 | *** join/#maemo-ssu NIN101 (~NIN@p5DD28A45.dip0.t-ipconnect.de) |
| 15:45.00 | DocScrutinizer05 | iDont: well, that's a pretty normal basic shell function. However if we can't configure history behaviour in a "convenient" way at runtime, we might want to move *all* history handling to some config scripts like .bashrc .bash-startup whatever the name |
| 15:46.07 | DocScrutinizer05 | after all it's one simple command in startup and one in exit script |
| 15:46.49 | iDont | DocScrutinizer05, sorry, I'm not sure what you're talking about |
| 15:47.05 | DocScrutinizer05 | sorry, I'll try to elaborate |
| 15:47.12 | iDont | thanks :) |
| 15:49.52 | DocScrutinizer05 | history: history [-c] [-d Offset] [n] oder history -anrw [Dateiname] oder history -ps Argument [Argument...] |
| 15:51.00 | iDont | BusyBox doesn't supply `history` at all |
| 15:51.26 | DocScrutinizer05 | WUT? |
| 15:51.42 | iDont | check it ;-) |
| 15:52.13 | DocScrutinizer05 | indeed, so how the fuck we should handle history at all then? |
| 15:52.42 | DocScrutinizer05 | this is so incredibly stupid |
| 15:53.23 | iDont | As user, you only can only manipulate the standard envorinment variables ($HISTFILE et al) |
| 15:53.34 | DocScrutinizer05 | pfff |
| 15:53.57 | iDont | hehe, I didn't say ash is better than bash ;-) |
| 15:54.09 | iDont | it just happens to be the default shell in Maemo |
| 15:54.17 | DocScrutinizer05 | ~messybox |
| 15:54.17 | infobot | messy... err busybox is meant for lean scripting. Regarding all the missing options and immanent limitations (see su, passwd) it's not really the interactive shell of choice. A lot of people hate busybox because a lot of system integrators don't understand the difference between busybox and a decent user interactive shell plus unix utils |
| 15:55.02 | freemangordon | hehe |
| 15:55.22 | DocScrutinizer05 | tr5ying to teach the dog to fly |
| 15:55.33 | iDont | yep. I mainly use busybox-power for its tools. It's really convenient to have a lot of tools always available. If can always install proper tools if BusyBox is lacking. However, that hasn't occured too much for me yet (with busybox-power) |
| 15:55.49 | iDont | s/if/I/ |
| 15:56.01 | iDont | woops |
| 15:56.08 | iDont | we'll, you get what I mean |
| 15:56.16 | iDont | well* |
| 15:56.17 | iDont | damn |
| 15:56.30 | iDont | not my best day |
| 15:57.26 | DocScrutinizer05 | so I don't really care what you do to messybox history handling, unless it changes behaviour for non-interactive |
| 15:58.27 | DocScrutinizer05 | users loving busybox for all the missing stuff may find a way to deal with whatever history handling you come up with. don't expect that to go into cssu fixed busybox-vanilla though |
| 15:59.00 | DocScrutinizer05 | asince I hardly can see any reason to review that patch |
| 15:59.30 | iDont | DocScrutinizer05, I don't think we're on the same page. I'm not planning to change any history related code |
| 16:00.15 | iDont | I suggested changing a compile-time option. |
| 16:00.29 | iDont | And history handling is _always_ turned off for non-interactive shells (unless your script starts with #!/bin/sh -i, which it really shouldn't), so you don't have to worry about the subject at all |
| 16:00.55 | iDont | sorry if a misunderstanding has come from my side |
| 16:01.31 | DocScrutinizer05 | we're worrying about *any* patches going into cssu busybox vanilla |
| 16:02.03 | DocScrutinizer05 | since any patch comes with risk, and usually with added payload for rootfs |
| 16:02.57 | DocScrutinizer05 | your "portrait" patch was pretty minimalistc, so no probelm to review it, and no impact to size |
| 16:03.19 | iDont | DocScrutinizer05, the portain patch was from Pali, not me ;-) |
| 16:03.30 | DocScrutinizer05 | (though I have to admit I don't get what it actually does) |
| 16:04.00 | freemangordon | hmm, do I get it right, upstream bb handles history differently from stock? |
| 16:04.23 | freemangordon | *stock maemo |
| 16:04.25 | DocScrutinizer05 | seems so |
| 16:04.34 | freemangordon | in what way? |
| 16:05.49 | iDont | Nokia patched in an own method to save history, but it was broken. Upstream BusyBox provides two different ways of saving shell history, configurable via a compile-time option |
| 16:06.17 | freemangordon | aah,ok. DocScrutinizer05: what is the problem with that? |
| 16:06.49 | DocScrutinizer05 | no problem, just asking why we need that in busybox vanilla |
| 16:07.37 | iDont | Well, you don't want to patch in Nokia's broken method in upstream, do you? |
| 16:07.43 | DocScrutinizer05 | and also asking if that assumtion it's been buggy Nokia implementation is any quotable, e.g ticker on bugtracker where Nokia admits there's a bug and not a feature we didn't understand |
| 16:07.54 | freemangordon | hehe |
| 16:08.18 | DocScrutinizer05 | s/ticker/ticket/ |
| 16:08.24 | freemangordon | iDont: what is broken? history being overwritten by the last interactive shell? |
| 16:09.02 | freemangordon | iDont: sorry if you already answered |
| 16:09.41 | iDont | one sec |
| 16:09.47 | DocScrutinizer05 | afk now, finally getting my end-of-day / /end-of-week / end-of-contract / end-of-work drink |
| 16:10.15 | merlin1991 | DocScrutinizer05: aren't you on a new contract like tomorrowß |
| 16:10.21 | DocScrutinizer05 | ping me if there's a proper cssu meeting later (it's Friday after all) |
| 16:10.22 | merlin1991 | s/ß/?/ |
| 16:10.29 | DocScrutinizer05 | nope |
| 16:11.11 | freemangordon | well, chem|st is missing, merlin1991 is away and with bad inet, I don't think there will be a meeting today ;) |
| 16:11.40 | DocScrutinizer05 | good :-D |
| 16:12.06 | freemangordon | merlin1991: may I ask you to do me a favor? |
| 16:12.18 | merlin1991 | depends on the favour ;) |
| 16:12.48 | freemangordon | there was a conversation regarding licensing of VKB RE stuff and I promised to change the license |
| 16:13.09 | merlin1991 | and I gotta do what? |
| 16:13.33 | merlin1991 | rm -rf / on my server? :D |
| 16:13.34 | freemangordon | for the life of mine I cannot think of what that "(C) Nokia" license should contain |
| 16:14.04 | freemangordon | no, invent some license and replace LGPL wherever applicable |
| 16:14.20 | iDont | DocScrutinizer05, I can point out the flaw in Nokia's shell-hist.patch |
| 16:14.26 | ivgalvez | freemangordon hi |
| 16:14.32 | freemangordon | ivgalvez: hi |
| 16:14.52 | ivgalvez | what's the original license or eula file in Nokia's package |
| 16:14.54 | ivgalvez | ? |
| 16:15.02 | *** join/#maemo-ssu MrPingu (~chatzilla@86.92.226.97) |
| 16:15.04 | freemangordon | there is no ;) |
| 16:15.10 | ivgalvez | you just need to keep that file |
| 16:15.12 | ivgalvez | doh! |
| 16:15.41 | ivgalvez | OK, then use this: http://tablets-dev.nokia.com/eula/index.php |
| 16:15.50 | ivgalvez | and add a notice file |
| 16:15.54 | iDont | freemangordon, back to you. Were you talking about Maemo's busybox, upstream BusyBox, or busybox-power :-P? |
| 16:15.58 | iDont | in your question |
| 16:16.05 | ivgalvez | saying what we already tlked last day |
| 16:16.37 | freemangordon | ivgalvez: not applicable, I used binaries from SB :P |
| 16:17.01 | freemangordon | iDont: just a minute, I want to finish with that license once and for all :) |
| 16:17.06 | iDont | k |
| 16:17.14 | ivgalvez | Actually, qgil commented yesterday by email that Nokia EULA and already exiisting declarations on TMO are covering fair use |
| 16:17.18 | ivgalvez | for Nokia devices |
| 16:17.55 | DocScrutinizer05 | ivgalvez: ++ and thanks! |
| 16:18.42 | ivgalvez | I have insisted about it and he answered that it's absolutely clear that we can use Nokia copyright for Open Source projects on Nokia devices |
| 16:19.23 | ivgalvez | qgil: "There won't be anything more official than what has been written and |
| 16:19.23 | ivgalvez | explained in the forum. The Nokia EULA is official and it doesn't make |
| 16:19.23 | ivgalvez | any sense to have an official message contradicting the EULA. Please |
| 16:19.23 | ivgalvez | keep playing nice and there won't be any problem." |
| 16:19.44 | ivgalvez | so don't try to install Maemo in $DEVICE |
| 16:20.10 | DocScrutinizer05 | "this file may contain parts derived from disassembly of binaries unde Nokia's copyright (see http://tablets-dev.nokia.com/eula/index.php). The original licencing conditions apply to to all those derived parts as well and you accept those by using this file" |
| 16:20.16 | DocScrutinizer05 | sth like that will do |
| 16:20.28 | ivgalvez | perfect |
| 16:20.52 | ivgalvez | so now we need to contact Adobe ;) |
| 16:21.28 | DocScrutinizer05 | SSSHHH! |
| 16:21.43 | DocScrutinizer05 | ;-) |
| 16:22.57 | freemangordon | hmm, I like that, thanks, going to update the sources |
| 16:23.13 | ivgalvez | no probs |
| 16:23.13 | DocScrutinizer05 | please fix my spelling ;-) |
| 16:23.14 | kerio | "hey adobe, we're gonna ship your latest flash player on maemo kthxbye" |
| 16:23.21 | freemangordon | hehe |
| 16:23.41 | merlin1991 | kerio: the important part is the kthxbye :D |
| 16:26.07 | ivgalvez | merlin1991 I hope somehow you will be able to actually administrate the repos during next week |
| 16:26.45 | ivgalvez | I have a big list of applications to promote form Testing-Squad list ;) |
| 16:26.46 | DocScrutinizer05 | sips on his nice cold drink |
| 16:27.49 | merlin1991 | ivgalvez: as soon as I can actually do stuff I'll be happy todo so :) |
| 16:28.25 | DocScrutinizer05 | kerio: (latest flash player) do we actually *want* to do that? would we even be able to find something worth it? |
| 16:28.44 | kerio | eeh, you're probably right |
| 16:28.51 | kerio | most porn sites work fine with flash 9 |
| 16:28.52 | DocScrutinizer05 | merlin1991: how's your vacations? |
| 16:29.06 | freemangordon | /** |
| 16:29.08 | freemangordon | @file hildon-im-vkbrenderer3.c |
| 16:29.10 | freemangordon | This file is part of libhildon-im-vkbrenderer3. |
| 16:29.12 | freemangordon | Тhis file may contain parts derived from disassembly of binaries under Nokia's copyright, |
| 16:29.14 | freemangordon | see http://tablets-dev.nokia.com/maemo-dev-env-downloads.php. |
| 16:29.16 | freemangordon | The original licencing conditions apply to all those derived parts as well |
| 16:29.19 | freemangordon | and you accept those by using this file. |
| 16:29.21 | freemangordon | */ |
| 16:29.22 | kerio | *licensing |
| 16:29.23 | freemangordon | ok? |
| 16:29.29 | freemangordon | thanks |
| 16:29.33 | DocScrutinizer05 | OK |
| 16:29.35 | kerio | also, maybe "the disassembly"? |
| 16:29.35 | merlin1991 | DocScrutinizer05: perfect, only tomorrow is the last day :/ |
| 16:29.37 | ivgalvez | great |
| 16:29.46 | kerio | is not a native english speaker |
| 16:30.04 | freemangordon | too |
| 16:30.10 | ivgalvez | merlin1991 did you actually do anything apart from going to the beach? |
| 16:30.12 | DocScrutinizer05 | derived by disassembling... |
| 16:30.17 | DocScrutinizer05 | -of |
| 16:31.10 | DocScrutinizer05 | merlin1991: so enjoy it to the last minute |
| 16:31.27 | DocScrutinizer05 | maemo madness waiting for you, you know ;-) |
| 16:31.58 | merlin1991 | ivgalvez: been to ronda and gibraltar |
| 16:32.05 | DocScrutinizer05 | \o/ |
| 16:32.09 | ivgalvez | nice |
| 16:32.11 | merlin1991 | and then ofc lots of beach and booze :) |
| 16:32.15 | DocScrutinizer05 | both nice places I've been as well |
| 16:32.48 | DocScrutinizer05 | merlin1991: don't miss to visit cabo trafalgar / los canos de mecca |
| 16:33.09 | ivgalvez | Caños de Meca |
| 16:33.17 | DocScrutinizer05 | some 50(?) km from Gibraltar up the atlantic coast |
| 16:33.30 | DocScrutinizer05 | ivgalvez: indeed |
| 16:33.38 | freemangordon | I suppose I can have different licensing for .c/.h, as I want headers LGPL licensed |
| 16:33.50 | freemangordon | ? |
| 16:33.52 | DocScrutinizer05 | probably, yes |
| 16:34.11 | freemangordon | what about package (C)? |
| 16:34.12 | ivgalvez | perfectly possible, just add the license notice in each header file |
| 16:34.28 | DocScrutinizer05 | as long as the .h don't include stuff too obviously basing on disassembly |
| 16:34.58 | DocScrutinizer05 | package (C) always the most restrictive option of all available |
| 16:34.59 | freemangordon | well, function names, but nothing like v21 |
| 16:35.01 | ivgalvez | the package contains Nokia stuff so it has to keep Nokia copyright |
| 16:35.06 | freemangordon | ok |
| 16:35.22 | ivgalvez | and is not redistributable out of Nokia devices |
| 16:35.36 | DocScrutinizer05 | freemangordon: function names are free ;-) |
| 16:35.44 | DocScrutinizer05 | var names as well |
| 16:36.28 | DocScrutinizer05 | yeah, beefeater kicks ass |
| 16:36.32 | DocScrutinizer05 | :-D |
| 16:36.45 | merlin1991 | how does that fit? :D |
| 16:36.51 | merlin1991 | half a day spent on irc in spain, time to get out again xD |
| 16:37.05 | DocScrutinizer05 | not at all, to the topic. Pretty good, to my mood |
| 16:37.15 | merlin1991 | hehe |
| 16:37.23 | merlin1991 | though tbh beefeater is not that good gin |
| 16:37.40 | DocScrutinizer05 | good enough for longdrinks |
| 16:38.01 | DocScrutinizer05 | (they had no Gordon's @ Karstadt :-o ) |
| 16:38.06 | merlin1991 | anyway I'll go and find me some longdrink, probably back on sunday |
| 16:38.26 | DocScrutinizer05 | cya, enjoy yourself! |
| 16:39.15 | iDont | have a good one, merlin1991! |
| 16:44.14 | freemangordon | http://pastebin.com/XkyaJBh2 |
| 16:44.16 | freemangordon | ok? |
| 16:45.57 | freemangordon | DocScrutinizer05 ^^^ |
| 16:56.31 | DocScrutinizer05 | freemangordon: seems ok |
| 16:57.41 | DocScrutinizer05 | somebody will rise concerns that there are two conflicting licences, but I'm not one of them, since I think it's clear that the second more restrictive one overrides the GPL where applicable |
| 16:57.53 | DocScrutinizer05 | (sorry for delay) |
| 17:01.15 | freemangordon | yep, fixed it |
| 17:01.15 | freemangordon | https://gitorious.org/community-ssu/hildon-im-vkbrenderer3/blobs/63e2f77d158f74d809264187e93c4d8b54d59545/debian/copyright |
| 17:01.31 | freemangordon | DocScrutinizer05: ^^^ |
| 17:02.47 | DocScrutinizer05 | freemangordon: perfect |
| 17:05.02 | freemangordon | will change the other package too, but tomorrow :) |
| 17:05.09 | DocScrutinizer05 | swallows some bitter comment about este^H^H and prepares another drink |
| 17:06.50 | freemangordon | iDont: I was asking what is broken in stock bb |
| 17:10.54 | DocScrutinizer05 | yumyumyum http://www.cocktailscout.de/cocktail_Gr__ne_Wiese_rezept_149.html |
| 17:11.31 | DocScrutinizer05 | actually baeh! |
| 17:11.46 | DocScrutinizer05 | missing the proper huge dash of gin |
| 17:13.44 | iDont | freemangordon: if you have multiple instances of ash open, only the command history of the last closed shell will be saved. All commands typed in other instances will be lost |
| 17:13.52 | DocScrutinizer05 | haha http://www.cocktaildatenbank.de/cocktail-rezepte/801-gruene-wiese |
| 17:14.29 | freemangordon | iDont: ok |
| 17:14.47 | freemangordon | and what is upstream doing? |
| 17:16.07 | freemangordon | iDont: TBH there is lots of stuff that can be stripped from bb-p, rpm and rpm2cpio for example :) |
| 17:16.08 | iDont | By default, it appends each command to the history file. All instances of ash does this, so you'll get interleaving commands from different ash instances |
| 17:16.17 | freemangordon | ok |
| 17:16.22 | freemangordon | sounds ggod |
| 17:16.27 | freemangordon | good even |
| 17:16.32 | iDont | if you set ENABLE_FEATURE_EDITING_SAVE_ON_EXIT at compile time, it will append its history to the histfile on shell closure |
| 17:17.18 | freemangordon | which is close to stock behaviour, ain't? |
| 17:17.47 | freemangordon | iDont: what httpd in busybox do? |
| 17:17.49 | DocScrutinizer05 | yeah sonds pretty convenient |
| 17:18.07 | iDont | Yes, and that's what we have turned on in busybox-power (to save wear on the eMMC). However, if ash is closed unnicely (for the lack of a better term), the history file can get garbled |
| 17:18.13 | iDont | that's still a bug that puzzles me |
| 17:18.52 | DocScrutinizer05 | iDont: don't worry about eMMc wear! |
| 17:19.03 | kerio | freemangordon: make an educated guess |
| 17:19.09 | DocScrutinizer05 | ...since your EE colleagues already did ;-) |
| 17:19.17 | freemangordon | yeah, that won't get flushed until needed |
| 17:19.30 | iDont | :-D great! |
| 17:20.05 | iDont | then there is no issue wrt history handling at all anymore |
| 17:20.07 | DocScrutinizer05 | you get buffering on any (laso eMMC) writes to storage anyway |
| 17:20.17 | DocScrutinizer05 | so "don't worry, be happy!" |
| 17:20.29 | kerio | is there a way to enable something similar to TRIM for the eMMC? |
| 17:20.56 | DocScrutinizer05 | *burp* |
| 17:21.02 | DocScrutinizer05 | sync:sync |
| 17:21.08 | DocScrutinizer05 | ; |
| 17:21.16 | kerio | ...no |
| 17:21.18 | iDont | freemangordon, httpd is a complete webserver implementation in busybox ;-) |
| 17:21.19 | kerio | that's nt TRIM |
| 17:21.26 | freemangordon | iDont: I think you should be able to move httpd, rpm stuff, sendmail, etc to /opt and get rid of acpid and such |
| 17:21.28 | iDont | freemangordon, although a tiny one |
| 17:21.30 | DocScrutinizer05 | there's no TRIM on mmc |
| 17:21.33 | kerio | shame |
| 17:21.46 | iDont | freemangordon, yes, and probably more as well |
| 17:21.52 | freemangordon | yep |
| 17:22.13 | DocScrutinizer05 | TRIM is pretty lowlevel |
| 17:22.26 | DocScrutinizer05 | eMMC controller doesn't have API for that |
| 17:22.31 | freemangordon | and you will fit in those 100-150 k limit, witout risk to break someone's early boot script |
| 17:22.50 | iDont | everyone's happy :-) |
| 17:22.54 | freemangordon | yep :) |
| 17:23.02 | DocScrutinizer05 | without risk to break somebody's heart ;-D |
| 17:23.14 | freemangordon | mission accomplished |
| 17:24.15 | DocScrutinizer05 | wonders if it's his nature to play the bastard, or it's just some users who don't get the whole picture make him feel like that |
| 17:24.15 | iDont | I'm very glad we finally got something productive going regarding busybox and CSSU. Last week hasn't been really fun for anyone I guess |
| 17:24.33 | DocScrutinizer05 | actually I'm also striving for the best of maemo |
| 17:24.53 | iDont | DocScrutinizer05, I think nobody would deny that |
| 17:25.02 | DocScrutinizer05 | but I get mad on somebody forecefeeding anything to somebody else |
| 17:25.47 | freemangordon | iDont: well, it is up to you then. Though my proposal is to clone bb as it is now(on gitorious), forward the source to upstream, make the needed changes and request a merge |
| 17:26.21 | freemangordon | that way we can make a review of what are the actual changes in the source code |
| 17:26.31 | DocScrutinizer05 | iDont: I concur with last (2) week(s) nobody felt happy (except maybe estel for his successful trolling) |
| 17:27.06 | freemangordon | iDont: is that sound sane? |
| 17:27.07 | DocScrutinizer05 | nah, that's been mean |
| 17:27.17 | freemangordon | DocScrutinizer05: why? |
| 17:27.19 | DocScrutinizer05 | I think even estel wants the best for maemo |
| 17:27.28 | freemangordon | aah, ok |
| 17:27.34 | freemangordon | you are still on estel :P |
| 17:27.41 | DocScrutinizer05 | he just has poor diplomatical skills |
| 17:27.54 | iDont | freemangordon, yes, sounds good. However, there are a _lot_ of commits between BusyBox 1.10 and 1.20 |
| 17:28.38 | DocScrutinizer05 | freemangordon: yeah, that tears me down more than you might expect |
| 17:29.03 | freemangordon | iDont: btw by saying "upstream" do you mean "debian" or some git repo? |
| 17:29.05 | DocScrutinizer05 | I just don't get it how he's such a douchebag and always bitching at me |
| 17:29.46 | iDont | I mean the latest stable tagged busybox release by upstream |
| 17:29.49 | kerio | DocScrutinizer05: what do you mean you don't get it? |
| 17:29.51 | kerio | it's easy |
| 17:29.57 | kerio | DocScrutinizer05: it's your fault the freerunner sucked! |
| 17:30.05 | kerio | see? |
| 17:30.06 | DocScrutinizer05 | after all he seems the only one thinking I got time to spare just to annoy him |
| 17:30.24 | freemangordon | guys, lets finish with bb, please |
| 17:30.36 | kerio | and let's move to cbsms |
| 17:30.49 | DocScrutinizer05 | kerio: indeed, I should've jumped in more early, with much more verve, to save the project |
| 17:30.59 | kerio | wait, really? |
| 17:31.03 | kerio | so it *was* your fault! :O |
| 17:31.12 | iDont | @freemangordon <iDont> I mean the latest stable tagged busybox release by upstream |
| 17:31.40 | freemangordon | kerio: https://gitorious.org/community-ssu/operator-name-cbs-widget/commit/5d30fedb5ebea226d9ccfe9ac8453bfe9acb02c4/diffs/9c19e807f04312b1e5d71d4283f4aa55bd152f0f |
| 17:31.52 | freemangordon | now, lets go back to bb |
| 17:32.05 | kerio | wtf is that |
| 17:32.39 | DocScrutinizer05 | kerio: lol for cbsms |
| 17:32.40 | freemangordon | iDont: well, then you should be able to simply rebase (after removing nokia patches) |
| 17:32.47 | DocScrutinizer05 | good topic change |
| 17:32.52 | kerio | DocScrutinizer05: don't lol, that's your fault too! |
| 17:32.58 | DocScrutinizer05 | yes!!!! |
| 17:33.10 | DocScrutinizer05 | I take all the blame for it |
| 17:33.30 | DocScrutinizer05 | I however won't accept it as an excuse to continue like that |
| 17:33.44 | iDont | freemangordon, yes, that's what I'll do. I had a little misunderstanding ;-) |
| 17:33.53 | kerio | i don't want to use it as an excuse to continue like that, i want it out of my cssu :C |
| 17:34.07 | kerio | or fixed |
| 17:34.11 | DocScrutinizer05 | after all, if we don't learn from our mistakes, we're real fools |
| 17:34.29 | kerio | by the way, the dpkg divert it uses is a massive kludge |
| 17:34.30 | freemangordon | kerio: hmm, where is your CSSU, I want to try it. |
| 17:34.43 | kerio | and whoever thought of that should be shot in the back |
| 17:34.54 | kerio | or maybe lightly mocked |
| 17:35.01 | kerio | one of those two |
| 17:35.19 | freemangordon | kerio: wasn't trolling so far enough? |
| 17:35.38 | kerio | if you want to do a proper one of those, do the same as the future busybox-power - provide and conflict with connui-home-cellular |
| 17:36.08 | DocScrutinizer05 | kerio: (out of cssu or ficed) I'm all with you regarding that |
| 17:36.40 | DocScrutinizer05 | kerio: and I promise it won't make it to cssu-s in this condition it's now |
| 17:37.32 | DocScrutinizer05 | kerio: THAT is what cssu-t is all about. Get packages you *think* are already withput problems, then learn if they actually are |
| 17:38.01 | DocScrutinizer05 | but it's no excuse to act sloppy on prior evaluation of possible problems to anticipate |
| 17:38.40 | DocScrutinizer05 | I failed on anticipating the problems we see with cbsms |
| 17:38.51 | DocScrutinizer05 | and I take the blame for that |
| 17:39.05 | kerio | besides... |
| 17:39.14 | kerio | can't it be enabled on-demand? |
| 17:39.29 | DocScrutinizer05 | I however *won't* take any accusations for trying to avoid same mistake in the future |
| 17:40.39 | kerio | it's ok, i still love you <3 |
| 17:42.13 | DocScrutinizer05 | and I probably hire ninjas if some estel comes again stating I don't contribute so his valuable experience is way more relevant than anything I say |
| 17:43.02 | DocScrutinizer05 | after all for *what* he ever took responsibility? |
| 17:44.16 | DocScrutinizer05 | what has been his invaluable contribution to maemo at large, except some pretty poorly written shellscript 10-liners that *we* tought him char by char |
| 17:45.03 | DocScrutinizer05 | and yet they were like WTF-of-the-week |
| 17:45.19 | DocScrutinizer05 | since he didn't listen and learn |
| 17:45.39 | DocScrutinizer05 | meh , could somebody kick me please? |
| 17:45.55 | kerio | kicks DocScrutinizer05 on the shins |
| 17:46.04 | DocScrutinizer05 | thanks |
| 17:46.07 | iDont | freemangordon, is there anything else to discuss regarding busybox? I'll make sure to do what you suggested, although I can't promise that it'll be completely done first thing tomorrow ;) |
| 17:46.36 | DocScrutinizer05 | iDont: nobody expexts that, so relax |
| 17:46.51 | iDont | :-) |
| 17:47.19 | iDont | Otherwise I'll call it a day, got some plans for tonight (Friday!) |
| 17:47.25 | DocScrutinizer05 | iDont: after all, we don't even have a pressing bug ticket against the whole thing |
| 17:48.01 | DocScrutinizer05 | iDont: so I suggest you get a life, something I should finally try to do as well :-d |
| 17:48.05 | DocScrutinizer05 | :-D |
| 17:48.51 | iDont | hehe, true. Busybox-power in its current state does however fix quite a few maemo bugs (/feature requests) |
| 17:49.37 | DocScrutinizer05 | maybe, but how many users of N900 will not sleep due to thise bugs tonight? |
| 17:50.07 | DocScrutinizer05 | cssu is about the comfy feeling that you don't have to worry |
| 17:50.22 | DocScrutinizer05 | since there are other guys doing that for you |
| 17:51.01 | iDont | well, if they really can't sleep, they can alway apt-get install busybox-power! |
| 17:51.10 | DocScrutinizer05 | if you wanna go bleeding edge or as 1337 as it gets, there are other ways you can do |
| 17:51.20 | iDont | regarding CSSU, who doesn't have that installed ;p |
| 17:51.23 | DocScrutinizer05 | yes, exactly |
| 17:53.25 | DocScrutinizer05 | cssu is first and foremost about bringing security fixes to users. 2nd about fixing long pending annoyances everybody suffers from, like e.g. portait (not a good example) or cpu-hog-bug in hildon-desktop (much better example) |
| 17:54.19 | DocScrutinizer05 | cssu is _not_ about "leading your people to the promised land" (like in holy bible) though |
| 17:54.46 | iDont | yup, I get what you're saying |
| 17:55.36 | DocScrutinizer05 | fine, probably I should take own advice and continue my ethanol intoxication enterprise somewhere else |
| 17:55.58 | DocScrutinizer05 | ~seen estel_ |
| 17:56.04 | infobot | estel_ <~Estel@Maemo/Community/council/Estel-> was last seen on IRC in channel #maemo, 6h 25m 16s ago, saying: 'happy trolling, i'm out.'. |
| 17:56.11 | iDont | hehe |
| 17:56.14 | DocScrutinizer05 | byebye |
| 17:56.25 | iDont | I'm calling it a day as well. Everyone have a good one tonight! Bye! |
| 17:56.42 | DocScrutinizer05 | iDont: thanks for participating |
| 17:56.50 | DocScrutinizer05 | any enjoy your time |
| 17:57.20 | *** join/#maemo-ssu ivgalvez (~quassel@41.pool85-49-220.dynamic.orange.es) |
| 17:59.04 | DocScrutinizer05 | <kerio> can't it be enabled on-demand? #### sure it should be optional |
| 17:59.36 | DocScrutinizer05 | and we already agreed on it going cssu-extras |
| 18:00.01 | DocScrutinizer05 | minus the lib patch which is core system but for now seems to be safe |
| 18:00.46 | DocScrutinizer05 | yay, newsflashes |
| 18:00.52 | DocScrutinizer05 | o/ |
| 18:04.36 | *** join/#maemo-ssu ShadowJK (~jk@terminus.enivax.net) |
| 18:25.37 | *** join/#maemo-ssu ShadowJK (~jk@terminus.enivax.net) |
| 18:34.51 | *** join/#maemo-ssu javispedro (~javier@Maemo/community/contributor/javispedro) |
| 18:35.58 | *** join/#maemo-ssu nox-- (noident@p57900C13.dip.t-dialin.net) |
| 18:36.35 | *** join/#maemo-ssu nox-- (noident@p57900C13.dip.t-dialin.net) |
| 18:46.48 | *** join/#maemo-ssu ShadowJK (~jk@terminus.enivax.net) |
| 18:53.09 | *** join/#maemo-ssu arcean (~arcean@aael108.neoplus.adsl.tpnet.pl) |
| 18:55.00 | *** join/#maemo-ssu ShadowJK (jk@terminus.enivax.net) |
| 18:59.04 | *** join/#maemo-ssu arcean (~arcean@aael108.neoplus.adsl.tpnet.pl) |
| 19:09.02 | *** join/#maemo-ssu arcean (~arcean@aael108.neoplus.adsl.tpnet.pl) |
| 19:26.54 | *** join/#maemo-ssu ShadowJK (jk@terminus.enivax.net) |
| 20:04.13 | gregoa | kerio: cbs-widget: pali has pushed some fixes yesterday, and I've built packages for myself. so far they look good, at least the operator name doesn't vanish when I switch between 2G and 3G. if you want to try: wget http://info.comodo.priv.at/tmp/connui-home-cellular_3.1+nmu1_armel.deb ; wget http://info.comodo.priv.at/tmp/operator-name-cbs-widget_3.1+nmu1_armel.deb |
| 20:07.50 | kerio | gregoa: yay ^_^ |
| 20:07.54 | kerio | i'll try those |
| 20:08.22 | kerio | DocScrutinizer05: i actually meant keeping both the stock one and the cb one saved, and loading one or the other depending on whether the user enables something in Settings |
| 20:08.25 | gregoa | kerio: let's hope they fix your problems too |
| 20:08.44 | kerio | gregoa: btw, one of those two packages is a fake |
| 20:08.49 | kerio | just fyi :) |
| 20:09.16 | gregoa | I know I know |
| 20:12.42 | kerio | sadly, the *wrong* package is a fake |
| 20:23.11 | kerio | gregoa: i'll have to test it for a couple of days i think |
| 20:23.45 | kerio | gregoa: not sure about you, but i don't always get the problem |
| 20:23.48 | gregoa | nods |
| 20:23.53 | kerio | once i do, though, it stays there until i reboot |
| 20:24.22 | kerio | besides, i think it also depends on the cell i'm connected to |
| 20:24.31 | kerio | which makes the problem... "fun" to diagnose, i suppose |
| 20:24.53 | gregoa | with the latest version I could reproduce the "no op name" reliably by switching between 2G and 3G, and this effect is gone now at least |
| 20:25.27 | gregoa | btw, "killall hildon-home" seems to be enough for reviving it |
| 20:25.35 | kerio | it's always temporary for me |
| 20:25.45 | kerio | like, after i switch i get the wrong name/no name again |
| 20:26.17 | kerio | anyway, i suppose i can just leave operator-name-cbs-widget installed as a fake package |
| 20:26.25 | kerio | and reinstall the stock connui-home-cellular |
| 20:26.26 | kerio | :D |
| 20:30.58 | DocScrutinizer05 | CHEEERS |
| 20:31.59 | DocScrutinizer05 | beefeater is quite nice, when dilluted in orrange juice |
| 20:32.30 | DocScrutinizer05 | -l |
| 20:32.37 | DocScrutinizer05 | -r |
| 20:32.38 | DocScrutinizer05 | meh |
| 20:32.48 | *** join/#maemo-ssu arcean (~arcean@aael108.neoplus.adsl.tpnet.pl) |
| 20:33.16 | DocScrutinizer05 | friggin paperwork all over the world |
| 20:33.41 | DocScrutinizer05 | CV! >:-( |
| 20:33.46 | DocScrutinizer05 | shoots the C |
| 20:33.53 | DocScrutinizer05 | and the V separately |
| 20:34.44 | DocScrutinizer05 | since when a CV ever told something really relevant about he person in question |
| 20:37.18 | DocScrutinizer05 | I always hired my teams without any fancy CV, just on the merit they exposed to me |
| 20:38.05 | DocScrutinizer05 | competence, commitment, and character |
| 20:39.49 | DocScrutinizer05 | 5 minutes of talk already tell you more than any friggin CV |
| 20:40.21 | DocScrutinizer05 | 5 min of chat will do almost as well |
| 23:54.04 | *** join/#maemo-ssu LaoLang_cool (~LaoLang_c@221.226.175.139) |
| 23:54.27 | *** join/#maemo-ssu jonwil (~jonwil@27-33-137-199.static.tpgi.com.au) |
