lifelessjam: also new patch; btree refactoring that was needed in pack repo00:00
lifelesspoolie: slugging?00:32
abadger1999When branching from launchpad, does one have to have a launchpad account?01:00
mwhudsonthe branches are accessible over plain old http01:00
abadger1999I keep getting a permission denied error.01:00
abadger1999Okay, how do I translate the lp:BRANCH URL to an http URL?01:01
lifelessabadger1999: private branches require a lp login01:01
lifelessabadger1999: because access control01:01
abadger1999lifeless: How do I tell if they're private?01:02
mwhudsonabadger1999: what are you actually doing?01:02
abadger1999I'm updating the Fedora package.01:02
mwhudsonabadger1999: as in, pastebin01:02
abadger1999And I'm writing instructions for other people to retrieve the branch in case they need to verify that what I packaged is what's upstream.01:03
abadger1999So I just need to figure out how to tell them to retrieve: "bzr branch lp:trac-bzr"01:03
mwhudsonthat should work for you01:04
abadger1999mwhudson:  ahh.... Thanks!  I see my error now.01:05
abadger1999I do have a launchpad account registered in bazaar.conf01:05
abadger1999But I've changed my ssh key since it was registered.01:05
abadger1999So I was assuming lp: was erroring because I was anonymous but it was really because my ssh key didn't match.01:06
=== mw is now known as mw|out
lifelessspiv: sorry for death-by-a-thousand-replies01:40
lifelessspiv: also I think you might benefit if you think about hooks a little differently;01:41
markhjelmer: ?01:41
lifelessspiv: because they are intended to allow plugins to add actions, they -by definition- cannot operate on a per-hooked-thing basis01:41
lifelessspiv: rather they look like C-object-style with object as the first parameter;01:42
lifelessspiv: as such, its _never_ right to add a hook function just-for-one-instance; instead its always add-hook-thunk, which acts-when-appropriate01:42
spivlifeless: yeah.  That's why I had the alternative implementation that did just that.  But it seemed more complicated in this instance.01:48
lifelessspiv: WeakKeyDictionary FTW ?01:49
lifelessspiv: surely thats all you need01:49
spivThe problem is that WeakKeyDictionary just silently drops the entry when the ref goes away.01:49
spivI just had an idea.01:49
spivI *might* be able to get away with using a WKD + my own weakref, so that the callback on my weakref can retrieve the value out of the WKD before it goes away.01:50
lifelesssubclass ReferenceType01:50
spiv(Weakref callbacks are guaranteed to be called in reverse order of weakref creation)01:51
spivRight, I can do that too.  But again that's significantly more complicated.01:51
spivI'm willing to add the complexity if people think its worth it, but I thought that it would be best to try the simplest approach first.01:52
lifelessI think fitting the pattern hooks are designed around is simpler01:52
spivIt is frustrating that WKD is so close to what I need, but not quite there.01:52
lifelessthe thing that is unique in this case is wanting a 'done with' event01:52
lifelessand I think it would be easier for you if you had a 'done with medium' hook :P01:53
spivIt would be.  Any suggestions on how to implement that easily? :)01:54
lifelessadd a __del__ to Medium01:54
spivIt already has one.01:54
lifelessadd a hook that triggers during del01:54
lifelesswith a signature of (weakref(hook))01:54
spivI'm not sure why I haven't tried using that __del__, actually.01:55
lifeless(so that we aren't adding refs to the hook accidentally)01:55
lifelessspiv: this is I think why I mentioned /thinking/ about hooks differently01:55
spivWell, I already did try thinking that way.01:55
spivAs I hope the alternative patch in my original mail shows :)01:56
lifelessspiv: sure, I think I'm expressing myself badly01:56
lifelessI just mean that it seemeed simpler to you to try and work against the current01:57
lifelesswhich suggests you haven't quite internalised the reasons behind the stream01:57
lifeless[to me]01:57
lifelessaaaanyhow, I'll stop blathering and let you get on with it;01:58
spivWell, I don't think so.  I just failed to see a nice way for a single hook function to find the right medium to associate with when using weakrefs.  That didn't mean there wasn't, just that I didn't find one yesterday afternoon.01:59
lifelessspiv: isn't the hook called  with the medium ?01:59
spivI definitely appreciate that it's not so nice to have lots of hook function registrations.01:59
spivIt is, but I was keeping weakrefs in the counter object to keep the impact as obviously minimal as possible.02:00
spivAnd WKD is unfortunately nearly but not quite what I needed...02:00
lifelessa hook even on del would do it, and will trigger when the WKD will too02:01
spivYeah, seeing as there's already a __del__ I think I may as well use that.02:01
spivIf there wasn't already a __del__, I think weakrefs would be the way to go.02:01
jammarkh: yes?02:08
markhI notice the 1.7 branch is labeled as 1.7.1rc1 - should I just skip a 1.7final?02:08
markhor jump back a rev or 202:09
markh(maybe I should be using a tag on that branch?  I haven't looked I admit...)02:09
jammarkh: We need to do a 1.7-final02:10
jamyou can either use the tarball02:10
jamor use rev 370502:10
markhok, will do.  When do you expect 1.7.1 final?02:12
markhheh - so, how do I force a branch *back* a revision?  Using -rfoo when the current rev is greater than foo doesn't seem to do anything?02:15
fullermdWhat -rfoo?  pull works...02:15
lifelessmarkh: uncommit02:17
lifelessmarkh: or pull -rfoo --overwrite02:17
markhlifeless: I just thought of override as you said it - sorry for the noise!02:17
markhoverwrite too :)02:18
lifelessbzr heads -> 1.6GB used02:19
fullermd1.6 billion heads are better than one.02:21
lifelesseeepic fail02:21
lifelessI think its the svn-branch-open-leak-fail02:23
lifelessjelmer: is that fixed?02:23
jamlifeless: so generally, I think there is a lot of cleanup we *could* do, and some discussion to be had. But we can do that after it lands.02:24
lifelessjam: 'it' ?02:25
jamlifeless: iter_changes in pyrex02:25
lifelessah yes02:25
lifelessI want to make it much smaller and more many-function clean02:25
spivOh right, the __del__ isn't on SmartClientMedium, just one of its subclasses.  I'll see if I can workaround WKD's deficiency...02:25
lifelesssuper(self, Class).__del__()02:26
jammarkh: well for making a release, you are probably fine to do "bzr revert -r -2" make foo; bzr revert ; make foo02:26
jamand build both the 1.7-final and 1.7.1rc102:26
jamlifeless: I'm pretty sure it is super(Class, self).__del__() :)02:27
spivlifeless: I really don't want to add __del__ to objects that don't already have them02:27
lifelessjam: MEH, DETAILS02:27
lifelesssorry for shoutig02:27
spivlifeless: that would mean the debug option would be penalising things even when not used.02:27
markhjam: ah, thanks.  As it turns out I've built 1.7.1rc1 first, but that should be fine as it stands.  I've build 1.7 and will testing that now...02:27
jamspiv:  so as always, can we push the __del__ into an attribute other than self, to avoid circlese02:27
lifelessspiv: sometimes its the right thing to do though02:28
spivjam: or, just use weakrefs :)02:28
jamI wasn't following closely, just poking at __del__02:30
lifelessjam: oh bugger02:50
lifelessjam: guess what I just did02:50
jamfound a problem, or submitted your version?02:50
lifelesssubmitted la version robert02:50
lifelessand then took a shower, so its well and truely in progress02:50
jamnp, we can always submit another one :)02:51
lifelessdo you want to queue yours up now ?02:51
jamyou didn't do any other changes?02:53
lifelessspiv: is there a way to tell RemoteRepositoryFormat to create a specific backend format ?03:15
spivlifeless: I think if you pass something other than a RemoteBzrDir to RemoteRepositoryFormat.initialize it might work.03:19
lifelessI'm trying to test RemoteRepository with a chk_bytes supporting backend03:20
spivI don't think we have many tests of RemoteRepo on top of specific backends.  The ones we do have probably all do it by making the backend repo directly, then re-opening that via a SmartTCPServer_for_testing.03:22
lifeless+class TestCaseWithRepositoryCHK(TestCaseWithRepository):03:28
lifeless+    def make_repository(self, path):03:28
lifeless+        TestCaseWithRepository.make_repository(self, path)03:28
lifeless+        return repository.Repository.open(self.get_transport(path).base)03:28
lifelessthat works, ilttle fuglay03:28
markhhrm - 'bzr selftest' has 41 threads running for me!03:45
markhmake that 72 :)03:46
markheek - and counting - just crashed through 300!03:49
markh500!  How much can vista on a vm handle!03:51
mwhudson'running' in a very loose sense i think03:53
markh1/2GB ram, 6000 handles open...03:55
lifelessmarkh: well it is *testing* :P04:19
lifelessjam: this is wrong/missing:04:44
lifeless# source_branch: http://bzr.arbash-meinel.com/branches/bzr/1.8-\04:45
lifeless#   dev/trivial_python_compat04:45
lifelessanyone around for a quick irc teddy bear session04:59
* beuno tries to resist asking what that would be04:59
AfCI just used Google's image search on "IRC teddy bear" and got http://images.villagevoice.com/issues/0521/expo-011s.jpg Something is clearly wrong with the world.05:04
mwhudsonAfC: i need a drink now05:05
fullermdAnd a cigarette.05:06
mwhudson(possibly i needed a drink already, before clicking that link, mind)05:08
fullermdPossibly you had a drink already, if you're clicking links AfC pastes with disturbing prose around them   :p05:11
kgoetzi'm thinking this image may not be good to clik at work05:14
AfCI figured I had done my part to make it clear that the aforementioned link was for mature audiences only. That said, the real question is what Robert is doing looking for an IRC teddy bear. Fascinating, really.05:14
beunoand why he would need someone else...05:15
fullermdI was going to say I myself could use an IRC piggy bank, but I figured I should google it first, just to be safe.05:17
fullermdAnd somehow I end up with http://gadgets.boingboing.net/2008/06/19/bandai-ikemenbank-pi.html05:17
* fullermd boggles.05:17
* beuno wonders if google substitute "IRC" for something kinky internally05:18
fullermdWell, I still sometimes end up with 'International Reply Coupon' on my first acronym-fault...05:19
lifelessAfC: when designing things its often easier to discuss it with someone05:22
lifelessAfC: they are a teddy bear, if they are not needed for content so much as for the fact-of-discussion05:22
lifelessAfC: and being on IRC was well, being on IRC :P05:23
fullermdWell, way to make it boring in comparison   :p05:28
fullermdHere we were, picturing stuffed animals engaging in all sorts of bazaar acts...05:29
jmllifeless: it's also called "rubber ducking" sometimes.05:30
lifelessjml: thats so much more open to misinterpretation05:30
lifelessjml: it has rubber, and water sports, and its fowl05:30
jmlquick! get me my pun glasses!05:31
lifelessfingers crossed, all my status work will have landed in 30 minutes or so05:38
vilahi all !06:53
lifelessyay, status stuf landed06:57
lifelesshave a good weekend all06:57
fullermdWeekend indeed...  it's only an hour into Friday   :p07:07
beunoyou too lifeless07:08
* beuno is happy to be on the other side for once07:08
poolienight lifeless07:15
poolieabentley: bb is down :-/07:43
abentleypoolie: restarted07:44
vilaabentley: which one ? :D08:02
vilaabentley: joke aside, I playfully thought about multiple BB instances... interesting problem (not worth the trouble though)08:04
poolieoh, thanks!08:28
pooliehi vila, abentley08:28
poolievila, that was a 'tweak' overall for the 2.6 stuff08:29
vilaha, ok, hmm, I'm checking a bit more but I see your points and will merge most of it (at least)08:30
vilaI've checked that Exception.message has indeed be deprecated, that leave only the unicode stuff08:31
tvainikawhat means format: unnamed in bzr info? e.g. I create bzr init-repo --1.6.1-rich-root and then branch or checkout under it, then shared repo shows format: 1.6.1-rich-root, but branch under it format: unnamed.09:10
spivtvainika: it means bzr doesn't have a short label for the combination of branch format & repo format you have.  "bzr info -v" will tell you more.09:13
spivtvainika: "unnamed" isn't very helpful.  There's a bug filed about that: https://bugs.launchpad.net/bzr/+bug/20208309:15
ubottuLaunchpad bug 202083 in bzr "need better short names for format combinations" [Undecided,New]09:15
=== cjwatson_ is now known as cjwatson
jonnydeebzr revert returns with      bzr: ERROR: Could not acquire lock "D:/duscher/docs/ProjektM/dev/.bzr/checkout/dirstate"12:44
jonnydee i am using bzr.dev newest version and I rebooted my computer to make sure there is no system lock....12:44
awilkinsjonnydee: I think that's either been fixed or I saw a patch in the pipe that fixes it13:13
* awilkins wonders if anyone else but him uses msvc 7.1 to build the extensions13:13
jonnydee1awilkins: ok, so until now the fix seems not to be in bzr.dev because I did an update of my bazaar installation right before I tried to revert... So I hope the patch comes soon, thanx :)13:31
awilkinsjonnydee1: I think it's http://bundlebuggy.aaronbentley.com/project/bzr/request/%3C48DC0B60.4010201%40arbash-meinel.com%3E13:33
awilkinsSo if you do a bzr merge http://bundlebuggy.aaronbentley.com/download_patch/%3C48DC0B60.4010201@arbash-meinel.com%3E  to your bzr.dev, maybe it will fix it :-)13:33
=== asabil is now known as asabil_is_not_as
=== asabil_is_not_as is now known as asabil
asabilis there a way to cherry-pick commits between branches ?15:40
=== _Verterok_ is now known as Verterok
james_wasabil: bzr merge -rx..y ../other-branch15:47
asabilwell, real cherry picking with merge tracking15:48
asabiland commit message preservation15:48
luksbzr replay -rx..y ../other-branch for the second point15:50
=== fta_ is now known as fta
=== ja1 is now known as jam
abadger1999I'm looking at a bug in the trac-bzr plugin and have a question.16:19
abadger1999bzr's  NEWS file says that _get_weave() was deprecated in favour of RevisionTree.plan_merge().16:19
abadger1999But there is no plan_merge() in Tree.16:19
abadger1999Does the document mean: One of these: 'plan_file_lca_merge', 'plan_file_merge' ?16:20
abadger1999Or does it mean VersionedFile.plan_merge() ?16:21
abadger1999Looks like I'm working on https://bugs.launchpad.net/trac-bzr/+bug/26330016:39
ubottuLaunchpad bug 263300 in trac-bzr "Does not work with bzr 1.6" [Undecided,New]16:39
Okkinhow can I generate a patch (like the send command) unsing directly bzrlib ?16:42
Odd_BlokeOkkin: Do you want a patch or a bundle?16:46
Odd_Blokejelmer: How do you keep track of what API breaks are going on in bzrlib that might affect you?16:47
Odd_BlokeOkkin: i.e., are you looking to generate a patch, or do you want to be able to merge from the produced output?16:47
OkkinOdd_Bloke: a blundle16:48
Okkini want to merge the result in a remote branch that is only accessible by email16:49
Odd_BlokeOkkin: Then I'd suggest looking at the code for the send command. :)16:49
Okkinthat want i was doing in fact :)16:50
Okkinbut I'm lazzy on friday16:50
Odd_BlokeOkkin: Well, that's what most of us would have to do to help you, and it's Friday for us as well. ;)16:51
OkkinOdd_Bloke :)16:51
OkkinI understand so well the friday laziness16:53
Odd_Blokesabdfl had a sudden posting spree to the bzr list about 16 hours ago.16:58
LarstiQOdd_Bloke: read NEWS?17:04
Odd_BlokeLarstiQ: Sure, but at what point?17:07
Odd_BlokeBecause presumably he's going to want to have made the changes before the release containing said NEWS.17:07
LarstiQOdd_Bloke: right17:29
LarstiQOdd_Bloke: pull bzr.dev from point to point and read NEWS? :)17:29
* LarstiQ heads off17:29
Odd_BlokeLarstiQ: Yeah, I'm wondering how that could be improved.17:35
Odd_BlokeOr, rather, if it needs to be.17:35
resolvehi folks. i've been using mercurial for the last year, and i was using bzr and arch before that17:39
resolvesince a year has passed i've decided to survey the field again17:39
Odd_Blokeresolve: Hi. :)17:40
resolvei've been very happy with mercurial - generally it did what i wanted without trouble17:40
resolvebut bzr seems to have made decent progress recently, and the ability to use launchpad does seem nice17:41
resolveany of you here switched to/from bzr from mercurial?17:41
resolvehas 1.7 made any changes related to the repo blowout on http://vcscompare.blogspot.com/2008/06/git-mercurial-bazaar-repository-size.html ?17:43
Odd_Blokeresolve: I'm not sure about 1.7, but there are some improvements of that ilk in the pipeline.17:46
Odd_BlokeIn the development{1,2} formats.17:46
Odd_Bloke1.7 may have included development1, I'm not sure...17:46
=== gotgenes_ is now known as gotgenes
vilala la la, pqm blocked17:56
vilaany LOSA around ?17:57
vilajam: pqm is blocked on a successful merge, once again :-/ I hate leaving for week-end like that, could find a LOSA and kill the offending (ssh ?) process (worked well the las timeS it occured)18:00
vilas/could/could you/18:01
vilapqm has been updated to bzr-1.6.1 (AFAIK) in the hope it will fix the problem. It doesn't apparently18:01
jamvila: what I want to know, is why does it always happen with *your* branches? :)18:02
vilaShooting in the dark again but: it looks like I'm the only one triggering this18:02
vilaMy only guess is that it happens with branches "freshly" pushed on lp18:02
jammaybe because you are using 'lp:' ? just a guess18:02
jamI always use my own18:03
jamstill, it doesn't make a lot of sense18:03
vilathat too but that a bit short as a diagnosis :-/18:03
jamsince it isn't failing to *merge* it is failing to commit18:03
vilanot even failing18:03
vilathe commit succeeds even when the process is killed, something else should block...18:04
ignaswhat do I do with "bzr: ERROR: [Errno 17] File exists" ?18:07
james_wif you use lp: and PQM has a launchpad login then it will use ssh, presumably everyone else will submit with http?18:08
james_wignas: during what operation?18:08
ignasjames_w: bzr ci18:08
james_wignas: running again with -Derror will give some clue as to what is going on18:08
ignasjames_w: where do you want your traceback?18:09
james_wignas: my guess is https://bugs.launchpad.net/bzr/+bug/24251018:09
ubottuLaunchpad bug 242510 in bzr "Pack already exists when pushing/autopacking" [High,Fix committed]18:09
james_wah, no, wrong message I guess18:09
james_wignas: paste.ubuntu.com or anywhere similar is fine18:10
james_wnot pastebin.ca18:10
ignasjames_w: http://paste.ubuntu.com/50932/18:10
james_wwow, that's an odd one18:11
james_wI guess you're not running bzr.dev?18:11
ignasBazaar (bzr) 1.7.1rc118:12
ignasjames_w: i have a dev version18:13
ignasi can try using it18:13
ignaswhen i'll bzr pull it18:15
james_wit seems like one of opendir, readdir or closedir are returning "File exists"18:16
james_wThe man pages don't say that that will happen though18:16
james_wI'm stumped18:19
james_wignas: please file a bg18:19
ubottuLaunchpad bug 274875 in bzr "Unexpected File exists error when trying to commit" [Undecided,New]18:21
ignasbranched the branch locally18:30
ignasand tried committing the same changes18:30
ignasit failed with the same error18:30
abadger1999Anyone here use bzr commit --fixes ?18:32
ignasyep, i can't commit into any of the branches in that shared repository18:32
ignasand I really do not like it...18:32
ignasfrankly - it is preventing me from working :/18:32
abadger1999I'm wondering what the syntax is for marking a bug fixed in launchpad... --fixes 1234 OR --fixes lp:1234 OR ....18:32
ignasok, i can't do any bzr commits on my machine...18:33
ignasok, I can with bzr.dev18:34
ignashmm, i will recompile bzr.dev and see then18:37
ignasyep, still works18:37
james_wabadger1999: the latter18:38
abadger1999james_w: Excellent.  Thanks18:38
ignasso bzr.dev works, bzr 1.7.1rc1 packages from PPA - don't18:39
Peng_Augh, what big new thing landed in bzr.dev that's making pulling it so slow? :(18:44
barryhi folks, bzrtools is driving me crazy18:51
barryi have this in my sources.list: http://ppa.launchpad.net/bzr-beta-ppa/ubuntu hardy main18:51
barrybut bzrtools is always getting out of sync.  either it's too old, or if i branch lp:bzrtools, it's too new18:52
abadger1999barry: Switch to Fedora :-)18:52
barryhow am i supposed to keep these in sync?!18:52
barryabadger1999: yeah, not actually an option :)18:52
abadger1999barry: There was just a discussion about this on the bazaar mailing list.18:53
* abadger1999 looks for URL18:53
Peng_barry: My solution is to run from source. :|18:53
barryPeng_: i might have to do that :/18:54
abadger1999The devs uploading the ppas came up with a plan to "do better" about keeping them in sync.18:54
barryabadger1999: cool.  at least they're aware of the problem.  i need to figure out something to get my bzr shelve back now, but i'll install from src if i have to for the short term18:55
abadger1999barry: Here's where the thread starts: https://lists.ubuntu.com/archives/bazaar/2008q3/047810.html18:55
barryabadger1999: thanks18:56
abadger1999barry: No problem.  I think bzr should change it's release practices to make this better for everyone but... I'm only a distro packager and occassional bug fixer so I don't have much clout.18:57
barryabadger1999: i see that shelve is a candidate for pulling into the core.  that's the one that always kills me, so that would benice18:58
abadger1999barry: My problem as a packager is that we get into situations where one set of plugins only works with an older version of bzr.18:59
abadger1999Meanwhile other users want to have the newer bzr because someone they work with has upgraded their repository to an incompatible version.19:00
barryabadger1999: i don't envy packagers jobs at all! y'all do a great job with a tough problem19:00
abadger1999barry: Were you at PyCon and attended the BoF on packaging?19:01
barryi was!19:01
barryabadger1999: you too?  /me looks at abadger1999's info19:02
abadger1999barry: Yep. I'm toshio, the skinny Fedora guy :-)19:02
barrynice to see you here19:02
abadger1999likewise :-)19:03
barryabadger1999: i see a lot of traffic on the distutils-sig.  i have no time to keep up with it, but how do you think it's going w.r.t. distro needs?19:03
abadger1999barry: I'm sad to say I haven't been able to keep up with it either.19:03
abadger1999barry: when I take a look at the code, it doesn't look like there's much going on.19:04
* barry perfects his clonebot19:04
abadger1999But there might be discussion that just hasn't been implemented yet.19:04
barryabadger1999: lots of grand ideas19:04
barryat least they're getting phillip involved.  sometimes guilt is the best motivating factor in floss (it's worked on me *many* times :)19:06
abadger1999Yeah.  That is good.19:06
abadger1999I've been migrating some build scripts over to paver recently.  That seems to fit the distro packagers needs a lot better than vanilla setuptools19:06
barryi'm not familiar with paver19:07
abadger1999It's something like a make/setuptools cross.19:07
barryneat: kevin dangoor19:08
abadger1999It imports distutils (and setuptools if available) so you can have those commands if you want them.19:08
* barry bookmarks19:08
abadger1999But it allows you to define custom tasks easily.19:08
barrysort of like a cleaner scons?19:08
abadger1999And add more declarative information.19:08
abadger1999I haven't actually used scons.19:09
barryi built a huge system with scons in my previous job.  nicely modular, but the hard things were *really* hard19:09
jambarry: I just synced bzrtools into bzr-ppa19:09
jamMak esure you have both19:09
jamI'm going to try and keep them in sync more19:10
barryjam: cool, thanks! i think the thing was i was using bzr-beta-ppa19:10
jambarry: it doesn't usually have "beta" releases, and it always wants tobe in lock-step...19:10
barrywhich didn't have bzrtools19:10
jamyou can probably use both19:10
abadger1999hmm... Yeah.  paver aims to make things always easy.19:10
NfNitLoopso Ubuntu is trying to upgrade bzr and bzr-svn, but is complaining that they can't be authenticated?   Anyone know what might be up w/ that?19:10
barryjam: awesome, thanks19:10
barryabadger1999: i'm really looking for something better for mm3 development, than just setup.py develop19:11
NfNitLoopit also looks like the "upgrade" verison is the same as the one that's installed, but I'll ask about that in #ubuntu. :p19:11
barryabadger1999: but virtualenv just doesn't DTRT for me19:11
barryabadger1999: thanks for the paver link19:11
abadger1999barry: Cool.  Keep in touch because I'm very interested in this too.19:13
barryabadger1999: definitely!19:13
barrygotta run.  thanks everyone!19:14
=== bac is now known as bac_dog_walk
vilajam: No LOSA around ? :-/20:04
jamnobody has responded20:04
vilajam: thks20:05
jamit is friday night after all20:05
* vila remembers his first *day* as intern: 'del library member', damn that's long, hey tutor, why so long ? EEEEEEEEERK Of course you have backup tutor ? And why the 'del' command doesn't check its arguments before running ?20:08
herb.win 1120:08
vilapfff, dos was just a child in those days :) No the system name was Pick or something and the script language 'English', it was supposed to be natural (like real people the script was ignoring what it didn't understand :-D )20:10
=== bac_dog_walk is now known as bac
vilaWell, I did my best to summon fullermd, but that should really be friday night :)20:18
=== bac is now known as bac_walk
=== bac_walk is now known as bac
jamvila: well, mthaddon was nice enough to restart it21:06
vilayeah for mthaddon !21:07
vilayeah for jam !21:07
jamvila: you may need to resubmit your patch21:07
jamor *not* for now :)21:07
vilahehe, yeah, I'll left pqm alone for the week-end ;-)21:08
guilhembijam: hi! please, what's the status of "put merge_lca_multi into bzr.dev" ?21:09
jamguilhembi: 1.7.1rc1 is out and in ~bzr-beta-ppa21:09
jamI need to merge it back, though the pqm was wedged for a bit21:09
guilhembijam: uh, merge it back... to where?21:10
jamguilhembi: it is in the 1.7 branch, I need to merge that into bzr.dev21:10
guilhembijam: 1.7.1rc1 is out? where (bazaar-vcs.org only mentions 1.7) ?21:11
jamit is available at https://launchpad.net/bzr/1.7/1.7.1rc1 I just need to update the other pages21:11
=== jam changed the topic of #bzr to: Bazaar version control system | http://bazaar-vcs.org | bzr-1.7 now available! please test bzr-1.7.1rc1 | http://irclogs.ubuntu.com/ | http://planet.bazaar-vcs.org/
abadger1999Any people here who use looms?21:28
abadger1999I'm wondering if they solve my problem or not.21:28
abadger1999I have a sequence of patches. and I want to be able to get them in two forms:21:29
abadger19991) Independent patches against the base revision.  These would be suitable for sending to upstream if I have no idea of the order that upstream is going to take the patches in.21:29
abadger19992) A sequence of patches against revision.  These patches would be suitable for applying when creating a distribution package.21:30
abadger1999I know how to do #2 using separate branches.21:30
abadger1999I'm not sure how to do either one using looms.21:30
james_wabadger1999: looms naturally satisfies number 221:31
abadger1999james_w: Excellent.  How do I convert the threads into the patches I need?21:32
abadger1999Is it a semi-manual process?21:32
james_wabadger1999: export-loom I think is the command21:33
abadger1999james_w: hmm... Okay. That gets me from loom to branches.21:35
james_wmaybe the command you want doesn't exist yet then21:36
james_wI would like the same command as you, so I'll write it one day :-)21:36
abadger1999Ah.  Okay for #2 this will work:21:39
abadger1999bzr diff -r thread:lp:trac-bzr..thread:no-repo21:39
abadger1999bzr diff -r thread:no-repo..thread:get-ancestry21:39
abadger1999Generates two patches with the changes stacked on top of each other.21:39
abadger1999I foresee #1 being harder to achieve.21:39
james_wis there another revisionspec provided?21:39
james_wbelow: or something21:40
james_w-r below:thread:no-repo..thread:no-repo or something21:40
abadger1999Hmm... It's not in the documentation21:40
james_weasier to code21:40
james_wah, maybe it's just one of those imagined features21:40
abadger1999Yep.  Looks like a not yet implemented21:41
abadger1999Ah.. thread:21:42
abadger1999nothing after thread: selects the thread below the current one.21:42
james_whmm, doesn't help getting the thread below the one below easily though21:43
abadger1999heh... down-thread functions as a 'set-thread' command if a thread name is given21:46
abadger1999but up-thread does not.21:46
abadger1999So.. alternate commands would be bzr down-thread lp:trac-bzr ; bzr up-thread ; bzr diff -r thread: ; bzr up-thread ; bzr diff -r thread:21:49
=== cody-somerville_ is now known as cody-somerville
Odd_BlokeAny thoughts on what might be causing http://rafb.net/p/AhoLJv69.html?22:37
Odd_BlokeHmm, http://mail.python.org/pipermail/distutils-sig/2007-May/007600.html may contain the answer.22:39
abadger1999Hmmm... anyone tried running loggerhead via mod_wsgi?23:09
MapManhey guys, you know what's causing the RMB menu to disappear for no reason? Im talking about win32 bzr23:11
Odd_BlokeMapMan: Do you mean TortoiseBZR?23:12
Odd_BlokeMapMan: markh is your guy for that.23:12
Odd_BlokeHe's probably not around, as it's the weekend.23:12
Odd_BlokeI'm afraid I have no idea how to diagnose a TBZR problem. :(23:12
MapMantoo bad23:13
MapManit happens from time to time to me and friends23:13
MapManand adding files manually takes more time... Especially explaining friends on how to do that.23:13
MapManmanually = from command line23:14
markhMapMan: please check .bzr.log - you might find a traceback there.  It might say something about "would recurse to death" which is a problem I'm aware of but can't repro23:28
MapManyou're right markh, I got that in my log23:29
markhcool - at least we don't have a *new* problem ;)23:30
MapManand it happens pretty often23:30
MapManmaybe I need new py win32?23:30
MapManor smt23:30
markhno - its a bug in tbzr23:32
markhits something to do with the order things are requested.  I've seen it myself, but can't for the life of me make the test suite hit it23:32
markhits frustrating, and its a priority now 1.7 is (almost) out23:33
MapManyeah, I realize it might be frustrating23:34
MapMangood luck on fixing it man23:34
MapMandoing good job on tbzr23:34

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