/srv/irclogs.ubuntu.com/2010/04/13/#bzr.txt

spivGood morning.00:14
jelmermoin spiv01:06
spivjelmer: Morning.01:06
spivjelmer: Any thoughts on /foo,bar/baz? :)01:07
jelmerspiv: I posted a comment on that MP less than 20 seconds ago01:07
jelmer:-)01:07
spivOoh :)01:07
pooliehi spiv, jelmer01:15
pooliebiab01:15
* igc out for a few hours01:43
poolie1thanks for the bug triage, spiv02:32
poolie1the queue was getting a bit long again02:32
spivNot a problem.02:32
spivDo you remember which bug tag we decided on for the content merge hook?  content-merge-hook maybe?02:34
spivAh, just 'merge-hook' I think02:34
spivHmm, my IRC log is inconclusive.02:34
spivpoolie1: care to make a decision (or flip a coin) on that?02:35
* spiv goes with 'content-merge-hook'02:40
spivZero new bugs.  Time for coffee.02:45
lifelessspiv: I'd just take them merge, myself.02:48
poolie1spiv: wfm03:08
poolie1lifeless: the point is to have a name for the feature03:08
poolie1it's more than just merging03:08
=== poolie1 is now known as poolie
lifelesspoolie: I think too many semantic tags becomes a bit counterproductive03:11
pooliei don't think every bug needs to have precise coordinates in its tags03:12
pooliethe original discussion is that we had a few user conversations of saying "you should use that thing like is used for news merges"03:12
poolieand it's worth having some name for that03:12
=== samurai is now known as samiam
lifelesspoolie: http://www.rendell.org/pebble/software/2010/02/09/1265756844985.html might be an interesting read for you06:15
poolieyes, it is06:31
igcme back06:39
poolieyay06:44
poolieigc i'll see you monday! :)06:44
lifelessspiv: your pull relock is +1 from me07:12
lifelessspiv: lp barfed on my control mail07:12
spivwhee, ok.07:12
lifelessOOPS-1564CEMAIL2207:13
ubottuhttps://lp-oops.canonical.com/oops.py/?oopsid=1564CEMAIL2207:13
lifelessoh wheeee07:14
lifelessProgrammingError: permission denied for relation codeimport07:14
lifelessspm: ^07:14
lifelessMethinks we has a problem.07:14
lifelessmwhudson: / thumper: ^07:14
spmI shall arbritarially blame spiv. No reason other than it's been a while, and hence his turn.07:14
lifelessI'm thinking more 'uhm is all mail merge processing about to go boom' ?07:15
spmgawd I hope not - this has been active since the last rollout I believe....07:15
lifelesshave a look a the oops07:16
lifelessdoesn't look like a temporal issue07:16
mwhudsonlifeless: what did your merge proposal do?07:16
lifelessmwhudson: review: +1 merge: +107:16
mwhudsonlifeless: on which branch?07:16
mwhudsonis it proposed to merge into a code import branch?07:16
lifelessno07:16
lifelessspivs bzr pull-relock branch07:17
lifelessmwhudson: forwarded you the email07:18
mwhudsonlifeless: looks like we do have a problem indeed07:19
spmstill sounds like spiv's fault to me07:19
lifelessmwhudson: Yah, I try to avoid the panic button otherwise ;)07:19
vilahi all07:20
spmhey vila!07:20
mwhudsoni guess a simple grant select on codeimport will fix it though07:20
vilahey spm !!07:20
mwhudsoni'm confused as to how this is only turning up now though07:20
spmlifeless: can you (just being a paranoid sysadmin) easily recreate this to test it works if I run the grant?07:21
lifelessspm: sure07:21
spivFWIW, I just voted on a bzr branch proposal a few minutes ago via email with no trouble.07:22
lifelessspiv: by no trouble, do you mean 'it has taken effect'07:22
spivlifeless: yes07:23
spivOr at least, the email from LP tells me it did ;)07:23
mwhudsonoh, i sort of see07:26
mwhudsonyou have to be able to edit a merge proposal to approve it, obviously07:26
mwhudsonthis is the check:07:26
mwhudson        return (user.inTeam(self.obj.registrant) or07:26
mwhudson                user.inTeam(self.obj.source_branch.owner) or07:26
mwhudson                check_permission('launchpad.Edit', self.obj.target_branch) or07:26
mwhudson                user.inTeam(self.obj.target_branch.reviewer))07:26
mwhudsonthe third line there blows up07:27
lifelessmwhudson: I can edit that proposal, can't I ?07:27
mwhudsoni guess spiv (and most of us) hit the first couple of lines07:27
mwhudsonor indeed, the earlier cases of the check in the third line07:27
mwhudsonlifeless: file a bug?07:27
lifelessmwhudson: I don't understand07:28
lifelessmwhudson: I can approve it in the web ui07:28
lifelessmwhudson: why would I be lacking permission in the mail UI ?07:28
lifelessmwhudson: I think you should file the bug, you understand whats going on here.07:28
mwhudsonlifeless: it's not a failure of permission, per se07:29
mwhudsonlifeless: it's the check that you have permission hitting a db permission issue07:29
mwhudsoni'll file the bug07:29
mwhudsonlifeless: btw, i wrote some code you'll *really* hate today07:29
mwhudsonlifeless: https://pastebin.canonical.com/30468/07:29
lifelessas opposed to every other day ? :>07:30
C-SDoes anybody know how to get the download links from launchpad such as launchpadlibrarian.net/xxxx07:30
C-S?07:30
C-SI am searching for the correct link to download bzr-gtk07:30
lifelessC-S: hit the web page07:30
C-Slifeless: I know I could do that :-) but I need the link for implementation in the FreeBSD port system07:31
lifelessC-S: FreeBSD should learn to follow redirects :)07:31
lifelessC-S: I'm not being facetious or difficult - thats really the issue.07:32
C-Slifeless: anyhow. I am not sure if it does :-)07:32
lifelessUhm, wget -S of the url you see in the web page should show you the redirect info07:32
C-Slifeless: cool. I should maybe try both ways. to be honest, the redirect link would work07:33
lifelessmwhudson: so, as I read that, 'if its an import push by copying packs' ?07:33
mwhudsonlifeless: yeah07:33
C-Slifeless: but its more comfortable like this. Thanks a lot07:33
lifelessmwhudson: so, uhm, I think this needs some pretty significant justification. And a bug in bzr related to that code bidirectionally, *at a minimum*.07:33
mwhudsonlifeless: and copy_tree_to_transport doesn't work when the source is an http transport07:33
mwhudsonlifeless: well, part of the justification was dependent on whether it helped07:34
lifelessmwhudson: its also buggy07:34
mwhudson(and i now know that it does)07:34
mwhudsonlifeless: i'm not surprised07:35
mwhudsonso yeah, i'll send an email/file a bug tomorrow07:35
lifelessto make it less buggy you need to:07:36
lifeless - take the pack names lock07:36
mwhudsonlifeless: the basic story is that 2a fetch is slow07:36
lifeless - delete obsolete pack and index files07:36
lifelessby less buggy I mean 'wont blow up hugely eventually'07:36
mwhudsongrabbing the kernel import takes ~an hour on the slave, grabbing it via copy_tree_to_transport takes 30 seconds07:37
lifelessmwhudson: why are you copying it around at all ?07:38
mwhudsonbecause that's how the import system has always worked07:39
mwhudsonit would be nice to use stacking, but that doesn't work for other crappy reasons07:39
mwhudson(that i should probably dig into)07:39
mwhudsonbut!07:39
mwhudsontomorrow07:39
lifelessI was thinking lightweight checkout07:39
lifelessnot stacking07:39
mwhudsonhm, might work i guess07:40
mwhudsonthe puller has the same issue though07:41
mwhudsoni guess there would be other ways around that07:41
mwhudsonbut really07:41
mwhudsontomorrow07:41
lifeless^^07:44
AfCI'm trying to follow jam's emails about history-db, and I'm a bit confused. I thought Bazaar's packs were already a database, so I'm a bit vague on how another is helping him?08:28
AfC[there is no criticality whatsoever associated with me knowing what he's talking about, but I enjoy following the engineering discussions here and learn from them]08:28
spivHorses for courses, AIUI.08:28
spivI haven't yet looked closely enough to give you a more informed analysis than that, though :)08:29
AfCspiv: jam's emails are kinda long08:29
pooliehe tends to be very detailed08:30
spivI figure he writes so much to let me I don't need to read it, because he's obviously checked everything already ;)08:31
AfCIsn't it funny that we all write too-long emails (expecting people to follow and appreciate our every last detail), but complain at everyone else having the temerity to write long messages that have detail.08:32
lifelessso08:33
lifelessbzr's repository is a database08:33
lifelessthere is a particular query that we have to do a table scan to answer today08:33
lifelessjam has been working on a schema to avoid that table scan when answering that query08:34
lifelessand doing it as a plugin for more freedom in testing and deploying it.08:34
lifelessit may end up part of our core database, or a separate one (partitioning for different write patterns) eventually;08:34
lifelessnote that its new db content, not a new db engine08:35
AfClifeless: plugin, sure. Adding an sqlite dependency, that seemed a bit odd.08:35
lifelessoh, did he? I missed that08:35
vilaAfC: a key point in the experiment is that it's easier *today* to do range queries08:35
* AfC could be wrong08:35
lifelessuhm, thats likely expediency08:35
AfClifeless: no doubt.08:35
lifelesspreprocessing graphs for range queries is a well studied problem in the literature08:35
AfClifeless: but on the other hand, you might want to be careful lest that gets too far out into the wild08:35
lifelessI don't know if jam looked into that.08:35
AfCreputation and memes 'n all that08:36
lifelessAfC: I don't follow08:36
vilaAfC: I share these concerns08:36
vila:)08:36
AfC"Bazaar is so inefficient they had to turn to sqlite to store their data. Which is yet another format change. God these guys are idiots. And another dependency to boot"08:37
AfCall of that is untrue, but we have had a PR problem for a long time08:37
lifelessoh08:37
lifeless*if* we need a better k-v store, I'd rather use sqlite than roll our own for the sake of it.08:38
lifelessand sqlite is really really good08:38
* AfC has to get going cycling home before it gets too dark08:39
AfCsee ya08:39
lifelessciao08:39
AfC[sorry to run out on an interesting topic]08:39
spivlifeless: so if we're using subunit on PQM now, should we try --parallel as well?08:41
lifelessspiv: the machine is old08:42
lifelessspm: please confirm balleny's cpu core count08:42
lifelessspiv: (we could do --parallel without subunit btw)08:42
spmlifeless: 1.08:43
lifelessspiv: ^08:43
lifelesswe could use the EC2 plugin on the canonical UEC cloud08:43
lifelesswith a little work08:43
spmor #cores == #cpus :-)08:43
spm... or bribe me to sneak a pqm instance onto eg wildcherry.... :-P08:44
lifelessspm: what would that take?08:44
lifelessa VM on there would be fine.08:45
spivAh ok.  For reason I had misremembered that our PQM had more than that.08:45
spivs/For/For some/08:45
lifelessspiv: I think the new LP pqm box doth have it08:45
spmlifeless: joke. not  going to happen. LP main DB server? I think not. :-)08:45
spivlifeless: and a crushingly slow test suite to match!08:45
lifelessspm: go back far enough ....08:45
spmspiv: is *that* your fault then?? (still trying to pin blame on teflon-spiv here...)08:46
lifelessspm: yes, I believe spiv did the first commit to launchpad, so its clearly all his fault.08:46
spmwe have a blame08:46
spivI did?  I guess it's possible...08:50
lifelessspiv: your previous flat; a demo with the basical url dispatch and what was that orm again08:51
bialixhi all08:58
spivlifeless: that does ring a vague bell, yeah...09:32
spivlifeless: a long time ago :)09:32
lifelessin a flat far far away!09:33
edgimarIf I have checked out a branch via "bzr checkout --lightweight", how do I get the revision that the directory is currently associated with?09:49
edgimarrevno just gives me the lastest revision of the branch from what I can tell.09:50
edgimar(which isn't necessarily the revision associated with the files currently in my local directory.)09:52
lifelessbzr revision-info --tree09:53
edgimarlifeless, ok thanks.  I wonder why it needs to be so complex -- I would intuitively like "bzr revno" to do that for me, but oh well...09:54
lifelessedgimar: well, one of the two has to be the default :)09:54
edgimarI should be able to find out the latest revision just by 'bzr log' -- or there could (should?) be a 'bzr latestrevno' command.09:56
vilahey bialix09:56
vilaedgimar: 'bzr revno' *is* the latest, using an option or using a different command anyway...09:57
bialixheya vila!09:58
vilaedgimar: when the tree and branch revnos disagree bzr is generally issuing a warning about using 'bzr update', did you encounter a case where it didn't ?09:58
edgimarvila, right - I wan't it not to be the latest, but to be "my current".09:58
vilaedgimar: as lifeless said, one of them should be the default and I think there are more cases where you want it to be the branch one, so use --tree09:59
awilkinsedgimar, bzr qlog has an indicator on the log list where the tree is at10:00
vilajelmer: ping10:00
edgimarawilkins, ok - good to know.10:02
edgimarawilkins, is qlog a standard command in bzr?10:03
bialixedgimar: no, it's from QBzr plugin10:07
edgimarone other question: how do I update to a specific revision number?  it seems that "update" won't work for this?10:10
edgimarok found it - revert.10:12
edgimarIf I have a lightweight checkout, though, and I do "bzr revert <filename>", does it change the file to the *latest* revision, or just the revision which you get from 'bzr revision-info --tree'?10:17
edgimarHmm, revert doesn't seem to work at all for lightweight checkouts -- I get bzr: ERROR: Cannot lock LockDir(chroot-47767537201040:///bzrroot/path/to/repo/.bzr/branch/lock): Transport operation not possible: readonly transport10:20
edgimarSo does that mean that there's no way to switch your tree to a different rev with a lightweight checkout?10:21
lifelessedgimar: I thought we fixed that bug10:32
lifelessedgimar: what bzr release are you using ?10:32
edgimar2.0.210:42
edgimarlifeless ^^10:43
lifelessedgimar: its merged into 210:46
lifeless2.0.6 shouldhave the fix10:47
edgimarok.10:47
lifeless2.0.5 might have it10:47
lifelessit was merged 9th march10:47
lifelessif you wanted to test and let me know that would be grand ;)10:47
edgimarI can't right away, but perhaps if I have some spare time later.10:48
lifelesssure10:49
lifelessuhm10:49
lifelesshttps://bugs.edge.launchpad.net/bzr/+bug/498409 is the bug10:49
ubottuLaunchpad bug 498409 in bzr "bzr revert takes a branch lock" [Medium,Fix released]10:49
lifelessjust for your reference10:49
lifelesspoolie: still around ?10:50
lifelesspoolie: please pencil a quick call with me tomorrow am :P10:50
awilkinsAnyone know a good comparision of bzr-svn vs git-svn ?11:46
jelmerawilkins: in what sense?11:47
awilkinsjelmer, In the sense - what features does each support, what are the differences11:54
awilkinsjelmer, Not especially fussed about performance but it's nice to know11:54
awilkinsjelmer, e.g. - I've not played with git enough, but from a cheatcard I saw today there's a special command for pushing to SVN but in bzr I know you just push (in general) - that sort of thing11:55
awilkinsThinking of using git for a versioned data store for a particular project and realised that I haven't used git beyond playing with it.11:55
dcolesBazaar uses the svn props to you can roundtrip via a svn repository11:56
dcolesWhich is actually quite nice11:56
awilkinsCurrently I manage my local branches of the sources via bzr-svn, but I thought I should switch to git-svn and dogfood for a bit to gain some familiarity11:56
dcoles(though can confuse the heck out of non-bzr people)11:56
dcolesI think git initialises a subversion metadata directory on the client side... not sure if it pushes extra stuff to the svn repo11:58
jelmerdcoles: no, it doesn't push extra stuff to the svn repo afaik12:01
=== mrevell is now known as mrevell-lunch
=== mrevell-lunch is now known as mrevell
lelithi all! I'm back on my svn->bzr switch... I was using "bzr branch https+urllib://..." for my tests; to move faster, I got a local copy of my svn repos, so I thought there was a "bzr+svn://local/path"... Is there?13:32
lelitI got the thing with "svn+ssh://localhost/", but maybe I'm missing an even better way13:32
lelitdoh, bzr does magics :)13:35
lelitbranch file:///local/path works as (un)expected :)13:35
jelmerlelit: hi13:42
jelmerlelit: yep :-)13:42
lelitjelmer, is there a trick to get just a subtree with that url?13:43
lelitI mean, I get an error trying "branch file:///repos-path/branches/interested-in"13:44
jelmerlelit: what error?13:45
lelitERROR: Not a branch: "..."13:47
lelituhm, wait13:48
=== vds1 is now known as vds
lelitjelmer: ignore that, sorry13:50
edgimarlifeless:  I checked the problem I had before with bzr 2.1.1, and it still occurs (same error).14:13
* awilkins is being driven mad by the obliqueness of git14:34
jelmeredgimar: I think lifeless is probably asleep (he's in .au)14:38
edgimarjelmer, ok- I guess he'll see it sometime - I'll check back later...14:44
=== grahal_ is now known as grahal
AfCawilkins: I observed in here the other day that I saw the Git book from O'Reilly ... and that it was very confusing.15:00
vilajelmer: ping15:05
vilajelmer: lowering the alert level about using name=name instead of name, it was due to an overly aggressively blind local patch to bzr-loom,15:06
vilajelmer: the remark still stand though, since you're adding a keyword arg than can be None, better use the name= syntax to avoid breakage15:07
jelmervila: I agree it's a good idea to use name= anyway15:07
vilajelmer: cool :)15:07
abadger1999jelmer: I've updated https://code.launchpad.net/~toshio/bzr-gtk/handle-dirty-patches/+merge/1885615:52
abadger1999jelmer: But the web ui hasn't updated yet and I'm seeing problems with the branch. (bzr log traceback)15:52
jelmerabadger1999: hi15:53
abadger1999jelmer: Let me know if it gives you problems when you review it.15:53
jelmerabadger1999: thanks15:54
abadger1999jelmer: Sure, not a problem.15:54
jelmerabadger1999: I see only one revision as well15:54
=== IslandUsurper is now known as IslandUsurperAFK
jelmerabadger1999: I guess there should be more?15:55
abadger1999jelmer: Yep.  If you bzr branch lp:~toshio/bzr-gtk/handle-patch-fix15:55
abadger1999The second is present in diff.py15:56
abadger1999*second change15:56
abadger1999But the branch is definitely not happy (bzr log => bzrlib.exceptions.SyntaxError, bzr diff -r last:1 => ReisionNotPresent)15:58
abadger1999You could manually diff against lp:bzr-gtk15:58
abadger1999Or I could create a new branch15:59
jelmercan you create a new branch perhaps?16:00
jelmerI'll promise to review it today16:00
abadger1999okay16:00
=== deryck is now known as deryck[lunch]
abadger1999jelmer: https://code.launchpad.net/~toshio/bzr-gtk/handle-patch-dirty/+merge/2333016:22
* abadger1999 submits bzr bug for the corrupted branch16:23
=== IslandUsurperAFK is now known as IslandUsurper
jelmerabadger1999: thanks and thanks :-)16:23
abadger1999:-)16:24
vilaabadger1999: you're toshio !!!! I would have never guessed :-/16:28
abadger1999vila: Hehe :-)  Yeah, we need and irc nick::name mapping :-)16:29
vilaabadger1999: indeed :) It's already hard to map nick <-> face :)16:29
jelmerabadger1999: I'll have a look in an hour or two16:40
abadger1999jelmer: Thanks.  No hurries -- I'm just processing my downstream bug queue :-)16:41
jelmerabadger1999: :-)16:42
* jelmer wished launchpad supported recognizing merges based on patch contents rather than revids, that would make +activereviews really useful for this sort of thing16:43
=== deryck[lunch] is now known as deryck
=== beuno is now known as beuno-lunch
jamvila: still around?17:33
* vila cries in log code :(17:35
vilamorning jam17:35
jamhey vila. I think I responded to your request for history-db info. I'd be happy to chat more directly about it.17:52
jelmervila: btw, thanks for that --strict fix17:54
vilajam: reading17:54
vilajam: sorry EOD time has come, I promised :-/ So, roughly: my feeling is that you should either: 4) profit for lp and loggerhead OR keep hammering until you get something that can be backported18:03
jamso I think 'hammering until backported' should block on me finishing the rework of PackCollection18:04
jamand possibly the annotation cache18:04
vilathe later means an incremental merge sort at a minimum (if I understand you correctly) based on gdfo or anything else (I don't care that much :)18:04
vilajam: yup18:04
vilajam: I think the plugin is already worth deploying for lp/lh18:05
vilajam: by the way, I fixed a typo:18:05
vilajam: http://paste.ubuntu.com/413761/ my revno is 9018:06
jamI don't make typos, the world just doesn't know how to spell consistently with me :)18:07
fullermdWait, vila FIX a typo?18:07
* vila notes18:07
* fullermd core dumps.18:07
vilaLOL18:07
vilafullermd: thanks for making my day end in a good laugh, I needed that :)18:07
jamfullermd: actually, I would say vila fixes his typos all the time :)18:07
=== beuno-lunch is now known as beuno
jamhave a good evening vila18:07
* fullermd waves at vila.18:08
vilajam: I'll try to answer to your mail with more details later or tomorrow18:08
vilajelmer: hehe, in fact I high-jacked your bug, we discussed it far before and I thought there was a bug for it until you filed yours ;-)18:10
durin42jelmer: hi18:25
durin42jelmer: gotta get legal approval for contributing to another project, will take me a couple of hours depending on latency there18:25
cody-somervilleI'm doing a bzr pull and its causing bzr to crash with TooManyConcurrentRequests18:52
fullermdThat error is usually a knock-on from something else...18:54
cody-somervilleyes indeed18:59
cody-somervilleodd19:06
cody-somerville'bzr --pull merge <branch>' works though19:06
cody-somerville(it did a pull and not a merge too)19:06
fullermdI'm slightly surprised that that works, but merge --pull WILL do a pull if it can.19:07
cody-somervilleaye19:41
cody-somervillejust wonder whats causing just plain ol' bzr pull to crash19:41
__monty__I'm looking for some help with a bug, this one to be precise: https://bugs.launchpad.net/bzr/+bug/4559919:51
ubottuLaunchpad bug 45599 in bzr ""no repository present" error should suggest using bzr branch" [Wishlist,In progress]19:51
jamcody-somerville: my guess, some plugin you have (like bzr-search) which is trying to do something other than 'just pull', and isn't triggering from 'bzr merge --pull'20:47
mwhudsonhuh21:55
mwhudsonclicking around http://bazaar.staging.launchpad.net/~mwhudson/linux/trunk/files is reasonably performant21:55
mwhudsona pleasant surprise :)21:55
lifelessedgimar: yes, its not in 2.1.1 yet22:15
lifelessedgimar: we have multiple release branches - 2.0.x, 2.1.x, 2.2.x, for users wanting stability.22:22
lifelessedgimar: the upshot of this is that a fix in 2.0.Z isn't necessarily in 2.1.B, for any B - you have to check the date of the releases.22:23
lifelessmwhudson: can you land that patch please, I haven't gotten across the new landing procedures yet22:25
mwhudsonlifeless: sure22:25
lifelessmwhudson: also, were there docs I should have updated, that describe the limit to end users ?22:25
lifelessmwhudson: could the diff be related to db-devel/devel split ? though only one unmerged revision shows...22:28
mwhudsonlifeless: i very much doubt it22:28
mwhudsonlifeless: db-devel/devel, yes maybe22:28
lifelessmwhudson: and devel was the right branch to target for this change ?22:28
mwhudsonlifeless: yes22:28
mwhudsonlifeless: we do have edge codehosting now, so it makes sense to target devel22:28
lifelessok cool22:29
mwhudsoni guess that'22:30
mwhudsons another reason for some kind of authenticated lp:-resolution: we can direct beta testers to bazaar.edge.launchpad.net22:31
lifelessmwhudson: or we could just assign some % to edge22:33
lifelessand monitor stats about behaviour22:33
lifeless:P22:34
mwhudsonwell, it's been a while since we had a really bad bug in codehosting...22:35
lifelessmwhudson: did you review by email ?22:36
lifelessor web ui ?22:36
mwhudsonlifeless: web ui22:37
lifelessthanks22:39
lifelessone bug fixed, two bugs filed.22:39
lifelessits going to be one of those days ;)22:39
mwhudsonlifeless: so, to continue from last night, i'd like to talk about why i did that packs hackery22:44
lifelessok22:44
lifelessdid you mean voice when you say talk ?22:44
mwhudsonno, i think irc will be fine22:44
lifelesskk22:44
mwhudsonbasically the problem is the amount of cpu entailed in doing a from-scratch fetch of a kernel-sized 2a branch22:45
lifelessright22:45
lifelesswe validate all the data - process it not dumb copy22:45
lifelesswe don't do any cross checks22:46
mwhudsonright22:46
lifeless[not expensive ones anyway - we do check that all the texts are present etc]22:46
lifelessit also trims unreferenced data, which is important for privacy22:46
lifelessif you commit a password, uncommit it, and then push; the password revision must not propogate22:47
mwhudsonbut in my case i really don't care about this22:47
mwhudsoni just want to move the files from there to here22:48
mwhudsonbecause i control the process that produced the branch22:48
lifelesswhy don't you rsync, or copy the entire branch that way22:48
mwhudsonbecause, boringly, the branch is accessed over http22:48
lifelessthe thing that is particularly squicky is copying only some data as a dumb fs operation22:48
mwhudsoni guess changing that is probably the right thing to do22:49
mwhudsonthen i can use copy_tree_to_transport again, and not grub around in pack internals22:49
lifelessI mean, if you say 'hey, I cp -a, which you guys support, and X happens', in the future, we're in a good position to analyse and fix without false starts22:49
awilkinsI found 2a a lot more cpu-hungry than the previous formats, I really noticed it22:49
awilkinsEspecially the periodic repacks22:50
lifelessawilkins: thats interesting; was it also *longer*, or just more intense ?22:50
lifelessawilkins: and do you have the C extensions built ?22:50
mwhudsonlifeless: is there scope to make the checks/filtering faster in the medium term?22:50
awilkinslifeless, definitely longer ; C extensions built. Not sure how typical the trees I have are22:50
lifelessmwhudson: there is scope to (for instance) preserve intact the packs structure and avoid all compression overhead22:51
lifelessmwhudson: however without looking at current profiling data I can't really comment on time to make improvements22:52
lifelessmwhudson: nor what scale they would be22:52
mwhudsonlifeless: over the internet you don't really notice, but over the data centre network or if you use 2a branches without a shared repo, you definitely notice the cpu cost of 2a22:52
lifelessmwhudson: how long does git take to do a full scratch clone22:52
lifelessof linux, for a head-head comparison22:52
mwhudsonlifeless: yeah, don't know22:52
lifelessgit does a similar amount of conceptual work22:53
lifelessso a reasonable comparison point22:53
mwhudsonwow, my isp must have really done something useful recently22:59
lifeless?22:59
mwhudsongetting ~1 megabyte a second download for the kernel22:59
lifelesswho are you using ?23:00
mwhudsonthat sort of thing never used to happen23:00
mwhudsonlifeless: vodafone23:00
lifelesswired ?23:00
mwhudsonadsl23:00
mwhudson(2+)23:00
lifelessinteresting23:00
lifelessI'll have to consider staying with them next month23:00
mtayloryup23:00
mwhudsonoh rught23:00
lifelessvodafone NZ seems a lot more sane23:00
mwhudsonright23:00
mwhudsonmmm23:00
lifelessthan AU23:00
mwhudsoncustomer support is a bit flaky23:01
mwhudsonbut i don't have experience with anyone else23:01
lifelessmwhudson: I was impressed by their forums... where engineers actually post!23:01
lifelesswith helpful comments!23:01
lifelessthis is unheard of in .au23:01
mwhudsoni thought all techy people were on internode in .as23:01
mwhudson.au23:01
lifelessmwhudson: vodafone are only mobile here23:02
lifelessinternode are only really wired23:02
mwhudsonoh right23:02
lifelessso yes, I'm with internode :)23:02
mwhudsonwell for mobile you don't get a lot of choice here :)23:02
lifelessIt would be fun to have international number portability23:03
lifelessmwhudson: 3 providers I think, for mobile?23:03
lifelessmwhudson: or is it 4 ?23:03
mwhudsonvodafone (big megacorp) telecom (ex monopoly) telstra (ex .au monopoly, don't have their own network i think) 2degrees (payg only)23:03
lifelesshmm23:03
lifelessand you chose?23:03
mwhudsonvoda23:04
mwhudsoni think they are the best choice23:04
mwhudsonbut the customer service is a bit crap23:04
mwhudsontelecom's network has had some embarrassing outages23:04
lifelessclear were pretty good when I was there23:05
mwhudsonnow telstraclear -- probably enough to put anyone who's spent time in .au off? :)23:06
lifelesstempting to knee jerk23:07
lifelesshowever as the underdog I'd expect them to actually have to do shit in NZ23:07
mwhudsonalso they don't have their own network, i think they resell voda23:07
lifelessmwhudson: for mobile, heh that would be entertaining23:07
lifelessmwhudson: for backhaul they should have their own network23:08
lifelessthey started with the railway country backbone23:08
pooliehi all23:12
poolie(phone)23:12
mwhudsonlifeless: git clone git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-2.6.31.y.git took 8m24 wall clock and 1m39 user, 25s sys23:14
lifelessok, significantly faster23:15
mwhudsonyes23:15
lifelessso23:15
lifelessits worth having a bug open I think23:15
mwhudsona local clone took 20s23:15
* lifeless twitches23:15
lifelessmwhudson: for your copy, can you guarantee noone else is writing to the source branch when you make your copy?23:16
mwhudsoni guess not, strictly speaking23:19
lifelessso, you'll need to loop23:19
lifelessuntil your copy and the source mach23:19
lifelessmatch23:19
lifelessbzr does this a little more cleverly23:19
mwhudsonhow do i tell if they match?23:19
mwhudsonsha1 the pack-names or somethign?23:19
lifelesssame ls -lR23:20
lifelessuhm23:20
lifelessfirst approximation is list-and-copy everything; list again, and if its changed copy everything again23:21
lifelessas copying is fast we don't expect this to be a problem23:21
lifelessparticularly as this the exceptional case, not the normal case23:21
james_wlifeless: seen http://chasmd.org/ ?23:30
lifelessjames_w: yes23:30
lifelessin discussion with them about collaboration; I think lmirror is substantially more complete at this point23:30
james_wlooks like it23:33

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