=== cinerama_ is now known as cinerama [00:07] poolie says he' [00:08] whoops, poolie says he'll be back in a little while -- just out running some errands === poolie_ is now known as poolie [02:53] 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] looks like an ssl problem [02:56] e.g. yes your 3g connection ;) [02:58] righteo then [03:05] sagaci: the bzr 2.4 betas will avoid that problem (they don't use the XML-RPC interface to resolve lp: URLs) [03:17] Question: What does UDD mean? [03:18] ubuntu distributed development [03:19] But what about UDD failures? [03:20] bzr import failures I assume [03:21] Thanks [03:21] Is loggerhead a plugin? [03:22] benonsoftware, hello, are you having trouble with udd packaging branches or something? [03:22] or just curious about the titles? [03:22] s//topic [03:22] Just wondering :) [03:22] package-import.ubuntu.com [03:22] Do you know if loggerhead is a plugin poolie ? [03:23] it is [03:25] So do I need to extract it and just place it in the plugins folder? [03:29] Do I need a web server for it poolie ? [03:34] you can either run it stand alone or inside apache [03:34] there are some docs in readme [03:34] (or any other wsgi web server) [03:34] biba [03:35] poolie: Can I just run it without any other software for it? [03:46] benonsoftware: it has a few dependencies apart from bzrlib: [03:46] benonsoftware: https://bazaar.launchpad.net/+branch/loggerhead/view/head:/docs/index.rst [03:54] Thanks. Does bzrlib come with bzr windows? [03:57] 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] IIRC there's probably .zip file installed by the windows installer you can add to your PYTHONPATH that would make it available. [06:00] hi all ! [06:03] hi vila, jelmer, jam, [06:04] jelmer is in vacations AIUI [06:06] oh he is too [06:26] Vacation? How do I get me one of those? === poolie changed the topic of #bzr to: Bazaar version control | try https://answers.launchpad.net/bzr for more help | http://irclogs.ubuntu.com/ | Patch pilot: jam | UDD failures: 400 [06:30] fullermd: *you* can't :-p [06:42] morning all [06:43] fullermd: I believe the line is "no rest for the wicked" [06:43] hi poolie, You scheduled the meeting for 6UTC, but I think we actually agreed on 7UTC [06:45] hi jam, want to join us? [06:45] mm when i scheduled it it wasn't super clear which time it was actually going to be [06:46] sure. just 6UTC is before I take my son to school [06:46] I thought we wanted to move it by 1hr, not 2 [06:48] i'm not sure if the calendar captured my intention [06:54] Wicked? Me? Why, I never... [07:09] james_w: are you still interested in / working on bzr builddeb? [07:09] [or is someone else looking after it now?] [07:09] Quite a few folks are poking at it regularly I think. [07:10] I made a branch for it just yesterday :) [07:10] spiv: Ok, I'll ask generally, then :) [07:10] 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] 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] (it doesn't) [07:12] Query 3: would you have expected that [07:13] $ bzr merge-upstream ~/path/to/file.zip --version 1.0 --distribution debian --package name [07:13] (or ~path/to/unpacked/) [07:13] would fail, whereas [07:13] $ bzr dh-make --bzr-only name 1.0 ~/path/to/file.zip [07:14] appears to work just fine? (creating a commit tagged 'upstream-1.0') [07:14] Hm. That's just about a bug report, once someone tells me which the bug is. [07:14] s/fail/apparently do nothing including not committing anything/ [07:15] [around here fail means stack trace] [07:16] hi afc [07:17] * AfC advances his regards poolie's way [07:23] what's the context where you're running merge-upstream? [07:23] an empty branch? [07:23] that seems like it should be reported as a bug anyhow [07:26] afc, to start a new package i would think you'd do import-upstream and then commit on top of that [07:26] i wonder if it's sufficiently documented [07:35] * maxb lols at pkg-bazaar-maint receiving spam selling pipes and looms :-) [07:36] i get a lot of spam about pools and spas [07:36] I don't get any spam about bleaching clothes :( [08:07] ing [08:18] poolie: yes, an empty branch [08:18] * AfC tries again [08:19] 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] So I should report this, obviously. Any preference for a bug title? [08:40] 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... === jamestunnicliff_ is now known as jamestunnicliffe === hunger_ is now known as hunger [09:02] 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] sagaci: no *precise* way (as in number of bytes), but 'bzr info -v lp:ubuntu-docs' should give you some hint [09:12] thanks vila [09:12] 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] err, scratch that, actually it downloaded ~2M, the 8M includes the working tree [09:42] bazaar explorer says "unable to obtain lock file: c:\users\\AppData\Roaming\bazaar\2.0\lock [09:43] ive deleted that file but it still keeps coming back and freezing the program [11:15] Gar, the branch for bug 248418 has caused bug 806425. [11:15] Launchpad bug 248418 in Ubuntu Distributed Development "Should set append_revisions_only on branches it creates." [High,Fix released] https://launchpad.net/bugs/248418 [11:15] Launchpad bug 806425 in Ubuntu Distributed Development "AppendRevisionsOnlyViolation in import_package" [Critical,Confirmed] https://launchpad.net/bugs/806425 [11:16] 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] Rrr. The error on pull'ing from a non-branch-root is annoying. Have I moaned about that before? [12:10] Hi all [12:15] can anyone please help me with this annoying bzr explorer bug =( [12:15] i dont know what its doing with this lock file === sidnei-away is now known as sidnei [15:07] Hello people. [15:07] 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" ? === med_out is now known as medberry === medberry is now known as med_out === beuno is now known as beuno-lunch === beuno-lunch is now known as beuno === med_out is now known as medberry === oubiwann is now known as oubiwann-lunch === yofel_ is now known as yofel === luks_ is now known as luks === oubiwann-lunch is now known as oubiwann [20:18] hi all [21:02] hi abentley [21:03] poolie: hi. [21:03] is your mp essentially saying "no, there are no reasons to want to take the other root?" [21:04] poolie: no, I'm just accepting that it's a less-disruptive change and doesn't expose several of our UI issues. [21:05] poolie: It's restoring the status quo. [21:05] right [21:05] i guess i just wonder if we should try again at making that switch, perhaps by a different course [21:06] 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] ok === poolie_ is now known as poolie === medberry is now known as med_out