[00:00] <lifeless> dvheumen: subclassing is a very big hammer
[00:00]  * lifeless really has to duck out; I'll be back
[00:00] <dvheumen> lifeless, but otherwise I'm probably implementing almost the same code three times
[00:00] <dvheumen> (i think)
[00:01] <dvheumen> also, is it "a very big hammer" in python, or in object oriented languages in general?
[00:02] <bob2> general
[00:03] <jelmer> dvheumen: I think Rob also means that changing that now will be a fairly big change with a lot of consequences
[00:04] <dvheumen> even though most classes derive from 'object'?
[00:04] <dvheumen> sorry guys, but I'm trying to form a picture here of what the complications are
[00:04] <bob2> they derive from object for hysterical raisins
[00:05] <bob2> it's for backwards compatibility in python 2.x - deriving from object gives you a 'new style' class, which adds some features, but is subtly incompatible with old-style ones
[00:06] <dvheumen> okay, I'll read up on that
[00:06] <bob2> well, you don't have to, you can just always inherit from object if not inheriting from anything else (for bzr, at least:)
[00:07] <dvheumen> bob2, true, but I like some background info, helps with the thinking :P
[00:07] <bob2> google descrintro for the whole shabang
[00:09] <dvheumen> k, tnx
[00:11] <dvheumen> aha ... I see some other complications with my idea ... okay, back to the drawing board :P
[00:15] <poolie> actually i do think having a common Component class is a good idea
[00:15] <poolie> but we should be very careful what goes in it
[00:15] <poolie> at least saying "there is a common interface" is a good idea
[00:16] <dvheumen> hey, don't steal my idea now ;)
[00:17] <dvheumen> any candidates that you want to put in there?
[00:19] <spiv> .bzrdir is probably the most obvious common attribute.
[00:20] <dvheumen> ah right :P
[00:21] <lifeless> back
[00:21] <lifeless> caffeined up
[00:22] <spiv> Possibly the logic for opening them (so reading .bzr/$component/format files and finding the right implementation from a registry) and initializing them.  But even then some of that is just common to bzr native components, not foreign ones (e.g. SvnRepository)...
[00:22] <lifeless> dvheumen: the code in question is something like lock. 'invoke_lock_callback(self)' though
[00:23] <dvheumen> lifeless, yeah, I know
[00:23] <dvheumen> it's much easier than I was previously thinking
[00:23] <lifeless> note that many external formats *don't have* components
[00:23] <lifeless> in fact our older formats aren't split into neat little orthogonal elements
[00:24] <lifeless> so while  I like the idea of a Component for things that are Components, Branch per se isn't a Component, IMO
[00:24] <lifeless> BzrBranch4+ could be
[00:26] <dvheumen> lifeless, I'm gonna try something in the coming days and then I'll get back to you
[00:26] <lifeless> cool
[00:27] <dvheumen> bye
[00:27] <poolie> oops
[00:48] <jelmer> igc: hi!
[00:48] <igc> hi jelmer!
[00:48] <lifeless> poolie: oops?
[00:48] <jelmer> igc: lp:bzr-website is pack-0.92 at the moment, is there any reason it's not upgraded yet?
[00:49]  * maxb has just finished using bzr-rewrite to rebase a branch based on a bzr-hg import of a hgsubversion import of a svn branch onto a bzr-svn import of the svn branch. How's that for a brainteaser :-)
[00:49] <igc> jelmer: nope. Feel free to upgrade it :-)
[00:49] <jelmer> maxb: :-))
[00:49] <jelmer> igc: Ok, thanks!
[00:52] <wgrant> I can't 'bzr pump' with bzr 2.1.0 and pipeline 2.1 r157 (the latest on the 2.1 branch).
[00:52] <wgrant> bzr: ERROR: exceptions.AttributeError: 'RevisionTree' object has no attribute 'branch'
[00:53] <lifeless> wgrant: -Derror please
[00:58] <wgrant> lifeless: http://paste.ubuntu.com/392911/
[01:02] <lifeless> ugh, soo many spans
[01:02]  * lifeless tries without wget
[01:04] <lifeless> wgrant: ok, its a bug in the new merge hook facility
[01:04] <lifeless> wgrant: and you have a merge hook enabled for your branch - possibly builddeb
[01:04] <wgrant> lifeless: You can also add '/plain'
[01:04] <wgrant> lifeless: Ahh.
[01:04] <lifeless> please file a bug, its something we'll need to do a 2.1.1 for
[01:05] <wgrant> lifeless: Summary?
[01:05] <jelmer> igc: done
[01:06] <igc> jelmer: thank-you!
[01:07] <lifeless> ConfigurableFileMerger does not support merging with this_tree a revision tree
[01:07] <lifeless> or something
[01:07] <lifeless> include the backtrace of course
[01:07] <wgrant> right.
[01:09] <wgrant> lifeless: Bug #537041
[01:10] <lifeless> also please include the output of bzr hooks for the merge_file_content point
[01:11] <wgrant> lifeless: Just NEWS, but it's on the bug now.
[01:11] <lifeless> thanks
[01:11] <lifeless> if you wanted to patch it
[01:12] <wgrant> I would, if it's simple.
[01:14] <lifeless> minimall would be to guard the attribute access, and if it fails, try for a global config instead
[01:14] <lifeless> better still would be a test showing that that works.
[01:27] <thumper> poolie: ping
[01:27] <thumper> lifeless: hi
[01:27] <lifeless> hi
[01:28] <thumper> I bumped into a friend I hadn't seen for ages
[01:28] <thumper> he manages a programming team now
[01:28] <lifeless> cool
[01:28] <thumper> I asked about what they use for version control
[01:28] <thumper> he said CVS and Subversion
[01:28] <thumper> but they are looking at DVCSs
[01:28] <thumper> I asked if he'd like me to come in and give a talk
[01:28] <thumper> he was very enthusiastic
[01:29] <thumper> so I have something next Tuesday at 10:30 am
[01:29] <thumper> would love some help with a talk outline
[01:29] <thumper> I'm sure there'll be questions about git as they are looking around now
[01:29] <lifeless> sure
[01:29] <thumper> so I'd like some bullets
[01:29] <lifeless> uhm
[01:29] <thumper> :)
[01:29] <lifeless> what language do they use
[01:29] <lifeless> what ide if any
[01:29] <thumper> bzr-explorer will be a good one
[01:29] <thumper> perl
[01:29] <lifeless> what platform
[01:30] <spiv> thumper: bullets?  Don't shoot potential users! :)
[01:30] <thumper> all he asked was "does it work on mac os"?
[01:30] <lifeless> ok, cool
[01:30] <thumper> lifeless: heard of AD instruments?
[01:30] <lifeless> yeah
[01:30] <thumper> data capture
[01:30] <thumper> analytics
[01:30] <lifeless> I suspect I know your friend :)
[01:30] <thumper> john
[01:31] <lifeless> mmm, no. But I definitely know *someone* there. I think.
[01:31] <lifeless> anyhow, thats not important
[01:31] <lifeless> key points are going to be -
[01:31] <lifeless> we build and test macos X
[01:31] <lifeless> explorer
[01:31] <lifeless> python for extensability
[01:32]  * thumper nods
[01:34] <lifeless> single site?
[01:35] <thumper> at this stage as far as I'm aware
[01:35] <thumper> they want good merging :)
[01:35] <lifeless> so, you can talk about ease of migration
[01:35] <lifeless> stay with the same workflow, ease into distribution
[01:35] <lifeless> merging is great
[01:36] <lifeless> very very hookable in 2.1
[01:36]  * thumper nods some more
[02:09]  * igc lunch
[02:24] <parthm> hello. regarding bzr-grep bug #536688 i wanted to check if anyone had any opinions. i am ok with either options.
[02:24] <parthm> --recurse is closer to POSIX grep while recurse by default is similar to hg and git.
[02:29] <lifeless> I'd recurse by default
[02:29] <lifeless> ls doesn't, but it used to, and I think we made a mistake making it not do it by default
[02:30] <spiv> I agree, recurse by default.
[02:31] <fullermd> I always run ls twice since it stopped recursing.
[02:31] <spiv> Plain old grep doesn't have the advantage of knowing 'these files are all part of the one project', but bzr does.
[02:31] <parthm> fullermd: :-)
[02:33] <parthm> sounds fine to me. i will go with recurse as default and add a --no-recurse option.
[02:33] <parthm> there is already a --from-root.
[02:34] <parthm> if we go with recursive grep and user sets 'grep=grep --no-recurse' as an alias, how can (s)he override it from command line.
[02:35] <parthm> do we need an explicit --recurse option or does the option processing framework do some magic?
[02:37] <lifeless> parthm: our option stuff automatically does --recurse if you have --no-recurse, I think.
[02:38] <parthm> lifeless: that sounds fantastic. i will go ahead with the --no-recurse.
[02:38] <parthm> thanks everyone for your inputs.
[04:17] <poolie> hi spiv, are you around?
[04:17] <poolie> how are things?
[04:19] <spiv> Yeah, I'm around.
[04:20] <spiv> Things are going pretty well.  It's amazing how much easier it is to cope with the email load working 3 days a week rather than 2 :)
[04:22] <spiv> I'm catching up on in-progress work that had started to accumulate.  Oh, and I'm glad I'm subscribed to the 'answers' for bzr, it's much more active than I had realised.
[04:42] <poolie> yes it is
[04:42] <poolie> i thought you were all just slack for not answering them ;-)
[04:42] <poolie> i just put up an mp to plot that too
[07:17] <vila> hi all !
[07:21] <fullermd> Oh, vila's around.  Must be bedtime.
[07:21] <vila>  :)
[08:40] <codygman> is there an option to exclude certain filetypes in bazaar?
[08:40] <codygman> when adding
[08:40] <codygman> wait..  im just now seeing ingore list
[08:44] <codygman> wow.. bzr remove actually deletes files doesnt it?
[08:46] <bob2> yes
[08:46] <bob2> unless you ask it not to
[08:47] <codygman> rofl i freaked for a second
[08:47] <codygman> then found revert
[08:47] <codygman> and thanks.. i was just trying to get it to stop VC'ing some files
[08:48] <codygman> so could i just use the --keep flag to do that?
[08:48] <codygman> bzr remove ./lib --keep
[08:48] <lifeless> yes
[08:49] <codygman> thanks lifeless
[08:58] <lifeless> vila: hey
[08:58] <lifeless> vila: I put it to you that 'Conflict: can't delete lptools because it is not empty.  Not deleting.' is the largest cause of merge conflicts.
[08:58] <lifeless> vila: and there is a bug about it, suggesting a lost+found approach, amongst other things.
[08:58]  * vila nods
[08:58] <lifeless> vila: if you were to fix this, I would be extremely excited.
[08:59] <vila> It's definitely on the radar
[08:59]  * lifeless bounces, gently.
[08:59] <vila> A pretty big spot even
[08:59]  * lifeless bounces faster.
[09:00] <vila> I realized yesterday that 'bzr clean-tree' is kind of a workaround in some cases in the mean time
[09:01] <lifeless> by the time you know you need it ..
[09:01] <vila> sure, workaround is an optimistic way to talk of the problem :]
[09:01] <vila> s/of/about/
[09:02]  * lifeless wafts activation energy at vila
[09:03]  * vila receives that gratefully
[10:00] <quicksilver> vila: where is the canonical place to download DVC these days?
[10:01] <vila> quicksilver: I'm not of any change there (I didn't upgrade it for a while though), let me checl
[10:01] <quicksilver> there was some confusion about which repo to use last time I checked
[10:01] <quicksilver> which was a while ago, I admit
[10:02] <vila> http://bzr.xsteve.at/dvc/
[10:02] <vila> I currently miss 48 revisions 8-}
[10:02] <quicksilver> Forbidden
[10:02] <quicksilver> You don't have permission to access /dvc/ on this server.
[10:05] <vila> quicksilver: huh ? Where did you get that ? I just pull -v
[10:05] <quicksilver> oh, OK.
[10:05] <quicksilver> and you run straight out of the repo?
[10:05] <quicksilver> or you copy the elisp files somewhere?
[10:06] <vila> quicksilver: I run from the repo but I have a ++build there where I run make
[10:06] <vila> quicksilver: I set that up so long ago I'm not even sure I still use it though
[10:06] <quicksilver> :)
[10:06] <vila> let me check another install
[10:06] <quicksilver> ah well I better find a machine I have bzr on. I'm stuck on a temporary windows box :(
[10:07] <vila> quicksilver: ouch
[10:07] <vila> windows is the only OS I've yet to address in my versioned setups...
[10:08] <quicksilver> mostly I just run emacs and putty and firefox and ignore the rest of the system
[10:08] <quicksilver> I dont' try to program on it (I do that via ssh and a linux box)
[10:08] <vila> I use the stock emacs there without any customization which has... some surprising results when confronted with my muscle memories :)
[10:09] <quicksilver> hmm I don't know if I will want to do this after all
[10:09] <vila> firefox on windows ?? Wow, I don't even make my windows VMs visible on the internet :)
[10:09] <quicksilver> I just remembered that vc-bzr is really really painful over plink
[10:09] <quicksilver> I imagine dvc will be as bad.
[10:10] <vila> branch locally :)
[10:10] <quicksilver> well new hard disk arriving today. Hopefully won't be long now.
[10:11] <vila> quicksilver: not running make in ++build seems to work (as in no messages under emacs), but that doesn't mean it used the right versions either...
[10:12] <vila> quicksilver: anyway, I think to remember you need to compile dvc before using it which require auto<something> and getting that on windows...
[10:15] <vila> quicksilver: I *had* some instructions about installing/setting up dvc, but I can't find them anymore :-/
[10:16] <vila> . o O (Well done for versioning all that setup stuff, well done really :-( )
[10:17] <vila> hmm, may be it's because the dvc INSTALL file seems to cover it (including using ++build which is a rather unusual dir name for me)
[10:18] <vila> quicksilver: so basically: autoconf; cd dvc; mkdir ++build; cd ++build; ./configure ; make
[10:18] <vila> quicksilver: see the INSTALL file in short :)
[10:20] <vila> ha, found these notes back, yeah, they are obsolete, I now use instructions from the dvc INSTALL file
[10:20] <vila> :)
[10:38] <quicksilver> :)
[10:53] <Keybuk> bzr diff --using meld seems to be broken
[10:53] <Keybuk> the diff still ends out mostly on stdout :(
[10:59] <spiv> Keybuk: works ok for me, just the "[11:01] <spiv> (even with --no-plugins, --using is a builtin feature these days)
[11:02] <Keybuk> spiv: I get the diff
[11:02] <Keybuk> in fact, I get some diffs
[11:02] <Keybuk> then sometimes meld pops up with the diff of just *one file*
[11:02] <Keybuk> you close it, you get more diff on stdout
[11:03] <Keybuk> interesting
[11:03] <Keybuk> the diff is for added files
[11:03] <Keybuk> (on stdout)
[11:06] <spiv> Huh!
[11:06] <spiv> That sounds like a silly bug.
[11:07] <spiv> It is annoying that it only pops up meld for one file at a time.
[11:08] <spiv> It's rapidly approaching my bedtime, so please file a bug report.
[12:05] <cbx> Hey, I'm a newbie to version controls, and was wondering if all the code ends up in the trunk folder ?
[12:05] <cbx> I have a live website I'm running, and would like to use that as the main branch. I can access that by FTP
[12:39] <amitk> Hi all, What are the bzr commands to reorder a set of bzr commits while making some modifications to each commit (after a review cycle)
[12:42] <beuno> amitk, bzr-rewrite
[12:42] <beuno> it's a plugin
[12:44] <amitk> beuno: hmm, apparently not in karmic
[12:44] <xeviox2> what is stored in the "indices" folder of an repository?
[12:45] <xeviox> s/an/a
[12:49] <beuno> amitk, http://wiki.bazaar.canonical.com/BzrPlugins
[12:49] <jelmer> amitk: it's still named bzr-rebase in karmic
[12:49] <xeviox> does bzr use one .pack file for each file in the repository?
[12:55] <beuno> xeviox, no, packs combine many revisions
[12:55] <amitk> jelmer: rebase doesn't seem to do what I want. I don't want to rebase revisions r4..410 to another branch. I want to be able to export r4..r10 separately, fix the problems in each commit and reapply to a new branch. Does that make sense in bzr?
[12:55] <jelmer> amitk: Hmm
[12:55] <jelmer> amitk: Perhaps fastexport does what you need?
[12:56] <amitk> jelmer: not from it's help
[12:56] <xeviox> beuno: ok thanks, as far as I understand there are records stored in the .pack files and each record is compressed using zlib, correct?
[12:57] <beuno> xeviox, yes
[12:59] <xeviox> beuno: ok, looking at the records it seems that a blank line is used as a separator between the records. Each record has 3 lines as header. The first is a string showing the compress lib (e. g. gcb1z for zlib), the 2nd and 3rd are numbers, what are they for?
[12:59] <jelmer> amitk: is there a particular reason you would like to modify the existing revisions rather than just fix the branch itself?
[12:59] <beuno> xeviox, I don't know that much detail
[12:59] <beuno> lifeless does, not sure if he's still around
[13:00] <xeviox> beuno: thanks for the help :D
[13:00] <xeviox> lifeless: ping
[13:00] <beuno> xeviox, http://doc.bazaar.canonical.com/latest/developers/packrepo.html
[13:01] <amitk> jelmer: I don't want all the the mistakes I make to go out in the final set of commits that I ask to be merged
[13:01] <xeviox> beuno: thanks :D
[13:02] <amitk> jelmer: I wonder if my workflow is unsuited for bzr
[13:13] <xeviox> k, I'll come back later, thanks for the help :D
[13:17] <jelmer> bob2: have you seen http://lists.alioth.debian.org/pipermail/pkg-bazaar-maint/2010-March/002925.html ?
[13:22] <Stavros> hi
[13:22] <Stavros> does anyone know where plugins are installed by default in ubuntu?
[13:24] <Stavros> there's a bzr-notify running
[13:24] <jelmer> Stavros: usually /usr/share/pyshared/bzrlib/plugins/*
[13:24] <Stavros> ah, thanks
[13:25] <Stavros> hmm, anyone know why bzr-notify would be running? i don't have that plugin as such
[13:26] <jelmer> bzr-notify is not a plugin, it's a separate app
[13:26] <jelmer> it lives in /usr/bin/bzr-notify
[13:26] <Stavros> oh
[13:26] <maxb> Stavros: It is a daemonm, and is started by /etc/xdg/autostart/bzr-notify.desktop
[13:27] <Stavros> i don't see it in the packages i installed, how can i remove it?
[13:27] <jelmer> Stavros: it's part of bzr-gtk
[13:27] <Stavros> ah, thanks
[13:29] <Stavros> jelmer: i removed that and it's gone, thanks
[15:26] <JamieBennett> I'm having problems with a "bzr branch" complaining about a publickey permission problem and I can't see what it is (most likely a simple user error). Is there any way to get a debug log message of what is happening?
[15:29] <Breaking_Pitt> what means this? I can't find any info -> bzr --no-plugins
[15:35] <jelmer> JamieBennett: Hi; Usually it's easiest to see if you can use sftp to the same host
[15:35] <jelmer> Breaking_Pitt: I'm not sure I understand your question?
[15:36] <JamieBennett> jelmer: what can I do to test this? I thought it was a key issue but looking at my launchpad page and doing a gpg --list-keys it seems I have the right key on this system
[15:37] <jelmer> JamieBennett: try connecting to launchpad using 'sftp -vv bazaar.launchpad.net'
[15:38] <loxs> is there some tool that can show statistics on who committed what portion of the code?
[15:40] <jelmer> loxs: you can use "bzr annotate" (or "bzr qannotate") to see who was responsible for what lines of the code in a particular file
[15:40] <loxs> jelmer, yeah, I know that, but this doesn't solve my problem :)
[15:40] <jelmer> loxs: "bzr stats" (from the bzr-stats plugin) will print a list of how many commits every committer has made
[15:40] <JamieBennett> jelmer: seems its trying to log me in as jamie rather than jamiebennett, mmm
[15:41] <jelmer> JamieBennett: ah, sorry - you might need "sftp -vv jamiebennette@bazaar.launchpad.net" in that case - bazaar knows your username but sftp doesn't
[15:41] <loxs> hmm, thanks I'll check bzr-stats
[15:42] <SamB_XP> probably can fix that with something in .ssh ?
[15:45] <sjamaan> Hi
[15:45] <JamieBennett> jelmer: http://pastebin.ubuntu.com/393336/
[15:46] <jelmer> JamieBennett: is any of the ssh keys reported by 'ssh-add -l' listed on your lp page?
[15:53] <Breaking_Pitt> i don't know what means the flag --no-plugins
[15:56] <jelmer> Breaking_Pitt: See "bzr help global-options"
[15:56] <jelmer> Breaking_Pitt: basically it prevents Bazaar from loading any of the plugins (see "bzr plugins" for a list of available plugins)
[15:57] <Breaking_Pitt> ok jelmer
[15:57] <Breaking_Pitt> tthanks
[16:00] <jelmer> Breaking_Pitt: yw
[16:11] <JFo> jpds, that --show-diff has really come in handy lately, thanks for recommending it.
[16:12] <jpds> JFo: No problem.
[18:10] <jelmer> maxb: hi
[18:19]  * kfogel is away: switching consoles for a bit, back soon
[20:32] <speakman> morning folks
[20:33] <jelmer> hi speakman
[20:33] <speakman> I don't really get the "loom" thing. And I'm not really sure what's the difference between a SCM and Quilt either. Any tip of documents to read about it?
[20:35] <speakman> (actually I'm a little confused about what's a proper workflow in bzr using launchpad and a random bunch of people in a very-early stage in a new project)
[20:39] <jelmer> speakman: a VCS records history - quilt or loom allows you to work with inter-dependent changesets that can be modified
[20:41] <speakman> jelmer: but how does that differ from branching?
[20:41] <jelmer> speakman: revisions don't change, quilt patches do
[20:42] <lifeless> beuno: ?
[20:48] <speakman> oh... but... patches becomes revisions..?
[20:48] <jelmer> I think I might not be the best person to explain this.
[20:48] <jelmer> sorry :-/
[20:51] <lifeless> speakman: you're using launchpad and bzr?
[20:53] <speakman> jelmer: it's ok :-D
[20:53] <speakman> lifeless: yes we do
[20:54] <lifeless> speakman: great. So, do whateever you like with bzr: it tries to keep out of your way.
[20:54] <lifeless> speakman: ignore looms; ignore quilt
[20:54] <speakman> lifeless: yes, I've been using bzr for a couple of years by now :)
[20:54] <speakman> But there are still some workflows I just can't figure how to do "right"
[20:54] <lifeless> looms are for distro folk collaborating on won't-be-merged stuff
[20:55] <lifeless> speakman: ok, I got the wrong bit of the stick :). Can you tell me about the workflow that isn't working for you?
[20:59] <speakman> First; I'm currently the only one with write permission to the projects primary target branch. Other contributors makes their own branch of that branch and do their work on their branch. But when finished with one feature (with all revisions pushed to ~username/projectname/my-new-feature and a merge requests sent) how do they get on with the next feature? Re-branching the primary target branch once again?
[21:00] <lifeless> speakman: sure
[21:00] <lifeless> speakman: they could fairly easily do 'bzr pull lp:project --overwrite'
[21:00] <lifeless> speakman: or if they have a shared repo setup, 'bzr switch trunk; bzr pull'
[21:01] <speakman> shared repo setup..?
[21:01] <speakman> never heard of "switch"...
[21:01] <lifeless> do this somewhere innocuous
[21:01] <lifeless> bzr init-repo --no-trees project
[21:01] <lifeless> cd project
[21:01] <lifeless> bzr branch lp:YOURPROJECT trunk
[21:02] <lifeless> bzr checkout --lightweight trunk working
[21:02] <lifeless> cd working
[21:02] <lifeless> now, to make a feature branch:
[21:02] <lifeless> bzr switch -b newfeature
[21:02] <lifeless> # hack hack hack, can push etc
[21:02] <lifeless> # back to trunk
[21:02] <lifeless> bzr switch trunk
[21:02] <lifeless> # new feature
[21:02] <lifeless> bzr swich -b newfeature2
[21:02] <lifeless> #back to feature1
[21:03] <lifeless> bzr switch feature
[21:03] <luks> (btw, you can do that in one step: bzr branch --switch trunk newfeature2)
[21:03]  * speakman is practising as we speak... hold on
[21:04] <lifeless> luks: not with the same magic path lookup, last I looked.
[21:04] <lifeless> luks: we should get it doing that though
[21:04] <luks> oh
[21:06] <speakman> is this documented somewhere? it really sounds useful, and I even didn't know about it!
[21:06] <lifeless> sure is
[21:07] <speakman> this looks especially useful in python projects, where the path is part of the module namespace
[21:08] <speakman> anyone of you worked with Django?
[21:09] <lifeless> not really
[21:09] <lifeless> jelmer: how did you go on bug references?
[21:11] <speakman> however -- in general, python projects relies on the current working directory name. Using bzr all branches have their own working dir name.
[21:11] <mtaylor> jelmer: hey there... any thoughts on when a new bzr-builddeb package is going to be released to the ppa?
[21:11] <jelmer> lifeless: for commitfromnews ? Haven't spent any more time on it yet
[21:11] <jelmer> mtaylor: hey
[21:11] <lifeless> jelmer: I might do a yak shave this morning then.
[21:11] <jelmer> mtaylor: No idea, I'm not sure who's doing the PPA uploads - do you know?
[21:11] <lifeless> ping john ferlito
[21:12] <lifeless> via mail
[21:12] <jelmer> lifeless: that'd be awesome - did you see my wip branch?
[21:12] <lifeless> jelmer: no
[21:12] <mtaylor> jelmer: I don't ... I just know that I can't install bzr-builddeb on my debian build machine without it breaking bzr
[21:12] <lifeless> jelmer: I was going to start o bzr core with a new hook
[21:12] <lifeless> I do _so_ love commitfromnews
[21:12] <mtaylor> jelmer: should I just install from lp:bzr-builddeb?
[21:16] <lifeless> mtaylor: join the bzr packing team and fix the ppa ;)
[21:16] <mtaylor> lifeless: heh. I'd never thought about doing that :)
[21:18] <jelmer> mtaylor: Yeah, I'd either ask johnf for an update or switch to lp:bzr-builddeb
[21:19] <mtaylor> jelmer: cool
[21:19] <mtaylor> thanks!
[21:20] <mtaylor> jelmer: branching bzr-builddeb worked
[21:21]  * mtaylor now wants a command "bzr branch-plugin" which translates "bzr branch-plugin builddeb" into "bzr branch lp:bzr-builddeb ~/.bazaar/plugins/builddeb" ...
[21:23] <jelmer> mtaylor: talk to Beuno :-)
[21:24] <speakman> Is shared repo a way to work around this python issues?
[21:26] <speakman> Or should every python project have a "container" directory (where the setup.py usely exist)
[21:27] <speakman> questionmark... :)
[21:28] <lifeless> mtaylor: write it ;)
[21:28] <lifeless> speakman: I don't know what your python issues are
[21:29] <mtaylor> lifeless: I don't want it that badly - I want it sort of in the "I'd really like for someone to walk over and hand me a plate of freshly baked cookies" sort of way
[21:30] <lifeless> mtaylor: I've started trying to aggressively yak shave
[21:30] <chx> how can i revert on a lightweight checkout of a bzr:// ?
[21:30] <chx> it says Transport operation not possible: readonly transport
[21:30] <lifeless> mtaylor: https://code.edge.launchpad.net/~lifeless/lptools/lp-project/+merge/21124 was last nights
[21:30] <lifeless> chx: its a bug, its fixed in trunk I believe
[21:30] <chx> lifeless: wow
[21:31] <mtaylor> lifeless: BOO YAH
[21:31] <lifeless> or if not in trunkm then the patch is getting reviewed at the moment
[21:32] <chx> checking out bzr/trunk is not fast.
[21:36] <speakman> lifeless: 22:11:23 < speakman> however -- in general, python projects relies on the current working directory name. Using bzr all branches have their own working dir name.
[21:37] <speakman> "from myproject.modules import MyClass"
[21:37] <lifeless> chx: have you done lp-login ?
[21:37] <lifeless> speakman: most python projects have myproject as a directory at the top of their branch
[21:37] <speakman> lifeless: ok. that's how to solve it?
[21:38] <speakman> (it's a pinax based project I'm currently into btw)
[21:39] <chx> lifeless: how can i convert my tree into something revertable instead?
[21:40] <lifeless> bzr reconfigure --branch should do it
[21:44]  * beuno hides
[21:47] <djmeltdown> just came to get some help...but a reinstall of the software fixed my problem...so ill just say hi!
[21:52] <lifeless> jelmer: so, where is your branch?
[21:52] <jelmer> lifeless: https://code.edge.launchpad.net/~jelmer/bzr-commitfromnews/extractbugnumbers
[21:53] <lifeless> ok
[21:53] <lifeless> I'll see about getting the bzr infrastructure togetherr
[21:54] <jelmer> yarrr
[22:04] <speakman> Doing on-the-fly conversion from <RepositoryFormatKnitPack1> to (remote). source
[22:04] <speakman> This may take some time. Upgrade the repositories to the same format for better performance.
[22:04] <speakman> what's that? "(remote). source" ?
[22:08] <lifeless> launchpad
[22:08] <speakman> how do I upgrade + pushing back?
[22:08] <lifeless> you can use bzr info -v to find out mor details
[22:08] <speakman> oh
[22:08] <lifeless> there is an upgrade button on the launchpad branch page
[22:09] <speakman> oh! cool :D
[22:21] <speakman> If I set a big group as "Review Team" on a branch -- they still can't push to that branch can they?
[22:27] <jelmer> hmm, no poolie today?
[22:27] <lifeless> poolie has a day off
[22:27] <lifeless> speakman: that is correct
[22:27] <jelmer> lifeless: I'm trying to decide if he meant bb:tweak for https://code.edge.launchpad.net/~jelmer/bzr/export-use-tree-timestamp/+merge/20865
[22:28] <lifeless> yes
[22:28] <jelmer> (since he voted "Needs Fixing")
[22:29]  * kfogel is away: machine fan cleanup; back later
[22:46] <jelmer> maxb: hi
[22:46] <maxb> hello
[22:46] <jelmer> maxb: I've merged your range inclusion patch for bzr-rewrite
[22:46] <maxb> I saw, thanks
[22:50] <maxb> btw, one of the other things I'm working on is making rebase-foreign process its revisions in proper toposort order instead of the weird line-following algorithm it currently has. Do you know why it currently does what it does instead of just toposorting?
[22:55] <jelmer> maxb: hysterical raisins? It just uses the other rebase infrastructure
[22:56] <maxb> fair enough. I need to comb through my "random hackery to just make this work" branch and pull out a change for submission
[22:56] <jelmer> maxb: btw, I noticed you added explicit handling of 'hg-v1:' to pseudonyms; that shouldn't be necessary since bzr-hg has always set the converted-from revision property
[22:57] <maxb> My conversion was svn -> hgsubversion -> bzr-hg :-)
[22:59] <jelmer> maxb: I mean this change: http://bazaar.launchpad.net/~maxb/bzr-rewrite/hg-papt-rebase-foreign/revision/180
[23:00] <jelmer> maxb: those revids are already extracted in the call to foreign.foreign_vcs_registry.parse_revision_id() later in that function
[23:00] <poolie> hi jelmer
[23:00] <poolie> would you like to be patch pilot next week?
[23:01] <jelmer> hey poolie
[23:01] <poolie> it doesn't have to be a very big job but it does seem good to have one particular person driving it
[23:01] <maxb> jelmer: I had the same underlying revisions from path A: [svn ---(bzr-svn)---> bzr] and path B: [svn ---(hgsubversion)---> mercurial ---(bzr-hg)---> bzr] and I needed the two end results to be considered pseudonymous
[23:01] <jelmer> poolie: I wouldn't mind being patch pilot for a week, but I'm at lean training and a sprint next week so that week isn't ideal
[23:01] <poolie> heh, ok, maybe later
[23:02] <poolie> someone else? spiv/igc?
[23:02] <jelmer> maxb: Yes, that would still be the case without that change
[23:02] <igc> morning poolie
[23:02] <poolie> hi there
[23:02] <jelmer> maxb: ah, nevermind
[23:02] <poolie> i'm not really here today
[23:02] <jelmer> maxb: I see now you're using timestamps
[23:02] <maxb> jelmer: Yes, tortuous, isn't it :-)
[23:03] <jelmer> poolie: happy birthday btw :-)
[23:03] <poolie> thanks :)
[23:03] <maxb> And in a later revision I changed it because the timestamps didn't work because somewhere they'd become DST-shifted on one of the legs
[23:04] <maxb> Anyway, the hacks to the pseudonyms function are very much specific to a particular branch that needed weird rebasing
[23:04] <maxb> But I have bugfixes to other bits of rebase-foreign which I will polish and submit
[23:04] <lifeless> poolie: shoo :P
[23:04] <lifeless> poolie: wasn't it yesterday?
[23:04] <jelmer> lifeless: I'm in Europe :-)
[23:04] <poolie> it was
[23:04] <poolie> today is Martin Day (observed)
[23:04] <lifeless> \o/
[23:05] <poolie> lifeless: do you want to pilot next week perhasp?
[23:05] <lifeless> poolie: no thanks
[23:05] <jelmer> maxb: I guess I shouldn't look at branches that haven't actually been proposed for merging yet :-)
[23:06] <maxb> jelmer: Not if you expect them to actually be applicable for merging :-)
[23:06] <lifeless> poolie: I'm still rotated, and I only just managed to get 3 hours of personal time in the last 3 or so weeks to do coding stuff.
[23:06] <poolie> np, i understand
[23:06]  * jelmer continues with maxb's rebase-merges branch
[23:06] <lifeless> poolie: add to that that I'm travelling next week
[23:06] <maxb> thanks
[23:18] <spiv> poolie: I happy to do it if no-one else does, although I wasn't planning to do it until I was back full time.
[23:18] <spiv> poolie: enjoy Martin Day (observed) :)
[23:30] <lifeless> ok, cue music, time for another yak shaving session