=== asabil_ is now known as asabil [12:55] I'm already liking bazaar...it's so simple. [12:56] cool [12:56] I like to hear such things === igc [n=igc@ppp121-45-197-71.lns1.bne1.internode.on.net] has joined #bzr [01:00] morning all === fog [n=fog@debian/developer/fog] has left #bzr [] [01:03] hi [01:03] jelmer: ping [01:05] jelmer: your code.launchpad.net/~jelmer/bzr-svn/trunk is borked [01:37] lifeless: thanks, I'll have a look [01:39] lifeless: the new annotation stuff is in. === jml [n=jml@ppp108-61.static.internode.on.net] has joined #bzr [01:55] jelmer: I think you renamed something and didn't tell launchpad [01:55] jelmer: also you should tell launchpad what branch is used for each release series === poolie [n=mbp@ppp112-44.static.internode.on.net] has joined #bzr [01:57] helol [02:01] hi [02:02] hi poolie === danlarkin [n=danlarki@cpe-24-195-204-195.nycap.res.rr.com] has joined #bzr === spiv [n=andrew@86.228.233.220.exetel.com.au] has joined #bzr [02:31] poolie: w.r.t. your partial review, did you want the -D options in a separate 'debug-options' topic, in a separate "table" or just all together in the existing table separated by a newline say? === jrydberg__ [n=johan@213.115.45.46] has joined #bzr [02:32] abentley: if you're happy with Nam's tweak to the hook doc in his pre-commit patch, let me know and I'll merge the change today [02:42] igc,just in the same thing separated by a newline [02:42] would be fen [02:42] fine [02:42] thanks [02:42] igc: abentley is not here [02:42] ok [02:52] spiv, ping? === grimboy_uk [n=grimboy@85-211-243-222.dsl.pipex.com] has joined #bzr [02:58] pong [03:01] lifeless, should we be using ppas at all for bazaar packaging? [03:01] spiv, can i call? [03:02] Sure. [03:04] poolie: no advantage at this point [04:01] poolie: just confirming, the indentation of NEWS items was explicitly reduced by 1 char in 2773. Any reason for that? [04:01] igc, because i noticed that the rest rendering had them at different bulletpoint levels [04:01] in different sections of the file [04:02] i think i got it right [04:02] np - just impacting merging of course. [04:02] yes http://doc.bazaar-vcs.org/bzr.dev/en/release-notes/NEWS.html#in-development [04:02] it's better but there are still some that are a bit worng [04:04] ok - I'll clean it up now as a trivial change. I need to fix some other ReST formatting anyhow in developers/update.txt so I'll do both while I'm at it [04:06] jml, hi? [04:06] poolie: hi [04:09] igc: just sent a commit patch up that you might like to review [04:10] lifeless: got the email re memory but no patch thru yet [04:11] lifeless: I have 4G on my main benchmarking machine of which 1G is given to a VM btw [04:12] lifeless: ok, patch thru now - will review today [04:14] are you able to benchmark outside the vm ? [04:15] I'm doing that - in the other 3G [04:15] cool [04:15] the VM is Windows [04:15] we still spend 13% in libz [04:16] but I'm not surprised that compression is an overall win - thanks to reduced IO [04:16] oh yes === AfC [n=andrew@office.syd.operationaldynamics.com] has joined #bzr [04:17] raw pack is 990MB when annotations are used === jdong has just sinned.... === jdong rewrote his own tailor, tailored for svn [04:22] tailor config files have just been more painful than swallowing needles for me... [04:24] why not use bzr-svn ? [04:24] 'pull' is about as simple as it gets :) [04:24] lifeless: because I only need a -20-revision horizon.... [04:25] also, for my KTorrent needs.... bzr-svn would have to mirror the *entire* KDE xD [04:26] but for smaller trees, bzr-svn is bliss [04:32] jdong: why would it mirror everything ? [04:33] lifeless: because KTorrent is a subdirectory of the entire KDE subversion repository.... [04:33] lifeless: at least from what I understand, I would have to branch the entire KDE svn, not just a subdirectory [04:37] if its structured well bzr-svn can treat them as nested trees [04:40] New bug: #136890 in bzr "merge --uncommitted ignores specific file" [Undecided,New] https://launchpad.net/bugs/136890 [04:41] lifeless: hmm I'll have to look more into that then === igc lunch [05:14] igc: another one up === NamNguyen [n=namnt@148.177.217.131] has joined #bzr [05:39] lifeless: got it - will review now === abentley [n=abentley@bas8-toronto63-1088754407.dsl.bell.ca] has joined #bzr [06:14] lifeless: what's our policy w.r.t. changing return values on public methods? Should we use another name like add_lines_get_details() instead of just changing what add_lines returns? [06:15] igc: we aim for compatability where the tradeoffs are worth it [06:15] this is very much an internal aspect of implementation, I don't think compatability is worth it [06:16] I'm ok with that. [06:17] still, might be worth putting it in the API breaks part of NEWS for completeness, yes? [06:20] I did [06:20] :) [06:23] /wishes he looked at the diff for NEWS in meld and not just bzr cdiff :-) === abadger1999 [n=abadger1@65.78.187.68] has joined #bzr [06:27] spiv, hi? [06:27] igc: "Can we get this change through as an incremental improvement and have [06:27] this discussion separately?" yes, in principle, i'll read the code [06:27] cool === Verterok [n=Verterok@184-220-114-200.fibertel.com.ar] has joined #bzr [06:34] spiv: pack patch you may be interested in up [06:34] spiv, how's the format doc? [06:36] poolie: Will have it mailed in a few minutes. [06:39] lifeless: can you quickly explain the changes to test_weave.py? StoreText and StoreTwo are redundant tests I gather so deleting them is fine, yes? [06:40] poolie: I'm done for the day; started at 6am. 3 patches up, user time is now 3m5seconds [06:40] igc: thats right. The other change was to use the new return value api [06:41] ok - all approved. I'll mark it in BB as such. [06:41] thanks [06:45] poolie: ping [06:55] lifeless: if you're still there, that change might be breaking sefltest test_bundle. I'll dig a bit deeper [07:00] igc: it does. I'll fix and submit tomorrow morning [07:00] ciao [07:00] bye === ne1uno [n=ne1uno@dialup-4.156.210.253.Dial1.Boston1.Level3.net] has joined #bzr === bialix [n=chatzill@89.21.82.79] has joined #bzr [07:15] lifeless: hi === poolie [n=mbp@ppp112-44.static.internode.on.net] has joined #bzr [07:28] bialix: lifeless has wrapped up for the day after an early start [07:29] spiv, thanks for your thorough review of C patience diff [07:29] poolie: hi === orospakr [n=orospakr@CPE0014bf6eebf5-CM000a73a95880.cpe.net.cable.rogers.com] has joined #bzr [07:30] hi bialix [07:31] thanks for the review poolie === jml_ [n=jml@ppp121-44-221-92.lns1.hba1.internode.on.net] has joined #bzr === hdima [n=hdima@idealer.cust.smartspb.net] has joined #bzr === davidmccabe [n=david@c-67-171-248-19.hsd1.wa.comcast.net] has joined #bzr [08:33] Sorry, this seems like a dumb question, but I couldn't find with google: [08:33] I have two branches here; how do I see the diffs between them? [08:35] davidmccabe, bzr missing would be one way [08:35] never mind, that was too easy :) [08:36] it *looks like* I can just do, bzr diff wc-1 wc-2 [08:36] yeap, that would output a diff [08:36] missing tells you the difference on the commit level [08:37] ah, I was looking for a diff. [08:37] to recollect all my changes at the end of a feature branch. [08:37] actually, I am comparing VCSs on speed here. [08:37] My actual VCS for work is SVN. It took fifteen minutes. [08:37] git does it in under a second. [08:38] bzr does just fine at 1.29 seconds. [08:38] ah, right, bzr isn't focused too much on performance at the moment, although a lot of work is being done on it [08:38] It performs great! [08:38] git is written in C with a bit of assembly, and it's only a few times faster for this operation. [08:38] (must be IO-bound?) [08:39] well, it'll be fun to watch when they do focus on performance :D [08:43] davidmccabe, beuno, we are very focussed on performance in our current work [08:43] we were not so much in the past [08:43] but look at all the performance patches on the list in the last week === Basic_py [n=Basic@gatekeeper.real-time.com] has joined #bzr === ThomasAH [n=thomas@aktaia.intevation.org] has joined #bzr === siretart [i=siretart@ubuntu/member/siretart] has joined #bzr === jrydberg_ [n=johan@213.115.45.46] has joined #bzr === jml_ is now known as jml [08:52] poolie, right, I've seen all the working going on, I just still have in my head the so much repeated phrase "we are not focusing on performance" :D === beuno removes the "not" part from his head [08:53] poolie, would that mainly be the "pack" feature? [08:54] pack, commit performance, hpss, inventory changes [08:54] iter merge [08:55] that just got in, so it's not in 0.90, right? I have a few <1gb branches at the office I would like a performance boost on :D [08:56] pack will be in 0.92, not the last release or this one === vila [n=vila@lec67-4-82-230-53-244.fbx.proxad.net] has joined #bzr [08:56] but if you want to try it from robert's branch that would be enormously useful [08:56] hi all [08:56] hi vila [08:57] poolie, sure, I could run some tests if that would help, they mainly contain a lot of binaries (PSDs, PNGs and all that) [08:57] poolie: sorry for the delay in coming back, huge backlog :-/ [08:58] vila, np === mvo [n=egon@p54A67360.dip.t-dialin.net] has joined #bzr [09:00] poolie: not sure I get all the details right, but it looks like I will be most helpful to bzr by: 1) looking at the FTP password bug, 2) multiple connections for update, 3) auth-ring spec, 4) recursive hash on directories [09:00] in that order of priority [09:00] any comment ? [09:01] that sounds great [09:01] i'm working on 45 [09:01] 4 === davidmccabe [n=david@c-67-171-248-19.hsd1.wa.comcast.net] has left #bzr ["Leaving"] === ddaa [n=david@canonical/launchpad/ddaa] has joined #bzr [09:02] poolie: I re-read your directory-fingerprints.txt yesterday, nice work, I'd try to comment on it asap === fog [n=fog@debian/developer/fog] has joined #bzr [09:07] is Lukas here? [09:08] poolie: do you except your work to land in 0.91 or later ? [09:08] later, it's based on packs and they will likely be in the next release [09:09] ok === RichardL [n=Skippy@host81-149-28-129.in-addr.btopenworld.com] has joined #bzr === g0ph3r [n=g0ph3r@p57A0A021.dip0.t-ipconnect.de] has joined #bzr === hsn_ [n=radim@234.114.broadband5.iol.cz] has joined #bzr === RichardL is now known as rml === allenap [n=allenap@212.233.37.68] has joined #bzr === matkor [n=matkor@beauty.ant.gliwice.pl] has joined #bzr [09:31] New bug: #136942 in bzr "What's in the trash" [Wishlist,Triaged] https://launchpad.net/bugs/136942 === AfC [n=andrew@office.syd.operationaldynamics.com] has joined #bzr [09:41] vila, interesting suggestion [09:41] I claim royalty rights on the name when somebody writes "bzrchaeology". [09:42] poolie: Just had the need for it :) [09:43] fullermd: I will argue that I use the name archeology for years ! Whether for VCS purposes or just trying to understand code :) [09:43] Yes, but you didn't pun it with 'bee zee arr'. === fullermd files a trademark. [09:44] fullermd: and don't start me about explaining young developers that, no, people are not stupid, even if their code looks so. Once, with the help of archeology, you understand why they wrote it this way *at the time* their code was not stupid, nor them :) [09:44] Oh, you're whistling in the dark, there. I stand by my conviction that pretty much everybody in the world _is_ stupid :) [09:45] fullermd: this may be true but is unrelated :) [09:45] or is it in a self-referring way ??? [09:45] commits/developers=iq [09:46] Oh, no. I'm a genius. Everybody else is a moron. The fact that you don't immediately recognize my brilliance simply proves the point ;) [09:46] fullermd: ooops, just realized my remark was ambiguous :) I meant: are you calling people stupid by looking at their code ? [09:47] Oh, no. I don't have to look at code. I assume _everybody_ is stupid. [09:47] fullermd: hmmm, you remind me of someone...just can't remember who... === grimboy [n=grimboy@85-211-243-222.dsl.pipex.com] has joined #bzr [09:52] What, somebody else has attained my exhalted level?? Never! We'll joust for the title! === igc dinner [10:11] spiv, can i read about the protocol yet? [10:11] poolie: Yeah, I sent a merge/rfc about it. [10:11] oh great, thanks [10:12] spiv, can you look at http://bundlebuggy.aaronbentley.com/request/%3C46D86283.4080602@utoronto.ca%3E [10:13] actually, i see a bug, but if you can say if the basic intent is right that'd be good [10:13] Yeah, that's high on my mental todo list. Like Robert I'll need to page in a little bit too, but not as much as Robert... [10:17] ok, don't worry til your stuff is up [10:17] i can read it === gabe_ [n=gabriel@91.84.56.254] has joined #bzr === mrevell [n=matthew@canonical/launchpad/mrevell] has joined #bzr === fog [n=fog@debian/developer/fog] has joined #bzr === GaryvdM [n=chatzill@mtngprs5.mtn.co.za] has joined #bzr === asabil [n=asabil@62.70.2.252] has joined #bzr === mrevell_ [n=matthew@82-47-122-108.cable.ubr05.wolv.blueyonder.co.uk] has joined #bzr === Zindar [n=erik@stockholm.ardendo.se] has joined #bzr [11:00] New bug: #136952 in bzr "Bzr doesn't merge the most recent revision" [Undecided,New] https://launchpad.net/bugs/136952 [11:31] spiv, is http://bundlebuggy.aaronbentley.com/request/%3C20070826091222.GC11127@steerpike.home.puzzling.org%3E [11:31] the most current fix for that bug? [11:31] for trunk [11:31] poolie: yes [11:31] thanks [11:31] igc, thanks for all the reviews [11:32] np === ipkiss_ [i=ipkiss@nat/ecp/x-0fa243067226cbc6] has joined #bzr === BrianB04 [n=bbommari@c-69-136-128-216.hsd1.mi.comcast.net] has joined #bzr [12:27] Morning all. [12:33] morning BrianB04 [12:33] Morning, Bri. Doing a checkout or branch of a branch I've just pushed I get the error bzr: ERROR: No such file: 'http://code.discussium.org/discussium/.bzr/repository/knits/8f/models.py.old-20070902211246-zblkha1c6hz8yag7-30.kndx'. The file is available where I pushed from put not where I pushed to. I've tried using both sftp and bzr+ssh but both do the same thing. Any idea what I'm doing wrong? [12:34] s/put/but/ === Kamping_Kaiser [n=kgoetz@gnewsense/friend/kgoetz] has joined #bzr [12:46] is bzr still compatible with the 0.8.2 in Ubuntu 6.06? [12:47] seems fine for me [12:47] i'm on dapper [12:47] i was just making sure there hasnt been any storage format breaks [12:47] Kamping_Kaiser: how do you mean, "compatible". whether branches created with current versions can be read by 0.8? [12:48] dato, and vica versa [12:48] as will be the case [12:48] vice versa, yes, always. [12:48] branches created by the default format up to 0.90 can be read by 0.8 as well. [12:49] however 0.15 and onwards have a newer format that is incompatible with 0.8, but it has to be enabled by hand. [12:49] finally, 0.91 will make that new format the default. [12:50] (but you can still create branches in the old format with 0.91 and upwards; you just need to pass the appropriate flag to bzr init) [12:50] would the version of bzr in debian 4.0 or ubuntu 7.04 be compatible? i'm asuming so [12:51] the very same comments apply. [12:51] sweet [12:51] *goes to find out versions in said distro releases* [12:51] debian 4.0 has 0.11 [12:51] I'm back, sorry about that, quick shower. Ya know, I offically love Bazaar...it's so simple once you get an idea of how things work. [12:52] Kamping_Kaiser: in any case, there are backports for both debian (in backports.org) and for ubuntu (in bazaar-vcs.org/releases/debs) [12:52] Kamping_Kaiser: in case you're interested [12:52] 0.15 in feisty [12:52] dato, i'll bear it in mind, thanks [12:53] Otherwise Kamping_Kaiser: Why not just grab the source from the bazaar site? [12:53] i just init'd a project before i came and asked here [12:53] BrianB04, what, build it myself? [12:54] Kamping_Kaiser: Yea, not that difficult. And, you can do a quick google search for something like 'build bzr in x distro' and usually will find (Especially for debian/ubuntu) howtos of exactly what you need to apt-get to make it build properly. [12:54] BrianB04: well, why build yourself if both distros provide updated backports?? === sverrej_ [n=sverrej@213.236.208.247] has joined #bzr [12:54] BrianB04, i prefer not to build (esp. if thers backporst) [12:56] dato: Unfortunetly, they are not always updated, that's the big problem. You know what I always found a little weird, when I was first looking into bazaar, that Ubuntu does not keep the most up to date in repos...and they are 'owned' by Canonical who does Bazaar. [12:56] BrianB04: what "repos"? [12:57] In one of the main not like Backports, ya know? [12:57] BrianB04: latest versions have always been in bazaar-vcs.org/releases/debs, ttbomk [12:58] you'd have to ask some ubuntu person why they are in bazaar-vcs.org instead of feisty-backports, eg. [12:58] Ah, I haven't been in Ubuntu in awhile...stupid computer now doesn't like Ubuntu, in the least. [12:58] the -backports repos are pulled from a later release, by someone in the backports team with motivation [12:58] i asume the bzr-cvs ones are done as a mater of course [01:00] But, I'm happy that finally launchpad mirrored my bazaar repo after the race condition yesterday. Hey, I have a trivia question regarding bazaar/drcs if someone knows, when did the whole DRCS thing start? Back when Bitkeeper came in to being to 'help' out the kernel team, or did DRCS start before then? === Zindar_ [n=erik@stockholm.ardendo.se] has joined #bzr === Zindar_ [n=erik@stockholm.ardendo.se] has joined #bzr === mrevell_ is now known as mrevell-lunch === Zindar [n=erik@stockholm.ardendo.se] has joined #bzr === asabil [n=asabil@62.70.2.252] has joined #bzr === phanatic [n=phanatic@3e70d9e7.adsl.enternet.hu] has joined #bzr === grimeboy [n=grimboy@85-211-248-129.dsl.pipex.com] has joined #bzr === Zindar [n=erik@stockholm.ardendo.se] has joined #bzr === Zindar_ [n=erik@stockholm.ardendo.se] has joined #bzr === AfC [n=andrew@office.syd.operationaldynamics.com] has joined #bzr === Zindar [n=erik@stockholm.ardendo.se] has joined #bzr === phanatic [n=phanatic@3e70d9e7.adsl.enternet.hu] has joined #bzr === grimboy_uk [n=grimboy@85.211.236.165] has joined #bzr === mrevell-lunch is now known as mrevell === deadwill [n=deadwill@146037.fln.virtua.com.br] has joined #bzr [02:22] When doing a checkout or branch of a branch I've just pushed I get the error bzr: ERROR: No such file: '*blah*/.bzr/repository/knits/8f/models.py.old-20070902211246-zblkha1c6hz8yag7-30.kndx'. The file is available where I pushed from but not where I pushed to. I've tried using both sftp and bzr+ssh but both do the same thing. Any ideas what I'm doing wrong? === luks [i=lukas@unaffiliated/luks] has joined #bzr === Demitar [n=demitar@PC96-180.oru.se] has joined #bzr === niemeyer [n=niemeyer@200-103-134-216.ctame705.dsl.brasiltelecom.net.br] has joined #bzr === markvandenborre [n=mark@ubuntu/member/markvandenborre] has joined #bzr === allenap [n=allenap@212.233.37.68] has joined #bzr [02:32] I'm setting up a central bzr repository for two people [02:32] how do I avoid having to fiddle with that repo as root? [02:33] we are two people, each with our own ssh account on this machine [02:33] markvandenborre: ensure both people are the members of a same group [02:34] gabe_, yes, of course,... [02:34] and that group has write permissions on the repository [02:34] but then you still need to set the default group for newly created files [02:34] with umask-ish stuff [02:34] I don't see if that is possible on a directory basis [02:35] or rather: how that is possible [02:35] ensure that the directory is mode g+s and g+w [02:35] (numeric mode 2775) [02:35] bzr *should* take care of the rest, or so I hear === Zindar [n=erik@stockholm.ardendo.se] has joined #bzr === bac [n=bac@canonical/launchpad/bac] has joined #bzr [02:36] works for me with the users being in the same group [02:47] 02755 and umask 0002 worked for us [02:50] grimboy_uk: are you using http to pull from ? === Zindar_ [n=erik@stockholm.ardendo.se] has joined #bzr [02:59] Hey, are bzr branches cheap? [03:03] Short answer: yes === mw|out [n=mw@189.146.15.187] has joined #bzr === sabdfl [i=sabdfl@ubuntu/member/pdpc.silver.sabdfl] has joined #bzr === deadwill is now known as xxxxx1 === hdima [n=hdima@idealer.cust.smartspb.net] has joined #bzr [03:30] BrianB04: Even cheaper if you have them in one repo [03:31] Of course, more to the point, they're real branches :) === AndyP_ [n=andyp@cpc3-cwma2-0-0-cust15.swan.cable.ntl.com] has joined #bzr [03:37] God, I hate going outside of stories when developing in rails, but...blech I have to for this. [03:42] dato, bzr commit -m "Test met gebruiker Onno" [03:42] Password: [03:42] bzr: ERROR: Permission denied: u'/srv/bzr/.bzr/repository/lock/pending.62hc7mnjpa6jcyrq91v1.tmp': [Errno 13] Permission denied [03:44] I'm still locked to this one user "mark" [03:45] I know I could chgrp -R admin ./ in /srv/bzr [03:45] (both users are in the admin group- [03:45] ) [03:45] but that would not be the cleanest way to do it, would it [03:46] what is the cleanest way when it comes to permissions [03:47] markvandenborre: find /srv/bzr -type d -print0 | xargs -r0 chmod 2755 [03:47] markvandenborre: find /srv/bzr -not -type d -print0 | xargs -r0 chmod 664 [03:47] do that and try [03:49] you make me change all directory rights g+ws, and all file rights ug=rw,o=r [03:50] aha [03:50] would that be the cleanest way? [03:50] I wonder if this is such an uncommon setup [03:50] that I have to fiddle with it like this... [03:51] (btw, thx for your help, dato!) [03:51] well, maybe the permissions were bad, to this should be a one time thing === asak [n=alexis@201-13-111-178.dsl.telesp.net.br] has joined #bzr === xxxxx1 is now known as deadwill [03:58] dato, the problem is that mark.mark is still the user/group rights on many files, so onno can't touch them [03:59] (after setting up the repo with g+ws as you first suggested) [03:59] ah, then if you don't have root there, you will need mark to fix [03:59] I have root here [03:59] but I was wondering how to fix this in a sustainable way [03:59] so that mark and onno can work together without touching anything at the shell level once it is set up well [04:00] presuming they stay within an existing repository, that is [04:01] as I understand it, the starting point is (1) all files and directories g+w; (2) all directories g+s; (3) all files and directories group "admin" [04:01] AfC mentioned something about the umask, but I've hear jam say bzr preserves the g+w bit, so it should not be needed [04:02] ok [04:02] how documented is this? [04:03] I don't know. [04:04] (group whatever-you-want-it-to-be) [04:08] lifeless, Yes. === mw|out is now known as mw [04:11] But I've looked at it on the server through the file system and the file that's on my computer that it's complaining about not having (*blah*/.bzr/repository/knits/8f/models.py.old-20070902211246-zblkha1c6hz8yag7-30.kndx) isn't there. === grimeboy [n=grimboy@85.211.238.235] has joined #bzr [04:28] I have this bzr with central workflow running now, as described at http://doc.bazaar-vcs.org/latest/en/user-guide/centralized_workflow.html [04:28] thx, step 1 is complete === Demitar [n=demitar@c-212-031-190-120.cust.broadway.se] has joined #bzr === hsn_ [n=radim@234.114.broadband5.iol.cz] has joined #bzr === sverrej [n=sverrej@pat-tdc.opera.com] has joined #bzr === BleSS [n=BleSS@13.Red-88-27-146.staticIP.rima-tde.net] has joined #bzr [04:52] niemeyer: hi! I contacted with you ago 2 weeks about issues on python-mcrypt and python-mhash, and I sent you an email but withou answer [04:54] and you said me that you were to looking/working about them on past week, I would to know if you aren't maintain those projects netiher upload to PyPi [04:54] because I started to built a python wrapper over your programs for nothing [05:06] BleSS: First, this isn't the right channel to talk about it.. [05:06] BleSS: Second, I said I wouldn't be able to look at these projects before the sprint was over.. it didn't mean I would look at them immediately after the sprint was over [05:07] niemeyer: yes, it's true, sorry, but as I was not answered by email after of 3 emails ... [05:07] BleSS: I have dozens of things to look at, literally, and these projects aren't at the top of my list. [05:07] niemeyer: excuse me but you said me that you were to looking them on the last week [05:07] BleSS: I appreciate your effort on them, and don't want you to feel frustrated because I'm not giving you attention [05:08] niemeyer: then, for the next time you must say the truth and answer the emails === BleSS [n=BleSS@13.Red-88-27-146.staticIP.rima-tde.net] has left #bzr ["Konversation] === p4tux [n=p4tux@189.169.92.184] has joined #bzr [05:11] a strange beginner question: [05:11] I want to use bzr for web development [05:12] generally one uses it to manage revisions ;-) [05:12] ... [05:12] Aug 21 11:02:02 So I apologize for the lack of response [05:12] Aug 21 11:02:08 no problem [05:12] Aug 21 11:02:19 Ok.. I'll try to look at these issues next week [05:12] Aug 21 11:02:23 if you're busy i don't disturb [05:12] Harsh.. harsh.. [05:13] !? [05:13] radix, for managing revisions of web development files of course [05:13] radix: Discussion above.. [05:14] wow [05:14] markvandenborre: oh, ok :-) [05:14] but how do I get the clean source tree [05:14] without any .bzr stuff [05:15] so that I can use a checkout directly in my web tree? [05:15] I'm probably not expressing myself too correctly here [05:15] well, 'bzr export' will do that [05:16] but i'm not sure that's what you actually want [05:16] ah, thx [05:16] mwhudson, now I can at least look things up [05:16] export is a one-time operation, so you won't be able to use "pull" or "update" in that directory. [05:17] But "pull" and "update" require a .bzr directory, even if it doesn't have a lot in it. [05:18] I'm not sure why you want to avoid ".bzr". === abadger1999 [n=abadger1@65.78.187.68] has joined #bzr [05:24] ls === rotty` [n=user@81.223.119.66] has joined #bzr === Zindar [n=erik@stockholm.ardendo.se] has joined #bzr [05:45] I don't think that a webserver could even see a .bzr directory. [05:46] abentley, I wonder if this has any security implications [05:47] BrianB04: They typically don't show it on directory listings, but yes, you can access a .bzr over http. If not, most public branches wouldn't work. [05:48] abentley: Yes, that's true but how many people are just going to try that? [05:48] markvandenborre: Well, you can always make .bzr/* a forbidden URL in your server config. But you certainly don't need to store all the version history there, anyhow. You can make a lightweight checkout instead. === sverrej [n=sverrej@pat-tdc.opera.com] has joined #bzr [05:59] abentley, ahh... another good thing you bring up [05:59] a lightweight checkout === sverrej [n=sverrej@pat-tdc.opera.com] has joined #bzr [06:03] what is the fastest operation: lightweight checkout, or export? [06:05] think of a web site in development that needs to be updated quite frequently from a bzr repository [06:05] maybe there is a better/faster way? === nicodaemos [n=user@ip68-100-80-47.dc.dc.cox.net] has joined #bzr [06:09] ... any good doc pointers pertaining to this also welcome [06:09] ! [06:15] New bug: #137044 in bzr "Saved FTP passwords not used, password not prompted" [Undecided,New] https://launchpad.net/bugs/137044 [06:15] New bug: #137045 in bzr "bzr push hangs some minutes if server data quote is exceeded" [Undecided,New] https://launchpad.net/bugs/137045 [06:22] a bzr update from a remote sftp server (pubkey auth) where nothing has changed consistently takes about nine seconds [06:22] is that normal? [06:22] this is on bzr 0.15-0ubuntu2 === cypherbios [n=cyr@ubuntu/member/cypherbios] has joined #bzr [06:25] markvandenborre: Step 1: upgrade to the current release, 0.90 [06:26] markvandenborre: you are using code that is more than 4 releases old. [06:26] AfC, or from another perspective, I'm using the latest ubuntu on a production server... [06:26] markvandenborre: well. then that's an Ubuntu bug, then. [06:27] maybe there is something more recent in a backports repo somewhere [06:27] markvandenborre: yes, the latest bzr packages for ubuntu are made available [06:27] oh, nice [06:27] you'll find info in the download section of bazaar-vcs.org [06:28] thx! [06:28] radix, brilliant! === sits [n=sits@cpc3-cwma2-0-0-cust739.swan.cable.ntl.com] has joined #bzr [06:29] I seem to be getting KeyError errors trying to do [06:29] bzr branch 'https://code.launchpad.net/~asac/intellinuxwireless/ipw3945.asac' [06:29] on Gutsy. Any ideas? === ionstorm [n=ion@70-58-119-250.phnx.qwest.net] has joined #bzr === grimeboy [n=grimboy@85-211-251-88.dsl.pipex.com] has joined #bzr [06:36] AfC, regarding performance [06:36] I have just upgraded to the latest .90 release (thx again for the suggestion!) [06:37] averages for a bzr update from a central repo with one very short text file and three revisions is just below 6 seconds on average now [06:37] is there anything else I should check regarding performance? [06:38] oh, I still need to bzr upgrade, apparently [06:39] any other suggestions [06:39] ? [06:43] markvandenborre: I expect that updating a checkout is faster than updating an export, because updating a checkout will only affect modified files. But updating an export requires outputting all files each time. [06:44] abentley, this is a checkout already, but thanks for the suggestion [06:45] You asked for a comparison earlier. I was responding to that. [06:45] ah, thx! [06:46] sits: Please pastebin your traceback. [06:46] ubtotu: paste [06:46] ubotu: paste [06:46] pastebin is a service to post large texts so you don't flood the channel. The Ubuntu pastebin is at http://paste.ubuntu-nl.org (make sure you give us the URL for your paste - see also the #ubuntu channel topic) === cnus8n [n=cnu@122.164.151.137] has joined #bzr [06:50] markvandenborre: The repository is remote? [06:57] http://paste.ubuntu-nl.org/36208/ === ddaa [n=david@canonical/launchpad/ddaa] has joined #bzr [07:15] abentley, yes, the repo is remote [07:16] oh... too late === ddaa [n=david@canonical/launchpad/ddaa] has joined #bzr [07:52] hello [07:52] I am still trying to get my complete workflow of development flowing with launchpad. [07:53] I beleive I reach one of the final step of the loop. I am trying to push my branch from a remote host to launchpad.net.I am getting this error message:yml@ssh1:~/workspace$ bzr push "sftp://yml-nospam@bazaar.launchpad.net/~yml-nospam/survey/main-yui"Could not create directory '/home/yml/.ssh'.Permission denied (publickey).bzr: ERROR: Unable to connect to SSH host bazaar.launchpad.net; [07:53] Does this make sense to someone? [08:01] "sftp yml-nospam@bazaar.launchpad.net" works for you? [08:01] I think it's something wrong without your local ssh key setup [08:01] yml, I'm not a bzr expert, but you should probably get your pubkey auth fixed first [08:03] make sure .to add the contents of your local ~/.ssh/id_dsa.pub to the remote ssh/authorized_keys2 [08:03] lucks you want me to type this: sftp yml-nospam@bazaar.launchpad.net [08:03] make sure to have pubkey auth switched on in the remote sshd configuration [08:03] yml: yes [08:03] I think you don't have your private ssh key installed correctly === asak [n=alexis@201-26-119-50.dsl.telesp.net.br] has joined #bzr [08:05] luks : all the problems come from that my key are not in /home/yml/.ssh but in /home/yml/www/.ssh [08:06] luks : same kind of error: [08:06] yml@ssh1:~/workspace$ sftp yml-nospam@bazaar.launchpad.netConnecting to bazaar.launchpad.net...Could not create directory '/home/yml/.ssh'.Permission denied (publickey).Couldn't read packet: Connection reset by peer [08:07] what would be the best way to backup a central bazaar repository? [08:07] when I do a ssh-add -l I can see my key [08:08] markvandenborre: with multiple branches? [08:08] yml: it probably needs to write to known_hosts in ~/.ssh === asak_ [n=alexis@201-26-116-104.dsl.telesp.net.br] has joined #bzr [08:08] luks: :) [08:08] yml: ssh -v can be helpful sometimes. [08:08] hm? === asak_ is now known as asak [08:09] james_w, I'm really a beginner when it comes to bzr, but... [08:09] we're two users working on one central repository from different computers [08:09] This took me a day to set up ssh to write known_hosts in the correct directory [08:09] with several branches in this same repository [08:10] one for each web project [08:10] http://forum.alwaysdata.com/viewtopic.php?id=93 [08:10] at least, that's the layout that was suggested to me as the most logical one [08:10] markvandenborre: ok, so for backup, either use bzr and pull each branch in turn, to a repo on another machine. Or just rsync the whole repo over or similar. [08:12] luks: here it is the output of sftp -v => http://dpaste.com/18500/ [08:12] james_w, which one would be most bandwidth efficient? [08:12] well, it obviously doesn't try to use ~/www/.ssh [08:12] not that it's such a big problem right now, but I want things to be scalable [08:13] but I really don't know how to fix that [08:14] markvandenborre: rsync, unless you have masses of unreferenced revisions in the repository (you often uncommit revsions that are stored there or similar). [08:14] luks : thank you, I am like you but me I searching the solution for the last 2 days [08:14] :[ [08:14] james_w, thx! [08:14] why not just use ~/.ssh? [08:14]