/srv/irclogs.ubuntu.com/2010/11/29/#bzr.txt

=== r0bby is now known as robbyoconnor
=== vednis is now known as mars
=== mlh_ is now known as mlh
=== jamesh_ is now known as jamesh
vilahello all !07:34
pooliehello vila07:40
vilapoolie: hi there !07:40
vilapoolie, spiv: Regarding the doc-new-config mp, thanks for the feedback !07:40
pooliehi there07:40
pooliethanks for posting it; sorry for the delay07:41
vilaI don't think it's ready to land in trunk, devnotes sounds more like it, but even there, I think more work is needed before landing, so I will reply to the points raised and put it in wip07:42
pooliewell, i think you should merge it to devnotes then07:42
pooliethere doesn't have to be any guarantee that files in that tree are finished or agreed-upon07:42
poolieand it makes them visible and shareable07:43
poolie(more so than being in just a random wip branch)07:43
vilagood point, I'll do that then07:44
MTecknologySo... somebody just asked me "How do I do bzr?"07:48
MTecknologyany link?07:49
vilaMTecknology: http://doc.bazaar.canonical.com/en/ ?07:49
vilaMTecknology: http://doc.bazaar.canonical.com/bzr.dev/en/tutorials/index.html ?07:49
MTecknologythanks :)07:50
poolievila, so on the sru07:50
vilapoolie: So, as maxb raised, on step forward two steps backwards for the Mricro Release Exception, we need testtools included in the main archive to be able to run the tests as part of the build07:50
vilapoolie: as you pointed out in your reply, this means running the tests externally07:51
vilapoolie: and making sure testtools is part of main for natty07:51
vilapoolie: jml said he doesn't care whether python-testtools is part of main or universe, I've started looking at what is needed to get it in main (hopefully not much)07:53
vilahttps://wiki.ubuntu.com/MainInclusionProcess is the relevant page AIUI07:53
poolieok07:55
vila From https://wiki.ubuntu.com/UbuntuMainInclusionRequirements, I think this shouldn't cause any problems07:55
pooliemeant to do it today; didn't07:55
vila?07:55
vila*I* meant to do it Friday but couldn't finish ;)07:55
vilawell, I didn't get farer than reading the above pages really07:56
lifelessvila: farther07:59
vilalifeless: haaaa, but of course !08:01
poolie*further*08:01
poolieor not?08:02
vilameh08:02
poolieapparently yes, but only barely: http://englishplus.com/grammar/00000213.htm08:02
vilaI meant: I've started, there is more to do, but I lacked time to continue08:03
poolieright, that's what i understood :)08:04
vilaso literally I think it's farther, but the English usage is probably further, thanks to both of you anyway ;)08:05
spm"farer" that's perfect! it even makes sense following the insane rules of english.08:05
pooliei think i'll just send a brief note to tb and see what they say08:05
vilapoolie: ok, can you CC me ?08:06
pooliei will08:08
lifelesspoolie: heh, whoops.08:09
lifelesspoolie: I've finally logged into netbank and wired you that stuff08:09
pooliethanks08:11
poolievila, maxb: just so i don't embarrass myself, it is correct that the test suite is now clean both during a build and from the installed package08:19
pooliein 2.2.208:19
vilaI haven't checked recently, but that's my understanding08:19
vilaIf that's not the case, it should be fixed08:20
poolievila: sent; we'll see08:55
vilaok08:56
vilapoolie: maverick slave upgraded to 2.2.2, running the test suite there to confirm08:58
poolieok, good night vila09:05
vilahehe, good night to you ;)09:06
lifelesspoolie: http://blog.benstrong.com/2010/11/google-and-microsoft-cheat-on-slow.html09:10
poolienice09:13
poolie"Google.... decided the best way to make forward progress was to just turn it on and see whether the internet actually melts down or not"09:13
poolie:)09:13
fullermdWhich do they consider success?   :p09:16
=== cody-somerville_ is now known as cody-somerville
=== Odd_Blok1 is now known as Odd_Bloke
=== Ursinha-` is now known as Ursinha
=== Ursinha is now known as Ursinha-afk
=== Ursinha-afk is now known as Ursinha
=== Ursinha is now known as Guest51647
=== Guest51647 is now known as Ursinha-afk
=== Ursinha-afk is now known as Guest17956
=== Guest17956 is now known as Ursinha
=== beuno_ is now known as beuno
=== mbarnett` is now known as mbarnett
=== bac` is now known as bac
vilajelmer: ping15:22
jelmervila: hey15:23
vilajelmer: I tried to upgrade lp:~bzr-core/bzr/devnotes which is still in format knitpack6 (bzr 1.9) but it failed because it's still stacked on the old trunk15:24
vilathere is now a backup.bzr.~1~ there with the previous content15:24
vilajelmer: is there a way for me to either restore that and re-stack on the new trunk and upgrade or do I need someone powerful hand behind the scenes ?15:25
jelmervila: It should be possible to use hitchhiker to move the old backup directory and manually fix the stacked-on branch using hitchhiker as well15:26
vilajelmer: ha right, made a typo with lftp15:27
vilaand got a misleading Access failed: Permission denied: "Cannot create '.bzr-broken'. Only Bazaar branches are allowed.15:28
jelmerthere are particular file names that are allowed15:29
jelmerI think backup.bzr* is allowed15:29
jelmeras well as .bzr15:29
vilayeah, the typo was backup.bzr~2~ instead of backup.bzr.~2~ after .bzr-broken was refused15:30
vilaso the last period is mandatory15:30
=== weigon__ is now known as weigon
=== jam1 is now known as jam
vilajelmer: I had to upload a locally patched branch.conf to update the stacked-on repo :-/ After the upgrade failed successfully 8-/15:49
jelmervila: \o/15:49
jelmervila: This is too hard for somebody not familiar with the internals though :-/15:49
vilajelmer: yeah, filing a bug asking for --stacked-on parameter for upgrade15:50
vilajelmer: exactly my point15:50
=== rockstar` is now known as rockstar
=== beuno is now known as beuno-lunch
jammorning vila and jelmer16:28
vilahey jam 116:28
vilahow was the turkey ?16:28
jampretty good16:28
jelmerhey John16:28
jamfun to be around my family16:28
=== Ursinha is now known as Ursinha-afk
maxbjelmer: hey. Got a moment to talk about how to run tests on a buildd and the 2.2.2 SRU?16:35
jelmermaxb: sure16:35
maxbThe thing is, the 2.2.2 SRU as is doesn't pass the tests16:35
maxbThe problem is the tests in 2.2 fail if they are run in a directory containing setup.py and run as root16:35
jelmermaxb: I don't think we should be introducing the change to run the tests in a SRU16:35
vilamaxb: which ones ?16:35
jelmermaxb: I fixed the setup.py test a week or two ago in bzr.dev.16:36
maxbThe one which tests 'setup.py install', and tries to write to /usr/share/apport/16:36
maxbThis is not a problem in bzr.dev because I ripped out the apport installation from setup.py there with poolie's blessing16:36
jelmermaxb: Why did you remove the apport installation?16:37
maxbI can dig up the MP, but the summary is "This is never the right thing to do - configuring apport is something for distros to do."16:38
vilamaxb: I think this test should be skipped if run by root, sounds far too dangerous anyway16:38
maxbhttps://code.launchpad.net/~maxb/bzr/no-install-apport/+merge/3846316:39
jelmermaxb: Ah, ok. That's a reasonable approach (though it'd mean we'd have to patch bzr in Ubuntu)16:39
maxbvila: To be honest, I'm rather confused why this test is considered valuable at all16:39
jelmermaxb: Making sure that "setup.py install" works seems like a nice thing, it's broken in the past.16:40
vilamaxb: catching up regressions16:40
maxbjelmer: The interesting fact to note is that the old apport installation code does *not* install the apport hooks in the bzr ubuntu package :-)16:40
jelmermaxb: https://code.launchpad.net/~jelmer/bzr/setup.py-root/+merge/4006716:40
maxbOh, I get it now, you want to catch setup.py install failures in PQM16:40
vilamaxb: which is why eager tests are bad :(16:40
jelmermaxb: But I guess that's been obsoleted by your change.16:40
vilamaxb: I ran http://babune.ladeuil.net:24842/job/selftest-maverick/ this morning, but not as root, is it the only test failing ?16:42
maxb--root is more technically correct anyway16:42
maxbvila: checking for my ppa build log...16:42
vilameh, wrong url, the correct one is: http://babune.ladeuil.net:24842/job/selftest-maverick-proposed/16:43
maxbhttps://code.launchpad.net/~maxb/+archive/ppa/+build/206415016:43
vilamaxb: so I used the bzr from the bzr/proposed ppa16:43
maxbThat buildlog shows just the one failure16:43
maxbOh, you are testing the run-tests-when-installed part of the puzzle, I am focussing on the run-tests-on-buildd part of the puzzle16:44
vilamaxb: yes16:45
vilamaxb: my understanding was that we couldn't use python-testtools during the build so I reverted to the manual check16:46
vilaoh, so you activate the tests in your private ppa (was wondering where I got my bzr-2.2.2 suddenly ;)16:47
maxbvila: I'm testing in ~maxb because ~bzr has a newer testtools than the primary archive, so wouldn't be a realistic test16:54
maxbAlso, I am running the tests in ~bzr, but with some tweaks to how they are invoked in debian/rules, which I haven't managed to convince jelmer of the rightness of for Debian&Ubuntu yet.16:56
=== beuno-lunch is now known as beuno
=== oubiwann is now known as oubiwann_
=== oubiwann_ is now known as oubiwann
=== oubiwann is now known as oubiwann_
bzrHi--I'm having some trouble with pushing from bzr explorer.  Is this the right place to be?19:44
bzrIs anyone here?19:58
jelmerbzr: hi20:06
bzrHi!20:06
jelmerbzr: I'm afraid I don't really have much experience with bzr-explorer. What's the problem?20:06
bzrI seem to have set my username wrong--I'm George from that tricky bzr push bug.20:06
bzrWhen I try to push, I get:20:07
bzrRun command: bzr push20:07
bzrUsing saved push location: https://george@nanotech.com@pl3.projectlocker.com/nano/www/svn20:07
bzrbzr: ERROR: Please upgrade your Subversion client libraries to 1.5 or higher to be able to commit with Subversion mapping v4 (current version is (1, 4, 4, ''))20:07
bzr(The bug was https://bugs.launchpad.net/bzr/+bug/681285?comments=all)20:07
ubot5Launchpad bug 681285 in Bazaar "Can't push my changes in Bazaar (affected: 1, heat: 6)" [Undecided,Incomplete]20:07
jelmerbzr: you're using bzr-svn trunk?20:08
bzrI think so.20:08
bzrIs that:20:09
bzrsvn 1.0.320:09
jelmeryour copy of subvertpy was linked against an old version of libsvn20:09
bzr   Support for Subversion branches20:09
bzr   /Library/Python/2.5/site-packages/bzrlib/plugins/svn20:09
bzrHow do I fix that?20:09
bzrI tried rebuilding bzr using MacPorts, but that didn't work at all...20:09
jelmerbzr: you can either recompile subvertpy against a newer libsvn or install bzr from another source20:09
bzrCan I recompile just subvertpy using MacPorts?  Or is there another way to do that?20:10
bzrWhat other sources can I use to install bzr?20:10
jelmerbzr: I'm not sure (I've never really used a Mac)20:10
bzrHm.20:11
jelmerbzr: I think the other alternative is the installer on the bzr site20:11
Takmacports is a quick path to brokenness20:11
dashnah20:11
bzrI used the installer from the bzr site.20:11
bzrThis one:20:11
bzrhttp://edge.launchpad.net/bzr/2.2/2.2.1/+download/Bazaar-2.2.1-OSX-10.5-1.dmg20:11
bzrRight?20:11
dashyeah you can't use the installer if you want to use macports stuff20:11
bzrI've also tried: http://launchpad.net/bzr/2.2/2.2.0/+download/Bazaar-2.2.0-OSX-10.5-1.dmg20:13
bzrShouldn't those have a more up-to-date svn version?20:14
bzrDo I want to try: http://launchpad.net/bzr/2.3/2.3b3/+download/Bazaar-2.3b3-OSX-10.5-1.dmg20:14
bzr?20:14
jelmerI've been using 2.3 for quite some time without problems20:15
bzrOkay, I guess I'll try that then...20:16
bzrIs it possibly that I'm on OS X 10.5?20:17
bzrSame error on bzr 2.3b3.20:23
pooliehi all20:24
pooliehm, that's confusing :)20:24
bzrRun command: bzr push20:24
bzrbzr: ERROR: Please upgrade your Subversion client libraries to 1.5 or higher to be able to commit with Subversion mapping v4 (current version is (1, 4, 4, ''))20:24
jelmer'morning poolie20:24
bzrHi poolie.20:24
bzrI just tried downloading and installing the py26-subvertpy via MacPorts.  Same error.20:27
jelmerbzr: I'm not sure what's going on there. It could be that you end up using the system svn libraries or something like that20:27
bzrMy system svn claims to be 1.6.9.20:28
maxbbzr: Perhaps you could first confirm where this Subversion 1.4.4 installation is - the system one? Something else?20:28
bzr(from svn help)20:28
bzrIt's not the system one.20:28
bzrI really don't know where it is.20:28
bzrIs there any way to get bzr to tell me where it's getting its svn?20:29
pooliebzr set 'BZR_PDB=1' in the environment20:36
pooliethen when it/if it crashes, type 'pp sys.modules()'20:36
=== bzr_ is now known as bzr
bzrWhere do I type pp sys.modules()?  And will it work if bzr doesn't crash?20:38
bzrIt just fails with:20:40
bzrRun command: bzr push20:40
bzrUsing saved push location: https://george@nanotech.com@pl3.projectlocker.com/nano/www/svn20:40
bzrbzr: ERROR: Please upgrade your Subversion client libraries to 1.5 or higher to be able to commit with Subversion mapping v4 (current version is (1, 4, 4, ''))20:40
maxbIf it does not crash, you will not get the prompt at which you would type the pp command20:40
bzrHm.20:40
bzrIs there a way to get it to crash?20:40
maxbbzr: OK, so I have checked the bzr-svn source code, and the 1.4.4 being reported is the version of Subversion that the subvertpy python extension was compiled against20:41
bzrThanks.20:41
bzrSo...I need to upgrade subvertpy?20:42
bzrShouldn't updating subvertpy via MacPorts have worked?20:42
maxbI have zero Mac knowledge20:42
maxbBut certainly, you do need to rebuild subvertpy against a newer subversion20:43
bzrWho would know how to do that?20:45
maxbI have to go now, sorry.20:48
=== oubiwann_ is now known as oubiwann
bzrI have to go too.  More anon.  Thanks!20:51
rootarthello to all21:30
rootartI have a question about the bzr hooks and signals, how we can check on server side that new branch is created?21:31
rootartI found this hook post_branch_init but I'm not very familar with API so, can someone suggest how to work with this ?21:32
spivrootart: have you seen http://doc.bazaar.canonical.com/development/en/user-guide/hooks.html ?22:39
spivrootart: the object passed to the hook is http://people.canonical.com/~mwh/bzrlibapi/bzrlib.branch.BranchInitHookParams.html22:41
rootartspiv: yes, I saw that, for now I think I can get the action, but now I have over one, I have a repository 'repo', I want create a branch 'b1', I am getting the new one branch object, but how can I know what repository this branch is a copy of ?22:42
rootartspiv: thanks again, that is done I think22:42
rootartspiv: now have only this last one question22:42
spivrootart: if you have a branch object, the repository is 'your_branch.repository'22:49
pooliehi maxb, spiv, jelmer23:35
dOxxxevening23:40
mgz...if I try and delete the bug watch from bug 682600 I get OOPS-1794O230923:54
ubot5Launchpad bug 682600 in Bazaar "Fix RandomPool Depreciation Warning from pycrypto (affected: 2, heat: 262)" [High,Confirmed] https://launchpad.net/bugs/68260023:54
ubot5https://lp-oops.canonical.com/oops.py/?oopsid=1794O230923:54

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