/srv/irclogs.ubuntu.com/2011/06/07/#bzr.txt

quotemstrIf I have a branch that's diverged from upstream, how do I discard my changes and revert so I can use 'pull' again (instead of merge)?03:25
spivquotemstr: pull --overwrite03:40
quotemstrspiv: Thanks.03:40
poolieand then 'bzr revert'04:44
pooliehi spiv04:44
spivHi poolie.04:50
spivpoolie: I'm currently digging into the libffi package import failure: initially it was the old stacked repo problem, but having repaired the stacked repositories (to have the parent inventories) some fetches still fail04:51
poolieok, that's good04:51
pooliei'm working on getting X going on my laptop04:52
pooliewell, on my laptop with an external screen04:52
poolieand i will push on 22046404:52
spivpoolie: I *think* there may be an issue when a revision in a stacked repo has the same inventory and thus same CHK maps as one of revisions immediately over the stacking boundary04:52
pooliewould be interested in your thoughts on the mp actually, if you didn't comment already04:52
poolienot the diff, just the conceptual thing of when we should consider it safe to break04:52
pooliehm, interesting04:53
spivAnd relatedly I'm finding there's no good in-tree documentation of the stacking invariants, and so perhaps unsurprisingly even if the code is correct here it's a bit unconvincing.04:55
pooliethat would be good to add04:55
pooliehm04:55
pooliei don't think we have properly closed things up about adding developer documentation04:55
spivBecause it just does a bunch of stuff to determine what records are interesting and uninteresting, without explaining/justifying why.04:55
pooliefor instance, how much we should insist on it being done in the mp04:55
poolieright04:55
spivYeah, I don't think so either, but I don't have any great ideas to fix that.  I am actually in the middle of drafting an addition about stacking to doc/developers/fetch.txt04:55
spivBut more out of a lack of better ideas about where to write it down in-tree than because I feel it'll actually acheive much :/04:56
poolieanyhow, i short, i think updating them would be very good04:56
pooliejorge gave a talk at UDS encouraging people to delete bad data from the Ubuntu wiki04:56
pooliei liked it04:56
pooliein fact he challenged people to delete 5 bad things from the internet each04:57
spivHeh.04:57
spivA productive variation on "someone is wrong on the internet" :)04:57
spivpoolie: so regarding the stale locks breaker04:58
spivpoolie: my first impression is "isn't your patch ok then?"04:59
poolie:)04:59
poolieon the whole it is04:59
pooliei think.04:59
poolierebooting to try a new kernel05:00
spivAs all the scenarios people are actually concerned about (as opposed to pathological hypotheticals) seem likely to work ok.05:00
pooliei think so05:00
spivHmm05:00
pooliethe hypotheticals like having two machines with the same name and the same disk are not... ridiculously contrived05:00
spivTrue, especially with default hostnames.05:00
pooliebut perhaps not that likely to happen05:01
spivBut people do tend to customise hostnames almost always?05:01
spivIf there were a portable way to get machine- (or boot-) specific unique info to add in, then great, but there isn't that I know of, so that's a can of worms.05:02
spivI don't really like the idea of being in the business of finding out MAC addresses or whatever.05:02
spivIf only "time at boot" was a portably available feature ;)05:03
spivpoolie: so I guess my thought is "if there's a config option to disable it and/or make it more conservative" then I'm totally comfortable05:05
spivWe have to balance this against the risk that users today don't understand how locks interact with smart servers05:05
poolieright05:06
spivSo the answer they give to break-lock (which bzr does suggest they run) is probably going to be wrong at least as often as your heuristic!05:06
poolieexactly05:06
poolieok, thanks for that05:06
pooliei'll just have a look at the pqm failure then05:06
spivOk, time to go grab a pie, bbiab.05:07
poolie:) enjoy05:07
spivpoolie: https://code.launchpad.net/~spiv/bzr/doc-stacking-constraints/+merge/6364007:16
pooliethanks!07:18
poolieunicode's elipsis character is not really all that well typeset07:20
spivDear unity: please unhide all the windows that were on workspace 307:20
poolieat least in monospace07:20
poolieok, replied07:21
poolieand rebooting again07:21
vilahi bazaaristas !07:30
jammorning all07:44
vilajam: hey !07:44
spivGood afternoon vila, jam07:45
jamhey poolie, sorry I missed you yesterday07:45
spivjam: would you mind taking a look at https://code.launchpad.net/~spiv/bzr/doc-stacking-constraints/+merge/63640?07:45
jamspiv: certainly07:46
jamanother way to describe the short rule07:46
jam"a repository must be able to generate a valid stream for revisions it claims are present, without having access to a backing repository"07:47
jamI'm not sure what is clearer07:47
jamI agree with vila that the short rule should be at the beginning of the document.07:47
spivGiven a sufficiently clear definition of "valid stream", of course :)07:48
jamspiv: your opening statement is actually slightly wrong07:48
jamthe actual requirement07:48
spivExcellent!07:48
jamis that if someone has X, and we have Y descended from X07:48
jamthen they can get everything for Y that they need from us07:48
spivAh yes.07:48
spivThat is what I was trying to say, but you're right I didn't quite hit the mark.07:49
jamthe idea of "complete stream" is that we can generate everything needed for Y *without* the backing repo07:49
spivRight.07:49
pooliehello jam, vila08:02
vila_o/08:02
vilaDoes anybody know the fullname of Geoff/xaav ?08:19
spivvila: see the committer in the bzr revisions08:24
spivWell, it's closer anyway :)08:24
vilahmm, I was wondering if it was a nickname or his true fullname :-/08:25
vilaI'd settle with Geoff/xaav in the news entry, if he disagrees we can fix it later08:26
=== jml` is now known as jml
jamspiv: do you want me to rewrite the text a bit, or are you working on it?08:59
spivjam: just done, and in fact sent to PQM08:59
spivjam: you're certainly welcome to polish that version even further if you think you can improve it :)09:00
jamspiv: sure, I just didn't want to be editing something concurrently09:00
spiv...and that's 6pm, so probably a good point to wind up.09:00
spivjam: just briefly before I go09:01
spivjam: I think GC's stream source is maybe not quite right when there are inventories with identical contents in the "interesting" and "uninteresting" sets09:02
jamspiv: it is possible09:02
jamwould take a bit of digging09:02
spivActually, hmm, this is probably a discussion to have a touch more time for09:02
jamI think I see your point (direct root inventories of the interesting set should be sent)09:02
spivRight09:03
spivAs an example, the current state of lp:libffi/debian/experimental; try fetching that into an empty repo09:03
MerwinCan someone tell what's the best way to know if a directory is a valid bzr repo ? Is there a command which return 0 or 1 ?09:03
spiv(and then try making a standalone branch of it...)09:03
jamMerwin: "bzr root" ?09:04
jamnot sure about the return code, though09:04
spivAnyway, I'll happily keep digging into that tomorrow09:04
Merwinjam: Thanks09:04
spivThe stacking invariant docs were written partly to make sure I had it clear in my head exactly what the requirements are.09:04
spivG'night folks09:05
vilaspiv: g'night09:05
=== hunger_ is now known as hunger
strycoreHi12:21
strycoreIs there any way to configure bzr so I can type bzr branch bzr+ssh://myserver/myproject instead of bzr+ssh://myserver/path/to/repo/myproject ?12:22
fullermdYou could look at the bookmarks plugin.12:25
fullermdOr create a symlink in your homedir and use /~/myproject/12:26
bigjoolsis there a way to uncommit a sub-commit inside a branch that I merge to my branch?12:27
fullermdYou can only uncommit off the top.12:27
bigjoolsyeah, as I thought :(12:28
fullermdRemoving a rev in the middle somewhere means you need to create new revs for everything after it.12:28
bigjoolswell it was at the top of the other branch I merged12:28
bigjoolsthen I did a bunch of conflict resolution, not realising, and now I have to re-do all that work :(12:29
fullermdDo you really need to eliminate it from the history, or is it OK to just create a new commit reversing it?12:30
bigjoolsI can't reverse it because my branch will eventually get merged back to the other one12:30
fullermdAh.  Yeah, then you're stuck with nothing to do but re-do the merge.12:31
bigjoolsmy day just gets better!12:31
maxbbigjools: So, you just want to have merged one less revision than you actually did?12:32
bigjoolsmaxb: pretty much, yeah12:33
maxbI'd probably do something like this12:33
maxb1. Uncommit the merge12:33
bigjoolsI could uncommit + shelve each12:34
maxb2. Forget the pending merge tip12:34
maxb3. Shelve the tree changes12:34
maxb4. Rerun the merge minus the unwanted revision12:34
maxb5. "bzr revert ." - revert the tree, but keep the pending merge tip12:34
maxb6. Unshelve the tree from 3.12:35
maxb7. Manually or with the aid of patch get rid of tree changes from the unwanted revision12:35
maxb8. Commi!12:35
maxb+t12:35
* vila nods12:35
vila9. Check that merge --preview <that branch with the unwanted revision> is what you expect12:36
bigjoolsright, I'll bash that in, thanks for the help!12:38
vilabigjools: you'll need bash-dwim for 7 :-/12:39
fullermdY'know, if you'd just integrate bash-dwim with the bug tracker on LP, it would save an awful lot of development effort.12:40
vilaThat's what I meant... :)12:43
bigjoolsI just snapped my fingers and it all worked like magic12:44
* vila sends black helicopters to capture fingers12:46
jamjelmer: it looks like your add-by-delta patch broke the case-insensitive code for windows.13:10
jamI'm not positive, but: http://babune.ladeuil.net:24842/job/selftest-windows/435/13:11
jamthat's what it looks like13:11
jamvila: the "test_branch_local_remote" doesn't fail here, the other 2 do13:11
jelmerjam: Ah, hmm. Thanks for letting me know, I'll have a look13:12
jelmerunless you're already looking into it?13:12
vilajam: fuzzy memory, but I think there are multiple tests failing with .pack files involved, some failures  may be transient ?13:14
jamvila: I'll see if I can provoke it13:15
jamI've also seen some things like that fail because it is a single CPU instance13:16
jambecause it changes how GIL contention works13:16
vilajam: also, #437 doesn't have this failure, so transient++13:16
jamvila: after 15 runs, no failures here13:16
jamvila: one problem with rename failures, is we don't know if it failed because of the target, or the source.13:17
jamI'm guessing source was still marked as open13:17
jam"sftp" is very suspcious13:17
jambecause of non-deterministic closure13:17
jamjelmer: also, I'd really like to work with you on barry's "is this branch up-to-date" command. Is it somewhere I can just poke at it myself?13:17
vilajam: did you query babune for a big/huge log file ? (couple of minutes ago ?) I saw a weird spike on disk accessees13:18
vilas/ee/e/13:18
jamvila: nothing more than opening that url and the linked urls.13:18
jamsome are modestly sized13:19
vilanah, just the tracebacks shouldn't explain that.... unless jenkins needs to load the whole log file to display them (and cache it then)13:20
spivstrycore: yes, or perhaps more accurately you can configure your sshd to do that:13:20
spivstrycore: http://doc.bazaar.canonical.com/bzr.dev/en/admin-guide/simple-setups.html#using-a-restricted-ssh-account-to-host-multiple-users-and-repositories http://doc.bazaar.canonical.com/bzr.dev/en/admin-guide/security.html#using-ssh13:22
strycorethanks fullermd and spiv :)13:40
jelmerjam: I was hoping to finish the bzr deployment to lp related fixes today; should we meet for some pair programming sometime this week?13:53
jamjelmer: sure. I think the lp stuff is most important for now14:37
maxbjubany Request: ./requeue_package.py python-unit python-werkzeug language-pack-az language-pack-gnome-uz # Transient failures15:21
=== maxb changed the topic of #bzr to: Bazaar version control <http://bazaar.canonical.com> | try https://answers.launchpad.net/bzr for more help | http://irclogs.ubuntu.com/ | Patch pilot: vila | UDD failure ratchet: 482
maxb(+1 for the mysterious cpuarrayd import, which isn't actually a problem since the package does not exist in Ubuntu or Debian)15:22
james_wmaxb, done15:27
maxbthanks15:27
james_wmaxb, cpuarrayd never existed, or just no longer exists15:28
james_w?15:28
maxbjames_w: Launchpad now claims it never existed15:28
maxbThough apparently it temporarily existed at some point15:29
maxbOr perhaps someone did  requeue --force on a bogus name?15:29
jimi_hendrixhello, i am using bazaar explorer to branch something, but i keep getting the following error: bzr: ERROR: Unsupported protocol for url15:30
james_wmaxb, yeah, that's certainly possible, I think there are a couple of odd package names in the db when I mistyped things15:31
maxbjimi_hendrix: Well... what is the url?15:31
jimi_hendrix lp:~snova/+junk/lyx15:32
jimi_hendrixmaxb, ^15:36
maxbhm15:41
maxbWell, I don't see anything wrong there, so you'll need someone who has actually used bzr-explorer, which I have not15:41
jimi_hendrixmaxb, going from the command line works16:07
jimi_hendrixdont know what was up16:07
vilajimi_hendrix: unsupported protocol for 'lp:' strongly hints at plugin disabling16:30
=== deryck is now known as deryck[lunch]
=== deryck[lunch] is now known as deryck
jamvila: if he is using bazaar explorer, he probably has plugins enabled, but maybe unselected "Launchpad" from being installed.18:31
vilajam: but he said the command-line was working...18:32
jamI missed that part. Definitely strange18:32
* gour notices that someone descended from the heaven here19:26
arnetheduckhi, I'm getting 207 failures when running the selftest on win7 64-bit py2.7 - is that normal or should I report it somewhere?19:38
james_warnetheduck, http://babune.ladeuil.net:24842/view/Windows/job/selftest-windows/lastCompletedBuild/testReport/ only sees two failures currently19:56
james_warnetheduck, so I would say yes19:57
james_was a bug I mean19:57
arnetheduckjames_w, I'm testing a fairly recent lp:bzr with no compiled extensions - maybe that makes a difference?20:22
=== jimi__hendrix is now known as jimi_hendrix
james_warnetheduck, I'm not sure20:26
james_wthe no compiled extensions thing may be involved20:26
=== yofel_ is now known as yofel
=== jelmer is now known as Guest3391
=== medberry is now known as med_out
pooliehi all23:03
mgzhey poolie.23:23
pooliehi mgz23:33

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