libera/#maemo-leste/ Wednesday, 2024-01-17

freemangordonuvos: re locales: Nokia managed to avoid building on device, by pre-building on image-builder07:43
freemangordonumm, in auto-builder, not image-builder07:43
freemangordonperhaps we can create a package that contains pre-build locales and tracks libc607:44
freemangordonor, we can just not enable anything but en_GB on the image, and provide an UI for user to add more locales as she wants07:59
siceloi think en_US would be better than en_GB, or at least both then. many locales inherit from en_US afaik11:28
Wizzupfreemangordon: debian rebuilds them upon libc upgrade only11:43
Wizzupso when people flash an image they don't run into rebuilding issues11:43
tmlindWizzup: 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 far12:55
Wizzupyeah it works quite smooth :)13:01
inkyimportant lagrange update: gemini://bbs.geminispace.org/s/Lagrange/13969 - i need to make an update.13:06
Wizzupinky: check13:30
inkycheck what? i am building it on device now to test, then will try in phoenix.13:31
Wizzupinky: as in confirm13:33
Wizzupas in ok13:33
Wizzup:)13:33
freemangordonWizzup: yes, but on libc upgrade, it takes ages15:27
Wizzupyup15:28
Wizzuplike I said, just edit /etc/locale.gen15:28
WizzupI am not sure if we need a UI for that now15:28
freemangordonbut, we can do it on the opposite - enable only en_GB in /etc.locale.gen by default15:29
WizzupI would do en_US like sicelo said, but yes15:29
Wizzupthis is easy and I think the image builder or leste-config does this15:30
freemangordonand then "just edit /etc/locale.gen"15:30
freemangordonyes15:30
freemangordonwhy US?15:30
Wizzup# TODO: Do this through a package when we have a language-changing package15:30
Wizzup# Generate locales15:30
Wizzupapt-cache search hildon-common-strings-l10n \ | grep -v mr0 \ | awk -F'[()]' '{printf "%s.UTF-8 UTF-8\n", \$2}' \ >> /etc/locale.gen15:30
Wizzuplocale-gen15:30
Wizzuphttps://github.com/maemo-leste/image-builder/blob/master/chimaera.blend#L11515:30
Wizzupfreemangordon: that's the default on basically all systems15:31
Wizzupwe also set it as default as you can see in the chimaera.blend file15:31
freemangordonnot on fremantle though15:31
Wizzuphttps://github.com/maemo-leste/image-builder/blob/master/chimaera.blend#L26 just noticed this typo15:32
Wizzupfreemangordon: I don't think fremantle ever regenerated them15:32
Wizzupin 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 any15:32
Wizzupso how do we manage locale.gen going forward? it needs to be through some package15:35
Wizzupuvos: 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 instability15:52
bencohWizzup: 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 platforms16:14
Wizzupyes, we're in agreement I think16:14
bencohah okay16:14
Wizzupright now we're generating /all/ of them16:14
Wizzupthe question is, how does the user control which ones he/she wants16:14
bencohoh, I see16:14
bencohyeah, that's the question indeed16:14
Wizzupright now I think the only ones visible in the settings UI are the *generated* ones16:14
Wizzupso we can just tell people 'sudo vi /etc/locale.gen && locale-gen'16:15
WizzupI'm fine with that16:15
Wizzupbut 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, etc16:15
Wizzupcould be some hacky one-shot postinst script I suppose16:15
uvosplease use en_US as the default locale16:26
uvosidk 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 fremantle16:27
uvosen_US is simply the universal default, and everthing that is unintentioally broken on other locales works in en_US16:28
uvosWizzup: btw yes cpufreq works again in 6.6 after depmod16:33
uvosso was just that16:34
Wizzupcool16:34
uvoswait no16:34
uvosi just booted the wrong thing :D16:34
uvosnvm16:34
Wizzuphow do you test?16:34
uvoscat /sys/bus/cpu/devices/cpu0/cpufreq/ is missing16:34
freemangordonin our localisation packages, en_GB is the base locale16:35
freemangordonso that makes it the default16:36
freemangordoneverything else is based on en_GB16:36
Wizzupuvos: # CONFIG_ARM_OMAP2PLUS_CPUFREQ is not set16:36
Wizzupis that a problem?16:36
freemangordonheh16:36
freemangordonthat might explain cpufreq not being loaded16:37
Wizzupthere is also16:37
Wizzup# CONFIG_PM_DEVFREQ is not set16:37
sicelofreemangordon: ok. i think having both is fine then :-)16:37
freemangordonwhy?16:37
freemangordonwhy exactly you need en_US?16:37
freemangordonfor non-maemo packages?16:37
Wizzupthe world runs on en_US, it's the default everywhere, and I don't think it will negatively affect maemo16:38
Wizzupit's also mostly a non-issue I think, which is why I don't care :D16:38
Wizzupin fact, as stated before, it is -currently- the default on maemo leste16:38
freemangordon"freemangordon: in our localisation packages, en_GB is the base locale"16:39
uvosWizzup: yeah thats wierd but here is 6.1 # CONFIG_ARM_OMAP2PLUS_CPUFREQ is not se16:39
uvosso this dident change16:39
Wizzupfreemangordon: that's fine, but the d4 in your pocket uses en_US and clearly the maemo locales work16:39
freemangordonno16:39
freemangordonit uses en_GB16:39
uvosi dffed the config and its the same between 6.1 and 6.616:40
* freemangordon checks16:40
uvosand its the same besides additions16:40
Wizzupuvos: strange16:40
uvosofc one of those could now be required idk16:40
freemangordonEnglish (United Kingdom) ;)16:40
Wizzupcan you share output of 'locale'16:40
freemangordonLANG=en_GB.utf-816:40
Wizzupok, then you manually changed it16:40
freemangordonsure16:40
Wizzupmine is English (United States)16:41
sicelomine's en_US too (n900). i can't swear to it, but i'd like to think i never changed it16:41
WizzupI linked the image-builder scripts and it set it to en_US16:41
freemangordonWizzup: the pont is - in every osso- localisation package, the locale every other locales are based on is en_GB16:41
Wizzupso no need to check16:41
uvosLANG=en_US.utf-816:41
Wizzupfreemangordon: fine then change it and please deal with the fallout if any16:42
uvosdident change it besides LC_NUMERIC=de_DE.utf-816:42
WizzupI'm sure there will be some funny error messages popping up that aren't quite googleable because they are slightly different16:42
sicelootherwise yes, i also don't think en_GB would adversely affect my usage ... i'm just used to en_US16:42
WizzupI just /really/ don't care about the default locale so I don't want to waste energy on it16:42
uvoserror: user missing trousers16:43
* sicelo thinks someday there should be en_SZ :p16:43
freemangordonWizzup: see, I am trying to understand why the obsession on US16:43
uvosbecause most software is terrible16:43
Wizzupfreemangordon: no obsession, it's just the default everywhere16:43
uvosand since its the default everywhere most terrible software works correctly so16:43
freemangordonsicelo: IIRC, default in fremantle is en)GB, fro the reason I stated above16:43
uvos:P16:43
Wizzupall my machines are also en_US because I don't want coredumps to use a different word that isn't googleable16:43
uvosgoogleablilty is a good point16:44
freemangordonok16:44
freemangordonso be16:44
WizzupI checked my fremantle and it is en_GB16:44
freemangordonyes16:44
freemangordonI know16:44
WizzupI don't know enough how locales work but I think there shouldn't be any problems showing english to the user either way16:44
Wizzup(that's a serious question)16:44
gnarfacedpkg-reconfigure locales?16:45
uvosmain issue i encourter is locale aware parsers being used in places they should not causing issues16:45
uvosbane of ones existance with scientific software/scripts parsing csv files and things16:46
freemangordonok, lets have both US and GB16:46
Wizzupgnarface: good point, we didn't consider how debian handles this16:46
freemangordonthe issue with US as default is that there might be osso- localisation packages that has GB but not US entry16:47
Wizzupfreemangordon: so the way controlpanel regional plugin works is that it only looks at the generated locales, so then users won't /see/ the other languages16:47
gnarfacei 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 set16:47
freemangordonWizzup: yes, I know16:47
Wizzup16:47 < freemangordon> the issue with US as default is that there might be osso- localisation packages that has GB but not US entry16:47
Wizzupso that was my question16:47
WizzupI think the en_ prefix just means there is a fallback16:47
Wizzupbut that is an assumption16:47
freemangordonnot sure either16:47
gnarfacei think the pine64 keyboards may also need en_GB-altgr or whatever it's called16:47
Wizzupfreemangordon: I see maemo text just fine and mine is set to en_US16:47
Wizzupso probably it just works16:47
uvosworste case it ends up with effectively C as locale or which is also english?16:48
uvosnot sure16:48
gnarface(some of them, anyway)16:48
freemangordonno, probably there is no issue wieh US localisation16:48
WizzupI think keyboard layout is independent from localisation16:48
Wizzupwell at least on a 'locale' leven16:48
Wizzuplevel*16:48
freemangordonWizzup: regarding locales not listed - I think it is very easy to add one more touch selector "add locale" to cpl applet16:48
gnarfaceoh, yes it's "dpkg-reconfigure keyboard-configuration" but you often find you have to set both of these to a coherent set16:48
freemangordonI can take on that16:49
Wizzupok16:49
freemangordonI just need the full list of locales we want to support16:49
uvosgnarface: not on leste as lots of people use droid4s with only us keyboards16:49
freemangordonbut I can take that from the image16:49
bencohWizzup: sounds like the regional panel would need an additional 'install languages/locales' panel to modify /etc/locale.gen ?16:49
gnarfaceTBH 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 them16:49
gnarface... not that i have any horse in this race, just an opinion16:50
Wizzupgnarface: yeah I think we're (all) in agreement16:51
Wizzupcurrently the base install has /all/16:51
Wizzupwhich 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 :P16:51
bencoh:]16:52
uvosthers also the l10n packages16:53
freemangordonbencoh: "(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
bencohyeah16:54
Wizzupuvos: yes, that would need to be sorted via a meta pkg too16:54
uvosits a bit annoying that one is forced to have so many l10n packages installed for languages one dosent speak16:54
freemangordonuvos: I think we are in agreement here16:54
freemangordonwe'll have only GB and US pre-enabled16:54
freemangordonand controlpanel UI to add/remove16:55
Wizzupwhat about mountain german16:55
freemangordonwhat about it?16:55
uvosi dont speak that16:55
Wizzupfreemangordon: it was a joke16:55
freemangordonI know16:55
freemangordonmy point was - no issue with it, lets add it as well :p16:55
Wizzupthere's no austrian locale it looks on leste atm ;)16:56
freemangordonWizzup: but yeah, we need a package16:56
Wizzupcan you make an issue for this? or maybe two?16:56
Wizzupuvos: I'm booting my leste droid3 and also charging the android one16:56
Wizzupin case you'd have some time at some point16:57
freemangordonthey don;t deserve, forcing me waiting hours on the Greek border :p16:57
freemangordonWizzup: no, I'll just implement as soon as I have some spare time16:57
Wizzupwait austria doesn't border greece16:57
Wizzupfreemangordon: cool16:57
freemangordonyeah, but they stopped BG from full Schengen16:58
Wizzupoh yeah, before that it was just NL for 10 years16:58
freemangordonyeah, but NL played it generous just before NY16:58
freemangordonit is only Austria stopping us16:58
freemangordonwell, they allowed air and see16:59
WizzupI'm sure they'll resolve it soon16:59
freemangordonbut not the land16:59
freemangordonwill, see, but until then no locale in leste :p16:59
uvos"wait austria doesn't border greece" laughs in 191516:59
Wizzupuvos: something I also notice when I use clownboot on the d3, the screen backlight flickers a bit when a usb cable is plugged in17:00
uvosWizzup: hmm17:00
uvosWizzup: strange17:00
Wizzupuvos: in any case I need to do some work but if there is a good time to bug you about the d3 let me know17:03
uvosWizzup: so the first thing would be https://github.com/tmlind/cpcaprw17:03
uvosdump that in android at the same oop as mainline and see if we are missconfigureing any regulators17:04
uvosthe d3 has a special kernel so really anything could be different17:04
uvoscould maybe also make sense to look at omap-emif since the memory chip is the other thing thats quite different17:05
Wizzuphow could I ensure things are at the same oop?17:05
uvosexamine the d3 stock dts diffed against the xt875 one again and the signal map17:06
uvosWizzup: you can use cpu freq to force the oop17:06
Wizzupin android?17:06
uvosyes17:06
uvosclowboot dose it in the script even17:06
uvosjust before kexec17:06
Wizzupok17:06
uvosso look ther17:06
uvose17:06
Wizzuphm, I don't have armel cross, only armhf (for cpcaprw)17:07
Wizzupwell, let's see if I can fix that17:07
uvosi would strongly recommend using the android sdk17:07
uvosand using this pr https://github.com/tmlind/cpcaprw/pull/117:07
Wizzupif you have a binary around, could you share it? that would save me getting the whole android sdk/ndk17:08
uvosWizzup: sure https://uvos.xyz/maserati/cpcaprw17:10
uvosbut im not sure what api level i compiled this against17:10
uvosif it compiled it agains api level 15/android 4.0 it wont work on droid 3 which is api level 9 or 1017:11
Wizzupok, when my d3 is charged we will see17:11
Wizzupheh this one is the chinese droid 3 :)17:12
Wizzupxt88317:12
uvosoh and dont do this via adb17:23
Wizzupdon't do what?17:23
uvoswe want the no usb connected state17:23
Wizzupoh, that will be new for me17:23
uvosjust use the android build in terminal on device17:23
Wizzupok17:23
uvosyou have to go to settings -> device proparties (or so)17:24
uvosand click on the build number 10 times17:24
uvosthen you get a new developer entry in settings17:24
uvosthere you can unhide the build in terminal17:24
uvosotherwise the cpcap regs will have a bunch of spurious differences17:25
uvosas the mainline kernel dosent setup charging the same way17:26
Wizzupotherwise -> if using adb over usb ?17:26
uvosyou will have lots more registers to lookup after the diff with the mainline kernel17:26
Wizzupok, I'll try to get this set up in the next few hours17:28

Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!