/srv/irclogs.ubuntu.com/2009/09/01/#bzr.txt

lifelessigc: hai00:01
igcmorning all00:09
igchi lifeless00:09
pooliehi igc00:10
igchi poolie, jam00:10
lifelessigc: have you used netbeans as a datasource for benching?00:11
igclifeless: no00:12
lifelessigc: I ask, because one of the drizzle folk was bemoaning the lack of a bzr scm module00:12
lifelessso I pulled the thing... 1.7GB, 90K files00:12
lifeless133K commits00:12
igclifeless: as in an addon for NetBeans?00:13
lifelessyeah00:13
lifelesstheir addons are all in tree00:13
lifeless_pain_00:13
igclifeless: yuk00:13
igclifeless: it was nice to see qbzr-eclipse 0.7 out overnight00:14
igcand I'm pretty sure there's someone working on a C++ Builder/Delphi integration along those same lines00:14
igclifeless: http://bazaar-vcs.org/IDEIntegration/Guide00:15
igclifeless: I'm pretty sure nick put together the original qbzr-eclipse integration in around 2 days00:16
igclifeless: so it's typically easy to get *something* useful going00:17
igclifeless: my main reluctance with doing an integration myself is ongoing ownership - it's better if someone using a given IDE everyday owns it IMO00:18
lifelessigc: I agree; I don't really like the different UI that qbzr-* gives though00:20
ronnyigc: are you Ian Clatworthy?00:20
igcroony: yes00:21
igcronny: ^00:21
ronnyigc: great, well, what do people do that do api-level integration instead of subprocess levle integration :P00:21
igcronny: I'm not sure I understand the question ...00:22
igcronny: you can always call into bzrlib and into qbzr itself if you want00:23
* ronny is the author of anyvc, a vcs abstraction lib, i just import bzr instead of calling to it00:23
igcthough the qbzr API has no stability guarantees00:23
igcronny: the point behind using the qbzr applets is to same the engineering time required to design, develop and test 30-40 dialogs00:25
ronnyigc: well, does it have version metadata, and some more convience tools for common ops than bzrlibs?00:25
ronnyigc: im not sure if qbzr wil lbe that helpfull for me, as i need the dialogs for other vcs's, too00:26
igcronny: right. Down the track. I'd hope to see qbzr working in combination with bzr-svn, etc. to provide a common GUI over multiple VCSs but it sounds like you're solving a different problem00:28
ronnyigc: yup, i'll probably have to support the svn integrations anyway at some point00:29
jelmerfwiw the combination of qbzr and bzr-svn should already work00:33
jelmerJohn Szakmeister did quite a bit of testing with it and reported bugs00:33
lifelessigc: hg fastexport is kinda slow :(00:40
igclifeless: yep00:41
igclifeless: on packs, so it bzr-fast-export; 2a is a much happier place for bulk data export/import00:42
igcs/it/is/00:42
lifelessyeah00:43
lifelessI should hope so :P00:43
poolieigc, so i liked your wishlist blog postn00:48
pooliebut i think we need to distinguish "things that will actually block 2.0" from "things we'd like to do" :-/00:49
pooliebecause that list is pretty incompatible with hitting karmic00:49
igcpoolie: yep00:50
poolie2.0 is kind of trying to be two different things00:51
pooliethe release that makes 2a the stable format00:51
poolieand the "everything's great and finished" release00:51
fullermdIt's also trying to be the "Crap, we have to hit karmic" release...00:53
igcpoolie: no, it's not the later00:54
igcpoolie: 2.0 is trying to be 2.000:54
igcpoolie: that does mean a new format00:55
igcpoolie: it also means "now's a god time to take another look at Bazaar if you're not using it"00:55
igcgood00:55
pooliesure00:55
pooliei guess i'm glad you're raising these things but the week we're trying to freeze the code is a00:56
pooliewell, maybe not a great time00:56
poolie:/00:57
igcpoolie: that's not totally fair ...00:57
igcI've been raising better packaging for weeks and weeks now on multiple email lists00:57
pooliethat's true00:57
poolie-> phone00:58
flacosteif I use bzr-svn to merge a svn branch onto the trunk, will svn grok the merge?01:28
lifelessjelmer: ^01:28
flacostei was talking with a guy last week at Agile2009 who use git-svn01:29
flacosteon windows01:29
flacostehe finds it painfully slow01:29
flacosteand that was another pain point for him01:29
flacostei want him to have another try at bzr01:29
flacostehe try it out last year01:29
lifelessbbs fooding01:30
igchi jelmer01:46
igcjelmer: I think qbzr is working over bzr-svn01:47
igcjlemer: I wonder if we need some tweaks though, e.g. a gui way of doing a dpush" or whatever name we selected for that operation01:47
igcjelmer: ^^^01:48
=== CardinalFang is now known as CardinalFangZzzz
lifelessjelmer: ping02:11
igcbbiab02:27
pooliespiv: hi, late call?02:39
spivpoolie: sure02:42
pooliewill call in 2m02:42
spivHmm, jam's mail server is bouncing mail.03:00
rbelemanyone knows which command in !bzr shows just the changes from a given revision?03:44
bob2what is !bzr?03:44
rbelembob2, ops... typo03:44
rbelem:D03:44
fullermdThe logical counterpart of ~bzr03:45
rbelemehehehe03:45
bob2bzr diff -c xxx03:46
rbelembob2, that was exactly what I was wanting03:47
rbelemthanks a lot!03:47
* rbelem leaving03:52
* igc lunch03:56
=== AfC1 is now known as AfC
andrewksis there a way to make bzr missing walk up a sequence of branches?04:50
AfCup?05:06
tbradshawLarstiQ: a status update:.  After recompiling subvertpy, I was able to get things to commit properly to the svn repo!  Thanks again for your help earlier today.05:08
andrewksAfC: transitive relationships.  the parent of the parent branch, etc05:41
AfCandrewks: so, to my knowledge, no, that's not built in. But it wouldn't be _that_ hard to [shell] script, especially if you assume that branches are sanely set-up, and that `bzr diff -r ancestor:` does what you want it to in each branch. Or you could parse `bzr info` output. etc05:45
andrewksyes, I'm going with sane locations for now.  This isn't something I have to do often05:45
fullermdAFAIK it all chains fine, so things like "parent:parent::parent" would DTRT.05:48
fullermdAlso really screw up your brain trying to read, but hey, you can't have everything...05:48
fullermdOr maybe it doesn't 'cuz my brain is screwed up.  It's probably too late for anything I say to be worth listening to today...05:50
AfCfullermd: hm. Not so sure about that: `bzr status -r ancestor:ancestor:` just now didn't work06:00
vilahi all07:20
pooliehi vila07:43
vilahey !07:43
lifelesshttps://bugs.launchpad.net/bzr/+bug/42240307:46
ubottuLaunchpad bug 422403 in bzr "bzr log -v -n 0 | less on drizzle takes ~ 3-4 secs before displaying anything in less" [Undecided,New]07:46
lifelesshi vila07:46
vilaadd --forward to that and we should be quite close to the slowest possible context07:48
lifelesshe runs this all the time07:49
lifelessto see what he has pulled07:49
vilaI think Ian answer makes sense, drop -n007:49
viladrill down only when needed07:49
vilathat's the only work around I can think of07:50
pooliespm: actually maybe we should talk here07:50
spmpoolie: heh. indeed. just reading now.07:50
poolievila: well, it can be an open bug still07:50
poolielet's make sure it's deduped and clear: takes too long to start showing revisions for indented less07:50
vilauntil we are able to calculate revnos lazily, that bug will remain open... lol, fully agree poolie :)07:50
pooliesure07:50
spmpoolie: err. I'm not sure I can do that - I think I fail on the "friendly sysadmin" part???07:51
pooliesaying it depends on the other bug is ok07:51
pooliedamn07:51
poolieneed 3 wise men too07:51
lifeless[he didn't tell me he used -0 :P]07:51
vilalifeless: they just love to trick us :-)07:51
poolieit might be worth drilling into why he's doing this07:52
poolieis it that he really wants to see all the history and -n0 is the best way07:52
spmpoolie: yeah, that looks fairly straight forward. shall I start to make it so?07:52
pooliewell, i guess you'll still need incremental revnos07:53
pooliespm, yes, how about turning off pqm first07:53
poolieat least for that branch, or globally07:53
poolieand let's make an extra adhoc backup of it, then run check07:53
spmglobally for bzr, yes. backups is good.07:53
vilapoolie: we have incremental revnos if we display mainline revisions only :-) We start at the top and decrement, easy.07:55
vilas/top/tip/07:55
poolieright07:57
spmpoolie: lifeless: I can't help but feel I'm missing something really obvious here. the master location is (pqm config) /home/pqm/archives/thelove/bzr/2.0 but that's only a 44Kb directory. 1.18 etc are the same. ??07:59
pooliespm, that's probably a bzr branch with no working tree08:00
pooliewhat does bzr info show you?08:00
spmpoolie: it is; would it really be that small tho?08:00
vilaspm: and a shared repo above it08:00
spmright. yes.08:01
spmshared repository: /home/pqm/archives/thelove/bzr08:01
spm  repository branch: .08:01
vilaspm: 44Kb now sounds even too much :)08:02
lifelessspm: cd to /home/pqm/archives/thelove/bzr08:02
lifelessspm: upgrade *that*08:02
spmvila: heh. well a sum total of 570Mb is more the ballpark I was expecting.08:02
lifelessspm: same as launchpad, shared repo.08:02
poolieok08:02
poolieso tar up the whole thing before starting?08:02
poolieand then run check in there08:02
poolieoh also we should check what version of bzr you're using there08:03
vilanot sure, it will make a difference when run locally, but upgrading the test slaves, I noticed huge differences in performances between 1.17, 1.18 and 2.1dev, I think 2.0rc1 at least is needed here (or did spiv patch regarding IDS landed in bzr.dev only ?)08:04
spmso tarball: ~/archives/thelove/bzr-backup-2.0.tar fwiw08:04
spmwe have bzr 1.17 locally; I can moderately easy create a special bzr of any version needed?08:05
poolieusing 2.0rc1 would be good08:05
poolieor the ppa nightly08:05
spmppa's is hard. build from source/branch is easy08:05
spmamusingly :-)08:06
vilalp:bzr/2.0 then08:06
vilahmm, wait08:06
poolieyes, that'd be good08:06
lifelessvila: need 2.0 on launchpad before it will be fast :P08:07
lifelesspoolie: re conversion performance: this is what spiv and I meant by 'very slow without network deltas'08:07
lifelesspoolie: its not hanging, its doing millions of little round trips on the VFS08:08
vilalifeless: it already makes a difference when pulling from lp08:08
poolielifeless: it's not doing any network io08:08
poolieas observed by trace08:08
lifelesspoolie: oh, thats extremely odd08:08
pooliestrace*08:08
vilapoolie: but didn't you have CPU consumed ?08:09
lifelessdid you try ctrl-\ and inspect?08:09
poolieyes, that's the bug i filed08:09
lifelessok08:09
poolienow i'm fixing bug 341535 :)08:09
ubottuLaunchpad bug 341535 in bzr "hpss SmartMedium doesn't handle eintr" [Medium,In progress] https://launchpad.net/bugs/34153508:09
lifelesslooks like a server bug of some sort08:09
lifelesshmm08:09
vilaI didn't comment on the bug, but I had symptoms pretty close to yours (poolie) except my pulls finished...08:10
vilaspm: so, lp:bzr/2.0 is already a bit more than 2.0rc1, nothing to be worried about I think, but if you keep notes on the upgrade it will be good to note the revno you used08:12
spmvila: 'kk08:13
spmbtw. "Setting ssh/sftp usernames for launchpad.net." how do I stop bzr from doing that? it creates that )(*^)*(&^(%^&%$&*%^$*&%ing authentication.conf file and hence fails to connect. I assume by not using lp:bzr/blah syntax08:14
vilaerr, how do you connect ?08:15
vilayou use bzr-pqm user right ?08:15
vilaon lp I mean08:15
spmbzr branch bzr+ssh://bazaar.launchpad.net/~bzr-pqm/bzr/2.0 bzr-2.0 <== works; bzr branch lp:bzr/2.0 bzr-2.0 <== fails08:15
spivWhy is the existence of the authentication.conf a problem?  Because it's putting in 'spm' rather than 'bzr-pqm'?08:15
spmspiv: tbh, I don't precisely know, but using that lp:bzr breaks it totally. it's bzr-pqm, I'm sudo'd as the pqm user.08:16
vilasudo doesn't matter, what is you $HOME ?08:16
spmoh that's right - we have aliases "somewhere" that map users keys to branches or somesuch.08:16
vilaauthentication.conf is such a map !08:17
spm.ssh/config08:17
vilaalso08:17
vilabut looked at after :)08:17
spmISTR that the issue is around the *other* accesses that this uid has; all with diff keys08:18
vilaspm:  what is your $HOME ?08:18
spm /home/pqm08:18
vilawhat is /home/pqm/.bazaar/authentication.conf  content?08:19
vilaLOL, I never went to https://edge.launchpad.net/~bzr-pqm before :D08:20
spmvila: [Launchpad] host = .launchpad.net ;; scheme = ssh ;; user = launchpad-pqm08:21
vilaso launchpad-pqm should be bzr-pqm ? Oooooooh, that's the problem ! It's used for launchpad and bzr right ?08:22
spmvila: launchpad no, but other projects yes.08:23
spmsorta.08:24
vilaspm: and they need that launchpad-pqm identity ?08:24
spmheh. they have their own. like bzr-pqm :-)08:24
spivThe same PQM instance is used for multiple projects?08:24
spmyeha. what spiv said. thanks andrew :-)08:24
spivThat seems strange to me, no wonder we're having trouble :)08:25
vilahaaa, I think I get it, the lp directory service  is the one that create auth.conf, so that explains the difference08:26
poolienice image for pqm :)08:26
vilapoolie: made me LOL yes :)08:26
spmhuh. default balleny doesn't have pyrex installed, just the bzr pqm chroot does.08:26
poolievila, so on bugs like the pqm speed one, can we change the description/subject to something reflecting the general bug?08:27
vilaspm: strictly speaking the lp dir. service is wrong here, it shouldn't create an auth.conf file because... using different users to connect to the same host is not a case that auth.conf can handle (I think(08:28
vilapoolie: pqm speed bug ? # ?08:29
pooliesorry, i meant log speed08:29
spmvila: fair enough08:29
vilaspm: the bad news is that the only work-around I can think of is 1) stop using  lp: shortcuts, 2) always mention user@bazaar.launchpad.net in urls08:30
spivOr set BZR_HOME differently for each pqm 'instance', as a substitute for having different system users.08:31
spmvila: heh. 1, we'd kinda figured out, if not enunciated clearly. 2. ?08:31
spmspiv: ahhh. that's easily doable I 'spect08:31
vilaspm: spiv idea is better :)08:32
vilaspm: same effect: the user is explicit so auth.conf is not injecting a bad one anymore08:33
spmvila: spiv is more than just a teddy bear; you heard it here first.08:33
viladropping bear ?08:33
spmvila: ah. right.08:33
spmvila: so the upgrade/check. /srv/pqm.ubuntu.com/chroot-amd64/home/pqm/bzr-2.0/bzr revno /srv/pqm.ubuntu.com/chroot-amd64/home/pqm/bzr-2.0 ==> 464708:35
poolieseems about right08:38
pooliewe should try check on it?08:39
spmis running atm. just "/.../bzr check"  yes?08:39
spmerr.. in /home/pqm/archives/thelove/bzr to be more precise08:40
poolieright08:40
poolieand did you tell pqm to stop processing mails?08:41
pooliethanks for doing it today btw, i know it's getting late08:41
spmpoolie: aye, processing bzr ones at any rate. is cool, I had to work later today anyway.08:43
vilawe can't 'bzr log' without showing any revnos at all ? Did we lose that or did I dream it ?08:43
pooliei don't recall having that08:43
poolieit might be useful08:43
vilaI thought --show-ids was doing that but no08:43
vilapoolie: I think you should create a 2.1 milestone,08:49
pooliegood idea08:49
vilacreating 2.1 release branch may wait though08:50
poolievila, it should be something different, like --no-revnos08:50
vilapoolie: I agree08:50
poolievila, do you want me in particular to do it?08:50
pooliei don't mind, but don't you have access?08:50
poolielifeless: i'm trying a conversion here and getting08:51
vilaoh no, it was just that I wanted to check with you first (you may have had (sp ?) a reason for not creating it)08:51
pooliebzr: ERROR: The file id "mpregen-20070411063203-5x9z7i73add0d6f6-1" is not present in the tree <bzrlib.inventory.CHKInventory object at 0x4372650>.08:51
vilapoolie: it was also mentioned in https://code.edge.launchpad.net/~vila/bzr/releasing-clarified/+merge/10854 and really that's a new *series* that should be created :)08:53
poolieright, it should be both08:53
pooliethough, um08:53
vila:)08:53
poolieactually i'm not sure how this will interact and whether the milestone should be on trunk or on the 2.1 series08:53
poolieprobably the second, for the final release08:54
pooliewere you wanting to target something now?08:54
vilano08:54
vilabut someone want, and in principle, since bzr.dev now says 2.1dev, 2.1 should exist08:54
vilathat's why I repeat the "create milestone" mantra several times in releasing.txt, because that's the one that is the most often forgotten08:55
vilabut no urgency, just something I wanted to get out of my mind and onto the RM shoulders :)08:55
vila(that's the famous: "you can sleep now, that's not *your* problem anymore" joke :)08:56
poolie:)08:58
vilapoolie: bzr-gtk create milestones in the trunk series, I'm not sure that's better, but just have a look at https://edge.launchpad.net/bzr-gtk/+series08:58
spmfyi: bzr check still running. just going afk for a bit; will be back in 10.09:00
poolievila, they may not branch for releases?09:00
poolievila, my point about the bug title is: don't mention "1233 revisions" or "on mysql" unless it really is specific to that case09:02
vilaindeed. I did the last two releases, but I just followed the existing practice. In retrospect, I'm almost sure it wasn't really a conscious decision, just a simplification that lp allowed09:02
poolieusers always make them specific but i'm sure it's clearer if we make them as general as is appropriate09:02
pooliehelps with removing dupes etc09:02
pooliei'll do a 2.1 series now09:02
pooliethe little diagram is interesting09:02
vilapoolie: good point09:03
vilayes, that's why I pointed you there09:04
lifelesspoolie: when did you last check your repo ;)09:04
jmllifeless, "Handing over to a machine to do CI is just as expensive as handing to a colleague." -- Handing over to a machine is probably a little cheaper09:04
vilait captures the release process amazingly09:04
lifelessvila: the other thing forgotten is 'create NEWS headers'09:04
poolielifeless: just now :-O09:04
jml(advogato sucks for replies)09:04
vilalifeless: I mentioned it in the cover letter09:04
lifelessjml: for you, not for the machine :)09:04
vilaI thought you read it there first, but that's just more telepathy obviously :)09:05
vilaoh, no *create*, yes, I forgot that, I thought you were referring to NEWS header ordering with overlapping releases09:05
vilabut both are tied anyway09:06
lifeless:P09:06
poolielifeless: i'm just checking it again now in a clean local branch09:07
jmllifeless, when you hand off to humans, you almost always have to transfer knowledge. that's less commonly true for machines.09:07
lifelesspoolie: also are you upgrading with the latest ?09:07
jmlalthough there's probably an argument-by-different-definition to be made there09:07
poolieyes, trunk as of today09:07
pooliei might use 2.0 instead though09:07
lifelessjml: How about this: When you hand off to a human, you can stop worrying, but the act of handing costs more. When you hand off to a machine, you know its coming back to you if it fails, so there is some cognitive load.09:08
lifelessjml: And I'm asserting that these, while different, are approximately the same09:08
lifelessjml: what blog site did you end up using?09:09
jmllifeless, I use blogger.09:10
lifelesswhat would you like to see them improve?09:10
jmllifeless, I think I'll use wordpress for my next project though.09:10
lifelesshosted or self-run?09:10
jmllifeless, ease of pasting code samples :)09:10
lifelessand why wordpress?09:11
jmllifeless, I host my own blogs currently, blogger sftps them to my site09:11
lifelessinteresting; and does your feedback too?09:11
lifelessto your site, or from your site?09:11
jmlblogger uploads to my site09:12
lifelessnice09:12
jmlI actually have no idea how comments work, but they do work.09:12
jmllifeless, wordpress because it seems to have the biggest community and all the blogs I see that look good & use free software seem to use wordpress09:12
poolielifeless: i just reproduced this failure on a fresh branch of bzr from lp into a fresh directory :/09:13
jmlit's also quite flexible.09:13
lifelesspoolie: \o/ dogfooding09:13
lifelessjml: and you'll self host again?09:13
jmlhow do I get pqm-submit to not care about the fact that I lack a local copy of the branch I want to submit?09:14
jmllifeless, probably.09:14
lifelessthough I understand that for wordpress that means more than it did/does for blogger09:14
lifelessjml: patch it09:14
lifelessjml: its on my 'do it the next time it annoys me' list.09:14
vilajml: what are you submitting then ? pqm-submit is more or less supposed to ensures that *you* are submitting *this*09:15
jmlvila, I'm submitting a patch on someone else's behalf.09:16
vilajml: irrelevant :) In principle you still need to "sign" *this*, where is *this* ?09:17
lifelessvila: nah, thats recent09:17
lifelessvila: pqm-submit is 'tell pqm what to do'09:17
lifelessvila: there is no good reason to prevent clueful use being convenient.09:17
vilalifeless: I know, hence my "in principle" and "more or less"09:18
lifelessvila: I'm arguing the principle is unclear :)09:18
lifelesslike the bug on switch. boy that hurt :(09:18
jmlhere's what I want09:18
vilaWe agree :) I'm trying to avoid popularizing a hole I dislike in pqm-submit :-)09:19
jml(as a hacker of Launchpad)09:19
lifelessa fast test suite09:19
jmla way of submitting an approved merge to land, conditional on tests passing09:19
lifelessa great user experience09:19
vilalifeless: :D09:19
pooliei'm posting a reproduction on bug 42242309:19
ubottuLaunchpad bug 422423 in bzr "NoSuchId error upgrading to 2a" [Critical,Confirmed] https://launchpad.net/bugs/42242309:19
jmla way of submitting an approved merge to land09:19
poolieit's just a tarball from lp09:19
jmllifeless, those too.09:19
pooliei have to go out with S now, but i'll come back and look at this09:20
pooliespm, we'd probably better not proceed until we get to the bottom of it09:20
lifelessjml: please, its pretty obvious; take the code, opportunistically fix it. Use it and submit a merge.09:20
lifelessjml: (like I did for removable :P)09:20
jmllifeless, suree.09:20
lifelessjml: by obvious I mean that the code is small and simple.09:20
jmllifeless, yeah, I'll do it the next time I get a chance09:22
jmlbut I don't have any more time to hack this evening09:22
* igc dinner09:22
jmland if I did, I really ought to use it to pack, not hack.09:22
spmpoolie: ok, at this stage the check actually failed.09:25
poolieinteresting09:26
poolieso09:26
pooliewe should probably reenable pqm, and not proceed further until we know what's causing this09:26
spmhttps://pastebin.canonical.com/21673/09:26
spmoki09:26
spmbzr pqm re-enabled09:27
pooliethanks09:29
pooliei'm going to look at it tomorrow, or at most later tonight09:29
pooliespm is that pastebin before it failed??09:29
poolieit has no errors09:29
vilafound error:Internal check failed: revno does not match len(mainline) 1649 != 167409:30
spmI'm not sure how serious an error that is? recommendations to RTFM will be ignored. :-)09:30
vilathat's a bit strange, and I can't see if it's for 0.8 or 1.8... 1.8 has 3766 revisions in the mainline anyway...09:34
vilaspm: ok, 0.8 has 1674 revisions so that's the one09:39
vilaspm: I'm pretty sure reconcile will fix that09:41
spirov92I have 2 branches in the same directory, let's say branch1 and branch2, with a similar file structure. Can I copy branch1/lib/some_file.php to branch2/lib/some_file.php using bzr?11:05
emmajaneping poolie11:19
johnfabentley: will you be doing a 2.0.0 release of bzrtools?13:45
abentleyjohnf: Yes.13:45
johnfjelmer: same question for bzr-svn :)13:46
jelmerjohnf: I'm going to release a bzr-svn matching bzr 2.0, probably bzr-svn 1.013:46
jelmerjohnf: not sure yet for bzr-git13:46
jelmerhas anybody seen james_w recently?13:57
=== jam1 is now known as jam
=== jam is now known as jam1
=== jam1 is now known as jam
=== kiko__ is now known as kiko
=== CardinalFangZzzz is now known as chad
=== chad is now known as CardinalFang
igcnight all15:03
CameronPHI there!15:22
CameronPI just installed bzr!15:22
CameronPTrying to merge my first lot of changes back to main branch - through tortoise bzr , i cant find a way to merge15:23
jamis anyone else seeing launchpad be a bit slow to load today?16:13
=== kiko is now known as kiko-fud
=== deryck is now known as deryck[lunch]
=== beuno is now known as beuno-lunch
=== garyvdm_ is now known as garyvdm
=== deryck[lunch] is now known as deryck
=== beuno-lunch is now known as beuno
=== gcerquant_ is now known as gcerquant
=== EdwinGrubbs is now known as Edwin-lunch
=== kiko-fud is now known as kiko
=== jkakar_ is now known as jkakar
=== Edwin-lunch is now known as EdwinGrubbs
Kobazhow do you perminantly remove something from a branch19:50
luksyou can't19:51
Kobazaww, i thought i remember reading something somewhere that you could19:51
jelmeryou can remove a revision from a *branch* by using "bzr uncommit"19:52
Kobazuncommit only removes from the head it seems19:52
garyvdmKobaz: You can do it, by branching it to a new branch, and deleting the old branch. This won't remove it from other branches that may have the revision.20:08
Kobazk20:08
Kobazso if you like, delete stuff, and then branch?20:09
Kobazor do uncommits, and then branch?20:09
garyvdmHi jelmer20:09
garyvdmjelmer: was going to ask if you knew of any code that uses ui.get_username, other than bzr-svn, but I see that bzrlib/config.py uses it.20:11
garyvdmdo uncommits, and then branch20:14
lifelessmoin20:57
lifelessjam: ping21:00
jammorning lifeless21:00
lifelesshowzitgoing?21:00
jampretty good21:03
lifelessjam: so, recompressing21:03
jamI'm trying to evaluate real-world effect. but making branching from scratch significantly slower isn't a real gain, IMO21:05
jamif it was only incremental, then maybe21:05
lifelessWithout this we will still fragment21:06
lifelesssue to incremental pushes to common repos21:06
lifelesss/sue/due/21:06
jfroy|workjelmer: wasn't there a way to see the svn revision associated with a particular bzr revision? I can't seem to find that info anywhere.21:07
lifelessnow, I desire us to have a hybrid, but its not clear to me that we should block 2.0 on having a hybrid21:07
jamlifeless: incremental pushes will eventually autopack21:08
jamso we won't fragment in the same way that we were21:08
lifelessjam: yes, but that argument applies to the prior code too21:09
lifelessthere were two causes of fragmentation: separate push events, and group filtering21:09
lifelessthere is currently one cause of combining - pack21:10
jamlifeless: sure, though the latter was a much bigger portion of it21:10
jamlifeless: well, autopack combines21:10
lifelessjam: yes21:10
jamso incremental push /pulling has a chance to pack everything but the initial stuff21:10
lifelessjam: I'm not classing autopack as fundamentally different21:10
lifelessjam: except that the user doesn't /choose/ it21:11
lifelessjam: right21:11
lifelessso an initial pull of LP, with large amounts of history, is going to take ages before the next auto-complete-pack21:11
lifelessbut the data that was pulled will be read from many many times21:12
lifelesswow! hg fast export has sbeen running for 24 hours now21:12
lifelessstill not finished21:12
jamlifeless: exporting what?21:12
lifelessnetbeans21:12
lifeless40G stream so far21:13
lifelessI was looking at the chance of quick-hack to make an hg plugin for it21:13
lifelesssadly way to high a cost to fit in opportunistic coding time21:14
lifelessbut having done hg branch (1.6G ofdata, 90K files, 133K revs), I figured I may as well get a test case for 2a from it21:14
jamlifeless: do you mean a bzr plugin for netbeans ?21:14
lifelessyes21:15
* lifeless adds caffeine21:15
jamargh.... with a fresh windows install, I decided to try py26, overall nice, but now pycrypto spewes 2 deprecation warnings everytime I connect via ssh :(21:16
lifelessurgh21:16
lifelessrmeinds me21:16
jamI think there is an open bug about pycrypto and python2.621:16
lifelessI should send the python 2.6 fixes to pyrex upstream21:17
jambut they haven't released a new pycrypto yet21:17
jamlifeless: the Exception issues?21:17
lifelessyeah21:17
jamlifeless: I'd rather we switched to cython :)21:17
lifelessjam: I want us to reevaluate our external deps21:17
lifelessI'd like cython, testresources, testscenarios, subunit, sphinx, all to become hard build deps21:18
lifelessWe also need to start versioning the output of cython so we can build it on pqm21:18
lifelessand elsewhere21:18
lifelesshave you converted mysql-server into 2a?21:19
jamlifeless: not recently, but I did do testing in the past w/ mysql21:19
lifelessI'm going to talk focusedly at drizzle today21:20
lifelessmtaylor: ^21:20
beunomwhudson, +1 to upgrade loggerhead to 2a?  it's alrady 1.9-rr anyway...21:20
jamlifeless: so I think there is distinctly several possible tradeoff points for the balance between recompression on the fly none, some, all. I think unordered + none is a better tradeoff today than all, and we can write a 'some' implementation for the next release.21:20
mtaylorlifeless: ola21:21
jamlifeless: http://bazaar-vcs.org/Roadmap/BrisbaneCore/Details scroll down to: $ du mysql-5.1-test21:21
lifelessmtaylor: drizzle should upgrade to 2a21:21
jammysql 5.1 at that stage went from 501MB => 170MB on disk21:21
mtaylorlifeless: it's ready for us to convert all of our branches?21:22
lvhapparently so!21:22
lvhdash is doing it for twisted21:22
lvhand twisted is super important21:22
jamlvh: launchpad itself has been using it for a while21:22
lifelessmtaylor: the bug you encountered on libcpuinfo is fixed21:23
mtaylorok. cool21:23
lvhjam: yeah, apparently my fears of pre-release non-default repo formats eating my data is unfounded21:23
mtaylorlifeless: what's the version of bzr that it requires?21:23
lvhs/is/are/21:23
lifeless2.0rc1 should be pretty damn solid, even though we have landed more bug fixes since21:23
lvhmtaylor: 1.16 or something.21:23
lifelessmtaylor: I suggest 2.0rc121:23
lvhmtaylor: it's been around for a few releases21:23
lvh2, I believe21:24
lifelessmtaylor: 1.16 and up can read-write it21:24
lifelessmtaylor: but there are bugs in those versions that make it desirable to upgrade all the way21:24
mtaylorso, I have to get about 50 people to upgrade their bzr ... so I need to be real specific. do I need to have them upgrade to 1.16? or to 2.0rc1?21:24
lvhlifeless: if I want to use 2a for my branch I have to wait until the maintainer for the main project updates everything to 2a first, right?21:24
mwhudsonbeuno: sure21:24
lifelesslvh: if they are on a rich-root format, you can upgrade early and send bundles21:25
lifelesslvh: if they aren't on a rich root format, you have to wait21:25
lvhI think they are.21:25
=== Noldorin_ is now known as Noldorin
beunoPeng_, upgrading LH to 2a21:25
jamlifeless: it seems the bazaar wiki will lock you out if you hit Preview too frequently... :(21:26
lifelessjam: lol21:26
* mtaylor now considers whether to upgrade all of our branches to 2a while brian is at burningman21:26
lifelessmtaylor: let me get an estimate for drizzle21:27
jamand, of course, it doesn't tell you how long the lockout period is, and it warns that submitting too soon may increase the lockout time...21:27
jamis it seconds, minutes, an hour?21:27
jamargh21:27
lifeless#is21:27
lifeless8-way machines <321:28
lifelesshah, conversion error21:28
mtaylorheh.21:29
* mtaylor will wait until that is fixed :)21:29
beunoanyone know how to remove a backup.bzr dir from LP?  hitchhiker tracebacks when using rm21:29
* lifeless reconciles drizzle21:29
beunoabentley, ^ any ideas?21:30
lifelessbeuno: whats the traceback?21:30
lifelessbeuno: also, I know that lftp works21:30
mtaylorbeuno: lftp21:30
abentleybeuno: rmtree.21:30
beunowow21:30
beunothat's it, rmtree21:30
beunothanks abentley21:30
beunoand lifeless and mtaylor21:30
abentleybeuno: np21:30
beunowe really need to fix this to smoothen upgrades21:31
* mtaylor AGREES21:31
abentleybeuno: See also: https://answers.edge.launchpad.net/launchpad/+faq/67521:31
* mtaylor would sort of love it if there were a button on launchpad that said "upgrade"21:31
beunomtaylor, rockstar had that on his plate for a while21:31
beunoI even got a nice icon for him21:31
beunobut something... happened21:31
=== EdwinGrubbs is now known as Edwin-afk
mtaylorhewh21:32
* rockstar looks up21:32
mtaylorrockstar: bzr branch upgrade button ftw?21:32
lifelessmtaylor: There is a bug. Put it in your wishlist for lp :)21:32
lifelessunless you've done one already21:32
mtaylorlifeless: prolly have :)21:33
mtaylorlifeless: I think around the time I upgraded drizzle to 1.921:33
lifelessmtaylor: there is a thread on lp-users21:33
lifelessmtaylor: about 3 wishes for lp21:33
lifelessmtaylor: it is to that that I refer21:34
mtayloroh, right21:34
lifelessI'm getting 6 GB of ram for this machine today21:35
lifeless\o/21:35
rockstarmtaylor, so, the work is basically done, except that we need to actually upgrade the branch without blocking your work.21:35
lifelessrockstar: really?21:35
lifelessrockstar: I would have thought blocking there work was expected21:35
rockstarlifeless, you were there when Mark told us we need to.21:35
rockstar(it was at lunch at AllHands)21:36
lifelessrockstar: oh right. sadness21:36
rockstarlifeless, it's not a big deal, and actually an excellent point.  However, then we got other things.  I'm sure we'll get back to it soon after 3.021:36
lifelessrockstar: well if its easy to go great, its obviously better than blocking. OTOH I still think that most projects are so small they wouldn't notice or care21:37
lifelesss/to go/to do/21:37
lifelessjam: I want to use knowngraph in reconcile/check21:38
=== kfogel is now known as launchpad
lifelessjam: can you think of any gotchas?21:38
rockstarlifeless, I think the most difficult thing to worry about is the chicken and egg upgrading of stacked branches.21:38
=== launchpad is now known as kfogel
lifelessrockstar: we've fixed that upstream21:38
lifelessrockstar: bzr upgrade URL_of_stacking_branch just works now21:39
lifelessyou can't use the branch till thats done - so lp should do a reverse graph walk and fix them up21:39
rockstarlifeless, oh, awesome.  I think I have some projects to upgrade then.21:40
lifelessuse 2.0rc121:40
jamlifeless: I don't know of any specific gotchas, other than you need to have the whole graph, but you should have that for check/reconcile21:40
lifelessnot because its strictly needed for that21:40
lifelessbut it has the most fixes21:40
jamIt doesn't currently expose a way to get the individual parents21:40
jambut garyvdm put together a patch for that21:40
lifelessbugger :( reconciled drizzle fails to upgrade too.21:41
* lifeless bugginates21:41
garyvdmHi jam and lifeless21:41
jamso garyvdm, was the code you were using already using iter_merge_sort?21:41
jam(the code you 'improved' to start using KnownGraph)21:41
jamI believe it is Branch.iter_merge_sorted_revisions()21:42
jamas if you want to look for a perf improvement, it iter_merge_sorted_revisions was updated to use KnownGraph internally21:42
garyvdmjam: let me have a look21:42
jamso you may need to compare between versions of bzr, rather than qbzr w/ vs w/o KnownGraph support21:42
garyvdmjam: I we were previously using bzrlib.tsort.merge_sort21:44
garyvdmNot Branch.iter_merge_sorted_revisions, because we have to handle multiple branches21:44
jamah, ok21:44
garyvdmjam: If you are intrested: lp:~garyvdm/qbzr/knowngraph21:46
garyvdmjam: I need so time to profile it in detail to see why it is not faster.21:46
jamgaryvdm: taking a look21:46
jamgaryvdm: so... the *biggest* improvement you could get is switching to the find_ancestry stuff, which doesn't yet support multiple sources21:50
jammerge_sort itself is probably at most a second or so of your runtime21:50
garyvdmJam: I agree21:51
garyvdmjam: I also can only initialy load the mainline. That would be a big win.21:52
jamgaryvdm: you might try something like this: http://paste.ubuntu.com/263407/21:55
jamand see if that gets you somewhere nice21:56
=== cprov is now known as cprov-afk
lifelesshi garyvdm22:12
lifelessjam: https://bugs.edge.launchpad.net/bzr/+bug/42284922:17
ubottuLaunchpad bug 422849 in bzr "InconsistentDelta error upgrading drizzle repo to 2a" [Critical,New]22:17
jamlifeless: I don't know anything offhand other than: https://bugs.launchpad.net/bugs/42242322:17
ubottuLaunchpad bug 422423 in bzr "NoSuchId error upgrading to 2a" [Critical,Confirmed]22:18
jamwhich Martin just reported22:18
lifelessI'll track this one down22:18
lifelessand see if it fixes martins after that22:18
lifelesscould be a common cause with different visible effects22:18
jamobviously the guess is that there is a problem with the computation of the delta22:19
lifeless:)22:19
lifelessI'll be getting more conversion timing data22:20
lifelessas well22:20
jamistr converting mysql took about 2 days on a rather old machine22:22
lifelesstypo22:23
lifelessI meant 'fetch timing'22:23
lifelessI will be doing this netbeans repo test conversion22:23
lifelesspartly to say to the sun folks how great it is :)22:24
lifelessand also to see how we do: 1G of 1.7G are manifests.22:24
emmajanepoolie, morning22:24
pooliehello emmajane, lifeless22:24
lifelesshi poolie22:25
lifelesspoolie: 'Slack' is highly entertaining. I think I'm an eve :P22:25
pooliehm22:25
pooliei don't recall that bit, is that one of the personas?22:25
lifelesspoolie: yes, the first one22:26
lifelessseeks growth & challenge22:26
lifelesspoolie: so you know, drizzle isn't converting to 2a either22:30
lifelessI'm investigating now. It may have a common cause with the error you had yesterday. Or maybe not.22:31
pooliebecause, not yet, or because?22:31
poolieoh i see22:31
lifeless'fails to convert'22:31
pooliei was going to work today with igc on content filtering22:31
poolieanyhow breakfast first22:31
lifelesshttps://bugs.edge.launchpad.net/bzr/+bug/42284922:31
ubottuLaunchpad bug 422849 in bzr "InconsistentDelta error upgrading drizzle repo to 2a" [Critical,New]22:31
lifelessOnce I know the cause I'll target it etc22:31
lifelessstill gathering details/assessing22:32
pooliehm22:34
pooliei tested mysql a little while ago22:34
pooliei could retest it, which would narrow the problem to whatever time window that was22:34
pooliei was thinking i22:34
lifelessdrizzle != mysql though, different history22:34
poolie... well i was but i'll tell you later22:34
poolietrue22:34
beunoHPSS calls: 8670 (8668 vfs)22:35
beuno\o/22:35
beuno(upgrading LH to 2a)22:35
lifelessWTB: network upgrade.22:35
beuno:)22:35
beunomwhudson, Peng_, lh is on 2a22:40
* mwhudson runs upgrade locally22:41
lifelessmtaylor: drizzle only drops 14MB in 2a23:47
lifelessmtaylor: what do you have in there..binaries?23:47
lifelessfound the bug23:49
igcmorning23:54
mtaylorlifeless: nope. no binaries for us!23:59
lifelessspiv: what tests would be the closest ones to the ones you changed in your ids-only-necessary-texts for bug 42284923:59
ubottuLaunchpad bug 422849 in bzr "InterDifferingSerializer generates InconsistentDelta error upgrading drizzle repo to 2a - adds a file already versioned" [Critical,In progress] https://launchpad.net/bugs/42284923:59
mtaylorlifeless: why don't we drop more?23:59
lifelessmtaylor: I don't know yet23:59

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