[03:17] <lifeless> jelmer: why did you marjk lp:~jelmer/testrepository/fix-uxsuccess rejected?
[04:50] <AuroraBorealis> hmmm
[04:50] <AuroraBorealis> anyone know what this error means? :<
[04:50] <AuroraBorealis> bzr: ERROR: Failed to rename C:/Users/Mark/Code/bzr/mips/csc252/trunk/prog2 to C:/Users/Mark/Code/bzr/mips/csc252/trunk/.bzr/checkout/limbo/new-5/prog2: [Error 5] Access is denied
[11:55] <jelmer> lifeless: I got a disapprove vote and I'm not going to look into it further at this point.
[14:53] <Noldorin_> hi jelmer
[14:53] <jelmer> hi Noldorin_
[14:53] <Noldorin_> how's it going?
[14:54] <jelmer> alright, how are you?
[18:59] <lifeless> jelmer: I thought it was just needs-tests
[18:59] <lifeless> jelmer: jml said he was going to look at landing it himself
[19:00] <jelmer> lifeless: yes, but with tests - my fix was trivial
[19:05] <jelmer> lifeless: anyway, I was mainly just trying to clean up my list of in-progress branches
[19:06] <jelmer> lifeless: I agree it wasn't really rejected as such, but there isn't really a way to stop being involved in a MP otherwise
[19:07] <lifeless> rejection doesn't stop involvement either :)
[19:08] <jelmer> lifeless: ok, you got me there. but it at least means it no longer shows up in my wip and needsreview listings
[19:08] <lifeless> sure. I can understad the motivation
[22:36] <lamont> bzr: ERROR: exceptions.AssertionError: get_next() called when there are no chars left
[22:36] <lamont> sigh
[22:36] <lamont> that's in 2.2.4-0ubuntu1
[22:44] <jelmer> lamont: hi
[22:44] <jelmer> lamont: that's usually a sign of a corrupt dirstate because of a truncated file - unsafe unmount?
[22:45] <jelmer> lamont: FWIW, newer versions of bzr fdatasync more agressively
[22:46] <lamont> jelmer: machine panic
[22:46] <lamont> so yeah, that could be consistent with an unsafe umount
[22:46] <lamont> OTOH, it should be ext3
[22:47] <jelmer> lamont: removing the checkout and creating it again should fix, but will discard any pending metadata changes you had in bzr
[22:47] <jelmer> "rm -rf .bzr/checkout; bzr co"
[22:48] <lamont> something tells me that a bzr co might tend to modify files in the working directory
[22:49] <spiv> lamont: IIRC it's not impossible for the "write tmp file, rename tmp to final location" idiom to leave 0-byte files after a crash with ext3, because by default it allows metadata to be committed before data.
[22:50] <lamont> spiv: and whether or not that is a grave bug in ext3 has been debated before
[22:50] <spiv> The O_PONIES feature request :)
[22:53] <jelmer> hey spiv :)
[22:53] <spiv> o/
[22:56] <lifeless> spiv: thats ext4 I believe
[22:56] <lifeless> spiv: ext3 cna't selectively sync journal contents
[22:57] <spiv> lifeless: IIRC it's possible (but less probable) under ext3 too
[23:00] <lifeless> spiv: you need journal_data_writeback for that
[23:00] <lifeless> spiv: IIRC which is not on ext3 by default (it defaults (or defaulted?) to journal_data_order
[23:01] <lifeless> spiv: IMBW - I haven't checked the code since ages ;)
[23:02] <spiv> lifeless: http://lwn.net/Articles/351422/ says the defautl mode under ext3 switched from data=ordered to data=writeback around 2.6.30
[23:03] <spiv> Possibly that change got reverted later due to this sort of fallout?
[23:03] <lifeless> ah! heh
[23:04] <spiv> But anyway that's enough for me to stop short of being certain that "default ext3" == "necessarily safe for that idiom"
[23:04] <lifeless> so if they changed that, then yes, its unsafe
[23:04] <lifeless> and sigh, still no user space barriers
[23:04] <lifeless> to we have to choose between slow and crap
[23:05] <lifeless> or use btrfs!
[23:07] <poolie> hi lamont, spiv, jelmer, lifeless
[23:11] <lamont> howdy
[23:11] <poolie> there is a repair-dirstate operation
[23:12] <poolie> 'bzr repair-workingtree'
[23:14] <lifeless> morning poolie
[23:15] <Peng> /1/1
[23:15] <Peng> >.>
[23:18] <poolie> lamont, i think that's https://bugs.launchpad.net/bzr/+bug/709158 btw
[23:18] <poolie> thanks for pointing it out
[23:19] <lamont> ah, cool
[23:30] <jelmer> g'morning poolie
[23:38] <wgrant> Morning.
[23:39] <wgrant> wgrant@lucid-test-lp:~/launchpad/lp-branches/separate-zopeless-mail$ bzr pull :push
[23:39] <wgrant> bzr: ERROR: Unsupported protocol for url "lp:~wgrant/launchpad/separate-zopeless-mail"
[23:39] <wgrant> Is that meant to not work?
[23:39] <wgrant> I believe the push URL is set in locations.conf.
[23:40] <jelmer> wgrant: it's a known issue; bzr itself always sets expanded URLs (not requiring directory services) in configuration files
[23:40] <wgrant> jelmer: Hmm, but bzr push works fine.
[23:41] <jelmer> wgrant: does "bzr push :push" work?
[23:41] <wgrant> Indeed not. Good point.
[23:42] <wgrant> At least there is a workaround, then. Thanks!
[23:45] <jelmer> wgrant: anytime