| 00:33.32 | *** join/#maemo-ssu int_ua (~int_ua@ip-602f.proline.net.ua) |
| 00:37.36 | freemangordon | lus - yes, we can RE all closed localisation packages, it's been already done for osso-pdf-viewver, modest, camera-ui, etc |
| 00:37.49 | freemangordon | luf: ^^^ |
| 00:37.54 | freemangordon | (ENAME) |
| 00:38.11 | luf | Ok :( Any volunteer? :D |
| 00:38.40 | luf | freemangordon: where can I find such localizations? In extras? |
| 00:39.08 | freemangordon | merlin1991: what was the magic command to RE .mo to .po? I know you wrote it somewhere last time. :D |
| 00:39.12 | luf | Just I'm curious where put them (once I find time for it). |
| 00:39.23 | luf | msgunfmt ;) |
| 00:39.26 | luf | freemangordon: ^^^ |
| 00:39.33 | freemangordon | luf: hmm, those should be available in SDK |
| 00:39.37 | freemangordon | luf: aah, yes |
| 00:39.50 | freemangordon | exactly, msgunfmt :) |
| 00:40.10 | luf | I downloaded all hildon-fm packages ... But when rebuild where to store? |
| 00:40.46 | freemangordon | luf: what? hmm, lemme think... ummm.. cssu-devel? |
| 00:40.48 | freemangordon | :P |
| 00:40.55 | luf | sources? |
| 00:41.02 | freemangordon | aah, on gitorious |
| 00:41.51 | luf | Ugh, you're right I again overlooked something ... |
| 00:41.54 | freemangordon | check that one for example - https://gitorious.org/community-ssu/osso-pdf-viewer-l10n |
| 00:42.02 | luf | Yeah I see now. |
| 00:42.17 | freemangordon | what you've missed? |
| 00:43.00 | luf | Nothing now. |
| 00:43.06 | luf | Just time? :D |
| 00:43.57 | freemangordon | luf: BTW i looked at the commit. it looks ok to me. not that I've reviewed it thoroughly, but at first glance it seems ok |
| 00:44.19 | freemangordon | luf: time? hmm, RE l10n takes about 30-40 minutes :P |
| 00:45.34 | luf | freemangordon: what commit are you talking about? libhildonfm? |
| 00:45.46 | luf | I think you'll like the libhildonfm change :D |
| 00:46.12 | freemangordon | no, gnomevfs-extras |
| 00:46.29 | freemangordon | did you commit it? |
| 00:47.12 | luf | Yes I did also libhildonfm ;) |
| 00:48.08 | freemangordon | so you don;t use dbus? |
| 00:48.14 | freemangordon | to get the name that is |
| 00:48.58 | freemangordon | I wonder if it can bring troubles, though I can't think of any :) |
| 00:49.42 | luf | freemangordon: yes, that's it :) |
| 00:50.12 | luf | freemangordon: Maybe the name change will be a little bit slower but it get the icon from gconf so why not name also ;) |
| 00:50.34 | luf | Simple and bluez change independent :D |
| 00:53.29 | freemangordon | sure, though I wander what will happen if device get re-paired |
| 00:53.33 | freemangordon | *a device |
| 00:54.01 | freemangordon | device class most probably will remain the same (thus the icon), while the name could get changed |
| 00:54.17 | freemangordon | onthe other hand... |
| 00:54.31 | freemangordon | gconf key should be changed too, ain't? |
| 00:54.49 | luf | Sure it can and I think it is. |
| 00:54.50 | freemangordon | well, that is easy to be verified |
| 00:54.54 | luf | We'll see ;) |
| 00:54.59 | freemangordon | yep :) |
| 00:58.55 | luf | freemangordon: It seems to me that nobody wants to test it :) Even kerio ... maybe he's ill. |
| 01:01.28 | *** join/#maemo-ssu jonwil (~jonwil@27-33-137-199.static.tpgi.com.au) |
| 01:08.30 | luf | freemangordon: do you know gnomevfs? |
| 01:10.05 | luf | I don't like it's prereading the "directories" so when you go into Bluetooth (sfil_li_bluetooth) it connects to all devices and reads their content. |
| 01:12.57 | DocScrutinizer05 | gnomevfs is a real annoyance |
| 01:13.45 | DocScrutinizer05 | the funny part is even poettering dislikes it |
| 01:39.47 | *** join/#maemo-ssu LaoLang_cool (~LaoLang_c@221.226.175.139) |
| 03:31.34 | *** join/#maemo-ssu kolp_ (~quassel@212.255.37.28) |
| 03:43.36 | *** join/#maemo-ssu amiconn_ (amiconn@rockbox/developer/amiconn) |
| 04:00.34 | *** join/#maemo-ssu DocScrutinizer05 (~HaleBopp@openmoko/engineers/joerg) |
| 05:41.32 | *** join/#maemo-ssu ekze (~nyan@bakaekze.ru) |
| 06:06.15 | *** join/#maemo-ssu amiconn_ (amiconn@rockbox/developer/amiconn) |
| 06:08.18 | *** join/#maemo-ssu DocAvalanche (~lagrange@lagrange.cloud-7.de) |
| 06:20.46 | *** join/#maemo-ssu dhbiker (~dhbiker@95.87.145.172) |
| 06:33.06 | *** join/#maemo-ssu dhbiker_ (~dhbiker@95.87.145.172) |
| 06:40.29 | *** join/#maemo-ssu DocScrutinizer51 (~lagrange@openmoko/engineers/joerg) |
| 06:43.31 | *** join/#maemo-ssu Pali (~pali@Maemo/community/contributor/Pali) |
| 08:11.10 | *** join/#maemo-ssu luf (~luf@ip-89-102-208-114.net.upcbroadband.cz) |
| 08:38.49 | freemangordon | luf: will test it when I have some spare time |
| 09:28.16 | freemangordon | luf: does i still segfault? as I will test it on my primary, don;t want to risk a rebootloop |
| 09:28.31 | freemangordon | *does it |
| 09:57.53 | freemangordon | luf: Bad news :). using gconf to retreive device names don't work, I have 4 devices shown, but only 2 with names |
| 09:58.29 | freemangordon | i chacked in /var/lib/bluetooth/names and missing (in filemanager) devices are there |
| 09:59.07 | freemangordon | so you should revert hildonfm commit and use bluez dbus API to get device names. BTW the same should happen for the icon |
| 09:59.36 | freemangordon | as I have missing icons for those to devices too |
| 10:07.59 | *** join/#maemo-ssu M4rtinK (~M4rtinK@mail.melf.eu) |
| 10:10.32 | *** join/#maemo-ssu jonwil (~jonwil@27-33-137-199.static.tpgi.com.au) |
| 10:28.00 | *** join/#maemo-ssu wmarone (~wmarone@c-67-174-151-253.hsd1.ca.comcast.net) |
| 10:37.33 | *** join/#maemo-ssu arcean (~arcean@aacu163.neoplus.adsl.tpnet.pl) |
| 10:38.51 | *** join/#maemo-ssu lizardo (lizardo@nat/indt/x-chcotfqpzgorlonp) |
| 11:05.51 | *** join/#maemo-ssu Martix (~martix@ip-62-245-106-78.net.upcbroadband.cz) |
| 11:16.16 | *** join/#maemo-ssu kolp (~quassel@212.255.37.28) |
| 11:26.45 | luf | freemangordon: It's not funny :( However I don't have gnome icons names to change also icons. |
| 11:27.34 | luf | freemangordon: do you remember how you add such devices? Maybe two with names you added from N900 and the other two you added from remote devices. |
| 11:28.26 | luf | freemangordon: do you see segfaults? |
| 11:47.44 | *** join/#maemo-ssu arcean (~Arcean@aacu163.neoplus.adsl.tpnet.pl) |
| 12:15.19 | *** join/#maemo-ssu arcean_ (~Arcean@aacr234.neoplus.adsl.tpnet.pl) |
| 12:22.49 | *** join/#maemo-ssu wmarone (~wmarone@c-67-174-151-253.hsd1.ca.comcast.net) |
| 12:58.13 | *** join/#maemo-ssu M4rtinK (~M4rtinK@mail.melf.eu) |
| 13:02.07 | *** join/#maemo-ssu M4rtinK (~M4rtinK@mail.melf.eu) |
| 13:06.00 | *** join/#maemo-ssu Pali (~pali@Maemo/community/contributor/Pali) |
| 14:06.15 | *** join/#maemo-ssu LaoLang_cool (~LaoLang_c@221.226.175.138) |
| 14:09.30 | *** join/#maemo-ssu iDont (~iDont@ip4da305b4.direct-adsl.nl) |
| 14:21.56 | *** join/#maemo-ssu NIN101 (~NIN@p5DD28AE6.dip0.t-ipconnect.de) |
| 15:24.28 | DocScrutinizer05 | reports flawless update of T |
| 15:24.47 | DocScrutinizer05 | haven't checked my certs yet though |
| 15:26.42 | DocScrutinizer05 | merlin1991: chem|st: could you take care about that X-MAEMO-changelog or whatever it's called section in pkg .deb sources, to have some description of what's new in this release, so HAM does show that |
| 15:26.47 | DocScrutinizer05 | for S |
| 15:27.17 | merlin1991 | hit chemist that he does it this time |
| 15:28.13 | DocScrutinizer05 | you know what i'm talking about? |
| 15:28.31 | Pali | DocScrutinizer05, do you mean my patch? https://gitorious.org/community-ssu/mp-fremantle-community-pr/commit/65fda141c8b92f4b5364b42e8de5e1452cf2b027 |
| 15:29.14 | DocScrutinizer05 | Pali: no |
| 15:29.49 | Pali | and what is X-MAEMO-changelog?? |
| 15:33.58 | DocScrutinizer05 | XB-maemo-upgrade-description in debian/control |
| 15:34.25 | merlin1991 | Pali: yep he means your patch (in a way) |
| 15:34.52 | Pali | DocScrutinizer05, my above patch doing it :-) |
| 15:35.04 | DocScrutinizer05 | overrides description if somebody doesn't install for first time |
| 15:35.29 | Pali | it generating maemo-upgrade-description from debian/changelog directly to debian/package/DEBIAN/control |
| 15:35.37 | DocScrutinizer05 | oooh |
| 15:41.04 | DocScrutinizer05 | anyway, please take care for HAM showing some "we fixed the TURKTRUST...bla bla bla" instead of standard gossip, for those who do upgrade. OTOH I don't know, maybe every fresh CSSU isnatll is already an upgrade for HAM? |
| 15:41.18 | DocScrutinizer05 | install* |
| 15:42.09 | DocScrutinizer05 | or rather, don't do anything like that for CSSU-S this time, since we didn't trst in T |
| 15:43.21 | DocScrutinizer05 | given we want to play safe for S, we probably shouldn't change *anything* form T to S |
| 15:43.23 | merlin1991 | DocScrutinizer05: any cssu install is already upgrade |
| 15:43.37 | merlin1991 | because the enabler postinst injects the fake mp so ham can upgrade it |
| 15:43.39 | DocScrutinizer05 | :nod: occured to me |
| 15:45.13 | DocScrutinizer05 | so we don't want pali patch I guess, not for now and not for future, rather edit "Description:" section in debian/control to include some info about this very upgrade and what it does |
| 15:45.37 | DocScrutinizer05 | and omit XB-maemo-upgrade-description completely |
| 15:45.44 | DocScrutinizer05 | right? |
| 15:45.54 | merlin1991 | nope |
| 15:46.05 | merlin1991 | because description also goes into apt-cache search and friends |
| 15:46.20 | merlin1991 | and there we don't need the update specific notes |
| 15:46.28 | DocScrutinizer05 | umpf |
| 15:46.45 | Pali | maemo pr1.3 metapackage does not show pr1.1 changes too |
| 15:47.10 | DocScrutinizer05 | then copy description section content to XB-maemo-upgrade-description section and augment it by some notes about what's new in current update |
| 15:47.14 | Pali | so I do not see reason to show changelog for first CSSU |
| 15:47.58 | DocScrutinizer05 | Pali: merlin just explained there's no such thing like a first CSSU |
| 15:48.04 | DocScrutinizer05 | (install) |
| 15:48.09 | Pali | yes |
| 15:48.21 | Pali | there is only update to last CSSU version |
| 15:48.40 | DocScrutinizer05 | yes, even for first time install |
| 15:49.06 | Pali | and debian/changelog in cssu metapackage is good place for *user* changelog |
| 15:49.18 | DocScrutinizer05 | *sigh* |
| 15:50.40 | DocScrutinizer05 | I don't think info in HAM for "Maemo CSSU system upgrade" should be "fixed TURKTRUST" for those who install CSSU first time |
| 15:50.53 | DocScrutinizer05 | it has to be a tad more verbose |
| 15:53.25 | DocScrutinizer05 | for now what I see in HAM "description" is fine for first time installing users |
| 15:54.07 | DocScrutinizer05 | once we get XB-maemo-upgrade-description, this will vanish even for those first time installers |
| 15:56.19 | DocScrutinizer05 | so pretty please take care that the info shown by HAM is appropriate for both first-timers and upgraders. The former wnat to learn what's a maemo5 CSSU system upgrade, the latter want to know what's new in T7.2 |
| 15:56.38 | merlin1991 | DocScrutinizer05: srly |
| 15:56.44 | merlin1991 | the former have to run the enabler |
| 15:57.01 | merlin1991 | hence either they learned already or something is really really wrong |
| 15:57.30 | DocScrutinizer05 | that's kinda flawed user experience |
| 16:00.17 | Pali | DocScrutinizer05, I think that HAM show on first line package name and on second line package description |
| 16:00.33 | Pali | and upgrade notes are shown tab when you click details |
| 16:01.23 | Pali | you have buttons like backup and details when you going to install cssu upgrade |
| 16:01.29 | DocScrutinizer05 | not afaik |
| 16:01.45 | kerio | add an X-maemo-install-description that takes priority over X-maemo-upgrade-description if it exists and has the information Doc wants |
| 16:02.04 | Pali | kerio, not possible |
| 16:02.10 | Pali | HAM is part of CSSU |
| 16:02.16 | kerio | ...oh, right |
| 16:02.17 | kerio | heh |
| 16:02.24 | Pali | so you need to upgrade metapackage for new HAM |
| 16:02.54 | Pali | but I think that HAM really show package name & description in update window |
| 16:03.11 | Pali | and not maemo-upgrade-description |
| 16:05.03 | DocScrutinizer05 | "XB-maemo-upgrade-description:" overrides "description:" |
| 16:05.25 | DocScrutinizer05 | usually for upgrades only, for CSSU though unconditionally |
| 16:06.10 | DocScrutinizer05 | if merlin1991's info been correct |
| 16:06.43 | DocScrutinizer05 | so if something overrides some other thing unconditionally, it's basically useless |
| 16:07.15 | merlin1991 | well usually you don't dpkg -i a basepackage before you fire up ham to install(upgrade) it |
| 16:07.19 | merlin1991 | but that's what our enabler does |
| 16:07.23 | merlin1991 | in order to bootstrap the mp |
| 16:08.09 | Pali | DocScrutinizer05, cssu is installed via enabler |
| 16:08.20 | Pali | so you will see install info in enabler package |
| 16:08.31 | kerio | hm, can't HAM directly *install* a system package? |
| 16:08.40 | Pali | so here is info what CSSU is |
| 16:08.54 | merlin1991 | 10 points for Pali :) |
| 16:09.09 | Pali | kerio, problem is that you can have only one mp-fremantle metapackage |
| 16:09.27 | kerio | so? make HAM do its thing |
| 16:09.34 | kerio | if it can |
| 16:09.45 | Pali | so we need enabler, which uninstall all metapackages and install that from cssu |
| 16:10.00 | DocScrutinizer05 | Pali: I don't care when the content of my microwave food is listed on manufacturer's webpage, I want it on package of the food |
| 16:10.25 | Pali | ham does not support something like provides & replaces |
| 16:10.29 | Pali | so ham cannot do it |
| 16:10.45 | kerio | Pali: are you sure? it works for kernel, kernel-flasher and kernel-modules |
| 16:10.56 | Pali | kerio, not working |
| 16:11.06 | Pali | we have also problem with operator name widget update |
| 16:11.21 | DocScrutinizer05 | and friggin hell, how hard can it be to concatenate content of "description:2 and changelog into "XB-maemo-upgrade-description:" ? |
| 16:11.36 | kerio | Pali: why does fmg claim that it works then? |
| 16:11.38 | Pali | also on irc there was info that first is needed to update operator name widget and then cssu metapackage |
| 16:12.12 | Pali | DocScrutinizer05, why? |
| 16:12.24 | Pali | if you want to install CSSU you need: |
| 16:12.34 | Pali | 1. open web package and click on install button |
| 16:13.02 | Pali | 2. HAM will show that you are going to install package enabler which installing CSSU, there is written what CSSU is .... |
| 16:13.21 | Pali | 3. open menu and click on continue cssu installation |
| 16:13.45 | Pali | 4. HAM will show update and you will update system packages |
| 16:14.21 | kerio | btw, why can't we ship mp-fremantle-generic-pr? |
| 16:14.33 | Pali | kerio, becuase generic is on for global FW |
| 16:14.52 | kerio | really? the other ones have special metapackages? :o |
| 16:14.52 | Pali | there are variants: mp-fremantle-<code>-pr |
| 16:14.56 | Pali | yes |
| 16:15.18 | Pali | DocScrutinizer05, steps 1, 2 show cssu info |
| 16:18.29 | DocScrutinizer05 | Pali: I don't get your reasoning why you refuse to add the very info we got on *every* update until now |
| 16:19.43 | DocScrutinizer05 | it's poor product maintenance to not provide user with basic info about the opject he just looks at |
| 16:20.18 | Pali | now we have: |
| 16:20.20 | Pali | Maemo-Display-Name: Maemo 5 Community SSU Package |
| 16:20.27 | Pali | Description: Community SSU package, includes latest fixes from Gitorious and the community |
| 16:20.45 | DocScrutinizer05 | and til now we did provide such info in first installation, now you say you want to ditch that to *replace* it with changelog. Why? Can't you show both?? |
| 16:21.03 | Pali | and scripts will generate: |
| 16:21.04 | kerio | DocScrutinizer05: hm, adding both would be fine |
| 16:21.05 | Pali | Maemo-Upgrade-Description: Changelog for $(VERSION): |
| 16:21.37 | Pali | DocScrutinizer05, do you really want to see that Description line in Maemo-Upgrade-Description? |
| 16:21.46 | kerio | will HAM display it, otherwise? |
| 16:22.10 | Pali | If yes write some short first line for Maemo-Upgrade-Description: |
| 16:22.10 | DocScrutinizer05 | YES! rathe that only, than changelog ONLY |
| 16:22.23 | kerio | Pali: i'll write it |
| 16:22.28 | kerio | "Community SSU package, includes latest fixes from Gitorious and the community" |
| 16:22.33 | kerio | there :D |
| 16:26.22 | Pali | ok, we can test *what* and *where* will be displayed in next update |
| 16:26.54 | Pali | and then we can change lines which will be problematic |
| 16:27.13 | DocScrutinizer05 | fine with me |
| 16:28.17 | Pali | if HAM is really non deterministic with those descriptions (and lines) we can duplicate some lines between description and upgrade-desc. |
| 16:28.27 | DocScrutinizer05 | my general suggestion would be: copy content of "Description:" to "XB-maemo-upgrade-description:", then *append* changelog |
| 16:28.56 | DocScrutinizer05 | simple as that |
| 16:29.04 | Pali | full description? or only first line? |
| 16:29.21 | Pali | and where to copy it? at begining? or to append at end? |
| 16:29.24 | DocScrutinizer05 | err, the relevant info |
| 16:29.40 | DocScrutinizer05 | to beginning, then append changelog |
| 16:30.00 | Pali | DocScrutinizer05, better wait for next cssu-t update and see how and what do change |
| 16:30.56 | DocScrutinizer05 | Pali: basically next update tells me nothing since this is about those users who install firsttime |
| 16:31.47 | Pali | there is no "first time" installation of metapackage |
| 16:31.56 | Pali | only upgrade |
| 16:32.06 | DocScrutinizer05 | but i'm able to figure what stuff will look like, for firsttime and for update (which is no differnece according to merlin1991 and my estimation), and for differnet way to generate that text |
| 16:32.09 | Pali | first time is installing cssu enabler |
| 16:32.13 | Pali | which was not touched |
| 16:32.48 | Pali | cssu enabler installing via dpkg -i in terminat cssu metapackage |
| 16:36.03 | DocScrutinizer05 | Pali: sorry I'm a tad upset, so a last time: I'm not talking about enabler! |
| 16:37.23 | DocScrutinizer05 | frankly spoken, average lusers tend to forget that they have to run that upgrade in HAM after installing enabler |
| 16:38.16 | DocScrutinizer05 | and when they look into HAM and see maemo CSSU system upgrade, they get puzzled when it says "this is bringing you a fix for TURKTRUST" |
| 16:39.42 | DocScrutinizer05 | and during enjoying that puzzling feeling, they forget that they have run enabler 20 min ago (yes it will be 20 min since they did) |
| 16:45.56 | freemangordon | guys, Pali's patch was tested with latest -thumb, and IMO this is how all this shit have to look like |
| 16:46.20 | freemangordon | first tab - package description ("latest gratest studd") |
| 16:46.23 | freemangordon | *stuff |
| 16:46.26 | DocScrutinizer05 | freemangordon: I beg to differ |
| 16:46.54 | freemangordon | second tab: changelog |
| 16:47.26 | Pali | so I remember correctly that changelog is on separate tab? |
| 16:47.29 | freemangordon | yes |
| 16:47.57 | Pali | DocScrutinizer05, so why did you think that it wasnt? |
| 16:48.10 | DocScrutinizer05 | look, I did all that shit with starhash enabler (and i guess I was the first to ever use XB-maemo-upgrade-description), and for all I can recall XB-maemo-upgrade-description overrides Description: |
| 16:48.55 | freemangordon | DocScrutinizer05: is it a bit different: |
| 16:48.57 | freemangordon | Maemo-Upgrade-Description: |
| 16:48.59 | DocScrutinizer05 | maybe HAM chnaged since then |
| 16:49.21 | freemangordon | and it is on a second tab called "description" |
| 16:49.31 | *** join/#maemo-ssu ZogG (~zoggrules@109.67.174.226) |
| 16:49.31 | *** join/#maemo-ssu ZogG (~zoggrules@funtoo/user/ZogG) |
| 16:49.58 | freemangordon | so we have 3 tabs |
| 16:50.00 | DocScrutinizer05 | headdesks a bit and puts it on "bash them later" |
| 16:50.09 | freemangordon | works gor me :D |
| 16:50.11 | freemangordon | *for |
| 16:54.11 | freemangordon | the fuck, obexftp works in osso-file-manager, kudos to luf :) |
| 16:57.47 | DocScrutinizer05 | freemangordon: than name in file */starhash-enabler/debian/control is "XB-Maemo-Upgrade-Description:" |
| 16:57.59 | DocScrutinizer05 | s/than/the/ |
| 16:58.41 | Pali | XB mean include only in binary deb package (not to source dsc file) |
| 16:58.52 | DocScrutinizer05 | ...and it's supposed to override "Description:" tag in same file, for updates only |
| 16:59.52 | *** join/#maemo-ssu Martix (~martix@ip-62-245-106-78.net.upcbroadband.cz) |
| 17:00.02 | DocScrutinizer05 | mybe i'm completely wrong |
| 17:00.53 | DocScrutinizer05 | you could install starhash-enabler=0.1 and then upgrade to 0.2 to see the effects |
| 17:01.02 | DocScrutinizer05 | in HAM |
| 17:04.32 | freemangordon | Pali: so in actual debian/control XB_ is stripped? |
| 17:04.37 | freemangordon | *XB- |
| 17:04.43 | Pali | yes |
| 17:04.56 | Pali | XB- is prefix only for *debian*/control |
| 17:05.16 | Pali | in dsc or deb package is Xsomething- stripped |
| 17:05.32 | freemangordon | however - doc, you should really see how it looks like |
| 17:07.10 | DocScrutinizer05 | as long as firsttime-installers see "Community SSU package, includes latest fixes from Gitorious and the community" (or whatever) I'm stopping any rant |
| 17:07.46 | freemangordon | DocScrutinizer05: TBH I don't like ^^^ either |
| 17:07.55 | freemangordon | as it means absolutaly nothing :D |
| 17:08.05 | freemangordon | *absolutely |
| 17:08.23 | DocScrutinizer05 | it means this is a package that comes with more than just what's mentioned in changelog |
| 17:08.55 | freemangordon | well, lets check on gitorious, what is the first-time-installer description |
| 17:09.47 | freemangordon | hmm, how is it called? |
| 17:09.55 | DocScrutinizer05 | I don't give a fsck about gitorious, I'm talking about lusers looking at HAM, after they already almost gave up on that shit ever finishing (or even starting) to do anything |
| 17:10.08 | freemangordon | sure |
| 17:11.18 | freemangordon | DocScrutinizer05: they see that message. At least I saw it yesterday |
| 17:11.46 | DocScrutinizer05 | when those lusers see a maemo-cssu-system-upgrade then that tells them "install me to fix break in last version's foobar" then the average luser says "DUH! I never even *had* foobar, so why install this upgrade?" |
| 17:12.03 | freemangordon | <PROTECTED> |
| 17:12.23 | freemangordon | you should explicitly click on it |
| 17:12.35 | freemangordon | are you fine wuth that? |
| 17:12.39 | freemangordon | *with |
| 17:12.49 | DocScrutinizer05 | yes |
| 17:13.21 | freemangordon | ok, good :) |
| 17:13.51 | DocScrutinizer05 | yesterday on T7.2 upgrade I actually missed the *changelog* that says what will actually come with this particular upgrade |
| 17:14.14 | freemangordon | DocScrutinizer05: Pali pushed the changes after it was out |
| 17:14.32 | freemangordon | or you mean on TMO? |
| 17:14.37 | DocScrutinizer05 | but I don't want the changelog to *replace* the description I've seen yesterday, for fisttime installers |
| 17:14.49 | freemangordon | it don't |
| 17:14.57 | DocScrutinizer05 | I'm talking about HAM, freemangordon |
| 17:14.58 | freemangordon | *doesn't |
| 17:15.03 | freemangordon | me too |
| 17:16.10 | freemangordon | DocScrutinizer05: lets leave it as it is and continue the discussion (if needed) after the next T |
| 17:16.45 | DocScrutinizer05 | and for all I ever knew, XB-maemo-upgrade-description *replaces* Description: |
| 17:17.22 | freemangordon | it does not, at least for system upgrades, I saw it with my eyes |
| 17:17.39 | DocScrutinizer05 | well, strange then |
| 17:17.48 | DocScrutinizer05 | for starhash-enabler it did |
| 17:18.09 | freemangordon | which PR was that? 1.2? |
| 17:18.16 | DocScrutinizer05 | 1.0.1? |
| 17:18.26 | freemangordon | well, seems HAM had evolved since |
| 17:18.36 | DocScrutinizer05 | quite possible |
| 17:18.50 | DocScrutinizer05 | I admitted that above |
| 17:19.13 | freemangordon | however, it looks pretty nice, you'll see |
| 17:19.28 | DocScrutinizer05 | I even seem to recall I "raised a bug2 against it |
| 17:19.42 | DocScrutinizer05 | so maybe they actually fixed it |
| 17:19.48 | freemangordon | check it, it might got resolved :P |
| 17:20.38 | DocScrutinizer05 | something like "get changelog on separate tab PLZKTNX" |
| 17:22.13 | DocScrutinizer05 | I probably never noticed, since ^^^ "i guess I was the first to ever use XB-maemo-upgrade-description" |
| 17:22.26 | DocScrutinizer05 | and the only one, more or less |
| 17:23.07 | DocScrutinizer05 | I'll shut up now |
| 17:23.21 | DocScrutinizer05 | wait and see next upgrade :-) |
| 17:24.03 | DocScrutinizer05 | sorry for the noise, if I was wrong |
| 17:34.22 | Pali | freemangordon, I have updated all packages from cssu-thumb & devel but still getting reboot loop |
| 17:34.34 | *** join/#maemo-ssu NIN101 (~NIN@p5DD29A7D.dip0.t-ipconnect.de) |
| 17:34.42 | Pali | how to fix that zlib1g reboot loop problem? |
| 17:35.08 | freemangordon | Pali: afaik you should not use zlib and libxml2 from devel |
| 17:35.15 | freemangordon | use -thumb version |
| 17:35.17 | kerio | D: |
| 17:35.20 | freemangordon | *versions |
| 17:35.50 | kerio | oh |
| 17:35.59 | Pali | libxml2 2.6.32.dfsg-5maemo4+0m5+0cssu0-thumb0 |
| 17:36.07 | Pali | zlib1g 1:1.2.7.dfsg-13maemo1+0cssu1+thumb0 |
| 17:36.14 | Pali | still reboot loops |
| 17:36.23 | freemangordon | 2.6.32.dfsg-5maemo4+0m5+0cssu1+thumb0 |
| 17:36.35 | freemangordon | libxml2 ^^^ |
| 17:36.44 | kerio | Pali: wait, -thumb0? |
| 17:37.20 | freemangordon | zlib1g 1:1.2.7.dfsg-13maemo1+0cssu1+thumb0 |
| 17:37.30 | freemangordon | those are the correct versions |
| 17:37.31 | Pali | http://pastebin.com/U7fwJ0yZ |
| 17:37.46 | freemangordon | apt-get update? |
| 17:37.47 | Pali | I have re-run apt-get update and upgrade before |
| 17:37.54 | freemangordon | NFC |
| 17:38.03 | kerio | Pali: sudo apt-get install libxml2=2.6.32.dfsg-5maemo4+0m5+0cssu1+thumb0 |
| 17:38.14 | kerio | freemangordon botched the versions again :s |
| 17:38.17 | Pali | now I see that |
| 17:38.19 | Pali | 0cssu0-thumb0 |
| 17:38.23 | Pali | 0cssu1+thumb0 |
| 17:38.31 | freemangordon | http://maemo.merlin1991.at/cssu/community-thumb/pool/free/libx/libxml2/ |
| 17:38.33 | kerio | yeah, apt-get is weird |
| 17:38.52 | kerio | freemangordon: well, even the non-thumby one should work now, right? |
| 17:39.02 | freemangordon | kerio: no |
| 17:39.12 | freemangordon | afaik |
| 17:39.14 | kerio | still the dependency issue? |
| 17:39.18 | kerio | oh well |
| 17:39.26 | freemangordon | Pali: where did you get that from? |
| 17:39.40 | Pali | I have no idea |
| 17:39.46 | Pali | I only used apt-get |
| 17:40.05 | Pali | freemangordon, we need some tool which list packages with higher version in status |
| 17:40.26 | kerio | Pali: the issue is just -thumb |
| 17:40.49 | kerio | instead of +thumb |
| 17:41.06 | kerio | right now, only xserver-xomap, xserver-xorg-core and fennec have that "problem" |
| 17:41.16 | freemangordon | Pali: WTF? |
| 17:41.19 | freemangordon | https://gitorious.org/community-ssu/libxml2/commit/cf3eba1ba26ad5d323f28df38d4c94ca9a95bb94 |
| 17:41.21 | kerio | and it's not a problem in fennec's case, because the next version would be 18 anyway |
| 17:41.25 | freemangordon | 3 months ago |
| 17:41.44 | kerio | Pali: dpkg -l | grep -- -thumb |
| 17:41.49 | kerio | (and ignore hildon-thumbnail) |
| 17:41.53 | freemangordon | yep, very good idea |
| 17:42.15 | Pali | we have similar script in cssu disabler |
| 17:42.27 | Pali | which find packages which are not in any repo |
| 17:42.34 | freemangordon | Pali: check for similar please |
| 17:42.35 | kerio | Pali: and what do you do with those? |
| 17:43.19 | freemangordon | Pali: you don't upgrade with HAM, do you :P |
| 17:43.45 | kerio | anyway, just pin the whole repo at 1001 priority |
| 17:43.50 | kerio | so it'll "downgrade" to its latest version |
| 17:43.58 | kerio | willingly, i mean |
| 17:44.06 | freemangordon | kerio: no |
| 17:44.19 | freemangordon | it will get higher priority that -T then |
| 17:44.24 | freemangordon | aiui |
| 17:44.34 | kerio | freemangordon: just to fix the versions i mean |
| 17:44.38 | kerio | then put it back at normal |
| 17:44.45 | kerio | i actually have community-thumb at priority 600 |
| 17:44.52 | kerio | so i won't actually go through cssu-testing |
| 17:44.56 | freemangordon | aah, ok |
| 17:53.43 | DocScrutinizer05 | btw I witnessed one user who probably fubared his system by "uninstalling" CSSU |
| 18:02.55 | DocScrutinizer05 | took like two days on #maemo to do the 1st-level-helpdesk for that user, and sorry I can't recall any details anymore, just that my conclusion been that CSSU uninstall is flawed by concept, never can work under certain conditions and most likely should get nuked |
| 18:05.10 | DocScrutinizer05 | similarly that set of catalogs in HAM eventually MUST vanish, since lusers can't be stopped to enable e.g. CSSU-devel catalog, once it's available under catalogs |
| 18:07.45 | kerio | DocScrutinizer05: +1, cssu-devel is dangerous, and we don't really need the domain information for it, people who are supposed to use it are knowledgeable enough to use apt |
| 18:07.54 | kerio | to test HAM deployment there's cssu-future |
| 18:09.21 | DocScrutinizer05 | I also don't get the rationale to have CSSU-T repo in CSSU-S catalog list |
| 18:09.36 | DocScrutinizer05 | this has to go away |
| 18:09.59 | DocScrutinizer05 | catalogs that are there will inevitably get enabled |
| 18:10.17 | DocScrutinizer05 | that's joe average user's nature |
| 18:10.19 | kerio | i'm not sure if you can add the domain information without the catalogs though |
| 18:12.35 | DocScrutinizer05 | if there's no way to manage catalogs in a sane way via HAM catalogs GUI, cssu must ship enabler for users to run, or exploit red-pill-mode in HAM or whatever |
| 18:13.35 | DocScrutinizer05 | no way CSSU-T or even CSSU-S shall ever ship e.g. CSSU-devel catalog preconfigured. Same applies for CSSU-T catalog in CSSU-S |
| 18:14.32 | merlin1991 | hm we discussed this quite some time ago |
| 18:14.39 | DocScrutinizer05 | no normal user of CSSU-S will ever want to get CSSU-T or CSSU-devel catalog enabled |
| 18:14.49 | merlin1991 | what was the problem with putting each catalog into a own package? |
| 18:15.07 | DocScrutinizer05 | for those who know what they're doing, we could ship enabler binary to run |
| 18:15.55 | DocScrutinizer05 | if that's even needed, since those experts should be able to edit config files |
| 18:17.54 | *** join/#maemo-ssu MrPingu (~chatzilla@86.92.226.97) |
| 19:06.31 | *** join/#maemo-ssu freemangordon (~freemango@130-204-50-168.2074221835.ddns.cablebg.net) |
| 19:23.37 | *** join/#maemo-ssu dafox (~dafox@ip51cc571d.speed.planet.nl) |
| 19:24.05 | *** join/#maemo-ssu nox- (noident@freebsd/developer/nox) |
| 19:38.09 | dafox | hi all. I just wanted to thank you for making -thumb possible, and for helping me set up -thumb. It seems to be working great :) |
| 19:41.49 | freemangordon | luf: https://gitorious.org/community-ssu/libhildonfm/commit/f40a6ed07054380b34eaac995e8d19df1c8657f2 |
| 19:47.32 | DocScrutinizer05 | dafox: for all we know -thumb is working fine, just a tad cumbersome when you have to reflash or anything |
| 19:47.51 | DocScrutinizer05 | since there's no way back from a thumb system to a stock one |
| 19:58.03 | dafox | I think (hope) that -thumb is the future for the cssu, and that there will be no need to go back :) |
| 20:00.26 | DocScrutinizer05 | dafox: well, it's not about 2downgrading", it's about stock resources missing support for thimb, resulting in a broken system when user does not follow exactly the right sequence of things to do in a reflash for example |
| 20:01.37 | dafox | I'm sorry, I don't understand? Are you saying that with -thumb it is possible to have a non-working phone, even after re-flash? |
| 20:01.40 | DocScrutinizer05 | for instance installing uBoot to a cssu-thumb system already renders your system bootlooping due to uBoot coming with stock kernel |
| 20:02.29 | kerio | dafox: to run thumb2 binaries, you need a particular patch in the kernel you're running |
| 20:02.49 | DocScrutinizer05 | doing a reflash to stock and then restoring apps etc again renders system bootlooping, since you need a kernel supporting thumb |
| 20:02.51 | kerio | if that patch is lacking, shit will not fly |
| 20:03.15 | dafox | yes, I understood that, but I thought that reflashing reverted everything to stock (includign the kernel) |
| 20:03.32 | kerio | dafox: reflashing will give you a working system |
| 20:03.39 | kerio | it's not your system though |
| 20:03.43 | DocScrutinizer05 | dafox: that's exactly the problem |
| 20:04.52 | kerio | basically, you have to be very wary of what kernel you flash |
| 20:05.04 | DocScrutinizer05 | dafox: the only working sequence of things to do to reflash is: reflash Pr1.3 fiasco, insatll most recent powerkernel, only _then_ restore your system from your backup |
| 20:06.07 | kerio | DocScrutinizer05: actually, not really :) |
| 20:06.17 | DocScrutinizer05 | maybe I forgot ath |
| 20:06.18 | kerio | kernel-cssu has a different uname than kernel-power |
| 20:06.19 | DocScrutinizer05 | sth |
| 20:06.38 | DocScrutinizer05 | mhm |
| 20:06.41 | kerio | so it won't load the modules, even if they're pretty much the same |
| 20:07.06 | freemangordon | kerio: which modules? |
| 20:07.07 | DocScrutinizer05 | my point is it's not exactly foolproven |
| 20:07.13 | kerio | freemangordon: dem modules |
| 20:07.31 | freemangordon | is it backupmenu we talk about? |
| 20:07.36 | kerio | yep |
| 20:07.47 | dafox | aha, ok. So I've never had to restore a backup before. I always back up both optfs and rootfs, so does that then not include the kernel? |
| 20:07.48 | kerio | there's no easy way to install kernel-cssu on pr1.3 |
| 20:08.02 | freemangordon | kerio: what? |
| 20:08.06 | kerio | dafox: the kernel is in a separate partition |
| 20:08.07 | DocScrutinizer05 | dafox: nope |
| 20:08.16 | kerio | freemangordon: say you accidentally the whole system |
| 20:08.24 | dafox | ok, so simply restoring from backup without flashing works ok |
| 20:08.25 | kerio | you have BM backups made when you had kernel-cssu |
| 20:08.48 | kerio | to restore them with backupmenu you have to reflash pr1.3 |
| 20:08.50 | freemangordon | kerio: enable cssu-thumb repo in HAM, and you're fine |
| 20:08.50 | kerio | install backupmenu |
| 20:09.01 | freemangordon | cssu-thumb will appear |
| 20:09.01 | kerio | install kernel-cssu from the cssu-thumb repo |
| 20:09.03 | kerio | then restore |
| 20:09.38 | dafox | wasn't there an option in the flasher to flash the kernel only? Or some way to flash just a kernel? |
| 20:09.44 | freemangordon | and? i'd rather say this is a problem of BM, not -thumb |
| 20:09.52 | kerio | freemangordon: indeed |
| 20:09.53 | DocScrutinizer05 | dafox: yes |
| 20:09.56 | freemangordon | dafox: yes, there is |
| 20:09.57 | kerio | but it's also a problem of cssu-thumb users :) |
| 20:10.10 | kerio | dafox: yep, you'd have to install backupmenu on a fresh system to load the backup |
| 20:10.17 | kerio | then flash the appropriate kernel |
| 20:10.20 | kerio | then you can boot again |
| 20:10.42 | freemangordon | kerio: so, we conclude that -thumb users are screwed, because some third-party app does not support kernel restore? meh |
| 20:11.01 | kerio | my, how defensive |
| 20:11.06 | DocScrutinizer05 | freemangordon: we didn't conclude anything like that |
| 20:11.34 | dafox | suppose that you mess this up somehow (-thumb restored userspace, non -thumb kernel), could you still flash the system? |
| 20:11.42 | kerio | dafox: yep |
| 20:11.57 | kerio | there's very little that you can do on the software side to really ruin a N900 |
| 20:12.08 | DocScrutinizer05 | indeed |
| 20:12.11 | freemangordon | dafox: as a general rule - nothing can stop you from flashing but broken USB port :) |
| 20:12.14 | dafox | ok, I'm not really seeing the problem then... besides having a momentarily unbootable n900 |
| 20:12.27 | kerio | even blowing up CAL leaves you with an almost completely working n900 |
| 20:12.32 | kerio | you're basically missing bluetooth at that point |
| 20:12.44 | kerio | and toying with bluetooth-sysinfo would fix that, too |
| 20:12.44 | freemangordon | kerio: wifi MAC is not in CAL? |
| 20:12.53 | DocScrutinizer05 | dafox: it's just cumbersome, not a "problem" |
| 20:12.57 | kerio | freemangordon: iirc sambo7 (the nandtester) had working wifi and phone |
| 20:13.15 | kerio | freemangordon: is there a way to rebuild a CAL? |
| 20:13.24 | freemangordon | hmm, good. i've always tought wifi MAC is in CAL |
| 20:13.29 | freemangordon | kerio: sure |
| 20:13.31 | DocScrutinizer05 | [2013-01-08 20:47:31] <DocScrutinizer05> dafox: for all we know -thumb is working fine, just a tad cumbersome when you have to reflash or anything |
| 20:13.42 | dafox | but doesn't the only way to 'break' this already include flashing a new kernel? Flashing = cumbersome? |
| 20:13.46 | freemangordon | kerio: acrually it rebuilds by itself |
| 20:14.07 | kerio | freemangordon: ...really? :o |
| 20:14.14 | kerio | even after writing random data to its partition? |
| 20:14.21 | kerio | hm, maybe you need a flash_eraseall on it |
| 20:14.36 | DocScrutinizer05 | dafox: you still don't get it. The flashing resets your kernel, and that *is* your problem |
| 20:14.41 | freemangordon | kerio: CAL has 2 system and one user part |
| 20:15.26 | kerio | dafox: you need to unreset it from your pc's side |
| 20:15.27 | freemangordon | those 2 are used as some kind of RAID1 |
| 20:15.38 | kerio | aka download the kernel-cssu deb, unpack it, grab the .fiasco and flash it |
| 20:15.53 | freemangordon | if both become unusable, libcal writes to the first |
| 20:15.57 | dafox | DocScrutinizer05: we're talking about the sequence flash pr1.3 -> install backupmenu -> restore breaking boot, right? |
| 20:15.58 | kerio | neat |
| 20:16.13 | DocScrutinizer05 | dafox: basically yes |
| 20:16.25 | kerio | dafox: yep, you have to do flash pr1.3 -> install backupmenu -> restore -> flash kernel-cssu |
| 20:16.29 | freemangordon | kerio: you can install it from the device, no need of a PC |
| 20:16.41 | kerio | or that^ |
| 20:16.49 | freemangordon | and anyway you need a PC to flash it |
| 20:17.01 | kerio | freemangordon: it's actually faster to flash it from a PC though, if you have to restore a full backup anyway |
| 20:17.27 | dafox | DocScrutinizer05: ok, but what I was thinking is that why do I need to reflash to restore? Can't one just boot backup menu and restore, without reflashing pr1.3? |
| 20:17.28 | kerio | dafox: or, if you haven't changed the kernel, boot from rescueOS -> untar |
| 20:17.40 | kerio | dafox: if you can still run it, sure |
| 20:17.43 | kerio | then you avoid all problems |
| 20:17.45 | freemangordon | dafox: :nod: |
| 20:17.47 | DocScrutinizer05 | dafox: usually yes |
| 20:17.59 | DocScrutinizer05 | dafox: unless you entered a bootloop or sth |
| 20:18.28 | freemangordon | isn;t BM part of preinit script? |
| 20:18.33 | dafox | I think backupmenu is like grub, in that it runs before the kernels boots |
| 20:18.38 | dafox | no? |
| 20:18.53 | DocScrutinizer05 | there are however situations where you need a reflash, and then it becomes cumbersome to restore your complete thumb system |
| 20:19.01 | kerio | dafox: nope, bootmenu runs after the kernel is loaded |
| 20:19.29 | kerio | DocScrutinizer05: we really need robbiethe1st to port backupmenu to rescueos :) |
| 20:19.29 | *** join/#maemo-ssu kolp_ (~quassel@212.255.37.28) |
| 20:19.38 | DocScrutinizer05 | :nod: |
| 20:19.49 | DocScrutinizer05 | and include kernel backup |
| 20:20.14 | dafox | recently I noticed backup menu offering to boot from a different partition or something, so that does something weird to replace the running kernel then? |
| 20:20.25 | MrPingu | Basically it's tarring the whole partition, no? |
| 20:20.42 | kerio | MrPingu: the whole partitions |
| 20:20.50 | DocScrutinizer05 | MrPingu: nope, it tars the whole fs |
| 20:20.59 | kerio | ..er, yes |
| 20:21.18 | DocScrutinizer05 | BM basically doesn't know about partitions |
| 20:21.26 | kerio | on restore, it cleans the ubifs partition from all files - possibly because nobody really understands ubi and ubifs |
| 20:21.29 | DocScrutinizer05 | it's no disk image |
| 20:21.40 | kerio | then does mkfs.ext3 on the homefs/optfs |
| 20:21.43 | kerio | and untars there |
| 20:21.45 | dafox | DocScrutinizer05: ok, I understand now, so you have two steps involving the flasher, instead of just one |
| 20:21.54 | kerio | ...and of course also untars the rootfs image on the rootfs |
| 20:21.56 | DocScrutinizer05 | yep |
| 20:22.09 | MrPingu | Isn't that easy to write just an script for and need to be issued by user, in rescueOS |
| 20:22.12 | kerio | dafox: or you have to install kernel-cssu in your newly-flashed system |
| 20:22.26 | DocScrutinizer05 | though one of them can be done on-board with N900 flasher |
| 20:22.27 | kerio | MrPingu: backupmenu has such a cute interface, though :c |
| 20:22.40 | DocScrutinizer05 | or what kerio said ^^^ |
| 20:22.50 | dafox | ok, this is all very good to know :) |
| 20:23.16 | MrPingu | kerio: you beat me |
| 20:24.00 | DocScrutinizer05 | o/ |
| 20:24.23 | DocScrutinizer05 | bbl, need to have a shower and then coordinate migration a tad further |
| 20:24.43 | DocScrutinizer05 | ivgalvez back and well! \o/ |
| 20:25.20 | kerio | yay :D |
| 20:25.24 | freemangordon | good |
| 20:25.29 | DocScrutinizer05 | yep |
| 20:25.54 | DocScrutinizer05 | I should probably post it on #maemo as well |
| 20:27.23 | kerio | dafox: the N900 can be ridiculously restorable |
| 20:28.02 | kerio | you've got the usb flashing, which pretty much works every time, at worst you have to coldflash the bootloader first |
| 20:28.24 | kerio | i've got uboot as my kernel, so at worst i can load something on a uSD and boot from there |
| 20:28.39 | kerio | i've got rescueOS installed, which gives me a clean system with a shell and some restore tools |
| 20:29.21 | kerio | after the maemo kernel is loaded, i've got bootmenu, which gives me usb mass storage and usb networking |
| 20:29.35 | kerio | and the bootmenu recovery console, which gives me an on-device shell too |
| 20:29.50 | kerio | then there's backupmenu, which has all the nifty backup restore stuff |
| 20:57.12 | dafox | heh, n900 <3 :D (although I've only installed backup menu) |
| 21:06.22 | kerio | dafox: what do you mean? :o |
| 21:06.27 | kerio | when have you got your n900? |
| 21:07.06 | dafox | a bit more then a year ago (christmas 2011) |
| 21:08.02 | kerio | oh, i misunderstood you |
| 21:09.41 | dafox | I'm pretty happy with it, my old phone really was old (sony-ericsson p800) |
| 21:16.16 | kerio | bet on WizardNumberNext being a gentoo user |
| 21:16.44 | MrPingu | why? |
| 21:17.10 | kerio | dammit! |
| 21:17.38 | freemangordon | kerio: fun, isn;t it? :D:D:D |
| 21:20.50 | dafox | nice way to categorize people |
| 21:25.34 | kerio | bet on dafox being a gentoo user |
| 21:25.50 | dafox | guily as charged :p |
| 21:25.51 | MrPingu | What am I? :P |
| 21:25.53 | dafox | *guilty |
| 21:35.17 | *** join/#maemo-ssu kolp (~quassel@212.255.37.28) |
| 21:38.26 | *** join/#maemo-ssu xxxxxxx (~MrPingute@86.92.226.97) |
| 21:39.42 | *** join/#maemo-ssu ekze (~nyan@bakaekze.ru) |
| 21:42.17 | *** join/#maemo-ssu MrPingu (~MrPingute@86.92.226.97) |
| 21:46.47 | *** join/#maemo-ssu arcean (~arcean@aacr234.neoplus.adsl.tpnet.pl) |
| 22:01.07 | *** join/#maemo-ssu MrPingu (~MrPingute@86.92.226.97) |
| 22:03.41 | amiconn | is somewhat confused |
| 22:04.29 | amiconn | I have cssu thumb installed (updated from cssu-t), but now ham offers a (plain?) cssu upgrade. Should I remove/ disable the plain cssu repository? |
| 22:04.47 | freemangordon | amiconn: refresh |
| 22:05.13 | amiconn | I didn't migrate today, but a few days ago |
| 22:05.33 | freemangordon | still, refresh, there is newer -thumb |
| 22:05.42 | amiconn | Ah, today it's not the same offer, it's -thumb again |
| 22:05.57 | amiconn | But anyway, should plain cssu-t repo be disabled or not? |
| 22:06.16 | MrPingu | basically thumb = testing |
| 22:06.25 | freemangordon | amiconn: no |
| 22:07.06 | amiconn | MrPingu: Yeah, but if testing gets an update (usually a bit earlier than thub) I suspect it would migrate a buch of packages back to non-thumb |
| 22:07.47 | MrPingu | amiconn: yes, that's right. Because thumb doesn't version number |
| 22:07.47 | amiconn | Als ham got even slower with the addition of the cssu-thumb repo |
| 22:07.55 | amiconn | *Also |
| 22:07.59 | MrPingu | *change |
| 22:08.11 | MrPingu | that's also true |
| 22:08.37 | MrPingu | whenever theres a new version of testing version numbers increase |
| 22:09.10 | MrPingu | so it pulls the latest but doesn't care if it's thumb or non-thumb |
| 22:09.11 | amiconn | Yeah, hence my question |
| 22:09.50 | amiconn | The only reason that would speak against disabling plain cssu-t repo is if the thumb repo is incomplete |
| 22:09.57 | kerio | yep |
| 22:10.01 | amiconn | But this is what I don't know |
| 22:11.44 | MrPingu | Enjoy this update, you won't be getting a new update soon :P :P :P |
| 22:17.33 | *** join/#maemo-ssu joshgillies (~josh@hobart.office.squiz.net) |
| 22:36.17 | DocScrutinizer05 | amiconn: basically there's no proper upgrade strategy for cssu-thumb. You'll face same "issues" each time cssu-t gets a new upgrade. Since cssu-thumb is just a "patch" on top of cssu-t |
| 22:37.34 | DocScrutinizer05 | for cssu-thumb to become a proper "distro" it would need to port all cssu-t packages to thumb repo and disable cssu-t |
| 22:37.57 | freemangordon | which makes no sense :) |
| 22:38.17 | DocScrutinizer05 | for now it only has those pkgs that are actually thombified |
| 22:38.28 | freemangordon | :nod: |
| 22:38.55 | DocScrutinizer05 | and that will cause conflicts with the pkgs in those repos it's basing on |
| 22:39.21 | freemangordon | could some who has stock tklock installed test something for me? |
| 22:39.37 | DocScrutinizer05 | as soon as there are upgrades that are not in thumb repo yet, but thumb has an older thumbified version of those pkgs |
| 22:40.36 | freemangordon | set display backlight timeout to 10 seconds, wait for screen to lock and unlock with slider. Now check after what time the screen will get locked again. is it 10s? |
| 22:40.58 | DocScrutinizer05 | actually I think CSSU-T does same mess with original Nokia repos on which it is basing, but we rarely see issues there since upgrades on Nokia repos are highly unlikely |
| 22:41.20 | freemangordon | anyone? ^^^ |
| 22:41.29 | DocScrutinizer05 | wait 20 s ;-D |
| 22:41.30 | freemangordon | DocScrutinizer05: could you test that for me? |
| 22:41.32 | freemangordon | ok |
| 22:41.42 | *** join/#maemo-ssu BCMM (5c159c50@gateway/web/freenode/ip.92.21.156.80) |
| 22:43.13 | DocScrutinizer05 | dim after 10, off after another 4 orso |
| 22:43.50 | freemangordon | did you unlock with visual slider? |
| 22:43.58 | DocScrutinizer05 | nah, with slider switch |
| 22:44.03 | freemangordon | no, use visual |
| 22:44.13 | DocScrutinizer05 | err, how? |
| 22:44.21 | freemangordon | press power button |
| 22:44.29 | freemangordon | and slide-to-unlock |
| 22:44.47 | freemangordon | you may need to press power button teice |
| 22:44.53 | freemangordon | *twice |
| 22:45.13 | DocScrutinizer05 | meh 30 and still on |
| 22:45.17 | freemangordon | yep |
| 22:45.30 | DocScrutinizer05 | still on |
| 22:45.34 | freemangordon | I thought it is bug in tklock replacement :D |
| 22:45.45 | freemangordon | but it seems it is by design |
| 22:45.46 | DocScrutinizer05 | noooow |
| 22:45.52 | freemangordon | or bug in mce |
| 22:46.05 | DocScrutinizer05 | unlocked |
| 22:46.12 | freemangordon | some 60s? |
| 22:46.21 | DocScrutinizer05 | 20 |
| 22:46.31 | DocScrutinizer05 | 30 |
| 22:46.51 | DocScrutinizer05 | 50 |
| 22:47.07 | DocScrutinizer05 | 60 |
| 22:47.20 | DocScrutinizer05 | dim after 70 |
| 22:47.26 | freemangordon | nice :D |
| 22:47.40 | DocScrutinizer05 | o/& |
| 22:47.43 | freemangordon | well, not much that we can do, mce is closed :( |
| 22:48.05 | DocScrutinizer05 | I never use that method to unlock |
| 22:48.19 | freemangordon | you will ruin your slider swith ;) |
| 22:48.29 | DocScrutinizer05 | lockswitch works as supposed |
| 22:48.34 | freemangordon | sure |
| 22:49.02 | DocScrutinizer05 | I rather uin my powerbuttons usually, and scratch my screen |
| 22:49.20 | freemangordon | however, thanks |
| 22:49.25 | DocScrutinizer05 | my lockswitch is fine |
| 22:49.30 | DocScrutinizer05 | o/ |
| 22:49.32 | DocScrutinizer05 | afk |
| 22:50.33 | DocScrutinizer05 | btw my timeout been 60 before I set it to 10 for you. 70 = 60 + 10 FWIW |
| 22:50.51 | DocScrutinizer05 | no, I won't reboot with timeout set to 10 |
| 22:50.52 | freemangordon | hmm, yeah, could be that |
| 22:51.04 | freemangordon | DocScrutinizer05: have 1 more minute? |
| 22:51.11 | freemangordon | for another test |
| 22:51.13 | DocScrutinizer05 | sorry, nope |
| 22:51.18 | freemangordon | ok |
| 22:51.42 | DocScrutinizer05 | post instructions, maybe later |
| 22:52.32 | freemangordon | DocScrutinizer05: while on desktop, wait for screen to dim(not lock) and press it. do you see h-d settings button to appear? |
| 22:52.57 | DocScrutinizer05 | never |
| 22:53.06 | freemangordon | hmm, try it |
| 22:53.22 | DocScrutinizer05 | I "try" that 20 to 100 times a day |
| 22:53.22 | freemangordon | i remember i've seen that, but I am not sure |
| 22:53.53 | DocScrutinizer05 | first touch even get swallowed by something, during dim |
| 22:54.10 | DocScrutinizer05 | I think there's a setting for that in mce.ini |
| 22:54.12 | freemangordon | but not when on desktop |
| 22:54.27 | freemangordon | it is called "event eater" :D |
| 22:54.29 | DocScrutinizer05 | ok, I'll try it |
| 22:54.33 | DocScrutinizer05 | :-/ |
| 22:56.12 | DocScrutinizer05 | answer stays: nope |
| 22:56.17 | freemangordon | ok, thanks |
| 22:56.55 | DocScrutinizer05 | check mce.ini! |
| 22:57.04 | freemangordon | nah, it is tklock |
| 22:57.18 | DocScrutinizer05 | *sigh* |
| 22:58.32 | DocScrutinizer05 | [TKLock] |
| 22:58.33 | DocScrutinizer05 | # Blank immediately instead of dim before blank when tklock is enabled |
| 22:58.59 | DocScrutinizer05 | .. |
| 22:59.00 | freemangordon | DocScrutinizer05: it is some bug in my replacement |
| 22:59.02 | DocScrutinizer05 | # Policy for touchscreen interrupts |
| 22:59.04 | DocScrutinizer05 | # |
| 22:59.05 | DocScrutinizer05 | # 1 - disable immediately |
| 22:59.06 | DocScrutinizer05 | # 0 - wait until display is blanked |
| 22:59.08 | DocScrutinizer05 | DisableTSImmediately=1 |
| 22:59.27 | DocScrutinizer05 | fool! |
| 22:59.34 | freemangordon | :D |
| 22:59.44 | DocScrutinizer05 | when I suggest to check mce.ini, you should consider it |
| 23:00.04 | freemangordon | DocScrutinizer05: i've just reinstalled stock |
| 23:00.11 | freemangordon | and tested |
| 23:00.20 | freemangordon | settings button does not appear |
| 23:00.39 | freemangordon | this pretty enough for me |
| 23:00.56 | DocScrutinizer05 | since stock checks DisableTSImmediately=1 |
| 23:01.21 | freemangordon | no, this tells mce what to send to tklock |
| 23:01.24 | DocScrutinizer05 | if you "fix" yours, you're swapping one bug for another |
| 23:01.29 | freemangordon | and it is tklock who does the work |
| 23:01.38 | DocScrutinizer05 | mhm |
| 23:01.40 | DocScrutinizer05 | maybe |
| 23:02.08 | freemangordon | and I fail to "eat" the event when on the desktop |
| 23:02.16 | freemangordon | for some reason I am going to check |
| 23:02.17 | DocScrutinizer05 | :nod: |
| 23:05.02 | DocScrutinizer05 | you're right, DisableTSImmediately=1 works globally, not only on desktop |
| 23:05.18 | freemangordon | yep |
| 23:05.53 | DocScrutinizer05 | I never had a doubt on this, but it occurred to me just now |
| 23:07.26 | DocScrutinizer05 | btw qt is fecked, it takes pen-down events for button-activate, instead of the worldwide usual pen-up |
| 23:07.59 | DocScrutinizer05 | I noticed that in calculator |
| 23:10.56 | DocScrutinizer05 | actually the stnadard correct GUi behaviour is to button-press *only* on pen-down followed by pen-up in same widget |
| 23:11.04 | freemangordon | oh, the fuck, got it. h-d reacts on release event :( |
| 23:11.27 | DocScrutinizer05 | tadaa we're on topic |
| 23:11.33 | DocScrutinizer05 | ;-P |
| 23:11.34 | freemangordon | yep |
| 23:11.49 | freemangordon | so I should play it smart there :D |
| 23:12.21 | DocScrutinizer05 | you can neither slide out of a button nor slide in, to press it |
| 23:12.46 | DocScrutinizer05 | you need to press and release on same button to make button-push |
| 23:13.48 | DocScrutinizer05 | except for *very* special cases like stopwatch (which usually fails to do so ;-P) |
| 23:14.27 | DocScrutinizer05 | instead, fekkin calculator does |