/srv/irclogs.ubuntu.com/2009/06/24/#bzr.txt

lifelessmtaylor: its the older form of shelve00:02
lifelessmtaylor: for folk with old shelves they need to get ack00:03
Peng_Or for people on Windows, right?00:09
garyvdmHi - I'm getting an error trying to commit which is quite weird.00:21
garyvdmhttp://paste.ubuntu.com/202463/00:21
garyvdmCould not acquire lock "/home/garyvdm/qbzr/wd/qbzr/.bzr/checkout/dirstate": (11, 'Resource temporarily unavailable')00:21
garyvdmThere is nothing that I am aware of that could be holding a lock.00:22
garyvdmNothing running that is.00:22
garyvdmAh - never mind - I had a bzr runinng in my ide that was stoped in pdb that was holding the lock.00:24
pooliehello00:27
pooliejam, thanks for the analysis of 39074500:31
pooliejml/thumper/mwh: I'm thinking about doing "reconfigure --stacked-on" or --unstacked soon00:38
poolierobert questions whether this is a good use of time or not00:39
poolieany opinions?00:39
mwhudsonpoolie: YES PLEASE00:39
pooliek00:42
thumperpoolie: how would that interact with LP?00:42
igcmorning00:43
pooliehello igc00:43
pooliethumper: um00:43
igchi poolie, thumper00:44
thumperpoolie: as in, reconfiguring a stacked LP branch00:44
thumperhi igc00:44
poolieit would work over hpss to let you configure branches to be either stacked or unstacked00:44
poolienot sure what you're asking00:44
thumperpoolie:would it pull the necessary revisions from the stacked branch?00:44
thumperpoolie: how about the ability to override the suggested stacking branch?00:44
poolieyes, it would potentially copy a lot of data when making the branch standalone00:45
thumperpoolie: is incremental reconcile very hard?00:45
poolielifeless estimates several days00:46
lifelessthumper: its tricky; gotta copy some data exclude others while simultaneously altering it00:47
thumperI'd say that is more important than playing with stacking right now00:48
thumperIMHO00:48
thumperor00:48
thumpersome optimisations for reconcile on 2a formats00:49
thumperwe're wanting to move more internal teams to the 2a format00:49
thumperand james_w's ubuntu branches00:49
poolieok, that's useful feedback00:49
pooliethough it's not necessarily either/or00:50
thumperheh00:50
thumperno00:50
thumperwe want everything, and a pony00:50
pooliein that i'd need to page in a lot of robert's state to do renconcile00:50
jmldelicious ponies.00:50
pooliebut i can do the stacking thing fairly quickly00:50
thumperreduced swapping is always a win00:51
thumperI'd still like the ability to tell the bzr client not to stack no matter what LP suggests00:51
thumperwhich we can't do right now00:51
lifelessthe streaming fetch bug is highest IMO00:52
lifelessreconcile is a pain, can't merge for lp developers is a blocker00:52
lifelessother teams have /way/ fewer devs per branch, which makes transition much easier. Also smaller history.00:52
thumperyeah00:53
thumper+1 on streaming fetch00:53
spivlifeless: as in inventory deltas, or do you mean something else?00:54
mwhudsoni was assuming reconfigure --unstacked/--stacked-on wouldn't be especially hard00:54
poolieme either00:54
lifelessspiv: https://bugs.edge.launchpad.net/bzr/+bug/39056300:54
ubottuUbuntu bug 390563 in bzr "absent factory exception from smart server when streaming 2a stacked branches" [Critical,Triaged]00:54
poolieso easy a manager could do it00:54
thumperpoolie: :)00:54
thumperpoolie: also a definitive "don't stack" flag should be easy too right?00:54
lifelessmwhudson: the library call to change already takes care of fetch; more problematic is making a new repo when making a shared repo branch into a stacked branch00:55
lifelessthumper: don't stack may require smart server verb changes. FWIW00:55
lifelessthumper: but is a don't stack flag needed ?00:55
thumperlifeless: I thought we decided a while ago that stacking was determined entirely client side00:55
poolieso, seriously00:55
pooliei have to make some calls today00:55
lifelessthumper: I know the lp-code team have occasion to use it for testing, but outside that group?00:56
pooliei was hoping i could do one or the other of them in the time i do have today00:56
thumperlifeless: for unrelated branches, it is useful00:56
thumperalthough, perhaps limited use00:56
thumperpoolie: pick one an do it!00:56
thumper:)00:56
lifelessthumper: /may/ require verb changes  ;)00:56
lifelessthumper: we have more verbs doing more things, now.00:56
thumperlifeless: is one "JFDI" ?00:57
lifelessfor a small hack, I'd most like to see network activity not overwriting stuff when there is no progress bar. Or something like that. Its a very visible ugliness00:57
poolielifeless: it's high on my list too00:58
lifelessmwhudson: the bzr log from codehosting00:59
lifelessmwhudson: is it safe to attach to the bug, or do you think there are things we'll want kept secret in them ?01:00
mwhudsonlifeless: i think it's pretty unlikely there's anything sensitive in there01:00
igcpoolie: ready for a call soon?01:04
Peng_Yep, pushing 2a -> 1.9rr over hpss isn't very fun. 22 seconds, while 2a -> 2a is 6.01:04
Peng_(For 11 revisions of loggerhead.)01:05
poolieigc, yes, let me get a couple of things closed here01:05
pooliewill call you in 5?01:05
Peng_Still usable, of course, but it doesn't make dogfooding very fun.01:05
igcsure01:07
lifelessPeng_: indeed01:07
Peng_Well, I could upgrade lp:loggerhead to 2a when nobody's looking, and it would take them a while to figure it out... :D01:09
lifelessI wouldn't01:09
lifelessnot till we fix the current set of critical bugs01:09
Peng_What is the current set of critical bugs?01:10
Peng_Absent factory, IDS being used for push, ?01:10
lifelesslp knows :P01:12
Peng_Yeah, that's mostly it, aside from some rich-root upgrade issues.01:22
Peng_The other one is cross-format inventory delta streaming.01:25
lifelessthats needed for cross format pushing to be pleasant01:26
poolieigc https://edge.launchpad.net/bzr/+milestone/2.001:49
pooliePeng_: that url for you too01:49
lifelessspiv: what are you up to today? Could I request https://bugs.edge.launchpad.net/bzr/+bug/338561 ?01:49
ubottuUbuntu bug 338561 in bzr "calling an unknown method logs noise (do_end, and a backtrace)" [High,Confirmed]01:49
poolielifeless, spiv, can you tell me about bug 390563 too?01:49
ubottuLaunchpad bug 390563 in bzr "absent factory exception from smart server when streaming 2a stacked branches" [Critical,Triaged] https://launchpad.net/bugs/39056301:49
lifelesspoolie: I'm investigating it at the moment01:51
lifelesspoolie: all I know for sure is in the bug01:51
lifelessI think01:51
Peng_poolie: Oh, thanks.01:51
spivlifeless: hmm, I could have sworn I fixed that a couple of months back.  Sure, I'll look at that.01:57
lifelessspiv: lots of them in ~/.bzr.log on lp codehosting ;)01:58
SamBspiv: could be that someone unfixed them02:00
SamBor that the fix somehow got lost before being merged...02:00
lifelessSamB: thats what we have tests for; and lp/bb both track merge status by revids02:01
lifelessSamB: e.g. 'no' ;)02:01
lifelesspoolie: is there more you want to know about 390563?02:02
SamBlifeless: depending on how forgetful you are02:02
SamBand/or whether you actually manage to write said tests02:02
spivSamB: it's possible that I actually just fixed something similar but not quite the same, too :)02:03
spivSamB: my memory of things I did a few months ago tends to be pretty hazy.02:03
SamBspiv: yeah, there's also that02:03
lifelessspiv: a few months ago, at my place, we looked at it and said 'lets file a bug and keep going on streaming'02:03
spivlifeless: ah02:06
spivAlso, I think before that I fixed a similar issue to do with streaming bodies, perhaps.02:07
lifelessyes, that rings a bell02:07
mwhudsoner02:21
mwhudsonpqm seems to be getting absentcontentfactory errors with two non-stacked branches02:21
lifelessmwhudson: details?02:23
lifelessmwhudson: push or pull02:23
lifelesscould be bug 36561502:24
ubottuLaunchpad bug 365615 in bzr "Random 'AbsentContentFactory' object has no attribute 'get_bytes_as' errors with CHK repository" [Critical,Fix released] https://launchpad.net/bugs/36561502:24
mwhudsonlifeless: merge, i expect, i don't really know details02:24
lifelessmwhudson: who does02:24
mwhudsondunno02:24
mwhudsonlifeless: all i'm going in is failure mails to the launchpad list02:24
mwhudsonit could be 365615 i guess02:25
mwhudsona traceback would be nice...02:25
fullermdigc: Nice timing results...02:35
igcfullermd: indeed. jam rocks!02:36
fullermd's almost enough to make me wanna see how long importing ports would take...02:36
fullermdThough I don't think I'd want my system murdering me in my sleep for doing so.02:37
igc(I'm guessing his chk-map tweaks made a huge difference, together with his faster-commit stuff)02:37
igcfullermd: for *really* huge imports, there's still plenty of tuning to do I think02:37
igcfullermd: but probably in fast-import itself, more than the core02:38
igcfullermd: and I'm unlikely to get to tuning fast-import till after 2.0 reaches RC02:38
fullermdYeah.  It'd be pretty huge.  Say around 200k revisions of 200k files.02:38
fullermd(well, files and dirs)02:39
lifelessfullermd: doit02:42
lifelessfullermd: generate a stream and save to disk ; then you can import incrementally or some such02:43
fullermdYeah, the first step would be seeing if I have enough disk space to hold the fast-import stream...02:44
fullermdCertainly no time for it this weekend though; it's Field Day.02:44
fullermd(and the following few days will be "desperately catch up on sleep", as usual  ;)02:45
lifelesswhats a field day?02:45
fullermdhttp://www.arrl.org/contests/announcements/fd/02:46
thumperlifeless: does the nightly ppa contain the autopack fix yet?02:47
fullermd(For some of us, hanging around an IRC channel about a version control tool just ain't nerdy enough, see...)02:47
lifelessthumper: I don't know02:49
thumperok02:50
thumperlifeless: a pack of an already mostly packed 2a repo is taking quite a while02:50
thumperis that expected02:50
thumper?02:50
thumperlike 10 minutes02:50
lifelessthumper: do you have the C extensions?02:52
thumperlifeless: it is from the PPA so I think so02:53
lifelessthumper: and 'pack' has to recompress all history, so its a slow command to run (which is why you shouldn't ever run it unless you have specific reasons to do so)02:53
lifelessthumper: so why were you packing?03:02
thumpertesting mainly, making my repo smaller, considering how to handle this on a large scale for LP03:03
lifelessthumper: bzr will pack as needed03:06
lifelessmanual packing is generally a bad idea03:06
Peng_mwhudson or beuno: ping03:12
jfroy_jelmer: I just tried to diff two local branches which are both branches of remote svn branches03:21
jfroy_And bzr died with a missing revision / no such revision error03:22
jfroy_Is there any way to figure out, perhaps, where that revision is?03:22
jfroy_if anywhere03:22
jfroy_this is kind of an open question too, I suppose03:22
jfroy_wondering if there's a way to search a repository or a branch for a specific revision ID03:23
lifelesslog -r revid:REVID03:24
jamigc: did you change fast-import to use _add_text instead of add_lines at least?03:24
jfroy_lifeless: ok I think I am screwed :/03:27
jfroy_well maybe03:28
jfroy_it's odd03:28
lifelessor cat-revision03:28
jfroy_that revision shows up in a branch in another repository03:28
jfroy_but does not show up in the same branch in another reposityr03:28
jfroy_*repository03:29
jfroy_it's clearly a bzr-svn bug03:29
jfroy_:(03:29
jfroy_actually, it looks like that revision was in a local branch I did not push to subversion03:30
jfroy_and have since deleted in the local repository03:30
=== timchen119 is now known as nasloc__
Peng_mwhudson & beuno: unping. :)03:41
mwhudsonPeng_: not-hi03:42
Peng_mwhudson: Heh, nice timing.03:44
igcjam: not yet - my figures are still with code calling add_lines()03:45
lifelessjam: hi03:47
lifelessjam: did you get anywhere with the stacking bug overnight?03:47
jamlifeless: I did not, other than to not be able to reproduce it locally, but to have the lp branch fail :(03:48
lifelessjam: lftp seems to be working again with lpp03:49
Peng_mwhudson: FWIW, I unpinged you because I decided to send a merge request.03:49
lifelesslp's sftp server, so you can just mirror down the branch03:49
lifelessyou don't need all of lp03:49
mwhudsonPeng_: oh ok03:50
mwhudsonPeng_: ah, cool in principle at least, haven't read the diff yet :)03:54
Peng_mwhudson: The diff is the part I'm worried about. :P03:54
jelmer_jfroy_: hi03:59
jelmer_jfroy_: there's been another report of that as well03:59
jelmer_jfroy_: I suspect there's a regression since one of the 0.6 releases03:59
jfroy_is there anything at al to be done to salvage that revision?03:59
jfroy_I suspect push_merged_revision will help04:00
jfroy_since it will push merged revisions, even those of otherwise purely local branches I would not otherwise push myself04:00
jfroy_(which I do a lot, scratch branch, private feature branch, merge branches)04:00
jelmer_jfroy_: until we've figured out what the bug is about, no idea if push merged revisions will help04:01
jfroy_I think it will04:03
jfroy_the branch nick on that missing revision if from a branch that was purely local04:03
jfroy_I suspect that specific revision never got pushed to svn04:03
jfroy_so other people, starting from scratch, will have that revision as a ghost04:03
jfroy_push merged revision should avoid that situation04:04
jfroy_(purely local and since then deleted)04:04
jelmer_if you can confirm that is the case, please let me know04:06
jelmer_are you using "bzr branch" or "bzr svn-import" to fetch?04:06
jfroy_branch04:08
RenatoSilvaIs there any documented problems with Novell filesystems?04:08
lifelessno04:08
jelmer_jfroy_: I need to get some sleep, again, if you find more info please let me know04:08
jfroy_will do04:09
jelmer_jfroy_: I hope to put some time into bzr-svn again at the end of the week04:09
jfroy_np04:09
jfroy_it's not a show stopper04:09
RenatoSilvaI get an error about .bzr/branch/lock/[...].tmp/lock, something like that. I think it may be related to big dir names or so. Stupid Novell anyway.04:12
mtaylorlifeless:04:15
mtaylor>>> import cpuinfo04:15
mtaylor>>> cpuinfo.cpuinfo_processor_count(True)04:15
mtaylor204:15
lifelessmtaylor: cpuinfo.processor_count(True) would be nicer04:25
lifelessmtaylor: and for nonstrict mode (which scripts will want,04:25
lifelesscpuinfo.processor_count()04:25
mtaylorlifeless: indeed04:25
lifelessif you can :)04:26
mtaylorlifeless: totally04:26
lifelessmtaylor: don't you need perl first ?04:26
mtaylorlifeless: ew04:26
lifelessmtaylor: to be able to use this, I mean?04:26
lifelessisn't your test thingy that checks cpu counts perl?04:26
mtaylorlifeless: so - do you have any philosophical or other arguments about various ways to build python extension modules in the context of a larger autotools-run project04:27
mtaylorlifeless: yeah. I'll add perl in just a sec04:27
lifelessmtaylor: personally, I hate setup.py being mixed in with autotools04:27
thumperspiv: ping04:27
lifelessno point taking one half assed build system and mixing *another* half assed one in with it04:27
spivthumper: pong04:28
lifelessmtaylor: but, working >> purity04:28
thumperspiv: I have a local lightweight checkout of a 2a branch04:28
mtaylorlifeless: k. I go back and forth on that... because I hate mixing the two - but I also hate telling automake all about python :)04:28
mtaylorlifeless: working bitshift purity?04:28
thumperspiv: bzr info -v tells me it is Branch format 704:28
* mtaylor is confused 04:28
lifelessmtaylor: working is more important than purity04:28
thumperspiv: pushing to LP says: Source branch format does not support stacking, using format:04:29
thumper  Branch format 704:29
mtaylorlifeless: yes yes. trolling04:29
thumperspiv: what can I do to help diagnose04:29
spivthumper: known bug, lemme get you the number04:29
spivthumper: https://bugs.edge.launchpad.net/bzr/+bug/38890804:29
lifelessthumper: its filed as a bug already04:29
ubottuUbuntu bug 388908 in bzr "unnecessary stacking upgrade warning with bzr.dev" [High,Triaged]04:29
thumperok, thanks04:30
abentleyjam: branch push is complete.04:30
thumperspiv: I was wondering if it had something to do with the format 6 remote branch format problems04:30
lifelessthumper: what format 6 remote branch problems?04:31
spivthumper: no04:31
* igc lunch (and afk for a few hours)04:35
mtaylorlifeless: it would be great if ruby and perl had something like AM_PATH_PYTHON...04:50
lifelesswouldn't it just04:57
jfroy_hey, this may be a stupid question, but is there a difference between bzr shelve and looms?05:00
lifelesshuge05:03
Peng_mwhudson: loggerhead/main.py should lose the exec bit, right?05:04
mwhudsonPeng_: i thought i did that, so yes05:05
Peng_mwhudson: Mind if I do it?05:06
Peng_mwhudson: Err, yeah, you did do it. I misread the diff. Sorry!05:06
mwhudsonPeng_: i just did05:06
mwhudsongar, didn't mean to commit that :(05:07
* mwhudson uncommits05:07
Peng_Oh yay, one of my 2a branches just committed suicide.05:07
Peng_Oh, it was just bzr-search.05:09
Peng_...Which doesn't really make a difference, because I usually bug lifeless about these sorts of things anyway. :P05:10
Peng_mwhudson: Hey hey, your revision makes bzr-search explode on 2a. :)05:15
mwhudsonPeng_: hooray05:21
mtaylorlifeless: python. ruby. done.05:23
mtaylorlifeless: perl next05:23
Peng_Buggy bug filed, FYI -- https://bugs.edge.launchpad.net/bzr-search/+bug/39145905:27
ubottuUbuntu bug 391459 in bzr-search "KeyError in _terms_for_file_terms lambda indexing 2a copy of Loggerhead" [Undecided,New]05:27
Peng_"Ubuntu bug"?05:28
Peng_mwhudson: I like 'hi', 'ho', 'ha'. :) Today I used 'Hello' but it felt kind of silly and verbose.05:37
lifelessPeng_: thanks for the bug; will check later05:44
Peng_lifeless: :)05:46
=== abentley1 is now known as abentley
pooliespiv, around? want a quick call in a bit?06:30
bignosebzr-loom crashes, no matter what I do (Debian bug #532947).06:48
ubottuDebian bug 532947 in bzr-loom "bzr-loom: =?utf-8?Q?=E2=80=98loomify?=" [Important,Open] http://bugs.debian.org/53294706:48
bignosehow can I un-loomify a branch so I can keep working on it?06:48
pooliebignose: can you branch individual threads out into separate branches?06:49
bignosepoolie: using what command? whatever I do it crashes with the message as recorded in that bug report.06:49
lifelessbignose: I think its all fixed upstream06:50
lifelessbignose: I'm not sure the branch is corrupted; is it possible that you simply have a broken combination of loom + bzr?06:50
bignoseanything's possible.06:51
bignoseso how can I get back to a working state for that branch?06:53
bignoseor, more relevant to today: a branch that has already been working fine with a loom, but is now unreadable as per that bug report?06:54
lifelessif it *is* a damaged loom, you might be able to get the thread tip ids out using hexdump on .bzr/branch/current-loom, and use the python api to fetch content from the repo06:55
bignoseurk.06:55
wgrantI'd just try upgrading bzr-loom first, though...06:55
lifelessif, as I suspect, you just  have an incompatible loom, get your loom version matching your bzr version, and it should be fine06:55
bignoseI'll wait for the Debian package to update, then.06:55
lifelessjelmer was asking for help on it06:56
bignosethe "Debian Bazaar maintainers" (listed as the maintainer) have yet to give any response to that bug report, though :-(06:56
poolieigc, could you post your "IDE Integration..." message on the project blog?06:57
bignoseis this related to the discussion on the Bazaar mailing list, about the systemic problem of plug-ins that *need* to be at the same version, but never *say* that in the corresponding OS packages?06:57
lifelessbignose: loom tries very hard not to be tied to specific versions06:58
lifelessbut there have been a few API skews that affected it recently.06:58
vilahi all07:29
lifelesshai07:29
igchi vila07:37
vilahi Ian !07:46
=== afk is now known as mthaddon
=== maxb_ is now known as maxb
Peng_Does bug #390563 waste disk space in non-stacked branches or just bandwidth?09:23
ubottuLaunchpad bug 390563 in bzr "absent factory exception from smart server when streaming 2a stacked branches" [Critical,Triaged] https://launchpad.net/bugs/39056309:23
Peng_...S'pose I could check it myself.09:23
vilaPeng: and tell us if you can reproduce it and how09:23
Peng_Oh, right, I forgot that that bug only affects certain branches.09:24
Peng_effects? eh09:28
fullermdAffects.09:28
fullermdWell, the bug may effect certain branches too, but that would be a really weird bug   :p09:28
Peng_Someday, I should learn the difference between those two words.09:29
Peng_Then I should verify "then" and "than". :P09:29
fullermdGenerally, affect is a verb and effect is a noun.09:30
Peng_(OK, I just said that one for the punny thing.)09:30
* Peng_ is obviously a linguistic master. :P09:30
fullermdOh, you can sort them out.  Their knot that hard.09:31
mwhudsonfullermd: you're a bad man09:34
Peng_mwhudson: Shouldn't that be "your a bad man"?09:36
fullermdHey, the proof is in the pudding, just take a different tact.09:37
Lo-lan-doHi all09:54
Lo-lan-doWhat's the status of the HistoryHorizon feature currently?09:54
Lo-lan-do(The use case I'm looking for is the "Old huge project" mentioned on http://bazaar-vcs.org/HistoryHorizon)09:55
Lo-lan-doIs it fulfilled by stacked branches?09:56
Peng_Lo-lan-do: They're not the same thing, but stacked branches let you store the repository on the server, similar to a lightweight checkout, only you've got a real branch.09:59
lifelessLo-lan-do: we have decent performance and excellent compression even for huge old projects, in the 2a format.10:07
Peng_Users will just move the goalposts by making even huger projects. :P10:17
Lo-lan-dolifeless: Huge as in?10:18
Lo-lan-doI'm talking about a 16G CVS repo here.10:18
Peng_lifeless: Do you sleep?10:19
Lo-lan-doWe need to do some cleanup in there, and it'll be smaller with bzr, but still, if the main repo could be limited in history that would certainly help.10:19
Lo-lan-doCould the main repo be stacked on a historical one, thus making day-to-day operations fast while keeping history?10:21
Peng_Lo-lan-do: What do you mean? Like, have a stacked branch pointing to another one on the same machine?10:22
Lo-lan-doI'm very glad to hear about 2a, too.  Do you think it'll be stable before the end of the year?10:22
Lo-lan-doPeng_: Yes.  So daily commits only add to the smaller "current" repo.10:23
Lo-lan-doBut maybe 2a entirely removes the benefits of such an approach, in which case I'll happily recommend that.10:23
asabilhi all10:24
asabilis there a way to setup a configuration (bugtracker settings) that will be propagated during a bzr branch to all users ?10:24
Peng_Lo-lan-do: Having a larger repo isn't a problem. Stacking that would be pointless.10:26
lifelessPeng_: theory has that I do10:27
Lo-lan-doHaving to replicate a large repo with file transfers could cause problems.10:27
lifelessLo-lan-do: that could be massively smaller - perhaps even 1GB total, in 2a10:27
Peng_Lo-lan-do: Actually...a smaller repo would probably save a few ms here and there, but stacking would also cost a few ms here and there. :D10:27
Peng_Lo-lan-do: If the users do "bzr branch --stacked", they won't have to replace the entire thing.10:27
Lo-lan-doI fear that smart repo formats wouldn't be very good at rsyncing (but maybe I'm completely wrong)10:27
lifelessPeng_: but its only EOD, not time-to-sleep now10:27
Peng_Err, replicate*10:27
Peng_lifeless: Ah.10:28
lifelessLo-lan-do: all our formats since pack-0.92 rsync very well10:28
Peng_lifeless: Except when they get packed...10:28
lifelessLo-lan-do: old data is rarely moved on disk, so it rarely shows up10:28
lifelessLo-lan-do: as long as noone runs 'bzr pack', which they shouldn't.10:28
Lo-lan-doGood to know.10:28
Lo-lan-doI guess bzr pack could be run monthly or so, if it's useful at all.10:29
lifelessI wouldn't even do that10:29
lifelessbzr incrementally packs as commits and pushes occur.10:29
Lo-lan-doMore and more excellent.10:29
lifelessevery power of 10 commits it does a full pack automatically10:30
lifelessso if you have 1M commits today, you'd need another 9 million to need another full pack ;)10:30
Peng_Running "bzr pack" occasionally *would* buy you a teensy bit of performance, but it's not enough to matter. Autopacking keeps things from getting out of hand.10:31
lifelessPeng_: actually, full packing when its not needed, with pack ordering, can decrease performance :)10:32
lifelessPeng_: (for a central repo thats only push/pulled with)10:32
Peng_lifeless: Oh? Why? I don't get it.10:32
Peng_Also, Firefox crashed. Arrgh.10:32
Lo-lan-doHow do the new repo formats cope with thousands of branches?10:32
lifelessPeng_: by creating a single large btree that has to be read rather than a smaller one with the most recent data and a larger one that isn't read at all10:32
Peng_lifeless: Ahh.10:33
lifelessyou'd need fairly extreme repos for this to show up10:33
lifelessas we get a 200:1 fanout in our indices today10:33
lifelessLo-lan-do: should be fine; there isn't a single file listing all the branches or anything, so its much of a muchness10:34
Lo-lan-doGood.10:34
Lo-lan-doLast two questions: timeframe for format 2a being officially stable?  And possibility for repo-side hooks?10:35
Peng_Repositories don't really know about branches. They're just big bags of revisions.10:35
Lo-lan-do(The hooks can be done without, they use incron for now)10:35
Lo-lan-do(they=my current client)10:36
Peng_Well, I guess it could matter if you had a complicated history and bzr was bad at choosing compression parents, but it's not.10:36
lifelessLo-lan-do: 2a is supported now; however you need https://bugs.edge.launchpad.net/bzr/1.16/+bug/365615 - we're still polishing the code around the format.10:36
ubottuUbuntu bug 365615 in bzr/1.16 "'AbsentContentFactory' object has no attribute 'get_bytes_as' errors with CHK repository on write operations" [Critical,Fix committed]10:36
lifelessLo-lan-do: we'll be doing a 1.16.1 with that hotfix and possibly a couple of others (to do with stacking on 2a formats)10:37
Lo-lan-doI'm not in much of a hurry, they'll need time to think about it anyway.10:37
Lo-lan-doMy current job is to find quickfixes to make the CVS repo a bit more usable than it currently is.10:38
Lo-lan-do...and to provide recommendations for the longer term.10:38
Lo-lan-doI'm pretty sure bzr will be in that part :-)10:38
lifelessawesome10:39
Peng_Stupid question: how large is MySQL's repo?10:40
Lo-lan-doA bzr branch uses 600 MB (with working-tree)10:40
mwhudsonPeng_: ~600 megs or so10:40
Lo-lan-doThe .bzr is 467MB here10:41
lifelessLo-lan-do: of mysql?10:41
lifelessLo-lan-do: it shrinks by about 2/3rds going to 2a10:41
Lo-lan-do(Branched from lp:mysql-server sometime this week)10:41
Lo-lan-doformat: unnamed, bzr 1.1110:42
lifelessinfo -v will show you the actual repo format10:42
Peng_In 1.11, it'll probably also spend a long time churning through the history, but you can Ctrl+C it.10:42
Lo-lan-dopacks 610:42
Lo-lan-doThis 2/3 number is awesomely impressive.10:43
Lo-lan-doSorry, crashed.  You were saying?10:48
lifelessnothing ;)10:48
lifeless19:42 < Lo-lan-do> packs 610:48
lifeless19:43 < Lo-lan-do> This 2/3 number is awesomely impressive.10:48
lifeless19:46 -!- Lo-lan-do [n=roland@193.252.149.222] has quit [Read error: 104 (Connection reset by peer)]10:48
lifeless19:48 -!- Lo-lan-do [n=roland@193.252.149.222] has joined #bzr10:48
Lo-lan-doCool.10:48
Lo-lan-doAnyway, will you be available for a beer at Debconf? :-)10:49
Lo-lan-doI think I owe a couple to jelmer too.10:49
lifelessI won't be at debconf10:52
lifelesssorry :(10:52
KinnisonYou won't? Boo hiss :-(10:52
Lo-lan-doRMLL in Nantes maybe?10:52
lifelessKinnison: where is it this year ?10:53
Lo-lan-doWestern Spain10:53
KinnisonCacéres, Spain10:53
lifelessyah. Wrong side of the world10:53
KinnisonAbout four hours west of Madrid10:53
lifelesswhen things line up, its awesome to get to such things10:53
lifelessbut as it stands, its awfully hard to get there, and I've used all my conference leave this year already.10:53
Kinnisonfair enough10:54
Lo-lan-doMy plan is to develop the bzr plugin for fusionforge during debcamp/debconf10:54
KinnisonLo-lan-do: coo. sounds amusing.10:54
Lo-lan-do(And git, and hg, and whatever VCS out there if there's a guru around to tell me what needs to be done for his preferred one)10:55
Lo-lan-doI'll probably implement a cpold plugin too, if only as a proof of concept after my refactoring.10:55
Kinnisonlifeless: any plans for a UDS in the UK any time soon?10:55
Peng_cpold?10:56
lifelessnext is US I think; beyond that no idea10:56
Lo-lan-doPeng: The oldest VCS of them all.10:56
Lo-lan-doPeng: "cp foo.c foo.c.old"10:56
Peng_Lo-lan-do: Oh. I use that one a lot!10:57
Lo-lan-doThere you are :-)10:57
Lo-lan-doI'm wondering if I'll have the nerve to actually upload a gforge-plugin-scmcpold to Debian :-)10:58
Lo-lan-doAnyway, food calls.  Thanks for your answers!10:58
Peng_Lo-lan-do: See you later! :)10:59
Peng_Hmm, food. Good idea.10:59
awilkins_Is bzr 2 getting copy of files in inventories?12:01
=== awilkins_ is now known as awilkins
gioelehello12:02
lifelessawilkins: no12:02
awilkinsI suppose it would be yet another awkward format hump to drive over12:03
awilkinsIt's nice to see that not-rich-root is deprecated for 2a12:03
gioeledo stacked branches require the master branch to support the staking in some way? Or this feature can be used with any published branch, regardless of its format?12:06
lifelessthe formats must match12:20
lifelessand bzr won't honour default-stacking requests with very old branches because that would potentially leave the trunk unable to merge from feature branches12:20
gioelelifeless: anyway, is it possible to use stacking with lp:bzr?12:23
lifelessyes, and bzr should do that by default12:24
gioelelifeless: that = stacking? if I do a bzr clone lp:bzr I end up with a stacked branch?12:25
lifelessno12:25
lifelessand doing that isn't very useful or sensible anyway12:25
lifeless(stacking your local copy on the network version12:25
lifeless)12:25
lifelessif you do a bzr push lp:~gioele/bzr/foo, it will stack on lp;bzr automatically12:26
gioelelifeless: but then the remote branch is stacked, not the branch on my PC, if I understood that correctly12:27
lifelessright, but its not useful to stack branches on your pc12:31
lifelessa stacked branch doesn't have enough data in it to even create a working tree12:31
gioeleI see12:32
gioelethank you for the explaination12:35
=== mrevell is now known as mrevell-lunch
ddaaHello.13:39
ddaaI have a collaborator, who is using Windows to write to some files in a linux-based bzr tree over the network (presumably SMB)13:40
ddaaThis appears to cause the executable bit to turn on on every file he edits from the network. Which is kind of annoying to me.13:40
ddaaIs there a way to edit files in a linux bzr tree from windows over SMB that will not cause those files to be recorded as executable when committing from linux.13:41
ddaaNote that I do not really care about whether the becomes executable on the linux filesystem. I just do not want bzr to record a permission change.13:42
matkorHi ! what is easiest way to apply changes (uncommited) from given branch to current one ?13:48
Lo-lan-dobzr merge --uncommitted $given13:49
ddaabialix: Can I make my collaborator use the bzr-x-bit plugin on linux to solve this problem?13:49
bialixddaa: no13:49
matkorLo-lan-do: Looks great, thank you very much !13:49
Lo-lan-domatkor: Then you'll probably do "cd $given ; bzr revert" or so13:50
bialixx-bit plugin does reverse thing13:50
Lo-lan-do(Be sure to only do that afterwards)13:50
ddaabialix: doh, any idea?13:50
bialixSMB settings maybe? I'm not Linux expert13:51
ddaaI know, but you're the expert of all things windowish around.13:51
bialixIIUC this is always problem: try to open USB flash disk on Linux and all files have x-bit set13:51
bialixddaa: IIUC your situation: your collaborator working directly with files over the network?13:52
bialixso why he does not have separate tree on his local disk?13:52
bialixe.g. lightweight checkout13:52
ddaaYup. As I said, I do not care much what the filesystem says, I just do not want this nonsense to contaminate my carefuly tended bzr branch.13:52
bialixlightweight checkout will help you13:52
ddaabialix: out of convenience, he's editing, over SMB, files that are used by a live web server on linux.13:53
* bialix out of ideas13:53
bialixI'm usually working via ssh in those cases13:54
ddaaI do not want to worry about running the web server on windows, but I would like him to be able to retain the convenience of editing files on his big-screen windows system while he's testing IE compatibility.13:54
* ddaa contemplates how all evil in computing those days can be ultimately traced to Internet Explorer.13:54
bialixand Bill G. of course!13:55
ddaaI do not like to take things personally. It's fine to hate pieces of technologies, but not people.13:56
matkorLo-lan-do: Sure, I will even commit first on current :)13:56
bialixas you wish, I've tried to make joke13:56
ddaabialix: sorry :) I'm just annoyed about how it became fashionable to hate B. Gates and Microsoft over the past few years.13:57
ddaaI mean, they actually invented a few good things.13:57
ddaaLike the scroll wheel.13:57
ddaaThinking of it... Microsoft is actually pretty good at making mice, keyboards and joysticks...13:58
LeoNerdMS mice are quite nice, yeah..13:58
LeoNerdProbably because Logitec make them?13:58
garyvdmWhen Bug 1 gets fixed people will be replace those with Mark S. and Canonical :-P13:59
ddaaLeoNerd: that might have something to do with it :)13:59
* garyvdm ducks and runs13:59
ddaagaryvdm: a few people already have.13:59
garyvdmIs ubottu asleep/13:59
garyvdmbug 0000113:59
ubottuhttps://bugs.launchpad.net/ubuntu/+bug/1 (Timeout)13:59
ddaaNot ubottu, but most of the time this page times out.14:00
ddaasomething to do with insanely large amount of comments, dups, subscribers and so on and so forth.14:00
fbondHi.  In the old bzr shelve, I could `bzr shelf show FOO`, I think, to see a diff representing that particular change on the shelf.  Can I do that with the new shelve/unshelve commands?14:00
fbond`bzr unshelve --dry-run` shows me a stat-like representation of the change, but not a diff.14:01
garyvdmbug 39147114:01
garyvdmbug #39147114:01
ubottuLaunchpad bug 391471 in tortoisebzr "Inconsistent Diff behavior" [Undecided,New] https://launchpad.net/bugs/39147114:01
garyvdmhttps://bugs.launchpad.net/ubuntu/+bug/114:02
ubottuError: Could not parse data returned by Ubuntu: The read operation timed out (https://launchpad.net/bugs/1/+text)14:02
fbondgaryvdm: That bug has a lot of comments.14:02
garyvdmlol14:02
garyvdmoops - I've now cause to to try 3 times...14:03
garyvdm*caused it14:03
=== mrevell-lunch is now known as mrevell
ddaaOkay it turns out there should be two ways of fixing it.14:11
ddaa1. setting the "create mask" in smb.conf to something like "644", so files are not create executable14:11
ddaa2. configuring the windows-side editor to save files in place (instead of doing the copy-rename thing).14:12
asabiljelmer: ping ?15:07
jelmerasabil: pong15:18
asabiljelmer: did you receive my filter-branch merge request for bzr-rebase ?15:18
jelmerasabil: no, I didn't see anything15:32
asabiljelmer: I did send it a while ago, maybe I should resend it ?15:32
jelmerasabil: please do15:33
Lo-lan-doAre pack files often modified?15:33
Lo-lan-doOr are they only generated once by a commit or a repack and not changed afterwards?15:34
Lo-lan-doI'm pondering about risks of filesystem fragmentation.15:34
jelmerLo-lan-do: pack files are not modified themselves, but new pack files will be created regularly15:42
jelmer(e.g. by commit, repack, push/pull etc)15:42
Lo-lan-doOkay, so little risk for fragmentation increasing over time.  Good, good.15:50
mxpxpodjelmer: ping?15:53
jelmermxpxpod: pong15:56
mxpxpodjelmer: I'm trying to mirror dojotoolkit.org's svn repository using bzr-svn's svn-import, but we have a strange branching and tagging method16:00
mxpxpodbasically, each project (dojo, dijit, dojox) has it's own sub-repository (src/dojox/{branches,tags,trunk})16:01
mxpxpodbut then when we release, we create a structure in src/branches/{release_version} that copies current trunk of each project into that directory16:01
mxpxpodsame with tagging with the tags directory16:01
mxpxpodjelmer: if you want to take a look, it's at http://svn.dojotoolkit.org/src16:03
abentleyjam: In case you missed it earlier, the push to /home/abentley/branches is complete16:04
mxpxpodjelmer: src/trunk is our old code-base16:05
mxpxpodjelmer: the problem is that when I did the svn-import, I specified branches=branches/*;*/branches/*;*/trunk and tags=tags/*;*/tags/*, but no tags showed up16:07
mxpxpodjelmer: am I going to have to tag things manually?16:07
jelmermxpxpod: sorry, phone, back in a few minutes16:11
=== Kissaki^0ff is now known as Kissaki
asabiljelmer: just sent it, you should receive it on your samba mailbox16:16
jamabentley: thanks16:18
jamrobert says you can lftp the broken branch16:18
jamwhich works well, too16:18
abentleyjam: was the lftp message for me?16:21
jamyes16:22
jamnot that *you* need to16:22
jamjust that it is another branch I can use16:22
abentleyjam: I don't understand.  by "broken branch", you mean db-devel?16:23
jamcinnamon-and-spice, IIRC16:23
jamabentley: sorry, crimson-and-clover16:23
abentleyjam: Oh, you'd like a copy of lp:~sinzui/launchpad/crimson-and-clover ?16:24
=== vxnick is now known as vxnick_afk
abentleyjam: I've mirrored crimson-and-clover for you at /home/abentley/crimson-and-clover16:32
mxpxpodis there a way to register a directory service and have it create a shared repo for multiple branches for certain urls?16:34
asabiljelmer: did you get it this time ?16:37
jelmerasabil: yep, thanks16:37
asabilcool16:38
jelmermxpxpod: re16:41
jelmermxpxpod: that should've worked16:42
jelmermxpxpod: did svn-import say anything about the layout being used?16:42
mxpxpodjelmer: Using repository layout: WildcardLayout(['branches/*', '*/branches/*', '*/trunk'],['tags/*', '*/tags/*'])16:43
* awilkins thinks bzr-svn should have a layout option for "total freakin' mess"16:43
mxpxpodawilkins: :)16:43
mxpxpodjelmer: I think the problem is that we have src/tags/release-1.3.1/dojo16:44
kirklandjelmer: hi there16:44
mxpxpodand dojo resides in src/dojo/{trunk,branches}16:44
kirklandjelmer: i'm still getting a vcs import update failure for qemu's git16:44
kirklandjelmer: i was under the impression that LP's rollout this morning had your latest fixes?16:44
kirklandjelmer: http://launchpadlibrarian.net/28287607/qemu-git-log.txt16:45
kirklandjelmer: https://code.edge.launchpad.net/~vcs-imports/qemu/git16:45
=== abentley1 is now known as abentley
jelmerkirkland: I'm not sure what version of bzr-git launchpad is using16:47
kirklandjelmer: is there any way that I can run this script/process locally, on my hardware16:48
kirklandjelmer: and push to a bzr branch in LP?16:48
kirklandjelmer: i'm happy to cut vcs-imports out of the loop, until they get that fixed16:49
kirklandjelmer: i need a bzr/git mirror up ASAP16:49
jelmerkirkland: yeah, just install bzr-git and run something like this from a cronjob:16:50
kirklandjelmer: what's bzr-git?  a bzr pluggin?16:51
Jc2kyes16:51
jelmerkirkland: "bzr svn-import git://git.savannah.nongnu.org/qemu.git qemu; bzr push -d qemu lp:~kirkland/qemu/git-import"16:51
jelmersorry, git-import rather than svn-import obviously16:52
kirklandjelmer: s/svn-import/git-import/16:52
kirklandk16:52
kirklandjelmer: thanks16:52
jelmerkirkland: alternatively if you just need the main branch you can just use "bzr branch" / "bzr pull" with git URLs16:53
mxpxpodjelmer: I'm figuring for this strange layout that we have that I'll have to do some sort of custom import for this repo16:54
kirklandjelmer: and getting git-import ....16:54
kirklandjelmer: cd .bazaar/plugins; bzr branch lp:bzr-git ?16:55
jelmerkirkland: yep16:55
jelmerkirkland: you'll also need dulwich, which is a dependency of bzr-git16:55
jelmermxpxpod: there don't seem to be any actual tags for dojo that bzr-svn could import16:55
jelmermxpxpod: http://svn.dojotoolkit.org/src/dojo/tags/ is empty16:56
kirklandUnable to load plugin 'git'. It requested API version (1, 17, 0) of module <module 'bzrlib' from '/usr/lib/python2.6/dist-packages/bzrlib/__init__.pyc'> but the minimum exported version is (1, 13, 0), and the maximum is (1, 13, 1)16:56
mxpxpodjelmer: yeah, we tag dojo, dijit, dojox, and util at src/tags/{release_name}/{project_name}16:56
jelmerkirkland: the version of bzr you have locally is too old, you need at least 1.14 for bzr-git16:57
kirklandjelmer: best way of getting a newer bzr onto a jaunty machine?  a ppa, perhaps?16:59
jelmerkirkland: yeah, there's a bzr ppa (~bzr on lp)16:59
kirklandjelmer: cheers, thanks for your help, dude16:59
mxpxpodkirkland: https://launchpad.net/~bzr/+archive/ppa16:59
jelmermxpxpod: so in that case it seems your tags setting is incomplete16:59
mxpxpodjelmer: right, but how do I tell svn-import that the tag is at tags/release-1.3.1/dojo rather than dojo/tags/release-1.3.1 ?17:00
mxpxpodand then how do I get it to translate the former to the latter for the conversion?17:01
jelmermxpxpod: try tags/*/dojo17:02
mxpxpodjelmer: what if I'm importing the whole repo at one time?17:02
=== abentley1 is now known as abentley
jelmermxpxpod: shouldn't be any different17:05
mxpxpodjelmer: so, just put tags/*/{project_name} for each project?17:06
jelmermxpxpod: yeah, that's how it's intended to work at least17:06
mxpxpodjelmer: same with branches?17:07
jelmermxpxpod: yeah17:07
mxpxpodjelmer: welp, here goes nothing ;)17:09
=== abentley1 is now known as abentley
=== vxnick_afk is now known as vxnick
marianomhi guys, can anyone tell me why I'm hitting this error? bzr: ERROR: Reserved revision-id {null:}17:55
marianomFirst time I see it17:55
mxpxpodjelmer: that didn't work :(18:02
mxpxpodjelmer: I did this: bzr init-repo --1.14-rich-root test; cd test; bzr svn-import http://svn.dojotoolkit.org/src .18:05
kirklandjelmer: http://pastebin.ubuntu.com/203025/18:20
kirklandjelmer: dulwich is installed18:20
kirklandnever mind18:24
kirklandbzr: ERROR: exceptions.ImportError: bzr-git: Dulwich is too old; at least 0.3.1 is required18:28
kirklandi installed dulwich from the ppa18:28
jelmerkirkland: I don't think there's a current dulwich packaged in the ppa18:38
kirklandjelmer: okay, thanks.18:38
jhhi, I'm trying to get to the newest revsion of a branch on launchpad. I had already a local copy of the repository and changed some things (and committed it locally). how can I change to the current remote revision? ignoring all my local changes18:40
dashyou want to remove your local changes?18:41
dashor merge the remote ones into your local branch18:41
jhI want to ignore my local changes18:41
dashbzr pull --overwrite <remote url>18:42
dashif by 'ignore' you mean 'remove'18:42
jhy18:42
jhthx!18:42
ddaaThere's something annoying about shelve storing a pack in the shelf instead of a diff.18:44
dashyes18:44
ddaaPreviously, I could go into the shelf, and modify the shelved diff.18:44
dashalso the shelve plugin has more features than the builtin18:44
ddaaIn this instance, I want to split a diff hunk.18:45
dashme too18:45
* ddaa shakes dash's hand18:45
ddaadash: so what is it you do you to satisfy you obsessive-compulsive need for clean commits?18:45
dash(I am trying to split up a very large diff into multiple unrelated ones via loom+shelve)18:45
dashddaa: Nothing easy.18:46
ddaathat kind of sucks18:46
dashyes18:46
dashi think i am going to switch back to shelve118:46
ddaayou mentioned a different between a plugin and a builtin18:46
dashyes, the 'shelve' in bzrtools is different18:47
ddaaI did not realize shelve was now a builtin18:47
dashso yeah, try 'bzr shelve1'18:47
ddaaYay, happiness.18:48
ddaabzr shelve1, manual diff editing, bzr unshelve118:48
ddaadash: thanks pal18:49
dash<318:49
=== vxnick is now known as vxnick_afk
=== mthaddon is now known as afk
mwhudsonjelmer_: hello, https://code.edge.launchpad.net/~vcs-imports/mnemosyne-proj/maemosyne still seems to be failing with bzr 0.4.0, i can't remember if i asked you about this one already :)20:26
mwhudsonbzr-git, obv20:26
=== afk is now known as mthaddon
=== cprov is now known as cprov-afk
pooliehello21:37
* beuno waves at poolie 21:37
pooliegood morning beuno21:37
beunohow are you poolie?21:38
pooliegood thanks21:40
pooliewoke up a bit too early though21:40
pooliehow are you?21:40
beunopretty good21:41
beunoslow day for me today21:41
pooliehow is 2a dogfooding going for you?21:42
pooliei realize bug 390563 is a big deal21:42
ubottuLaunchpad bug 390563 in bzr "absent factory exception from smart server when streaming 2a stacked branches" [Critical,Triaged] https://launchpad.net/bugs/39056321:42
beunopoolie, that's really making things chaotic21:53
beunobut, apart from that, things seem much faster21:53
beunoI've upgraded about 30 branches at the office to 2a21:54
beunoand it's gone well21:54
beunono problemas at all21:54
beunosomething to note is that at least half the branches didn't go down in size from 1.921:54
poolieok, interestig21:56
pooliehow about if you repack them?21:56
beunoI do, all of them21:56
beunoinitially the branches are larger21:56
beunoand then they go down to about the same size after a pack21:56
beunothey are branches with heavy binary usage21:57
=== Kissaki is now known as Kissaki^0ff
lifelessoh wow22:32
lifelessdid all codeimports die overnight?22:32
lifelessmwhudson: ^22:32
mwhudsonlifeless: no22:32
thumperlifeless: no, we've just now automatically failing imports that have failed lots22:32
mwhudsonoh yes, that's a lot of spam in my codeimport folder...22:33
lifelessvila: still around?22:35
pooliehello mwhudson, lifeless22:38
mwhudsonhi poolie22:38
lifelessmwhudson: you're going to cherrypick bug 365615 today, yes?22:49
ubottuLaunchpad bug 365615 in bzr/1.16 "'AbsentContentFactory' object has no attribute 'get_bytes_as' errors with CHK repository on write operations" [Critical,Fix committed] https://launchpad.net/bugs/36561522:49
mwhudsonyeah, we should22:50
mwhudsonlifeless: it won't hit prod until uk versions of 'today' of course22:50
mwhudsonlifeless: is there any sense in waiting for a fix to the other absentcontentfactory bug to maybe appear?22:51
mwhudsonlifeless: also, is the fix for that bug in the 1.16 branch?22:51
mwhudsonseems no22:52
mwhudsoni guess i should talk to the 1.16 release manager22:52
mwhudsonwho should be waking up around about now...22:53
lifelessmwhudson: its not in the 1.16 branch yet22:56
lifelessmwhudson: just cherry pick22:56
lifelessand no, no sense waiting22:56
poolielifeless: did you talk to jam today (au time)?22:59
pooliei was just going to call him and say hello22:59
lifelesspoolie: no; I'd like to to pickup the state on the bug23:00
lifelesshe commented about 7 hours ago on the bug, but hasn't mailed a status note, nor has vila23:00
lifelessso AFAICT it hasn't advanced any23:00
lifelesswhich may just mean that a lot of work hasn't ruled anything out nor proven anything23:01
lifelesspoolie: I'll be on m mobile; just grabbing a hot brekkie23:03
poolielifeless: john's sending an update now23:12
FibeRichioHi, I wanted to exclude a directory called 'webstats' from the revision, so I did 'bzr ignore ./webstats'. It told me that there already existed a directory in the revision and that I should use the remove command, but after I did 'bzr remove webstats', the entire directory dissappeared from my filesystem?23:17
lifelessback23:20
lifelesspoolie: thanks23:20
lifelessFibeRichio: right, it did that because it was versioned23:21
lifelessFibeRichio: do this:23:21
lifelessbzr revert webstats23:21
lifelessbzr remove --keep webstats23:21
FibeRichiothanks, that looks bettter :)23:21
lifelessnp23:25
rockyjelmer_: hey, does deleting tags not work with bzr-svn ?23:28
pooliejam, lifeless,  i filed bug 39185123:47
ubottuLaunchpad bug 391851 in bzr "groupcompress holds a compressed full text for each file in each group" [Medium,Confirmed] https://launchpad.net/bugs/39185123:47
pooliejml that's what you mentioned last night23:47
lifelessoh that reminds me23:47
pooliei don't think there was a bug for it previously23:47
lifelessI'll file one on skinny networkin23:47
lifelessg23:47
poolieok, refer back to this one23:47
pooliei mean put in a see also23:47
lifelessActually23:48
lifelessI think yours really should just be turned into 'skinny on the network please'23:48
lifelessas the other aspects were all considered and balanced during design.23:48
lifelesssingle commit having a full text isn't a drawback, as it makes commit fast; and group size is dynamically tuned based on file size23:49
lifelesspoolie: ok if I repurpose it? or should I close it and file a targeted one for networking?23:49
poolieeither is ok23:51
pooliei'd like the other one perhaps open at least at low priority23:52
poolieso it has a handle23:52
lifelesspoolie: I'm not clear what it is meant to be though - I don't see anything in 391851 as a bug or defect, other than networking not being skinny23:53
lifelesspoolie: quick call?23:55

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