freemangordon | uvos: re locales: Nokia managed to avoid building on device, by pre-building on image-builder | 07:43 |
---|---|---|
freemangordon | umm, in auto-builder, not image-builder | 07:43 |
freemangordon | perhaps we can create a package that contains pre-build locales and tracks libc6 | 07:44 |
freemangordon | or, we can just not enable anything but en_GB on the image, and provide an UI for user to add more locales as she wants | 07:59 |
sicelo | i think en_US would be better than en_GB, or at least both then. many locales inherit from en_US afaik | 11:28 |
Wizzup | freemangordon: debian rebuilds them upon libc upgrade only | 11:43 |
Wizzup | so when people flash an image they don't run into rebuilding issues | 11:43 |
tmlind | Wizzup: nice if you got m-l image in works for mz617 :) have not seen the atmel_mxt_ts issue, then again i've mostly used it without a gui so far | 12:55 |
Wizzup | yeah it works quite smooth :) | 13:01 |
inky | important lagrange update: gemini://bbs.geminispace.org/s/Lagrange/13969 - i need to make an update. | 13:06 |
Wizzup | inky: check | 13:30 |
inky | check what? i am building it on device now to test, then will try in phoenix. | 13:31 |
Wizzup | inky: as in confirm | 13:33 |
Wizzup | as in ok | 13:33 |
Wizzup | :) | 13:33 |
freemangordon | Wizzup: yes, but on libc upgrade, it takes ages | 15:27 |
Wizzup | yup | 15:28 |
Wizzup | like I said, just edit /etc/locale.gen | 15:28 |
Wizzup | I am not sure if we need a UI for that now | 15:28 |
freemangordon | but, we can do it on the opposite - enable only en_GB in /etc.locale.gen by default | 15:29 |
Wizzup | I would do en_US like sicelo said, but yes | 15:29 |
Wizzup | this is easy and I think the image builder or leste-config does this | 15:30 |
freemangordon | and then "just edit /etc/locale.gen" | 15:30 |
freemangordon | yes | 15:30 |
freemangordon | why US? | 15:30 |
Wizzup | # TODO: Do this through a package when we have a language-changing package | 15:30 |
Wizzup | # Generate locales | 15:30 |
Wizzup | apt-cache search hildon-common-strings-l10n \ | grep -v mr0 \ | awk -F'[()]' '{printf "%s.UTF-8 UTF-8\n", \$2}' \ >> /etc/locale.gen | 15:30 |
Wizzup | locale-gen | 15:30 |
Wizzup | https://github.com/maemo-leste/image-builder/blob/master/chimaera.blend#L115 | 15:30 |
Wizzup | freemangordon: that's the default on basically all systems | 15:31 |
Wizzup | we also set it as default as you can see in the chimaera.blend file | 15:31 |
freemangordon | not on fremantle though | 15:31 |
Wizzup | https://github.com/maemo-leste/image-builder/blob/master/chimaera.blend#L26 just noticed this typo | 15:32 |
Wizzup | freemangordon: I don't think fremantle ever regenerated them | 15:32 |
Wizzup | in any case I really don't care enough about the default locale, if you want it to be en_GB that is fine but then please deal with fallout if any | 15:32 |
Wizzup | so how do we manage locale.gen going forward? it needs to be through some package | 15:35 |
Wizzup | uvos: later tonight and/or tomorrow I will bring two droids to my desk, one with leste on it and one with android, hopefully you can help me figure out what might cause the instability | 15:52 |
bencoh | Wizzup: I don't think forcing too many locales to the user is a good idea, because regenerating it takes a lot of time on aging platforms | 16:14 |
Wizzup | yes, we're in agreement I think | 16:14 |
bencoh | ah okay | 16:14 |
Wizzup | right now we're generating /all/ of them | 16:14 |
Wizzup | the question is, how does the user control which ones he/she wants | 16:14 |
bencoh | oh, I see | 16:14 |
bencoh | yeah, that's the question indeed | 16:14 |
Wizzup | right now I think the only ones visible in the settings UI are the *generated* ones | 16:14 |
Wizzup | so we can just tell people 'sudo vi /etc/locale.gen && locale-gen' | 16:15 |
Wizzup | I'm fine with that | 16:15 |
Wizzup | but then some pkg should 'own' locale.gen, or otherwise we can't bring it as an update, but that then means that user choices could be reverted by upgrades, etc | 16:15 |
Wizzup | could be some hacky one-shot postinst script I suppose | 16:15 |
uvos | please use en_US as the default locale | 16:26 |
uvos | idk about gb but de_DE causes alot of stupid bugs in dumb scripts, i dont think it makes sense to rock the boat just because fremantle | 16:27 |
uvos | en_US is simply the universal default, and everthing that is unintentioally broken on other locales works in en_US | 16:28 |
uvos | Wizzup: btw yes cpufreq works again in 6.6 after depmod | 16:33 |
uvos | so was just that | 16:34 |
Wizzup | cool | 16:34 |
uvos | wait no | 16:34 |
uvos | i just booted the wrong thing :D | 16:34 |
uvos | nvm | 16:34 |
Wizzup | how do you test? | 16:34 |
uvos | cat /sys/bus/cpu/devices/cpu0/cpufreq/ is missing | 16:34 |
freemangordon | in our localisation packages, en_GB is the base locale | 16:35 |
freemangordon | so that makes it the default | 16:36 |
freemangordon | everything else is based on en_GB | 16:36 |
Wizzup | uvos: # CONFIG_ARM_OMAP2PLUS_CPUFREQ is not set | 16:36 |
Wizzup | is that a problem? | 16:36 |
freemangordon | heh | 16:36 |
freemangordon | that might explain cpufreq not being loaded | 16:37 |
Wizzup | there is also | 16:37 |
Wizzup | # CONFIG_PM_DEVFREQ is not set | 16:37 |
sicelo | freemangordon: ok. i think having both is fine then :-) | 16:37 |
freemangordon | why? | 16:37 |
freemangordon | why exactly you need en_US? | 16:37 |
freemangordon | for non-maemo packages? | 16:37 |
Wizzup | the world runs on en_US, it's the default everywhere, and I don't think it will negatively affect maemo | 16:38 |
Wizzup | it's also mostly a non-issue I think, which is why I don't care :D | 16:38 |
Wizzup | in fact, as stated before, it is -currently- the default on maemo leste | 16:38 |
freemangordon | "freemangordon: in our localisation packages, en_GB is the base locale" | 16:39 |
uvos | Wizzup: yeah thats wierd but here is 6.1 # CONFIG_ARM_OMAP2PLUS_CPUFREQ is not se | 16:39 |
uvos | so this dident change | 16:39 |
Wizzup | freemangordon: that's fine, but the d4 in your pocket uses en_US and clearly the maemo locales work | 16:39 |
freemangordon | no | 16:39 |
freemangordon | it uses en_GB | 16:39 |
uvos | i dffed the config and its the same between 6.1 and 6.6 | 16:40 |
* freemangordon checks | 16:40 | |
uvos | and its the same besides additions | 16:40 |
Wizzup | uvos: strange | 16:40 |
uvos | ofc one of those could now be required idk | 16:40 |
freemangordon | English (United Kingdom) ;) | 16:40 |
Wizzup | can you share output of 'locale' | 16:40 |
freemangordon | LANG=en_GB.utf-8 | 16:40 |
Wizzup | ok, then you manually changed it | 16:40 |
freemangordon | sure | 16:40 |
Wizzup | mine is English (United States) | 16:41 |
sicelo | mine's en_US too (n900). i can't swear to it, but i'd like to think i never changed it | 16:41 |
Wizzup | I linked the image-builder scripts and it set it to en_US | 16:41 |
freemangordon | Wizzup: the pont is - in every osso- localisation package, the locale every other locales are based on is en_GB | 16:41 |
Wizzup | so no need to check | 16:41 |
uvos | LANG=en_US.utf-8 | 16:41 |
Wizzup | freemangordon: fine then change it and please deal with the fallout if any | 16:42 |
uvos | dident change it besides LC_NUMERIC=de_DE.utf-8 | 16:42 |
Wizzup | I'm sure there will be some funny error messages popping up that aren't quite googleable because they are slightly different | 16:42 |
sicelo | otherwise yes, i also don't think en_GB would adversely affect my usage ... i'm just used to en_US | 16:42 |
Wizzup | I just /really/ don't care about the default locale so I don't want to waste energy on it | 16:42 |
uvos | error: user missing trousers | 16:43 |
* sicelo thinks someday there should be en_SZ :p | 16:43 | |
freemangordon | Wizzup: see, I am trying to understand why the obsession on US | 16:43 |
uvos | because most software is terrible | 16:43 |
Wizzup | freemangordon: no obsession, it's just the default everywhere | 16:43 |
uvos | and since its the default everywhere most terrible software works correctly so | 16:43 |
freemangordon | sicelo: IIRC, default in fremantle is en)GB, fro the reason I stated above | 16:43 |
uvos | :P | 16:43 |
Wizzup | all my machines are also en_US because I don't want coredumps to use a different word that isn't googleable | 16:43 |
uvos | googleablilty is a good point | 16:44 |
freemangordon | ok | 16:44 |
freemangordon | so be | 16:44 |
Wizzup | I checked my fremantle and it is en_GB | 16:44 |
freemangordon | yes | 16:44 |
freemangordon | I know | 16:44 |
Wizzup | I don't know enough how locales work but I think there shouldn't be any problems showing english to the user either way | 16:44 |
Wizzup | (that's a serious question) | 16:44 |
gnarface | dpkg-reconfigure locales? | 16:45 |
uvos | main issue i encourter is locale aware parsers being used in places they should not causing issues | 16:45 |
uvos | bane of ones existance with scientific software/scripts parsing csv files and things | 16:46 |
freemangordon | ok, lets have both US and GB | 16:46 |
Wizzup | gnarface: good point, we didn't consider how debian handles this | 16:46 |
freemangordon | the issue with US as default is that there might be osso- localisation packages that has GB but not US entry | 16:47 |
Wizzup | freemangordon: so the way controlpanel regional plugin works is that it only looks at the generated locales, so then users won't /see/ the other languages | 16:47 |
gnarface | i see a lot of people mangling the settings ala-carte, the dpkg-reconfigure script will at least set all the environment variables right as a set | 16:47 |
freemangordon | Wizzup: yes, I know | 16:47 |
Wizzup | 16:47 < freemangordon> the issue with US as default is that there might be osso- localisation packages that has GB but not US entry | 16:47 |
Wizzup | so that was my question | 16:47 |
Wizzup | I think the en_ prefix just means there is a fallback | 16:47 |
Wizzup | but that is an assumption | 16:47 |
freemangordon | not sure either | 16:47 |
gnarface | i think the pine64 keyboards may also need en_GB-altgr or whatever it's called | 16:47 |
Wizzup | freemangordon: I see maemo text just fine and mine is set to en_US | 16:47 |
Wizzup | so probably it just works | 16:47 |
uvos | worste case it ends up with effectively C as locale or which is also english? | 16:48 |
uvos | not sure | 16:48 |
gnarface | (some of them, anyway) | 16:48 |
freemangordon | no, probably there is no issue wieh US localisation | 16:48 |
Wizzup | I think keyboard layout is independent from localisation | 16:48 |
Wizzup | well at least on a 'locale' leven | 16:48 |
Wizzup | level* | 16:48 |
freemangordon | Wizzup: regarding locales not listed - I think it is very easy to add one more touch selector "add locale" to cpl applet | 16:48 |
gnarface | oh, yes it's "dpkg-reconfigure keyboard-configuration" but you often find you have to set both of these to a coherent set | 16:48 |
freemangordon | I can take on that | 16:49 |
Wizzup | ok | 16:49 |
freemangordon | I just need the full list of locales we want to support | 16:49 |
uvos | gnarface: not on leste as lots of people use droid4s with only us keyboards | 16:49 |
freemangordon | but I can take that from the image | 16:49 |
bencoh | Wizzup: sounds like the regional panel would need an additional 'install languages/locales' panel to modify /etc/locale.gen ? | 16:49 |
gnarface | TBH though my suggestion would just be to make it clear for users how to change both, and not weigh the base install down with lots of them | 16:49 |
gnarface | ... not that i have any horse in this race, just an opinion | 16:50 |
Wizzup | gnarface: yeah I think we're (all) in agreement | 16:51 |
Wizzup | currently the base install has /all/ | 16:51 |
Wizzup | which isn't really an issue until they need to be re-generated or you need to fix leste in a 800MB partition because of locked bootloaders :P | 16:51 |
bencoh | :] | 16:52 |
uvos | thers also the l10n packages | 16:53 |
freemangordon | bencoh: "(17,48,17) freemangordon: Wizzup: regarding locales not listed - I think it is very easy to add one more touch selector "add locale" to cpl applet" | 16:53 |
freemangordon | :) | 16:53 |
bencoh | yeah | 16:54 |
Wizzup | uvos: yes, that would need to be sorted via a meta pkg too | 16:54 |
uvos | its a bit annoying that one is forced to have so many l10n packages installed for languages one dosent speak | 16:54 |
freemangordon | uvos: I think we are in agreement here | 16:54 |
freemangordon | we'll have only GB and US pre-enabled | 16:54 |
freemangordon | and controlpanel UI to add/remove | 16:55 |
Wizzup | what about mountain german | 16:55 |
freemangordon | what about it? | 16:55 |
uvos | i dont speak that | 16:55 |
Wizzup | freemangordon: it was a joke | 16:55 |
freemangordon | I know | 16:55 |
freemangordon | my point was - no issue with it, lets add it as well :p | 16:55 |
Wizzup | there's no austrian locale it looks on leste atm ;) | 16:56 |
freemangordon | Wizzup: but yeah, we need a package | 16:56 |
Wizzup | can you make an issue for this? or maybe two? | 16:56 |
Wizzup | uvos: I'm booting my leste droid3 and also charging the android one | 16:56 |
Wizzup | in case you'd have some time at some point | 16:57 |
freemangordon | they don;t deserve, forcing me waiting hours on the Greek border :p | 16:57 |
freemangordon | Wizzup: no, I'll just implement as soon as I have some spare time | 16:57 |
Wizzup | wait austria doesn't border greece | 16:57 |
Wizzup | freemangordon: cool | 16:57 |
freemangordon | yeah, but they stopped BG from full Schengen | 16:58 |
Wizzup | oh yeah, before that it was just NL for 10 years | 16:58 |
freemangordon | yeah, but NL played it generous just before NY | 16:58 |
freemangordon | it is only Austria stopping us | 16:58 |
freemangordon | well, they allowed air and see | 16:59 |
Wizzup | I'm sure they'll resolve it soon | 16:59 |
freemangordon | but not the land | 16:59 |
freemangordon | will, see, but until then no locale in leste :p | 16:59 |
uvos | "wait austria doesn't border greece" laughs in 1915 | 16:59 |
Wizzup | uvos: something I also notice when I use clownboot on the d3, the screen backlight flickers a bit when a usb cable is plugged in | 17:00 |
uvos | Wizzup: hmm | 17:00 |
uvos | Wizzup: strange | 17:00 |
Wizzup | uvos: in any case I need to do some work but if there is a good time to bug you about the d3 let me know | 17:03 |
uvos | Wizzup: so the first thing would be https://github.com/tmlind/cpcaprw | 17:03 |
uvos | dump that in android at the same oop as mainline and see if we are missconfigureing any regulators | 17:04 |
uvos | the d3 has a special kernel so really anything could be different | 17:04 |
uvos | could maybe also make sense to look at omap-emif since the memory chip is the other thing thats quite different | 17:05 |
Wizzup | how could I ensure things are at the same oop? | 17:05 |
uvos | examine the d3 stock dts diffed against the xt875 one again and the signal map | 17:06 |
uvos | Wizzup: you can use cpu freq to force the oop | 17:06 |
Wizzup | in android? | 17:06 |
uvos | yes | 17:06 |
uvos | clowboot dose it in the script even | 17:06 |
uvos | just before kexec | 17:06 |
Wizzup | ok | 17:06 |
uvos | so look ther | 17:06 |
uvos | e | 17:06 |
Wizzup | hm, I don't have armel cross, only armhf (for cpcaprw) | 17:07 |
Wizzup | well, let's see if I can fix that | 17:07 |
uvos | i would strongly recommend using the android sdk | 17:07 |
uvos | and using this pr https://github.com/tmlind/cpcaprw/pull/1 | 17:07 |
Wizzup | if you have a binary around, could you share it? that would save me getting the whole android sdk/ndk | 17:08 |
uvos | Wizzup: sure https://uvos.xyz/maserati/cpcaprw | 17:10 |
uvos | but im not sure what api level i compiled this against | 17:10 |
uvos | if it compiled it agains api level 15/android 4.0 it wont work on droid 3 which is api level 9 or 10 | 17:11 |
Wizzup | ok, when my d3 is charged we will see | 17:11 |
Wizzup | heh this one is the chinese droid 3 :) | 17:12 |
Wizzup | xt883 | 17:12 |
uvos | oh and dont do this via adb | 17:23 |
Wizzup | don't do what? | 17:23 |
uvos | we want the no usb connected state | 17:23 |
Wizzup | oh, that will be new for me | 17:23 |
uvos | just use the android build in terminal on device | 17:23 |
Wizzup | ok | 17:23 |
uvos | you have to go to settings -> device proparties (or so) | 17:24 |
uvos | and click on the build number 10 times | 17:24 |
uvos | then you get a new developer entry in settings | 17:24 |
uvos | there you can unhide the build in terminal | 17:24 |
uvos | otherwise the cpcap regs will have a bunch of spurious differences | 17:25 |
uvos | as the mainline kernel dosent setup charging the same way | 17:26 |
Wizzup | otherwise -> if using adb over usb ? | 17:26 |
uvos | you will have lots more registers to lookup after the diff with the mainline kernel | 17:26 |
Wizzup | ok, I'll try to get this set up in the next few hours | 17:28 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!