/srv/irclogs.ubuntu.com/2009/05/11/#bzr.txt

igcmorning all00:09
igcmoening lifless, mwhudson00:09
igclet's try that again ...00:10
mwhudsonhi igc00:10
igcmorning lifeless, mwhudson00:10
mwhudson:)00:10
jmllifeless: why doesn't aws-status read my access key from the same file as ec2test?00:21
jmli.e. ~/.ec2/aws_id00:22
lifelessit uses the same variables as bzr ec2test00:23
lifelessand if it doesn't find it it will look in gnome-keyring too00:23
lifelessyou could file a bug to have it look at a file as well; AFAIK the amazon toolchain just looks for environment variables, which is why I copied that00:24
jmllifeless: ok.00:24
jmllifeless: the real answer might be "Why does Launchpad's ec2test use a non-standard file"00:24
* jml makes a note00:24
lifelessof course, if the amazon toolchain does read a file, a bug on txaws is definitely in order00:26
jmllifeless: yeah. I'll chase it up later.00:27
lifelessthanks00:28
AfC1lifeless: Robert, you're signing emails with a key that's not on the public keyservers. You might want to upload it somewhere.00:36
=== AfC1 is now known as AfC
lifelessAfC: odd, I have. it just hasn't propogated ><00:37
AfClifeless: It's not on subkeys.pgp.net or pgp.mit.edu00:37
AfClifeless: I would have thought you would have uploaded to them directly, seeing as how they're the main ones00:38
* igc working on branch-specific rules today00:40
lifelessigc: you were going to mail about the issue; have I missed that ?00:41
igclifeless: nope - sending it today00:41
pooliegood morning00:54
=== _thumper_ is now known as thumper
thumperhow worried should I be about 2485 revisions missing parents in ancestry and 3547 inconsistent parents?00:57
lifelessthumper: it will be affecting the output of annotate00:57
lifelessthe 2485 are the unimported arch revisions00:58
thumper2645 ghost revisions00:58
lifelessoh hmm00:58
igcmorning poolie00:58
lifelessthen its filled in ghosts00:58
bob2would it be sensible to have 'bzr bind' with no args pick one of the configured urls (maybe in order: parent, push, merge)?00:58
lifelessyou should reconcile anyhow00:58
pooliehelol igc00:58
lifelessbob2: confusing00:58
pooliewill comment on your docs soon00:58
lifelessbob2: as it already has a saved bound location00:59
thumperlifeless: what will reconcile do?00:59
pooliebob2: if it guaranteed to rebind just where it was last bound00:59
pooliewhat he said00:59
lifelessit will rewrite the parents00:59
thumperto what?00:59
lifelessto the correct value based on the data available in the repository00:59
bob2lifeless: hm, I meant, only if it didn't have a previously saved one01:00
lifelessbob2: still confusing, no01:00
bob2ok01:00
lifelessbob2: as in01:00
lifelessbind (grabs parent)01:00
lifelesspull x (sets parent in master and local)01:00
lifelessunbind01:00
lifelessbind01:00
lifeless(does not grab parent)01:00
bignosewith Loggerhead, browsing a file gives me the “annotate” view01:14
thumperwhat's the status of bzr-hg?01:14
bignosehow can I just view the content of the file from head, without annotation?01:14
bignosei.e. the URL formed has …/trunk/annotate/head%3A/README01:15
bignosewhat URL should I use instead to just display the raw content of that revision of the file?01:15
lifelessmwhudson: ^01:16
mwhudsonbignose: there is no view to display the raw content01:16
bignose:-(01:16
mwhudsonbignose: because we're worried about xss attacks01:17
mwhudsonbignose: there is a branch which adds it somewhere, but we need a way to turn it off01:17
mwhudsonbignose: https://code.edge.launchpad.net/~intellectronica/loggerhead/view-file is one01:18
bignosemwhudson: thanks for the response.01:19
lifelessmwhudson: 'if hacked(): disable_it_now()' ?01:19
mwhudsonbignose: np01:19
mwhudsonlifeless: yeah01:19
lifelessit would be nice to be able to get at plain text versions01:20
lifelessits a pity that browser authors are insane01:20
bignosemwhudson: actually on second thought: what XSS vulnerability?01:20
lifeless[content sniffing]01:20
lifelessbignose: I could upload arbitrary html to my branch01:20
bignoseshouldn't it be just a matter of serving the file as ‘Content-Type: text/plain’?01:20
mwhudsonha, ha, yes, it should01:21
lifelessbignose: many browsers sniff content and ignore content-type01:21
lifelessbignose: and there is now a 'standard' under discussion for controlling when the do this. Its insane01:21
bob2haha01:21
bob2is it enabled via a meta tag?01:21
bignoselifeless: those broswers deserve to get pwned then :-)01:22
bignosehmm, though I guess in that case it's the site getting pwned.01:22
lifelessits batshit insane01:22
lifelessand es01:22
lifeless*yes*01:22
lifelesshttp://www.nabble.com/NEW-ISSUE:-content-sniffing-td22795699.html01:22
lifelessI should raise this on the wg01:23
bignoseyes, please. that's intentional brokenness01:23
bignoseit's like Reply-To field munging, except with hideous security vulnerability01:23
lifelesshttp://tools.ietf.org/html/draft-abarth-mime-sniff-00 is the spec01:23
lifelessmwhudson: in theory if you avoid all the holes in that, it would be safe to present it as application/octet-stream. Note that I haven't read the algorithm in sufficient detail to comment.01:26
lifelessI just followed the surface discussions01:26
mwhudsonlifeless: that would be nice01:26
bignoseeugh. ‘text/plain’ would be better01:26
lifelessbignose: what would be? (no quotes please)01:27
bignosecontent which can't display well as ‘text/plain’ should be downloaded anyway IMAO01:27
mwhudsonbut the fact remains that it's going to require a lot more effort to get right than it should01:27
bignoselifeless: fix yer UTF-8 man :-)01:27
bignoselifeless: text/plain01:27
lifelessbignose: I want to; its somewhere down in xlib01:27
lifelessbignose: we don't know what the type is as bzr doesn't encode mime types in its store01:28
bignose(specifically in the context of showing content of a file under VCS)01:28
lifelessbignose: so text/plain would be a guess, and work badly with showing a jpg, for instance01:28
bignoselifeless: yes, that's why I'm saying the common denominator should be text/plain01:28
lifelessits also likely that text/plain is one of the ones browsers sniff-up to html01:28
bignoseright, and application/octet-stream would be *just as bad* for non-text content01:29
bignoselifeless: this was in direct response to you saying if-the-sniffing-problems-are-resolved01:29
lifelessbignose: oh; so they won't be. Browsers are out there (including FF as far as I know)01:30
lifelessthe only way to resolve it is to implement http/2.0 and have a very large blacklist hammer for any nonconformant browsers that appear01:30
* bignose deprecates stupid people.01:31
lifelesspragmatically thats not happening, so we have to a) convince authors not to be idiots from here on out, and b) work within the limits of whats out there01:31
lifeless'resist the temptation to guess' isn't something that ie or mozilla had heard, I guess.01:31
mwhudsonlifeless: i think the correct response to the issue in http://tools.ietf.org/html/draft-abarth-mime-sniff-00 involves a time machine and a very large bat01:38
eferraiuoloI was wondering if it's built in or if you need the bzr-git plugin to run: bzr branch git:// commands?01:39
mwhudsoneferraiuolo: you need the git plugin01:40
eferraiuolomwhudson: cool, well I'm about to branch it then :-)01:41
Peng_eferraiuolo: bzr-git depends on dulwich as well.02:17
lifelesspoolie: I think a script is better than trying to get all devs to change their bug filing behaviour :)02:32
poolieit seems to me the importance needs to come from a human02:33
pooliei don't see how a script can generate it02:33
poolieit could make them all default to wishlist i guess02:33
pooliethat might force people to dtrt02:33
lifelessmedium seems fine to me02:33
lifelessanyhow, my previous comment was 'when I've thought about I do', which seems valid to me02:34
* igc lunch02:35
poolieBB seems to be down..02:39
lifelessmondayitis02:39
poolienot a good day for servers apparaently02:40
jelmer_mwhudson: main improvement is that dpush to remote git repositories works now03:03
jelmer_mwhudson: and pull from remote git repositories only does one smart protocol command now03:04
=== mlh_ is now known as mlh
mwhudsonjelmer_: so nothing very interesting from a launchpad pov03:20
jelmer_mwhudson: no, not really03:21
mwhudsoncool, less work for me :)03:21
mwhudsonjelmer_: i set up a samba import on staging :)03:23
jelmer_mwhudson: :-)03:27
jelmer_mwhudson: are there other git branches there yet that I can look at?03:27
mwhudsonwell, some on staging03:27
jelmer_which ones?03:28
mwhudsonbut staging has just gone *bang*03:28
mwhudsonjelmer_: etckeeper, gedit, banshee03:28
=== timchen119 is now known as nasloc__
jelmer_re03:55
jelmer_thumper: it can view history but that's it, no fetch03:56
lifelessjelmer_: are you going to do some stuff to it?03:56
jelmer_lifeless: Don't have anything planned atm, would be interested in doing so03:57
thumperjelmer: what?03:58
jelmer_thumper: bzr-hg03:58
thumperjelmer: ah03:58
thumperjelmer: how big a repo can bzr-git handle right now?03:59
jelmer_thumper: I've imported samba on my desktop machine03:59
thumperjelmer_: how big is that?03:59
thumperin the big picture of things04:00
thumpersay compared to the kernel04:00
thumperor evolution04:00
jelmer_thumper: IIRC it's ~70k revisions, about ~3k files in the tree on average04:01
jelmer_I'm not sure what the numbers are for the kernel04:01
jelmer_evolution is smaller than samba, at least04:01
lifelessless commits more files for the kernel, IIRC04:02
jelmer_thumper: the #1 bottleneck is the inventory handling in bzr04:02
lifelessjelmer_: in dev6 still?04:03
wgrantDoes CHK fix that?04:03
jelmer_lifeless: dev6 is significantly better, but afaik the lp imports are still using 1.904:04
jelmer_lifeless: with dev6 inventory handling accounts for 20% of the CPU time during git imports04:04
lifelessjelmer_: thats good; should be lower though04:04
jmlwhere is the mainline commit message policy for bzr documented?05:26
jmlI didn't realize that NEWS conflicts can never auto-resolve.05:33
igclifeless, poolie, jam: status update & proposed direction for branch-specific rules sent to the list now05:46
igcjelmer_: ^^^05:50
pooliehi igc05:52
poolieigc re bug 345693 being closed05:53
ubottuLaunchpad bug 345693 in bzr-usertest "should test "bzr ls -r -1"" [Undecided,Fix released] https://launchpad.net/bugs/34569305:53
pooliedoes that mean we should cross "Check performance of full inventory extraction" off the brisbane-core list?05:53
* igc looks06:05
poolieok so i see that means we now have a usertest for it06:06
poolieand iirc it didn't turn out to be too slow?06:06
igcpoolie: I think it was slower but it's not a major deal for ls06:06
poolieok06:07
igcit may be for other commands though06:07
poolieso, not too many of them should be using it06:07
pooliei'll cross it off for now06:07
igcpoolie: ok. I'll rerun the benchmark soon as well to see where it's at06:07
igcpoolie: on another topic, abentley has appointed you as the reviewer for his compositetree patch06:08
igcpoolie: that makes you the bottleneck :-)06:08
igcpoolie: he wants you to say wwhether the design doc is now sufficient or not to proceed06:08
poolie:)06:08
poolieok06:08
lifelesspopping up to the chemist, back soon06:10
=== abentley1 is now known as abentley
lifelessjelmer_: oh, I know why it was slow for you to push cross-format06:56
lifelessjelmer_: it's john's changes to IDS06:56
lifelesspoolie: 374726 for vila07:01
lifelesspoolie: I suspect thats more than a day to have a good answer on07:02
lifelesspoolie: so I'll look for other things tomorrow07:02
=== TheMuso_ is now known as TheMuso
pooliebug 37472607:16
vilahi all07:16
ubottuLaunchpad bug 374726 in bzr "annotate performance on development-rich--root" [High,Triaged] https://launchpad.net/bugs/37472607:16
pooliehello vila07:16
vilahmm thanks for the gift lifeless :)07:17
lifelessvila: anytime07:18
lifelessvila: I know you've looked at annotate recently :)07:19
vilalifeless: yup07:19
vilaand from what I recall before paging in I can't see why it could become slower... I'll see07:20
lifelesswell, if you bench a few juicy files from bzr and emacs and its fine, then we'll know :)07:21
vila...and mysql :)07:21
lifelessindeed07:22
lifelessI built drizzle on the weekend07:22
lifeless... and found [and fixed some] bugs :)07:22
vilasheesh, wrong button07:23
lifelesshaha07:23
lifelesspoolie: I've done as much wiki gardening as I think is useful for a few days07:24
lifelessback to check for a bit then signoff07:24
* vila teach himself: heron is the background means no menu bar at the top of the screen07:25
igchi vila07:34
vilahi Ian07:34
vilaBB is down07:39
* lifeless halt()s08:14
Peng_lifeless: Good night. :)08:14
poolievila: can you try using lp reviews for some things?08:19
poolieyou may get less outages08:19
vilapoolie: sure, old habits... but in that case it's a bzr-gtk critical bug that got affected to bzr instead08:20
poolieoh ok08:22
pooliei just meant in general08:22
vilapoolie: sure, my last submission(s?) to BB were followed by a 'damn it, use lp reviews ! You already pushed your branch ! You just have to use lp-open instead of bzr send !!!' :)08:31
vilaspiv: I noticed that you have added some 'if token is not None: xxx.leave_lock_in_place()' at the *end* of one (may be two so far) tests,08:33
vilaspiv: Am I right thinking that you forgot to delete them after having written more focused tests ?08:33
spivvila: hmm, which tests?08:41
vilaspiv: bzrlib/tests/per_repository/test_write_group.py test_abort_write_group_does_not_raise_when_suppressed08:42
vilaspiv: bzrlib/tests/test_pack_repository.py test_abort_write_group_does_not_raise_when_suppressed and test_abort_write_group_does_raise_when_not_suppressed08:43
spivvila: those two lines are there to suppress "object was locked when gc'd" warnings when possible08:45
vilaspiv: haaa, so if I get rid of the warning you din't mind me deleting them then ?08:46
spivvila: I suppose we could also achieve that by renaming foo back to repo and doing an unlock.08:46
vilayup: self.addCleanup(t.rename, 'foo', 'repo')08:46
spivI don't mind you deleting them, but how are you going to get rid of the warning?08:46
spivOk.08:46
=== serg_ is now known as serg
* igc dinner09:15
vilalifeless: I know you're aware of the problem but I thought I'll share the fun anyway: Ran 1 test in 0.027s09:54
vilaFAILED (errors=2)09:54
vilaobserved with an error in a cleanup hook :)09:55
lifelessyes, its by design ugly though it is09:56
lifelessvila: feel free to fix; though I think its low priority - its cosmetic not functional10:34
vilalifeless: naah, just surprising, I think the fix could be a bit hard to get rigth though and not worth the effort right now (test errors should be fixed anyway)10:35
vilaand it's true that there was 2 errors...10:35
jelmer_mwhudson: what does lp run, dapper or hardy?12:01
jelmer_vila, lifeless: do you know perhaps?12:11
vilajelmer: I'd say dapper but since I'm not sure, you'd better check with a LOSA12:12
elmojelmer_: hardy12:12
vilaelmo: do you when it was upgraded ?12:13
vilayeah, know is missing of course :)12:13
elmovila: not offhand; over 6 months ago?  I can find out exactly, if you really need to know12:15
jelmer_elmo: thanks12:15
vilaelmo: thanks, that's precise enough :)12:15
vilaabentley: BB is down13:04
vilaabentley: but hi first, sorry :)13:04
abentleyvila: Restarted.13:05
abentleyvila: hi :-)13:05
vilaabentley: how strange... For http://bundlebuggy.aaronbentley.com/project/bzr-gtk/request/<m2tz3x6rw6.fsf%40free.fr>, I got an ack email  to bazaar@list.canonical.com, which was wrong since it's for bzr-gtk, yet, on BB, it's correctly affected to bzr-gtk...13:09
abentleyvila: Any reviewer can reassign a merge request to the correct project.13:10
vilabut as soon as I got the ack email I tried to do that, BB has been down since13:10
vilaand http://bundlebuggy.aaronbentley.com/project/bzr/request/%3Cm2tz3x6rw6.fsf%40free.fr%3E is also valid 8-)13:11
vilaBB is too magick :)13:11
vilajelmer: any change you can review the abvove ?13:45
jelmer_vila: sure, one sec14:10
cornucopicvila, Hello16:18
vilacornucopic: hi, how is your patch for #372800 going ?16:21
cornucopicvila, Just resumed looking at it. To make sure, that I am in sync with you on the bug, can you please take a look the bug report?16:22
cornucopicvila, the description: https://bugs.launchpad.net/bzr/+bug/37280016:23
ubottuUbuntu bug 372800 in bzr "Wrong behavior of SMTP authentication during post commit email" [Undecided,In progress]16:23
vilacornucopic: I,m pretty we are sync, how about you submit a patch so we can discuss on concrete code :)16:23
vilas/pretty/pretty sure/16:23
cornucopicvila, Hmm..Okay :) As you suggest.. !16:24
rbriggsatuiowaI tried to shelve a delete and the unshelve failed miserably16:28
rbriggsatuiowathe ticket here https://bugs.launchpad.net/bzr/+bug/319790 seems to indicate this is fixed in later versions - what version will work (ie: is this in a release or dev version?)16:29
ubottuUbuntu bug 319790 in bzr "bzr unshelve crashes losing all changes" [High,Fix released]16:29
vilarbriggsatuiowa: 1.13 should include it AFAICS16:32
vila_rbriggsatuiowa: 1.13 should include it AFAICS (just got a crash here, don't know if you got that)16:35
rbriggsatuiowaI'm building 1.14 right now and can't find a --prefix option for setup.py ...16:35
rbriggsatuiowaI was running 1.1016:35
vila_rbriggsatuiowa: you know you can run from source right ?16:36
=== vila_ is now known as vila
rbriggsatuiowaahh - thanks16:37
cornucopicvila, I can safely use a string function to extract the port number from smtp_server ?16:40
vilacornucopic: yes, use split()16:41
SamByou mean .split(':'), yes ?16:41
cornucopicSamB, vila, yes16:42
* SamB meant that question for vila ;-)16:42
rbriggsatuiowavila: 1.14 worked for me - thanks16:42
vilarbriggsatuiowa: always happy to help (TM)16:43
SamBrbriggsatuiowa: you maybe want --home ~16:43
SamBthat's what I use16:43
rbriggsatuiowayeah - that's what I found once I read the FAQ (:))16:43
SamBIt was used in some example in the Python documentation16:44
rbriggsatuiowaI'm too used to the --prefix configure option16:44
SamBhehe16:46
SamBI was pleased to see that git's build system defaults to installing in $HOME16:47
rbriggsatuiowaweird - I've always been a big fan of installing into /opt/app and fixing PATH when I do source installs16:48
rbriggsatuiowamakes it easy to hose old versions without hurting other apps - but a pain to maintain (have to set pythonpath as well)16:48
vilarbriggsatuiowa: old SunOS user maybe ? :-)16:54
vilarbriggsatuiowa: what os/version are you using right now ?16:54
rbriggsatuiowagentoo17:02
rbriggsatuiowathe bzr version is way out of date17:02
rbriggsatuiowa1.917:03
rbriggsatuiowaI started using /opt when running rocks clustering stuff at work17:04
vilarbriggsatuiowa: rocks clustering, I see :)17:05
rbriggsatuiowayeah - it's supposed to simplify clustering stuff - I found it a little binding17:05
rbriggsatuiowaI haven't used it in four years though, so it might be better17:06
=== r00t_ is now known as amit
amitvila, can you please take a look at http://pastebin.com/m6a72d8ad? Is this on the correct road?17:12
=== amit is now known as Guest98791
Guest98791vila, amit here..17:13
vilaGuest98791: please, send a proper submission to the list or do a merge proposal from launchpad, it's far easier and efficient to review code in context than in pastebin/IRC, thanks in advance :)17:14
Guest98791vila, Ok. cool. Thanks.17:16
=== Guest98791 is now known as cornucopic
cornucopicthe bzr-email plugin replaces the bzr installation's 'smtp_connection.py' ?17:36
cornucopicapparently, it uses its own copy of smtp_connection17:42
cornucopicand not the globally installed one17:43
jelmer_jam: hi18:22
jelmer_jam: when you talk about chk stacking you mean chk stacked on chk right?18:22
jamjelmer_: yes18:22
jamI think I have it all working18:23
jamI'm just doing testing18:23
jelmer_nice18:23
jamand uncovering stuff like: bug #37501918:23
ubottuLaunchpad bug 375019 in bzr "auto-stack logic selects wrong repo format" [Undecided,New] https://launchpad.net/bugs/37501918:23
jamhey vila... you know, we really should start chatting more often18:26
jamI got out of the habit with multiple conferences, and getting sick, but I'd like to catch up sometime18:27
jelmer_jam: whoops18:30
jelmer_jam: what about chk stacking on 1.9 and vice versa?18:31
jelmer_jam: 1.9-rr on chk I mean18:31
jamjelmer_: ATM we can't stack across serialization formats18:31
jamso no stacking 1.9-rr <=> dev618:32
jamor svn <=> bzr anything18:32
jametc18:32
jelmer_ah, ok18:32
jelmer_jam: svn <=> bzr has worked for quite a while :-)18:32
jamjelmer_: how did you manage that?18:32
jelmer_jam: bzr-svn provides fake VersionedFiles implementations18:32
jamGiven that I get:18:33
jambzr: ERROR: CHKInventoryRepository('file:///C:/Users/jameinel/dev/%2Ctmp/d6rr/.bzr/repository/')18:33
jamis not compatible with18:33
jamKnitPackRepository('file:///C:/Users/jameinel/dev/%2Ctmp/d6rr-b-stacked/.bzr/repository/')18:33
jamdifferent serializers18:33
jelmer_that call Repository.get_revision() under the hood18:33
=== beuno_ is now known as beuno
jelmer_and serialize again using the serialization format that 1.9-rich-root uses18:33
jamjelmer_: so it would fail for dev6, because you are explicitly casting to 1.9-rr ?18:33
jelmer_jam: yeah18:34
jam(also, you can stack 0.92 => 1.9 because the serializer didn't change)18:34
jelmer_jam: ok, so I guess we'll need something more generic at some point anyway18:39
vilajam: definitely, I was hoping to call you today but... so many things to do :)19:01
jamvila: not a big deal. I just saw your email, and realized we haven't talked in a while. Maybe tomorrow.19:03
vilajam: sure19:04
Peng_Space Shuttle! :D19:10
Takcouldn't see very well from here19:17
Peng_I couldn't see it at all. It was cloudy, and the trajectory may have interfered.19:21
beunojam, w0000000t!20:09
* beuno dances20:09
LarstiQbeuno: you received some lettuce in the mail? :)20:10
beunojam, EVEN BETTER!20:10
beunoa patch for stacking on brisbane-core20:10
Kissakiyo, can you with bzr commit -m "" how can I add newlines?20:11
Kissakiaka line breaks20:12
beunoKissaki, I think you need to drop the -m, and jump into an editor20:12
LarstiQit can be done with -m20:13
Kissakihm, ok20:13
Kissakithx20:13
Kissakican=can't ? ^^20:13
LarstiQKissaki: what I do is bzr ci -m 'Added foo.<hit enter>Added bar.'20:13
LarstiQKissaki: ie, let my shell handle the newlines20:13
LarstiQKissaki: can20:14
Kissakitried \n, but that didn't work :/20:14
LarstiQKissaki: have you tried an actual literal enter?20:14
Kissakihm?20:14
LarstiQKissaki: use the enter key.20:14
Kissakipressing it will exec the cmd ofc20:15
Peng_Kissaki: Depending on your shell, if you're inside quote marks, it won't.20:15
Kissakiusing windows cmd right now20:15
LarstiQah. windows cmd20:15
LarstiQKissaki: I don't know if the windows shell has support for multiline editing20:16
LarstiQKissaki: I'd leave off -m and spawn a commit editor then.20:17
Kissakiwell, I'll try copy paste for comment next time20:17
Kissakicommit editor? is that something special?20:17
LarstiQI doubt tricks like bzr ci -m `cat` will work on windows?20:17
Kissakiyeah20:17
LarstiQKissaki: it looks at $VISUAL or $EDITOR, and will spawn notepad on windows if it can't find anything else20:18
LarstiQKissaki: also, you configure what editor to use for commit messages, see `bzr help configuration`20:18
sidneiis there an argument for reading the commit message from a file? in svn you can do svn ci -F <filename> or something20:18
LarstiQwhich might come in handy on windows20:18
LarstiQsidnei: oooh, good one!20:18
LarstiQthat was even my first patch for bzr, shame I don't remember :/20:18
LarstiQKissaki: as sidnei said, you can use -F20:18
luksKissaki: have you tried bzr qci20:19
Kissakino20:19
luksit might not be what you want, but just in case20:19
sidneiqci is cool too20:19
Kissakidon't even know what ci is20:19
lukscommit20:19
Kissakiah20:19
luks(and qcommit)20:19
Kissakiwhat's the difference?20:20
luksit opens a dialog window20:20
GaryvdMnothing - qcli is an alias20:20
lukswhere you can type the commit messages, select files, see diffs, etc.20:20
GaryvdMqcli is an alias for qcommit20:20
luks*message20:20
LarstiQGaryvdM: qcli or qci?20:20
GaryvdMerr qci20:21
Kissakioh, nice20:22
Peng_jam: You left a "bork" in bzrlib/repofmt/groupcompress_repo.py in the dev6 stacking patch. :P20:22
Kissakiqcommit indeed does open a commit window/dialog/editor thingy20:22
Kissakithx20:22
jamPeng nice catch :)20:35
jamthough that would hint that the code isn't exercised (as I thought it wasn't)20:35
Peng_:D20:37
LeoNerdUhh... Where'd 'bzr revert' move my file to?20:38
LeoNerdIt always used to keep a backup20:38
beunoLeoNerd, ~filename~20:39
LeoNerdI don't see one20:40
beunoLeoNerd, ls -la?20:40
LeoNerdIn the directory it used to live, or in the treeroot?20:40
LeoNerdWell. it's absent either way20:40
LarstiQLeoNerd: it doesn't leave backups if it can be constructed otherwise, afaik.20:40
LeoNerdHrm...20:41
LeoNerdit was locally modified20:41
=== awilcox_ is now known as awilcox
ekahi all22:04
ekais there any way to work using bzr with a git repo?22:05
mwhudsoneka: yes, 'bzr-git'22:05
ekamwhudson: it's stable?22:07
mwhudsoneka: it's moving quite quickly, but mostly in a positive direction :)22:08
mwhudsoneka: it works pretty well, in my testing22:08
ekamwhudson: thanks for the tip22:09
mwhudson(launchpad will be using it to import git repositories into bzr soon)22:09
jamlifeless: ping22:10
jelmermwhudson: so, bzr-git now supports using tdb to store its cache data22:24
jelmermwhudson: which is significantly faster than sqlite22:24
adamfastI've got a question - a while back I upgraded via the installer to 1.13.2 (and then today to 1.14.1) but I keep getting a "bzr: WARNING: bzrlib version doesn't match the bzr program." the bzrlib version is 1, 14, 1, 'final' and bzr --version tells me it's 1.14.1. Has anyone seen this before?22:28
adamfast(I should mention I'm using a Mac with the Leopard Python 2.5)22:28
thumperadamfast: my guess is that the bzr executable isn't the one you installed22:29
adamfastany idea what the/a possible fix could be? Try to delete all the files and run the installer again?22:30
mwhudsonjelmer: tdb?22:30
mwhudsonjelmer: is it packaged for hardy?22:31
jelmermwhudson: yep22:31
thumperjelmer: is it chosen automagically?22:31
mwhudsonjelmer: hmm, where is the cache stored between runs?22:31
jelmerthumper: yep, we also still support sqlite22:31
jelmerthumper: and if tdb is not there sqlite is used like it was before, it'll just be slower22:32
jelmerthumper: (slower than tdb, not slower than it is with sqlite now obviously)22:32
jelmermwhudson: it's in .bzr/repository/git.[t]db22:32
mwhudsonjelmer: does push preserve it?22:33
Peng_Can you upgrade a repo from sqlite to tdb?22:33
jelmermwhudson: no, but if it's not there bzr-git will regenerate it22:33
mwhudsonjelmer: how bad is that, relatively speaking?22:34
mwhudson(because it seems with the system we have in place we'll regenerate it each time)22:34
jelmermwhudson: one sec, I'll try on a bzr.dev repo22:34
thumperlifeless: you up yet?22:35
jelmermwhudson: I guess it would be nice if push could preserve it I guess but we'd need better hooks for that22:37
jelmermwhudson: also, if you don't keep this database around you'll hit problems when there are revisions that contain characters that can't be represented in XML22:37
mwhudsonjelmer: well, it would be easy enough to preserve it by hand, esp if bzr-git can tell me where it should go for a branch22:38
thumperjelmer, mwhudson: well that is a handy thing to know22:38
mwhudsonthumper: indeed22:38
Peng_Why's lp:dulwich a remote branch?22:40
jelmermwhudson: regenerating the sha map takes 16 seconds for 1000 revisions (bzr-git)22:40
jelmermwhudson: try 'bzr git-object' in any bzr branch to generate a full map22:41
mwhudsonjelmer: will it need to do that for a pull where the remote tip hasn't changed?22:41
jelmermwhudson: I'm not entirely sure22:42
jelmermwhudson: it shouldn't need to, but I don't know what it does atm22:42
jelmermwhudson: only one way to find out :-)22:42
mwhudsonjelmer: :)22:43
lifelessthumper: yes22:43
lifelessthumper: but I'm doing bio stuff22:43
thumperlifeless: I've just done mine :)22:44
thumperlifeless: why does pack take so long with bbc?22:48
thumperpacking launchpad with packs took under 3m22:48
thumperpacking launchpad in bbc took over 3 hours22:48
thumperalthough packing packs went from 1.1G to 1.1G (not much change :)22:49
thumperpacking bbc went from 248M to 137M22:49
thumperfor the pack dir at least22:50
lifelessfor xml based formats all pack does is reduce latency22:50
lifelessfor the chk formats, we recompress22:50
thumperlifeless: is this going to happen automatically when combining packs?22:50
thumperlifeless: because if it does, it will make for very slow pushes :)22:50
lifelessthumper: 'bzr pack' recombines all history. of course its slow22:51
mwhudsonjelmer: it seems maybe not22:51
thumperlifeless: but what about the autopack?22:51
lifelessautopack doesn't do a full pack22:51
thumperso it will still be fast?22:52
lifelessyes22:52
lifelesskindof an obvious question :)22:52
thumpercool22:52
jelmerlifeless: is it right that running 'bzr pack' in a dev6 repo multiple times gives "Pack already exists ..." after the first time ?22:52
thumperjust making sure :)22:53
lifelessjelmer: file a bug please22:53
lifelessjelmer: its because we don't short-circuit pack and avoid doing it in dev622:53
jelmerlifeless:  I guess that's a "no"22:53
lifelessjelmer: its not the desired behaviour :)22:54
lifelessthumper: autopack has a exponential backoff on frequency for a given text22:55
=== phinze_ is now known as phinze
lifelessthumper: 10 autopacks of 10 revs in the first 99 commits, then one of 100 revs, and so on22:55
lifelessif you've got 100K commits, it will be a very long time before autopack decides to rewrite the 100K pack when you push a single revision22:56
thumperlifeless: just saying "yes it'll be fast" is good enough for me22:56
lifelessthumper: sure, but you may as well understand it too ;)22:57
beunolifeless, https://pastebin.canonical.com/17459/    bug?22:57
thumperlifeless: however your explination doesn't help me understand because I'm missing too much context :)22:57
lifelessthumper: ok. In short - autopack may do a full pack, but its very rare, and becomes more rare thelarger the repo22:58
lifelessthumper: theres a heuristic, which seems to work well.22:58
lifelessbeuno: bug22:59
beunolifeless, danke. What does --default-rich-root default to in bzr.dev?   0.92 still?22:59
lifelessI'm not sure. that was on branch anyhow23:00
jelmerbeuno: rich-root-pack23:00
beunoah, lh is 1.923:00
beunoso I guess it's trying to do 1.9 -> rich-root-pack23:01
beunoso failing23:01
lifelessbeuno: its the branch object thats failing23:01
lifelessnothing to do with roots23:01
beunooh23:01
beunok, bug files23:03
beunoand filed23:03
jelmerheh, dpush from svn into git works (-:23:04
jelmersecretly bzr is just tailor Done Right [tm] ;-)23:05
lifelessjelmer: lol; scary, and 'No'23:06
beunonice. Loggerhead in bbc is ~40% smaller, and "bzr log -v" takes less than half the time23:11
beuno(compared to 1.9)23:12
luksbeuno: out of curiosity, how long is that? :)23:14
luksI'd expect that to still be unusable23:14
beunoluks, 3.7sec to 1.6sec23:15
lifelessbeuno: be sure to bzr check ;; bzr reconcile before migrating23:15
beunopretty usable23:15
lukswhat? log -v does still all the deltas?23:15
lifelessbeuno: I encourage you to migrate to rich roots soon; see the thread on bzrtools which has migrated to rich roots already23:15
beunolifeless, I will, although I'm just fooling around now, to try and hash out any obvious problems23:15
beunolifeless, I'm more than happy to, if we can get mwhudson and Peng_ on board23:16
jamlifeless: I have to go now, but if I get some time, I'd like to chat after a few hours23:16
lifelessbeuno: thats part of the process; read my mails ;)23:16
lifelessjam: sure23:16
lifelessjam: ping me23:16
lifelessjam: I'm going to be poking at check, then presentations23:16
mwhudsonbeuno: sure, no problems at all with going to rich root23:17
beunolifeless, both check and reconcile?23:17
lifelessbeuno: yes, or just reconcile23:17
beunomwhudson, what happens with the existing stacked branches?23:17
Peng_beuno: My position on rich-roots hasn't changed. I'm on board, pending that email from a few weeks ago about changing how converting worked.23:17
beunothey all break?23:17
lifelessbeuno: with a check afterwards23:17
mwhudsonbeuno: well that's the fun part :)23:17
Peng_Or whatever it was about.23:17
mwhudsonbeuno: i'm sure lifeless talks about that too in his mails23:17
lifelessbeuno: 1) read my mails about this; 2) reply with anything unclear so we can capture it and improve - please23:18
beunoPeng_, mwhudson, ok, I may attempt to upgrade trunk later today then23:18
beunocheck and reconcile looked ok on lh bbc23:18
lifelessbeuno: read the mail first; doing it today would pretty much break all the rules23:19
beunoeven when going from plain 1.9 -> bbc23:19
beunook, *today* I may read lifeless's email more carefully23:19
beunoand see where that takes me23:19
lifelessPeng_: noone has altering the conversion process in their queue that I know of23:19
beunolifeless, any hint on how to find that email?23:22
lifelessSubject: [DRAFT][RFC] Migrating to rich roots23:23
beunologgerhead is very spify on bbc: http://bazaar.launchpad.net/~beuno/%2Bjunk/loggerhead-bbc/changes23:23
lifelessspify?23:23
lifelessdo you mean fast or pretty?23:24
beunofast23:24
lifeless3 seconds to toggle a >23:24
lifeless:<23:24
beunonot sure what that means23:25
lifelessin the changes pge23:25
lifelessthere are > beside each rev23:25
lifelessif I click one, its about 3 seconds, sometimes up to 5, before the expanded content is complete23:25
beunoI clicked on expand all23:25
beunoand it took ~2-3 seconds to bring all of them in23:26
Peng_lifeless: I dunno. There was some email about somehting or other. I still don't know what it was about. :P23:27
lifelessbeuno: 10 seconds to do that for me23:28
lifelessbeuno: where are you at the moment23:28
lifelessPeng_: I do23:28
beunolifeless, argentina23:28
lifelessstrange :-)23:28
beunolifeless, so upgrading to rich-roots breaks stacked branches. Can they be upgraded as well, or are they just discarded?23:28
Peng_Whoever did it first had to wait for the cache to be generated.23:28
lifelessPeng_: I did it second23:28
lifelessbeuno: clean your eyes23:29
lifeless3) Users migrate their own branches before this time, including lp23:29
lifelesshosted branches and particularly stacked branches.23:29
beunolifeless, I don't follow23:29
lifelessPeng_: its possible its slower now its cached23:29
beunocurrent branches stacked can be upgraded to rich-root, even though the stacked-on branch isn't rich-root?23:30
Peng_Stupid question that I can figure out on my own: is it possible to push to a lightweight checkout on a remote server, where the branch is stored on the same server?23:30
Peng_s/can/should/23:30
lifelessbeuno: yes, they will break after the upgrade; then when the stacked on is a matching format again, they will work again23:30
beunolifeless, gotcha23:30
lifelessPeng_: it should be yes, unless the the server is chrooted so as to divide them23:31
lifelessPeng_: but it may not work dependign on the path in iuse in the checkout23:31
Peng_lifeless: In this case, no chroot, but they're totally different paths.23:31
Peng_Maybe I should use a stacked branch instead.23:32
lifelessPeng_: there's always a chroot23:32
lifelessPeng_: ChrootTransportDecorator23:32
Peng_Eh.23:32
beunoit pretty much sucks that all branches tied to merge proposals will break, unless we hunt down each and upgrade (which takes ages remotely)23:32
lifelessPeng_: and the jail23:32
awilcoxokay it has been a few days so I think I will reask my question.  Is there any way to utilise Bazaar in XCode?23:32
Peng_Yeah, I love the jail.23:32
lifelessPeng_: the jail works with the chroot decorator23:32
lifelessawilcox: no idea sorry; have you checked the IDE page?23:33
awilcoxlifeless: I have and it said that CVS, SVN, and Perforce are supported natively, but others can use a plug-in interface23:33
lifelessawilcox: I mean our one23:33
lifelesson bazaar-vcs.org23:33
awilcoxI googled, and some people mentioned projects for a plug-in, but I haven't found the actual code.23:33
Peng_The situation is, I have branches of one project in 3 different locations, with a checkout in 1 of them, and want to get rid of one of the duplicate repositories. (The other can stay, I guess. Although I could convert it to a stacked branch too, hmm.)23:33
awilcoxohhhh sorry.23:33
awilcoxhttp://bazaar-vcs.org/IDEIntegration doesn't even have XCode listed.23:39
lifeless:(23:39
lifelesscare to add it?23:39
awilcoxI don't see a way to edit the page23:42
lifelessbottom of the page is an edit link23:43
lifelessif you're logged in23:43
awilcoxah.  I don't have an account.23:43
lifelessif you don't have an account you can just create one, or I can add xcode to it for you (but I don't know anything about xcode which is why I asked you to add it :))23:43
* beuno -> off for a while23:45
Raimhi23:56
Peng_Hello23:56
RaimI am trying to branch using bzr 1.9 as client from a server with bzr 1.5 using the bzr+ssh:// protocol23:57
Raimare these versions known to be incompatible?23:58
mwhudsonRaim: no23:58
Raimso I am seeing these messages and it fails: http://pbot.rmdir.de/0347a921ae170e1ba6dfb075de29c6d023:59

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