[05:36] Can any UDDers please perform this? $ requeue_package.py --full initramfs-tools [05:36] don't you want #launchpad instead? [05:36] Someone recommended that I go here for this request. [05:38] jam, maybe? [05:39] Or lifeless? [05:39] Logan_: lifeless is no longer @canonical, but I'll look into it. One moment. [05:39] Alright, thanks. :) [05:40] I'm requesting it based on http://package-import.ubuntu.com/status/ and the linked https://bugs.launchpad.net/udd/+bug/714622 , which recommends running that command for packages that encounter that bzr failure. It has worked in the past. [05:40] Ubuntu bug 714622 in Ubuntu Distributed Development "import fails when lp branch has been push --overwrite'n" [High,Confirmed] [05:43] Logan_: I have requeued your package. [05:44] Awesome, thanks jam. :) [08:40] morning [08:42] i've a need to use svn to contribute to some open-source project, so wonder how does bzr-svn compare with hg & git's options? [08:42] otoh, it's sad to see bzr development stalled :-( [08:45] bzr-svn is pretty good [09:09] mornin' [09:10] morning mgz [09:10] lifeless: what's going to happen with bzr? === mmrazik is now known as mmrazik|afk === mmrazik|afk is now known as mmrazik === lamont` is now known as lamont [13:31] hiya [13:32] so what exactly is the difference between development-colo and bzr-colo, and how am I supposed to use the former? [13:42] hello All.. [13:42] im pretty new to bazaar and would like to implement it in my workplace.. [13:43] bzr-explorer is good and would like to master it so that i can talk to developers on how to use it and create a workflow. [13:43] 1 issue im facing is.. [13:43] i have a revision in the server with name, think-blog.. [13:43] i checkout in a client (win7) machine with bzr-explorer installed. [13:43] it asks for sftp password when doing checkout which is normal. [13:44] once i download, if im not wrong, the revision with its history is saved in the client.. [13:44] but here whenever i open bazaar explorer and open that working tree, it asks for passwords.. when i do a diff, it asks for passwrods.. [13:44] why is it still dependent on the server which actually should be doing everything from the local perspective ? [13:44] any ideas ? [13:45] or is it that im doing it wrong ? [13:49] hi,.. anybody ? [14:03] jiku: you don't want a lightweight checkout, you want to make a proper branch [14:04] mgz, oh.. ok... [14:04] i was doing that by default.. [14:04] let me try again. [14:04] you then also may want to put the passwords in your authentications.conf file, see `bzr help authentication` [14:05] ok.. [14:05] let me try this.. [14:05] or, use an agent so you don't type the password each time but use a public key instea [14:05] d [14:06] mathrick: you don't want to use development-colo, but you can use the builtin colo support in 2.6, it's just a little less polished than the bzr-colo plugin [14:09] mgz, hmm.. [14:09] looks like, whenever i do a checkout using explorer, it does with --lightweight enabled. [14:09] you don't want to do checkout [14:09] you want a branch [14:09] (I suspect) [14:10] if you have options over workflows, you really don't want to emulate the centralised server thing of svn etc [14:10] mgz, true.. yes.. [14:11] mgz, was confused with git (never used but just read).. there you checkout and branch.. (if im not wrong) [14:11] depends what you think you can get everyone else to use, but having a full branch locally, and working with trunk+merge is how to get the main benefit of dvcs [14:12] yes.. right.. this is what we need actually.. there shouldn't be a centralized locking.. [14:12] in git, saying 'checkout' means get me all the history, and branch just... prints the branch name or something [14:12] mgz: right, but still, how do I use it? I don't see much explaining how to do it [14:13] mathrick: basically, you just create a new standalone branch, do `bzr switch -b trunk` or whatever to name the default branch [14:13] ah [14:13] then you can do `bzr switch -b feature` to create a feature branch [14:14] `bzr switch trunk` to go back to trunk [14:14] and what about cloning, will it carry over all branches? [14:14] the main missing thing is a nice addressing scheme for colocated branches outside of a few commands [14:14] I see an open bug about it, so I guess not? [14:14] right, it doesn't, though there's a workaround of some kind I think [14:15] what'd that be? [14:16] not sure, but it's reasonably trivial to iterate over local branches and push them all up, there's a plugin that does something like that for shared repos [14:16] this was what I hoped most for, along with fixing the fact that bzr-colo refers to branches with absolute paths, which breaks alternative approaches of just sharing the same workspace dir amongst many machines [14:17] mgz: well, yes, but it needs thinking on my part and remembering to do it. As much as I think git's model is stupid, the fact that fetch carries over everything is a boon [14:17] not just my part, but everyone I talk to [14:17] which is a bigger problem really [14:18] mgz: does 2.6 need anything in the way of the branch format to support colocated branches? [14:18] nope, that's all done [14:18] so just 2a? [14:18] it's just making it all pretty to use that's unfinished [14:19] mhm [14:20] I'm using it for one project currently as an experiment [14:20] apart from some confusion setting up, and needing to know to type file:,branch=FEATURE in a few circumstances, I've not had any issues [14:21] that said, I've not wanted to push all branches, push has been specifically for updating remote trunk after feature branch merge [16:41] jam: Can you please do < requeue_package.py --full iscsitarget > when you get the chance? Thanks so much! [16:41] (Or any other UDDer, for that matter.) [16:44] warum? [16:46] I can do this... well, I could look at the package log as well, but would prefer to not take 15 minutes looking at it first. === deryck is now known as deryck[lunch] === deryck[lunch] is now known as deryck === yofel_ is now known as yofel === Logan__ is now known as Logan_ === _thumper_ is now known as thumper === ccxCZ_ is now known as ccxCZ === Enlik is now known as Guest98527 === lifeless_ is now known as lifeless === Guest98527 is now known as Enlik|meh === bradm_ is now known as bradm [22:51] Is shelve expected to work with bzr-svn? I'm getting "NotImplementedError: '>>" [22:52] nDuff: no, I don't think it works with bzr-svn