| xipietotec | can anyone tell me, when installing flash10, should I install to /usr/lib/firefox or /usr/lib/firefox-3.0 ? | 01:03 |
|---|---|---|
| asac | hi | 09:13 |
| asac | sorry, was gone for the sweeked | 09:14 |
| jtv | asac: hey there | 11:29 |
| asac | jtv: yeah. great to see you | 11:29 |
| asac | was just about to hunt you ;) | 11:29 |
| jtv | asac: uh-oh... is this where I'm given 10 seconds to run or hide? | 11:30 |
| asac | jtv: too late ;) | 11:30 |
| asac | jtv: but first, what can i do for you? | 11:30 |
| jtv | asac: actually, it's sort of more a thing I've been doing for you, that you could test. | 11:30 |
| jtv | asac: I prototyped xpi export this weekend. | 11:30 |
| asac | jtv: \o/ | 11:31 |
| asac | sounds cool | 11:31 |
| jtv | asac: sudden inspiration | 11:31 |
| jtv | asac: even does multiple languages in one file. | 11:31 |
| asac | so you did a complete rewrite? | 11:31 |
| jtv | asac: I know of several things that are still missing though: | 11:31 |
| jtv | No no no, it was just a matter of writing a new export plugin. Not an easy one, mind you, but the existing code is intact. | 11:32 |
| jtv | asac: still missing: install.rdf generation, merging in the non-locale files from the template, those special tags that don't carry any translations, and some details on template export. | 11:33 |
| asac | jtv: ok | 11:33 |
| asac | sounds good | 11:33 |
| jtv | asac: I'm not sure which of those you need, and some of them could be very hard. | 11:33 |
| asac | jtv: we have the install.rdf generation code in the po2xpi thing | 11:33 |
| jtv | asac: gimmegimme! | 11:33 |
| asac | jtv: err. its a filter actually based on the en-US.xpi install.rdf | 11:34 |
| jtv | asac: that's pretty much what I need (though we can add some of our own metadata as well) | 11:34 |
| asac | just: cat en-US.xpi/install.rdf | sed -e 's/en-US/YOURLOCALE' | 11:34 |
| asac | well with proper syntax | 11:35 |
| jtv | asac: duh | 11:35 |
| asac | jtv: the other nifty thing you have to do is setting up proper defaults | 11:35 |
| asac | for cases where we have two country codes for one language | 11:35 |
| * jtv shivers | 11:35 | |
| asac | jtv: you have two chrome.manifest i guess right? | 11:36 |
| asac | well ... most likely concat'ed into one for the final en-US.xpi | 11:36 |
| jtv | asac: two? | 11:36 |
| asac | one for pt-PT and one for pt-BR | 11:36 |
| jtv | One XPI file, one chrome.manifest. I know it's harsh, but they don't grow on trees you know | 11:36 |
| jtv | I've produced a very simple canonicalized layout, so a manifest may look like: | 11:37 |
| jtv | locale de foo jar:locale/de.jar!/foo/ | 11:38 |
| jtv | locale fr foo jar:locale/fr.jar!/foo/ | 11:38 |
| jtv | locale de bar jar:locale/de.jar/bar/ | 11:38 |
| jtv | etc. | 11:38 |
| jtv | (actually, sorted by locale) | 11:38 |
| asac | jtv: and for pt? | 11:39 |
| jtv | asac: it depends on what's in your database. If you wanted, you could have pt, pt_PT and pt_BR and you could export them all in a single xpi file. Each of the 3 would have its own jar file and its own manifest entriese. | 11:39 |
| jtv | *entries | 11:40 |
| * jtv makes a note that the manifest wants to use dashes, not underscores, to attach country codes to language codes | 11:40 | |
| asac | jtv: ok. let me tell what we are currently doing for pt-PT | 11:40 |
| asac | and pt-BR | 11:41 |
| asac | we have entries for both and add entries for "pt" which point to the locale we want to be default for LANG=pt | 11:41 |
| asac | or LANG=pt_UNKNOWN | 11:41 |
| asac | understood? | 11:41 |
| asac | so we have locale pt-BR jar:...pt-BR.jar!/... | 11:42 |
| asac | and locale pt-PT jar:...pt-PT.jar!/... | 11:42 |
| jtv | asac: ah, an example helps, thanks. | 11:42 |
| asac | and locale pt jar:...pt-PT.jar!/... | 11:42 |
| jtv | asac: for import we don't support multiple languages in one file yet, so what happens is this: | 11:42 |
| jtv | you upload a file. If it's e.g. pt.xpi, that's easy; it gets auto-approved. | 11:42 |
| asac | jtv: no its for export | 11:43 |
| asac | jtv: we need at least the same features we have now ... where we upload pt-PT.xpi and pt-BR.xpi ... and export that all into the same pt.xpi ;) | 11:43 |
| jtv | asac: shouldn't be a problem. You just browse to the *template* and request a download of pt and pt_BR, in XPI format. | 11:44 |
| jtv | That'll give you a single xpi containing both languages. | 11:44 |
| jtv | asac: there is one catch, of course. | 11:44 |
| asac | jtv: ok, so where can i test current code? | 11:46 |
| jtv | Since we stick to the convention of "pt" rather than pt_PT, the two languages in your export (right now) will be pt and pt_BR | 11:46 |
| asac | k | 11:46 |
| jtv | asac: if you've got devpad access, you can bzr my branch from there. | 11:46 |
| asac | jtv: i doubt i have that ;) ... so what do you want me to test? or did you just want to talk about this? | 11:48 |
| jtv | asac: ah, you didn't think all this came for free, did you? :) | 11:50 |
| jtv | asac: I want to produce some test files for you, and ask you to see if they're any good. | 11:50 |
| asac | jtv: ok cool | 11:55 |
| asac | jtv: my question was more of bug nature ;) | 11:55 |
| jtv | asac: go ahead | 11:55 |
| asac | jtv: did you came to fix the comment (//) issue in .properties files? | 11:56 |
| jtv | asac: yes and no | 11:57 |
| jtv | asac: I still need to write the tests. | 11:57 |
| asac | ok | 11:58 |
| armin76 | bumb | 11:58 |
| asac | jtv: https://translations.edge.launchpad.net/ubuntu/hardy/+source/xulrunner-1.9/+imports | 11:58 |
| asac | there are two items that need review? | 11:58 |
| armin76 | asac: bumb! | 11:58 |
| asac | armin76: what? | 11:58 |
| armin76 | asac: bumb yourself! | 12:01 |
| jtv | asac: did we really want that old fi.xpi blocked? I thought it was a mistake, in which case we'd better just delete it. | 12:04 |
| asac | jtv: i cant remember what that upload was about | 12:04 |
| asac | jtv: afaik all except the // thing is ok now in fi so we probably dont want that | 12:05 |
| asac | jtv: en-US.xpi needs to be approved though | 12:05 |
| jtv | asac: ahhh, wasn't that the one with some problem that made the import fail? | 12:05 |
| asac | didi i forget to tr - _ ? | 12:05 |
| jtv | asac: I already approved those two. | 12:05 |
| jtv | asac: not in the filename, that's for sure! | 12:05 |
| asac | jtv: ok ... also uploaded en-US.xpi for ffox 3 | 12:13 |
| asac | thanks! | 12:13 |
| asac | (for approval) | 12:13 |
| asac | https://translations.edge.launchpad.net/ubuntu/hardy/+source/firefox-3.0/+imports | 12:14 |
| jtv | asac: that should be auto-approved, no? | 12:15 |
| asac | jtv: hmm. not sure | 12:16 |
| asac | why would that be auto approved, but the previous xulrunner one not? | 12:16 |
| jtv | asac: auto-approval may take a while. | 12:17 |
| asac | hi Jazzva | 12:59 |
| Jazzva | hey asac :) | 12:59 |
| asac | Jazzva: how are you? | 12:59 |
| Jazzva | asac, good :). Had an exam on Saturday at 8am, still feeling tired. You? | 13:00 |
| asac | not so bad either ;) | 13:00 |
| asac | Jazzva: how was your exam? | 13:01 |
| asac | went well? | 13:01 |
| Jazzva | asac, this one did went well :)... telecom exam didn't. but, that's ok for now | 13:01 |
| asac | Jazzva: you think you have to redo telecom? | 13:01 |
| Jazzva | I know. I failed it (as most of the people who did it) | 13:02 |
| asac | hmm. sry for that | 13:02 |
| asac | exams are one of the things i certainly dont like to do twice ;) | 13:02 |
| Jazzva | no problem :). I had to do some of them more than once... | 13:04 |
| Jazzva | asac: btw, do you know where I can find wiki administrators? | 13:04 |
| Jazzva | asac, and is it ok if I move MT/Firefox3Extensions/LargeScaleMaintenance to MT/Extensions/LargeScaleMaintenance? | 13:06 |
| asac | Jazzva: not sure about wiki admins. feel free to rename the LargeScaleMaintenance page ... can you figure if we can create a redirect or somethign? | 13:08 |
| Jazzva | asac: I think it automatically creates a redirect when a page is renamed. But I didn't know that when I started, so I created new pages. Then I found that out, so I deleted the new pages, and tried to rename the old ones. Now it reports I can't rename them, since those pages already exist. Let me try again. | 13:09 |
| Jazzva | heh, not redirecting for LargeScale... Let me check help for moin wiki | 13:12 |
| Jazzva | asac, we can redirect | 13:34 |
| Jazzva | just add "#REDIRECT NewPage" in the OldPage. | 13:34 |
| Jazzva | https://wiki.ubuntu.com/MozillaTeam/Firefox3Extensions/LargeScaleMaintenance | 13:35 |
| asac | Jazzva: cool | 13:42 |
| Jazzva | I'm doing that for the rest of the extensions' pages now | 13:42 |
| asac | Jazzva: largescale does not yet redirect form e | 13:43 |
| asac | for me | 13:43 |
| Jazzva | it doesn't? Weird. It always redirect and shows notice at the top of the page | 13:44 |
| Jazzva | try to refresh page :) | 13:44 |
| Jazzva | maybe it didn't pick the new one, and loads it from cache | 13:44 |
| asac | Jazzva: ah ok | 13:45 |
| asac | thanks | 13:46 |
| Jazzva | np | 13:46 |
| asac | hmm ... still doesnt redirect | 13:46 |
| asac | just shows that it wants to | 13:46 |
| asac | but that never happens | 13:46 |
| Jazzva | try with http://wiki.ubuntu.com/MozillaTeam/Firefox3Extensions/Packaging | 13:46 |
| Jazzva | btw, do we need this one: https://wiki.ubuntu.com/MozillaTeam/Firefox3Extensions/Bzr ? Most of those instructions are incorporated in Packaging page | 13:47 |
| asac | i think it works now.. wierd | 13:49 |
| asac | Jazzva: the packaging page is ment to be a tutorial page ... that doesnt cover all cases | 13:50 |
| asac | so yes, Bzr page makes sense. just needs to be populated with more use-cases | 13:50 |
| asac | (imho) | 13:50 |
| Jazzva | Ok... I'll see with gnomefreak what did he planned to do with it :) | 13:51 |
| Jazzva | and I think we can ditch this one: https://wiki.ubuntu.com/MozillaTeam/Firefox3ExtensionsReview , when we move some of the contents to MT/Extensions/List | 13:52 |
| asac | Jazzva: yeah ... delete the review page | 13:54 |
| Jazzva | asac, you also created this one: https://wiki.ubuntu.com/MozillaTeam/Firefox3Extensions/BogusList ... We keep that info in tables at List page, so I'll remove BogusList | 13:54 |
| asac | if you add the ones that are not on Extension list to the table that "is missing info" that would be great | 13:55 |
| asac | but not needed imo | 13:55 |
| Jazzva | I planned on doing that | 13:55 |
| asac | Jazzva: i am not sure if the normal list page shouls also get the bogus list | 13:56 |
| asac | that table was ment to track reported issues | 13:56 |
| asac | e.g. if someone files a bug like "this freature is broken" and finall we find that its caused by extension X | 13:56 |
| Jazzva | we keep "Extensions that are not suitable for Ubuntu" table at the list page | 13:56 |
| asac | we would add that incident to that page | 13:56 |
| Jazzva | aham... ok | 13:56 |
| asac | of course so far we didnt do that ;) | 13:56 |
| asac | so not sure if thats the right thing | 13:56 |
| Jazzva | so, it's not the same as "not suitable extension" list | 13:56 |
| Jazzva | just to know :) | 13:57 |
| asac | maybe tagging bugs that someone confirmed as being "extension caused" | 13:57 |
| asac | would be a good start | 13:57 |
| asac | Jazzva: yeah. its different | 13:57 |
| asac | jtv: so now all is imported. do we have to wait for a new delta tarball to arrive based on this? | 14:04 |
| asac | or can we trigger the creation of a delta now? | 14:05 |
| asac | jtv: if you used the po2xpi code we had, then you could have used runpo2xpi to do the copying of the non .dtd/.properties files as well as the install.rdf creation | 14:20 |
| jtv | asac: how do you map the directory layouts between the "template" (en-US) and the translation? | 14:24 |
| jtv | asac: about the deltas: those are for the entire Ubuntu release, so better coordinate with Arne & Martin. | 14:25 |
| asac | jtv: the directory layout is always the same | 14:34 |
| asac | with en-US replaced by xx-YY | 14:34 |
| asac | in the end those files should be single translatable entities imo | 14:34 |
| asac | e.g. one entity for the complete file | 14:35 |
| asac | which then the po2xpi transformer identifies and handles correctly | 14:35 |
| jtv | asac: translatable? So that means that you don't always want the versions from the en-US.xpi? | 14:38 |
| jt1 | asac: think I lost my connection for a bit there. | 14:43 |
| jt1 | asac: sorry, connection trouble. I know how to fix it, but believe it or not, getting it fixed involves contacting my favourite pizza place. | 14:54 |
| === jt1 is now known as jtv | ||
| asac | jtv: haha | 14:59 |
| asac | jtv: well. if they are in en-US.xpi and they are resolvable through a chrome://xxx/locale/ URI, then those are in the end translatable files | 14:59 |
| asac | like complete .xhtml files | 14:59 |
| asac | or images. | 14:59 |
| asac | i think we dont want to support images right from the beginning | 14:59 |
| asac | but xhtml file translation would be great | 14:59 |
| jtv | asac: probably not this week though :-) | 15:01 |
| jtv | asac: I was thinking it might be healthier for now to produce a simple canonical directory structure, and if people want to merge other files into the XPI, they can just unzip/add/rezip. | 15:02 |
| jtv | asac: though I do understand that you'll probably want complete, merged xpi archives. | 15:03 |
| jtv | asac: one big advantage of what I have right now is that it works without looking at the en-US.xpi at all. | 15:03 |
| jtv | asac: and it keeps a very simple mapping between chrome paths and "xpi paths." | 15:04 |
| jtv | asac_: ah, having trouble as well? | 15:04 |
| asac_ | no ... i think this was daily reconnect ;) | 15:04 |
| asac_ | emphasize on "think" ;) | 15:05 |
| jtv | asac_: the files from en-US.xpi that you'd want merged into a translation... do they all live in the locale directories covered by the locale entries in the manifest? | 15:10 |
| asac_ | jtv: if they are not accessible through a locale/ directory, then we dont need to copy them | 15:12 |
| jtv | asac_: I see. That was the one big question I had. At some point I'll have to scan the en-US.xpi as part of the export process anyway, so that's doable without adding too much weight. | 15:18 |
| jtv | asac_: what I've done for now has the advantage of not needing any knowledge of the template, and keeping a simple mapping between chrome paths and directory layout. | 15:19 |
| === asac_ is now known as asac | ||
| === Moot2 is now known as MootBot | ||
| rzr | hi | 17:51 |
| rzr | asac: I saw the Flashblock bug | 17:53 |
| rzr | does something need to be done to backport it to hardy ? | 17:54 |
| rzr | I proposed to merge a branch a couple of week ago I think | 17:54 |
| asac | rzr: you want to backport a bug? | 18:24 |
| asac | i'd suggest to backport the fix ;) | 18:24 |
| asac | hehe | 18:24 |
| asac | rzr: we havent yet setup the auto-notification if you suggest a merge | 18:24 |
| rzr | it = flashblock :) | 18:24 |
| rzr | auto-notification ? did I miss something ? | 18:25 |
| asac | rzr: no ... thats nothing you missed, but we missed it | 18:26 |
| asac | rzr: we cannot upload a "may fix something unknown" to -proposed | 18:29 |
| asac | we should upload this to hardy-backports | 18:30 |
| asac | and once we know about a specific bug get a minimal patch to -proposed | 18:30 |
| rzr | ok | 18:30 |
| asac | rzr: just change the changelog target to hardy-proposed | 18:30 |
| asac | and document that its a upload to backport | 18:30 |
| asac | * backport, may fix trouble with firefox 3 | 18:31 |
| asac | if you have "may", just leave that part | 18:31 |
| rzr | <asac> rzr: just change the changelog target to hardy-proposed | 18:32 |
| rzr | or hardy-backoprts ? | 18:32 |
| rzr | -op+po | 18:32 |
| asac | rzr: backports | 18:35 |
| asac | rzr: did i upload the release to intrepid yet? | 18:36 |
| rzr | ok this makes sense now | 18:36 |
| rzr | yes you did | 18:36 |
| asac | ok | 18:36 |
| rzr | you asked me this twice :) | 18:36 |
| asac | rzr: use the same bug id in changelog | 18:36 |
| asac | rzr: today? | 18:36 |
| rzr | last week :) | 18:36 |
| asac | ok, then i am not scared about brain-damage ;) | 18:36 |
| asac | rzr: can you also change the Vcs-Bzr header to point to the backports branch? | 18:38 |
| asac | Vcs-Bzr: https://code.launchpad.net/~ubuntu-dev/firefox-extensions/flashblock.ubuntu.hardy-backports | 18:38 |
| rzr | let's do this now .. | 18:38 |
| asac | rzr: wait a second ;) ... let me think if thats the right procedure (in regards to auto merging) | 18:39 |
| rzr | about the version name | 18:42 |
| asac | rzr: i think should be fine | 18:42 |
| asac | no. all fine | 18:42 |
| asac | just do as said | 18:42 |
| rzr | see : https://launchpad.net/ubuntu/+source/cmake | 18:42 |
| asac | change Vcs-Bzr header like above | 18:42 |
| rzr | 2.6.0-4~hardy1 | 18:43 |
| rzr | while | 18:43 |
| rzr | you suggested me to name it : 1.3.10a~snapshot20080611-0ubuntu0.8.04+backports.1 | 18:43 |
| asac | rzr: no | 18:43 |
| asac | this is not about version | 18:43 |
| asac | this is about branch name | 18:43 |
| asac | the version is ok like this | 18:43 |
| rzr | ok I see | 18:43 |
| asac | just hardy-backports for the distribution | 18:44 |
| rzr | humm | 18:44 |
| rzr | i am not sure we talk about the same thing | 18:44 |
| rzr | the cmake guys just added ~hardyN to package version which was in X-Y form | 18:45 |
| rzr | you explained me that wont fit because it's not in X-(Y minus 1) form | 18:46 |
| rzr | well I commit this changeset then | 18:49 |
| rzr | asac: at your service sir : http://bazaar.launchpad.net/~rzr/firefox-extensions/flashblock.ubuntu/revision/12 | 18:52 |
| === rzr is now known as rZr | ||
| armin76 | asac: hows that you don't use the distro useragent string on ff3? | 19:11 |
| stek79_ | hello | 19:56 |
| asac | stek79_: hi | 21:10 |
| Jazzva | asac, we did previous package for foxyproxy from xpi file. But there is a svn repo, which provides the build script and the rest. Should we switch to that one? | 21:13 |
| Jazzva | the build script is not present in the xpi file | 21:14 |
| asac | Jazzva: its not yet really understood how the auto syncher/merger would work for svn upstreams | 21:31 |
| asac | so for now we might wanna stick with svn | 21:31 |
| asac | err, xpi ;) | 21:31 |
| Jazzva | easier for me :) | 21:32 |
| asac | Jazzva: how do we unpack .xpi's? | 21:33 |
| asac | do we we have a standard format? | 21:33 |
| Jazzva | i use unzip :) | 21:33 |
| asac | Jazzva: yes, but the chrome jars need to be unpacked too | 21:34 |
| asac | just committing .jar files is ugly | 21:34 |
| Jazzva | download xpi, unpack it, unpack chrome.jar (if present), create rules that will zip it all up, install, and then remove jar on clean | 21:34 |
| Jazzva | it's two more lines of code | 21:34 |
| asac | Jazzva: where do you unpacke chrome.jar? | 21:34 |
| Jazzva | to chrome/ | 21:34 |
| asac | Jazzva: what do you do when there is more than one .jar in crhome? | 21:34 |
| Jazzva | this extension have icons/ and foxyproxy.jar in chrome/. | 21:34 |
| asac | should be quite common | 21:34 |
| Jazzva | More than one? Still haven't bumped into that | 21:35 |
| asac | really | 21:35 |
| asac | hmm | 21:35 |
| asac | we should do something about that imo | 21:35 |
| Jazzva | But I suppose I would use debian/some_temp_dir | 21:35 |
| asac | Jazzva: yes, but we need a working standard | 21:35 |
| asac | so every xpi extension is done in the same way ;) | 21:35 |
| Jazzva | COUNT = 0; for JAR_FILE in `find chrome -name *.jar` ; do unpack_to($TEMP_DIR+$COUNT) ; $COUNT++ ; done | 21:37 |
| Jazzva | in pseudo-bash-pseudo-code :) | 21:37 |
| asac | well. you would loose information about the name | 21:37 |
| Jazzva | $JAR_NAME+$COUNT | 21:37 |
| Jazzva | :) | 21:37 |
| asac | upack_to "$JAR_FILE!" | 21:37 |
| asac | why count? | 21:38 |
| Jazzva | oh, right :) | 21:38 |
| asac | $JAR_FILE should be unique | 21:38 |
| Jazzva | yep, agree.. | 21:38 |
| asac | append the ! which is used in chrome.manifest to denote a .jar delimiter | 21:38 |
| asac | Jazzva: ok, then we need a script to xpi_unpack <xpifile> <todir> | 21:39 |
| asac | and xpi_pack <xpifile> <indir> | 21:39 |
| Jazzva | ok, i'll try to make it. where to put it? | 21:39 |
| asac | :) | 21:39 |
| asac | Jazzva: mozilla-devscripts | 21:39 |
| Jazzva | inside xpi.mk? | 21:39 |
| asac | Jazzva: depends. i think we should make scripts out of them and then add convenience rules to xpi.mk that basically use xpi_pack | 21:40 |
| asac | Jazzva: the scripts should be installed in $bindir | 21:40 |
| asac | e.g. /usr/bin/ | 21:40 |
| asac | ltes name them mds-xpi-unpack and mds-xpi-pack | 21:40 |
| asac | or | 21:41 |
| asac | med-xpi-... | 21:41 |
| Jazzva | k | 21:41 |
| asac | whatever you prefer | 21:41 |
| Jazzva | off to dinner now. I'll see what I can do tonight :) | 21:42 |
| Jazzva | asac, which mozilla-devscripts branch to use :)? | 22:23 |
| [reed] | asac / fta2: where do you all disable safebrowsing? | 22:32 |
| [reed] | I couldn't find it | 22:32 |
| asac | [reed]: its not disabled (anymore) | 22:51 |
| asac | Jazzva: which branches do exist? | 22:51 |
| asac | Jazzva: https://code.edge.launchpad.net/~mozillateam/mozilla-devscripts/mozilla-devscripts | 22:51 |
| Jazzva | asac, sorry, was away from keyboard. Thanks for the link | 23:04 |
| gnomefreak | do i need to be scared of my email tonight? | 23:27 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!