/srv/irclogs.ubuntu.com/2011/11/20/#bzr.txt

=== mnepton is now known as mneptok
=== _nyuszika7h_ is now known as nyuszika7h
=== LeoNerd is now known as LeoNerdF
=== Noldorin__ is now known as Noldorin
Noldorinhey folks19:14
Noldorinjelmer19:14
alansaulHey guys, I've got a problem, I pushed a branch onto my main trunk repo, overwriting the entire revision history of the trunk21:27
alansaulHow can I get this back? My trunk is now has the same revision history as my branch! Bzr push doesnt seem to be incremental!21:27
alansaulAnyone any ideas?21:31
alansaul:( I don't want to develop anymore incase I can get it back somehow!21:37
alansaulseems really flakey if there is no way to get it back!21:37
beunoalansaul, hi21:42
beunoyou did push --overwrite?21:42
alansaulbeuno: Hey :)21:42
alansaulErmm, no, unless that is the default21:43
beunoit isn't21:43
alansaulI had a branch say x21:43
alansaulof trunk21:43
alansaulmade lots of changes21:43
beunoso you went from revision 120 to revision 221:43
beunosomething like that, yes?21:43
alansaulmerged trunk into x to make sure there was no conflicts21:43
alansauland then did bzr push x serverrepo/trunk21:43
alansaulbeuno: yeah21:43
beunoright21:43
beunoso here's what happenes21:43
beuno*happened21:44
beunotrunk was at revno 120 (lets pretend that's the revno)21:44
alansaulyep21:44
beunoyour local branch was at revno 1021:44
alansaulyep21:44
beunoyou merged in trunk, so you got revision 1121:44
beunoand pushed that21:44
alansaulyep21:44
beunowhich made trunk 1121:44
alansaulyep21:44
beunoin order to prevent that in the future21:44
beunowhat you do is have a mirror of trunk locally21:44
beunoand merge your branch into trunk21:45
beunoand not the other way around21:45
beunoand then push that21:45
alansaulbeuno: Yeah i realise that now :)21:45
beunothere's also a config value that will prevent revisions to be removed21:45
beunoso21:45
alansaulor merge trunk into x, then x into trunk21:45
alansaulthen push21:45
beunoif you do a "bzr uncommit" on trunk, I think that'll bring it back to the previous state21:45
alansauloooo21:45
alansaulhmmm its asking if I want to remove the revision 1121:46
beunoyes21:46
alansaulhmmm, my local trunk isnt up to date with my server trunk21:47
alansaulshould i update first yeah?21:47
beunosure, get them both in the same state21:47
alansaul(just don't wanna mess this up to some sort of irreversable state!)21:47
beunoright21:47
beunoI'd back up everything21:47
beunojust in case  :)21:47
alansaulhmmm21:47
beunojust copy over the folders21:48
alansaulokay so make a copy of my local trunk and branches just somewhere else locally?21:49
beunoyes21:49
alansaulokie21:50
alansaulokay whilst its copying, ill ask a few questions :P21:50
alansaulso uncommit will remove commit 11? and will go back to 120?21:50
fullermdI'm not sure uncommit is really what you want...21:50
alansaulOop... holding21:50
beunofullermd, no?  unless he has a previous copy of trunk, un-mangled, not sure how else to get there21:51
fullermdYou can just make one.21:51
fullermduncommit would just back you up to the rev before you merged trunk.21:51
fullermdPoke at log to find the previous head rev, make a new branch from that, push (--overwrite) over trunk, then go back to the question of merging in the local branch.21:52
alansaulI want to bring the trunk back to how it was before it was pushed ontop of21:52
fullermd(previous _trunk_ head rev that is)21:53
alansaulfullermd: Hmm think you lost me there21:53
fullermd(sorry, I'm in the middle of some stuff ATM...   don't have time for details for a bit  :|  )21:53
alansaulAww21:54
alansaulmy bzr log has branch nick: trunk up to 18 then branch-x from 18 to 2421:54
alansaulBut my trunk was on commit 48 or something before i pushed ontop of it21:54
fullermdImportant thing is: Don't Panic.  As long as push didn't require --overwrite, you've never lost anything.  It's just been rearranged.21:55
alansaulHmm, well that sounds promising! I just cant find anywhere in any logs which have a revno of 4821:56
fullermd'll have time in 15 or 20 minutes or something if nobody else elaborates before then.21:57
alansaulfullermd: Sweet, I can wait21:58
alansaulfullermd: Thanks :)21:58
fullermdIf you're bored 'till then, reading http://wiki.bazaar.canonical.com/MatthewFuller/SpotDocs/RevNumbering and http://wiki.bazaar.canonical.com/MatthewFuller/SpotDocs/RevHandling may help you understand what's happening.21:59
alansaulWorking on it :)22:17
* jelmer waves22:18
thomi|workHi - does anyone have any more information on bug #820805 ? I have run into this issue on a workmate's laptop and can't seem to work around it with any of the fixes mentioned in the bug report.22:18
ubot5Launchpad bug 820805 in Bazaar "access denied on Pageant .pag file" [Undecided,Confirmed] https://launchpad.net/bugs/82080522:18
alansaulfullermd: Okay read them :) Let me know when your back :)22:29
jelmerthomi|work: mgz has done some research into those bugs22:34
jelmerthomi|work: he posted a summary to the list a week or so ago22:34
wgzI've got a patch for pageant to send as well, the pain is I'm struggling to test it22:35
wgzas much as I dislike unix permissions, windows security things are far more painful.22:36
thomi|workwgz: I don't suppose you have a replacement .exe I could test for you?22:40
thomi|workI gotta skip out for lunch, but If there's anything I can do to help I'll give it a go.22:40
wgzI do, it's 32 bit though.22:45
wgzthomi|work: http://float.endofinternet.org/temp/pageant_dbg.zip22:47
wgzit's built with the debug stuff enabled so pops up a console with info22:48
wgzif you need a 64 bit version I'll look at cross compiling, but can also cc you on the patch (their list doesn't seem to be public)22:48
Noldorinhi poolie22:54
pooliehi Noldorin22:55
fullermdalansaul:  OK, yeah, that was sorta like 15 or 20 minutes...22:56
alansaulfullermd: Lol thats cool thanks for coming back :)22:56
Noldorinpoolie, saw your response to my bug (suggestion) about download types, etc. happy to talk about it here if you like22:57
alansaulI have to go reasonably soon though!22:57
fullermdSo, did that reading illuminate anything for you?22:57
alansaulso I need to find the revid that relates to revno 48 and revert back to that?22:57
alansaulits still there somewhere22:57
fullermdYah.  Or the new revno, even.22:58
fullermdLook at `bzr log -n0`.  Your latest rev is the one that merged trunk, right?22:58
fullermdSo the old head of trunk would be the first indented rev under that.  It'll have a dotted revno of some sort.22:58
alansaulnaw the last one isnt the merge22:59
alansaulI have a revno: 16.2.1 [merge] though23:00
alansaulbut its a few revisions behind, im on revision 2423:00
alansaulIf I can get this trunk back to the state before though, I can merge in the changes i made in the branch properly23:00
fullermdWell, wherever it was.  You merged in trunk, before pushing over it.23:01
fullermdI'm presuming you haven't done anything on trunk since (nor anybody else); in that case things get messier.23:01
alansaulI don't think so no23:01
fullermdSo whichever your 'merge in trunk' rev is, the first rev indented under that is the rev that was at the time the head of trunk.23:01
alansaulmy branch x is basically a more up to date version than the trunk, but i just want to merge it into the trunk without losing all the revision history the trunk had23:02
fullermdMmm.  Well, let's glance back a moment.  It's not lost, it's just not on the mainline (so log won't show it unless you use -n0).  Does that matter?23:02
alansaulI think I want to revert back to revno: 16.2.1 [merge]23:02
fullermdOnly thing that gives me pause there is that that revno implies that it was only a single rev merged (e.g., trunk had only grown one new thing).  Is that right?23:04
alansaulUmmm im not sure what you mean?23:06
alansaulThere is a further indented bit23:06
alansaulrevno: 16.1.2923:07
fullermdMmm.  Is this something you can share?23:07
alansaulMy revno: 16.2.1 [merge] has a commit comment of Merged data model with trunk, only one failing test (due to users not being implemented yet)23:07
fullermdi.e., a public branch I can clone and look at?  Or a log you can substantially pastebin?23:09
jelmerhmm, I think I got carried away by the awesomeness of HPSS there for a second..23:44
* jelmer goes back to spiv's branch23:44
jelmer(I'm not sure what made my inexplicably scared of the HPSS subsystem earlier, but it's really nice once you get used to it)23:44
jelmers/my/me/23:44
wgzyeah, going a bit overboard jelmer :)23:45
wgzone complaint, adding more things that bz2 on the fly is kinda ugh23:45
jelmerwgz: what would you like to do instead?23:46
wgzpractically, or ideally? :)23:46
wgzI'd like to see numbers for size/performance vs zlib23:47
jelmerboth :)23:47
wgzideally, sendfile.23:47
jelmerwgz: sendfile doesn't seem ideal bandwidth-wise23:48
jelmerwgz: you have a point bout zlib vs bz2 though23:50
jelmer*about23:50
pooliehi all23:50
pooliejelmer, i like seeing all those patches23:51
poolieyou should run it under Judge :)23:51
poolieyou might need to patch it to add some more options, like for the number of times23:51
poolieto run the test23:51
pooliei really hope to go back to memory consumption soon23:51
pooliei did some fun lp hacks on the weekend though23:51
wgzat least for initial branching, I've measured smaller transfer, and smaller resource usage with dumb transports over smart ones, because of the recompression/overhead23:51
wgzbeing able to pick out just the latest changes is something where smart and recompress does do better than splatting bytes, but wanting to get a whole repo isn't uncommon either23:52
jelmerhi poolie23:53
jelmerpoolie: Yeah, I should give that a try, at least for some of the methods where performance is relevant.23:53
jelmerwgz: at least for the things I've tried adding smart methods had a significant impact. I haven't compared with zlib though23:54
spivjelmer: :)23:54
pooliehi spiv23:56
jelmerpoolie: btw, thanks for being so persistent in trying to separate launchpad-buildd from its big siamese twin :)23:56
jelmerhey spiv23:56
poolieit's kinda funny23:56
pooliejust when you think it's deleted it rises back up like a zombie23:56
pooliedo you guys really like the subunit test output?23:57
pooliei'm not finding it very easy to deal with23:57
wgzit makes a massive difference for anything doing operations on a remote repo23:57
jelmerpoolie: :)23:57
poolieeg subunit crashed filtering this failure23:57
jelmerpoolie: I think the old subunit stuff was kinda nice to read. The new bits (with mime encoding) are harder to read, but alright after applying a filter. Also, testrepository ftw :)23:58
wgzbut for mirroring the data it can be suprisingly poor23:58
wgzpoolie: not much. are we talking pqm or in general?23:59
wgzit has definite robustness issues.23:59

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