[00:07] <cinerama> poolie says he'
[00:08] <cinerama> whoops, poolie says he'll be back in a little while -- just out running some errands
[02:53] <sagaci> hi, trying to push a branch to lp, getting the error "bzr: ERROR: Connection error: while sending POST /bazaar/: [Errno 8] _ssl.c:499: EOF occurred in violation of protocol"... I'll admit that I'm on a kinda dodgy 3G connection but it was fine this morning, any ideas or just try to push it via a wired connection?
[02:56] <lifeless> looks like an ssl problem
[02:56] <lifeless> e.g. yes your 3g connection ;)
[02:58] <sagaci> righteo then
[03:05] <spiv> sagaci: the bzr 2.4 betas will avoid that problem (they don't use the XML-RPC interface to resolve lp: URLs)
[03:17] <benonsoftware> Question: What does UDD mean?
[03:18] <bob2> ubuntu distributed development
[03:19] <benonsoftware> But what about UDD failures?
[03:20] <bob2> bzr import failures I assume
[03:21] <benonsoftware> Thanks
[03:21] <benonsoftware> Is loggerhead a plugin?
[03:22] <poolie> benonsoftware, hello, are you having trouble with udd packaging branches or something?
[03:22] <poolie> or just curious about the titles?
[03:22] <poolie> s//topic
[03:22] <benonsoftware> Just wondering :)
[03:22] <poolie> package-import.ubuntu.com
[03:22] <benonsoftware> Do you know if loggerhead is a plugin poolie ?
[03:23] <poolie> it is
[03:25] <benonsoftware> So do I need to extract it and just place it in the plugins folder?
[03:29] <benonsoftware> Do I need a web server for it poolie ?
[03:34] <poolie> you can either run it stand alone or inside apache
[03:34] <poolie> there are some docs in readme
[03:34] <poolie> (or any other wsgi web server)
[03:34] <poolie> biba
[03:35] <benonsoftware> poolie: Can I just run it without any other software for it?
[03:46] <spiv> benonsoftware: it has a few dependencies apart from bzrlib:
[03:46] <spiv> benonsoftware: https://bazaar.launchpad.net/+branch/loggerhead/view/head:/docs/index.rst
[03:54] <benonsoftware> Thanks. Does bzrlib come with bzr windows?
[03:57] <spiv> It does, but I'm not sure if the windows installer provides it in a way that makes it readily accessible as a library for other projects.
[03:58] <spiv> IIRC there's probably .zip file installed by the windows installer you can add to your PYTHONPATH that would make it available.
[06:00] <vila> hi all !
[06:03] <poolie> hi vila, jelmer, jam,
[06:04] <vila> jelmer is in vacations AIUI
[06:06] <poolie> oh he is too
[06:26] <fullermd> Vacation?  How do I get me one of those?
[06:30] <vila> fullermd: *you* can't :-p
[06:42] <jam> morning all
[06:43] <jam> fullermd: I believe the line is "no rest for the wicked"
[06:43] <jam> hi poolie, You scheduled the meeting for 6UTC, but I think we actually agreed on 7UTC
[06:45] <poolie> hi jam, want to join us?
[06:45] <poolie> mm when i scheduled it it wasn't super clear which time it was actually going to be
[06:46] <jam> sure. just 6UTC is before I take my son to school
[06:46] <jam> I thought we wanted to move it by 1hr, not 2
[06:48] <poolie> i'm not sure if the calendar captured my intention
[06:54] <fullermd> Wicked?  Me?  Why, I never...
[07:09] <AfC> james_w: are you still interested in / working on bzr builddeb?
[07:09] <AfC> [or is someone else looking after it now?]
[07:09] <spiv> Quite a few folks are poking at it regularly I think.
[07:10] <spiv> I made a branch for it just yesterday :)
[07:10] <AfC> spiv: Ok, I'll ask generally, then :)
[07:10] <AfC> Query 1: the docs for bzr import-upstream make it seem less suited that merge-upstream for starting a new package. Am I right about that?
[07:12] <AfC> Query 2: the docs for bzr-builddeb's "normal mode" #creating a new package recommends using merge-upstream, which then talks about being able to import farious .tar formats, "or a directory". Should that work [when starting from scratch?]
[07:12] <AfC> (it doesn't)
[07:12] <AfC> Query 3: would you have expected that
[07:13] <AfC> $ bzr merge-upstream ~/path/to/file.zip --version 1.0 --distribution debian --package name
[07:13] <AfC> (or ~path/to/unpacked/)
[07:13] <AfC> would fail, whereas
[07:13] <AfC> $ bzr dh-make --bzr-only name 1.0 ~/path/to/file.zip
[07:14] <AfC> appears to work just fine? (creating a commit tagged 'upstream-1.0')
[07:14] <AfC> Hm. That's just about a bug report, once someone tells me which the bug is.
[07:14] <AfC> s/fail/apparently do nothing including not committing anything/
[07:15] <AfC> [around here fail means stack trace]
[07:16] <poolie> hi afc
[07:17]  * AfC advances his regards poolie's way
[07:23] <poolie> what's the context where you're running merge-upstream?
[07:23] <poolie> an empty branch?
[07:23] <poolie> that seems like it should be reported as a bug anyhow
[07:26] <poolie> afc, to start a new package i would think you'd do import-upstream and then commit on top of that
[07:26] <poolie> i wonder if it's sufficiently documented
[07:35]  * maxb lols at pkg-bazaar-maint receiving spam selling pipes and looms :-)
[07:36] <poolie> i get a lot of spam about pools and spas
[07:36] <fullermd> I don't get any spam about bleaching clothes   :(
[08:07] <mrevell> ing
[08:18] <AfC> poolie: yes, an empty branch
[08:18]  * AfC tries again
[08:19] <AfC> ah. Well at least part of the problem is that `bzr dh_make --bzr-onle` groks a .zip upstream, whereas `bzr import-upstream does not.
[08:24] <AfC> So I should report this, obviously. Any preference for a bug title?
[08:40] <vila> AfC: No preference. Generally if/when I think the title is misleading, I just fix it once I get a better understanding of the bug. I don't necessarily have this understanding when I file one...
[09:02] <sagaci> hi, i'm wanting to branch ubuntu-docs, being bzr branch lp:ubuntu-docs... is there an argument to check how big the download will be without actually downloading the branch
[09:11] <vila> sagaci: no *precise* way (as in number of bytes), but 'bzr info -v lp:ubuntu-docs' should give you some hint
[09:12] <sagaci> thanks vila
[09:12] <vila> sagaci: just did 'bzr branch lp:ubuntu-docs' and it's ~8M on disk so it should be roughly the same download size
[09:13] <vila> err, scratch that, actually it downloaded ~2M, the 8M includes the working tree
[09:42] <AuroraBorealis> bazaar explorer says "unable to obtain lock file: c:\users\<username>\AppData\Roaming\bazaar\2.0\lock
[09:43] <AuroraBorealis> ive deleted that file but it still keeps coming back and freezing the program
[11:15] <spiv> Gar, the branch for bug 248418 has caused bug 806425.
[11:16] <spiv> It's well past EOD for me, but if someone's interested it might be good to look into it and possibly revert the offending change.
[11:34] <fullermd> Rrr.  The error on pull'ing from a non-branch-root is annoying.  Have I moaned about that before?
[12:10] <Lo-lan-do> Hi all
[12:15] <AuroraBorealis> can anyone please help me with this annoying bzr explorer bug =(
[12:15] <AuroraBorealis> i dont know what its doing with this lock file
[15:07] <JamesTait> Hello people.
[15:07] <JamesTait> Can anyone suggest how I might recover from "bzr: ERROR: The dirstate file (DirState(u'/home/jtait/[snipped]/.bzr/checkout/dirstate')) appears to be corrupt: Bad parse, we expected to end on \n, not: 1" ?
[20:18] <poolie> hi all
[21:02] <poolie> hi abentley
[21:03] <abentley> poolie: hi.
[21:03] <poolie> is your mp essentially saying "no, there are no reasons to want to take the other root?"
[21:04] <abentley> poolie: no, I'm just accepting that it's a less-disruptive change and doesn't expose several of our UI issues.
[21:05] <abentley> poolie: It's restoring the status quo.
[21:05] <poolie> right
[21:05] <poolie> i guess i just wonder if we should try again at making that switch, perhaps by a different course
[21:06] <abentley> poolie: If a user really wants it, they can just merge in the opposite direction, so the priority is pretty low, and several changes would need to be made.
[21:08] <poolie> ok