[14:07] {"remaining_hits":0,"hourly_limit":100,"reset_time":"Tue Apr 14 13:10:34 +0000 2009","reset_time_in_seconds":1239714634} [14:07] at install helps :) [14:08] hum ? [14:08] BUGabundo1: had to install curl i was using apt-get curl :( [14:08] i get same output [14:12] i get this feeling im forgetting something [14:14] hjmf: cu [14:18] oh crap [14:18] im using 0.8 [14:19] heh [14:19] thats a solid release [14:19] forgot to enable the gwibber repos solid but still twitter is broken ;) [14:20] ok updating to daily now. I will screw with it more when i get home this afternoon. I still have to figure out where i went wrong in SM [14:21] gnomefreak: use the gwibber team ppa [14:21] i am [14:21] i think [14:21] well that has 0.9.2 [14:21] and not 0.8 [14:22] nope daily im using i dont have team repos i dont think [14:23] BUGabundo1: what version do you have installed [14:24] from your april 12th comment you are not current [14:24] 1.0.2~bzr294-0ubuntu1~daily1 is up to date daily [14:24] dch -r [14:24] damnit [14:27] ok im gone i have to leave in a gfew minutes and havent started to get ready yet [14:28] gnomefreak: 1.0.2~bzr294-0ubuntu1~daily1 [14:29] asac, saw your merge request, good i didn't push that 0.9.2 to universe ;) [14:33] fta2: hehe ;) [14:33] i dont think we want to bump for jaunty [14:34] thats karmic. gwibber folks were just too late [14:42] asac, hmm, does twitter work in jaunty? (0.8.*) [14:42] fta define work! [14:43] donno, i'm not using twitter at all but people seem too be complaining about broken twibber with gwibber from universe [14:43] -too+to [14:44] daily ppa is working me, other then the 400 errors due to throtelling [14:44] some users are getting caught on GKD, but I didn't, don't know why [15:06] fta2: twitter changed something, there is a patch in trunk that fixes it [15:22] not sure what is supposed to be broken, but 0.9.2 works here with twitter [15:22] and 0.8 as well iirc [15:22] let me downgrade again [15:33] can I just copy my urlclassifier3.sqlite from one profile to the other? [15:33] I created a new 3.6 profile, but miss my 3.5 history [15:48] BUGabundo1: given that the new profile is new and risk of losing things is low, just copy it [15:49] okay [15:49] will do, when I close both [15:49] anything else? places.sqlite, maybe? [15:49] I used xmarks (ex-foxmarks) to import bookmarks and pass [15:49] but history didn't came [15:50] BUGabundo1: places.sqlite [15:50] yes [15:50] thats where the bookmarks and history are [15:51] isn't it urlclass? [16:49] BUGabundo1: is there a bug for twitter/gwibber open? [16:51] which one? [16:51] there are so many [16:53] BUGabundo1: nevermind [16:53] ;) [16:54] asac: https://bugs.launchpad.net/bugs/360468 https://bugs.launchpad.net/bugs/359885 [16:54] Launchpad bug 360468 in gwibber "Gwibber 1.0.2: HTTPError: HTTP Error 401: Unauthorized" [Undecided,Triaged] [16:54] this are the most active right now [17:09] asac: what is "martion source" ? [17:11] martian? [17:11] yes [17:11] typo [17:11] on #ubuntu+1 [17:11] user is getting that on the syslogs [17:12] BUGabundo1: if you say something comes from martian source it means (afaik) that something happens magically without knowing the source [17:12] ahh [17:12] BUGabundo1: for PCI events? [17:12] NM I think [17:12] BUGabundo1: please paste syslog. cannot find it on the other channel that quick [17:12] he rebooted to 8.10 to check [17:13] only place i think to remember that message was interrupts [17:13] martian means that there are interrupts the kernel cannot associate with anything (e.g. buggy bios) [17:14] asac: read "hwm" comments on +1 [17:15] yeah [17:15] hmw: how can i share a internet connection (hsdpa) with other pcs on my lan? my usually working script (route, forwarding, iptables, dhcpd) wont work with ubuntu. Syslog reports "martian source". This is my "router" script: http://pastebin.com/f22c41762 [17:15] unlikely to be martian source [17:15] anyway. that script looks not-compatible with anything NM wants [17:15] nm automatically sets up the iptables rules [17:15] so better not do anything manually [17:16] can't wait to see if nm0.8 has an easy way to share wireless networks via other connections [17:16] and not default to wired as 0.7 does [17:16] "echo 1 > /proc/sys/net/ipv4/conf/all/log_martians          # Log packets with impossible addresses" [17:21] BUGabundo1: heh right [17:21] thats a firewall rule [17:22] yeah. i would think its his router script [17:22] he should dump that in the river [17:22] or not use NM [17:30] ehh [17:37] asac: Is there any chance of getting bug 359382 fixed? [17:37] Launchpad bug 359382 in firefox-3.0 ""Ubuntu Wiki" default bookmark does not point to the wiki home page" [High,Triaged] https://launchpad.net/bugs/359382 [17:49] sigh... [18:03] bdmurray: kind of late [18:04] bdmurray: let me check [18:04] asac: so maybe talking to somone about a redirect is best? [18:05] bdmurray: redirect would also cure all the old releases [18:05] so i think its a good idea to do that in anycase [18:09] asac, is it still possible to send fixes to universe? i introduced a regression in ia32-libs :( bug 360870 [18:09] Launchpad bug 360870 in ia32-libs "libstdc++.so link in amd64 ia32-libs is wrong" [Undecided,New] https://launchpad.net/bugs/360870 [18:10] fta2: keep the change minimal, attach planned debdiff and subscribe motu-release to get an ack [18:11] fta2: also set bug to in progress, assign to you and bump importance to something != undecided ;) [18:12] k [18:35] fta isn't 3.5 be in universe?? [18:37] BUGabundo1: it is [18:37] 500 ftp://archive.ubuntu.com jaunty/universe Packages [18:37] there it is [18:37] the other day I didn't find it :( [18:43] fta just got a bunch of new user for 3.5 on +1 eheh [18:43] I still wonder where you got those stats of users for ff and chrome [18:45] BUGabundo1: popcon [18:45] popcon.ubuntu.com [18:47] fta2: fyi: https://code.edge.launchpad.net/~mozillateam/xulrunner/xulrunner-1.9.1.jaunty + https://code.edge.launchpad.net/~mozillateam/firefox/firefox-3.1.jaunty [18:52] ahh [18:54] I'm back [18:54] hjmf: can you also port the patch for the other branches we have? [18:54] asac: I'm going to do it right now. [18:54] If I do remember right first I have to branch those branches [18:54] merge [18:54] change things [18:55] commit [18:55] and finally push? [18:55] ? right [18:56] hjmf: 1. pull branch; 2. change and edit changelog; 3. debcommit; bzr push lp:~USERID/project/lpBUGID [18:56] hmmm, things changed a bit... [18:56] then you request a merge by going to that branch on LP and clicking "request merge" [18:56] hjmf: hehe. yeah. debcommit is quite nice ;) [18:57] any manual? never mind I'll search for it :-) [18:57] hjmf: its just debcommit [18:57] OK [18:57] hjmf: or debcommit -e if you want to edit the suggested commit msg [18:58] hjmf: if you commit it in two steps (e.g. first, just change the pluginreg.dat fix) and second: cleanup), we can cherry pick the change to the stable branches [18:58] (only relevant for firefox-3.0.head and maybe firefox-3.1.head) [18:59] no problem, I'll do in two steps [18:59] hjmf: look in changelog how to give you credits in an existing changelog [18:59] if you dont know ;) [18:59] like [ ... ] [19:00] Maybe that's the only thing that seems to be as I remember [19:00] :-P [19:01] :-) [19:05] fta2: didnt you say you had daily bzr branches somewhere? [19:06] e.g. so one can just branch and work on build failures [19:06] getting right orig and stuff from ppa [19:06] ah cool. found them [19:08] fta2: hmm. maybe we can keep only one commit on top of what we have in .head on that branch? [19:08] that would make it easy to just pull that, fix it and push to .head [19:08] without getting many commits [19:10] * hjmf is off for a while [19:28] fta or asac when will 3.6 be renamed Namoroka ? [19:29] as soon as there is a branch for it upstream [19:31] ok [19:31] nice to know [19:35] BUGabundo1, it's unlikely to happen before 3.5 final gets released. minefield means trunk and will always means trunk [19:38] ok [19:38] so its not like debian sid [19:38] or jaunty [19:38] stupid question: why not just call it TRUNK? [19:40] sounds too harmless [19:40] minefield describes it best ;) [19:40] eheh [19:40] time to go [19:43] asac, what about gwibber & rev50? [19:43] lack of context [19:44] fta: cutting a stable branch for jaunty [19:44] fta: kenvadine backported two patches ... he landed them now on top of revision 50 [19:45] so we can get it in (either directly or as SRU) [19:45] fta: he will probably request a merge soon. i wanted to poke it a bit more [19:45] !info sqlite jaunty [19:45] sqlite (source: sqlite): command line interface for SQLite. In component main, is optional. Version 2.8.17-4build1 (jaunty), package size 15 kB, installed size 80 kB [19:45] !info sqlite3 jaunty [19:45] sqlite3 (source: sqlite3): A command line interface for SQLite 3. In component main, is optional. Version 3.6.10-1 (jaunty), package size 20 kB, installed size 88 kB [19:45] !info sqlite3 koala [19:45] 'koala' is not a valid distribution ['dapper', 'gutsy', 'gutsy-backports', 'hardy', 'hardy-backports', 'intrepid', 'intrepid-backports', 'jaunty', 'jaunty-backports', 'kde4-ppa', 'kde4-ppa-intrepid', 'kubuntu-experimental', 'kubuntu-members-kde4', 'medibuntu', 'partner'] [19:45] fta: will you create that "stable maintenance" branch ? [19:45] (so he has a merge target) [19:45] bah [19:45] like gwibber.jaunty [19:46] Mozilla/5.0 (X11; U; Linux sparc64; en-US; rv:1.9.2a1pre) Gecko/20090414 Gentoo Firefox/3.6a1pre [19:46] asac_the_bumber: jackalope is also not a known branch ;) [19:46] asac_the_bumber: it will be "karmic" [19:46] asac: update sqlite to 3.6.13! [19:46] fta: so similar to what i did to all mozillateam branches (all i remembered ;)) [19:47] all main branches [19:47] asac_the_bumber: not for jaunty [19:47] why not? [19:47] 3.6.10 is rocking the boat here ;) [19:47] asac_the_bumber: we are in deep freeze [19:47] that version has unaligned acceses [19:47] alto, alto ;) [19:48] bumb quick [19:48] asac_the_bumber: hppa doesnt justify a deep freeze breach combinined with new upstream exception ;) [19:48] its not hppa :P [19:48] even sparc and hppa combined ;) [19:48] asac_the_bumber: does it fix arm? [19:48] thats the only supported arch ;) [19:48] (but first we need a crash report i guess ;)) [19:48] hah [19:49] well, i'm just trying now with 3.6.13, which should be fixed [19:50] asac_the_bumber: so is sqlite also compiled with no-align-error? [19:50] i'll find out if there's something that needs to be done on trunk [19:51] asac: i have no clue [20:12] asac, if you do a new 3.0, please remember the build-system... [20:13] fta: yeah. i hope i have time to get that in this round :( [20:13] i have a huge backport backlog :( [20:14] it's in ff3.head already, just cherry pick it [20:14] but i saw the build failure [20:15] fta: its not a single commit, but more spread over like 6 commits [20:15] revno: 285 [20:15] revno: 286 [20:15] revno: 323 [20:15] revno: 325 [20:15] revno: 326 [20:15] think thats all [20:15] lets check ;) [20:16] really? i don't remember [20:16] ;) [20:18] i will see how far i get ;) [20:22] fta: you want to be subscribed to the jaunty 1.9.1 and 3.1 branches? [20:22] should be pretty low traffic ;) [20:22] (otherwise we are doing something wrong) [20:45] do you mean for bugs? or commits? [20:46] fta: commits [20:46] ok for commits [20:47] done [22:36] asac: are you around [22:36] asac: ? [22:36] asac: how can I check which is the current version of a package [22:37] I'm going to edit the changelog to reflect the changes made in the apport hook [22:37] asac: I mean: firefox-3.0 (3.0.8+nobinonly-0ubuntu4) UNRELEASED; urgency=low [22:42] for example, in the ppa repos the last build of firefox-3.1 is the version 3.5~b4~hg20090414r24561+nobinonly-0ubuntu1~umd1 [22:44] ... and for jaunty the last one for firefox-3.0 is 3.0.8+nobinonly-0ubuntu3... [22:45] it is just that I want to be sure to put the right number. [22:46] asac: I'll do the debcommit && push when I get this thing clear :) === asac_ is now known as asac [23:44] hjmf: so we work on .head branches only [23:45] hjmf: we bump changelog version either when we release or when the patches need to be adjusted [23:45] so for stable products like firefox-3.0 we only commit stuff for new releases usually [23:45] asac: so... [23:45] asac: I've left the version number intact in the 3.0 changelog [23:46] hjmf: right. if on .head branch is UNRELEASED you dont need to change that [23:46] good [23:46] just add the new changelog entries and done [23:46] asac: I've just send the merge proposals for 3.0.head [23:47] one for the bug and another for the little refactoring [23:47] hjmf: ok so you named the branch thje same as the .head branch. its better to name it like the topic [23:47] e.g. lpXXXX_apport_hooko improvements [23:47] otherwise you need to delete your branch for the next contribution and so on [23:48] not a problem. just ahint for best practices [23:48] asac: I see [23:48] I'm trying to learn :) [23:49] so this will be better: bzr push lp:~hmontoliu/firefox/firefox-3.1.apport_hook [23:49] hjmf: so when you submit a single branch you only need a single merge request. e.g. https://code.edge.launchpad.net/~hmontoliu/firefox/firefox-3.0.head/+merge/5545 now has both commits so the other wasnt necessary [23:49] hjmf: yeah. except that without lp bug id you can only create one branch for apport_hoook ;) [23:50] hjmf: oh the other was ment to be ffox 3.1 [23:51] asac: ? [23:51] hjmf: you submitted the wrong branch ;) (https://code.edge.launchpad.net/~hmontoliu/firefox/firefox-3.0.head/+merge/5543 -> you requested to merge 3.0.head into that) [23:51] I need a manual :-( [23:52] hjmf: so https://code.launchpad.net/~hmontoliu/firefox/firefox-3.0.head/+merge/5545 is good [23:52] something beter than this https://wiki.ubuntu.com/MeetingLogs/devweek0809/MozillaTeam :-P [23:52] hjmf: you did your change on top of 3.0.head [23:52] and submitted that as a merge request [23:52] thats good [23:52] yes, I thought so [23:53] in both cases, [23:53] however, the other merge request: https://code.edge.launchpad.net/~hmontoliu/firefox/firefox-3.0.head/+merge/5543 [23:53] you changed on top of firefox-3.0.head and asked to merge that branch into our firefox-3.1.head [23:53] the right way would have been to do the change on top of firefox-3.1.head and ask that to be merged into firefox-3.1.head [23:53] makes sense? [23:54] hjmf: ok merged the 5545 merge request [23:54] err approved ;) [23:54] hmm makes sense I select the default "Merge into: lp:firefox" but in the second proposal I noticed that it was pointing to 3.1 so I changed to 3.0 [23:55] I thought it was a mistake in the second proposal [23:55] but the wrong one was the first [23:55] hjmf: yeah [23:55] asac: I see... [23:55] hjmf: i think we have 3.1 as current development focus for the firefox project [23:55] so thats probably suggested by default [23:56] thanks to point that [23:56] asac: back to the version number, in the changelogs of 3.1 where can I check for the current version [23:57] in the ppa repo? [23:57] hjmf: look how the changelog loks now in mozillateam .head branch [23:57] hjmf: thats how i ment it ;) [23:58] Committed revision 394. [23:58] hjmf: http://bazaar.launchpad.net/%7Emozillateam/firefox/firefox-3.0.head/revision/394/debian/changelog [23:59] hjmf: the current version is whatever is currently on top with UNRELEASED [23:59] (re 3.1)