[00:04] glyph: i don't see it there [00:04] igc, hi === lifeless_ is now known as lifeless === TheMuso_ is now known as TheMuso [00:38] jam: I think you should land your gc change [00:39] jam: I haven't fully reviewed, but its definitely conceptually fine [01:06] is there a way to, instead of unshelved changes, commit shelved changes only? [01:09] RaceCondition: shelve you current changes, unsehlve the ones you want to commit, commit. ? [01:09] lifeless: um, yeah, but you didn't answer my questio [01:10] is it possible or not to commit shelved changes [01:10] smth like bzr commit -m "msg" --shelved [01:11] apparently not, though, google gives me nothing on this [01:12] no there is no direct way to do this today [01:15] Random observation: bzrlib.errors.AmbiguousBase has been deprecated since 0.8 [01:15] We should delete it... [01:28] spiv, i have a branch outstanding that removes lots of old code [01:28] i have review comments from robert still to do === ampelbein is now known as Ampelbein [02:16] lifeless: streaming or the change to the delta_index code? [02:19] thumper: pong [02:20] abentley: I was wanting to talk to you about the bzr sprint at uds [02:20] thumper: sure thing. [02:21] thumper: did you mean on skype? [02:22] abentley: :) yes [02:31] * igc lunch === abentley1 is now known as abentley [03:13] jam: both === abentley1 is now known as abentley === Ampelbein is now known as ampelbein [04:24] poolie: what do we need to do to kick the backport effort in ubuntu? [04:26] james_w said something in bne about driving it [04:27] but he's on holiday until monday [04:27] bne? [04:27] nm [04:27] friday afternoon and I'm knackered [04:29] content filtering patch submitted to pqm [04:29] * igc off to hospital for the rest of the day [04:29] have a good weekend all [04:36] igc: good luck [04:38] bzr push needs some better error messages [04:39] "bzr push lp:~maco.m/seahorse-plugins" tells me that ~maco.m isnt a valid project name instead of telling me i need a branch name on the end of it [04:39] maybe this is launchpad-specific though....? should i bug them instead? [04:44] maco: its launchpad specific [04:44] ok ill go bug them [04:44] :) [06:06] idea: [06:07] maybe we could take all these people who like bikeshedding [06:07] and rent them out to actual power plants that need their bikesheds painted? [06:07] strictly one per shed [06:07] hopefully with big bikesheds [06:08] mm === r0bby_ is now known as r0bby [06:50] kfogel: don't you sleep? :) [06:51] poolie: long story :-) [06:51] poolie: I'm actually an early-to-bed person, but... sigh, something came up, so here I ma. [06:51] am [06:56] hi all [06:56] hi vila [06:57] hello vila [06:58] readjusted to europe? [06:58] poolie: fully :-) [06:58] I even add a ~2hours protest under my windows yesterday :) [06:59] s/add/had/ [06:59] not specifically targeted at me of course... [07:00] heh [07:00] not even at slow push to 1.13? :) [07:01] not even :-) But some wanted a faster selftest though... :-P [07:01] vila: you begged :P [07:01] vila: and we have now [07:02] lifeless: it rocks ! I toyed a bit yesterday evening trying to spawn 256/2048 processes instead of just 8 and obvisouly the kernel just can't handle that (I have plenty of memory so no problem from that side) [07:03] vila: :P [07:03] vila: its fixable [07:03] lol [07:03] Possibly stupid question: How does doing BzrDir.find_branches() on a local transport wind up returning remote branches? [07:03] its just in the wrong spot, the ec2 version has it moved to run() [07:03] Peng_: branch references [07:04] lifeless: spawning the processes you mean ? [07:04] yes [07:04] lifeless: Okay. [07:04] I wonder where I have one of those? [07:04] Oh, I remember. [07:04] lifeless: diff available somewhere ? [07:05] vila: no :P but the branch I put up has a new snapshot [07:05] vila: remember that none of this history will be merged, its all noise - I'm cutting and pasting bits for the relevant projects [07:08] poolie: 7m30 or so with 5 instances [07:08] though there are still, uhm, glitches [07:10] lifeless: branch url ? And yes, I understand we don't care about history (though I'm a bit surprised we make an exception there ;-P) [07:10] tests.parallel [07:12] lifeless: got it [07:12] Peng_, would you be interested in coming to this bzr sprint at all? [07:12] robert suggested at least putting you on the list [07:14] lifeless: wow, of course I should ignore all that ec2 related stuff [07:15] lifeless: I'll manage, back to test_breakin [07:17] ok, i think that's enough [07:20] ciao [07:21] have a nice week-end ! [07:25] Hi! Odd question perhaps, are there any free project hosting for free projects (like launchpad) that use bzr? [07:25] (except launchpad, ofcourse) [07:26] Sourceforge.net [07:26] sourceforge, savannah, any web hosting [07:26] They do? [07:26] Savannah is using bzr these days? [07:30] hmm is this an important error? bzr: ERROR (ignored): The medium '' has reached its concurrent request limit. Be sure to finish_writing and finish_reading on the currently open request. [07:30] I can't seem to get through this push, it just stalls at walking content, though if I control+c that is what I get [07:30] mrooney: it's typically a knock-on effect of some other error [07:31] it's better in later versions [07:31] cheerio [07:31] poolie: how many later versions are there than 1.13~rc1-1build1 ?! [07:31] not many :) [07:31] hm I can't seem to push, alas [07:32] it just sticks on walking content [07:32] mrooney: if it's reproducible please do control-backslash [07:32] which should put you in a debugger then type 'bt' [07:32] yes it does seem to be [07:32] and then put that in a bug and show vila :) [07:33] cause unfortunately i have to go [07:33] hm okay well here it is for any other eyes http://paste2.org/p/167921 [07:33] I really need to go also [07:33] I just wanted to push this code so someone else could work on it [07:33] I guess not :/ [07:33] poolie: lol [07:33] mrooney: looking [07:33] vila: thanks :) [07:34] mrooney: ok, so, hpss requests shouldn't interrupted as they don't know how to restart, instead you should use -Dhpss and look at .bzr.log [07:36] you can even add 'debug_flags = hpss' in bazaar.conf [07:36] it will always just get stuck at some random walking content number [07:36] mrooney: we need to look at that 'random' :-) [07:36] but first, [07:37] so where should that log be? [07:37] where are you pushing to ? What format is used there, are you stacking ? [07:37] I have no idea :) I just tried to push to a fresh branch [07:37] "bzr push lp:~mrooney/do-plugins/skreemr-plugin" [07:37] mrooney: 'bzr version' will tell you where the .bzr.log file resides [07:39] Hey, I can't find any evidence at all that sourceforge or savannah is using bazaar, any link to docs explaining how to use it? [07:40] vila: http://paste2.org/p/167923 [07:40] the top part is the .bzr.log part, the bottom is where I am stuck [07:40] http://bzr.savannah.gnu.org/ [07:40] mrooney: wow, wow, what bzr version are you using ? [07:40] for small values of using [07:40] yes indeed [07:41] 1.13~rc1-1build1 [07:41] There's nothing in the user guide nor http://savannah.gnu.org/userguide/ [07:41] jaunty [07:41] and the faq is lacking bzr commentary [07:42] You think it's a good idea to set public_branch on all of your, well, public branches on the server? [07:42] mrooney: What 'bzr info -v' shows in your local branch ? [07:42] The menus include git, cvs, svn and arch, no bzr [07:42] It's a bit redundant.. [07:43] vila: http://paste2.org/p/167924 [07:43] vila: thanks for helping me with this by the way :) [07:43] hopefully I can get this up [07:46] mrooney: hmm, assuming you put 'debug_flags = hpss' in bazaar.conf, can you try deleting the branch and pushing again ? [07:46] oh I didn't let me do that [07:47] mrooney: I suspect a stacking problem but upgrading all do-plugins branches to 1.9 may not be an option :-/ [07:48] mrooney: I can't parse "I didn't let me do that", surely you can be gentle with you and authorize yourself to delete a branch no ? ;-P [07:48] haha [07:48] "I didn't, let me do that" [07:48] now I am getting tons of output in the log [07:48] after doing that [07:50] vila: http://paste2.org/p/167927 [07:50] it does that forever on and on [07:51] mrooney: on purpose, that's a known bug, you're using a slow code path :-( [07:51] for excessive values of slow :( [07:51] vila: how long will it take? [07:53] mrooney: the main factor is your ping time for lp, with ~20ms I found it hardly tolerable, above that, well, it depends on whether you are patient or very patient :-/ [07:53] ~170 on average here [07:53] (bazaaar.launchpad.net) [07:54] I think lifeless just posted a patch against bzr.dev to address situations like yours (and spiv already posted one for some of them last week), it's definitively high on the list to have that bug fixed [07:54] so what is my situation though [07:54] all I did was branch from lp and push [07:54] what is special about it? [07:55] mrooney: nothing, that's the bug :) [07:55] hm okay haha [07:55] I'll guess I'll burn through some kilowatts and leave my computer on overnight [07:56] mrooney: hmm, just checked, lifeless patch hasn't landed yet [07:56] mrooney: if that's an option, go for it and let us know how it ends up :-/ [07:56] eh I guess I will try pushing tomorrow at work on a better connection [07:57] mrooney: the laternative will be to update all the do-plugins branches to format 1.9 which doesn't suffer from this bug [07:57] but I have 1Mb up, I guess the ping is bad [07:57] how do I do that? [07:57] 'bzr upgrade lp:do-plugins --format 1.9' for all branches [07:58] can I do it on just mine? [07:59] mrooney: possibly, but if stacking is enabled on lp for do-plugins, I'm not sure this will avoid the bug... It may be faster to try though [07:59] it will be faster to give up and sleep [07:59] :) [07:59] thanks for your help though [07:59] mrooney: sure, sorry about that :-/ [07:59] I will hope this magically works tomorrow or something [08:02] mrooney: things should be better once the initial push suceeds... [08:02] all I need is the initial push :) [08:02] it is only for review so it can be merged haha [08:02] as I don't have permission to push elsewhere [08:04] mrooney: hmm, looks like lifeless patch landed after all (BB didn't acknowledged it yet, but it's in bzr.dev), so you may want to try that too (please report if you do) [08:05] bzr: 1 me: 0 [08:05] I'll try to even the score tomorrow :) [08:05] good night thanks for your help! [08:05] mrooney: you're welcome [08:06] ps I upgraded the remote branch and my local although it didn't seem to fix it, I suppose your stacking suspicion was correct [08:07] mrooney: which remote one ? [08:07] ~mrooney/do-plugins/skreemr-plugin [08:07] the unpushed to one [08:08] I don't know if that actually does anything but it took about 10 minutes so I presume it does [08:08] I'm surprised you can update it if it's not pushed to yet... what does .bzr.log says ? [08:10] vila: http://paste2.org/p/167940 [08:10] apparently it took only 3 minutes [08:10] mrooney: hmm, sounds good, what does bzr push reports now ? [08:11] still hanging out at walking content [08:11] last thing in the log there is 8.569 fetch up to rev {mrooney@ubuntu.com-20090320073443-2g8kssdqgnwhyfnw} [08:12] well, so indeed, you may need bzr.dev (sorry about the trials, I don't have all the combinations clearly in head) [08:13] Another possibly-stupid question: What if I want to read from a branch and conditionally write to it? Should I always take out a write lock? Can I take out a read lock and "upgrade" it to a write lock if necessary? [09:35] * Peng_ wonders why downloading the most recent revision of bzr.dev over http took 1.5 minutes and ~3.7 MB of bandwidth [09:35] It's 14 lines of changes! [10:07] beuno: https://edge.launchpad.net/%7Ebzr-beta-ppa/+archive/ppa/+sourcepub/530792/+listing-archive-extra [10:45] jam: thanks, uploaded [13:30] LarstiQ, hi. So I should install bzr-svn from that PPA? [13:32] hi hi [13:34] beuno: either that or download the deb from there === ampelbein is now known as Ampelbein === Ampelbein is now known as ampelbein === ampelbein is now known as goodkarma === goodkarma is now known as Ampelbein [14:50] LarstiQ, installing bzr-svn works great [14:50] would you like me to use it in any way? === nevans1 is now known as nevans [15:12] I just shelved some changes using bzr 1.13 which included adding some files and now when it goes to unshelve them it gives me this error: bzr: ERROR: No such file: None [15:13] any way to fix that? === Ampelbein is now known as ampelbein [15:23] beuno: I wouldn't object to that :) I'm reasonably sure that if it gets through the phase where debian/control matters, that the actual code itself works. [15:24] LarstiQ, so I should just try and check out an svn branch with bzr? [15:24] got any handy? :) [15:25] beuno: http://svn.dojotoolkit.org/src/dojo/trunk [15:25] beuno: stolen from subvertpy examples: svn://svn.gnome.org/svn/gnome-specimen/trunk [15:27] fetching.... [15:27] so, does anyone know what's going on with bzr unshelve? [15:27] malbisetti@pentaserv:~$ bzr co svn://svn.gnome.org/svn/gnome-specimen/trunk test_svn [15:27] Initialising Subversion metadata cache in /home/malbisetti/.bazaar/svn-cache/203ae883-c723-44c9-aabd-cb56e4f81c9a [15:27] Upgrade to Subversion 1.5 or higher for faster retrieving of revision properties. [15:27] mxpxpod, maybe you're mixing shelve and shelve2? [15:27] mxpxpod: in what sense? [15:28] ah, you pasted something above [15:28] :) [15:28] beuno: nope, I did bzr shelve and then bzr unshelve [15:28] mxpxpod: doesn't look familiar to me, did you check the bugs page in launchpad? [15:28] yeah, looking now [15:29] I could swear I've seen this before... but I don't remember the fix [15:29] mxpxpod: there have been various shelve fixes the past releases [15:30] LarstiQ: yeah, I figured... I'm using 1.13 [15:31] and I need these files :( [15:31] mxpxpod: so if you trigger something in 1.13, either it's something new, something regressed, or newly exposed [15:31] frick [15:31] mxpxpod: we should be able to help you get your files back [15:32] mxpxpod: but it would be easier if this was a known problem [15:32] LarstiQ: fun ;) [15:33] the other problem is that I can't give out the shelf file because the files are internal to my company [15:33] that's fine [15:33] do you want me to paste the bzr log somewhere? [15:34] LarstiQ, worked like a charm [15:35] LarstiQ: oh, the other thing is that I added a new directory to the shelf too [15:35] and there was a file in that directory [15:36] LarstiQ: hmm, it might be trying to add the file in the directory before adding the directory back [15:38] morning vila (I have a conference call right now, but we can chat after if you want) [15:38] jam: chat sounds good [15:39] LarstiQ: it's dying in line 546 of bzrlib/transform.py [15:45] LarstiQ: any clues? [15:53] mxpxpod: sorry, irl sidetracked me for a moment there [15:53] mxpxpod: your analysis sounds plausible [15:55] mxpxpod: with that sequence I get a different message [15:56] mxpxpod: could you cp -a your branch so we can look at the state as it was later again? [15:56] LarstiQ: huh? [15:56] mxpxpod: .bzr/checkout/shelf is where shelf has stored your files [15:57] mxpxpod: I'm intending to get your file out first, and do bugreporting later [15:58] vila: call has completed if you want to chat [15:58] LarstiQ: ok, so do you want a copy of my branch? [15:59] jam: sure [15:59] mxpxpod: no, I just want to make sure you have an extra copy that we're not going to touch [15:59] LarstiQ: or, just for me to make a copy for later [15:59] LarstiQ: gotcha [16:01] LarstiQ: making the copy now [16:05] LarstiQ: ok, done [16:06] mxpxpod: ok, `bzr shelve --list` only shows 1 shelve? [16:06] LarstiQ: yessir [16:07] and there's only one file in .bzr/checkout/shelf [16:09] mxpxpod: if you open that with an editor, do you see the contents of your file clearly? [16:09] LarstiQ: yeah [16:09] LarstiQ: but there are other changes in the file [16:09] jelmer: ping, can we bug you in #mercurial briefly? [16:14] has bzr merge --force changed somehow in 1.13? [16:16] LarstiQ: I guess I'll just have to apply all of those changes manually [16:16] mxpxpod: ok, let me try a couple of things [16:50] durin42: sure [16:56] BasicOSX: ping [16:58] jam: hiyah [16:59] hey, just checking the 1.13.1 release [16:59] It looks like you don't have the fix for the "bzr merge --force" regressino [16:59] which was an issue for some other people [16:59] Do you might getting that into 1.13.1 before we make it finalized? [16:59] sec [17:00] Anyone else having troulbe pushing to lp? [17:01] BasicOSX: "bzr.dev 4146" I'm happy to create a cherrypick and submit it to PQM as long as you are signed off on it [17:02] jam: I can squeeze it in :-) Looks like Vincent fixed my bzrtools bug [17:02] so I was going to re-start the release as well [17:02] cherry pick and PQM to the branch, I'll sign off on it [17:02] k [17:05] Eeep! I missed 1.14rc1 -and- 1.14final according to mbp post! [17:06] jpds: it seems to be working for me [17:06] did you try again? [17:07] BasicOSX: yep. though if you read further he really did mean April :) [17:07] I know, was just putting it in irc to tease [17:08] Shucks. There I was thinking I'd finally gotten a good, long sleep... [17:10] jam: Just made it. [17:10] BasicOSX: change is on its way to PQM now [17:10] Shall I ping you when I get the confirmation? [17:10] My lunch hour almost over, drop me email on it? [17:11] since I'm going to loose wifi when I leave the cafe and drop back to the office :-) (yes, I bring my laptop to lunch) [17:12] can an uncommit be pushed to other branches? [17:12] Tak: with 'bzr push --overwrite' [17:13] jam, BasicOSX : SHouldn't revno 4174 (bug #345169) be included in 1.13.1, it seems to address some pushing-to-lp-is-slooow bugs that some early 1.13.1 are experiencing [17:13] Launchpad bug 345169 in bzr "bzr push to a new lp branch of bzr from a local copy fails to stack" [Critical,New] https://launchpad.net/bugs/345169 [17:13] then what happens if I pull from a branch that already has the revision as well? [17:13] vila: it isn't a regression [17:14] "source is 0.92 branch 7" [17:14] vila: I asked on the ... nm, jam answering [17:14] I know :-/ [17:14] vila: not worthy of a 1.13.1 release [17:14] they would get the same from 1.12 [17:14] Tak: uncommit just rolls the pointer back, it doesn't mark it as rejected [17:14] so pulling from a branch that had it will bring it back [17:15] so what I really want is to unmerge that revision [17:15] Tak: bzr revert -r -2; bzr commit [17:15] bzr merge -r X..X-1 ; bzr commit [17:15] sorry [17:15] bzr merge . -r X..X-1 ; bzr commit [17:16] depending on whether you want to reject the last commit, or something older [17:16] (merge works in both cases, but revert is more obvious, IMO) [17:16] * Tak nods [17:16] thanks [17:20] hello, i have some problem to push to a branch today, it stops at [17:20] [| ] Transferring:Walking content. 1294/1423 [17:20] and when i stop it using ctrl-c, i got this error: http://paste.pocoo.org/show/108824/ [17:21] d6g: I don't think it stopped, it is still transferring, just not giving progress messages. [17:21] This would be with at least bzr1.13 to another bzr.1.13 host, right? [17:21] it's 1.3 and push to launchpad [17:22] 1.13 [17:22] bzr.dev is a little better in that you still get 'activity' indications on the bytes sent/received. [17:22] but how long am i supposed to wait, it seems just stuck in there [17:22] and the number 1294 seems random, sometimes larger/smaller [17:24] jam: i think you are right, i saw the upload speed now, it still is around 50kb/s, so i will probably have to wait, thx. [17:40] vila: no more apparent luck today, hm [18:04] So, if I used --stacked on a branch that doesn't support stacking, how well does it work? [18:05] It's currently telling me it's using 1.6, inside a 1.9 repo, and it's doing stuff that I presume is stacking (building tree") === ampelbein is now known as Ampelbein === abentley1 is now known as abentley === Ampelbein is now known as ampelbein === ampelbein is now known as Ampelbein [20:21] hey there, I'm getting a "Permission denied (publickey)." when trying to "bzr pull lp:~kiddo/specto/specto-jeff" .... what's up? [20:21] using bazaar 1.6 "bundled with intrepid" [20:23] Does anyone know if bazaar version 1.5.0 supports Launchpad? [20:24] nekohayo: probably logged in, and bzr pull lp:... tries to use bzr+ssh [20:25] for a pull? [20:25] but then I still have no idea what to do in that case [20:26] bzr launchpad-login === Ampelbein is now known as ampelbein [20:58] abentley: hi [20:58] jelmer: hi [20:58] abentley: What could cause a "Revision incompatible" error while merging a bundle? [20:59] jelmer: I guess going from rich-root to non-rich-root? [21:07] abentley: that was it, thanks! [21:10] asabil: returns "kiddo" [21:18] asabil: nevermind, I upgraded to bzr 1.13 and that fixed it [21:19] how can i get around error message from apt-get public key is not available when i am trying to access bzr repos? [21:20] hsn_, [21:20] https://edge.launchpad.net/~bzr/+archive/ppa [21:20] https://help.launchpad.net/Packaging/PPA#Adding%20a%20PPA%20to%20your%20Ubuntu%20repositories [21:25] beuno: thank you it works now [21:50] How do I change the push branch of a working copy that already has one? [21:51] push --remember [21:51] With version 1.3.1 that doesn't seem to do it [21:51] Oh :( [21:52] Yes it does, I just have a comprehension problem. [21:52] Thanks [21:52] Coffee helps with that ;) [21:52] Hmm yea.... === abentley1 is now known as abentley [23:39] vila: hi [23:39] vila: do you have a copy of tests.parallel with both our stuff in it?