[00:00] asac___: what was the command for sign-off/releasing? [00:00] fta: the bug sounds ... [00:01] fta: so yeah. when i am back from holiday i will try to get that in [00:01] asac___, "No, Debian's fine. This is only in Ubuntu." [00:01] fta: run-mailcap.diff comes from debian [00:01] whether they are fine or not is nothing i said ;) [00:01] it's the last comment in the bug [00:02] http://code.google.com/p/chromium/issues/detail?id=19987 [00:03] asac___, ^^ we have a sync from debian so i don't understand [00:03] yes [00:04] commented === asac___ is now known as asac [00:10] fta: anyway. i think the xdg-mime > mailcup-run > BROWSER approach is something worth considering; one would have to do some research though how that is behaving in non DE environments etc. [00:10] but most likely its just the right approach to do both [00:17] ok [00:18] asac: https://code.launchpad.net/~bdrung/mozilla-devscripts/version-0.15/+merge/10558 [00:18] asac: i removed the 0.15 tag === Grantbow_ is now known as Grantbow [00:22] asac, isn't "foo Depends bar (= ${binary:Version})" enough to make sure that foo and bar are always in sync? (foo is arch, bar is all-arch) [00:29] hm, if amd64 is built 1st, a user can upgrade the browser without the lang packs still waiting for the i386 build to complete.. i should add a conflict there [00:35] asac: also uploaded to mentors: http://mentors.debian.net/debian/pool/main/m/mozilla-devscripts/mozilla-devscripts_0.15.dsc [00:49] fta: i think thats not always the case [00:49] think about you depending on a arch all package from a any package [00:49] and you do a binary NMU ... the arch package would not be updated most likely [00:50] bdrung: so pull does not work ;) [00:51] let me try to branch locally first ;) [00:51] pull does not work? [00:52] not in a bound branch [00:52] i did pull --local now [00:52] launchpad seems to be problematic ;) [00:52] now trying to push ;) [00:52] ok that worked [00:53] maybe bzr now opens concurrent connections when pulling multiple revisions into a bound branch === rickspencer3 is now known as rickspencer3-afk [00:57] asac, bin nmu, looks like debian to me [00:58] yes [00:58] but we use the same techniques in most cases [00:58] at lesat if someone ask: "is this enough ..." ;) [00:58] http://code.google.com/p/chromium/issues/detail?id=19694 [00:59] i have: chromium-browser-l10n depends on chromium-browser (= ${binary:Version}) [01:00] bdrung: uploaded [01:00] even if the bug doesn't look ubuntu to me, i realize now I have a race, so i need a conflict, or a break in chromium-browser [01:00] or something [01:00] thanks [01:01] (imho, you're releasing m-d too fast) [01:01] fta: i wanted to get this up before holiday ;) [01:01] ... also ... release fast and often ;) [01:02] and both debian and ubuntu ard not yet approaching release ;) [01:02] asac: I introduced myself to the Developers :) [01:02] hehe [01:03] micahg: seems they like you ;) [01:04] asac, so? [01:04] asac: I think I can reproduce the bug in Jaunty [01:04] at least part of it [01:04] good [01:04] so we can rule that out [01:05] fta: on what? [01:05] the depends? [01:05] yes [01:05] http://paste.ubuntu.com/257233/ that's today [01:05] it seems to me -l10n could be out of sync [01:06] fta: what do you think is the problem of the bug? [01:06] the packages not being forced to the right version? [01:06] the l10n not from the same build as the browser [01:06] ok you think they could be. let me see [01:08] fta: is anything run during post/pre scripts? [01:08] some l10n processing/compilation maybe or so? [01:08] no [01:09] then the depends should be enough imo [01:09] what if the amd/lpia builds are done 1st, and a user upgrade? [01:09] fta: maybe its unclear how to grab the right sources? so you dont have the right translations in the source? [01:10] no, the l10n files (which are in fact .grd files) are generated during the build [01:10] were from? [01:10] are the translations in the same directory as the code that uses them? [01:10] yes [01:10] really? [01:11] so i have main.c [01:11] and then i have main.c.grd ? [01:11] no [01:11] and then i have main.c.grd.fr .en .es ;) ? [01:11] yeah [01:11] eg http://src.chromium.org/svn/trunk/src/chrome/app/resources/locale_settings.grd [01:12] [01:12] or http://src.chromium.org/svn/trunk/src/chrome/browser/browser_resources.grd [01:12] where is the input file? [01:12] there are no translated strings either [01:13] hmm there seem to be but those dont look like the translations [01:13] rather like the "default/fallback" [01:13] fta: i wouldnt add the breaks t the l10n package [01:14] the depends alone should prevent it from upgrading chrome-browser without removing -l10n [01:14] http://src.chromium.org/svn/trunk/src/chrome/app/resources/google_chrome_strings_de.xtb [01:15] ok [01:15] i dont know. in worst case its a bug in lzma ;) [01:15] lol [01:15] or the sources were really not in [01:15] sync [01:16] Breaks: chromium-browser (<< 3.0.197.0~svn20090804r22432) [01:16] Replaces: chromium-browser [01:16] do you need this unversioned replaces? [01:17] hm, it was when i split the package [01:17] yeah since you maintain everything from same branch you can just make it versioned [01:17] << WHATEVERVERSIONYOUDIDTHEMIGRATION [01:18] anyway. i would hope thats not the problem (though you should consider it) [01:18] so the same as the breaks [01:18] so i would triple check that the sources i used are really what they expect them to be and ask the submitter to submit information about package verions etc. [01:19] eh? [01:19] how sure are you that the strings that are wrong for the french guy were/are really right in the sources? [01:19] identifying how those are different might help [01:19] if they are really daily changes then it might be a pointer to investigate further ;) [01:20] he pasted rpm with 2 different versions [01:20] the rpm seems to be repacks from my debs [01:20] -s [01:20] yeah so an eventual version diff because of arch all/any can be ruled out [01:20] which probably mean that the packaging is maybe missing some pieces? [01:21] fta: try to force the same dailies [01:21] and see if it works [01:21] if thats the case then its upstream out-of-sync issue [01:21] which i would think is a likely thing for dailies from trunk ;) [01:21] but i dont know upstream translation polices ... nor do i see from the bug how many strings are wrong [01:21] i never experienced this bug myself, i was just trying to figure out if it can happen [01:22] great. i cannot open pngs directly there [01:23] fta: what does the text mean that is in lowest thign? [01:23] that seems to explode the window [01:23] that big button (greyed out) [01:24] avez choisi d'ouvrir automatiquement certain types de fichier ... [01:24] how is "Desktop" called on french desktops? [01:24] if you install it as french from scratch i mean [01:25] do we translate that= [01:25] hmm. they use Download ;) [01:25] but still ... maybe it has something to do with how the french dir name is named [01:27] Desktop is Bureau in french [01:28] from what i understand, the guy said langpack generated with one build are not usable in another build [01:29] but no idea if that's correct [01:29] fta: what do they produce? [01:29] can you check if you can find this overly long string somewhere? [01:30] i doubt that its in the source [01:30] $ file /usr/lib/chromium-browser/locales/fr.pak [01:30] /usr/lib/chromium-browser/locales/fr.pak: data [01:30] looks like a mixup [01:30] comment 4 shows: [01:30] $ rpm -q chromium-browser chromium-browser-l10n [01:30] chromium-browser-4.0.203.0~svn20090818r23670-1.i386 [01:30] chromium-browser-l10n-4.0.202.0~svn20090813r23308-1.noarch [01:31] so it's not the same upstream version [01:31] i have no difficulty to understand that it may give bad results [01:31] yes [01:31] it obviously doesnt break if strings are still ok [01:32] question is if out of sync translations often break it [01:32] in #10, he said "OK, it's OK if both program & l10n data are synced, aka the same SVN rev." [01:32] i would hope not [01:32] otherwise they are doing something wrong [01:32] everything worse than gettext would be a step back [01:32] he's doing weird stuff with the package, not our problem, but could we have the same situation with the PPA? [01:32] fta: i really think you should just verify this reall ylong string. maybe its easy to see once you see how and wher that is typed ;) [01:33] fta: no [01:33] we are synched [01:33] the depends should be enough imo [01:33] you need conflicts/replaces only to transition stuff [01:34] $ find . -print0 | xargs -0 grep 'ouvrir automatiquement certains types' [01:34] ./src/chrome/app/resources/generated_resources_fr.xtb:Vous avez choisi d'ouvrir automatiquement certains types de fichiers après leur téléchargement. Vous pouvez changer ces paramètres afin que les fichiers téléchargés ne s'ouvrent pas automatiquement. [01:34] yeah [01:35] so question is where that is coming from [01:35] check the template used [01:35] $ find . -print0 | xargs -0 grep 724208122063442954 | pastebinit [01:35] http://paste.ubuntu.com/257247/ [01:35] yeah [01:35] fta: whats the english text for that? [01:35] in the source? [01:35] oh those are generated [01:35] is there a similar entry in source? [01:36] this is from a tarball, not from a build [01:36] ok and the english id? [01:37] thats not english ;) [01:37] oops [01:37] i scrolled up ;) [01:38] [01:38] You have chosen to open certain file types automatically after downloading. You can clear these settings so that downloaded files don't open automatically. [01:38] [01:39] yeah. but somehoe the english text in teh screenshot is a different string [01:39] so the ids have a mismatch [01:39] means: they are out of sync in the tree i guess [01:39] i guess the real string is a few before or after ;) [01:40] those 724208122063442954 numbers are coming from somewhere, but no idea from where [01:40] where is IDS_OPTIONS_AUTOOPENFILETYPES_INFO mapped to 724208122063442954 [01:40] fta: i guess they make up a number by a scheme or something [01:40] check whatelse is in the proximity of IDS_OPTIONS_AUTOOPENFILETYPES_INFO [01:40] or find the string you see in the english screenshot [01:41] the IDS_OPTIONS_AUTOOPENFILETYPES_INFO is probably in the proximity there [01:41] http://codereview.chromium.org/165209 [01:41] there is not the file i care most [01:41] the one where the IDS_OPTIONS_AUTOOPENFILETYPES_INFO was in [01:42] (Patch set is too large to download) [01:42] i dont see that file [01:42] http://src.chromium.org/viewvc/chrome/trunk/src/chrome/app/resources/ [01:42] its not there [01:43] http://src.chromium.org/viewvc/chrome/trunk/src/chrome/app/chromium_strings.grd?view=markup [01:43] okm [01:43] [01:43] Ask where to save each file before downloading [01:43] [01:43] good morning asac [09:19] you disappeared yesterday evening :) [10:50] does mozilla fennec run on android? [17:15] asac: ping [17:15] tell me you are around :) [18:50] hi [18:50] ola fta [18:51] BUGabundo, he's on holidays for a week [18:51] bahhhhh [18:52] who is going to help me now :( [18:52] good time to learn by yourself :) [18:52] like we do ;) [18:53] fennec on android, no way, unless android now allows native apps [18:53] fta: took me *one* year to figure that NM could _easily_ share a connection, to find out today, I can't make it work out of the box on a jaunty livecd :( [18:53] fta: it doesn't [18:54] but I read on the ML (thanks to google) [18:54] that someone is porting it to the SDK [18:54] then it's a full rewrite, not a port [18:54] I really would appreciate if you could ping me.... I loose all your replies :) [18:55] grrr, use a real irc client [18:58] for what? [18:58] I can very easily read all the channel blober [18:58] I just get a faster notification if you, fta, nick me :) [18:59] don't want, don't do it [18:59] be FREE [19:00] BUGabundo, it's just not natural to me once a discussion has started, and there's no interference [19:00] ok ok [22:17] Jazzva_: how about guessing the files for MOZ_XPI_DOCUMENTED_LICENSE_FILES if this variable is not set? [23:04] bdrung_: I think that sounds good, and should be easy. we could find the files with find command and set the M_X_D_L_F. is that what you had in mind? [23:05] Jazzva_: yes. here is what is needed: MOZ_XPI_DOCUMENTED_LICENSE_FILES ?= $(strip $(shell for f in COPYING LICENSE; do if test -f $$f; then echo $$f; fi; done)) [23:07] bdrung_: I think we cannot limit to those two. We need to include subdirectories, and there might be variations (for example license.txt, or something similar) [23:08] maybe to replace with [23:08] Jazzva_: ok, license.txt should be added. [23:08] but subdirectories? [23:09] bdrung_: I saw those cases :). weave or ubiquity has something like that. It uses some code, not written by the upstream team itself, and they ship license files with that code in subdirectories [23:09] i think we should check the common names [23:09] bdrung_: I agree with that. those three would be just fine, but I think we should also check the subdirectories... [23:10] Jazzva_: ok, then i transform it into a find command [23:10] for f in `find . -name {file1,file2}` ; do echo $$f ; done [23:10] yeah :) [23:12] Jazzva_: find -iname copying -o -iname 'license*' [23:12] that should do it [23:13] bdrung_: ok. if you want, you can add that. [23:14] Jazzva_: or sould we check for 'licence*', too? [23:16] bdrung_: ok. but maybe we should use the * wildcard. some other extension might use a file named licenseCheck.js. so, let's restrict to licen{s,c}e{,.txt} [23:16] s/should/shouldn't/ [23:18] Jazzva_: yes, that's better. the command looks now like: find * -iname copying -o -iname licen[sc]e -o -iname licen[se]e.txt [23:21] bdrung_: I think that's ok. just replace [se] in the last part with [sc] :) [23:21] ups, yes :) [23:30] Jazzva_: here you are: https://code.launchpad.net/~bdrung/mozilla-devscripts/mxdlf [23:32] bdrung_: brb, phone