/srv/irclogs.ubuntu.com/2009/04/02/#bzr.txt

spivlifeless: pong; just figuring out my after-work commitments now so I can plan that.00:01
Peng_mwhudson: Now with more evil and depravity :) http://bzr.mattnordhoff.com/loggerhead/loggerhead/yui-cdn/revision/324/loggerhead/templates/macros.pt00:06
lifelessspiv: kk00:14
weigonlp's ssh refuses to connect :(00:16
Peng_weigon: LP's down for maintenance.00:16
Peng_maintanence? Eh, whatever.00:16
weigon*doh* thx00:17
jelmercrap, revision properties contain arbitrary binary data?00:21
mwhudsonjelmer: it's just {str:str} isn't it, so i guess so?00:22
jelmermwhudson: what's the easiest way to escape arbitrary data in something representable in unicode?00:23
Peng_jelmer: repr()? s.encode('unicode-escape')? base64?00:24
mwhudsonjelmer: i guess it might be meant to be utf-8 or something00:25
mwhudsoni guess i'm the wrong person to ask00:25
lifelessjelmer: why do you say they contain arbitrary data?00:26
jelmerPeng_: base64 is overkill, unicode-escape requires a unicode string (and I have no way of creating one)00:26
mwhudsonPeng_: your increased depravity looks fine to me :)00:27
Peng_mwhudson: Is that a bb:approve? :D00:30
jelmerlifeless: at least one of the tests tries to add "\xb5" as property value00:30
jelmer(in other words, a <str> object and invalid utf8)00:32
lifelessjelmer: ah interesting00:34
lifelessand we what, base64 enciode them ?00:34
jelmerit seems like it silently gets casted to unicode00:35
jelmerin the XML serializer00:35
jelmerso "\xb5" goes in, u"\xb5" comes out00:35
lifelessbut you said \xb5 isn't valid unicode?00:36
jelmerlifeless: it's invalid utf800:37
lifelessjelmer: is the test testing that or is it a bug in the test?00:46
jelmerlifeless: the bug is in the test00:49
MizardXlifeless: "No shells on this server." ... Connecting with putty with same certificate seems to work. You said if that was so, then bzr didn't pick up Pageant. How would I fix that?00:49
lifelessMizardX: now we've reached the end of my knowledge :( I haven't used bzr on windows00:56
MizardXOk. Thanks.00:56
lifelessMizardX: but we now know that your launchpad and putty stuff is setup00:56
lifelessuhm00:56
lifelessdid you install using the windows binary, or the 'python installer' ?00:57
MizardXbinary00:57
lifelessbzr --version will give you the path to a log file00:57
MizardXI think it's compiled with py2exe00:57
lifelessyou might look in that log and see if there is anything about pagent/putty00:57
MizardXJust "ssh implementation is OpenSSH" and "ConnectionReset: Connection closed: please check connectivity and permissions"00:59
lifelessok00:59
lifelessthat suggests it found a ssh.exe on your machine and is using that01:00
lifelessthere is an environment variable to control this I think, one sec01:00
lifelessdo you have plink installed?01:01
MizardXyes01:02
lifelessok01:02
lifelesstry01:02
lifelesssetting the BZR_SSH environment variable to 'plink'01:02
MizardX"FATAL ERROR: Disconnected: No supported authentication methods available", not it doesn't find the certificate01:04
MizardXnow*01:04
spivlifeless: I'll head to you.  ETA is 11:50 by the time I buy my coffee :)01:06
MizardXAh, pageant wasn't running...01:06
MizardX"Branched 8 revision(s)." :D01:07
MizardXThanks, lifeless.01:07
Peng_mwhudson: ping01:10
Peng_mwhudson: Mind if I make an old-style class in Loggerhead new-style without getting it reviewed? (Well, asking is almost as inconvenient as a review...)01:10
lifelessMizardX: cool01:11
nsh22what does this mean: error: unable to create symlink 'themes' on this platform01:16
SnovaWould I be correct at guessing you're running Windows?01:16
SnovaAlso, how did this come about? What command caused it?01:16
nsh22unfortuneatly yes01:16
nsh22i was just getting a branch01:17
SnovaThen I can only assume the branch contains symlinks, which have no equivalent on Windows... I dunno what else it could mean.01:17
nsh22ugh, ok... the thing is is that it gave me any of the other files in the branch01:18
jmlLaunchpad is running bzr 1.13 on production now.01:20
jml~18s & 21 hpss calls to push no revisions to a stacked branch. ~7s of that is SSH connection time.01:21
jml~27s & 32 hpss calls to push one revision to a stacked branch.01:23
lifelessjml: is this better :)01:24
jmlyes.01:24
smg'day all01:27
smhow long should bzr selftest take on a macbook ?01:27
smit has been running an hour and a hlaf01:27
jelmersm: it takes about 20 minutes here01:28
jmllifeless: bzr pull is noticeably faster.01:28
smjelmer: on a macbook ?01:28
jelmersm: ah, no, sorry - linux01:28
jmllifeless, spiv: congratulations!01:29
lifelessthanks01:29
jmlhmm. making a new stacked branch is still kind of slow.01:32
jmlI wonder if bumping our format to 1.9 would change that.01:32
lifelessdo you have the patches we landed yesteday?01:32
jmllifeless: only if they are in the nightly -- I'll update my bzr.dev and try pushing with that.01:33
lifelesswell, whats your nightly version?01:33
jmllifeless:  1.14~bzr8.10-4223-101:34
jmllifeless: down from 81 -> 66 calls using bzr.dev. still the same elapsed time.01:35
lifelessjml: ok, thats interesting01:37
lifelesspop the log up somewhere01:37
jmllifeless: http://paste.ubuntu.com/142445/ -- first is using nightly, second is bzr.dev01:39
jmlboth are pushes of the same branch to Launchpad but to different locations. branch was made locally from a mirror of the default stacked-on branch. so no new revision data for either push.01:40
SnovaWhat would be the best way to have a particular file updated every commit to include a revision number? I think I could use a hook for it, but it looks like I would have to require it be installed on all committer's computers.01:44
Peng_Snova: Well, that's what the new keyword plugin is for, although it just applies to the working tree, not the history itself, like svn:keywords.01:45
Peng_Snova: That'd mean you only need the people who actually need the revision numbers to install it.01:45
Peng_Snova: Anyway, the usual workaround is to have your Makefile run "bzr version-info >whatever".01:45
lifelessSnova: what do you want to achieve with this?01:46
Snovalifeless: I'd like the server I'm writing to send the revision number along with the version.01:46
lifelessSnova: of the codebase its running?01:47
SnovaYes.01:47
lifelessas Peng says, invoking bzr version-info during server startup is probably better01:47
SnovaI could, but then it assumes it's always in a branch... a source tarball or any form of distribution wouldn't... although I primarily want this during development, if I actually released it there wouldn't be much point.01:48
=== ja1 is now known as jam
SnovaI guess that works, and it's the simplest way.01:49
lifelessyou can hook that into your tarball export logic too01:49
spivlifeless: http://bugs.python.org/issue566001:55
spivjml: well, we think we have stuff in the works that will cut another ~10s out of that fairly soon (needs new verbs, though).02:00
spivjml: thanks for the log02:01
AfCHooray for Bazaar!02:01
jmlspiv: cool.02:01
lifelessjml: so if you're lucky, 1.14 on the server and client will fix it02:02
lifelessif you're not, it won't :)02:02
jmlif I'm extra double lucky, we might get an edge codehosting service so we can run 1.14 on the server before the next LP release.02:02
lifelesswhen is the next release?02:04
jmllifeless: four weeks from today02:04
Peng_What would the edge codehosting do? Have a second copy of everything? Would the main and edge instances both pull mirrored branches?02:09
spivjml: btw, my locations.conf for my bzr branches now defaults to lp02:12
jmlspiv: nice!02:14
spiv67 HPSS calls, 48s (including SSH handshake) and 207k to push up a new branch with a new revision.  Not too bad.02:14
jmlPeng_: it would just be the SSH server & surrounds. There would be no edge puller.02:14
jmlPeng_: it would use the same data and be in every way analogous to the edge web service02:14
spivjml: uh02:15
spivjml: bzr: ERROR: Server sent an unexpected error: ('error', '<ProtocolError for xmlrpc.lp.internal:8097/branchfilesystem: -1 >')02:15
spivjml: that was on a Branch.unlock RPC on an empty push02:15
jmlspiv: hmm. I bet it's an operational glitch.02:16
spivjml: maybe the XML-RPC server was unreachable temporarily for the "hey please rescan this branch" ping?02:16
spivjml: how hard would it be to get that message to a) have an OOPS code, and b) make it clear that LP is to blame, not the client? :)02:16
jmlspiv: if you asked me, I would have thought that the OOPS was already in it.02:18
spivjml: I see!02:18
spivjml: So that means there is probably already an OOPS generated, at least?  That's nice!02:19
spivjml: btw, it does seem to be a transient issue, a second attempt at the empty push worked just fine, rather than erroring on the final (13th! spooky!) RPC.02:20
spivjml: In my magical land of perfect software and ponies, and temporary inability to reach xmlrpc.lp.internal wouldn't break anything...02:21
jmlhttps://bugs.edge.launchpad.net/launchpad-bazaar/+bug/28104202:21
ubottuError: This bug is private02:21
spivs/and/an02:21
jmldescribes such a land. except that it's private, for reasons that elude me at present.02:21
spivjml: ah, yes, I guess it was a timeout, judging from the 20s + a bit it took between request and error response.02:22
* spiv clicks the hard-to-find "me too" link.02:23
spiv(Something seems wrong when it's easier to add a "me too" comment than use the "me too" feature...)02:23
beunospiv, yes. Quite a few things, actually. Hopefully, we'll address that in 2.2.5 with the change in the bug lauout page02:26
jmlspiv: fwiw, https://bugs.edge.launchpad.net/launchpad-bazaar/+bugs?field.tag=codehosting-ssh is actually a fairly complete list of bugs in the codehosting server02:27
jelmerspiv: btw, what's the status of your ~ patch?02:27
spivjelmer: limbo; I need to find some spare time to rewrite along the lines poolie wanted to see if I'm happy with his approach02:28
spivjelmer: I think I'll be fine with poolie's approach (although his approach does need a new server, which is a minor drawback), but it needs to be implemented...02:29
jelmerspiv: ah02:30
spiv(on the other hand my approach needs a new client and his doesn't...)02:31
cody-somervilleCould someone take a look at lp:xubuntu-docs and see if there is anyway we can improve performance? Branching and pushing seems to take a very long time on it02:44
lifelesscody-somerville: use bzr 1.1402:45
lifelesscody-somerville: and be sure you have done bzr launchad-login02:45
cody-somervilleI have02:45
cody-somervilleI'm using 1.1302:45
cody-somervilleis 1.14 in the ppa?02:46
lifelessin the nightly ppa yes02:46
igcjelmer: jam has suggested that the filter registration function just take a callable, not a dict and a callable02:46
igcjelmer: I think it's a good idea. OK with you if I put a patch up for that?02:46
igcwe want the API stable for 1.1402:46
spivcody-somerville: also, have you tried branching and pushing since the lp rollout that happened an hour or so ago?02:47
cody-somervilleI just branched02:47
spivcody-somerville: I'm doing a branch now, and it's streaming to me here in Sydney at ~150K/s02:48
spiv(which I believe is the capacity of this ADSL link)02:49
lifeless(I have a 1.5MB connection, so thats 1.2MB used by bzr02:49
lifelesscody-somerville: and how long did it take to branch?02:50
lifelesscody-somerville: [you are aware you have 30Mb of history]02:50
cody-somervilleYea, I figure thats what the problem is02:51
cody-somervilleI did some nasty stuff to get the revision history to show correctly02:51
beunocody-somerville, and, you could use a shared repo, so you only download whatever revision once in a life time02:51
cody-somervilleI am using a shared repo02:51
lifelesscody-somerville: "12:46 < lifeless> cody-somerville: and how long did it take to branch?02:52
lifeless"02:52
beunoso it should be very fast after you did it oncec...?02:52
beunoonce even02:52
cody-somervillelifeless, about a minute02:52
spiv"time bzr branch lp:xubuntu-docs" here just took 4m23.953s, which seems to be about as fast as this ADSL link allows.02:52
spivGiven that it had to fetch ~36M02:52
lifelesscody-somerville: do another branch with -Dhpss please, and we can look at the network activity if you grab the log for that bzr command from your ~/.bzr.log02:53
cody-somervilleokay02:53
=== timchen119 is now known as nasloc__
lifeless60 seconds is long to figure out you have everything locally, unless you didn't branch into your shared repo02:55
cody-somervilleI did and am again02:55
lifelessoh; also try 'time bzr checkout --lightweight $SOME_LOCAL_BRANCH /tmp/foo'02:55
spivlifeless: FWIW, that takes less than 1s here.02:57
lifelesscody-somerville: ping; 1 minute should have finished ages back03:00
cody-somervillelifeless, It takes a long time to copy and paste the log :P03:00
lifelesscody-somerville: I'm kindof paying attention here to give you a fast turnaround; if you're going away to do stuff let me know and I'll get back to coding03:00
cody-somervillehttp://pastebin.ubuntu.com/142472/03:00
cody-somervilleNo, just takes a long time to copy and paste 6078 lines03:01
lifelessyou missed the top of the log even so :)03:01
cody-somervilleBefore that is log stuff about another command I did03:01
cody-somervilleoh wait03:02
cody-somervillenvm03:02
lifelesscody-somerville: don't worry03:02
lifelessyou're not using a shared repo03:02
lifelessso its copying everything03:02
cody-somervillehttp://pastebin.ubuntu.com/142475/03:02
cody-somervilleoh... I guess you're right03:03
cody-somervilleI thought I had created that03:03
cody-somervillebtw, I did bzr check and it said this: http://pastebin.ubuntu.com/142477/03:04
cody-somervilleIs an inconsistent parent bad?03:05
lifelessits something to fix03:05
lifelessbzr reconcile will fix it03:05
cody-somervillelifeless, So I moved a bunch of files - when I merge from the parent, which hasn't moved the files, will bzr do the right thing or will they go to the old location?03:06
lifelesscody-somerville: why don't you try ?:)03:07
cody-somervillelifeless, cause the branch is reconciling atm or I would ;)03:07
cody-somervilleoh, that was quick03:07
cody-somervillelifeless, would a repack help make the branch smaller?03:09
lifelesscody-somerville: no03:10
lifelessbzr repacks itself as it needs to03:10
cody-somervillewhat about that obsolete_packs directory?03:12
cody-somervilleis that maybe causing the download to be more than it needs to be?03:12
spivNo, it doesn't affect downloads at all.03:13
cody-somervillehmm... the branch seems to be bigger now than before03:13
lifelesscody-somerville: 1 minute is not long03:14
spivYou have 36M of actual revision history, which doesn't sound so unlikely for nearly 200 revisions of a 5.9M tree of files.03:14
cody-somervilleIts 77M on disk03:14
lifelesscody-somerville: all seems to be working reasonably; its under a second to make a working tree, and with a shared repo new branches hsould be about 3 seconds or less03:14
lifelesscody-somerville: thats because of the reconcile; ignore it03:14
lifelesscody-somerville: housekeeping will take care of it03:15
cody-somervillelifeless, so will this reconcile get pushed to launchpad?03:15
lifelesscody-somerville: no03:15
lifelesslaunchpad needs to be reconciled separately03:15
cody-somervilleshould I do that?03:15
lifelessif you like03:16
cody-somervillewhat exactly am I fixing?03:16
cody-somervilleWill it make merging easier or something?03:16
lifelesswhat revisions annotate will attribute content to03:16
lifelesscody-somerville: generally speaking you shouldn't need to worry or do anything special with bzr to make it perform well; the one key exception is shared repositories03:18
lifelessand the second key exception is using a smart server if one is available (which lp: does for you once you login, and bzr+ssh/bzr+http do elsewhere)03:18
exarkunHey I discovered the super awesome "bzr join" command without any help from mwhudson but the only problem is that I can't figure out how to use it would anyone like to assist me03:26
exarkunI have two unrelated branches and I want to make one of them just be part of the other one.03:26
cody-somervillehmm...03:28
cody-somervillebzr doesn't seem to have done the right thing :(03:28
cody-somervilleand ugh.. "1432 conflicts encountered".03:28
lifelessexarkun: use the bzr merge-into plugin; join is part of an as-yet unreleased feature03:29
lifelesscody-somerville: did it print 'criss cross merge' at the top ?03:29
cody-somervilleno03:29
lifelessthats very odd then03:30
lifelesswhat are the conflicts?03:30
lifelessand when you say you did nasty things, could you be more specific03:30
lifelessI'm going to guess you've been doing history-glueing in some nasty manner, and it is [predictably] biting you03:31
cody-somervilleWell, I took branch A and branch B03:31
exarkunlifeless: Oops!  I figured out how to use bzr join while I wasn't looking at IRC.03:32
cody-somervilleA wasn't based on branch B03:32
exarkunlifeless: Should I start over with merge-into?03:32
cody-somervilleBut really was03:32
lifelessexarkun: if it has worked, go for it.03:32
exarkunokay cool, thanks :)03:32
cody-somervilleSo I merged B into A using -c 103:32
cody-somervilleThat worked fine and I got what I wanted except I lost all the revision history from branch B and some people didn't like that03:32
lifelesscody-somerville: when you say 'a wasn't based on branch b' do you mean 'they were completely separate projects' ?03:33
cody-somervilleNo, it was Xubuntu docs and Ubuntu docs03:33
cody-somervilleThey're similar but the branches didn't have shared revision history because Matthew restarted all the branches from scratch for some reason03:33
cody-somervilleI imagine for performance reasons03:33
lifelessok, which means 'they were completely separate projects'03:34
lifelessno history -> separate projects03:34
cody-somervilleRight03:34
cody-somervilleB was based on C03:34
lifelessyou should use 'bzr merge-into' to join them.03:34
cody-somervilleand now I'm trying to merge C into B03:34
cody-somervilleOh I missed a part03:35
cody-somervilleI removed everything in B and put in the contents from A to get the history back03:35
cody-somervilleand then I merged A into B to get the metadata03:35
cody-somervilleB *is* based off of C and now I'm trying to merge C into B03:36
lifelesswell03:37
lifelessyou might try merge --weave03:37
cody-somervilleI moved a ton of stuff into a subdirectory03:37
lifelessit may do better03:37
lifelessdid you move using 'bzr mv' ?03:37
cody-somervilleso now I have a bunch of files in the old directory ending with .BASE and .OTHER03:37
cody-somervillelifeless, I did in A, yea03:37
lifelessor did you move by doing 'mv; bzr add' ?03:37
cody-somervilleI did bzr move03:38
cody-somervillebut in A03:38
lifelessis A merged into C or B or neither?03:38
cody-somervilleinto B03:38
cody-somervilleso should I do: bzr remerge --merge-type weave --reprocess03:41
* cody-somerville tries03:42
cody-somervillelifeless, If this doesn't work, would branching C and doing the moves over again and then merging that into B work and make future merges of C work?03:43
cody-somervillehmm... only 1324 conflicts this time03:43
cody-somervillebut didn't do the right thing. bzr diff desktop-guide (the directory I moved almost all the directories into) returns nothing.03:44
lifelesscody-somerville: what would you expect it to return?03:45
cody-somervillelifeless, The changes bzr merged in?03:45
cody-somervillelifeless, bzr isn't touching any of the files already in the branch03:47
cody-somervillelifeless, all the conflicts are on files its added03:47
cody-somervilleI'm also getting this error now trying to branch inside the shared repository I created: http://pastebin.ubuntu.com/142494/03:50
lifelesscody-somerville: you ran 'bzr init-repo' to make the shared repository, yes?03:52
cody-somervilleyup03:52
lifelesscd to the root of the shared repo03:52
cody-somervilleokay03:52
lifelessand run bzr upgrade --default-rich-root03:52
cody-somervillebzr: ERROR: no such option: --default-rich-root03:53
lifeless'use bzr 1.14' :)03:53
lifelesshell you're canonical, you should be using the nightly ppa :)03:53
cody-somerville;p03:55
cody-somervillealso, I just got this when trying to do bzr remove */po/*.po: bzr: ERROR: [Errno 24] open: Too many open files: '.'03:55
SamBhmm, I wish that the GNOME vcs-imports branches weren't the default branches :-(04:40
spivSamB: if there's a better branch to use, file a request at https://answers.launchpad.net/launchpad-bazaar asking for the default to be changed.05:20
SamBspiv: well, in #launchpad they've got me seeing if I was using a bleeding-edge enough bzr that they should have fixed the problem where it takes forever to push to a branch with little to no shared history with the branch it is to be stacked on ...05:21
spivSamB: ah, yes.  We keep fixing bugs :)05:22
spivSamB: but even so, if there's a better branch, do let the relevant people know05:23
SamBand they said something about how GNOME is supposed to be switching to git05:23
SamBso that the bzr-playground branches might not be that great for too long05:24
spivSSH handshake time is now well over a third of the overall time in random incremental pushes to my branches on LP.05:31
SamBoh, incremental pushes seem fine05:32
spivSamB: I'm opening to changing the message if it can be less confusing05:49
spivSamB: but I figured I should explain why it is saying that (and why it's not "lying").05:49
SamBWell, "transferring" is a much more neutral word05:49
SamBif it can't be bothered to figure out which of the two activities it is engaged in is taking all the time ...05:49
spivI'm not sure what you mean by that comment?05:50
spivThe activity is (accurately, by its choice of perspective) called "fetching".05:50
SamBwell, it's not waiting on the fetches from the local repository ... it's waitng on the stores to the other one05:50
spivNot really, those things aren't really decoupled.05:51
SamBwell, okay, in that case the word is "transfer"05:51
lifelessso05:52
lifelesswe're going to overhaul this05:52
lifelessand make it prettier05:52
SamBat least, in en_US that's the case05:52
lifelesstransfer is indeed a synonym05:52
lifelessor nearly so05:52
lifelessat the right point in the code05:52
SamBmaybe in en_AU or en_UK, fetch is more synonymous with transfer?05:52
lifelessbut one of the basic problems is that the code doesn't *know* which end of the pipeline the human is sitting05:53
lifelessso really, a more directional adverb to describe what is going on isn't easy to correlate with the UI05:53
SamBwell ... saying "transfer" is a nice and neutral thing to do in that case05:53
SamBor when, say, both repos are local05:53
lifelesssure, thats one way we can alter the message05:53
lifelessall I'm trying to say is:05:54
lifeless - it is broken at the moment05:54
SamBokay, yeah, I gathered ;-)05:54
lifeless - its not top of the pops for time until the rc05:54
lifeless - until then, I don't plan on thinking too hard about it05:54
lifeless(so please forgive me for simply acking that its an issue, until we're looking at the code, finding a combination that reads well and fits the code isn't necessarily easy05:55
lifelessthe code itself *is* highly directional05:55
SamByou know, I guess I don't need to finish this push ;-)05:57
lifelessSamB: is it still slow?05:57
SamBit's just that I was just pushing the same thing to a new branch05:58
SamBso now that I've established that it was just a confusing progress message, I don't need to finish05:58
lifelessoh :)05:58
lifelessmakes sense to me05:58
vilalifeless: did you see my patch about --parallel ?06:29
lifelessno06:31
vilalifeless: ~one liner to make it work but I think you're the one that can review it06:33
lifelesswhere is it06:49
lifelessvila: ^06:57
vilahttp://bundlebuggy.aaronbentley.com/project/bzr/request/%3Cm2iqlozk7x.fsf%40free.fr%3E06:57
lifeless # A registry where get() returns a suite decorator.06:58
lifeless parallel_registry = registry.Registry()06:58
lifeless+06:58
lifeless+06:58
lifeless def fork_decorator(suite):06:58
lifeless those changes are bogus , PEP8 allows adjacent for things that are closely related06:59
lifelessspecifically I want the FOO_decorator and register..FOO adjacent06:59
lifelessvila: reviewed07:05
vilalifeless: still ok to separate each couple ?07:15
lifelesssure07:18
=== serg_ is now known as serg
=== serg is now known as anyone
=== anyone is now known as serg
VSpikeIf I do bzr revert on a file, does that count as a change? IOTW, if I commit it, will it commit the reverted file as a head revision?11:43
luksbzr revert is no different from manually changing the working tree11:45
luksplain 'bzr revert' will just revert to the head revision, so it wouldn't commit anything11:45
VSpikeAh OK - thanks.  I used to use perforce, and that behaved quite differently IIRC. It would rememeber what revision number of each file you currently have in your working tree.11:46
lukshm?11:46
VSpikeSo pulling out an old version to look at was not a change.11:46
luksah11:46
luksno, bzr revert operates purely on the working tree, you can do something like 'bzr cat -r file >file' and it will be more or less the equivalent11:47
VSpikeRight - makes sense. Thanks!11:47
awilkinsjelmer/vila: would authentication.conf have problems with passwords that contain @ characters?12:18
awilkinsSpecfically, if I put my password in the file, it fails, remove it and I get prompted more than once for each bzr-svn push12:19
vilaawilkins: quote it12:21
awilkinsAha12:21
awilkinsvila: Failed12:22
vilaawilkins: :-/ quoted as in user@host => user%40host ?12:23
awilkinsAh, as in "c@r"12:23
vilaawilkins: sorry, I meant url encode it12:23
awilkinsHmmph, still not working12:24
awilkinsAlthough by now I may have locked out my account I suppose12:25
awilkinsNope, still works fine at the command line12:25
vilaawilkins: what protocol are you using ?12:25
awilkinssvn+http12:25
vilayou mean bug #256612 ?12:26
ubottuLaunchpad bug 256612 in bzr "should prompt for usernames during HTTP Basic/Digest auth" [High,In progress] https://launchpad.net/bugs/25661212:26
vilaor some related problem ?12:26
awilkinsTHe username is correctly being picked up from auth.conf with is set up for the host12:27
awilkinsIf I add the password it failes12:27
vilaI thought connecting succesfully with *svn* was the current work-around12:27
awilkinsYes, I thought I'd done that12:27
awilkinsAlthough it was with TSVN12:27
awilkinsI'll try getting it cached in the CLI client also12:27
awilkinsThat works12:29
vilagood, then you encountered the bug above or something very close12:30
awilkinsIt's obviously using the password when it's provided in the conf file, but it appears to be wrong12:33
=== ja1 is now known as jam
spivlifeless, jml: they've fixed the deepcopy(TestCase(...)) bug12:56
spivlifeless, jml: but you might want to take a look at the new TestCase.addTypeEqualityFunc method12:58
fbondjelmer: I imported an svn repository with bzr-svn's svn-import.  I see "svn revno: x" in log output, but I can't use -r svn:x.  Why not?13:33
=== sabdfl1 is now known as sabdfl
=== NEBAP is now known as NEBAP|work
=== NEBAP|work is now known as NEBAP|away
=== NEBAP|away is now known as NEBAP|work
jelmerfbond: you need a newer version of bzr-svn to do that on imported branches14:17
jelmerigc: yeah, just taking a callback sounds good to me14:18
fbondjelmer: Okay, thanks.14:18
fbondjelmer: I'm using trac-bzr; it'd be really swell if I could get the old references to svn revisions work in the diff viewer. ;)14:19
fbondI mean [283] links and whatnot.14:19
=== ja1 is now known as jam
=== abentley1 is now known as abentley
jelmervila: bleh, I'm not sure how I missed that appearance of 'password'15:04
vilajelmer: :-)15:04
jelmervila: I did actually refactor that function but changed it back after I noticed it broke for LC_ALL=C15:05
vilajelmer: huh ? the one you copy from has been passing for ages or did I miss something ?15:07
jelmervila: Yes, but I changed it after I copy pasted it15:07
vilahaaa :)15:07
jelmervila: and that broke the tests, so I fixed it and ended up with what the original did :-)15:08
jelmervila: Your NotATerminal patch looks ok, with one minor concern15:08
jelmervila: won't this caused backtraces when there's no terminal?15:08
jelmergetpass() will raise an exception that's not caught atm15:08
vilajelmer: which exception ? EOFError ?15:10
jelmervila: termios.error15:10
jelmerin my case:15:11
jelmertermios.error: (25, 'Inappropriate ioctl for device')15:11
jelmerincluding backtrace15:11
vilaand the backtrace leads to what ? 'sys.stdin.readline()' or some termios call ?15:12
jelmervila: getpass.py line 3215:13
jelmerthat's indeed a termios call in getpass()15:14
vilajelmer: grr15:14
vilastream=None => stream = sys.stdout, damn, I explicitely avoid using a prompt and see what happens ! :)15:14
vilavila: oh no, it's indeed related to stdin15:15
vilahmm, so that's why NotATerminal was there :-/15:17
jelmervila: ah, right15:20
jelmergood I did some testing then :-)15:21
jelmervila: So NotATerminal can't be removed, but your other refactoring is still valid right?15:21
vilajelmer: indeed !15:21
vilajelmer: No15:22
vilahmm, or may be we just need to put raise NotATerminal in get_password...15:22
vilaUrgh, how ugly, the user can enter its login but not its password15:22
vilano, I think the right fix is to either call readline() or getpass depending on stdin.isatty() or something like that15:25
vilaturning echo off makes sense only on a tty and that's the reason we want to use getpass15:25
jelmervila: sounds reasonable15:26
=== thunderstruck is now known as gnomefreak
=== thunderstruck is now known as gnomefreak
exarkunIf I committed with a bad username, is there a way to fix those revisions to use a new value for that field?16:02
LeoNerdOnly by uncommit/recommit16:05
LeoNerdOr variants thereof.. The internal revision ID uses a hash of the data, collectively. So changing the data would change the hash, and hence the revid16:05
jelmervila: will you submit a new patch?16:06
vilaI think so, but not in the coming minutes nor hours I'm affraid16:07
jelmervila: thanks, no hurry :-)16:08
jelmervila: and thanks for the work on this auth stuff, hopefully bzr/bzr-svn 1.14 will be the first bzr where this stuff works properly16:09
vilajelmer: np, I'd still like feedback from the other devs about utf8 encoding16:09
exarkunLeoNerd: Thanks16:09
vilajelmer: I noted that you didn't *call* get_username, are you planning to work on that ?16:09
vilajelmer: yeah hopefully, but as you see, evils is in the details :)16:10
=== serg_ is now known as serg
jelmervila: don't call it in what sense?16:10
jelmervila: get_user() would use it16:11
vilaoooh, yes, indeed, the other patch, ok16:11
jelmervila: speaking of which..16:11
vilathen will you update that one to take into account the other calls to getpass.getuser() /16:12
vilas!/!?!16:12
jelmervila: you mentioned that http uses get_user() atm and the others use getpass.getuser()16:12
vilayup, that point :)16:12
jelmervila: Just to make sure; they should all call get_user() but get_user() should default to getpass.getuser() ?16:13
jelmervila: You also mentioned something about only prompting if a prompt was specified16:13
vilajelmer: yes, except that defaulting should be the default but http can overrride it16:13
vilaha, I didn't think about using the prompt for that...16:14
jelmervila: so defaulting is directly returning getpass.getuser() or rather printing "[DEFAULT]" and letting the user just hit <enter> to use that?16:14
vila...I was thinking about a new, optional, parameter...16:15
vilano16:15
vilawe don't want to require pressing enter where we didn't before16:15
jelmerok16:15
vilawhen we default to getpass.getuser... we default period. You can ask for feedback but I doubt we want to change that16:16
jelmervila: ok, so I won't touch anything but http at the moment16:16
jelmervila: what would you like to change in case of http?16:16
jelmeris it ok to require pressing <enter> or entering a username there if there's no user specified in authentication.conf ?16:17
vilajelmer: I think you should change ftp/ssh/http, call ui.get_username() from config.get_user() but only if required via a parameter (i.e. http only) and get rid of the getpass.getuser() calls in ftp/ssh16:17
vilajust do a grep getpass you'll understand easily I'm sure16:18
jelmervila: ah, ok16:19
jelmervila: so, just to make sure:16:19
jelmervila: I'd add a new parameter to get_user() that specifies whether or not to ask the user16:19
jelmervila: and only http for now sets that parameter to true16:20
vilaexactly16:20
exarkunSo once I do the uncommit/commit dance to get my username right in the revisions, if I want to fix what's on launchpad, should I do a push --overwrite?16:21
vilasounds like the cleanest way while still allowing get_username to get overwritten by GUIs with the usual mechanism16:21
jelmerexarkun: yes16:21
exarkuncool16:22
=== abentley1 is now known as abentley
=== thunderstruck is now known as gnomefrak
=== gnomefrak is now known as gnomefreak
=== LenzGr is now known as LenzGr|dinner
nilghi, I've made bzr rm file, on the wrong file, is there anyway to get it back simply?18:42
nilgI haven't committed yet18:42
luke-jris there a bzr-cvs plugin?18:46
nilghi, I've made bzr rm file, on the wrong file, is there anyway to get it back simply?18:50
luke-jrbzr revert file?18:50
nilgluke-jr, it works thanks a lot (I got scared for a second)18:52
ricardokirknerhi jelmer, I am having some issues with bzr-svn, that I saw were supposedly fixed in bzr 1.6. I am using bzr 1.13 with bzr-svn from launchpad, and am still getting python: subversion/libsvn_subr/path.c:414: svn_path_is_empty: Assertion `is_canonical(path, strlen(path))' failed.19:43
ricardokirknerwhen trying to push to upstream19:43
fbondAny way to get a series of patches for a series of commits?19:53
fbond(In one command, or so.)19:53
fbondHm, I guess I'll just shell script it.19:54
jfroyAny thoughts on https://bugs.launchpad.net/bzr/+bug/354036?19:56
ubottuLaunchpad bug 354036 in bzr "ErrorFromSmartServer - AbsentContentFactory object has no attribute 'get_bytes_as' exception while pulling from Launchpad" [Undecided,New]19:56
jfroyI suspect it may have to do with the recent Launchpad bzr 1.13 upgrade19:57
jfroyBut that's speculation.19:57
klbateHello! If I have pushed a commit but forgot to sign it, how can I push just the signature afterwards?19:57
Peng_klbate: You can run "bzr sign-my-commits", but I dunno if pushing afterwards will push the new signatures.19:57
klbate_Sorry, was disconnected...19:59
klbate_In Git there is something like 'push --tags', is there a bzr equivalent?20:00
Peng_klbate_: "bzr push" will silently push new tags, so it's a reasonable assumption that it will do the same with signatures.20:02
Peng_It's worth a try, at least.20:03
ricardokirknerjelmer, really sorry to insist... but whenever you can I would really appreciate it, as it's a blocker for me right now20:04
lukscan somebody in the ~bzr lp group please copy the qbzr 0.9.9 packages from https://launchpad.net/~qbzr-dev/+archive/ppa to https://launchpad.net/~bzr/+archive/ppa ?20:17
Peng_Huh, bzr just started whining about an invalid config file somewhere.20:29
Peng_lifeless: ping20:33
abentleylifeless: ping20:37
abentleyemmajane: Oh, hi.20:38
emmajaneola abentley :)20:38
abentleyÇa va?20:39
ricardokirknerwhat options should I use in order to find out why bzr-svn is crashing?20:39
emmajanepresque. :)20:39
emmajaneI'm inside and it's nice outside. :)20:39
emmajaneabentley, how's the weather down south today?20:41
emmajaneabentley, someone told me we're getting another dump of snow. which makes me cry inside.20:41
abentleyemmajane: It's not bad.  You can get away without a jacket for a bit.  But the clouds have rolled in today.20:42
Peng_abentley: What are you pinging him about:? :D20:43
emmajaneabentley, boo to the clouds.20:43
abentleyPeng_: WorkingTree4.iter_references20:43
Peng_abentley: Oh.20:43
abentleyemmajane: Did you know Mike Audet's up in Peterborough nowadays?20:45
emmajaneabentley, the nerve! what's he doing up there?20:46
emmajaneabentley, my cousin is at Trent. :)20:47
abentleyemmajane: Teaching, doing some programming on the side.20:47
emmajaneabentley, sweet!20:47
kfogelit's fairly standard in bzr to use "r800" as an abbreviation for "revno 800", right?20:57
kfogel(Users Guide seems to indicate so, but only by implication...)20:57
mwhudsonkfogel: i certainly do that quite a lot20:58
kfogelmwhudson: thx20:58
Peng_kfogel: I picked up the habit from svn and still use it with bzr.20:58
kfogelPeng_: more confirmation, good20:59
james_wdoes -r handle "r800"?20:59
kfogeljames_w: in svn, yes :-)21:00
james_wI thought I remembered a bug about it not doing so21:00
Peng_Oh crap. I just reverted bzr to r3234 instead of r4234. Now it doesn't even recognize the branch format. :D21:04
Peng_Thank goodness I had another copy of bzr around.21:04
lifelessPeng_: pong21:07
lifelessabentley: pong21:07
abentleylifeless: DirStateWorkingTree.iter_references raises and AttributeError if you don't lock the tree before use.  I found this surprising.21:07
abentleys/and/an21:08
lifelessabentley: thats certainly a bug; I would expect it to raise, but not AttributeError21:08
Peng_lifeless: Oh hi. I filed bug 354075 about what I was pinging you about, but forgot to unping you.21:09
ubottuLaunchpad bug 354075 in bzr "Branch.get_config_file smart verb breaks get_bzr_remote_path" [Undecided,New] https://launchpad.net/bugs/35407521:09
lifelessabentley: btw, how long does it take you to run the bzr test suite ?21:09
nsh22hi umm, how do i merge two different lp branches?21:09
abentleylifeless: This is because you initialize DirStateWorkingTree._repo_supports_tree_reference when the tree is locked.21:10
lifelessnsh22: cd branch1 && bzr merge branch2 && bzr commit && bzr push21:10
abentleylifeless: Rather than at __init__ time, as you do with the RevisionTree.21:10
nsh22lifeless: thx21:11
abentleylifeless: What's the reason for delaying that?21:11
lifelessabentley: I guess I was thinking of cases where 'bzr switch' was used and the backing repo facilities changed21:12
abentleylifeless: I dunno how long the suite takes.  Maybe 25 minutes?21:12
lifelessabentley: with the bzr-ec2test plugin & 2 warmed up instances, its takes ~90 seconds. You might like to play :)21:12
abentleylifeless: In the 'switch' case, the tree would remain write_locked during the switch, so the _repo_supports_tree_reference would get stale, wouldn't it?21:22
lifelessabentley: possibly yes; I guess you're trying to see whether to work around [e.g. getattr, init to None etc] or to move it to __init__ - I'm happy either way, or even a third21:22
lifelessI'd suggest avoiding a getattr(), I don't think one is justified21:23
abentleylifeless: I'm also wondering if the win of caching that data on WT is worth it.  Thoughts?21:24
lifelessif its accessed during the iter_changes outer loop it may be measurable on 'bzr st' timings21:25
lifelessabentley: oh, possibly it wasn't caching at all; maybe WT2 can't be right root ?21:28
lifelessand so we have tree code that correctly needs to ask the tree not the repo.21:28
abentleylifeless: I suppose that's useful when you're detecting subtrees and then forcing them to directories because of the repo.21:30
lifelessabentley: well also for 'add-reference' to fail correctly when the tree can't represent the add21:31
abentleylifeless: In that case, I don't think the caching is essential.21:31
abentleyWT2 can implement add_reference to always raise...21:32
lifelessPeng_: so, what is 'bytes'21:46
Peng_lifeless: Eh?21:50
jelmerricardokirkner: hi21:53
jelmerricardokirkner: are you using the latest bzr, bzr-svn and subvertpy?21:53
ricardokirknerhi jelmer, thanks21:53
ricardokirknerbzr 1.1321:53
ricardokirknerlatest bzr-svn21:53
ricardokirknerand subvertpy21:53
ricardokirkneryes21:53
ricardokirknerI have been tracing bzr, until I got to line commit.py:60021:53
jelmerricardokirkner: please run inside of gdb and pastebin the bracktrace21:53
ricardokirknerI'll do that21:54
ricardokirknerbut maybe I have found the reason. let me explain21:54
jelmerricardokirkner: subvertpy 0.6.5?21:54
ricardokirkneryes21:54
ricardokirknerand python 2.6 (64 bits)21:54
ricardokirknerthe line that causes an abort, is when doing21:55
ricardokirknerret.append(ret[-1].add_directory(name, copyfrom_url, base_rev))21:55
ricardokirknernow, I just saw that copyfrom_url ends with a '/'21:55
ricardokirknerI from what I read, that is causing the svn abort21:56
ricardokirknerdoes this make sense?21:56
jelmerricardokirkner: copyfrom_url doesn't matter in this case21:56
jelmerricardokirkner: does path end in / ?21:56
ricardokirknerwhat path?21:57
ricardokirknername?21:57
jelmerricardokirkner: anyway, that backtrace would really be useful here..21:57
ricardokirknerok21:57
ricardokirknersec21:57
ricardokirknerjelmer, http://ricardokirkner.pastebin.com/d3ec659ab22:00
lifelessmwhudson: is loggerhead bust?22:04
lifelessmwhudson: it shows me no diff for http://bazaar.launchpad.net/~geoff.bache/bzr/trunk/revision/415822:04
mwhudsonlifeless: 'expand all'22:04
lifelessmwhudson: does nothing22:05
Peng_lifeless: It's all Ajaxy now. Do you have JS disabled, or a weird browser?22:05
mwhudsonlifeless: hmm, maybe shift-reload22:05
Peng_lifeless: It works for me.22:05
Peng_Oh, good point.22:05
mwhudsoni keep meaning to vary the static urls by version...22:05
lifelessPeng_: epiphany,22:06
lifelessmwhudson: thanks22:06
lifelessmwhudson: and please do that, kthanksworking22:06
jelmerricardokirkner: please try again with latest rev on subvertpy22:08
ricardokirknerjelmer, I installed subvertpy using easy_install, should I try downloading from trunk?22:09
jelmerricardokirkner: yeah22:09
ricardokirknerok22:09
jelmerlifeless: any chance you can have a look at my BzrDir.push() patch ?22:09
lifelessjelmer: sure, url22:12
jelmerlifeless: http://bundlebuggy.aaronbentley.com/project/bzr/request/%3C20090401141753.GA16842%40vernstok.nl%3E22:13
ricardokirknerjelmer, same thing :-(22:14
jelmerricardokirkner: are you sure you're running the latest subvertpy22:14
jelmerricardokirkner: oh, whoops22:14
jelmerricardokirkner: push failed, one sec22:14
ricardokirkneroh22:14
jelmerricardokirkner: pushed properly now, r205122:15
Peng_lifeless: Oh, sorry I didn't understand you. I updated the get_bzr_remote_path bug.22:16
Peng_Wait a minute, it's *supposed* to be the contents of branch.conf, so why is ConfigObj balking?22:17
ricardokirknerjelmer, :-(22:19
jelmerricardokirkner: ?22:20
ricardokirknersame thing still happening22:20
ricardokirknerI checked and doublechecked22:20
jelmerricardokirkner: backtrace?22:20
jelmerricardokirkner: at least the line numbers should be different..22:20
ricardokirknerok, one sec22:21
=== abentley1 is now known as abentley
ricardokirknerjelmer, http://ricardokirkner.pastebin.com/d767040a922:23
=== abentley1 is now known as abentley
=== abentley1 is now known as abentley
ricardokirknerjelmer, I have to go now,.. will try again later22:32
ricardokirknerthanks a lot for your help22:32
jelmerricardokirkner: I'm working on a fix22:33
jelmerricardokirkner: to subvertpy22:33
jelmershould be committed in a few minutes22:33
Peng_lifeless: ping22:39
lifelessPeng_: pong22:45
Peng_lifeless: Hi.22:46
lifelesshawwo, was just responding, again, to the 1.14 delay thread22:46
lifelesshopefully Ian wins troll of the year award22:46
lifelessfor his april first post22:46
Peng_?22:46
lifelessnew 1.14rc date, was posted april 1st22:47
Peng_Oh.22:47
lifelesshe really needs to jump out about now in the thread and say 'april fools'22:47
lifeless:)22:47
lifelessanyway22:47
Peng_lifeless: I was just pinging you because I want hand-holding through the get_config_file bug. :D22:48
lifelessright22:48
lifelessjust change it to bytes.splitlines('\n') is probably enoug22:48
lifelessrather than [bytes]22:48
lifelessalso config objs constructor blows chunks22:49
Peng_I just used "splitlines()". That's what I wanted to ask.22:49
lifelessoh22:49
lifelessyeah that shold be fine22:49
lifelessworking >> anything else22:49
Peng_Is that alright? Should I only split on \n?22:49
lifelesssplitlines should be ok22:49
lifelessjelmer: does bzrdir.push work for you?22:50
BasicOSXlifeless:  thanks for the response regarding 1.14 RC date22:52
BasicOSXI think mbp should never go on another holiday again, ever! :-P22:53
lifelessBasicOSX: :)22:54
Peng_lifeless: Anyway, the other thing I wanted to ask you about was adding a test.23:01
Peng_Um.23:01
lifelessEither expand one of the test_remote.py tests for _get_config23:01
lifelessor add another in the same class23:01
lifelessjust set two keys and then get one back23:01
lifelessshould trigger23:01
Peng_Um.23:03
Peng_Pardon my dumbness, but I'm completely lost in the test suite.23:06
lifelessuna momento23:07
Peng_Wait, hold on.23:07
Peng_I think I can just copy test_get_branch_conf.23:07
Peng_Or I could just modify it to use a 2-line file.23:08
Peng_Oh, interesting. ConfigObj(['# line 1\n# line 2\n'], encoding='utf-8') works.23:10
Peng_You need non-comment lines to trigger the failure.23:10
Peng_lifeless: Where should I add the test? test_remote.TestBranchControlGetBranchConf? That seems to be the only place it's tested.23:15
Peng_lifeless: (I mean, in that file..)23:15
lifelessPeng_: yes, thats the unit test for it23:20
Peng_lifeless: Should I modify the current test or add a new one? I'd prefer to do the latter, just...cuz.23:21
lifelesseither is fine, new test is clearer23:22
Peng_Okay.23:24
Peng_Then...send it to the mailing list? :D23:24
Peng_lifeless: If that email *was* an April Fool's joke, he definitely wins this year. That sparked a huge discussion!23:26
lifelessPeng_: sadly it wasn't23:29
lifelessPeng_: yah, [MERGE] it up23:29
Peng_lifeless: Oh, too bad.23:29
lifelessit will need to be cherry picked to 1.14 too now :)23:29
Peng_lifeless: ok23:29
lifelessjelmer: ping23:33
lifelessjelmer: does the BzrDir.push patch meet your needs, and is it mainly moved code?23:33
jelmerlifeless: yes and yes23:34
yacoobHello there :)23:34
lifelessjelmer: land it23:34
jelmerlifeless: is that a bb:approve ? :-)23:34
yacooba (perhaps stupid) question: provided I want to keep a set of config files in a bazaar repository, is there a way of saying 'get me this revision of this file from repo'?23:35
lifelessjelmer: not quite23:35
lifelessyacoob: bzr cat -r X this_file23:35
jelmerlifeless: so what do you mean exactly?23:36
lifelessI've reviewed23:36
lifelessBasicOSX: I too am a little confused23:37
lifelessBasicOSX: did you mean 'land bbc now' too ?23:37
BasicOSXlifeless:  yes23:38
lifelessok cool.23:38
lifelesswe'll land on trunk and merge to the rc branch then - you might like to clarify that on the list :)23:38
jelmerlifeless: ? land it where ?23:38
jelmerlifeless: oh never mind23:39
jelmerlifeless: I hadn't seen your email reply23:39
Peng_What's being landed where?23:41
Peng_lifeless: Anyway, I think I sent it. My IMAP server is slow today, but SMTP probably works.23:42
lifelessPeng_: if I understand BasicOSX correctly; brisbane-core will go to bzr.dev asap (meaning a once-through review) and be cherry picked to 1.1423:42
lifelessBasicOSX: ^ is that what you mean to have happen?23:42
Peng_Cherry-picking hundreds of revisions consisting of thousands of lines of code sounds like "fun".23:43
jelmerhmm23:44
* jelmer thinks one of the hot topics at the bzr sprint this year should be "parallel imports"23:45
johnjosephbachir'ello. bzr newbie here. i just did a couple commits, then did "uncommit" twice, then commited that. all seems to have behaved as epected, and bzr status shows no changes. BUT, the actual source tree has not been changed!23:47
lifelessjohnjosephbachir: it would't have23:48
johnjosephbachirORLY23:48
Peng_johnjosephbachir: "uncommit" and "commit" don't change the working tree.23:48
lifelessuncommit pops a commit off, it doesn't revert the changes in your tree23:48
BasicOSXI was under the impression BC was in 1 branch that could be merges in bzr.dev?23:48
lifelessBasicOSX: it is23:48
BasicOSX:%s/merges/merged/23:48
johnjosephbachirlifeless Peng_ okay cool cool... sooooo what do i do? :)23:48
lifelessjohnjosephbachir: well, what do you want to achieve?23:49
BasicOSXSorry on the busy and very bumby, typing going to be hard23:49
BasicOSXbusy=bus :-)23:49
BasicOSXtype23:49
lifeless:)23:49
johnjosephbachirlifeless: i waaaant.... to make my source tree reflect... my commits? (maybe i have the wrong terminology)23:49
lifelessBasicOSX: so am I understanding correctly? [you can say yes/no] - we merge it to .dev, and to 1.1423:50
Peng_johnjosephbachir: After uncommitting, if you want to throw out all of your noncommitted changes, use "bzr revert".23:50
* igc breakfast23:50
johnjosephbachirPeng_: hmm... just tried it... no change to files23:50
BasicOSXyes .dev, yes 1.1423:51
lifelessBasicOSX: thanks! will get right on it23:51
Peng_johnjosephbachir: Because you went and committed all of the changes again.23:51
johnjosephbachirPeng_ lifeless oh maybe i didn't commit... the uncommits properly, because i didn't revert after doing the uncommits?23:51
johnjosephbachirhaha, okay23:51
Peng_johnjosephbachir: You don't commit an uncommit. When you run uncommit, it removes the revision from the branch's history.23:52
BasicOSXcan yyuou clarify on the maikkling llist (eerrr!) so people aren't freaking out? <- lifeless23:52
Peng_johnjosephbachir: After running "uncommit", it's done. There's nothing left to do.23:52
johnjosephbachirPeng_: OIC23:52
johnjosephbachirthanks23:52
BasicOSXi will follow up properly once I get home23:52
Peng_johnjosephbachir: When you ran "commit" afterwards, all you did was commit all of the changes in your working tree, including the changes from the 2 revisions you uncommitted.23:52
johnjosephbachiroh noes!23:52
johnjosephbachirPeng_: okay, thanks, i'll try to apply all that knowledge and see where i get23:53
johnjosephbachirPeng_: yes, working perfectly now. hooray for bzr!23:53
Peng_:D23:53
lifelessBasicOSX: sure thing23:54
=== abentley1 is now known as abentley
BasicOSXalmost out of battery back tonight23:55
lifelessciao23:55
=== thewrath_ is now known as thewrath
thewrathhey all23:58
thewrathi got bzr working23:58

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!