[02:17] <gnomefreak> anyone stillhanging out?
[02:20] <gnomefreak> i see the java script is upstream errors :)
[02:47] <gnomefreak> btw i need testing done on both sunbird and lightning extensions please ignore the error when starting either, its upstream bug and im working with some of the people that are talking about it on the calendar dev list, waiting for a bug number from them
[02:48] <gnomefreak> asac: iceowl for lenny and sid or just one
[02:49] <gnomefreak> setting up shroots and was just wondering so i know what order to build them in
[16:04] <asac> ok doing plenty of NM tests ... going off for that
[17:04] <fta> [reed], is there a plan to unstick the "open new tab" button ? i find the new location really unnatural and annoying.. i want to be able to move it as before
[17:18] <asac> fta: i have a good idea for dquilt ;)
[17:18] <asac> the first dquilt push could also unpack embedded tarballs and then apply the first patch :)
[17:28] <fta> asac, hmmmmmmmm.... could work but what is your use case? using branches and bd --merge, i don't see how this could help
[17:30] <asac> fta: well. people can also prepare patches by apt-get source more easily
[17:30] <asac> fta: also its easier to tell someone:
[17:30] <asac> bzr bd --merge -e
[17:30] <asac> then go to the dir and use "dquilte" just like you would use quilt
[17:31] <asac> and remember to copy the new patches back to the bzr branch debian/patches directory
[17:31] <asac> also we could think about making bzr bd smart enough to create a link for debian/patches? or would that work?
[17:31] <asac> james_w: ^^
[17:31] <asac> ?
[17:32] <fta> i would like a bd switch doing -e + patch
[17:32] <asac> james_w: do you know why i suddenly have a bzr tray thing that doesnt really provide much features?
[17:32] <asac> my command line tool bzr just became a gui application :)
[17:33] <asac> fta: well yeah. dquilt could be used for that then and also for people working with apt-get source
[17:33] <james_w> asac: it's part of bzr-gtk
[17:34] <asac> james_w: how did that came to me? any idea?
[17:34] <asac> through a recommends?
[17:34] <asac> or was it always installed and just got a tray thing now?
[17:34] <james_w> asac: I uploaded a fix to the desktop file yesterdays so that it actually launches now
[17:34] <asac> ah
[17:34] <asac> :)
[17:35] <james_w> asac: and I don't know what you mean about creating a link for debian/patches
[17:35] <asac> james_w: what does it do? i only can select preferences with right mous but nothing with left
[17:35] <james_w> it hooks in to bzr-dbus and bzr-avahi to provide notifications of commits
[17:36] <asac> james_w: so it notifies me that i just commit something ;) ... sounds not really useful :-D
[17:36] <fta> asac, /usr/lib/firefox-3.0.3/defaults/preferences/firefox-branding.js is not the same file on i386 and amd64: http://paste.ubuntu.com/56044/
[17:36] <asac> james_w: anyway links:
[17:36] <asac> james_w: bzr bd --merge -e
[17:36] <asac> cd $builddir
[17:36] <asac> quilt push -a
[17:36] <asac> edit some/file
[17:37] <asac> quilt refresh
[17:37] <asac> now i have to manually take care that the patches get into the patches/ directory
[17:37] <asac> e.g.
[17:37] <asac> cp -r patches/* /path/to/bzr/tree/debian/patches
[17:37] <asac> the last step is quite cumbersome
[17:37] <asac> and i would like to get rid of it ;)
[17:37] <james_w> asac: as I said the other day "bzr bd-do" is intended to do exactly that
[17:38] <asac> james_w: ok. didnt understand it that way
[17:38] <james_w> saves you "cd $builddir" and "cp -r patches/*"
[17:38] <asac> james_w: cool if it does what it should do then it really is great
[17:38] <asac> fta: ^^ try that please ;) and then use the "new" dquilt :-P
[17:39] <james_w> I nicked it from svn-buildpackage
[17:39] <fta> asac, did you patch dquilt ?
[17:39] <asac> no :-P
[17:39] <james_w> one caveat is that you need to "bzr add" any new files (e.g. patches) afterwards
[17:39] <asac> fta: the new dquilt was a joke
[17:39] <fta> asac, ok
[17:40] <asac> james_w: afterwards?
[17:40] <asac> james_w: at best i would like to be able to just commit there as usual
[17:40] <asac> and then say exit 0
[17:40] <asac> -> then a bzr push happens
[17:40] <asac> or
[17:40] <asac> exit 1
[17:40] <asac> the changes done in the branch are discarded
[17:40] <james_w> that could work
[17:41] <james_w> it means the source you get during bd-do isn't the same one that is built, which might be a problem
[17:43] <asac> well. for some
[17:43] <asac> maybe
[17:43] <asac> bzr bd-do is usually ment for development
[17:43] <asac> and i dont think that a .bzr directory would cause issues for normal debuild -b
[17:44] <asac> otherwise bzr bd-do-dev ;)
[17:47] <james_w> :-)
[17:48] <james_w> the other alternative would be automatically adding, but I haven't thought it through completely, so I'm wary of doing that.
[17:50] <asac> james_w: personally i wouldnt like automatically adding
[17:50] <asac> james_w: actually i wouldnt like automatically copying all over when you exit
[17:51] <asac> james_w: now that i think about it, i think its a different command. bzr bd-do is similar to cdbs-edit-patch etc.
[17:51] <asac> while bzr bd-dev is just there to make a working/merged development tree ;)
[20:05] <fta> armin76, http://juliank.wordpress.com/2008/10/10/gentoo-destroying-earth/
[20:26] <fta> asac, mozilla bug 421977 => approval1.9.0.4 denied
[20:27] <asac> fta: fair enough
[20:28] <asac> fta: i think the policy gets "luckily" harder finally
[20:29] <fta> what a changelog! https://edge.launchpad.net/ubuntu/intrepid/+source/xserver-xorg-video-nouveau/1:0.0.10~git+20080706+b1f3169-1
[20:30] <fta> with automated ppa builds in it
[20:31] <fta> http://benjamin.smedbergs.us/blog/2008-10-09/release-branches-in-mozilla-central/
[22:34] <[reed]> fta: I requested blocking on it
[22:45] <fta> [reed], on what?
[22:45] <[reed]> new tab button
[22:45] <[reed]> making it movable
[22:47] <fta> bug id ?
[22:51] <fta> brb