/srv/irclogs.ubuntu.com/2009/05/01/#ubuntu-mozillateam.txt

clearscreenasac: 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?07:43
zirodayHi, is firefox intergration with notify-osd being worked upon and where?10:55
gnomefreakwhat app is used to shut down? hal?11:36
gnomefreakasac: have you been doing dailies by hand? or did fta get back?12:07
asacclearscreen: i dont think so. let me check12:24
asacgnomefreak: we fixed dailies12:24
gnomefreakasac: ah ok :)12:24
asacfta isnt needed as the uploads happen automatically12:24
clearscreenasac: also, when can we expect Fx3.5 showing up on testing repository? :)12:25
asacclearscreen: what is "testing" repository?12:25
asacclearscreen: maybe check if you can subscribe to PPA of https://edge.launchpad.net/~ubuntu-mozilla-daily12:25
clearscreenWell I used to run Debian, but I was refering to karmic on ubuntu12:26
asacclearscreen: karmic already has ffox 3.512:26
clearscreenasac: I wasn't aware of that :)12:26
asacalso jaunty has12:26
asacjaunty has some pre b4 snapshot (will be updated to b4 soon)12:27
asackarmic has b412:27
clearscreenI see12:27
clearscreenasac: 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
asacclearscreen: 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 UTC12:29
asacclearscreen: thats when builds should have finished12:29
clearscreenOther than security fixes obviously12:29
asacclearscreen: 3.0 is security only12:29
asac3.5 is active development. we provide the packages as previews12:30
asacbut12:30
asacwe also made the step and allow you to install both in parallel12:30
asacand so on12:30
asacfor us its firefox-3.0 and firefox-3.512:30
asacand not firefox12:30
asac(package name)12:30
asacdebian doesnt do that12:30
asacwe also have firefox-3.6 ;)12:30
asacwhich is trunk12:30
sebnertrunk is always good12:31
clearscreenaha.12:31
sebner^^12:31
asacyeah. the dailies definitly rock12:31
clearscreenAlso, is Fx3.5 called shiretoko because of the stuff that went on with mozilla <-> debian?12:32
asacto some degree yes12:32
asacwe could call it firefox, if its a milestone release12:32
asacbut not for snapshots12:32
asacso we dont bother12:32
clearscreenAlright12:32
clearscreenI'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
asacclearscreen: so the answer is: we dont want to bother with trademark stuff for anything except the default browser :)12:36
asacwhich is ffox 3 atm12:36
asacclearscreen: yeah12:37
asacclearscreen: its a bit hard to just jump into mozilla code base12:37
asacsame for other big things12:37
* gnomefreak working on seamonkey12:37
gnomefreakbe back in a bit i have hardy and intrepid building12:37
clearscreenAnd 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 :D12:38
asacclearscreen: i would think that going for C is better as those code bases in the linux stacks are usually much cleaner ;)12:38
asacclearscreen: well. the suboptimal code argument doesnt count much12:38
asacclearscreen: of course you need some basic skills12:38
asacbut then you need to produce code and get it reviewed by senior developers to get the final tuning of your skills12:39
clearscreenSorry got to break up this conversation, need to go to work :( some PHP job, *sigh*12:39
clearscreenbb12:39
asachehe12:39
asacenjoy12:39
asactoday is public holiday12:39
asacso i might not be available all the time12:39
asacgoing out to sun soon12:40
gnomefreakat least you have sun, it looks like rain here12:55
GregW3056Hi i'm having some trouble with firefox13:30
GregW3056would anyone be able to help me out?13:31
asacbe patient folks ;)13:37
* gnomefreak not really here but "having trouble with firefox" is a bit too general :(13:45
asacheh14:00
asac_reconnect while scp'ing a huge file ... bad14:19
gnomefreakthis is taking forever14:29
asac_sm?14:30
asac_what are you doing? does it fail again?14:30
gnomefreaksm2 builds for karmic jaunty intrepid hardy14:31
gnomefreakasac_: 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 fun14:32
asac_?14:32
gnomefreakasac_: no im updating my PPA14:32
asac_k14:33
=== asac_ is now known as asac
gnomefreakmozilla bug 48505214:34
ubottuMozilla bug 485052 in Security: PSM "Embed a list of default OCSP Responder URLs for certain CAs" [Normal,Resolved: fixed] http://bugzilla.mozilla.org/show_bug.cgi?id=48505214:34
gnomefreakah ok ive seen that one already14:35
gnomefreakdown to last build :)14:38
gnomefreakand last one is uploaded waiting for PPA to start on it :)14:47
BUGabundogood afternoon14:54
BUGabundohi gnomefreak14:54
BUGabundowhat's up with fta?14:54
gnomefreakhi BUGabundo14:54
gnomefreakBUGabundo: he took a few weeks off i thought14:54
BUGabundoah ok14:55
gnomefreak!info flight-of-the-amazon-queen14:55
ubottuflight-of-the-amazon-queen (source: flight-of-the-amazon-queen): a fantasy adventure game. In component universe, is optional. Version 1.0.0-5ubuntu2 (jaunty), package size 35682 kB, installed size 53028 kB14:55
BUGabundonot seen him a while14:55
BUGabundowhat a longgggg name14:55
gnomefreakthats why i wanted to see what it was :)14:55
BUGabundognomefreak: apt-cache not good enough?14:58
gnomefreaktoo hard i have 5 terminals open15:00
gnomefreakasac: we will not build with PGO unless upstream provides builds for it right?15:07
gnomefreakok branhes and packages are done now updates15:45
gnomefreak!info firefox hardy15:56
ubottufirefox (source: firefox-3.0): meta package for the popular mozilla web browser. In component main, is optional. Version 3.0.10+nobinonly-0ubuntu0.8.04.1 (hardy), package size 64 kB, installed size 120 kB15:56
gnomefreakfinally my bug is fixed15:59
clearscreenasac: I have no clue why, but firefox built in like 5-10 min instead of the 30-40 of yesterday17:44
asacclearscreen: firefox is tiny ... xulrunner takes long17:45
asacfirefox builds in 2-5 minutes usually17:45
clearscreenasac: oh. right, stupid me.. didnt realize I didnt build firefox yesterday17:45
clearscreenasac: I applied to the group @ launchpad, although I'm not entirely sure what I should do when the build breaks17:46
clearscreenand does karmic come with daily? or do I have to pull it from somewhere else17:47
asacclearscreen: karmic needs to be setup. however, the guy driving the bot is a bit away ;)17:47
asacclearscreen: so for now there are no karmic dailies17:47
asacclearscreen: i dont think joining the team would be right when you get started17:48
clearscreenThat's fine, I just though that was part of the procedure17:48
asacclearscreen: i think the right way is that the daily team gets its build mail sent to mailing list17:50
asacthat team is more a bot team without real members17:50
clearscreenwhere 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
asacclearscreen: we currently only build the branches that you see there17:52
asacclearscreen: we dont have a mailing list setup yet ;)17:53
asaci have to check something17:53
asacclearscreen: ok i applied for maling list17:54
clearscreenSorry for all the questions, but will I need deb (for build-dep libs) or would deb-src suffice?17:54
asacbuild-dep you need both17:55
clearscreenok17:55
asacclearscreen: remember me to write something about our dailies to the wiki or something17:56
asaci will see if i can do that soonihs17:56
clearscreenOk17:56
clearscreenAnother 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-dev17:59
clearscreenI can manually remove those with deborphan whenever I feel like it17:59
asacclearscreen: you cannot have multiple versions of -dev at the same time for xulrunner18:00
asacthe reason is that we share the same .pc filenames so they conflict18:00
clearscreenheh, k18:00
asacthis gives us the ability to respin xulrunner depends by just flipping build-depends18:00
asacand see where they break18:00
asacotherwise you would always need to patch any app that uses xulrunner-dev18:01
asacwhich is cumbersome and sometimes non-trivial18:01
asac(configure systems have grown to bad beasts for lots of gecko clients :))18:01
clearscreenhttp://paste.ubuntu.com/162359/ < my uber leet build script18:02
asacclearscreen: so if you want to build against xulrunner 1.9.2 you cannot have the 1.9 dev at the same time18:02
clearscreenasac: aha ok18:02
asacclearscreen: well. actually thats not the preferred way of building our packages18:02
asac(for development)18:03
clearscreenasac: I'm open for suggestions, heh18:03
asacso what you need are the packaging branches18:03
asaccreate a directory: mt-bzr (mozillateam bzr) or something18:03
asacand branch18:03
asacthe .head branches for the respective packages18:03
asacyou can find them here:18:03
asachttps://code.edge.launchpad.net/~mozillateam/18:04
asacthere are quite a few. just look for those with .head at the end18:04
asaclike xulrunner-1.9.2.head18:04
asachttps://code.edge.launchpad.net/~mozillateam/xulrunner/xulrunner-1.9.2.head18:04
asacso you just branch them to the directory18:04
asacand when a daily fails you change the debian/changelog version to just match the one that failed18:05
asac(well not the ~umd.. suffix)18:05
asacand use bzr-builddeb to build it18:05
clearscreenstupid question again, do I need to grab these with git?18:06
asachttps://wiki.ubuntu.com/MozillaTeam/Build/Bzr18:06
asacclearscreen: no with bzr18:06
asac;)18:06
asacclearscreen: dont do step #2 OPTIONAL: initialize that directory as a bzr repository:18:06
asacand dont use midbrowser ;)18:07
* asac thinks this should be updated for our firefox/xulrunner apps ;)18:07
asacthat wiki page is real crap ;)18:08
clearscreenheh18:08
asacclearscreen: so just branch the branch ... change the changelog version to the latest that was build in daily18:09
clearscreenah, I suppose I get it18:09
asacclearscreen: and run: bzr bd --merge --dont-purge --builder='debuild -b'18:09
asacthats all18:09
clearscreenhow do I upgrade my local copy of the branch?18:09
asacit will automagically grab the orig.tar.gz and so on nowadays18:09
asacclearscreen: local copy?18:10
asacclearscreen: did you use bzr branch to get it?18:10
asacif so you just run bzr pull18:10
asacto get latest18:10
clearscreenWell basically what I meant is.. can I just bzr pull over the same branch when there's a new revision available18:11
asacclearscreen: what exactly do you mean by "new revision available" ?18:11
asacyou only need to update the branch if there are new commits18:11
asacwe only commit when we either change something in the packaging18:11
clearscreenYeah, commit = revision++ :P18:11
asac_or_ if a patch or something failed18:11
asacclearscreen: yes. you just run bzr pull18:12
clearscreenah ok18:12
asacthat will update to latest18:12
clearscreenkk18:12
clearscreenwhat's head.genericbranding18:12
clearscreenI keep asking questions, I apologize :)18:13
asacwelcome18:13
asacclearscreen: that was a topic branch i created to test something. that has been merged in the meantime18:14
asacclearscreen: i should have mark the branch accordingly18:14
asace.g. its clutter that should not show up in the list18:14
asacdoing that now18:14
clearscreenalright18:14
asaci shouldnt have pused it to ~mozillateam in the first place (rather ~asac)18:15
clearscreenalright, I got all head branches18:19
clearscreensome that were last-modified 50 weeks ago, but yeah :)18:19
asachehe18:20
asacthats too much18:20
asacfor now only the .head branches of what is in dailies makes much sense18:20
asac;)18:20
asac lp:~mozillateam/iceape/ubuntu-1.1.x      1  Development    2007-04-24 11:57:10 CEST18:20
asac105 weeks ago18:20
asac;)(18:20
asac105 weeks18:20
asacfun18:21
clearscreenheh :D18:21
clearscreenBy dailies you mean the PPAs on the launchpad page I suppose?18:21
clearscreenand maybe Im dumb, but I dont see firefox 3.5 / firefox 3.6 in this branch lsit18:22
clearscreenlist*18:22
asacclearscreen: sorry for the confusion18:22
asacthose branches have been reversioned upstream18:22
asacso its still 3.1/3.2 for us ;)18:22
clearscreenoh ok18:24
clearscreenalso some that are in dailies have no head branches (FF3.1 and Prism on first glance), should I get the -dev branches?18:27
asacclearscreen: ffox 3.1 has a .head branch18:27
asacprism just has lp:~mozillateam/prism/prism18:28
asacthe .dev is dead18:28
asaclet me remove that18:28
clearscreenI must be blind but there's no firefox-3.1.head in that list18:29
clearscreenhad to manually modify the url :)18:29
clearscreengot it now18:30
asacthats odd18:30
asacclearscreen: oh its lp:firefox on the page18:30
asac;)18:30
asactricky18:30
clearscreenahw18:31
asacthats because someone marked that branch as the "main developmenet" series or something18:32
asacwhich makes not much sense imo18:32
asacbut well18:32
asacdoesnt reall hurt18:32
clearscreeni suppose18:33
clearscreenasac: bzr doesn't have a bd command18:38
asacinstall bzr-builddeb package18:38
asacclearscreen: so does it work ;)?18:49
clearscreenasac: yeah it's building 3.1 now18:49
clearscreenor 3.5, whatever18:50
asacclearscreen: good18:50
asacclearscreen: did you change the changelog version?18:50
asacclearscreen: or are you building unmodified?18:50
asacclearscreen: the idea is to change the changelog version to whatevert is currently in daily ppa18:51
asacclearscreen: simulating that you want to fix something that happens in current daily18:51
clearscreenSo how exactly would I go about doing that18:51
asacclearscreen: just open debian/changelog. there are two cases18:52
asaceither the topmost changelog entry is targetted for UNRELEASED or for jaunty18:52
asac(karmic, etc.)18:52
asacif its UNRELEASED you just change the upstream version in the first line18:52
asace.g. replace 3.1~b4 with 3.4~b5~hg....18:53
asacif its jaunty or something it means that you need to create a new topmost changelog ... for that you do:18:53
asacdch -i18:53
asacand write something in the changelog18:53
asacand change the changelog version of topmost line like you would do for UNRELEASED18:53
asacclearscreen: so for testing assume its UNRELEASED (3.1 is currently jaunty, but that doesnt matter)18:54
asacchange the first line to match whatever is in PPA18:54
asac;)18:54
asacand try to build18:54
clearscreenbzr: ERROR: Unable to find the needed upstream tarball: firefox-3.5_3.5~b5~hg+nobinonly.orig.tar.gz.18:56
clearscreenheh18:56
clearscreenahw .. it doesnt say UNRELEASED, nvm me18:57
clearscreenAm just confusing myself, time for a drink19:00
asacclearscreen: the version is not complete19:44
asacclearscreen: the hg... also has a date behind it19:45
asacbe sure that you use exactly the same upstream version that was built in ppa19:45
asachmm. seems like ftas bot uploaded, but somehow ppa rejected that21:39
asaclets see if it happens again tomorrow. for now lets assume launchpad ate them ;)21:40
BUGabundoeheh21:46

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