[07:43] <clearscreen> asac: if I were to be interested in doing what you talked to about Jazzva yesterday... is there any kind of RSS feed that can notify me whenever a new revision pops up?
[10:55] <ziroday> Hi, is firefox intergration with notify-osd being worked upon and where?
[11:36] <gnomefreak> what app is used to shut down? hal?
[12:07] <gnomefreak> asac: have you been doing dailies by hand? or did fta get back?
[12:24] <asac> clearscreen: i dont think so. let me check
[12:24] <asac> gnomefreak: we fixed dailies
[12:24] <gnomefreak> asac: ah ok :)
[12:24] <asac> fta isnt needed as the uploads happen automatically
[12:25] <clearscreen> asac: also, when can we expect Fx3.5 showing up on testing repository? :)
[12:25] <asac> clearscreen: what is "testing" repository?
[12:25] <asac> clearscreen: maybe check if you can subscribe to PPA of https://edge.launchpad.net/~ubuntu-mozilla-daily
[12:26] <clearscreen> Well I used to run Debian, but I was refering to karmic on ubuntu
[12:26] <asac> clearscreen: karmic already has ffox 3.5
[12:26] <clearscreen> asac: I wasn't aware of that :)
[12:26] <asac> also jaunty has
[12:27] <asac> jaunty has some pre b4 snapshot (will be updated to b4 soon)
[12:27] <asac> karmic has b4
[12:27] <clearscreen> I see
[12:29] <clearscreen> asac: I'm relatively knew to its development process; so why is there active development in both 3.0x (3.1?) and 3.5? I'm trying to put this into perspective..
[12:29] <asac> clearscreen: so i dont see how to subscribe to ppa mails ... the best way to do it is to load the page https://edge.launchpad.net/~ubuntu-mozilla-daily/+archive/ppa at ~8pm UTC
[12:29] <asac> clearscreen: thats when builds should have finished
[12:29] <clearscreen> Other than security fixes obviously
[12:29] <asac> clearscreen: 3.0 is security only
[12:30] <asac> 3.5 is active development. we provide the packages as previews
[12:30] <asac> but
[12:30] <asac> we also made the step and allow you to install both in parallel
[12:30] <asac> and so on
[12:30] <asac> for us its firefox-3.0 and firefox-3.5
[12:30] <asac> and not firefox
[12:30] <asac> (package name)
[12:30] <asac> debian doesnt do that
[12:30] <asac> we also have firefox-3.6 ;)
[12:30] <asac> which is trunk
[12:31] <sebner> trunk is always good
[12:31] <clearscreen> aha.
[12:31] <sebner> ^^
[12:31] <asac> yeah. the dailies definitly rock
[12:32] <clearscreen> Also, is Fx3.5 called shiretoko because of the stuff that went on with mozilla <-> debian?
[12:32] <asac> to some degree yes
[12:32] <asac> we could call it firefox, if its a milestone release
[12:32] <asac> but not for snapshots
[12:32] <asac> so we dont bother
[12:32] <clearscreen> Alright
[12:36] <clearscreen> I'm a relatively new C++ programmer, and been considering getting involved in some open-source project, but most interesting projects have huge codebases and it would take ages to familiarize myself with them, I guess...
[12:36] <asac> clearscreen: so the answer is: we dont want to bother with trademark stuff for anything except the default browser :)
[12:36] <asac> which is ffox 3 atm
[12:37] <asac> clearscreen: yeah
[12:37] <asac> clearscreen: its a bit hard to just jump into mozilla code base
[12:37] <asac> same for other big things
[12:37]  * gnomefreak working on seamonkey
[12:37] <gnomefreak> be back in a bit i have hardy and intrepid building
[12:38] <clearscreen> And even if I were familiar with the codebase, I'd probably produce suboptimal code.. so yeah, not a very good idea for me at the time :D
[12:38] <asac> clearscreen: i would think that going for C is better as those code bases in the linux stacks are usually much cleaner ;)
[12:38] <asac> clearscreen: well. the suboptimal code argument doesnt count much
[12:38] <asac> clearscreen: of course you need some basic skills
[12:39] <asac> but then you need to produce code and get it reviewed by senior developers to get the final tuning of your skills
[12:39] <clearscreen> Sorry got to break up this conversation, need to go to work :( some PHP job, *sigh*
[12:39] <clearscreen> bb
[12:39] <asac> hehe
[12:39] <asac> enjoy
[12:39] <asac> today is public holiday
[12:39] <asac> so i might not be available all the time
[12:40] <asac> going out to sun soon
[12:55] <gnomefreak> at least you have sun, it looks like rain here
[13:30] <GregW3056> Hi i'm having some trouble with firefox
[13:31] <GregW3056> would anyone be able to help me out?
[13:37] <asac> be patient folks ;)
[13:45]  * gnomefreak not really here but "having trouble with firefox" is a bit too general :(
[14:00] <asac> heh
[14:19] <asac_> reconnect while scp'ing a huge file ... bad
[14:29] <gnomefreak> this is taking forever
[14:30] <asac_> sm?
[14:30] <asac_> what are you doing? does it fail again?
[14:31] <gnomefreak> sm2 builds for karmic jaunty intrepid hardy
[14:32] <gnomefreak> asac_: no more failures :)
[14:32] <asac_> gnomefreak: heh. why do you build locally?
[14:32] <asac_> are you trying to improve packaging?
[14:32] <asac_> or just for fun
[14:32] <asac_> ?
[14:32] <gnomefreak> asac_: no im updating my PPA
[14:33] <asac_> k
[14:34] <gnomefreak> mozilla bug 485052
[14:35] <gnomefreak> ah ok ive seen that one already
[14:38] <gnomefreak> down to last build :)
[14:47] <gnomefreak> and last one is uploaded waiting for PPA to start on it :)
[14:54] <BUGabundo> good afternoon
[14:54] <BUGabundo> hi gnomefreak
[14:54] <BUGabundo> what's up with fta?
[14:54] <gnomefreak> hi BUGabundo
[14:54] <gnomefreak> BUGabundo: he took a few weeks off i thought
[14:55] <BUGabundo> ah ok
[14:55] <gnomefreak> !info flight-of-the-amazon-queen
[14:55] <BUGabundo> not seen him a while
[14:55] <BUGabundo> what a longgggg name
[14:55] <gnomefreak> thats why i wanted to see what it was :)
[14:58] <BUGabundo> gnomefreak: apt-cache not good enough?
[15:00] <gnomefreak> too hard i have 5 terminals open
[15:07] <gnomefreak> asac: we will not build with PGO unless upstream provides builds for it right?
[15:45] <gnomefreak> ok branhes and packages are done now updates
[15:56] <gnomefreak> !info firefox hardy
[15:59] <gnomefreak> finally my bug is fixed
[17:44] <clearscreen> asac: I have no clue why, but firefox built in like 5-10 min instead of the 30-40 of yesterday
[17:45] <asac> clearscreen: firefox is tiny ... xulrunner takes long
[17:45] <asac> firefox builds in 2-5 minutes usually
[17:45] <clearscreen> asac: oh. right, stupid me.. didnt realize I didnt build firefox yesterday
[17:46] <clearscreen> asac: I applied to the group @ launchpad, although I'm not entirely sure what I should do when the build breaks
[17:47] <clearscreen> and does karmic come with daily? or do I have to pull it from somewhere else
[17:47] <asac> clearscreen: karmic needs to be setup. however, the guy driving the bot is a bit away ;)
[17:47] <asac> clearscreen: so for now there are no karmic dailies
[17:48] <asac> clearscreen: i dont think joining the team would be right when you get started
[17:48] <clearscreen> That's fine, I just though that was part of the procedure
[17:50] <asac> clearscreen: i think the right way is that the daily team gets its build mail sent to mailing list
[17:50] <asac> that team is more a bot team without real members
[17:52] <clearscreen> where do I subscribe? and dont all the packages in PPA need to be built? (I dont even see Fx3.0 in that list)
[17:52] <asac> clearscreen: we currently only build the branches that you see there
[17:53] <asac> clearscreen: we dont have a mailing list setup yet ;)
[17:53] <asac> i have to check something
[17:54] <asac> clearscreen: ok i applied for maling list
[17:54] <clearscreen> Sorry for all the questions, but will I need deb (for build-dep libs) or would deb-src suffice?
[17:55] <asac> build-dep you need both
[17:55] <clearscreen> ok
[17:56] <asac> clearscreen: remember me to write something about our dailies to the wiki or something
[17:56] <asac> i will see if i can do that soonihs
[17:56] <clearscreen> Ok
[17:59] <clearscreen> Another question, can I tell apt somehow to keep older libs when installing a later one? between 3.0 and 3.5 builds it will constantly try to remove older/newer xulrunner-dev
[17:59] <clearscreen> I can manually remove those with deborphan whenever I feel like it
[18:00] <asac> clearscreen: you cannot have multiple versions of -dev at the same time for xulrunner
[18:00] <asac> the reason is that we share the same .pc filenames so they conflict
[18:00] <clearscreen> heh, k
[18:00] <asac> this gives us the ability to respin xulrunner depends by just flipping build-depends
[18:00] <asac> and see where they break
[18:01] <asac> otherwise you would always need to patch any app that uses xulrunner-dev
[18:01] <asac> which is cumbersome and sometimes non-trivial
[18:01] <asac> (configure systems have grown to bad beasts for lots of gecko clients :))
[18:02] <clearscreen> http://paste.ubuntu.com/162359/ < my uber leet build script
[18:02] <asac> clearscreen: so if you want to build against xulrunner 1.9.2 you cannot have the 1.9 dev at the same time
[18:02] <clearscreen> asac: aha ok
[18:02] <asac> clearscreen: well. actually thats not the preferred way of building our packages
[18:03] <asac> (for development)
[18:03] <clearscreen> asac: I'm open for suggestions, heh
[18:03] <asac> so what you need are the packaging branches
[18:03] <asac> create a directory: mt-bzr (mozillateam bzr) or something
[18:03] <asac> and branch
[18:03] <asac> the .head branches for the respective packages
[18:03] <asac> you can find them here:
[18:04] <asac> https://code.edge.launchpad.net/~mozillateam/
[18:04] <asac> there are quite a few. just look for those with .head at the end
[18:04] <asac> like xulrunner-1.9.2.head
[18:04] <asac> https://code.edge.launchpad.net/~mozillateam/xulrunner/xulrunner-1.9.2.head
[18:04] <asac> so you just branch them to the directory
[18:05] <asac> and when a daily fails you change the debian/changelog version to just match the one that failed
[18:05] <asac> (well not the ~umd.. suffix)
[18:05] <asac> and use bzr-builddeb to build it
[18:06] <clearscreen> stupid question again, do I need to grab these with git?
[18:06] <asac> https://wiki.ubuntu.com/MozillaTeam/Build/Bzr
[18:06] <asac> clearscreen: no with bzr
[18:06] <asac> ;)
[18:06] <asac> clearscreen: dont do step #2 OPTIONAL: initialize that directory as a bzr repository:
[18:07] <asac> and dont use midbrowser ;)
[18:07]  * asac thinks this should be updated for our firefox/xulrunner apps ;)
[18:08] <asac> that wiki page is real crap ;)
[18:08] <clearscreen> heh
[18:09] <asac> clearscreen: so just branch the branch ... change the changelog version to the latest that was build in daily
[18:09] <clearscreen> ah, I suppose I get it
[18:09] <asac> clearscreen: and run: bzr bd --merge --dont-purge --builder='debuild -b'
[18:09] <asac> thats all
[18:09] <clearscreen> how do I upgrade my local copy of the branch?
[18:09] <asac> it will automagically grab the orig.tar.gz and so on nowadays
[18:10] <asac> clearscreen: local copy?
[18:10] <asac> clearscreen: did you use bzr branch to get it?
[18:10] <asac> if so you just run bzr pull
[18:10] <asac> to get latest
[18:11] <clearscreen> Well basically what I meant is.. can I just bzr pull over the same branch when there's a new revision available
[18:11] <asac> clearscreen: what exactly do you mean by "new revision available" ?
[18:11] <asac> you only need to update the branch if there are new commits
[18:11] <asac> we only commit when we either change something in the packaging
[18:11] <clearscreen> Yeah, commit = revision++ :P
[18:11] <asac> _or_ if a patch or something failed
[18:12] <asac> clearscreen: yes. you just run bzr pull
[18:12] <clearscreen> ah ok
[18:12] <asac> that will update to latest
[18:12] <clearscreen> kk
[18:12] <clearscreen> what's head.genericbranding
[18:13] <clearscreen> I keep asking questions, I apologize :)
[18:13] <asac> welcome
[18:14] <asac> clearscreen: that was a topic branch i created to test something. that has been merged in the meantime
[18:14] <asac> clearscreen: i should have mark the branch accordingly
[18:14] <asac> e.g. its clutter that should not show up in the list
[18:14] <asac> doing that now
[18:14] <clearscreen> alright
[18:15] <asac> i shouldnt have pused it to ~mozillateam in the first place (rather ~asac)
[18:19] <clearscreen> alright, I got all head branches
[18:19] <clearscreen> some that were last-modified 50 weeks ago, but yeah :)
[18:20] <asac> hehe
[18:20] <asac> thats too much
[18:20] <asac> for now only the .head branches of what is in dailies makes much sense
[18:20] <asac> ;)
[18:20] <asac>  lp:~mozillateam/iceape/ubuntu-1.1.x   	  	 1  Development   	 2007-04-24 11:57:10 CEST
[18:20] <asac> 105 weeks ago
[18:20] <asac> ;)(
[18:20] <asac> 105 weeks
[18:21] <asac> fun
[18:21] <clearscreen> heh :D
[18:21] <clearscreen> By dailies you mean the PPAs on the launchpad page I suppose?
[18:22] <clearscreen> and maybe Im dumb, but I dont see firefox 3.5 / firefox 3.6 in this branch lsit
[18:22] <clearscreen> list*
[18:22] <asac> clearscreen: sorry for the confusion
[18:22] <asac> those branches have been reversioned upstream
[18:22] <asac> so its still 3.1/3.2 for us ;)
[18:24] <clearscreen> oh ok
[18:27] <clearscreen> also some that are in dailies have no head branches (FF3.1 and Prism on first glance), should I get the -dev branches?
[18:27] <asac> clearscreen: ffox 3.1 has a .head branch
[18:28] <asac> prism just has lp:~mozillateam/prism/prism
[18:28] <asac> the .dev is dead
[18:28] <asac> let me remove that
[18:29] <clearscreen> I must be blind but there's no firefox-3.1.head in that list
[18:29] <clearscreen> had to manually modify the url :)
[18:30] <clearscreen> got it now
[18:30] <asac> thats odd
[18:30] <asac> clearscreen: oh its lp:firefox on the page
[18:30] <asac> ;)
[18:30] <asac> tricky
[18:31] <clearscreen> ahw
[18:32] <asac> thats because someone marked that branch as the "main developmenet" series or something
[18:32] <asac> which makes not much sense imo
[18:32] <asac> but well
[18:32] <asac> doesnt reall hurt
[18:33] <clearscreen> i suppose
[18:38] <clearscreen> asac: bzr doesn't have a bd command
[18:38] <asac> install bzr-builddeb package
[18:49] <asac> clearscreen: so does it work ;)?
[18:49] <clearscreen> asac: yeah it's building 3.1 now
[18:50] <clearscreen> or 3.5, whatever
[18:50] <asac> clearscreen: good
[18:50] <asac> clearscreen: did you change the changelog version?
[18:50] <asac> clearscreen: or are you building unmodified?
[18:51] <asac> clearscreen: the idea is to change the changelog version to whatevert is currently in daily ppa
[18:51] <asac> clearscreen: simulating that you want to fix something that happens in current daily
[18:51] <clearscreen> So how exactly would I go about doing that
[18:52] <asac> clearscreen: just open debian/changelog. there are two cases
[18:52] <asac> either the topmost changelog entry is targetted for UNRELEASED or for jaunty
[18:52] <asac> (karmic, etc.)
[18:52] <asac> if its UNRELEASED you just change the upstream version in the first line
[18:53] <asac> e.g. replace 3.1~b4 with 3.4~b5~hg....
[18:53] <asac> if its jaunty or something it means that you need to create a new topmost changelog ... for that you do:
[18:53] <asac> dch -i
[18:53] <asac> and write something in the changelog
[18:53] <asac> and change the changelog version of topmost line like you would do for UNRELEASED
[18:54] <asac> clearscreen: so for testing assume its UNRELEASED (3.1 is currently jaunty, but that doesnt matter)
[18:54] <asac> change the first line to match whatever is in PPA
[18:54] <asac> ;)
[18:54] <asac> and try to build
[18:56] <clearscreen> bzr: ERROR: Unable to find the needed upstream tarball: firefox-3.5_3.5~b5~hg+nobinonly.orig.tar.gz.
[18:56] <clearscreen> heh
[18:57] <clearscreen> ahw .. it doesnt say UNRELEASED, nvm me
[19:00] <clearscreen> Am just confusing myself, time for a drink
[19:44] <asac> clearscreen: the version is not complete
[19:45] <asac> clearscreen: the hg... also has a date behind it
[19:45] <asac> be sure that you use exactly the same upstream version that was built in ppa
[21:39] <asac> hmm. seems like ftas bot uploaded, but somehow ppa rejected that
[21:40] <asac> lets see if it happens again tomorrow. for now lets assume launchpad ate them ;)
[21:46] <BUGabundo> eheh