[03:22] <kgoetz> asac: i'll want to ask you about bug 247157 (ot here, i know) at some point. i'll try and grab you in a few hours when i'm properly free, and your hopefully awake
[09:17] <asac> kgoetz: let me know ;)
[09:24] <fta> http://ubuntuforums.org/showthread.php?t=923136
[09:40] <fta> http://ubuntuforums.org/showthread.php?t=923038
[09:45] <fta> "Nightlies, showing ~ 12k active daily users    *
[09:45] <fta> Alpha 2  released Friday, Sept 5th, showing ~ 10k active daily users", how do they count that ? ping back ?
[11:04] <gnomefreak> lol i googled wizz_rss_news_reader and my .upstream branch is the first result
[11:04] <asac> fta: update server most likely
[11:15] <gnomefreak> asac: what format are we using for MOZ_XPI_EMID? the extension ID number or extension@extension.team
[11:18] <gnomefreak> asac: also can i shorten the name of the extension from wizz_rss_news_reader to wizz-rss (not stuck on it but i think name is a bit long.
[11:20] <gnomefreak> Jazzva: if you have thoughts on the 2 above questions let me know
[11:26] <asac> gnomefreak: you have to use whatever is in install.rdf
[11:27] <gnomefreak> ok
[11:34] <gnomefreak> s/./.)
[11:47] <gnomefreak> brb need to restart irssi for new script
[11:50] <gnomefreak> SUNWjoejaxx: are you still lead dev on fluxbuntu? i sent someone to #fluxbuntu not even sure if it was still maintained
[11:51] <gnomefreak> asac: im guessing that the full name of extension is ok? full name is wizz_rss_news_reader
[11:52] <asac> gnomefreak: full name for what?
[11:52] <gnomefreak> for wizz_rss_news_reader extension
[11:53] <gnomefreak> i was leaning towards wizz-rss but not sure what is best way
[12:02] <pmatulis> asac: hi, any news on the NFS/sqlite issue?  a 2nd support case in this morning on it
[12:11] <asac> pmatulis: i am sorry, but there are highest-prio issues on my plate these days which prevent me from looking closer into this :(
[12:11] <asac> cannot yet say for sure when i get back out of this
[12:13] <pmatulis> asac: ack
[12:14] <asac> pmatulis: but once thats done that issue will be back on my plate
[12:16] <pmatulis> asac: just wondering, what is your view on the profile locks?  should that be something users should see after a cold boot?
[12:21] <asac> pmatulis: no
[12:21] <asac> pmatulis: the files dont matter
[12:21] <asac> but they shouldnt lock firefox
[12:22] <pmatulis> asac: must be a bug on that
[12:22] <asac> pmatulis: on what?
[12:22] <asac> pmatulis: this is all related
[12:22] <asac> nfs doesnt release locks properly
[12:22] <asac> thats it
[12:22] <asac> thats the problem with places and thats the problem with parentlock and .lock
[12:23] <pmatulis> asac: i thought they were separate issues
[12:23] <asac> everything else doesnt make sense
[12:23] <asac> pmatulis: no ... try on a real system. i am sure that you can start firefox after cold boot
[12:23] <pmatulis> asac: right
[12:23] <asac> pmatulis: if that is broken then it would be a separate issue
[12:23] <asac> otherwise its all nfs ;)
[12:24] <asac> pmatulis: and my guts feeling is that those users have a nfs setup which lacks support for posix locks
[12:24] <asac> which is strange
[12:24] <asac> but maybe they just have a misconfiguration
[12:24] <asac> on client/server side
[12:24]  * gnomefreak goes for breakfast
[12:25] <pmatulis> well a standard nfs setup displays the issue
[12:26] <pmatulis> how to force posix locks support?
[12:27] <asac> pmatulis: not sure ... i cant know everything ;)
[12:28] <pmatulis> asac: ahhh
[12:28] <asac> maybe its also not the problem. maybe our nfs client is _really_ outdated (because its supposed to support flock since 2.6.12)
[12:29] <pmatulis> asac: there are some server team members floating around the montreal office, maybe i'll inquire
[12:30] <asac> pmatulis: ask them yes. maybe there are nfs tweaks or something.
[12:30] <asac> let me know what you find ;)
[12:30] <pmatulis> asac: will do
[12:44] <SUNWjoejaxx> gnomefreak: yeap i am
[13:16] <gnomefreak> Mozilla dropped the EULA on first run?
[13:49] <pmatulis> asac: possible to use ff3 without sqlite?  didn't think so
[13:55] <asac> pmatulis: no
[14:13] <asac> fta: NSS_3_12_1_RC2
[14:13] <asac> fta: we need to bump our hardy branches for that i guess
[14:14] <fta2> told you earlier, didn't i ?
[14:14] <asac> fta: right. i just had to sort things
[14:15] <asac> fta: especially what to do with old nss
[14:22] <fta2> you wanted us drop the sonames
[14:22] <fta2> +to
[14:44] <asac> fta: yeah. can i push that somewhere and you review?
[14:44] <asac> i am somewhat not sure if or if not the dh_shlibs works somehow still
[14:45] <fta2> asac, after the upgrade of prism, i get the following error:
[14:45] <fta2> XML Parsing Error: undefined entity
[14:45] <fta2> Location: chrome://mozapps/content/extensions/update.xul
[14:45] <fta2> Line Number 14, Column 1:<wizard id="updateWizard"
[14:45] <fta2> ^
[14:45] <fta2> but only once
[14:46] <Jazzva> gnomefreak, I suppose you can name the package wizz-rss. I think that name is ok.
[14:47] <asac> fta2: but soname changes are not ment to enter hardy (for now)
[14:47] <asac> so we can bump those branches ... e.g. just version
[14:47] <fta2> indeed
[14:53] <fta2> the error above is on "<wizard>"
[14:59] <asac> fta2: well. that means that a translation string is msissing
[15:00] <asac> or even a "base" string
[15:02] <gnomefreak> thanks Jazzva ill finish it tomorrow morning
[15:03] <Jazzva> ok
[15:07] <asac> fta2: ok. nss is a pure - though important bug fix release
[15:37] <asac> mozillla bug 454406
[15:37] <asac> mozilla bug 431819
[16:13] <Volans> asac: for the version comparison I have found on MDC install.rdf documentation this phrase:
[16:13] <Volans> "For addons hosted on addons.mozilla.org - Mozilla's update website may repackage your addon and correct or reject malformed version strings."
[16:13] <Volans> have you some way to know what characters are allowed in AMO extension's version? I have already searched in AMO without success
[17:32] <pmatulis> asac: i confirmed that the NFS/sqlite issue does *not* exist with NFSv4
[17:35] <asac> great
[18:11] <fta2> guiness time, cu
[18:32] <pmatulis> asac: again on the NFS issue, would it be feasible to patch firefox so that it looks for the broken scenario upon startup and does the magic required to fix it (essentially remove and move around small files)?
[18:41] <asac> pmatulis: no
[18:41] <asac> pmatulis: firefox has no chance to figure out when its ok and when its broken due to NFS
[18:42] <pmatulis> asac: that's surprising
[18:42] <asac> at least so far i cannot see what might identify that scenario
[18:42] <pmatulis> asac: no way to programatically determine whether it's database is available?
[18:42] <asac> pmatulis: of course not. thats why there is the lock
[18:42] <asac> the lock is the way to determine that
[18:43] <pmatulis> well right now it can't access any data.  that's one crude way of looking at it.  no?
[18:44] <asac> pmatulis: no its not. if parentlock is broken we dont even get to the sqlite lock
[18:44] <asac> so we have to fix parentlock .lock
[18:45] <pmatulis> why not just remove them?  clearly the user wants his own profile
[18:45] <pmatulis> to be available to himself
[18:45] <pmatulis> (sorry if this is crude thinking, i'm not a dev)
[18:50] <asac> pmatulis: those locks only exist for one purpose: to prevent access to the profile from _multiple_ processes
[18:50] <asac> pmatulis: e.g. user starts firefox on host A ... then goes to a second system starts firefox on host B
[18:50] <asac> both access the same profile
[18:51] <pmatulis> asac: right
[18:51] <asac> if there were no locks, once host A writes  host B is out of sync ... this means when host B writes you have data loss
[18:51] <asac> even worse: when bost write at the same time you get corruption ... which would be similar to wiping your profile or parts of it
[18:52] <pmatulis> looks like FF nor NFS can be changed.  server team suggests NFSv2 locking is not something that can be modified
[18:52] <asac> what version is it that you are testing?
[18:52] <asac> locking is only supported after nfs client 2.6.12
[18:53] <asac> thats a minimum requirement for firefox i would guess
[18:53] <asac> (and for sqlite of course)
[18:53] <pmatulis> hmm, how to tell?  nfs-common package?
[19:00] <asac> pmatulis: please find that out ... i dont know. the nfs-common packag version looks to small. otherwise i could tell. but at least we should verify if our nfs client has that minimum version requirement ... but i have no time
[19:00] <asac> pmatulis: there should be others in ubuntu that know about that ,)
[19:00] <asac> pmatulis: i have no time because here are really high-fires going on
[19:03] <pmatulis> asac: allright, no more on this, thanks for your time
[20:08] <armin76> asac: bumb
[20:23] <asac> armin76: what to bump?
[20:24] <armin76> yourself!
[20:25] <asac> armin76: unfortunately there is nothing higher than $DEITY ... so i cannot be bumped anymore :-P
[22:01] <fta> back
[22:06] <fta> SUNBIRD_0_9_RC2
[22:06] <fta> HG_COMM_INITIAL_IMPORT (wtf?)
[23:33] <Volans> asac: there?
[23:53] <asac> Volans: yeah
[23:53] <Volans> asac: what is the correct url for extension branches?
[23:54] <asac> Volans: what do you mean?
[23:54] <asac> in control?
[23:54] <asac> or in real?
[23:54] <Volans> I don't find them in mozilla-team nor in mozilla extensions team...
[23:54] <Volans> on launchpad
[23:54] <asac> ah
[23:54] <Volans> for the initbranches
[23:54] <asac> well firefox-extensions is the product
[23:54] <asac> Volans: ^^
[23:54] <asac> code.launchpad.net/firefox-extensions
[23:54] <asac> there are two kinds: ~SOMETHING ... and ~ubuntu-dev
[23:54] <asac> ubuntu-dev is always the branch as it was uploaded
[23:55] <asac> ~SOMETHING are either actively developed, suggested for merging or old not properly abandoned branches ;)
[23:55] <Volans> damn... I was searching in team's code page.. not project
[23:55] <Volans> I can assume that name.upstream branches have ALWAYS "name" == "ubuntu source package name"
[23:55] <asac> Volans: we dont have a closed set of maintainers for those
[23:55] <asac> its ~ubuntu-dev mostly
[23:56] <asac> and all contributors that suggest for merging
[23:56] <asac> Volans: but if you are talking about the import ...
[23:56] <asac> at best make the prefix configurable ;)
[23:56] <Volans> sure
[23:56] <Volans> but I want to test also
[23:57] <asac> yeah
[23:57] <asac> Volans: for testing push it: lp:~volans/firefox-extensions/ext.upstream
[23:58] <asac> Volans: or maybe to not pullute this put it in +junk for testing ;)
[23:58] <Volans> ok, and init-branches.sh should download only .upstream or also .ubuntu branches of a given package?
[23:58] <asac> didnt know that you are writing init-branches already
[23:58] <asac> ;)
[23:59] <asac> Volans: what scripts exist currently?
[23:59] <asac> mirror
[23:59] <asac> get-queue
[23:59] <asac> get-xpi
[23:59] <asac> ;)
[23:59] <Volans> atm I have fully functional:
[23:59] <asac> import-xpi
[23:59] <asac> ok
[23:59] <Volans> mirror.sh