/srv/irclogs.ubuntu.com/2010/07/14/#ubuntu-mozillateam.txt

yofelfolks, the firefox-4.0 package from the daily ppa gives me: http://paste.ubuntu.com/463223/ (i386)00:00
micahgyofel: you use ubuntuzilla?00:04
yofeler, what's that?00:04
micahgyofel: ugh seems like a prerm issue00:06
* micahg needs to learn that graph for when which file is used00:06
micahgyofel: which version was installed previously?00:07
yofelsec00:07
yofelPreparing to replace firefox-4.0 4.0~b2~hg20100712r47317+nobinonly-0ubuntu1~umd2 (using .../firefox-4.0_4.0~b2~hg20100712r47341+nobinonly-0ubuntu1~umd1_i386.deb) ...00:08
micahgyofel: ugh, that's my fault :(00:09
micahgyofel: first the profile was 3.7, then 4.000:09
micahgyofel: tonights upgrade should fix it then00:10
yofelok, thanks :)00:10
yofeloh great, trying to look up ubuntuzilla on sf.net results in the sf page crashing aurora and rekonq00:11
micahgyofel: I guess that's more bugs to file :)00:12
yofelindeed :D00:12
micahgyofel: I'm running the same version you were before03:47
micahgthere shouldn't have been a conflict there03:47
BUGabundo_remoteasac: what's the current ppa for TB 3.1?09:35
asacBUGabundo_remote: 3.1 is in daily ppa ... but seems to fail ;)10:33
BUGabundo_remoteasac: wasn't micah supposed to give it own PPA?10:33
BUGabundo_remotelong long agio10:33
asachmm10:40
asaci think that never happened10:40
asacfor -stable we have separtae ppas maybe10:40
BUGabundo_remotemaybe10:44
BUGabundo_remoteis there a stable for 3.1?10:44
yofelabout bug 557240: would that be SRUable and if yes before 10.04.1?11:41
ubot2Launchpad bug 557240 in ubufox (Ubuntu Lucid) (and 1 other project) "Disable "Report a Problem" menu item for the stable release (affects: 2) (heat: 47)" [High,Triaged] https://launchpad.net/bugs/55724011:41
yofelit seems everyone forgot about that11:41
=== BUGabundo_remote is now known as BUGabundo_lunch
chrisccoulsonyofel, nobody has forgotten about that, it's just that nobody has had time to do anything with it13:35
yofelchrisccoulson: the patch works fine here, I'm not sure if the branch I attached is correct13:38
=== BUGabundo_lunch is now known as BUGabundo_remort
=== BUGabundo_remort is now known as BUGabundo_remote
micahgchrisccoulson: did you think about instantbird and weave yet?  I'm thinking maybe we should keep them15:39
chrisccoulsonmicahg - i'm not so sure about weave. how certain is it that the functionality will be merged in to FF4.0?15:40
chrisccoulsoni was thinking about keeping instantbird as well though, but i want to have a play around with it first15:41
chrisccoulsonit looks pretty cool15:41
chrisccoulsonand the screenshots on their website are taken on ubuntu ;)15:41
micahgchrisccoulson: k, I want to file an archive admin bug to add mongodb and instantbird and weave if we keep them15:42
micahgto the package set I mean15:42
chrisccoulsoncool, no problem15:42
chrisccoulsoni need to fix instantbird so that it builds, i'll probably do that this afternoon15:42
micahgchrisccoulson: mongodb is currently unusable in Lucid because of a problem finding mozjs, I haven't had a chance to look at it yet, it slipped under the radar during the cycle15:44
micahgchrisccoulson: yes, from all the blog posts, it looks like weave/sync will be in 4.015:48
micahgchrisccoulson: but we're not shipping 4.0 with maverick :)15:49
chrisccoulsonmicahg - right, but maverick probably won't be on 3.6 for too long after release (assuming the release schedule doesn't slip, we'll probably be migrating to 4.0 early next year)15:50
micahgchrisccoulson: well, I would think, hopefully until Apr 2011 :)15:50
chrisccoulsonmicahg - i don't mind too much. is it building native components?15:51
micahgchrisccoulson: If we can hold out until Firefox 4.1 that'll be better, maybe we can only migrate once in the maverick cycle15:51
micahgchrisccoulson: yes, that why I think it should be kept15:51
chrisccoulsonmicahg - ok, so we should probably keep it then15:52
micahgchrisccoulson: I'm trying to remember if there are any other rdepends I forgot about15:53
micahgmediatomb :)15:53
micahgk, so I'll file an archive admin bug to add those 4 sources to the mozilla package set15:53
chrisccoulsonthanks15:54
micahgchrisccoulson: I haven't looked at the rdepends in main this cycle yet, willl you be taking care of those?15:55
asacwhere is the firefox-3.7.head branch nowadays? is that 4.0?15:56
micahgasac: yes15:56
asacah ... me changes checkout location15:56
BUGabundo_remotemicahg: http://brainbird.net/file/BUGabundo-20100713T213810-mfy4wkc.jpeg15:57
asachmm. you guys upgraded the branch to 2.0a?15:57
micahgasac: that was an accident, I wasn't warned about it15:57
asachmm15:58
asacnot my call ;)15:58
micahgasac: fta__: said to go with it and see if there are issues15:58
asacbut i hate 2.0a15:58
asacbecause hardy users cant branch it ;)15:58
asachuge mistake by bzr team imo to make it default before hardy is EOL15:58
asacbad for bzr reputation as a relyable thing15:58
micahgasac: right, I'm going to check the branches before merging now to make sure that doesn't happen to any others15:59
asacwell. its too late15:59
asacthe idea was that all mozillateam branches are fine15:59
asacnow there is not much point ;)15:59
chrisccoulsonb'ah, my laptop is completely unusable with maverick on it :/15:59
micahgasac: at least they backport in a PPA for hardy users16:00
micahgasac: I'm confused, is xine-plugin a xul rdepend? it seems to depend on nspr16:01
asacyes16:01
asacmight also use nspr directly (or nss)16:01
=== fta__ is now known as fta
asacok so after this upgrade and can remove all mozillateam branches :/16:01
asacit busted my repo16:01
ftaasac, when i hit that, it was already too late16:02
asacmicahg: i am pushing a good --pack-0.92 branch16:03
asacto the old location16:03
asacyou can kill the 4.0 branch and replay ;)16:03
asachmm. takes a bit longer16:04
asaci dont understand why bzr folks dont allow to lock donw the branch format. i dont want any branch to be updated by accident16:06
* asac goes and deletes 3.7 branch again and hopes that launchpad forgets the format16:07
micahgBUGabundo_remote: what was the pic?16:09
asachell how can i tell bzr to NOT stack a branch16:09
micahgchrisccoulson: do you think nspluginwrapper is ok to request as well?16:10
chrisccoulsonmicahg - yeah, should be16:10
micahgasac: do you know if nspluginwrapper upstream moved or is it dead?16:10
asacdead16:11
asacit was never really alive ;)16:11
asacjust got some defilbration shock treatments back then to make this working for flash 10 :)16:11
micahgasac: you mentioned before that 1.3 was a devel tree, Debian has been running it for some time already, do you think I should merge it or just try to fix the one known issue with GDK_NATIVE_WINDOWS on amd64?16:12
asaci dont care. get feedback on 1.3 in a ppa maybe.16:12
asacbefore upgrading16:12
asac1.3 is a pre-alpha... but if it helps then fine16:13
micahgasac: k, thanks16:13
micahgasac: is there a channel for armel porters in Ubuntu?  I have a couple failures that I'm not sure what to do with16:14
asacgrr ... i really hate bzr now16:16
BUGabundo_remotemicahg: pure awesomeness16:17
asacmicahg: ok i found a way .... delete branch ... run bzr init --pack-0.92 lp:~mozillateam/firefox/firefox-4.0.head16:30
asacthen you can push a fresh branch of the branch i currently create using the firefox-3.7.head16:31
asacis a workaround16:31
asacseems that launchpad changed the default to stack branches, which caused the implicit upgrade bacecause it needs format 6 to support stacking16:31
asacthe remote init (after delete) does the trick)16:31
asacki will let you know when the 3.7 branch is pushed16:32
micahgasac: k16:32
asacthough my branch might not be good either anymore because i did a pull initially16:32
asac(which failed, but could be its stuck in the middle wrt fromats now)16:33
micahgasac: you can run bzr check to see16:33
asacwell. bzr info -v also shows a bunch of nubmers16:33
asaci think its all fine ;)16:33
asaclets see what happends when i branch after the push16:33
micahgah, ok16:34
=== fta_ is now known as fta
chrisccoulsonwow, 10 minutes and counting to create a source package is just crazy17:27
micahgasac: awesome, it looks like it worked17:35
micahgfta: asac fixed the ff4.0 branch format, can I move it back into place under firefox-4.0.head?17:36
ftamicahg, do it, but i assume it will break the dailies17:37
micahgfta: k17:37
micahgfta: you might want to resubscribe as well17:42
micahgfta_: you might want to resubscribe as well17:42
=== fta_ is now known as fta
=== gavin__ is now known as gavin
asacmicahg: you cant move17:56
asacyou have to do bzr init --pack-0.92 with the new url (e.g. creat an empty branch)17:56
asacand then you can push my branch there17:56
asac(that should work)17:56
micahgasac: yes, you can rename the branches18:05
micahgasac: and I rebranched your branch18:06
micahgso the old one won't be used anymore18:06
micahgs/rebranched/branched locally/18:06
micahgasac: and my local copy shows branch format 6 now instead of branch format 718:07
asacyep18:08
asacalso bzr info with some luck says pack-0.9218:08
asacok out (communiting)18:08
micahgasac: on launchpad it does :)18:08
micahgasac: thanks18:09
=== fta_ is now known as fta
=== fta_ is now known as fta
chrisccoulsonjdstrand - i pushed the pre-release version of seamonkey to the PPA today, before i realised that we haven't published 2.0.5 yet in lucid19:44
chrisccoulsonis it still possible to do that?19:44
jdstrandchrisccoulson: possibly19:45
jdstrandchrisccoulson: well, actually, no19:45
jdstrandchrisccoulson: well, possibly19:45
jdstrand:)19:45
chrisccoulsonheh19:45
chrisccoulsoni wasn't sure if the binaries have disappeared or not ;)19:45
jdstrandlet's just say it is an operation I've not ever attempted19:45
jdstrandno, they haven't19:46
jdstrandyou could delete the one in the ppa now, then move the other back in place, at which point I could publish to the archive19:46
jdstrandthat should work19:46
chrisccoulsonhmmm, how do i do that?19:47
jdstrandI just don't think I can publish your superceded one with our current tools19:47
jdstrandchrisccoulson: if you'd like, I can do it19:47
chrisccoulsonjdstrand, if you don't mind, that would be great :)19:47
jdstrandchrisccoulson: done19:53
chrisccoulsonjdstrand, excellent, thanks19:53
jdstrandchrisccoulson: how I did it was I used 'Delete packages' followed by 'Copy packages'19:53
chrisccoulsonah, ok. makes sense now :)19:53
jdstrandchrisccoulson: it is a little weird copy packages to the same ppa, but that is how you do it19:53
micahgmdeslaur: did Seamonkey never make it to Lucid?20:06
chrisccoulsonmicahg, it didn't20:06
micahgchrisccoulson: k, should we wait a week and push 2.0.6?20:07
chrisccoulsoni'd just been discussing that with jdstrand before you reappeared20:07
micahgchrisccoulson: ah20:07
* micahg checks logs20:07
micahgchrisccoulson: k, so 2.0.5 is going20:08
micahggreat20:08
chrisccoulsonmicahg, yeah, that's the plan20:08
micahgchrisccoulson: are you planning on SRUing the newsblog fix in 2.0.6?20:09
micahgchrisccoulson: I also realized I forgot to do the back changelogs for hardy, jaunty, karmic20:09
chrisccoulsonmicahg - yeah, probably. i need to get a SRU ack for that though20:09
micahgchrisccoulson: k, I think that fix should deifinitely go in the hardy/jaunty/karmic 2.0.6 builds20:10
bobbyOMG, micahg I love you, thanks for FF4.0B <320:10
micahgbobby: enjoy :)20:10
bobbyNo more Java crashing :D20:11
micahgchrisccoulson: I need to make a ubuntu-mozilla-ppa-bugs project, should the owner be the team?  should the team be the bug supervisor?20:11
bobby... There isn't a bugs project yet?20:11
chrisccoulsonmicahg, yeah, that should be fine (making the team the owner)20:11
micahgchrisccoulson: that means the whole team will get e-mail for the PPA bugs20:12
micahgbobby: not for PPA bugs20:12
micahgchrisccoulson: well, not because of owner, but because of bug supervisor20:12
chrisccoulsonmicahg - ah, maybe that's not such a good idea20:12
micahgchrisccoulson: so, should I make another bugs team for that PPA?20:13
bobbyShiretoko? When the heck did FF4 get a codename?20:13
micahgbobby: not the codename for it20:14
micahgbobby: that was 3.520:14
micahgbobby: I'll try to fix that tonight :(20:14
bobby... So, why am I using the Shiretoko Wbe Browser Firefox 4.0 beta20:14
bobbyOh, okay, lol20:14
bobbyI was gonna say...20:14
micahgchrisccoulson: then I'll update the apport hook to report bugs there if they're from a PPA20:15
bobbyHey, anyone here know when the interface is getting update for 4.0?20:15
micahgchrisccoulson: do you want to receive the PPA bugmail?20:15
chrisccoulsonmicahg - yeah, i probably should do20:16
chrisccoulsoni'm just trying to work out how it works at the moment20:16
micahgchrisccoulson: k, so I'll make a team with you, me and ddecator20:16
micahgassuming he wants it :)20:16
chrisccoulsonmicahg, we should probably have a team similar to mozilla-bugs (called mozilla-ppa-bugs or something), which we use as the bug contact20:17
micahgchrisccoulson: with a ML that's subscribed to?20:18
micahgchrisccoulson: or just for the team membership to get the bugs20:19
chrisccoulsonmicahg - we probably don't need a mailing list20:21
chrisccoulsonwe could just create the team and make mozillateam a member, much like how mozilla-bugs works already20:22
micahgchrisccoulson: k, I'll set it up tonight, probably won't fix the apport hook till the weekend though20:22
chrisccoulson(and i've just realised why i get 2 mails for every bug)20:22
micahgchrisccoulson: no, mozilla-bugs has an ML, that's why we don't get the bugs20:22
chrisccoulsonmicahg - ah, i get it now. we should probably do it the same way then20:24
micahgchrisccoulson: I don't think we need the overhead of the ML20:25
micahgchrisccoulson: plus these are bugs that are for prereleases, so I don't they need to be archived20:25
micahg*think20:25
chrisccoulsoni'm slightly confused now. is there a team setting to not receive bug mail? i'm just wondering why i don't get mail for mozilla-bugs20:27
micahgchrisccoulson: because it goes to the Mailing list since that's the team contact address20:27
chrisccoulsonah, now that makes sense20:27
bobbyHey micahg... JS still isn't working :(20:35
micahgbobby: what do you mean?20:35
bobbyWell, when I try to open up a site that uses Javascript (Newegg in particular), it just doesn't load20:36
micahgbobby: that's weird20:36
bobbyThe little clock thing is about 80% full, and it says "Loading..." but it never loads...20:37
bobbyJava works fine though from what I've used though.20:38
micahgbobby: I'll have to look into it later20:39
bobbym'kay20:39
micahgbobby: BTW, saw an article that the new JS engine will be in around Sep 120:40
bobby*Twitch*20:40
bobbyHow about July 14th?20:40
micahgbobby: it should still work, I'm talking about Jaegermonkey20:41
bobbyYeah, I know :P, Oh yeah, why is 4k video on youtube running slow :P?20:42
micahgbobby: flash or HTML5?20:42
bobbyFlash :P, HTML5 on YouTube runs slow on any browser :P20:42
micahgbobby: idk, can't do anything about flash being slow20:43
bobbyIs it because it is in the new 4k resolution, would that slow it down?20:43
micahgbobby: yeah, that might do it :)20:45
bobbyOh okay. BTW: HTML5 video on YouTube runs slow, but I don't think that it is FF. The player itself is what is lagging, especially the interface20:45
bobbyHTML5 is too experimental ATM.20:45
micahgbobby: unless you have lots of RAM and a GPU w/RAM as well20:45
micahgbobby: well, it works pretty well20:46
bobbyHey! 4GB of DDR2 RAM, and an NVIDIA 9600M GT - 512MB dedicated, overclocked to 575MHz!20:46
ftahtml5/youtube is smooth here20:47
ftachromium20:47
chrisccoulsonmicahg - nice, i got instantbird working now20:47
micahgchrisccoulson: cool, I fix weave this weekend20:47
chrisccoulsonthanks20:47
micahgchrisccoulson: BTW, 0.2 was released20:47
micahginstantbird20:47
chrisccoulsonmicahg - do you think we should be shipping a symlink in /usr/include/xulrunner-1.9.2.7/ pointing to /usr/include/nss, much like we do already with nspr?20:48
chrisccoulsoninstantbird is looking in there for the nss headers, and i'm just wondering which one is right20:48
chrisccoulsonthe upstream SDK has a nss folder20:48
chrisccoulsonbut no headers in it :/20:49
chrisccoulsonoh, actually, the upstream xulrunner SDK does ship the nss headers20:49
chrisccoulsonperhaps we should be symlinking those then20:49
micahgchrisccoulson: yeah, that makes sense, I think we've been patching them to use pkg-config to find teh headers20:50
chrisccoulsonok, i'll add a symlink in our xulrunner packaging20:50
micahgchrisccoulson: I think we should probably test rebuild all the rdepends against it to see if there are any issues, what do you think?20:52
chrisccoulsonmicahg - yeah, can do20:52

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!