[00:07] <lifeless> mwhudson: the puller has to write to submit requests :)
[00:07] <mwhudson> oh truw
[00:07] <mwhudson> i was thinking on the wrong level
[00:20] <poolie> mwhudson: that's it
[00:21] <poolie> i think i can safely promise that if the direction is read or write it will only mean that we're actually reading or writing
[00:23] <mwhudson> jelmer: is that new dulwich branch pushed yet?
[00:24] <jelmer> mwhudson: dankje
[00:24] <lifeless> poolie: you can? do you mean reading or writing to a socket?
[00:24] <jelmer> mwhudson: argh, wrong channel
[00:24] <mwhudson> :)
[00:24] <jelmer> mwhudson: I meant yes
[00:24] <mwhudson> wrong language too
[00:24] <mwhudson> ok
[00:24] <poolie> lifeless: can't I? yes.
[00:24] <lifeless> fun and games with hardware:
[00:24] <lifeless> https://bugs.edge.launchpad.net/ubuntu/+source/dmraid/+bug/372170
[00:25] <lifeless> my new machine :(
[00:25] <mwhudson> jelmer: r296 is good now?
[00:25] <jelmer> mwhudson: yep
[00:25] <mwhudson> jelmer: thanks
[00:29] <kingos> lifeless: ping
[00:29] <lifeless> kingos: hi
[00:29] <kingos> lifeless: hi. sorry to keep bugging you ...
[00:30] <kingos> lifeless: any update on that bug of mine? I have some colleagues who would massively appreciate an increase in performance of our bzr setup!
[00:30] <lifeless> kingos: no - swamped with network issues - three critical bugs
[00:30] <lifeless> kingos: I do want to get to it
[00:30] <poolie> lifeless, igc, jml, others: spiv is still away today
[00:30] <kingos> lifeless: ah ok thanks. are you the only person who could help?
[00:31] <jml> poolie: thanks.
[00:31] <lifeless> kingos: I don't think I am
[00:31] <lifeless> kingos: vila might be in a position to help sooner though
[00:31] <kingos> lifeless: I imagine it will be quite tricky, something to do with *ghosts* I imagine from my infrequent reading of email lists (not that I know what they are)!
[00:34] <kingos> I would have a go myself if I had the first idea where to start.
[00:38] <jelmer> which bug is this?
[00:39] <kingos> bug #356028
[00:40] <kingos> we have a problem with our repository that is stopping us from upgrading.
[00:40] <lifeless> jelmer: I mailed you a consistency issue the other day
[00:40] <lifeless> jelmer: is it the same one as inkscape triggers?
[00:46] <jelmer> lifeless: no, I'm not sure what that one is exactly
[00:46] <jelmer> lifeless: did you see my reply?
[00:47] <lifeless> no
[00:47]  * lifeless looks
[00:47] <lifeless> how do we move the inkscape one forward
[00:48] <jelmer> lifeless: somebody with enough knowledge of the internals needs to have a look at why bzr thinks it needs the lhs parent even if that's not necessary for the delta
[00:49] <lifeless> jelmer: can I help you learn that knowledge?
[00:49] <jelmer> lifeless: lhs parent of a text
[00:54] <jelmer> lifeless: I'd rather focus on bzr-git for now, not sure I want to dive into pack internals
[00:58] <lifeless> brb, fooding
[01:13] <igc> morning
[01:41] <igc> abentley: is BB down?
[01:53] <poolie> hello igc
[01:53] <igc> hi poolie
[02:10] <lifeless> poolie: I can't skype yet on this new machine
[02:11] <lifeless> poolie: and as we haven't stood up; let me say I'm working on https://bugs.edge.launchpad.net/bzr/+bug/360791, and after that I plan to go and redo check; check is part of the upgrade process and its way to slow
[02:12] <lifeless> I don't know that I can make it hugely faster, but I want to stab at it
[02:23] <poolie> that makes sense
[02:24] <poolie> last time i looked it was very inefficient, reading things several times
[02:24] <poolie> it's pretty old code
[02:24] <poolie> so i think you'll find some tasty fruit
[02:24] <poolie> i'm reading the subtree related threads
[02:24] <poolie> i mean nested tree
[02:39] <abentley> igc: restarted.
[02:39] <igc> abentley: thanks
[02:41] <lifeless> poolie: did I tell you, my new machine is 4-core on die?
[02:41] <poolie> yes
[02:45] <lifeless> still buzzing about that bit :)
[02:45] <lifeless> hyperthreading on top of that
[02:47] <spm> lifeless: *8* cpu whatsists!?!?
[02:47] <lifeless> spm: yup
[02:47] <spm> *awesome*!
[02:47] <lifeless> spm: i7 920
[02:48] <lifeless> now I just need to get eucalpytus up locally, then I can use ec2test @ home :P
[02:48] <spm> ha!
[02:50] <lifeless> BasicOSX: uhm
[02:50] <lifeless> BasicOSX: 1.13.2 is looking rather close to bzr.dev ?
[02:52] <lifeless> BasicOSX: rev 4113 looks to me like you merged _all_ of bzr.dev, or bzr1.14 or something
[03:02]  * poolie tries to avoid being distracted to read about i7s
[03:04] <lifeless> :>
[03:04] <lifeless> I have a fix for bug 360971
[03:04] <lifeless> erm
[03:04] <lifeless> not that
[03:05] <lifeless> I have a fix for bug 360791
[03:05] <lifeless> yes, that
[03:11] <poolie> yay way to go
[03:17] <poolie> lifeless: i got approval for the patch recommending use of lp reviews so if you don't yell i'm going to merge it
[03:17] <poolie> if there are questions or problems we can improve it later on
[03:17] <poolie> thumper: ^^
[03:18] <thumper> dogfood tastes good
[03:19] <lifeless> poolie: I saw the patch :)
[03:20] <lifeless> poolie: I would like more docs myself; its fine to say we shouldn't document it in that file, but we _should_ link to appropriate docs
[03:20] <poolie> well, i did link to 2 or 3 existing docs
[03:20] <lifeless> poolie: oh, I may have missed that
[03:20] <poolie> if there are more that should be linked, or written and linked, let's do it
[03:20] <poolie> i also filed a bug asking for more detail,
[03:21] <poolie> bug 372057
[03:21] <poolie> np
[03:25] <lifeless> jml: is there a 'reviews I need to do' page in lp?
[03:25] <jml> lifeless: not cross-project.
[03:26] <lifeless> a) is there a bug asking for one? Is there one per-project that lists 'reviews I need to do' then?
[03:26] <jml> lifeless: there's https://code.launchpad.net/bzr/+active-reviews, for example
[03:26] <jml> (maybe without the hyphen)
[03:26] <jml> lifeless: yes, there's definitely a bug asking for one.
[03:26] <mwhudson> rockstar was working on it
[03:26] <jml> I might well have filed it :)
[03:27] <jml> lifeless: https://code.edge.launchpad.net/bzr/+activereviews
[03:27] <lifeless> ok
[03:27] <lifeless> jml: if you could toss me the bug asking for it, I'll me-too it
[03:28] <rockstar> mwhudson, I'm working on it right now.  :)
[03:28] <jml> lifeless: https://bugs.edge.launchpad.net/launchpad-code/+bug/325985
[03:45] <lifeless> lunchish stuff then check()
[03:51]  * igc lunch
[04:04] <SamB> how can there get to be reviews one *must* do ???
[04:05]  * SamB wonders if this involves a phb:employer-of RDF relation
[04:06]  * SamB wonders why you people eat lunch at such odd times
[04:06] <mwhudson> SamB: reviews someone has specifically asked *you* to do, as opposed to asked a team you are in to do
[04:07] <SamB> mwhudson: OHHH
[04:07] <SamB> I see
[04:07] <SamB> that sounds an awful lot simpler to implement than what I was thinking ;-)
[04:07] <mwhudson> heh
[04:08] <mwhudson> "if you haven't done this review by the end of next week we will kidnap your first born child" ?
[04:08] <SamB> so it's "reviews wanted of *me*" vs "reviews where I'll *do*"
[04:09] <lifeless> push vs pull
[04:10] <mwhudson> yar
[04:17] <poolie> igc, hi?
[04:18] <igc> hi poolie
[04:18] <igc> lifeless, mwhudson: lp-needs is ok by me
[04:20] <poolie> igc, can we have a chat?
[04:21] <igc> poolie: of course
[04:22] <lifeless> poolie: http://paste.ubuntu.com/165270/
[04:22] <igc> poolie: just call me on pots or skype when you're ready
[04:22] <lifeless> poolie: could you very quickly eyeball that
[04:22] <poolie> ok
[04:22] <lifeless> poolie: I'm seeking a 'sounds plausible' or 'eww'
[04:22] <poolie> lifeless, others: btw [rfc] how about deleting the very old pre-brisbane-core performance documents from the tree?
[04:23] <lifeless> poolie: many are still relevant; I do agree we should houseclean a little
[04:23] <poolie> yes, of course keeping the relevant ones
[04:23] <poolie> that pastebin seems plausible
[04:24] <poolie> the other things i have in mind are:
[04:24] <poolie> there are some checks that may be format-specific, some that may be done more efficiently in a format-specific way, but some should be done regardless of format (this is vague)
[04:25] <poolie> and also that it may be useful for it to not abort on the first error if possible but rather tell us if there's more than one
[04:25] <poolie> as far as ui i'd like it to be more clear by default if everything is ok
[04:25] <poolie> at the moment normal output sometimes disturbs people
[04:26] <poolie> so something like "checked %d revisions in %d branches; everything's ok"
[04:26] <poolie> and then otoh if there is a problem giving data that will help with a bug report with few roundtrips wbn
[04:26] <lifeless> naturally ;)
[04:26] <lifeless> i have all those things in mind
[04:27] <lifeless> at the moment I'm trying to architect a flow that will be easy to code and debug, but scale well etc
[04:27] <lifeless> which is what that doc trys to get at
[04:27] <lifeless> I will add those other things to the doc though, because explicit better than implicit
[04:27] <igc> lifeless: should check become an alias for reconcile --dry-run one day?
[04:29] <lifeless> igc: maybe; reconcile was written with the idea that there are 'small issues' and 'big issues' and reconcile is the 'big issue hammer'
[04:30] <lifeless> but perhaps this is wrong
[04:33] <igc> poolie: I believe http://code.aaronbentley.com/bzr/bzrrepo/nested-trees-loom is the public branch for nested trees
[04:50] <lifeless> poolie: you seem to be repeatedly mailng the same mail
[04:51] <lifeless> poolie: I'm up to 4 copies, letting you know now ;P
[05:06] <poolie> sorry
[05:07] <poolie> i kept getting "failed to send the message"
[05:58] <igc> poolie: when you get a chance, can you land http://bundlebuggy.aaronbentley.com/project/bzr/request/%3Ce01316480903232138n34d2e189w71e7e8ee1f7e255a%40mail.gmail.com%3E please?
[06:13] <eferraiuolo> How do you people have the user accounts on their server configured for a central bzr repo accessible via ssh?
[06:13] <eferraiuolo> I'm curious how file permissions work in this case
[06:14] <eferraiuolo> My goal is to setup an AWS EC2 machine with an EBS to house a central repo for my company's code. There is just two of us with SSH access to the EC2 machine and we want to setup central (master) bzr branches there
[06:40] <poolie> igc, oh thanks
[07:08] <vila> hi all
[07:09] <vila> lifeless: 3 things
[07:09] <lifeless> vila: yo!
[07:09] <lifeless> eferraiuolo: hi; uhm I use lp :)
[07:09] <vila> 1) Most important first: have fun with your new i7 :-)
[07:09] <lifeless> vila: 6 minutes for parallel test
[07:10] <lifeless> vila: I suspect your machine is faster or something
[07:10] <vila> lifeless: 3 here :) i7 965 @3.2 GHz
[07:10] <lifeless> ah, i got the 920
[07:10] <lifeless> 2.6G
[07:11] <vila> hmm, doesn't explain the whole difference then, may be the SSD helps too
[07:11] <lifeless> oh, if youhave an ssd that is likely it
[07:11] <poolie> eferraiuolo: what he said; otherwise add accounts for all the other people, make a group-owned directory for the repository and off you go
[07:11] <lifeless> I'll try on a tmpfs
[07:11] <vila> and 12GB RAM...
[07:12] <vila> but 4 should be far enough :)
[07:12] <vila> lifeless: 2) Testing and lock noise stipple, can you give a bit of feedback ?
[07:12] <vila> 3) PQM and unicode
[07:13] <lifeless> vila: I got 3GB, for trichannel mode
[07:13] <lifeless> for 2- what you and john said sounds fine
[07:14] <lifeless> I'm fine with a method to tell the test suite we're about to get rid of a lock
[07:14] <lifeless> as for break-lock, I think it should fire a release hook event
[07:14] <vila> lifeless: it seems that pqm gives ANSI_X3.4-1968 as fs encoding, that means all UnicodeFilenameFeature depending tests are skipped, I thought you filed an RT ticket about that ?
[07:15] <vila> lifeless: ok
[07:15] <lifeless> firing a release hook event in break-lock would make tests that do a break-lock line up, I think?
[07:16] <lifeless> vila: I did, let me check
[07:16] <vila> I should look into that but, a priori, we don't try to balance lock/unlocks precisely (as in cheking the actual locks), we just count the locks
[07:16] <lifeless> * * * * * LANG=en_GB.utf8 PQM_CONFIG=/home/pqm/pqm-config/bzr-pqm.conf USER=pqm HOME=/home/pqm PYTHONPATH=/home/pqm/pqm:/home/pqm/source/bzr.dev:/home/pqm/lib/python /home/pqm/pqm/bin/pqm --run --cron
[07:17] <lifeless> vila: counting is a rough approximation
[07:17] <lifeless> vila: its hard to have the count line up and the physical locks not match
[07:17] <vila> lifeless: I understand that, on the other hand.. yeah, what you said :)
[07:17] <lifeless> specifically, to get a release we have to have locked it first
[07:18] <vila> lifeless: break lock firing a release sounds appealing, I'll try that first
[07:19] <lifeless> so all the releases can be trusted to have had to have a matching acquire; the question then becomes can we have an acquire that doesn't hook properly; or similar
[07:19] <vila> lifeless: setting LANG doesn't seem to be enough or is not taken into account then:
[07:19] <lifeless> yeah
[07:19] <lifeless> I suspect dchroot-run or something is mangling it
[07:19] <vila> Unable to represent path u'\u05e9\u05dc\u05d5\u05dd' in filesystem encoding "ANSI_X3.4-1968"
[07:19] <vila> ...non_ascii.TestNonAscii.test_ignored(iso-8859-1) SKIP                   1ms
[07:19] <lifeless> spm: ^
[07:20] <vila> and that's from the "normal" run, not the ascii one
[07:20] <lifeless> yah
[07:20] <spm> whee. fun.
[07:20] <lifeless> spm: there was a ticket about this, so I'm just going to ask ;)
[07:20] <vila> I'll tend to consider that encoding problem rather critical as it means we can have some serious regressions go unnoticed
[07:21] <spm> lifeless: :-) So... what's the problem per-se? as I'm coming a bit cold at this. I gather is a LANG/dchroot issue?
[07:21] <lifeless> spm: we set lang around pqm
[07:22] <lifeless> it doesn't seem to propogate down to the running tests
[07:22] <vila> spiv: ... and python think the file system encoding is ANSI_X3.4-1968 (similar to ascii AIUI)
[07:22] <lifeless> spm: what we need is LANG set to something present in the chroot, when make is invoked in the chroot
[07:22] <vila> eerk, s/spiv/spm/
[07:23] <spm> vila: is cool - we're used to it - well I am, can't speak for Andrew :-)
[07:23] <spm> lifeless: hmmmm.....
[08:09] <spm> lifeless: how about modifying the "precommit_hook=/home/pqm/bin/kill-chroot-processes.sh /srv/pqm.ubuntu.com/chroot-amd64 && /home/pqm/bin/dchroot-run make check" to add the LANG ==> dchroot-run LANG=blah make check ???
[08:11] <lifeless> spm: lets do that
[08:12] <lifeless> spm: but please do it with vila
[08:12] <lifeless> so that he can send a patch through immediately; cause if it fails it will need to be rolled back
[08:13] <spm> lifeless: sounds like a plan.
[08:13] <spm> vila: still around? and able to submit a patch on demand? :-)
[08:14] <vila> spiv: what kind of patch ?
[08:16] <vila> AAArgh
[08:16] <spm> vila: whatever it was that caused the UTF fail earlier. I'll just modify the pqm submit
[08:16] <vila> spiv: what kind of patch ?
[08:16] <spm> I wasn't going to say anything :-)
[08:16] <vila> shudder 'sp' still matches both 'spiv' and 'spm' vila....
[08:16] <spm> :-D
[08:17] <fullermd> Obviously, the alphabet is conspiring against you.
[08:17] <spm> vila: you're submitting to pqm against bzr trunk?
[08:17] <vila> right, so a patch that fails if the fs encoding doesn't support unicode
[08:18] <vila> I can submit against anything, if you can set up a test branch I can submit against that (but it needs some public access>)
[08:18]  * vila tries rewiring visual control *before* press-enter control
[08:20] <spm> vila: cool. ok have modifed for sftp://escudero.canonical.com/srv/www.bazaar-ng.org/rsync/bzr/bzr.dev - so submit to pqm against that whenever you're ready?
[08:21] <lifeless> vila: anything really; just want to check that trunk isn't *already* broken
[08:21] <lifeless> vila: because if it is it will reject all merges until its fixed.
[08:22] <vila> lifeless: Oh, I see, I was able to reproduce the problem locally (at least I hope so) and fixed 3 failures where pqm failed on the first, so I'm pretty sure we are safe
[08:22] <lifeless> vila: pretty sure != safe :)
[08:22] <vila> lifeless: indeed
[08:22] <BasicOSX> lifeless:  Just wanted to let you know I received your irc message and yes, I was working 1.13.2 and 1.14.1 at the same time so I could have messed something up. I had to work late tonight, just got home (2:22am) and have to be back at work at 8am so I won't be able to look at it until to night.
[08:24] <lifeless> BasicOSX: thanks; thats fine. I'm not sure it is safe to do anything anyway.
[08:24] <vila> spm: submission sent with commit message 'testing pqm unicode support'
[08:25] <lifeless> BasicOSX: but it might be something we want to add a step to into the guide ;P
[08:25] <BasicOSX> 1. Do not work on 2 releases at the same time, BasicOSX  did this is borked the 1.13.2 release.
[08:26] <BasicOSX> That seems direct and short-n-sweet
[08:27] <spm> vila: ta
[08:27] <BasicOSX> What I hate about commercial develop, product goes out the door when marketing says it's time to go. /blah... off to bed
[08:28] <vila> BasicOSX: s/commercial// and s/marketing/sponsor/ :-) This is not always a bad thing but the consequences are rarely well understood
[08:32] <vila> spm: pqm.bazaar-vcs.org says: Coming up
[08:32] <vila>    1.
[08:32] <vila>       Wed May 6 08:24:24 2009 UTC: Vincent Ladeuil <v.ladeuil+lp@free.fr>, Request for non-PQM managed branch.
[08:34] <vila> spm: if it's simpler I can send the patch against bzr.dev, it's a one-liner, if it fails, your solution is wrong, if it succeeds, your solution is right and I'll send a submission to revert my patch
[08:38] <spm> vila: that sounds fair. I can easily remove items in the queue...
[08:39] <vila> spm: ok, resubmitted
[08:44] <spm> vila: and old submission removed
[08:44] <spm> vila: how long does pqm take to test bzr these days?
[08:45] <vila> pfew, no idea, it's fire and forget for me :)
[08:45] <spm> heh
[08:46] <spm> oki we'll it's dinner for me. I'll keep checking. if it really breaks and I don't respond soon - ring me via the staff directory or something :-)
[08:47] <vila> spm: enjoy your dinner
[08:47] <zyga> hello
[08:49] <zyga> I'd like to share my logsearch plugin (in early infancy)
[08:49] <zyga> for some review and suggestions for better API
[08:52] <vila> zyga: send a annoucement to bazaar@lists.canonical.com and may be bazaar-announce@lists.canonical.com
[08:52] <vila> zarq: you'll get a wider audience :)
[09:00] <zarq> vila, i will?
[09:00] <zyga> Ok, I'll push the code to a launchpad branch first
[09:00] <vila> zarq: ghaa, sorry, that was for zyga of course :-/
[09:00] <zarq> heh ok
[09:00]  * vila kills a chicken or two
[09:02] <Magneus> Hey gang
[09:04] <limor> hi the tip of a revision are e.g. the 2 revisions which were merged together to one?
[09:08] <vila> limor: the tip is the  most recent revision in a branch, a revision can have several parents, one for usual commits, at least two for merges
[09:09] <limor> ah  ok
[09:20] <LarstiQ> zarq: ocean's wide!
[09:20] <LarstiQ> without the apostrophe even
[09:21] <vila> spm: pqm is now running the ascii part so your fix seems good
[09:21] <spm> vila: oh sweet!
[09:22] <spm> vila: I suspect you killed the correct type of chickens.
[09:22] <vila> LOL
[09:25] <lifeless> spm: 40 minutes or so
[09:25] <spm> lifeless: ta
[09:30] <Magneus> hey gang, quick question: I'm a python and bzr noob, so bear with me:
[09:30] <Magneus> bzr-svn isn't working for me, so I'm running "bzr selftest svn"
[09:30] <Magneus> But it complains "bzr: ERROR: No module named tests
[09:30] <Magneus> Is this a Python module or a bzr module?
[09:32] <Magneus> ah ha "bzr: ERROR: No module named tests
[09:32] <Magneus> pardon me
[09:32] <Magneus> found it: bzrlib.tests module
[09:34] <spm> vila: that appears to have finished - all good at your end?
[09:50] <igc> vila: sorry I didn't get to review your http auth patch today
[09:50] <igc> vila: I'll do it tomorrow if no-one beats me to it
[09:50]  * igc dinner
[09:50] <vila> spm: yup, I'll submit a patch to revert
[09:50] <vila> igc: np, enjoy your dinner
[09:51] <igc> vila: thanks!
[09:51] <vila> Magneus: you'd better try 'bzr selftest' or only 'bzr selftest -s bp.svn'
[09:54] <vila> spm: reverting patch sent
[09:54] <vila> lifeless: now pretty sure == safe ;-P
[09:54] <Magneus> Will do, thanks vila. It seems that bzr can't find my selftest module, however.
[09:55] <Magneus> Is there an environmental variable I need to set?
[09:55] <vila> Magneus: oh, I misread, what does bzr version says ?
[09:55] <vila> Oh, wait, you're on windows ?
[09:55] <Magneus> Gentoo
[09:55] <Magneus> 1.14
[09:56] <Magneus> bzr 1.14.1 on python 2.6.1 (linux2)
[09:57] <LarstiQ> Magneus: if that is a gentoo bzr, maybe they've stripped the tests out
[09:57] <vila> ok, 'bzr version' should tell you where bzrlib is installed, there you should find a test directory unless the tests.. what LarstiQ said :)(
[09:58] <Magneus> well, I ls'ed the bzrlib folder
[09:58] <Magneus> and found that there is a healthy-looking tests folder
[09:58] <Magneus> full of .py files
[09:58] <LarstiQ> Magneus: good, good :)
[09:58] <Magneus> which is what has me thinking it's something like an env variable
[09:59] <LarstiQ> Magneus: there usually aren't any env variables involved with running the tests
[09:59] <vila> Magneus: nope, nothing needs to be set 'selftest' is a first-class command :)
[09:59] <Magneus> blah
[09:59] <LarstiQ> Magneus: your ~/.bzr.log might have some clues as to what is going on
[09:59] <Magneus> I wonder why it's not finding it, then
[09:59] <Magneus> Ah! log files. good stuff
[09:59] <Magneus> ty
[10:02] <Magneus> ah ha, looks like it's wanting pycurl
[10:02] <Magneus> is that requisite for tests?
[10:03] <LarstiQ> Magneus: only for https, it is not strictly required
[10:03] <LarstiQ> or well, not even then per se
[10:03] <LarstiQ> Magneus: so no
[10:03] <Magneus> understood
[10:04] <Magneus> also getting an error "ImportError: cannot import name ForeignBranch
[10:04] <LarstiQ> Magneus: that sounds like bzr-svn
[10:04] <cornucopic> hello folks..
[10:05] <cornucopic> is there any way to avoid giving the pass in plain text in bazaar.conf when using 'smtplib' ?
[10:05] <cornucopic> best, can I make it to prompt me ?
[10:05] <Magneus> LarstiQ: right you are. I realize I had left the .6 version in my plugins folder just now ><
[10:06] <Magneus> much better. back to "no module named tests"
[10:07] <LarstiQ> Magneus: is that now bzr-svn complaining it can't find its tests?
[10:07] <Magneus> Nah. simply a "bzr selftest" call
[10:07] <Magneus> Let me know if you want to see the traceback
[10:07] <LarstiQ> pastebin it please :)
[10:07] <Magneus> http://pastebin.com/d123100bf
[10:08] <LarstiQ> ok, so it's the xmloutput plugin
[10:08] <Magneus> ah
[10:08] <Magneus> I can axe it if need be
[10:08] <Magneus> so xmloutput is trying to import its own tests folder?
[10:09] <zyga> my branch is now online with the exception of exposing some launchpad bug/feature
[10:11] <Magneus> Looks like removing xmloutput did the trick
[10:12] <Magneus> bzr selftest is running now
[10:12] <zyga> igc: https://code.launchpad.net/~zkrynicki/+junk/bzr-logsearch (if you remember yesterday's chat)
[10:13] <LarstiQ> Magneus: good. If that is the most recent version of xmloutput, it might need filing a bug about that
[10:14] <Magneus> Got it. Thanks, LarstiQ. Another question:
[10:14] <Magneus> Selftest is finding a lot of little errors, 'str' object has no attribute 'get' - etc etc
[10:14] <Magneus> cause for concern?
[10:16] <LarstiQ> Magneus: there aren't supposed to be any errors, I wouldn't get concerned just yet though.
[10:18] <Magneus> alrighty. I'll poke around at bzr-svn, then
[10:18] <Magneus> I appreciate the help!
[10:18] <Magneus> Ha. Segfault on 'bzr selftest svn'
[10:24] <spm> vila: cool. I'll leave that LANG fix on bzr.dev (only) overnight. I've emailed the other losas so they know of it's existance if you do need a reversion. G'night! :-)
[10:25] <vila> spm: I think it's fine to deploy it, unless lifeless objects, I see no reason to *not* have it everywhere
[10:25] <spm> vila: blame it on me being a paranoid sysadmin - doing a "major" change and then buggering off is... not good :-)
[10:26] <vila> spm: no pb, take your time and enjoy your night :)
[10:26] <limor> question: If I use a shared repository the revisions of the branches inside the shared repository will be found in the shared repository .bzr and not in the .bzr of the branche as it would be normally?
[10:26] <vila> limor: yes
[10:32] <cornucopic> folks: is there any way to avoid giving the pass in plain text in bazaar.conf when using 'smtplib' ?
[10:51] <liw> the "bzr commit" I started yesterday, committing all of jaunty's source code in one operation, is still running: it's not using much CPU, it's not doing system calls, and it's virtual memory size is 9+ gigabytes, which is more than the physical RAM of the machine
[10:52] <liw> it doesn't show any obvious progress going on, either
[10:52] <luks> why would you do that?
[10:52] <liw> luks, for fun, to see if bzr can handle it
[10:52] <luks> well, if you wait a day, it obviously can't
[10:52] <liw> but I don't think I want to wait much longer
[10:53] <luks> you could find a smaller project to commit to find that out :)
[10:53] <liw> any bzr devs want me to do something to see if they can learn something useful from this?
[10:55] <james_w> liw: is that with the development format?
[10:56] <liw> james_w, --development-rich-root
[10:59] <cornucopic> does this code look good for a post commit hook: http://pastebin.com/d366a9b34 ?
[11:00] <lifeless> liw: I suspect its thrashing
[11:01] <luks> cornucopic: branch.Branch.hooks.install_named_hook should not be indented
[11:02] <cornucopic> luks, you mean outside the function ?
[11:02] <Lo-lan-do> Can one define bzr aliases that involve pipes to external programs?
[11:02] <Lo-lan-do> (diffstat comes to mind)
[11:03] <luks> cornucopic: yes, it should be executed when the code is imported
[11:03] <luks> Lo-lan-do: using the bzr-extcommand plugin
[11:03] <cornucopic> ok. trying..
[11:04] <lifeless> liw: iotop
[11:04] <Lo-lan-do> luks: Trying that, thanks
[11:04] <luks> Lo-lan-do: http://bzr.oxygene.sk/bzr-plugins/extcommand/__init__.py
[11:04] <luks> there are also some examples
[11:07] <cornucopic> luks, Thanks it works. Here is what I want to do: Since, I don't want my SMTP password in a plain text file, what I want to do is, post commit, I want to call my own code to send me the commit message using the smtp_connection.py.. Is that a good line of thinking?
[11:08] <luks> cornucopic: is the plain text password in your plugin a better solution?
[11:08] <luks> I don't see how are you going to avoid storing the password in plain text
[11:09] <lifeless> cornucopic: I send mail via a local mta, then it has [root accessible only] the password for forwarding it outwards
[11:09] <cornucopic> luks, I can prompt the user for the password and have it stored in smtp_password.
[11:10] <Lo-lan-do> luks: Yay, it works :-)
[11:11] <luks> cornucopic: you could just set right file permissions on the config file, it will be accessible only by root or you
[11:11] <luks> unless you are on windows
[11:12] <luks> Lo-lan-do: of course it does :P
[11:12] <cornucopic> luks, No I am on Ubuntu :) file permissions is a easy/indirect solution..
[11:12] <cornucopic> luks, however I have another idea now..
[11:13] <cornucopic> luks, the file which parses the contents of the smtp credentials..if it comes across a smtp_password, field, then it prompts the user for the password?
[11:15] <cornucopic> luks, i.e. if the smtp_password field is blank.
[11:15] <cornucopic> luks, Does it sound reasonable?
[11:16] <luks> cornucopic: I don't know much about hooking into the config system
[11:16] <luks> cornucopic: definitely should be possible though
[11:17] <cornucopic> luks, cool! its a post-commit email hook !
[11:17] <cornucopic> have to get the bzr sources now!
[11:17] <luks> bzr get lp:bzr :)
[11:18] <cornucopic> yep !
[11:21] <limor> does it take longer to get the hiostory or a checkout of an branch if I work with an large shared repostiory?
[11:21] <luks> checkout gets the history too
[11:21] <limor> yes
[11:21] <luks> and if you work in a shared repository, it doesn't matter
[11:26] <limor> hm are there no disadvantage of shared repositorys?
[11:27] <luks> I don't there is any for a single user
[11:27] <Lo-lan-do> You can't have different permissions on different branches.
[11:28] <luks> if you use a single repository on a server where multiple users commit to it, you might find some problems
[11:28] <luks> locking, permissions, etc.
[11:43] <cornucopic> is there any IO wrapper used in bzr ?
[11:52] <lifeless> what do you mean?
[11:56] <cornucopic> For eg. Should I use input() for Input or is there a bzr specific wrapper?
[12:02] <LarstiQ> cornucopic: you might want to look into the credential stores in bzr
[12:03] <liw> lifeless, iotop tells me it's reading a fair big (500-1500 kilobytes per second)
[12:03] <liw> lifeless, however, strace shows no syscalls, so I agree that virtual memory thrashing is going on
[12:06] <liw> top does not indicate VIRT size grows much, though
[12:06] <lifeless> liw: in and out, in and out:P
[12:07] <liw> conclusion: if I wait long enough, this will actually finish, but only I'm really patient
[12:07] <liw> (I'd be more patient with a progress reporter ;-)
[12:09] <liw> still, I'm glad to see bzr is getting much further now than earlier
[12:09]  * LarstiQ giggles at larz/johm
[12:10] <liw> LarstiQ, :-)
[12:13] <LarstiQ> liw: how is your cold?
[12:14] <liw> LarstiQ, worse than yesterday, so I'll be heading for yet another nap
[12:20] <cornucopic> I have made a change to smtp_connection.py so that it prompts for a password (masked) when it doesn;t find it in bazaar.conf
[12:20] <cornucopic> this saves us from keeping our password in a plain text file..
[12:20] <cornucopic> Can this be committed a patch?
[12:25] <LarstiQ> cornucopic: the functionality sounds good. If you push a branch to launchpad and propose it for merging into bzr it can get reviewed.
[12:26] <cornucopic> LarstiQ, awesome ! Should I use the dev branch ?
[12:27] <LarstiQ> cornucopic: yup
[12:28] <cornucopic> Cool.
[12:31] <LarstiQ> liw: I know 'ole hyvä' is not the right idiom, but I do wish you to be well.
[12:59] <awilkins> bwr
[12:59] <awilkins> oops
[13:58] <cornucopic|afk> how do I go about proposing my patch to be merged?
[14:05] <cornucopic> Should I directly mail bazaar@lists.canonical.com with my patch ?
[14:05] <cornucopic> LarstiQ, ping
[14:14] <liw> LarstiQ, thanks
[14:23] <igc> zyga: thanks for the link. It sounds like you had some success which is awesome! I'll take a look tomorrow.
[14:41] <k4y> hi
[14:41] <k4y> does anyone here have experience importing a darcs2 repo into a bzr repo?
[14:42] <k4y> i'm trying to use darcs-fast-export and bzr fast-import but things just don't seem to pan out
[14:42] <k4y> if i attempt to pipe the results of darcs-fast-export into bzr fast-import i get an error from darcs-fast-export about a broken pipe
[14:43] <igc> k4y: the latest fast-import may not work with darc2 repos yet
[14:43] <k4y> if i redirect the results of darcs-fast-export (darcs-fast-export > exp) to a file and pass that to bzr fast-import (bzr fast-import exp) i get:
[14:43] <k4y> AttributeError: 'RevisionStore1' object has no attribute '_load_texts_for_file_rev_ids'
[14:43] <k4y> igc: mmm
[14:43] <igc> k4y: try bzr fast-import --classic exp and see if that works better
[14:44] <k4y> i thought the point was to emit something in an intermediate format
[14:44] <igc> k4y: it is. darc-fast-export should generate that format
[14:45] <igc> k4y: and bzr fast-import *should* import it
[14:45] <igc> k4y: but ...
[14:45] <k4y> igc: "RevisionStore1" has to attribute "_..." seems like an issue separate from the file format
[14:45] <k4y> specifying --classic doesn't seem to change anything
[14:45] <igc> darc-fast-export uses a construct, IIRC, that most other fast-export tools don't, namely 'deleteall'
[14:46] <igc> and I haven't got that fully working/tested in the latest fast-import
[14:46] <igc> k4y: however, I did leave the old fast-import algorithm available via an option
[14:47] <igc> which is called --classic from memory
[14:47] <k4y> well, unfortunately it seems that there is a bug in that code
[14:47] <igc> k4y: so the bug appears whether you use --classic or not?
[14:48] <k4y> correct
[14:48] <k4y> i'm using bzr-fastimport 0.8.0~bzr181-1 on Debian sid
[14:48] <k4y> not sure whether that's old or not
[14:48] <k4y> igc: i can pastebin the complete traceback, if you'd like
[14:49] <igc> damn. Can you raise a bug please with a small fast-export stream reproducing it?
[14:49] <igc> k4y: I'm not going to be able to look at it now (just before midnight here)
[14:49] <k4y> hrm
[14:50] <k4y> okay, i'll see if i can find the smallest reproducable stream
[14:50] <igc> k4y: thanks
[14:50] <igc> if the stream is large, compressing it is a good idea before attaching it to the bug report btw
[14:51] <igc> k4y: rev 181 is pretty recent as well
[14:53] <k4y> igc: how does the plugin decide whether to use revision_store.RevisionStore1 or RevisionStore2?
[14:54] <igc> k4y: I'd have to look at the code
[15:12] <igc> night all
[15:18] <cornucopic> Bye all!
[15:57] <ronny> LarstiQ: sup?
[16:03] <LarstiQ> ronny: being a bit stuck on proving psi(s) > g(t) on an interval and reverse outside it.
[16:03] <LarstiQ> ronny: that is, been doing math first today.
[16:03] <LarstiQ> and now I need a break
[16:03] <LarstiQ> what better break than inflicting easy_install on myself? ;)
[16:04] <Lo-lan-do> psi() is... quantum?
[16:05] <LarstiQ> Lo-lan-do: no, defined in terms of linear interpolation between phi(t, h) and g(t), where g is a concave function
[16:05] <LarstiQ> it shouldn't be hard, just need to flex my muscles more
[16:06] <ronny> LarstiQ: i belive easy_install is supposed to die at some point tho
[16:06] <ronny> LarstiQ: and pip is supposed to work, too
[16:06] <LarstiQ> ronny: yeah, I agree. And you're probably right that it is very painful to read.
[16:07] <LarstiQ> Lo-lan-do: (chapter on non-parametric statistical models using kernel density estimators)
[16:08] <ronny> LarstiQ: the best fix would be to just upload to pypi
[16:08] <LarstiQ> ronny: if you have an automated way of doing that?
[16:08] <LarstiQ> and well, from our point of view also not the best
[16:09] <ronny> LarstiQ: why is that not the best, it creates the least indirections, and is a extra mirror
[16:09] <LarstiQ> ronny: ideally, humans would go to the Downloads page
[16:10] <LarstiQ> ronny: or hmm
[16:10] <ronny> LarstiQ: and they would
[16:10] <ronny> but scripts will go to pypi
[16:10] <LarstiQ> ronny: maybe making the pypi page the same as the Download one would work
[16:10] <LarstiQ> ronny: right. I promised you a fix for today, and you will get it.
[16:11] <ronny> im currently trying to get an idea how to teach py.test to run tests in slave virtualenvs
[16:24] <LarstiQ> ronny: do you have machinery to go through a large set of packages on pypi and check their setup.py/.cfg in an automated way?
[16:31] <ronny> LarstiQ: not really a good one - my current scripts dont check the sucess
[16:31] <ronny> virtualenv + pip could help
[16:38] <LarstiQ> ronny: how about getting a package listing?
[16:38] <ronny> all i do is 2 for loops and invoking virtualenv + easy_install
[16:39] <LarstiQ> hah :)
[16:39] <ronny> http://paste.pocoo.org/show/116024
[17:26] <Lo-lan-do> jelmer: Hi, does http://pastebin.com/f4eb7e154 make sense to you?
[17:26] <Lo-lan-do> I still can't do a git clone through bzr-upload-pack, but at least this patch seems to get me further on the path :-)
[17:28] <jelmer> Lo-lan-do: no, that seems wrong - the parent_lookup function that's passed in is incorrect
[17:29] <Odd_Bloke> When using --merge, how does bzr-buildpackage unpack the tarball?
[17:29] <Lo-lan-do> Ah.  I'll go back to investigating then.
[17:30] <jelmer> Lo-lan-do: the parent_lookup function should basically receive a bzr revid and return a matchiing git sha1
[17:30] <cornucopic|away> vila, ping. Amit Saha h
[17:30] <james_w> Odd_Bloke: tar recently
[17:31] <cornucopic|away> vila, I am the one who is talking to you about the smtp patch..
[17:31] <Odd_Bloke> james_w: I'm seeing a pax_global_header file created at some point.
[17:31] <vila> no you aren't, your nick says you're away, I'm just hearing voices :)
[17:31] <james_w> Odd_Bloke: then you have the old buggy version
[17:31] <cornucopic|away> vila, Voices it is then :)
[17:31] <Lo-lan-do> jelmer: I see.
[17:31] <jelmer> abentley: ping
[17:31] <Odd_Bloke> james_w: Ah, OK.
[17:31] <vila> cornucopic: haaa, does it work now ?
[17:32] <cornucopic> vila, No. Getting SMTP auth error
[17:32] <vila> interesting, you reverted your patch right ?
[17:32] <jelmer> abentley: I'm looking at providing a patch that moves Branch.update_references() -> InterBranch.update_references(). Do you think there is any value in keeping a Branch.update_references() ?
[17:33] <cornucopic> vila, yes, yes. I have commented out the lines..
[17:34] <abentley> jelmer: Sounds good.  I think we don't normally use Inter objects directly.  Do you want to change that.
[17:34] <abentley> ?
[17:35] <vila> cornucopic: so, what error do you get exactly ?
[17:36] <jelmer> abentley: No, I think using Branch.update_references() is preferable over using InterBranch.update_references() for API users
[17:36] <Odd_Bloke> I have a version string like '0+git20090506-1985f32-1', and bzr-buildpackage is giving me 'bzr: ERROR: Unable to find the needed upstream tarball: python-django-formfieldset_0+git20090506.orig.tar.gz.'  Bug?
[17:36] <cornucopic> vila, 'SMTP error: 530 5.7.0 No AUTH command has been given'
[17:36] <abentley> jelmer: So, keeping Branch.update_references as just a call into InterBranch.update_references seems fine to me.
[17:37] <Odd_Bloke> james_w: ^
[17:38] <james_w> Odd_Bloke: that's wrong then
[17:38] <james_w> Odd_Bloke: public branch?
[17:38] <Odd_Bloke> james_w: svn://svn.debian.org/svn/python-modules/packages/python-django-formfieldset/trunk
[17:38] <Odd_Bloke> I think that's the public address.
[17:47] <cornucopic> vila, nothinig much in .bzr.log with -Dauth
[17:47] <cornucopic> vila, only the earlier error message exists
[17:48] <vila> that means we don't match anything there, try to set a breakpoint and look at what auth.get_user() and auth.get_password() return
[17:48] <vila> cornucopic: that means we don't match anything there, try to set a breakpoint and look at what auth.get_user() and auth.get_password() return
[17:49] <james_w> Odd_Bloke: thanks, that's a stupid bug
[17:49] <cornucopic> vila, without the :25 it works!
[17:49] <cornucopic> vila, it asks for the password!
[17:49] <vila> cornucopic: ok, that's a nasty bug, can you file it at launchpad ?
[17:50] <cornucopic> vila, But however, is that really 'clean' ? I will file it- can you help me with the contents? and I would also like to fix it :)
[17:51] <vila> cornucopic: well, no, it's not clean, but python support specifying the port in the host for smtp, whereas in bzr there ar separated far earlier
[17:51] <vila> cornucopic: for the content, just explain what you expected, what you did, what you got, and mention the work around we just found
[17:52] <cornucopic> vila, so ideally, it should be able to take it from bazaar.conf? or is the :25 the ideal behavior?
[17:53] <vila> smtp_connection should be able to split the server variable into host and port
[17:54] <vila> once that is done, auth.get_user() and auth.get_password() will need to be updated to add that port parameter too
[17:54] <vila> and certainly other uses of _smtp_server should be updated accordingly
[17:55] <Odd_Bloke> james_w: No worries, thanks for looking at it. :)
[17:55] <Odd_Bloke> What're the odds it'll be in a Debian repo by tomorrow morning? ;)
[17:56] <vila> cornucopic: hmmm, that sounds a bit to invasive... may be splitting host, port before calling get_user() /get_password() will be enough
[17:56] <james_w> Odd_Bloke: slim, it will be in a branch in about 2 minutes though
[17:56] <vila> cornucopic: you'll need to add proper tests for that too :) Look into bzrlib/tests/test_smtp_connection.py
[18:03] <rellis> Anyone know where loggerhead looks for the config file by default?
[18:04] <rellis> or if theres a way to control that in 1.10?
[18:09] <beuno> rellis, what command are you using to start?
[18:09] <beuno> serve-branches or start-loggerhead?
[18:10] <rellis> beuno: serve-branches
[18:10] <beuno> rellis, it doesn't have a config file  :)
[18:10] <rellis> !? :)
[18:10] <rellis> okay just a sec
[18:10] <beuno> (it will in the near future)
[18:11] <rellis> beuno: I just want to define that server.webpath
[18:11] <cornucopic> vila, filed the bug: https://bugs.launchpad.net/bzr/+bug/372800
[18:11] <rellis> beuno: I'm proxying through apache and need to force url's to read http://bzr.myorg.com
[18:12] <beuno> rellis, and you've installed python-pastedeploy?
[18:12] <beuno> rellis, there's some information on the README on how to do that
[18:12] <rellis> beuno: python paste yes
[18:12] <rellis> beuno: okay fair enough
[18:13] <rellis> beuno: i see this bit about --prefix.. but that only allow to append /something.. was that what you meant?
[18:14] <beuno> rellis, yeah.
[18:15] <beuno> rellis, how about sending an email to the list?
[18:15] <beuno> I know it's been solved before
[18:15] <beuno> by thumper, mwhudson and lifeless
[18:15] <rellis> beuno: okay thanks
[18:15] <beuno> but they're all sleeping now
[18:15] <rellis> gotcha
[18:17] <rellis> beuno: your first guess was actually correct
[18:18] <rellis> beuno: i had paste but no PasteDeploy
[18:18] <beuno> rellis, needing pastedeploy?  :)
[18:18] <rellis> yep
[18:18] <rellis> thanks for thep ointer :)
[18:18] <beuno> no worries
[18:18] <beuno> any ideas on how we could of improved documentation to make that more obvious?
[18:19] <LarstiQ> make it a mandatory dependency?
[18:19] <rellis> beuno: Your docs actually seem spot on to me, it just didn't quite connect for me Paste and PasteDeploy beign different.. im a unix admin and a bit of a python novice
[18:20] <beuno> LarstiQ, even when it's just used for specific cases?
[18:20] <beuno> I don't necessarily think it's bad
[18:22] <LarstiQ> beuno: I know some people need it and miss it. I don't know how large the group of people not needing it is.
[18:22] <LarstiQ> beuno: afaik, it is hard to detect when you will need it?
[18:22] <beuno> LarstiQ, it is
[18:22] <beuno> well
[18:22] <beuno> it's a very small dependency
[18:22] <beuno> so it can't hurt to add it I guess
[18:22] <beuno> will make the experience better for some users, without making it worst for others
[18:23] <beuno> sounds like a good balance
[18:23] <LarstiQ> beuno: that is something for you-the-loggerhead-team to judge :)
[18:24]  * beuno is about to realease a new version any moment now
[18:29] <Peng_> beuno: That reminds me, I have a branch adding a several things to NEWS, though I'm not done. https://code.edge.launchpad.net/~mnordhoff/loggerhead/more-news
[18:29] <rellis> Does loggerhead support multiple repos in one instance?
[18:30] <beuno> Peng_, just slap it straight through if it's just adding stuff to NEWS
[18:30] <beuno> rellis, what do you mean multiple repos?
[18:30] <elmo> is there anyway to tell what a bzr pull did after the fact?
[18:30] <elmo> .bzr.log doesn't seem to record the version we were before the pull
[18:30] <elmo> s/version/revno/
[18:30] <Peng_> elmo: No. You could use "bzr pull -v" though.
[18:31] <elmo> peng: well sure, if I had a time machine :-p
[18:31] <Peng_> Git sets local tags, OLD_HEAD and HEAD or something like that.
[18:31] <Peng_> elmo: Right.
[18:31] <Peng_> Sorry. :\
[18:33] <LarstiQ> elmo: you could ls -t on the repo maybe, but nothing convenient after the fact.
[18:34]  * SamB wonders how to prevent aptitude from preferring package versions from PPAs
[18:34] <rellis> beuno: ummm.. that's probably the wrong bzr term... we have seperate projects
[18:34] <LarstiQ> elmo: that is, it says 'Now on revision 4340.' but not from where.
[18:34] <LarstiQ> elmo: I think it would be good to have that though.
[18:35] <LarstiQ> SamB: /etc/apt/preferences
[18:35] <LarstiQ> rellis: loggerhead works with a directory hierarchy
[18:35] <SamB> LarstiQ: figured
[18:35] <LarstiQ> rellis: so give it /srv/bzr for example, and it will serve up every branch under there, doesn't care about the repositories they are in
[18:35] <SamB> LarstiQ: oh, preferences huh?
[18:36] <SamB> I have apt.conf ...
[18:36] <SamB> Apt {
[18:36] <SamB>   Default-Release "testing";
[18:36] <SamB> }
[18:36] <rellis> LastiQ: Ah, gotcha. Thanks.
[18:36] <LarstiQ> SamB: man apt_preferences
[18:36] <LarstiQ> SamB: and look for Pin
[18:37] <SamB> LarstiQ: oh, I was really looking for something a bit more automatic than that ;-)
[18:37] <SamB> oh, hmm, nevermind
[18:37] <SamB> it's more than it sounds
[18:38] <rellis> LarstiQ: When I give loggerhead /opt/bzr as the root it says no revisions in the one tab and I get a 500 eror when visiting the file tab.
[18:39] <rellis> LarstiQ: I don't quite get how to navigate down into my projects which are directly under /opt/bzr i.e. /opt/bzr/Main
[18:40] <LarstiQ> rellis: using serve-branches?
[18:40] <rellis> yes
[18:40] <rellis> 1.10
[18:40]  * LarstiQ blinks
[18:41] <LarstiQ> beuno: ^^?
[18:41] <rellis> oh i think might be a perms issue
[18:43] <rellis> LarstiQ: Ya I don't get it.
[18:44] <LarstiQ> ronny: the whitespace in easy_install :(
[18:44] <LarstiQ> made me think pkg_resources.py was almost empty
[18:44] <LarstiQ> but then grep told me it _did_ have the class definition for Environment
[19:02] <james_w> Odd_Bloke: oh, I forgot to say that the fix is in lp:bzr-builddeb/2.1 if you want it
[19:08] <Odd_Bloke> james_w: Thanks again. :)
[19:36] <eferraiuolo> once a rich-root repo always a rich-root repo?
[19:36] <eferraiuolo> I'm trying to get a branch off of rich-root, is that possible?
[19:38] <Peng_> eferraiuolo: Once a rich-root, always a rich-root, like you said.
[19:41] <eferraiuolo> Peng_: is it recommended to use rich-root as a default?
[19:43] <Peng_> beuno: FWIW, I've finished up and merged my NEWS stuff.
[19:43] <beuno> Peng_, awesome, thanks
[19:43] <Peng_> eferraiuolo: Well...yes, more or less.
[19:43] <RainCT> Hi
[19:44] <RainCT> If I have commits ...502, 503, 502.1.1 (a merge done after 503) and 504, how can I revert only the changes done in revision 503?
[19:44] <LarstiQ> eferraiuolo: bzr is moving in that direction
[19:44] <LarstiQ> eferraiuolo: but at the moment, it will mean everyone that interacts with that branch/repo will need rich-root too, and you may not want to force that yet.
[19:45] <LarstiQ> eferraiuolo: since non-rich root -> richroot is possible, but the other way around is not.
[19:45] <Peng_> RainCT: "bzr merge . -r 503..502" or something like that.
[19:45] <RainCT> Peng_: thanks!
[19:46] <eferraiuolo> LarstiQ: Is it best practice to use the latest repo format 1.14, or the default 0.92? Therefore use 1.14-rich-root by default?
[19:48] <LarstiQ> eferraiuolo: best practice is to interoperate with older clients, 1.14 is too new. If you don't care about that, 1.14-rich-root sounds good.
[19:49] <LarstiQ> (there is a limit to old clients of course, yesterday someone tried a 0.11 client. That's too far :)
[19:49] <Peng_> beuno: And I just added 1.15 to require_any_api.
[19:50] <beuno> Peng_, we will require bzr 1.15
[19:50] <beuno> ?
[19:50] <eferraiuolo> LarstiQ: me, my business partner, and our server all have 1.14 on them; I'm thinking that we don't care about the older clients, we also are running the latest one.
[19:50] <eferraiuolo> LarstiQ: Thanks for the insight.
[19:51] <Peng_> beuno: I just added 1.15; I didn't remove 1.11 or 1.13. I think that's okay, right?
[19:51] <beuno> Peng_, I think it is
[19:51] <beuno> 1.14 as well?
[19:51] <beuno> maybe?
[19:52] <Peng_> beuno: I think they skipped 1.14.
[19:52] <beuno> maybe
[19:53] <LarstiQ> Peng_, beuno: qua minimum api versions, there is 1.13 and 1.15
[19:53] <LarstiQ> 1.14 exists in 1.14.0, but got fixed to be 1.13 in 1.14.1
[19:54] <LarstiQ> since it's a minimum, having 1.13 works fine
[19:54] <LarstiQ> eferraiuolo: then you're good to go
[19:55] <Peng_> Ah, okay.
[21:11] <Peng_> Wow, URLs like "nosmart+:parent" actually work too. That's awesome.
[21:12] <LarstiQ> ronny: ahem, it seems our moin doesn't do the comments parser. But at least easy_install can find 1.12 now ;)
[21:12] <LarstiQ> Peng_: nosmart+:parent/../sibling!
[21:15] <LarstiQ> ronny: next problem might be that setup.py alone is potentially not enough (on Windows)
[21:15] <Peng_> Ah, right, I forgot about URLs like that. Even better! :)
[21:19] <LarstiQ> beuno: do you know what version of moin bazaar-vcs.org is running?
[21:19]  * beuno looks it up
[21:21] <beuno> LarstiQ,  Moin 1.5.7
[21:21] <LarstiQ> beuno: thanks
[21:54] <LarstiQ> ronny, beuno: it seems the moinmoin wiki parser comment option got added in 1.6.0, 2 versions after what we're currently using.
[21:54] <beuno> LarstiQ, ah. I'll ask IS about upgrading
[21:57] <cody-somerville> bzr: ERROR: exceptions.TypeError: a float is required
[21:58] <cody-somerville> When I did bzr break-lock
[21:58] <LarstiQ> cody-somerville: there are bugs about that
[21:58] <cody-somerville> okay
[21:58] <cody-somerville> How do I break the lock?
[21:59]  * LarstiQ looks that up and then goes to bed
[22:02] <LarstiQ> cody-somerville: bug #365891 it seems
[22:03]  * LarstiQ is too tired to discern what to do
[22:03] <LarstiQ> ronny: things are in motion, but now I'm going to sleep.
[22:03] <LarstiQ> good night!
[22:06] <Peng_> I think the answer to the break-lock thing is "upgrade!".
[22:40] <phinze> is there an easy way to pull just a single file out of bzr?
[22:40] <phinze> got a case with a large branch and don't need the whole repo
[22:41] <beuno_> phinze, you could use loggerhead  ;)
[22:41] <phinze> beuno_: true, but i'm looking to pull something from source control in a script
[22:42] <phinze> specifically a crontab i'd like to install which is installed in our main project codebase
[22:42] <beuno_> phinze, ah, then you can do that with bzrlib
[22:42] <beuno_> a python script that grabs it
[22:42] <beuno_> you can look at how loggerhead does it
[22:42] <Peng_> phinze: You could use "bzr cat", but I dunno how much of the repo it'd wind up downloading.
[22:42] <thumper> what format should I use for brisbane core with 1.15dev?
[22:42] <Peng_> thumper: You mean development6-rich-root?
[22:43] <thumper> cool, 'cause I used --development-rich-root and got --development6-rich-root
[22:43] <beuno> phinze, not at the moment, no
[22:43] <thumper> I just wanted to be sure I had the right one
[22:43] <phinze> Peng_: well that worked... 2146KB downloaded
[22:43] <phinze> not terrible
[22:44] <Peng_> thumper: Yeah, --development-rich-root is an alias for the latest, well, rich-root development format, which is currently development6-righ-root.
[22:45] <thumper> I wish python had better multi core support
[22:45] <thumper> branching into a new brisbane core is slow, but only using one of my four cores
[22:47] <phinze> beuno: Peng_: thx much
[23:13] <cody-somerville> Is there any way to see how many commits a branch has had? Include those included in merges?
[23:13] <jam> cody-somerville: bzr ancestry | wc -l, bzr log -n0 | grep revno | wc -l
[23:14] <cody-somerville> neat, I didn't know about that command
[23:16] <cody-somerville> hmm
[23:16] <cody-somerville> didn't work
[23:16] <cody-somerville> wc: invalid option -- ','
[23:16] <cody-somerville> oh
[23:16] <cody-somerville> doh
[23:28] <rellis> Anyone know if the loggerhead root directory to serve needs to be a "bazaar directory"?
[23:28] <mwhudson> rellis: it definitely doesn't
[23:28] <rellis> okay
[23:28] <rellis> hmm.. can't figure out why i get a 500 on the files tab when i set it to my parent directory containing my bazaar projects
[23:29] <mwhudson> rellis: are you using serve-branches or start-loggerhead ?
[23:29] <rellis> http://www.pastebin.ca/1414760
[23:29] <rellis> i'm using serve-branches
[23:29] <rellis> that's the error i receive
[23:30] <rellis> i verified the permissions are correct on the repo as well
[23:30] <mwhudson> rellis: there isn't a files tab on non-bazaar directories
[23:32] <rellis> oh weird mwhudson
[23:32] <rellis> the parenty directory i'm pointing serve-branches at has a .bzr and .bzr.log
[23:32] <rellis> i'm going to try and delete them
[23:34] <rellis> mwhudson: Thanks, all is working now :)
[23:34] <rellis> all praise be to #bzr!
[23:34] <mwhudson> rellis: ah, k
[23:34] <mwhudson> glad it's working
[23:42] <Peng_> rellis: You don't have to delete .bzr.log.
[23:43] <rellis> Peng: It's already gone, and good ridance I say :)
[23:43] <rellis> but thanks for the tip
[23:46] <lifeless> igc: ping [when you get here]
[23:56] <spiv> Good morning.
[23:57] <jelmer> moin spiv