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

=== zyga is now known as zyga-afk
=== medberry is now known as med_out
=== AfC1 is now known as AfC
bignosennnggg06:12
bignose$ bzr update06:12
bignoseTree is up to date at revision 3418 of branch svn+ssh://benf@subversion/home/svn/empowered/trunk06:12
bignose$ bzr commit06:12
bignosebzr: ERROR: Bound branch BzrBranch7(file:///home/benf/projects/svn/empowered/) is out of date with master branch SvnBranch('svn+ssh://benf@subversion/home/svn/empowered/trunk').06:12
bignoseTo commit to master branch, run update and then commit.06:12
spivThat's weird.  It sounds a bit familiar though, perhaps someone else will recognise the bug.06:13
vila>-/ unbind/bind ?06:23
vilamakes no sense06:23
bignoseokay, it appears to be related to::06:26
bignose$ bzr merge --revision 1823 ../../devel/empowered.rt12430.confirm-reminder-email/06:26
bignoseinconsistent details in skipped record: StaticTuple('719@58802371-0b19-4c69-acb7-7d0c5b422186:trunk%2Fwdyt%2Fsource%2Fwdyt%2Fprofile_modules%2Fmanagement%2Fcommands%2Fsend_profile_reminders.py', 'ben@benfinney.id.au-20110701043735-hyhpvogab661xpcz') ('4721568 342529 114092 114205', ((('719@58802371-0b19-4c69-acb7-7d0c5b422186:trunk%2Fwdyt%2Fsource%2Fwdyt%2Fprofile_modules%2Fmanagement%2Fcommands%2Fsend_profile_reminders.py', 'svn-v4:5880237106:26
bignose M  wdyt/source/wdyt/reminder/tests/test_reminder.py06:26
bignoseAll changes applied successfully.06:26
vilabignose: as in: you're out of trouble but this is worth filing a bug ?06:33
bignosevila: as in, that's the consistent message that precedes the failure.06:37
bignoseI'm madly trying to merge these branches06:37
bignoseand it fails with that message06:38
vilawhat fails ? 'All changes applied successfully' does not sound like a failure (which is confusing)06:39
bignoseor rather that message precedes the “ERROR: Bound branch BzrBranch7(file:///home/benf/projects/svn/empowered/) is out of date with master branch” message when I try to make a change06:39
bignosethe sequence is: merge, get that “inconsistent details” message, then try to commit → ERROR06:39
vilawhich versions of bzr / bzr-svn are you using ?06:40
bignose$ bzr version06:41
bignoseBazaar (bzr) 2.2.406:41
vilahmpf06:41
bignose(from Ubuntu Maverick)06:42
bignosebzr-svn 1.0.3-106:42
vila2.3.3 / 1.0.4 are available from the stable ppa, that would be my first line of defense06:43
bignoseI'm not in a position to update this machine06:44
bignoseor install packages06:44
vilaI don't know the details but I know jelmer did a bunch of fixes (and he is out this week)06:44
vilahmm06:44
vilano other machine available to try ?06:44
bignosewhat should I try, though?06:44
vilasame commands with upgraded bzr / bzr-svn06:45
bignoseyou're aware that I've reported problems with bzr-svn this week, that others here have said are repository corruption?06:45
vilaif you can't upgrade it will be rather complicated to even get a fix (if it's not a known bug) :-/06:45
bignoseso I am trying to keep straight what's happened to each repository06:45
vilahmm, no I wasn't :-(06:45
vilairc is not a reliable medium when it comes to tracking bugs...06:46
bignoseno, I ended up reporting it to the mailing list06:46
vilahuh ? Did I miss that one ? ....06:48
vilaoh06:48
vilaCrash in ‘bzr-svn’, but works with Subversion ?06:48
bignosethat's the one06:48
bignosenow I appear to be reaping the repository corruption, trying to merge my work from earlier this week06:49
vilayou mentioned bzr-2.2.1, you did upgrade since then ?06:49
bignosehow the heck can I get my work properly into the Subversion repository?06:49
vilasee above, jelmer being away this week, I'll try with recent versions first, I know there have been fixes related to statictuple stuff but nothing more detailed :-/06:52
bignosevila: using bzr 2.3.1-1, bzr-svn 1.0.5dev07:16
bignoseI get a crash trying to merge07:16
bignoseFile "/usr/lib/python2.6/dist-packages/bzrlib/repofmt/pack_repo.py", line 2171, in _commit_write_group "Cannot add revision(s) to repository: " + problems_summary)07:17
bignoseBzrCheckError: Internal check failed: Cannot add revision(s) to repository: missing referenced chk root keys: [StaticTuple(…07:17
vila>-/07:17
vilabignose: can you pastebin a bit more details so I can paste it to the bug report ?07:18
bialixhi all07:19
bialixjam: hi07:19
vilabignose: missing chk root keys though... May be that can be worked around by pulling the right revisions in the right repo (if we can understand where they are missing that is...)07:20
bialixbonjour vila07:20
vilabialix: hi hi sir07:20
bialixvila: after the latest team changes initiated by maxb I left ~bzr and moed to ~bzr-core. But I didn't realize that bzr-windows-installer project maintained by ~bzr.07:22
bignosevila: <URL:http://paste.pound-python.org/show/9056/>07:23
jammorning all07:23
bialixso I can't land https://code.launchpad.net/~bialix/bzr-windows-installers/changelog_plugin/+merge/6676007:23
bialixhi jam07:23
bignosevila: thanks for the help so far07:23
maxbhuh. If anything my changes were to enable people to move from ~bzr-core to ~bzr07:23
bignoseI have to go now07:23
bialixmaxb: I don't blame you07:23
maxbbialix: I'm just confused why you chose to do that move07:24
bialixit was my mistake, I guess07:24
bialixmaxb: because of Olive07:24
bialixanyway all Bazaar projects are too big for me07:24
bialixbzr-core, qbzr, explorer and windows-installers -- those are areas of my expertise07:25
vilabignose: bug updated07:25
bignosevila: appreciated, thanks07:25
bialixjam: may I ask you to look and merge before 2.4 final this patch, please: https://code.launchpad.net/~bialix/bzr-windows-installers/changelog_plugin/+merge/6676007:25
vilajam: hello patch pilot ;-)07:25
bialixvila: topic/07:26
maxbbialix: ~bzr doesn't get any email about Olive07:26
bialixmaxb: it did some07:26
maxbyeah, that was quicly reverted07:27
bialixI was quicker07:27
* bialix is looking for jriddell07:27
maxbI think it's time for me to shout a bit more about my refactoring bugmail thread07:34
maxbThe only tricky thing is that to get ~bzr down to receiving no more bugmail than ~bzr-core, we also need to remove structural subscriptions from:07:35
maxb~bzr-gtk ~bzr-hg ~bzr-upload-devs ~qbzr-bugs07:35
maxbhmm, perhaps I should wait for a time when jelmer isn't away to propose this07:38
=== hunger_ is now known as hunger
=== zyga-afk is now known as zyga
vilaYES ! Today is a good day :-D09:07
vila1) My daughter got her baccalaureat09:08
vila2) bug #805809 is almost dead09:08
ubot5Launchpad bug 805809 in Bazaar "merge fails with NoFinalPath" [High,In progress] https://launchpad.net/bugs/80580909:08
jamvila: btw, we decided that the stand-up tomorrow would be at 9am local time, right? Not 8am?09:11
vilajam: yup, poolie send an invitation update09:12
vilasent09:12
maxboooh09:21
vilamaxb: recognize the 31 failures ?09:21
maxb805809 might make you a hero of udd09:21
vilamaxb: just so you know (and because I didn't explain all the gory details in the bug nor the mp): this is partly due to debian and ubuntu branches having different root-ids09:22
maxburgh09:22
vilathis is quite messy as lenny branches tend to have the same root-ids as the ubuntu branches but not always09:22
vilaprobably lots of of merge -r0..nnn involved09:23
vilai.e. despite having different root-ids, a lot of file-ids are still common and even revids...09:23
maxbwe may want to throw away and reimport some09:23
vilamaxb: I thought a bit about that but that doesn't seem required (at least it's *not* required with this fix)09:24
vilahaving different root-ids for upstream, debian, ubuntu branches is a use case we want to support09:25
vilahacing different root-ids among debian branches (or ubuntu branches) is a bit more weird but still conceivable09:26
vilamaxb: note that *this* bug is occurring when generating the ubuntu merges which we don't use (yet) so a related fix for udd *may* be to ~ignore them09:27
vilaat least, this shouldn't block pushing to the lp packaging branches (and may be it doesn't already)09:28
vilaghaa, retry:09:28
vilamaxb: I think the importer is pushing to lp and *then* failing to generate the ubuntu merges so these 31 failures are not blocking09:29
vilamaxb: does that sound right ?09:29
maxbThey are blocking09:36
vilarats09:36
maxbThey were not blocking the first time it failed, but for every subsequent upload, the importer tries to finish off the push/merge stuff before importing anything new09:37
vilaratsss09:37
vilahmm09:37
maxbWe may need to destroy and reimport these ubuntu branches anyway09:40
maxbWe have several bugs filed by people who are finding out the hard way that bzr's merge behaviour is unhelpful when parallel imports happen09:41
vilamaxb: my next target is to address parallel import in a very restricted way but still valid for udd (i.e. we damn well know the paths are the same even when the file-ids differ)09:58
vilamaxb: I'm unclear about how the branches are created anyway and how we can ensure all packaging branches use the same root-id and even if we achieve that we may still encounter issues if upstream use yet another one (which is a valid use case)09:59
vilamaxb: but I won't object about reimporting the branches if it helps (I'm not sure all cases will be addressed with that though)10:00
maxbYes, I definitely agree that reimports will never solve the larger issue.10:01
maxbThere may be places where they are an expedient solution though10:01
* vila nods vigorously10:01
vilawhy is 2.3.3 still in natty-proposed ?10:14
maxbNo one has verified any of the bugs, apparently10:15
maxbhttp://people.canonical.com/~ubuntu-archive/pending-sru.html10:16
maxbAlso, wasn't there discussion of a potential regression?10:16
vilado we need that even with MRE ?10:16
vilaoh, which one ?10:17
vila2.3.4 is planned for 13 July...10:18
maxbbug 79868810:18
ubot5Launchpad bug 798688 in bzr (Ubuntu) "possible regression in natty-proposed" [Undecided,Incomplete] https://launchpad.net/bugs/79868810:18
vila<shudder> final slashes and ~/%7E ... madness10:21
* vila off for lunch10:23
=== zyga is now known as zyga-food
=== zyga-food is now known as zyga
ScottKI have a directory in a bzr branch that I want to move to a different project (no common history).  How do I do that without losing the history for the files I'm moving?14:07
LarstiQScottK: this may not be the recommended way, but you could split and join. Drawback is that you carry all of the other history along.14:36
ScottKThis is a tiny piece of the overall project it's leaving, so that would be a bit daunting.14:37
ScottKThanks.14:37
LarstiQScottK: perhaps with fastexport and filtering inbetween?14:39
ScottKPerhaps.  I'll look into it.14:39
=== deryck is now known as deryck[lunch]
=== beuno is now known as beuno-lunch
lvhHi. Is there an easy way to find the point where the current branch branched off from its parent branch?17:00
=== deryck[lunch] is now known as deryck
maxblvh: It's not quite what you asked for, but there is "bzr find-merge-base BRANCH OTHERBRANCH"17:22
=== med_out is now known as medberry
=== sidnei is now known as sidnei-away
=== beuno-lunch is now known as beuno
ChrisCauserHello #bzr18:50
ChrisCauserIs there anyone out there who can help me with a spot of trouble I'm having with bzr 2.4?18:50
=== yofel_ is now known as yofel
=== medberry is now known as med_out

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