[02:20] <Greenery> the daily build of Firefox-3.1 won't close down completely. I have to kill the application although FIrefox-3.1 windows had been closed.
[02:22] <Greenery> Is this a known bug?
[08:58]  * asac back 
[11:37] <fta2> asac, if you have time, prism needs some love
[11:37] <asac> fta2: whats up with it?
[11:40] <asac> fta2: just diverged patch?
[11:41] <fta2> no, some issue with xpi.mk
[11:41] <asac> fta2: hmm. the current patches dont apply either
[11:42] <fta2> (after tweaking *.install)
[11:42] <asac> fta2: at least the package i got from umd
[11:42] <fta2> it does, i fixed that
[11:43] <asac> fta2: well. one minute ago i got the bits from umd
[11:43] <asac> fta2: patches didnt apply
[11:43] <asac> fta2: anyway. so you say with the bzr branc hthose should be fine?
[11:45] <fta2> i think so
[11:45] <asac> james_w: buuuugg ;)
[11:45] <asac> james_w: bzr: ERROR: Tags not supported by BzrBranch5('file:///home/asac/Development/ubuntu/mozillateam/prism/'); you may be able to use bzr upgrade.
[11:45] <asac> james_w: plz check that branch haz feature or dont die on this ;)
[11:46] <fta2> Tags?
[11:46] <asac> fta2: yes. i think bzr-buildeb tries various ways for getting orig
[11:46] <asac> fta2: it also has some magic tag syntax i presume
[11:46] <asac> fta2: and now bzr-builddeb bails out here on the not-upgraded branch
[11:50] <asac> james_w: filed bug 339886
[12:16] <Jazzva_> asac: ping bug 321814. As I mentioned in the bug report, if we don't want links to be created in /usr/lib/{mozilla,firefox}, we should edit patch 000_debian_make_symlinks. Tell me if that's what we want and I'll work it out :)
[12:20] <asac> Jazzva_: welcome back ;)
[12:20] <asac> Jazzva_: yes, we want to prevent default links
[12:20] <Jazzva_> asac: Thanks :)
[12:21] <asac> if NSPLUGINDIR is set
[12:21] <asac> Jazzva_: if you do that can you also do the upgrade to 1.1.4?
[12:21] <asac> (at best in two steps so we can handle the upstream bump in a FF exception upload)
[12:21] <Jazzva_> sure...
[12:23] <asac> bug 329061
[12:23] <Jazzva_> asac: what do you mean 1.1.4? there is 1.2.2 which we have, and the next release is 1.3.0 (which still isn't quite ready afaics)
[12:24] <asac> Jazzva_: hmm. thought there was a.4 release .... maybe 1.2.4?
[12:24] <Jazzva_> asac: nope... http://svn.beauchesne.info/gwenole/projects/nspluginwrapper/tags/
[12:24] <asac> Jazzva_: seems not ;)
[12:24] <asac> ok great. not sure whe ni had a dream ;)
[12:25] <Jazzva_> heh :)
[12:26] <asac> Jazzva_: also we should really look into making postinst smart to regen wrappers for existinginstalls
[12:26] <asac> i think we already talked about that
[12:26] <Jazzva_> nspluginwrapper -l, then foreach nspluginwrapper -u
[12:27] <asac> Jazzva_: yeah. i think we need -l, but also need meta files for NSPLUGINDIRS
[12:27] <valgaav> Hi ... I googled up a bit but found nothing interesting about this metter ... What's the status of Firefox Qt4 port ? Any chance to see it in ubuntu soon ?
[12:27] <asac> Jazzva_: so flashplugin would ship a file /var/lib/nspluginwrapper/dirs.d/flashplugin-nonfree
[12:28] <asac> which would have the NSPLUGINWRAPPER dirname
[12:28] <asac> valgaav: not in jaunty ... upstream has a qt port for xulrunner, but firefox hasnt been properly ported yet
[12:28] <Jazzva_> asac: right, that is not listed with -l
[12:29] <asac> Jazzva_: so maybe the -l should be teached to look at and env NSPLUGINDIRS=/var/lib/flashplugin-nonfree/:/var/lib/somethingelse
[12:29] <asac> and postinst would put together the right NSPLUGINDIRS based on something like above
[12:31] <valgaav> oh I see .. I'm fine in using ppas though ... Any chance to have it there ?
[12:32] <asac> valgaav: i dont think we have the resources to do that in this cycle. we can provide builds in PPAs for old releases once we have it
[12:32] <Jazzva_> asac: I think I get it. I'll see how npw keeps info about already installed wrappers, and check if it's maybe possible to write a function which would update all wrappers
[12:33] <asac> Jazzva_: yes. but i really think that teaching -l to also look at dirs in NSPLUGINDIRS environment should be enough
[12:33] <Jazzva_> and to also try and add the part to keep info about wrappers installed in NSPLUGIN_DIR, if that's not possible right now, then we could use meta files.
[12:33] <asac> sounds more easy. but theni dont know the code
[12:34] <valgaav> ahh ok thank you for your time :) I'll just wait patiently :P
[12:34] <Jazzva_> asac: me neither ;)
[12:34] <asac> Jazzva_: i dont tihnk nspluginwrapper keeps meta files. what it does is look at its "well known" directories (e.g. the default ones)
[12:34] <asac> and updates all files that look like they are npviewer. stuff
[12:34] <asac> thats why i think that extending the -l logic to just look at more dirs based on env is the easiest approach ;)
[12:35] <asac> but yeah. i dont care as long as it works ;)
[12:35] <Jazzva_> asac: that's what I think too, but I will check first :).
[12:35] <asac> making packages like flash ship a meta file that adds info about its nsplugindir is not that bad ;)
[12:35] <asac> not perfect, but acceptable ;)
[13:07] <asac> anyone here with intrepid?
[13:49] <asac> fta2: does latest NM detect your modem still?
[13:50] <asac> fta2: in syslog it should tell you if its detected through hal or udev ... which one is it for you?
[13:59] <fta2> asac, remind me of that later when i'm home, i'll do the test
[14:04] <asac> fta2: great. i will look at prism asap. have to do nss now and then tbird i guess and also teach some vendor folks about NM in #nm ;)
[14:17] <fta2> asac, yesterday, i read a lot about netbooks & ubuntu, networking seems to be a problem everywhere (broken n-m, no 3G, bad wifi drivers, madwifi, etc.)
[14:20] <asac> fta2: broadcom is still closed source and not in the mainline tree
[14:20] <asac> fta2: unfortunately broadcom is common
[14:20] <asac> fta2: 3G is what we are working on in NM atm
[14:20] <asac> most ship f3507g or derivate modems i would think
[14:20] <fta2> most netbooks don't have integrated 3G, yet
[14:21] <asac> fta2: right. but those that have, have the modem i am working on
[14:21] <fta2> https://help.ubuntu.com/community/NC10
[14:23] <fta2> i'm now targeting the Samsung NC10 instead of the Dell Mini 10
[14:24] <asac> fta2: not sure which modem is in there
[14:24] <fta2> hm, scrolling is super slow in this page (ff 3.2)
[14:24] <asac> could be that samsung really has its own modem, but most likely they just whitelabel licensed it somewhere
[14:24] <asac> so did te guy really confirm that it works?
[14:25] <fta2> he said "Modem really works"
[14:25] <fta2> ohoh, reset zoom fixed the slow scrolling
[14:30] <jcastro> asac: who do I poke for python-webkitgtk?
[14:30] <jcastro> it's been like a week
[14:31] <asac> jcastro: any archive admin ... i would think seb
[14:31] <jcastro> k
[14:31] <asac> thanks
[15:07] <gnomefreak> 39489k/39490k and my connection dies as seen above :(
[15:09] <asac> gnomefreak: nothing seen above ;)
[15:09] <asac> gnomefreak: but that sounds like a transparent ftp proxy issue
[15:09] <asac> my provider had that too for ages
[15:09] <asac> i had to scp to some other host and dput from there
[15:10] <gnomefreak> oh shit
[15:10] <asac> yeah really
[15:10] <asac> there was not much to do
[15:10] <asac> failed like 8 out of 10 times
[15:10] <asac> and reuploading was too painful
[15:10] <asac> gnomefreak: but maybe give it more time
[15:10] <gnomefreak> yep that sounds like it
[15:10] <gnomefreak> asac: i am this has been going on all weekend
[15:10] <asac> gnomefreak: could be that its a transparent proxy issue to flatten upload speed by waiting at the end
[15:11] <asac> gnomefreak: sitting there for how long?
[15:11] <gnomefreak> not sure maybe 3-5 minutes than gives an error 113 timed out
[15:12] <gnomefreak> we cant do shit to make source smaller either
[15:13]  * gnomefreak waits for error
[15:15] <gnomefreak> if it fails again people are not getting sunbird 0.9 for anything other than jaunty
[15:55] <gnomefreak> its still sitting there
[15:55] <gnomefreak> maybe ill try again after email and updates
[17:05] <gnomefreak> !info nspluginwrapper
[17:05] <gnomefreak> yep that is the app.
[17:05] <gnomefreak> asac: the npviewer is a module in nspluginwrapper right?
[17:06] <asac> gnomefreak: yes
[17:06] <gnomefreak> asac: thanks
[17:08] <gnomefreak> bug 338785
[17:08] <gnomefreak> hmmmm
[17:30] <gnomefreak> libmozjs is not built into xulrunner right?
[17:31] <gnomefreak> as i recall debian packages this separate and we dont but not sure if its in xulrunner
[17:32] <asac> gnomefreak: its build in xulrunner-1.9 but we dont provide it for publis consumption in ubuntu yet
[17:33] <asac> this will probably change. most likely not in jaunty though
[17:33] <gnomefreak> asac: ok i was referring to bug 339331 just making sure the user was right
[17:37] <asac> gnomefreak: asked
[17:37] <gnomefreak> thanks
[17:44] <gnomefreak> its firefox's fault that there is no setting in evo to change port numbers. WTH are people thinking
[17:46] <asac> gnomefreak: they probably use Help -> report a problem menu entry
[17:46] <asac> gnomefreak: just reassign to evo and go on
[17:47] <gnomefreak> i did
[17:47] <asac> gnomefreak: did you find the switch to subscribe mozillabugs to bugmail?
[17:48] <gnomefreak> asac: yep it done and i sent email reply to you
[17:48] <asac> gnomefreak: great
[17:48] <asac> thanks a lot
[17:48] <gnomefreak> asac: np
[17:48] <gnomefreak> !info swfdec
[17:49] <asac> thats probably something else ;)
[17:49] <asac> !info swfdec-mozilla
[17:49] <asac> !libswfdec3
[17:49] <asac> !info libswfdec5
[17:49] <asac> !info libswfdec6
[17:49] <asac> !info libswfdec-0.6-0
[17:49] <asac> !info libswfdec-0.6-90
[17:49] <asac> i hate this debian guy
[17:50] <asac> i mean why the hell does he do versioned stuff for a lib nobody uses ;)
[17:50] <asac> hate is the wrong word .... i dislike his decisions ;)
[17:52] <[reed]> the swfdec guy?
[18:02] <asac> [reed]: heh. no just the debian maintainer who decides to do new package names for every swfdec release ;)
[18:02] <asac> which you usually only do for really important libs that have to stay around longer bceause ther eare too many rdepends to transition
[18:02]  * asac off to cinema
[18:14] <gnomefreak> i'm off too while sunbird uploads hope it frigging works this time
[21:54] <asac>  ccscre	 -r
[21:58] <fta> lol
[22:11] <asac> 3g ;)
[22:11] <asac> latency
[23:22] <fta> asac, what did you want me to test?
[23:22] <asac> hmm .. so gnomefreak goes ahead and complains on dev-planning
[23:22] <asac> about the new firefox version
[23:23] <asac> fta: plug in your device with latest NM
[23:23] <asac> fta: a) is it detected in NM
[23:23] <asac> b) look in syslog: is it detected by udev or hal
[23:23] <asac> (search for your tty name)
[23:23] <asac> e.g. i hvae Mar  9 18:43:27 tinya NetworkManager: <info>  (ttyUSB2): detected GSM modem via udev capabilities
[23:23] <fta> he didn't ask here before :( i'm quite sure i said it was no problem for us
[23:24] <fta> lastest nm as in jaunty or ppa?
[23:24] <asac> fta: have you seen the mails that came to mozillateam
[23:24] <asac> ?
[23:24] <asac> ml?
[23:24] <asac> fta: jaunty
[23:25] <fta> i think i got the emails from mt in cc
[23:25] <asac> yeah
[23:27] <asac> ltes this doesnt get a flame ;)
[23:28] <asac> lets hope
[23:28] <asac> keboard hick-ups
[23:31] <fta> the sad thing is it means more transition packages
[23:39] <asac> thats the general trade-off of verisoned stuff
[23:39] <asac> the other idea would be to use firefox, firefox-next, firefox-trunk
[23:39] <asac> or something
[23:39] <asac> but i would think that such should be the meta packages
[23:40] <fta> well
[23:41] <fta> hmm, i had to reboot after the last batch of updates, now, i get apport say n-m crashed
[23:46] <fta> asac, a) ok
[23:48] <fta> asac, b) detected by HAL
[23:49] <fta> if i disconnect, and reconnect, all fine
[23:50] <fta> if i remove the key (after a disconnect), it's still listed in the applet :(
[23:51] <fta> when i reconnect, i have 2 entries :(
[23:54] <fta> with my other SIM (still locked), it's still the same problem, modem hangup just after the DNS are received
[23:55] <fta> asac, do you need something else?