[00:24] spiv: thanks. posted some mps for you to look over at your leisure. === oubiwann` is now known as oubiwann [06:39] spiv: hi [06:40] spiv: did you check for a branch.conf with %7E, or was it clearly stacking? [06:40] lifeless: there was a %7E in one branch.conf [06:40] spiv: the 11 second thing sounds suspiciously like sftp + branch locking + the url changing issue that broke checkouts [06:42] lifeless: but the stacked-on locations were definitely pointing to each other (modulo how the URL was escaped) [06:42] spiv: is that even possible, even with branch renames? [06:42] So maybe the %7E is a problem, but there also appears to be a stacking loop. [06:42] Which is surely a problem too :) [06:43] lifeless: I think so [06:43] lifeless: with changing the dev focus around and enough rename steps [06:46] See also , which features someone doing a complicated dance with dev focuses and renames (not sure why!) and ends up with a self-stacked branch. [06:47] lifeless: I agree it sounds simliar to that checkout issue too, although I haven't managed to dig up the relevant bug yet [06:47] kk [06:48] lifeless: I perhaps don't remember enough details, and I stopped looking for it when I saw the apparent mutual stacking. [06:48] the 'same branch' check looks for url string equality [06:48] a normalise call was either added/removed- I don't remember - on the lookup of something checkout related [06:49] it made 'bzr update' blow up [06:49] fullermd remembers the bug [06:53] Hmmwhut? [07:21] I don't recall ever being involved with any bugs on stacking... I have it on my mental "do not touch" list. [07:21] not stacking [07:21] bzr update and the %7E vs ~ thing [07:22] Hm. I vaguely remember hearing of such a thing, not sure I got anywhere near it. [07:22] * fullermd checks what LP has to say... [07:24] fullermd: last time this was discussed here, Ithought you piped up witht he bug # [07:24] perhaps it was peng [07:26] Hmmm... here's an ugliness about co's of co's with local vs remote paths: https://bugs.launchpad.net/bzr/+bug/325296 [07:26] Nothing about recursive livelocking though. [07:29] Unrelated, but on a bug gardening note: https://bugs.launchpad.net/bzr/+bug/582656 [07:30] Still showing a 'New' status on one of its product/effects/whatever's. Should it? [07:32] Annoying how LP shows the same bug multiple times (and widely separated) in its listout :| [07:35] thats the per context thing [07:35] there is a bug on it [07:35] it has a reasonable reason behind it, solvable with some good ui work === echo-are` is now known as echo-area [09:39] when i use this cmd [09:40] i got the following error [09:40] root@cdac[openstack]#bzr branch lp:nova [09:40] ssh: connect to host bazaar.launchpad.net port 22: Connection refused [09:40] bzr: ERROR: Connection closed: Unexpected end of message. Please check connectivity and permissions, and report a bug if problems persist. === hunger_ is now known as hunger [09:42] Manikandan: the service is up for me [09:43] Manikandan: you may have a firewall between you and bazaar.launchpad.net:22? [11:01] bzr branch lp:ubuntu/maverick/computer-janitor [11:01] Permission denied (publickey). [11:01] bzr: ERROR: Connection closed: Unexpected end of message. Please check connectivity and permissions, and report a bug if problems persist. [11:01] help me with this please [11:06] techbreak_: the SSH authentication is failing [11:06] spiv, what am I supposed to do ? [11:06] techbreak_: have you added your SSH public key to your Launchpad account? [11:06] spiv, yes [11:08] techbreak_: try 'ssh -v -l YOUR_LP_USERNAME bazaar.launchpad.net' and take a look at which keys it tries [11:09] spiv, http://paste.ubuntu.com/573882/ [11:10] Also, what's your launchpad username? I can take a look at your equivalent of https://launchpad.net/~spiv/+sshkeys and see if there's any really obvious problem. [11:12] Well, it's trying a key (/home/techbreak/.ssh/id_rsa), but it apparently doesn't match your publickey(s) on Launchpad. [11:13] Hi guys [11:14] Just wanted to say that I've just downloaded the PPA of the bazaar 2.4 and it is fantastic. It's so much zippier than the 2.2 I was using before. Keep up the good work. You have a fantastic codebase [11:14] ChrisCauser: thanks! :) [11:17] Spiv: No problem. I use bazaar everyday to integrate with a subversion repo and it does it much better than any other solution out there. I like how it made subversion faster even before I upgraded to 2.4! [11:31] spiv, so what am I supposed to do ? [11:32] techbreak_: Also, what's your launchpad username? I can take a look at your equivalent of https://launchpad.net/~spiv/+sshkeys and see if there's any really obvious problem. [11:33] spiv, gupta-chandan1 [11:33] techbreak_: but basically, as I said above, the SSH public key(s) you have imported into Launchpad don't match your local SSH key. [11:34] spiv, how am i suppose to import matching one then ? [11:34] :O [11:36] techbreak_: um [11:36] techbreak_: you should remove that publickey [11:36] techbreak_: and read https://help.launchpad.net/YourAccount/CreatingAnSSHKeyPair [11:36] spiv, how do I remove that publickey ? [11:37] spiv, same link I followed earlier and created key [11:37] techbreak_: no, you didn't create that key [11:37] techbreak_: that's a key from paramiko's demo's directory [11:37] spiv, huh? whats that now ? [11:37] techbreak_: it's important for your security that generate your own key [11:38] spiv, hmmm [11:39] spiv, ok now tell me what shall I do now and how ? bare my Noobity, I am just a beginner [11:39] techbreak_: https://help.launchpad.net/YourAccount/CreatingAnSSHKeyPair [11:40] techbreak_: it explains things more clearly than I can :) [11:40] spiv, ok I will do that :) [11:40] techbreak_: I'd like to know how you found that publickey to upload, though [11:40] techbreak_: it seems like an unusual thing to do! [11:40] spiv, wait i will tell you :) === Ursinha-afk is now known as Ursinha [11:41] spiv, gpg --fingerprint gupta.chandan1@gmail.com [11:41] spiv, and then gpg --send-keys [11:42] techbreak_: that's GPG, that's a different set of keys entirely [11:43] spiv, huh ? am I suppose to send some other key too ? [11:43] At a technical level the public key cryptography GPG does has a lot in common with SSH, but it's different software with different keys. [11:44] At some point you presumably went to https://launchpad.net/~gupta-chandan1/+editsshkeys and pasted in the contents of 'user_rsa_key.pub' from the demos/ directory of a library called paramiko. [11:45] You almost certainly *meant* to paste in the contents of ~/.ssh/id_rsa.pub [11:47] techbreak_: I'm off to bed. Good luck! [11:48] spiv, thaks a lot :) good night.. have sweetest dream :) [11:48] g'night spiv! [11:48] techbreak_: (and if you figure out where you went wrong, feel free to tell me in this channel, I'll see it in the morning) [11:48] spiv, can i have your email id ? or anything to contact if i get further problem ? [11:49] spiv, okie fine if you are regular in this channel :) i will surely tell .. whether i succeed or not ;) [11:49] (perhaps it's something we can improve) [12:29] hi [12:29] I'm trying to push a branch to lp:~zkrynicki/ubuntu/lucid/launch-control/packaging [12:30] I'm doing this for a number of my packages (I push the debian packaging to a branch under ubuntu lucid) [12:30] yet for some reason it fails on this branch, the error message is: "bzr: ERROR: Invalid url supplied to transport: "lp:~zkrynicki/ubuntu/lucid/launch-control/packaging": No such source package launch-control." [12:30] am I doing something wrong? The patter is ~username/distro/series/package/branch-name [12:31] zyga: Why not push the Debian packaging under debian? [12:32] Also, apparently there is no such source package as launch-control [12:32] maxb, that's not my problem - let's solve one problem first [12:32] You know you can push to lp:~zyga/debian/sid/sourcepackage/branch right? [12:32] maxb, there are no source packages for any of my things (I'm writing packaging for the first time) but previously it also accepted launchpad project names [12:32] zyga: I'm fairly sure it never did that [12:33] maxb, it did this for about half dozen other packages I made today and yesterday [12:33] maxb, please have a look at https://code.launchpad.net/~zkrynicki [12:33] zyga: are you sure those were packaging branches, not "regular" branches? [12:33] at the ubuntu/lucid brnahces [12:33] jelmer, please explain the difference [12:33] I infer that source packages already existed for the ones you've pushed already [12:34] nope [12:34] zyga: An "interesting" "feature" of launchpad is that source packages in PPAs count for this [12:34] I've started packaging the stuff I'm writing for linaro [12:34] ah [12:34] so if I push a package to a ppa first [12:34] then it's enough :D [12:34] that's something I might have done earlier [12:34] (build with pbuilder, push to ppa, push to lp) [12:35] yeah, that's a bug :-/ [12:35] see https://launchpad.net/ubuntu/+source/launch-control-tool for example [12:35] jelmer: But it's such a *useful* bug :-) [12:35] I like this bug :> [12:35] but in fact there are two bugs :/ [12:35] there is no sane way to push packaging in a way that would link it from the project [12:36] and project -> packages is a messy path with possibly different names [12:36] (it just happens that some projects have same source package name as lp project name) [12:36] right? [12:36] maxb, now what is the advantage to pushing to debian/sid? [12:37] maxb, my situation is rather strange as I need to target lucid explicitly and I cannot use more recent features without backporting things like dh_python2 that I'd rather not do (packaging is not my expertise) [12:37] You said "debian packaging". I inferred you meant "Packaging for Debian" [12:38] maxb, well I meant the packaging as in the debian directory for bzr-builddeb in merge mode (should have mentioned that) [12:38] ah :-) [12:38] while I'd love to push those packages to debian too [12:38] I do not know the way [12:39] (that would also solve future problem for the next LTS as I'll need to target that and it would come from debian for free [13:32] Question: is there a size limit for bzr controlled project? i have one that is around 9 Gb, 18Gb with repository, 50 revisions, biggest file around 1Gb of sql. bzr commit has started to segfault. Ideas? [13:33] zurgutt: there shouldn't be a size limit [13:34] zurgutt: there are some issues with memory usage, but you should just get a MemoryError in that case [13:34] zurgutt: Can you file a bug about this, with a gdb backtrace? [13:38] could be the dirstate pyx bug. [13:38] if you tell me how to do it [13:38] generally sizes > 4GB aren't well tested. [13:40] it has actually created a big problem for me so need to find solution, either fix problem, drop some history or convert to other system if thats only option, im used to bzr tho [13:45] is there a general guide about how to file bugs on actual crashes anywhere? does apport do the right thing? [13:46] * mgz doesn't know gdb [13:49] zurgutt: if nothing else, file a bug with the details on your repo and however much of .bzr.log gets output during the commit before it dies, and ask for more instructions [14:53] joing #ubuntu-devel [14:53] bah [14:55] viciousprimate: boing :) [14:55] zurgutt: something like "gdb --args /usr/bin/bzr commit" should land you in a gdb prompt [14:55] :) [14:55] zurgutt: after that, "run" to start bzr and then "bt" to print the backtrace when it's crashed [14:58] jelmer: roger, thanks, ill try [15:03] gdb --args /usr/bin/bzr commit [15:03] (gdb) run [15:03] Starting program: commit === Ursinha is now known as Ursinha-lunch [15:06] zurgutt: sorry [15:06] zurgutt: gdb --args /usr/bin/python /usr/bin/bzr commit === viciousprimate is now known as mbarnett === seiflotfy_ is now known as seiflotfy === zyga is now known as zyga-food === tchan1 is now known as tchan === beuno is now known as beuno-lunch === beuno-lunch is now known as beuno === zyga is now known as zyga-afk === zyga-afk is now known as zyga === jam1 is now known as jam [20:00] jam: Thanks for the bzr-cvsps-import review (though that MP was already Merged). In that instance I considered the commit message itself to convey sufficient information, hence not supplying an explicit cover letter. [20:01] Why does bzr complain about a " valid .bzr control directory, but not a branch or repository." when trying to upload to launchpad? [20:01] The local branch is fine. [20:01] maxb: when reviewing via email, you don't see the commit message [20:01] I actually reviewed it about a week ago [20:01] hmm. that seems like a bit of a flaw in the process [20:01] but launchpad rejected it for various reasons, so I was resending my "Submit Request Failure" queue [20:02] quotemstr: Can you show the whole error message please? [20:02] bzr: ERROR: At lp:~dan-colascione/emacs/misc-23/ you have a valid .bzr control directory, but not a branch or repository. This is an unsupported configuration. Please move the target directory out of the way and try again. [20:03] maxb: given that almost 100% of my submissions involve many commits, I think it is intentional [20:03] the point of the review is to summarize what happened [20:03] etc [20:03] it *does* tell me if you set an explicit recommended commit message for the proposal [20:03] quotemstr: I would imagine a previous attempt to upload the branch failed, leaving only the basics of a .bzr control directory. [20:04] Worked fine after I deleted the branch and recreated it. [20:04] Thanks. [20:13] hello, having some issues branching based on an rspec [20:13] bzr tags gives me this partial output: [20:13] 1:0.133.10 ? [20:13] 1:0.133.11 ? [20:13] i want the .10 version [20:14] so, i say: bzr branch update-manager test -r "1:0.133.10" [20:14] where update-manager is FROM and test is TO [20:14] and i get: bzr: ERROR: Not a branch: "/home/achiang/Projects/update-manager/0.133.10/". [20:21] any clues? [20:27] achiang: "number:path" is a revspec format, so that's what it's parsing it as [20:27] For tags containing colons, you'll need -r tag:blah [20:28] maxb: what value do i use for "blah" ? [20:28] e.g. -r tag:1:0.133.11 [20:29] oh, i see [20:30] am i just being dense? [20:30] achiang@oak:~/Projects/charlotte-x86/update-manager$ bzr branch update-manager charlotte -r tag:1:0.133.10 [20:30] bzr: ERROR: The branch update-manager has no revision . [20:30] oh... I have a hunch [20:31] Could you try "cd update-manager && bzr branch . ../test -r tag:1:0.133.10" ? [20:32] bzr: ERROR: The branch . has no revision [20:32] hrm [20:32] does it have something to do with that ? in the output of bzr tags? [20:32] oh! [20:32] yes [20:33] So, there's a tag there in the branch pointing at a revision-id, but that revision-id is not present in the branch [20:33] hm [20:34] that is disturbing. i just did a straight bzr branch from lp... [20:34] of what? [20:35] https://code.launchpad.net/~ubuntu-core-dev/update-manager/main [20:39] achiang: thats .... interesting [20:40] maxb: so, any clues on how to resolve this? i do kinda need to fork the branch at that revspec [20:41] based on looking at the earlier 0.133.* tags, I would suggest that that revision exists on some lucid-updates branch [20:43] Hi! I think that it's is not possible to make "partial push". I.e. let's assume that I have two files - both modified. And I would like to push changes just from one of them. I think that it is impossible (=hard and not straightforward) if main branch and the main have diverged. [20:43] hrm, ok. i guess i'll ping mvo tomorrow about this [20:43] Please, correct me if I am wrong [20:44] if my branch [20:44] and the main branch [20:45] achiang: Have you tried lp:~ubuntu-core-dev/update-manager/lucid [20:46] putrycy: You seem to be mixing two separate issues. If you have local modifications to two files, you can certainly commit one but not the other. [20:46] Meanwhile, your branch diverging from main is a separate issue [20:47] achiang: Yes, 0.133.11 is in that branch [20:47] maxb: ok, i'll take a look. need to eat before my stomach digests itself. [20:47] maxb: thanks for the help! [20:48] maxb: I know I can commit. But I'm talking about situation where one change is needed to push to the main branch. Is it possible? [20:48] I'm sorry, you're not explaining your problem well enough for me to be able to help. [20:59] maxb: It seems that I know how to explain it: As I said before I have two branches - a main one that is shared with other users and a local one. I use the local one to commit to it my small changes and from time to time I push my work to the main branch [20:59] And now I have a part that I could push to the main brach [20:59] and a part that is not ready yet [21:00] Question: how to push to the main branch only changes that are ready to show them to other users [21:00] ? [21:02] In version control systems like SVN I can commit for example only one directory. What would be equivlent with pushing changes from that directory in the case of usage of bazaar [21:02] right? [21:03] If you're using bzr in a svn-ish way, then you'd just commit the single directory in exactly the same way [21:03] and If I don't use it in a svn-ish way? [21:04] what then? [21:04] If you've already committed a mix of changes, then you have created a problem for yourself and will need to recommit changes in sensible logical groupings [21:06] OK [21:06] thanks for reply [21:07] * jelmer_ waves [21:18] hi all [23:25] Hi poolie, welcome back [23:27] hi, thanks [23:27] how are you? [23:34] Pretty good, finally. After the gastro last week I think my appetite has returned to normal today. === Ursinha is now known as Ursinha-afk === Ursinha-afk is now known as Ursinha [23:59] and you're pilot this week?