[00:19] <lifeless> poolie: landline is diverted, ping me I ring you
[00:20] <chiefinnovator> hi all, how can I find out what revision a file was added?
[00:21] <lifeless> bzr log file
[00:22] <chiefinnovator> bzr: ERROR: Path does not have any revision history: PyRSS2Gen.py
[00:22] <chiefinnovator> maybe it was never added?
[00:22] <bob2> bzr log --line filename | awk '{print $1}' | sed -e s/://
[00:22] <chiefinnovator> If I put a new file in the directory and do a commit, does it get added automatically?
[00:22] <lifeless> chiefinnovator: no
[00:22] <lifeless> chiefinnovator: you need to run bzr add
[00:23] <chiefinnovator> ohh
[00:23] <lifeless> chiefinnovator: you can use --strict on commit to have bzr error if you have un-added files
[00:23] <bob2> perhaps we could have some sort of regexp that designates a "source" file
[00:23] <bob2> and automatically add them
[00:23] <lifeless> bob2: hi tom, I see you've changed your nick
[00:24] <bob2> chiefinnovator: or add "[ALIASES]\ncommit = commit --strict" to ~/.bazaar/bazaar.conf
[00:24] <chiefinnovator> thanks
[00:24] <lifeless> bob2: we don't need an explicit include regexp because we have an explicit exclude one
[00:30] <mtaylor>   File "/usr/lib/python2.5/site-packages/bzrlib/graph.py", line 48, in <module>
[00:30] <mtaylor>     class DictParentsProvider(object):
[00:30] <mtaylor>   File "/usr/lib/python2.5/site-packages/bzrlib/graph.py", line 56, in DictParentsProvider
[00:30] <mtaylor>     @symbol_versioning.deprecated_method(symbol_versioning.one_one)
[00:30] <mtaylor> AttributeError: 'module' object has no attribute 'one_one'
[00:31] <mtaylor> hm
[00:31] <mtaylor> that's no fun
[00:32] <mtaylor> nm... I think I know what the problem is... maybe...
[01:31] <lifeless> mtaylor: interesting
[01:42] <mtaylor> lifeless: so, I got that from having a running bundlebuggy and then upgrading bazaar out from underneath it
[01:49] <Solarion> what is "rich-root" format?
[01:50] <fullermd> It emails your credit card number to your sysadmin.
[01:50] <bob2> it stores information about the branch root (.)
[01:50] <bob2> in practice, "it's the branch format you need to use bzr-svn"
[02:01] <ubotu> New bug: #187207 in bzr "commit reports error when a file has been moved and then removed in the same revision" [Undecided,New] https://launchpad.net/bugs/187207
[02:02] <Solarion> bob2: danke
[02:11] <bob2> (or rich-root-pack)
[02:13] <lifeless> always go for rich-root-pack over rich-root
[02:14] <bob2> both seem a lot slower for pulling from a pack repository than regular pack
[02:14] <Solarion> how does one select rich-root-pack over rich-root?
[02:14] <lifeless> yup
[02:14] <lifeless> different code path
[02:15] <bob2> like orders of magnitude
[02:15] <lifeless> bob2: thanks :)
[02:15] <bob2> Solarion: --rich-root vs --rich-root-pack to bzr init-repo/upgrade
[02:15] <bob2> hah
[02:15] <lifeless> Solarion: but only use --rich-rooot if you are using bzr-svn
[02:15] <lifeless> bob2: I worked quite hard to make packs fast :)
[02:16] <Solarion> lifeless: I am indirectly
[02:16] <Solarion> this is a branch of my working branch
[02:24] <bob2> lifeless: yeah, I've noticed :) is rich-root-pack going to be able to inherit much of that work?
[02:24] <fullermd> Actually, I imagine it does, if it's pulling rrp->rrp.  It's p->rrp that doesn't get the benefit.
[02:24] <bob2> hm
[02:25] <fullermd> (that's just a guess, of course)
[02:32] <jelmer> --rich-root-pack should be as fast as --pack-0.92 I think
[02:32] <jelmer> it only uses a slightly different serializer
[02:33] <mwh> jelmer: so loggerhead actually already supports file path/revision number based urls
[02:33] <jelmer> mwh: oh ok
[02:34] <jelmer> mwh: what url format should I use?
[02:34] <mwh> there is no way to know this without reading the source though
[02:34] <mwh> jelmer: i can't remember :/
[02:34] <mwh> i think you just put the revno where the revid would be
[02:34] <mwh> and append the path
[02:34] <bob2> pulling bzr.dev into a rich-root-pack repo is about 50% slower than into a pack one, and throws a missing revision error
[02:34] <mwh> so it's like http://loggerheadroot/annotate/$revno/file/path
[02:35] <jelmer> bob2: Right, I mean from rich-root-pack to rich-root-pack
[02:35] <bob2> jelmer: ah
[02:36] <jelmer> bob2: Anything that converts between formats is probably going to be slower (because you need to deserialize and reserialize)
[02:37] <bob2> ah - pack to rich-root is like 50x slower
[02:38] <fullermd> pack->knit (which r-r is) is probably real slow, since is has to generate the annotations...
[02:38] <bob2> ahhh
[02:50] <jearl> So what's the point of rich-root and rich-root-pack?
[02:51] <lifeless> bob2: don't pull bzr.dev into rich-roots yet anyhow, see the bug on lp about inventory sha corruption
[02:51] <bob2> ah
[03:15] <bob2> is it possible to get bzr log to show diffs?
[03:15] <bob2> or did I imagine that
[03:24] <skwashd> hi all
[03:25] <skwashd> any idea why ubuntu is shipping an uninstallable version bzr-svn in gutsy?
[03:25] <mtaylor> skwashd: why is it uninstallable?
[03:26] <skwashd> cos it depends on 0.91 yet the version of bzr in gutsy is 1.0.1
[03:26] <mtaylor> I think that's the version of bzr from bazaar-vcs.org
[03:26] <skwashd> \bzr-svn: Depends: bzr (< 0.91~) but 1.0-1~gutsy1 is to be installed
[03:26] <mtaylor> gutsy doesn't have 1.0 to the best of my knowledge
[03:26] <bob2> it's in gutsy-backports
[03:26] <mtaylor> did you add the bazaar-vcs.org apt sources to your sources.list?
[03:27] <mtaylor> ah
[03:27] <bob2> but an updated bzr-svn is not
[03:27] <mtaylor> well then.
[03:27]  * mtaylor recommends the bzr ppa ... but that's not really the question here, so he'll shut up now :)
[03:28] <skwashd> mtaylor: ok i will try that
[03:28] <bob2> skwashd: if you can live with older bzr, sudo aptitude install bzr=0.91, or what mtaylor said
[03:29] <mtaylor> which will give you bzr 1.1.0
[03:31] <pooliex61> mtaylor, you're the second person to mention this
[03:31] <pooliex61> could you file a bug on launchpad please?
[03:37] <beuno> quick question. What is used to output messages with line breaks in bzr?  been pokng around but I can't find any examples
[03:48] <skwashd> great now i have bzr 1.1 installed
[03:48] <skwashd> next issue :)
[03:49] <skwashd> i have 2 svn repos ... i want to be able to merge from one to the other ... can bzr handle that?
[04:55] <abentley> bob2: you imagined it, but feel free to make your dreams reality.  The API for diffing is pretty straightforward.
[04:56] <bob2> hehe
[04:56] <igc> bbiab
[04:58] <abentley> fullermd: that's a planned feature, but not here yet.
[04:59] <bob2> abentley: hm, do you think it'd be more reasonable to show diffs for each (nested) revision, or just leaves?
[05:01] <lifeless> bob2: I proposed log -vv to do this on the list a week or two ago
[05:01] <abentley> bob2: I use log-format=short, because I don't want to know about nested versions.
[05:01] <lifeless> bob2: patches for the win
[05:01] <bob2> ah
[05:01] <bob2> lifeless: hah, missed that, but that's the command I was trying
[05:01] <lifeless> log -v -> status
[05:01] <lifeless> log -vv -> diffs
[05:01] <lifeless> as abentley says, get it working :)
[05:01] <abentley> So I don't know what someone using log-format=long would want.
[05:02] <fullermd> If bob2 touches the code, that means he gets all wishlists for the output forever, right?   ;)
[05:02] <lifeless> for long, I would like to see the diff against each left hand parent
[05:02] <bob2> fullermd: the bikeshed will remain unpainted
[05:02] <lifeless> hmm
[05:02] <lifeless> or
[05:02] <lifeless> possibly better
[05:03] <abentley> Either that, or that shade of puke green that Tom's so fond of.
[05:03] <lifeless> the diff against the next output revisions
[05:03] <lifeless> abentley: zouch
[05:03] <bob2> haha
[05:03] <lifeless> abentley: you should be careful now; as an employee of The Evil Corporation(TM) you are now ripe for abuse and slander
[05:03] <bob2> (I was looking for the diff that showed why bzrlib.fetch.Fetcher was removed and broke the fetch command)
[05:04] <abentley> lifeless: oh fun.
[05:04] <lifeless> bob2: actually for diffs its easy: do the same diff that log -v does status off
[05:04] <lifeless> s/off/of/
[05:05] <lifeless> bob2: that way, we can just change both at the same time if so desired
[05:05] <abentley> lifeless: +1
[05:07] <abentley> oh, btw: did BB send you an error message for your bb:discuss-please ?
[05:07] <lifeless> yes
[05:08] <abentley> Sorry about that.  But I'm glad the error reporting's working.
[05:08] <lifeless> oh I was expecting something of the sort :)
[05:10] <bob2> heh, perhaps it is time to remove legacy_lf
[05:32] <bob2> lifeless: I can't quite figure out what you mean by "do the same diff thsat log -v does status off"
[05:32] <fullermd> Do the diff relative to the revision that it does the stat relative to for the filenames affected.
[05:34] <bob2> right
[05:36] <bob2> hm
[05:50] <abentley> Oh good grief!  I didn't even know we *had* a "get_deltas_for_revisions" method.
[06:19] <lifeless> abentley: didn't you add that ?
[06:19] <lifeless> abentley: btw, thats the sort of method I expect repo's to specialise :)
[06:51] <poolie> lifeless, i'm off the phone etc, but i guess you'regone
[06:52] <poolie> or anyhow you should go, soon
[06:52] <lifeless> heh
[06:52] <lifeless> you had a phone day huh?
[06:53] <poolie> yeah
[06:53] <poolie> one more mail, then it's either you or the bike :)
[06:54] <lifeless> on your bike
[06:54] <lifeless> lets talk tomorrow avo
[06:54] <lifeless> 3ish
[06:55] <poolie> fine with me
[06:55]  * lifeless is about to wow
[06:55] <poolie> enjoy
[09:50] <ubotu> New bug: #187267 in bzr "UnicodeDecodeError with non-ASCII character in filename" [Undecided,New] https://launchpad.net/bugs/187267
[10:25] <vila> jelmer: ping, got a workaround for the infamous '_' used for gettext in bzr-gtk clashing with bzr selftest
[10:41] <jelmer> vila: ah, nice
[10:42] <jelmer> vila: any chance you can send an email to the bzr-gtk list?
[10:42] <vila> jelmer: :) That's the bit I was searching, my last patch to bzr-gtk is so old I can't remember the workflow :)
[10:44] <vila> jelmer: is there a bug on lp or that ?
[10:44] <vila> s/or/for/
[10:44] <jelmer> I'm not sure
[10:44] <jelmer> it's a bit quiet in bzr-gtk land at the moment
[10:55] <vila> jelmer: Ok, I'll  file one then
[10:56] <ubotu> New bug: #187280 in bzr "Running 'bzr -log -r branch:../other_branch' raises ReadOnlyError" [Undecided,New] https://launchpad.net/bugs/187280
[11:00] <Toksyuryel> bzr rocks ^_^
[11:00]  * Toksyuryel just wanted to say that
[11:00] <vila> Toksyuryel: thanks :)
[11:05] <ubotu> New bug: #187283 in bzr-gtk "bzr selftest bizarre errors related to '_''s gettext" [Undecided,New] https://launchpad.net/bugs/187283
[11:08] <jelmer> vila: are you going to post the workaround too ? :-)
[11:08] <vila> jelmer: sure :) Finishing the mail, I needed the bug number before hand :)
[11:13] <vila> jelmer: sent
[11:17] <jelmer> thanks :-)
[12:24] <muffinresearch> The bazaar site has a list of projects that use bazaar http://bazaar-vcs.org/WhoUsesBzr. Is this up to date and does anyone have any other good examples of  large projects/companies using bazaar?
[13:16] <quik__> hey folks
[13:16] <quik__> the bzr mac port seems to always be broken
[13:17] <quik__> is there anything that I should know?
[13:19] <Peng> Well, the developers are all goths from Mars.
[13:20]  * Peng gets booed off the stage.
[13:22] <beuno> Peng, hehehe, it's early/late in the morning/evening for jokes that complex  :p
[13:22] <quik__> I reckon they might be. firstly they have a special deb-source for ubuntu. then the ports never work
[13:22] <quik__> ubuntu universe, like the rest of the world uses.. is WAY out of date
[13:24] <beuno> ubotu, last time I heard they had make a dmg for OSX for 1.1 that seemed to work fine. Where are you downloading from?
[13:24] <beuno> argh
[13:25] <beuno> s/ubotu/quik__
[13:25] <brink_> _quik:  I just installed 1.1 on OS X.   You have to have xcode installed.   Otherwise some of the dependencies crash and burn.
[13:25] <quik__> I just installed leopard and xcode 3.0 on this laptop yesterday
[13:26] <brink_> Not trusting xcode 3.0, I did 2.5.
[13:26] <snod> did youz try macports?
[13:26] <quik__> it installed a few weeks ago on two other machines that are on the same..
[13:26] <quik__> yes, always macports
[13:26] <brink_> Me too.
[13:27] <snod> okay, because that worked for me, though I'll have to stick with tiger and Xcode 2.5
[13:27] <brink_> You should also uninstalled and clean the dependencies.  I did  that after it failed.
[13:27] <brink_> Then it worked.
[13:28] <brink_> Too bad xcode isn't available via macports.
[13:36] <quik__> I think apple think that macports is a bastard child that dirty developers use
[13:36] <quik__> I can't understand that its not built into the os or even installed with xcode
[13:52] <Mythos> Hi!
[13:52] <Mythos> I would like to ask something about the smart server!
[13:53] <Mythos> I have set up a smart server through inetd with --directory=/home/lala/bzr-repo which is my repository
[13:54] <Mythos> So bzr branch bzr://host/branch1, where branch1 a branch in my repo, works ok.
[13:54] <Mythos> But trying to push changes through bzr push bzr+ssh://login@host/branch1 throws the following error
[13:54] <Mythos> bzr: ERROR: Parent directory of bzr+ssh://login@host/branch1 does not exist
[13:55] <Mythos> And I can push only if I give the full path, like:
[13:55] <Mythos> bzr push bzr+ssh://login@host/home/lala/bzr-repo/branch1
[13:55] <Mythos> Why I can't just bzr push bzr+ssh://login@host/branch1?
[13:57] <snod> my guess, because your logging in via ssh you don't use the smartserver from inetd
[14:00] <Mythos> Probably you are right, because I also can't branch with  bzr branch bzr+ssh://login@host/branch1
[14:00] <Peng> Yes.
[14:00] <Mythos> bzr: ERROR: Not a branch: "bzr+ssh://papadako@groogle.csd.uoc.gr/branch1
[14:00] <Peng> bzr+ssh sshes in and runs "bzr server".
[14:00] <Peng> And its paths are relative to the root of the server.
[14:01] <Mythos> Ok. So I can't do anything about it, right?
[14:01] <Mythos> Relative paths are smaller than full paths.
[14:02] <snod> perhaps a chrooted ssh enviroment could work
[14:02] <Peng> Well, not easily, anyway.
[14:03] <Peng> What he said, or maybe the contrib/bzr_access script, or some sort of ssh configuration.
[14:03] <Mythos> Ok. Thank you!
[14:04] <Peng> Well, if you have root access, you can put your repos in /srv/bzr or something.
[14:05] <Mythos> Yep, this could also work
[14:15] <Mythos> One more question..
[14:15] <Mythos> Related to the webserve.
[14:15] <Mythos> Last change for each branch, shows 38 years....
[14:16] <Mythos> See http://groogle.csd.uoc.gr/bzr/
[14:16] <Mythos> Like it does not read info from the branch.
[14:23] <vila> 38 years ago is 1970, i.e Unix epoch or (time == 0), I'll check file last modification time and time itself on the server...
[14:40] <Mythos> Time on the server is fine
[14:40] <Mythos> Wed Jan 30 17:20:15 EET 2008
[14:41] <Mythos> http://groogle.csd.uoc.gr/bzr/groogle-2007 for example shows correct info
[14:41] <Mythos> It is the main page showing 38 years.
[14:41] <Mythos> Also I hit a bug in http://groogle.csd.uoc.gr/bzr/terrier-devel
[14:41] <Mythos> <type 'exceptions.IndexError'>: list index out of range       args = ('list index out of range',)       message = 'list index out of range'  0
[14:42] <Mythos> in templater.py
[15:36] <muffinresearch> The bzr vs hg page on the wiki mentions bazaar having integration with bugzilla out of the box. Can any one point me in the direction of documentation on this feature?
[15:41] <abentley> muffinresearch: bzr help bugs
[15:43] <muffinresearch> Excellent thanks for that
[15:56] <ubotu> New bug: #187330 in bzr "Commit failed with attribute error" [Undecided,New] https://launchpad.net/bugs/187330
[16:40] <ubotu> New bug: #187342 in bzr "'bzr add --verbose' quietly ignores subdirs with their own .bzr" [Undecided,New] https://launchpad.net/bugs/187342
[16:47] <nebuchadnezzar> hello
[16:49] <nebuchadnezzar> I want to use a shared repository on a remote server to keep configuration files, but I want a process on this server to use this configuration.
[16:49] <nebuchadnezzar> I planned to make a 'rsync in the after commit hook' but I think there is a better solution
[16:50] <asabil> push-and-update ?
[16:50] <nebuchadnezzar> something like that yes
[16:50] <nebuchadnezzar> it doesn't seems to work over sftp :-/
[16:50] <nebuchadnezzar> debian sid bzr 1.1~rc1-1
[16:51] <nebuchadnezzar> ok, push-and-update is a plugin
[16:52] <nebuchadnezzar> asabil: thanks, I'll test this, but I wonder if it can works with merge ?
[16:55] <abentley> nebuchadnezzar: If you're doing merges, you should always do them locally anyhow.
[16:55] <ubotu> New bug: #187349 in bzr ""bzr branch" throws MemoryError" [Undecided,New] https://launchpad.net/bugs/187349
[16:56] <nebuchadnezzar> abentley: ok, thanks
[16:58] <nebuchadnezzar> arf, it need bzr on the remote side, ok
[18:41] <b0ef> ehlo
[18:41] <b0ef> I get a criss-cross merge
[18:41] <b0ef> is even bzr merge --weave ../foobar supposed to tell me "criss cross merge encountered"?
[18:42] <abentley> Yes.
[18:42] <b0ef> but I can expect that everything is fine?;)
[18:43] <abentley> If you have no conflicts, you can.
[18:43] <abentley> Criss-cross refers to the context in which you're doing the merge.  --weave just changes how you do the merge in that context.
[18:44] <b0ef> right, I'll just --weave and criss-cross fingers, then;), thanks
[18:45] <abentley> If you've got a recent Bazaar, --lca is faster and should give better results than --weave.
[18:47] <b0ef> abentley: thanks, I'll try
[18:47] <dato> I did a --lca the other day, and it didn't gave me a conflit where I was expeting one
[18:47] <dato> expecting
[18:47] <dato> and well, between the two possibilities, it didn't do the one I wanted
[18:47] <b0ef> no, I don't have any conflicts; it's just that I read that I might loose some history
[18:49] <abentley> dato: Okay, if you can send me details I'd appreciate it.
[18:49] <dato> sure, hang on
[18:59] <dato> abentley: I mailed you a recipe
[19:09] <abentley> dato: Thanks.  I've followed it, but NEWS produces conflicts whether I specify --lca or --merge3.  The output is identical.
[19:10] <dato> abentley: I think I said TODO, not NEWS?
[19:10] <abentley> Oh, my bad.
[19:10] <dato> ok
[19:12] <abentley> Yes, I confirm the difference in TODO.
[19:17] <abentley> However, I'll point out that --weave has the same problem as --lca for cases like this.
[19:18] <abentley> So I still think --lca is better that --weave, it's just not better than merge3 for this case.
[19:18] <dato> oh, indeed. I couldn've sweared I got a conflict with --weave.
[19:18] <dato> but you're right
[19:19] <dato> could've
[19:19] <abentley> I'll see what I can do to ensure conflicts in this case.
[19:19] <dato> ok, thanks for taking a look
[19:20] <abentley> Thanks for the report.
[20:11] <lifeless> moin
[20:13] <james_w> hi lifeless.
[20:13] <james_w> safely back?
[20:13] <lifeless> yup
[20:18] <abentley> Safe for who? (ducks)
[20:19] <lifeless> :-
[21:06] <jam> lifeless: ping
[21:06] <james_w> jam: hi
[21:06] <jam> hi james_w
[21:07] <james_w> jam: I got 550 Administrative prohibition when sending to your email account, did I do something to offend your mail server?
[21:07] <jam> hmm. I haven't seen Administrative prohibition, I've do have a greylist that asks people to try sending again after a while
[21:08] <jam> you might just try re-sending your email
[21:09] <jam> which is usually enough to get past the greylist
[21:10] <fullermd> Greylist certainly shouldn't 5xx, though.
[21:10] <james_w> jam: I assume you will get it via the list, so it's no loss.
[21:11] <jam> I admit to not being a mail guru, but I'm thinking it was giving 4xx
[21:11] <jam> james_w: well, I have no-dupes turned on, so I may not
[21:12] <fullermd> Hate that option.  Hate mailing lists that set it by default.
[21:12] <james_w> jam: looking in my logs it seems I also got a 450 Client host rejected: cannot find your hostname, [89.145.97.141]
[21:13] <m3thos> why is a reverse dns failure a motive to reject a host ?
[21:13] <jam> fullermd: it works very well for me
[21:13] <fullermd> It's not rejected, it's deferred.
[21:13] <jam> fullermd: it might be rejected
[21:14] <jam> I get a lot of spam
[21:14] <fullermd> ('course, presumably the sending host will stop trying eventually)
[21:14] <jam> The grey-list should be asking them to resend later
[21:14] <jam> but if I can't do a reverse lookup
[21:14] <jam> it may consider you suspect
[21:14] <fullermd> It's still 4xx'ing.  It won't get as far as the greylist checking then.
[21:14] <jam> # Reject sender hostname without DNS A or MX record, permit sasl users,
[21:14] <jam> # permit $mynetworks, check for permit/reject in /etc/postfix/access.
[21:14] <jam> #
[21:14] <jam> smtpd_sender_restrictions = reject_unknown_sender_domain,
[21:14] <fullermd> You wouldn't want to 5xx a PTR lookup failure, since that can be transient.
[21:15] <jam>         permit_sasl_authenticated, hash:/etc/postfix/access
[21:15] <fullermd> I find it easier to have all my restrictions in _recipient_restrictions; that way I can avoid repeated lookups, and have the precedences all the way I want 'em.
[21:15] <lifeless> jam: pong
[21:15] <fullermd> (of course, it's also 28 lines long, which may seem excessive...)
[21:16] <james_w> jam: ah, it's a different host that sends the 550
[21:16] <lifeless> m3thos: spammers
[21:16] <fullermd> But anyway, that error james_w pasted is from reject_unknown_hostname, not a sender call.
[21:16] <jam> lifeless: I wanted to pick your brain a bit about bug #187169
[21:16] <ubotu> Launchpad bug 187169 in bzr "Partial commit with mv and rm under breaks dirstate" [Critical,In progress] https://launchpad.net/bugs/187169
[21:16] <lifeless> sure
[21:17] <james_w> it hits your secondary MX for the retry, and get's the 550.
[21:17] <jam> So the first issue is that we have a rename and a file underneath that directory is deleted
[21:17] <jam> I checked with the old "knit" format
[21:17] <jam> and under that condition
[21:17] <jam> we would get a renamed foo => bar to be committed
[21:17] <jam> but the delete would still be pending
[21:18] <lifeless> bleep
[21:18] <jam> I think it is arguable which should happen (since the user script deletes it *after* the rename), but we can preserve either behavior
[21:19] <jam> So the failure of "update_basis_by_delta" is that it expects you wouldn't be renaming a file to a "deleted" target
[21:19] <lifeless> it sounds like we are creating an invalid delta?
[21:19]  * fullermd would absolutely expect the delete to be committed, FWIW.
[21:19] <jam> lifeless: well, the old code would have created a new record which is marked as already deleted
[21:19] <fullermd> (short of a commit --no-recurse or some such option)
[21:20] <jam> fullermd: there is a small problem in detecting that it happened, but I do understand your point
[21:20] <fullermd> I wouldn't expect the order of operations to matter, just the state when you 'commit'.
[21:21] <lifeless> fullermd: interesting topic, but orthogonal
[21:21] <jam> fullermd: sure, it is more that when you delete the file after the rename, the way it is stored makes it a little bit trickier to tell that it should be affected by the partial commit
[21:21] <lifeless> fullermd: perhaps we can focus on the bug-in-hand
[21:21] <jam> lifeless: anyway, the update_basis_by_delta code assumes that the target won't be marked "absent"
[21:21] <lifeless> jam: so we have /deleted-path (A, F)
[21:22] <lifeless> and we issue a rename in the delta ? /deleted-path -> /renamed-deleted-path
[21:22] <lifeless> but rather than getting (A, R(/deleted-path))
[21:23] <jam> it borks
[21:23] <jam> with "invalid ..."
[21:23] <jam> and then stops processing the delta
[21:23] <jam> which borks future operations because the rename was only partially applied
[21:24] <lifeless> ok
[21:24] <lifeless> so lets do two things here
[21:24] <lifeless> lets make this transactional
[21:24] <asabil> is bzr-svn able to handle https repos ?
[21:24] <asabil> like google code ?
[21:24] <lifeless> mark the dirstate as in-memory-fucked, and refuse to write it out
[21:24] <lifeless> asabil: yes
[21:24] <asabil> hmmm then what is wrong :
[21:24] <jam> asabil: I *think* you have to connect to it with the raw svn client first
[21:25] <jam> so that it can save the credentials
[21:25] <asabil> Unable to handle http code 401: expected 200 or 404 for full response.
[21:25] <jam> and then use "svn+https://"
[21:25] <lifeless> asabil: thats in the faq I believe
[21:25] <asabil> oh ok thanks
[21:25] <fullermd> This may or may not be related to bug 187207, too.  The trigger and symtoms are a bit different (not partial, second commit succeeds, stat doesn't fail), but it's a similar dirstate errror.
[21:25] <ubotu> Launchpad bug 187207 in bzr "commit reports error when a file has been moved and then removed in the same revision" [Undecided,New] https://launchpad.net/bugs/187207
[21:25] <asabil> so https is basically "half" supported
[21:26] <jam> asabil: AFAIK it is a problem with the SVN bindings not exporting the right stuff so that we can handle authentication prompts
[21:26] <asabil> okidoki
[21:26] <jam> which I think might be fixed in newer python-subversion bindings, which means it is also fixed in newer bzr-svn
[21:27] <jam> but I'm going from hazy memory of conversations with jelmer
[21:27] <jelmer> should work with all versions of python-subversion
[21:27] <jam> jelmer: I thought you couldn't authenticate to svn+https
[21:27] <jelmer> but you may have to prefix the url with "svn+" otherwise bzr-svn never sees the connection
[21:27] <jelmer> jam: You can, if you let svn do it for you
[21:27] <jam> using svn+?
[21:27] <jam> or you have to connect using svn one time and save the auth
[21:27] <jelmer> jam: or with python-subversion 1.5 bzr-svn can prompt you
[21:28] <jam> jelmer: that is what I thought, which is what I was trying to get across
[21:28] <jelmer> jam: sorry, I just read the line that said "jelmer" because that's the bit xchat highlighted
[21:28] <jam> lifeless: so, back to our thread.... I agree about marking the dirstate as IN_MEMORY_BROKEN
[21:32] <jam> how would you handle renaming an absent record?
[21:32] <jam> At first I thought about just skipping the error check
[21:32] <jam> but it seems to complain later on, too
[21:33] <lifeless> so the record is not included in the delta
[21:33] <lifeless> erm rephrase
[21:33] <lifeless> a delta that has a rename with a child that is absent
[21:33] <jam> (the first error is when it goes to process the delete side of the rename, it expects the file to have existed, the second error is when it goes to add the record, it expects the target path to already exist)
[21:33] <lifeless> [/foo->/bar], and /foo/quux is marked absent
[21:33] <lifeless> is that the situation ^ ?
[21:34] <jam> lifeless: correct
[21:34] <lifeless> so expanded we get [/foo/quux, /foo, /bar, /bar/quux] as the order of paths we touch
[21:34] <lifeless> or thereabouts
[21:35] <lifeless> hmm, so the question is 'is it valid to rename a deleted file'
[21:35] <lifeless> if we say 'no' then we have to fix commit to spider out file ids properly
[21:36] <lifeless> rather than the current broken code
[21:36] <lifeless> this is quite easily actually, with dirstate
[21:36] <lifeless> and I think that failing to commit the delete is definately a bug
[21:37] <jam> I'm curious if there would be another way to trigger this
[21:37] <jam> such that update_basis_by_delta should really handle it
[21:37] <jam> but otherwise I agree with you
[21:37] <lifeless> I think foxing the corruption is sufficient for now - if another case turns up we'll get a bug report :)
[21:38] <abentley> lifeless: fwiw, I think it should valid to rename a deleted file.  TreeTransform is explicitly designed to support that.
[21:38] <lifeless> abentley: in terms of historical trees though, this shows up as a rename and no delete
[21:39] <abentley> I would hope it would show up the same way as the reverse order would.
[21:39] <abentley> i.e. rename, delete.
[21:39] <lifeless> abentley: the delete is being skipped by commit
[21:39] <lifeless> abentley: so the delta does not include the delete
[21:41] <jam> lifeless: that, and if it did show the delete, it would show up as only a delete
[21:41] <lifeless> jam: right, but that would be correct and ok
[21:41] <jam> ie, it would show "old/b" deleted, not "old/b renamed to new/b" and "new/b" deleted
[21:44] <asabil> http://pastebin.be/8696
[21:44] <asabil> bzr exception with bzr-svn and google code
[21:44] <james_w> jam: I think that is just as accurate assesment of what happended.
[21:45] <jam> asabil: now there is an interesting path: /svn/!svn/vcc/default
[21:46] <james_w> jelmer: ^ have you seen that before?
[21:46] <asabil> jam: yep :) google code seems funky
[21:49] <james_w> asabil: https://lists.ubuntu.com/archives/bazaar/2008q1/036473.html
[21:50] <james_w> asabil: svn proplist https://waf.googlecode.com/svn/trunk/
[21:51] <asabil> oki
[21:51] <asabil> but this doesn't happen in the beginning
[21:52] <asabil> it happens at the end
[21:52] <asabil> and with an svn co
[21:52] <asabil> I get this after it is finished
[21:52] <asabil> svn: REPORT request failed on '/svn/!svn/vcc/default'
[21:52] <asabil> svn: REPORT of '/svn/!svn/vcc/default': 200 OK (https://waf.googlecode.com)
[22:01] <asabil> is it possible to convert an svn checkout into a bzr branch ?
[22:02] <jelmer> asabil: "svn co" (no bzr involved) also fails?
[22:02] <jelmer> asabil: Please file a bug against google code
[22:02] <asabil> jelmer: yes, but I can continue using an svn up
[22:02] <jelmer> asabil: still, that means there's a bug there
[22:02] <kjcole> qbzr plugin on the mac broke "bzr commit" ("bzr qcommit" still works.)
[22:03] <jelmer> asabil: a server bug most likely (googlecode uses a custom svn backend)
[22:03] <kjcole> (Error is "bzr: ERROR: [Errno 13] Permission denied")
[22:04] <jelmer> asabil: you can convert from a svn checkout to a bzr branch but it will use the same code patrh
[22:04] <jelmer> and will make the same requests to the svn server
[22:05] <asabil> oki :'(
[22:05] <kjcole> I just installed both today on a mac.
[22:12] <luks> how could installing qbzr cause "Permission denied"?
[22:17] <lifeless> the full backtrace may help
[22:17] <lifeless> check ~/.bzr.log
[22:17] <kjcole> luks I dunno.  I may be misinterpreting things as I hadn't tested much on the mac.
[22:17] <kjcole> lifeless, luks I just posted the log to launchpad
[22:18] <kjcole> lifeless, luks (under qbzr bugs)
[22:20] <luks> kjcole: the first commit was `bzr commit -m '...'` or `bzr commit`?
[22:20] <luks> the bug doesn't look qbzr related to me at all
[22:21] <luks> it has trouble launching the editor
[22:21] <kjcole> luks, bzr commit
[22:21] <luks> and it started an editor?
[22:21] <kjcole> luks, I've got my default editor set to emacs, which works fine on ubuntu (except that it doesn't delete the temp log file).  It appeared to work on OS X as well...
[22:22] <luks> check ~/.bazaar/config.conf
[22:22] <luks> er, ~/.bazaar/bazaar.conf
[22:27] <kjcole> luks, http://pastebin.ubuntu.com/4015/
[22:27] <luks> what happens if you remove the editor = "" line?
[22:28] <kjcole> luks, qbzr put in everything after the email line when I did the qconfig
[22:28] <luks> yes, that's probably the problem
[22:28] <luks> does it work if you remove it?
[22:29] <kjcole> luks, which is why I never thought to look at it.  So, that would be a qbzr bug?  (Removing now...)
[22:30] <kjcole> luks, that was it.
[22:31] <luks> ok, I'll try to convince ConfigObj to remove it instead of clearing it
[22:32] <kjcole> luks, if I decided to enter a value there, what's it looking for?  full path to my editor of choice?
[22:33] <luks> just the command name would be fine, if it's in PATH
[22:33] <kjcole> luks. thanks.
[22:34] <kjcole> P.S. what about command line arguments?  (for example "nano -bkw"?)
[22:34] <luks> no idea, try it :)
[22:35] <kjcole> Heh.  ;)
[22:37] <kjcole> luks, FYI It seems to work fine with the arguments.
[22:38] <james_w> The tarball of 1.1 on launchpad doesn't correspond to the tree of the last revision on the 1.1 branch. Should we release a 1.1.1 to fix this?
[22:38] <james_w> see bug #187330 for the details
[22:38] <ubotu> Launchpad bug 187330 in bzr "Commit failed with attribute error" [Undecided,New] https://launchpad.net/bugs/187330
[22:49] <igc> morning
[22:52] <james_w> morning.
[23:02] <jam> igc, poolie : meeting now?
[23:02] <igc> I'm on
[23:03] <igc> jam: poolie is still on a call apparently
[23:31] <ubotu> New bug: #187452 in bzr "Graph.find_differences() is confused by shortcuts" [Medium,Triaged] https://launchpad.net/bugs/187452