[00:11] <Ng> is it possible to copy a file from one place in a branch to another and retain its history? not move, copy
[00:32] <james_w> Ng: not currently
[00:32] <Ng> james_w: ok, ta
[00:32] <james_w> Ng: history of a file means tracking a file id across versions
[00:33] <james_w> duplicate file id in a singled revision => ARRGHH!
[00:33]  * Ng nods
[00:33] <james_w> there are some suggestions for how to extend the model to allow splitting and joining file ids though
[00:33] <james_w> so maybe one day
[01:50] <fbond> Hm, bzr branch --no-tree would be useful.
[01:51] <fbond> Am I missing something obvious?
[01:54] <mwhudson> it would be useful
[01:58] <spiv> fbond, mwhudson: that's probably why it exists in bzr.dev...
[02:00] <mwhudson> spiv: hooray time machines
[02:01]  * spiv -> food
[02:05] <fbond> spiv: Ah, neat.
[02:10] <lifeless> igc: ping
[02:10] <lifeless> poolie: you're dreaming, but I want to write one
[02:15] <igc> hi lifeless
[02:17] <lifeless> igc: I have 356 seconds of internet left
[02:20] <igc> lifeless: fyi, I went digging into what log -v was doing yesterday afternoon
[02:20] <igc> the chk_map.iter_changes() code was loading some nodes twice - about 20% in my test
[02:21] <lifeless> igc: 180sec left :P we may need a phone call or something. I'maround until 1345 sydney time
[02:21] <igc> I put a simpe cache in to stop that but it made next to no difference in overall time
[02:21] <lifeless> igc: ok
[02:21] <lifeless> igc: I think a useful thing to do would be to calculate/report in a brute force way the actual common/left-only/right-only node for two trees
[02:21] <lifeless> igc: we could use that to say 'we should be doing X work'
[02:22] <lifeless> igc: and it would also be useful to jam in evaluating the flavours
[02:22] <lifeless> I don't think he's got such a tool yet [I may be wrong]. repositorydetails would be a good place to put it
[02:22] <igc> ok, I'll download repodetails and see what's it doing now
[02:23] <igc> I'm still digesting chk_map's code fwiw
[02:49] <poolie> lifeless: do you still want your .../rob directory on orcadas?
[02:49] <poolie> i'm going to tar it up
[02:49] <poolie> that machine's almost out of disk
[03:09] <igc> poolie: lifeless is offline for 2 hours - flying
[03:09]  * igc lunch
[03:18] <thumper> spiv: is http://bazaar-vcs.org/SmartPushAnalysis1.13 up to date?
[03:23] <spiv> thumper: no, the current numbers are a bit better
[03:24] <spiv> lifeless and I have been improving things too rapidly to make keeping the page up to date worthwhile :)
[03:28] <poolie> igc, thanks, np
[03:43] <bignose> jelmer: upgraded ‘bzr-loom’ on Debian squeeze
[03:44] <bignose> now I get: Unable to load plugin 'loom' from '/usr/lib/python2.5/site-packages/bzrlib/plugins'
[03:44] <bignose> the plugin is still there (a ‘/usr/lib/python2.5/site-packages/bzrlib/plugins/loom/’ directory with Python modules)
[03:45] <mwhudson> bignose: if you run bzr -Derror rocks you should get a better error message
[03:47] <bignose> $ bzr -Derror rocks
[03:47] <bignose> Unable to load plugin 'loom' from '/usr/lib/python2.5/site-packages/bzrlib/plugins'
[03:47] <bignose> It sure does!
[03:48] <mwhudson> bignose: what version of bzr?
[03:49] <bignose> $ bzr --version
[03:49] <bignose> Bazaar (bzr) 1.5
[03:50] <bignose> all as per Debian ‘squeeze’
[03:55] <mwhudson> oh, that's fairly old
[03:55] <mwhudson> ~/.bzr.log might have something about loom's failure to load
[03:56] <bignose> nevertheless, both it and ‘bzr-loom’ are as in Debian ‘squeeze’, with no dependency issues.
[03:56] <mwhudson> hm
[03:57] <bignose> yes, the log does have something
[03:57] <bignose> warning: paste bomb
[03:57] <bignose> [19317] 2009-03-04 14:53:47.719 WARNING: Unable to load plugin 'loom' from '/usr/lib/python2.5/site-packages/bzrlib/plugins'
[03:57] <bignose> 0.239  Traceback (most recent call last):
[03:57] <bignose>   File "/usr/lib/python2.5/site-packages/bzrlib/plugin.py", line 208, in load_from_dir
[03:57] <bignose>     exec "import bzrlib.plugins.%s" % name in {}
[03:57] <bignose>   File "<string>", line 1, in <module>
[03:57] <bignose>   File "/usr/lib/python2.5/site-packages/bzrlib/plugins/loom/__init__.py", line 61, in <module>
[03:57] <bignose>     import branch
[03:57] <bignose>   File "/usr/lib/python2.5/site-packages/bzrlib/plugins/loom/branch.py", line 767, in <module>
[03:57] <bignose>     class LoomBranch7(LoomSupport, bzrlib.branch.BzrBranch7):
[03:57] <bignose> AttributeError: 'module' object has no attribute 'BzrBranch7'
[03:58] <mwhudson> yeah, the bzr is too old for the bzr-loom
[03:58] <bignose> am I right in thinking that means this version of ‘bzr-loom’ should depend on a newer version of ‘bzr’?
[03:58] <mwhudson> sounds like a packaging bug
[03:58] <bignose> okay. I'll file a Debian bug for this.
[03:58] <mwhudson> good idea :)
[03:58] <mwhudson> bzr 1.6 will make that error at least go away
[03:59] <bignose> mwhudson: thanks for the troubleshooting
[03:59] <mwhudson> np
[05:14] <bob2> isn't pycurl still optional?
[05:15] <bob2> (for accessing http:// urls)
[05:15] <bignose> accessing them fails entirely for me, unless I install it.
[05:16] <bignose> bob2: I presume we're talking about Debian bug#518098 ?
[05:16] <bob2> bignose: yeah
[06:31] <poolie> vila: are you up? see  ^^ about pycurl
[06:33] <vila> poolie: not yet but soon :)
[06:36] <vila> bob2: pycurl is optional but is/was the default for http and is still the default for https, what bzr version/os are you using ?
[06:38] <bob2> vila: bigtone was having problems on debian with http with bzr 1.5
[06:39] <vila> hmm, debian bug#518098 seems to refer to bzr-1.5
[06:39] <bob2> yeah
[06:39] <vila> :-) I'm pretty sure many (or at least several :)  bugs have been fixed in that area
[06:40] <vila> bob2: do you have an url to access that bug, google only gives mailing lists hits
[06:40] <vila> bignose == ben finney ?
[06:40] <bob2> bugs.debian.org/518098, yes
[06:42] <vila> He's right about the recommends (at least today, don't clearly remember for 1.5) also, one should not take DependencyNotPresent regarding pycurl too seriously since we may as well not show it, the other http implementation being selected in that case anyway
[06:43] <vila> bob2: thanks for the url
[06:43] <bob2> so it has nothing to do with pycurl, and something else is going on?
[06:45] <vila> bob2: ok, so after reading the bug report, I think ben is wrong about pycurl being mandatory, I may need to check what has changed since 1.5 but I don't have cases where pycurl works and urllib doesn't (except for https certificate verification, but that doesn't apply here)
[06:46] <vila> bob2: I may also need the relevant pycurl version too...
[06:46] <bob2> vila: the version of pycurl he doesn't have installed? ;p
[06:47] <vila> bob2: oh well, in the end, if it works with pycurl and until bzr is upgraded to a more recent version, the simplest is certainly to just install pycurl
[06:47] <vila> bob2: :-)
[06:48] <vila> bob2: Sorry, I'm not yet fully awake, so, one last try at explaining it clearly:
[06:49] <vila> bob2: there are two http client implementations for bzr: one is pycurl based the other is urllib2 based
[06:50] <vila> bob2: they are roughly equivalent these days except for the https certificate verification that only pycurl implements
[06:50] <vila> bob2: no https involved here, so it should be a bug in urllib that has been fixed *after* bzr-1.5
[06:51] <vila> bob2:  installing pycurl (which makes it the default http client used) fixes the problem
[06:51] <vila> bob2: ergo, for bzr-.15, install and use pycurl is the way to go
[06:51] <vila> bob2: ergo, for bzr-1.5, install and use pycurl is the way to go
[07:07] <poolie> good night all
[08:04]  * igc dinner
[10:18] <vila> bob2, bignose: sorry for the delay, but I'm pretty sure debian bug #518098 has been fixed as bug #230223 on lp (fix released in 1.6)
[10:18] <vila> sorry, ubottu, that was a debian bug I was talking about, not a bzr-loom one at all :)
[10:30] <Kamping_Kaiser> hehe.
[10:43] <ROza27> hi
[10:45] <james_w> vila: it has, but that package is just in experimental currently
[10:47] <ROza27> has anyone used trac with bazaar?
[11:01] <vila> james_w: ? You mean bzr is packaged in experimental with a more recent version ? Which one ?
[11:02] <james_w>        bzr |    1.5-1.1 |      unstable | source, alpha, amd64, arm, armel, hppa, hurd-i386, i386, ia64, mips, mipsel, powerpc, s390, sparc
[11:02] <james_w>        bzr |     1.12-1 |  experimental | source, alpha, amd64, armel, hppa, i386, ia64, mips, mipsel, powerpc, s390, sparc
[11:02] <vila> james_w: ok, great
[11:03] <james_w> it can get moved to unstable now, I just don't have the poert
[11:03] <james_w> power
[11:53] <james_w> rockstar: awesome news, thanks
[14:34] <vila> good morning jam
[14:55] <jam> morning vila, sorry about the delayed response :)
[14:56] <vila> :-)
[17:09] <bac> hi.  i'm trying to help someone who needs to break a lock on a repo on LP.  do i remember correctly that using sftp instead of bzr+ssh is helpful in breaking stubborn locks?
[17:09] <beuno> bac, stubborn in what way?
[17:10] <bac> beuno: in the way that it won't break...
[17:10] <beuno> bac, error message?
[17:10] <bac> nope
[17:10] <bac> https://answers.edge.launchpad.net/launchpad/+question/62700
[17:11]  * beuno looks
[17:12] <bac> beuno: shouldn't you be sprinting or something?
[17:12] <beuno> bac, shhhhhhhh
[17:13] <beuno> bac, I'd suggest deleting the branch and pushing again
[17:13] <beuno> considering it's empty
[17:15] <bac> ah, ok.  i just seem to recall when i was in asia trying to push to devpad i used to get a bunch of held locks and spiv suggested breaking the lock using sftp.  i could be on crack, though.
[17:15] <beuno> yeah, although I think it's different in LP
[17:16] <bac> beuno:  in rockstar's suggestion he mentions ":push" -- what exactly is that?
[17:17] <beuno> bac, that's the push location
[17:18] <bac> beuno:  so can you use :pull and :parent, etc anywhere a location is needed?
[17:18] <beuno> bac, yeap
[17:18] <bac> is that documented anywhere?
[17:19] <beuno> I expect that 'bzr help revisionspec' would
[17:19]  * bac notes "bzr revno :parent" doesn't work as expected
[17:19] <bac> nope, they aren't really revisionspecs
[17:20] <beuno> well, you know parents...
[17:21] <LarstiQ> they're not revisionspecs
[17:22] <RainCT> Hi
[17:22] <LarstiQ> bac: hmm, I can't find it in the bzr topics atm
[17:22] <LarstiQ> bac: but yes, :submit etc is very useful
[17:22] <bac> LarstiQ: no, me neither.  i'm looking in directory_service.py.
[17:23] <bac> they really are handy and should be documented somewhere
[17:23] <RainCT> bzr isn't working here on Jaunty.. It says that I need dulwich, but there is no "python-dulwich" package nor anything like that
[17:23] <RainCT> ah wait, seems like it's a plugin that gives the error, nevermind
[17:24] <LarstiQ> RainCT: dulwich would be bzr-git
[17:24] <LarstiQ> (requiring it)
[17:25] <LarstiQ> bac: oh, I didn't know about :this
[17:25] <RainCT> LarstiQ: right, just figured that out.. I'm too fast to complain :)
[18:34] <phinze> is there any way to get bzr to spit out the location of its parent branch?
[18:34] <phinze> looking for shorthand way of doing bzr up $PARENT_BRANCH; bzr merge $PARENT_BRANCH .
[18:35] <phinze> where "its" is "the current branch's"
[18:36] <james_w> ":parent"
[18:36] <phinze> james_w: perfect, thanks
[18:37] <phinze> where would i have found that in bzr help?
[18:37] <phinze> (just curious)
[18:37] <james_w> nowhere :-)
[18:38] <james_w> someone *just* opened a bug saying that it should be documented
[18:38] <phinze> ah ha, well that makes me feel better :)
[18:40] <Mez> and the conversion is complete. Work now uses bzr. I wonder how that happened <evil-laugh />
[18:42] <LarstiQ> Mez: that still needs work here, hmm
[18:42] <Mez> LarstiQ: poor you :d
[18:54] <jelmer> jfroy, ping
[18:55] <jfroy> pong
[19:24] <jfroy> jelmer: ping?
[19:26] <jelmer> jfroy, pong
[19:27] <jfroy> eh, I was just wondering why you pinged me and then went silent :p
[19:27] <jelmer> jfroy, I was wondering if you could still reproduce bug 332364
[19:27] <jfroy> I'll give it a go
[19:27] <jfroy> I didn't since the bug status didn't change
[19:27] <jfroy> (test it again, that is)
[19:32] <jelmer> jfroy, thanks
[19:34] <jfroy> it failed again
[19:41] <sabdfl> jelmer: ping
[19:41] <jelmer> sabdfl, pong
[19:41] <jelmer> jfroy, thanks, can you pastebin the exact traceback?
[19:42] <jelmer> jfroy: Since the error has hopefully changed :-)
[19:42] <sabdfl> jelmer: i submitted a branch for merging on bzr-gtk, do you review those?
[19:42] <jfroy> it has not
[19:42] <jfroy> at least not much
[19:42] <sabdfl> the branch removes the actions from the notifications bzr-notify emits
[19:43] <sabdfl> actions turn notifications into alerts (i.e, dialogs with cancel buttons that stick around forever) on jaunty
[19:43] <beuno> sabdfl, I reviewed and merged it a few days ago
[19:43] <sabdfl> ah, thanks beuno
[19:43] <sabdfl> would it be possible to put an updated package together?
[19:43] <sabdfl> for 9.04?
[19:44] <beuno> jelmer, you do the packaging for Ubuntu, right?
[19:44] <sabdfl> also, beuno, do you know the status of bzr and loggerhead packages in jaunty?
[19:44] <jelmer> sabdfl: I think a tweaked version of it has been merged based on your patch, which only disables it if the notify daemon (is that the right name) doesn't support actions
[19:44] <jelmer> beuno, Yeah, for Debian/Ubuntu
[19:44] <sabdfl> jelmer: that's better than my patch, i just used a hacksaw :-)
[19:44] <jelmer> sabdfl, I uploaded a fixed package to experimental, james_w was going to request a sync for that for jaunty
[19:45] <beuno> sabdfl, loggerhead is in 1.10, which is the latest release. bzr is in 1.12, which the latest release as well.
[19:46] <beuno> we could do a release of LH, trunk has advanced quite a bit since then
[19:46] <beuno> I'll talk to mwhudson about it
[19:46] <sabdfl> beuno: that would be a good idea, yes
[19:47] <sabdfl> when is bzr 1.13 due?
[19:47] <jelmer> sabdfl: IIRC According to the original schedule a RC1 would be due in a couple of days
[19:47] <beuno> sabdfl, I think after the brisbane sprint next week
[19:47]  * jfroy pasted http://pastie.textmate.org/private/fpkj1uc5yvyqrehvopq8ow
[19:47] <jfroy> jelmer:
[19:48] <beuno> jelmer, hasn't that been pushed back due to the sprint?
[19:48] <sabdfl> i believe 1.13 adds good work on the network performance front, so would encourage a plan to release it *and* get packages into 9.04
[19:48] <jelmer> beuno: Ah, I wasn't aware of that
[19:48] <beuno> jelmer, if I do a release of LH, can you do an upload to debian so we can sync?
[19:48] <jelmer> beuno, My information dates back a month
[19:48] <jelmer> beuno, yeah, np
[19:48] <jelmer> beuno, just ping me when it's out :-)
[19:48] <jelmer> jfroy, thanks
[19:48] <jfroy> np
[19:49] <beuno> jelmer, awesome, thanks. I'll work on it today/tomorrow evening
[19:50] <beuno> sabdfl, I'll email the list about it. When's the jaunty deadline?
[19:51] <sabdfl> beuno: we're already into UI freeze exception territory: https://wiki.canonical.com/DesktopExperienceTeam/JauntyUIFExceptions
[19:53] <beuno> sabdfl, ah, so it's pretty urgent to get these out then  :)    I'll poke people about this
[19:54] <sabdfl> thanks beuno
[20:54] <jpds> How can I resolve a conflicting tag?
[20:54] <rockstar> kfogel, so, it looks like your discussion about PQM is a little different than what PQM really is.
[20:56] <kfogel> rockstar: oh?
[20:56] <kfogel> where did we go off track?
[20:56] <rockstar> Basically, it's similar to Tarmac, only that it gets it's merge requests from email.
[20:56] <rockstar> It's still "client side" in the same way Tarmac is.
[20:56] <kfogel> hmmmm
[20:56] <kfogel> rockstar: so should they be merged?
[20:56] <rockstar> kfogel, absolutely not.
[20:57] <rockstar> PQM is pretty terrible in general, and is heavy, and a pain to install.
[20:57] <kfogel> rockstar: might be good to write a section on how they differ, since they're similar...
[20:57] <kfogel> oh
[20:57] <kfogel> rockstar: well, don't write that :-)
[20:57] <kfogel> rockstar: is Tarmac meant to eventually replace PQM?
[20:57] <rockstar> So I wanted something lightweight, and something that was closely connected to Launchpad.
[21:00] <jfroy> vila: ping
[21:00] <jfroy> +
[21:03] <kfogel> rockstar: *nod*
[21:03] <kfogel> rockstar: is the lightweight-ness or heavyweight-ness noticeable to the user anyway, though?
[21:05] <rockstar> kfogel, yes.  I tried setting up PQM for another project three times.  Each time, I got nominally closer than the previous time, but eventually gave up because of difficulties.
[21:05] <rockstar> kfogel, ask thumper what he thinks of PQM's codebase.  :)
[21:05] <thumper> *cough*
[21:06] <kfogel> rockstar: heh.  Okay, so it's not  that it's heavy in terms of code size or internal complexity, it's that it's heavy in terms of user setup.
[21:07] <rockstar> kfogel, all of the above.
[21:08] <kfogel> whew
[21:08] <kfogel> rockstar: PQM is not Canonical code?
[21:08] <kfogel> rockstar: (I haven't interacted with it much, mostly what I know is hearsay)
[21:09] <rockstar> kfogel, I believe it is now, but it's pretty old and crufty, and I wouldn't say there is active development going on.
[21:10] <LarstiQ> kfogel: it's a pre-bzr codebase
[21:10] <kfogel> LarstiQ: ah
[21:11] <jseutter> question: anyone know how I can get the bzr sources to build bzr on my system?  I need something that can talk branch format 7 to check out bzr.
[21:12] <jseutter> (and yes, all I have done is go to the bzr homepage and try to follow the instructions there.)
[21:12] <jelmer> rockstar, are there any plans to have tarmac work for non-lp?
[21:13] <LarstiQ> jseutter: I'd try the latest release.
[21:13] <rockstar> jelmer, not currently.  I mean, it figures out which branches to merge through the Launchpad API.
[21:13] <rockstar> I guess it could grow that though.  Patches welcome.
[21:14] <jelmer> rockstar, Cool, I might look into that then
[21:14] <rockstar> jelmer, it would be much appreciated.
[21:15] <rockstar> jelmer, I thought it might be good to grow some email features.
[21:15] <jelmer> rockstar, yeah, that's the bit I'm interested in
[21:17] <rockstar> jelmer, also, we've talked about a pluggable branch landing system, so it may be that tarmac could become that, with a LP plugin, and an email plugin.
[21:36] <jseutter> LarstiQ, sorry, I could have been more clear.  To check out bzr it is telling me that I need bzr 1.6 or newer.  The binaries listed on the bzr homepage are all older than that.
[21:36] <jseutter> I can't get the source to build a new version of bzr to get the source.
[21:36] <jseutter> ugh.  My brain is fried.  At any rate, I have a chicken and egg problem.
[21:37] <jseutter> I checked the Ubuntu packages and the Epel repo, and they're both older than 1.6.
[21:38] <jseutter> oh wait, there's a slackware link on the homepage that is 1.6.1.  I'll try building that
[21:45] <jseutter> oh fark.  1.12 > 1.5
[21:46] <jseutter> sorry about that.
[22:02] <lifeless> poolie: hi
[22:02] <lifeless> I've gatecrashed Tim's
[22:02] <poolie> hi lifeless
[22:02] <poolie> congrats
[22:15] <bob2> vila: thanks!
[22:27] <spiv> lifeless: d'oh, my less test skips patch failed because of your bzrdir network name changes...
[22:31] <jfroy> vila: when you get around, I need to discuss a few items concerning credential providers
[22:32] <lifeless> spiv: sorry :)
[22:42] <poolie> jfroy: he's probably not back for 8h now
[22:42] <jfroy> poolie: nothing urgent
[22:42] <jfroy> *it's nothing urgent
[22:47] <jelmer> jfroy, see privmsg
[22:51] <poolie> lifeless: progress messages are less important than making sure there are no showstoppers in the version in jaunty
[22:51] <lifeless> poolie: right. So let me cap the high features for you
[22:51] <lifeless> spiv: please add any I miss ;)
[22:52] <lifeless> poolie: we do network streaming push to stacked and non-stacked branches
[22:52] <lifeless> poolie: we do network streaming pull from non-stacked branches, and for stacked ones now use the generic versioned-files based fetch rather than pack-optimised [a slight regression for that specific case]
[22:53] <lifeless> poolie: the streaming requires both client and server to have the format for both source and target in common; that is pushing from a svn checkout to a bzr branch requires the server to have bzr-svn installed
[22:53] <lifeless> we have a bunch of new verbs for creating objects over the wire and getting more data about them when we open them
[22:54] <lifeless> we may find glitches during the beta cycle, but we'll fix them without more wire changes I expect
[22:54] <lifeless> we're happy with the general structure of the data on the wire, so I don't expect we'll need to drop the new verbs at all, or at least not for a long time
[22:55] <lifeless> so we can support the jaunty versions happily
[22:55] <poolie> have you tested all these cases manually, as well as in selftest?
[22:55] <lifeless> not explicitly, and I don't think thats a particularly good use of time until rc1 is out.
[22:55] <lifeless> I'm dogfooding though, and so is spiv
[22:56] <lifeless> so are the folk using bzr nightlies, though they will be nearly universally dogfooding the backwards compatibility behaviour not the new code
[22:56] <spiv> So far I've had no nasty surprises from dogfooding.
[22:56] <jelmer> fwiw I'm dogfooding too
[22:56] <igc> morning lifeless, spiv, jelmer
[22:56] <jelmer> hi Ian
[22:57] <poolie> ok
[22:57] <poolie> so, regardless, i'd like you to please test those cases manually today
[22:58] <poolie> historically this is the kind of change that has caused knock on effects and i'd ilke to reduce the chance in this release
[22:58] <lifeless> poolie: thats going to be basically the whole day
[22:58] <lifeless> poolie: there are a _lot_ of permutations
[23:00] <poolie> is it better to spend that day next week during the sprint?  i think that's even worse.
[23:00] <poolie> and if the other alternative is to do this release in to jaunty without integration testing, i like that even less.
[23:00] <lifeless> poolie: whats the due date for jaunty? Can we not do a days full-permutation testing after the sprint?
[23:01] <lifeless> poolie: and do a point release if we find any issues?
[23:03] <poolie> so that would give us more networking improvements in 1.13, but more chance that there are bugs in the ones we do have?
[23:04] <poolie> wiki.u.c is down and i don't have the dates written down here
[23:04] <poolie> ui freeze is today, beta freeze is march 19
[23:05] <lifeless> thursday after the sprint
[23:05] <lifeless> If we're going to do this sort of manual testing, I'd much rather do it monday the 16th
[23:06] <poolie> because why?
[23:07] <lifeless> well, we have two days left. We might be able to get to streaming-from-stacked, or vfs-free branch-from-non-stacked if we keep the momentum up
[23:08] <lifeless> as soon as we stop, the protocol is frozen for those verbs until the release in the absence of serious issues.
[23:13] <spiv> lifeless: I'm a bit unsure what the right fix for the less-skips + network_name failure is.  The server-side is failing on control_format.get_branch_format().network_name() in sprout_bzrdir_branch_ref tests.
[23:14] <lifeless> spiv: is there a network name for BranchReferenceFormat?
[23:15] <spiv> No, there isn't.  The error is AttributeError: 'RemoteBranchFormat' object has no attribute '_network_name', btw.
[23:16] <poolie> spiv, what do you think?
[23:17] <spiv> poolie: as lifeless says, we are tantalisingly close to some milestones.
[23:18] <poolie> ok
[23:18] <poolie> i will hold you two responsible if there are showstoppers in this release
[23:18] <spiv> So it's even harder than normal to be enthusiastic about manually testing ;)
[23:19] <poolie> but i wish you luck
[23:19] <poolie> sure, i can sympathize with that
[23:22] <lifeless> spiv: *serverside* is using a RemoteBranchFormat?
[23:22] <spiv> lifeless: right!
[23:22] <spiv> lifeless: it's a RemoteBzrDirFormat test.
[23:22] <lifeless> spiv: those two nouns should never be in a single sentence unless it is '*serverside does not use RemoteBranchFormat objects*'
[23:22] <spiv> Or rather, a bzrdir_implementations test.
[23:23] <spiv> Heh.
[23:25] <spiv> lifeless: ok, I can tweak bzrdir_implementations/test_bzrdir to explicitly use get_vfs_only_url or something.
[23:28] <lifeless> spiv: there may betwo issues; the test asking the server to do something bong; the server not preventing third-party-requests.
[23:28] <lifeless> spiv: we know the second exists
[23:29] <spiv> Well, the test was creating a branch reference (on a server), and then sprouting it (to a new url on the same server)
[23:30] <spiv> All three failing tests were following that pattern.
[23:31]  * igc breakfast - bbl
[23:31] <spiv> If I change it to create the branch reference locally, then sprout to a server, it works.
[23:32] <spiv> If I change it to create a remote branch reference, and sprout it to local, it still fails.
[23:32] <lifeless> spiv: so its reasonable to say to the server 'create a branch reference to url XXX'
[23:32] <lifeless> spiv: its not reasonable for the server to assume it can read it
[23:33] <spiv> Right.
[23:40] <lifeless> upo	el	thanks
[23:40] <Jerub> what's the best way to transition from svn to bzr? I tried using bzr-svn but it didn't work for me.
[23:42] <lifeless> Jerub: in what way didn't it work
[23:42] <spiv> Jerub: bzr-svn 0.5 has been working very well on the couple of projects I've tried it on.
[23:44] <Jerub> it was a few weeks ago i did it, I don't actually remember what the failure was.
[23:44] <lifeless> poolie: so qa wise I'm much more concerned that we're going to DOS the lp smart server
[23:44] <lifeless> than tat we'll have the client fail to work as desired
[23:45] <lifeless> poolie: theres plenty of adhoc testing that occurs as we just use the client, as we test stuff for the python guys and so on
[23:46]  * Jerub runs it again


[01:44] <ibeardslee> http://www.markshuttleworth.com/archives/1246
[01:44] <ibeardslee> 7 month support for 'interim' releases
[01:45] <ibeardslee> .. under consideration
[01:55] <ibeardslee> that combined with the LTS Enablement Stack I think does an great job
[01:56] <ibeardslee> just got to catch those 'interim' release installers that don't bother upgrading
[03:24] <olly> 7 seems a bit on the short side
[03:25] <olly> 18 has struck me before as needlessly long though, since you can't actually skip releases when upgrading between non-LTS releases
[03:26] <ibeardslee> yeah it probably is a bit short if there are more people trying to upgrade in that month .. assuming the interim releases stick to the 6 months
[03:27] <olly> when I used to follow the ubuntu interim releases, I tended to wait until I could afford to waste a day in case things went wrong
[03:28] <olly> and some months that doesn't really fit
[18:19] <ibeardslee> morning
[20:39] <olly> morning


[10:35] <Guest34599> Hi
[10:36] <Guest34599> any one know anything about the new ubuntu 16.04
[10:48] <Fudge> try #ubuntu+1


[01:01] <nhaines> pleia2: that's right!
[01:01] <pleia2> ok, thanks :)
[01:02] <nhaines> Everyone was slightly uncomfortable about that, but SCALE refused to let us require SCALE admission as a condition of UbuCon attendance.  :)
[01:03] <nhaines> So we accepted it, even though no one can figure out why anyone would go to SCALE and not at least buy the $10 expo pass.
[01:03] <pleia2> nhaines: hm, where is the scale registration code (wiki says to be updated soon)
[01:03] <pleia2> hah
[01:03] <nhaines> Oh, it's UBNTU.  I could have sworn that I'd updated that.
[01:04] <pleia2> nhaines: should http://loco.ubuntu.com/events/ubuntu-california/3234-scale-14x-and-ubucon-summit/ be updated to registration on meetup.com?
[01:04] <pleia2> it's suggesting registration is to scale
[01:04] <pleia2> when you click the "Register" button
[01:05] <pleia2> trying to help one of our ubucon speakers, I hadn't actually looked at any of this until now ;)
[01:05] <nhaines> Yes, that's on my todo list.  I think I wasn't certain whether or not to split SCALE to its own event on the LoCo thing, so I didn't do it immediately.  But now that we have the meetup thing it should still be updated.
[01:06]  * pleia2 nods
[01:07] <pleia2> I still haven't heard back about my main scale talk, so I haven't bought my ticket or reserved anything yet
[01:08] <pleia2> I emailed one of the organizers on saturday, said I should hear "in a couple days" so who knows
[01:09] <nhaines> LoCo Directory is updated, thanks.  :)
[01:09] <pleia2> thanks \o/
[03:35] <ianorlin> LAX was close enogh for me to easily drive
[03:36] <ianorlin> Pasadena is quite a bit farther for me


[03:22] <yuki-onna> i think the problem for this was that my monitor (new one) and tv  gave up on looking for a signal too fast
[03:23] <yuki-onna> i had fixed a monitor i had that blew a few capacitors that waits long enough for it to get a signal an mythtv seems to be working so far
[03:35] <yuki-onna> next hurdle is getting it to see my tv tuner ><
[03:38] <yuki-onna> and let me get back to a thing so the front end doesn't crash]
[03:48] <yuki-onna> gives me some dialog saying front end crashed and exit code 130
[06:39] <yuki-onna> ok so now x windows is working, but, new thing trying to get the front end to not crash, while exiting with exit code 130
[23:10] <yuki-onna> last problem as far i can see i have the tuner channels setup
[23:11] <yuki-onna> i have the back end detectable address wise and such
[23:11] <yuki-onna> but the frontend says the tuner is busy
[23:41] <yuki-onna> the front end says the tuners on my hauppauge 1600 are not recording anything but the front end says they are busy anything i can do about freeing them up so i can do live tv?


[00:16] <cmaloney> "My name is Birgit Efua. I'm in Charge of the Audit Department in a branch of the  Bank where i am presently working ."
[00:16] <cmaloney> Sounds legit.
[00:22] <jrwren> you know birgit too?
[00:26] <cmaloney> Apparently she works at all the banks
[00:28] <greg-g> depending on who receives the email
[01:20] <cmaloney> EVening
[01:43] <rick_h_> evening
[02:19] <cmaloney> I think Redshift is one of my favorite bands to program to
[02:19]  * cmaloney is listening to Death - Vacant Planets
[02:20]  * cmaloney is listening to Death - Vacant Planets
[02:20] <cmaloney> Feh
[02:20] <cmaloney> Apparently it hasn't caught up
[02:21]  * cmaloney is listening to Redshift - Siren V
[02:21] <cmaloney> THere we go
[04:32] <greg-g> redshift is also a great way of saving your eyes :)
[04:32] <greg-g> apt-get install redshift # that is
[05:07] <cmaloney> heh
[14:38] <cmaloney> Good morning btw.
[14:42] <brousch_> There's no one named "btw" here.  Kiss kiss.
[14:56] <cmaloney> ^^ Example of letter I would never have had the balls to write when I was a kid. :)
[16:21] <greg-g> g'morn
[16:22] <greg-g> I think the quick trip to MI gave me some cold/something. :/
[16:25] <cmaloney> You sure it wasn't sitting in close quarters with over a dozen people in an oversized sausage container?
[16:26] <greg-g> for ~16 hours out of 30? nah, can't be!
[16:29] <brousch_> jrwren probably poisoned you
[16:30] <greg-g> I did eat a couple cookies his wife was making....
[16:40] <jrwren> ha!
[19:08] <rick_h_> cmaloney: http://www.postgresql.org/about/news/1557/
[19:08] <rick_h_> Concurrently updatable Materialized Views for faster, more up-to-date reporting.
[19:09] <rick_h_> the new JSONB data type for PostgreSQL
[19:09] <rick_h_> :)
[19:09] <jrwren> yeah. postgresql <3
[19:09] <jrwren> ALTER SYSTEM looks interesting
[19:10] <rick_h_> Automatically updatable views were introduced in PostgreSQL 9.3, allowing data in simple views to be updated in the same way as regular tables without the need to define triggers or rules. In PostgreSQL 9.4 this feature has been enhanced to apply to a wider class of views and to allow new data to be validated against the view definition.
[19:10] <rick_h_> <3 could have used that so much at the last job
[19:17] <cmaloney> rick_h_: Already on it.
[19:17] <cmaloney> :)
[19:18] <cmaloney> Seriously, it's like PostgreSQL keeps knocking down the hard problems
[19:31] <jrwren> cmaloney: once they get master-master its going to be AWESOME!!!
[19:36] <brousch_> It's not awesome already?
[19:41] <cmaloney> brousch_: It's like every release is Christmas
[19:41] <cmaloney> and a chance for me to bug my boss that we're still not using PostgreSQL
[23:43] <brousch_> What are people using these days instead of byobu?
[23:44] <rick_h_>  nothing it's pointless imo
[23:46] <brousch_> So no terminator or whatever?
[23:46] <rick_h_> tmux + terminal and that's it
[23:46] <brousch_> So, tmux
[23:47] <rick_h_> sure
[23:47] <rick_h_> for "tabs" and reconnecting to sessions
[23:47] <brousch_> I haven't used any of these. I'm asking for a friend.
[23:47] <rick_h_> but byobu is a layer on tmux or screen
[23:47] <rick_h_> so I'd consider them different


[00:19] <shauno> you're a furry?
[00:20] <daftykins> always had my suspicions
[00:21] <shauno> I'm just surprised - it'd be the most normal thing about him
[00:21] <diddledan> :-)
[00:22] <shauno> I've only just figured out that 'zero cool', sickboy and sherlock from elementary are the same person.  "mind blown" as the internet goes
[00:22] <ali1234> johnny lee miller?
[00:22] <shauno> yeah
[00:23] <ali1234> remember back in the day when we didn't know what furry was, and http://en.wikifur.com/wiki/Amy_the_Squirrel was just  cartoon mascot for the amiga?
[00:24] <ali1234> we were so innocent back then
[00:24] <shauno> I'm not sure I can click on 'wikifur'.
[00:24] <ali1234> don't worry, there are no pictures
[00:25] <shauno> ah.
[00:25] <daftykins> so some girl just squatted on my doorstep
[00:25] <daftykins> i open the door as i heard movement
[00:26] <daftykins> her bf comes back up, apologises and gives me £10
[00:26] <daftykins> \o/
[00:26] <diddledan> lmao
[00:26] <shauno> so this is why ireland forbids alcohol on good friday?
[00:26] <daftykins> do they?
[00:26] <shauno> yup
[00:26] <diddledan> but it's turdsday until I wake up in the morning/afternoon
[00:27] <shauno> I have a mediocre "squatting" story
[00:27] <shauno> the day before I moved to the US, I went out on the town with .. well, everyone.  on the way home I relieved myself somewhere I probably shouldn't have
[00:28] <daftykins> wait, so IT WAS YOU!
[00:28] <shauno> mr "copper" stands right beside me while I finish up, and introduces himself.  he gets my number (schawing!) and we go about our ways
[00:28] <daftykins> odd way of dating sir
[00:28] <daftykins> ;)
[00:28] <shauno> 24 hours later I'm on Delta out of heathrow, and forget all about it
[00:29] <diddledan> shauno: there's a similar story about one of the UK's most wanted criminals
[00:29] <shauno> eventually daddy#2 shows up to sell the house we move out of, and finds the mail.  I have a notice to appear, a summons, a summary judgement on failure to appear ..
[00:29] <diddledan> we don't get much crime these days so peeing in the street is a somewhat of the most impressive of crimes
[00:30] <shauno> and to cap it off, it turns out the doorstep belongs to an ex
[00:30] <diddledan> lol
[00:30] <daftykins> LOL
[00:30] <daftykins> shauno: subconsciously you knew you had to do your business RIGHT there
[00:31] <shauno> possibly the strangest conversation ever was phoning transatlantic to explain to cumbria cty courts why I wasn't going to be appearing any time soon
[00:32] <daftykins> OI AM SHEEEEER-NO, OI AIN'T COMIN'
[00:32] <shauno> mostly just a silly story, until I moved back to europe.  and the first time I visited the UK, I was genuinely nervous that the border were going to stop me because I had failure to appear against my name
[00:34] <ali1234> happened to a friend of mine... for failure to pay TV license though
[00:35] <diddledan> shauno: you mean we actually let you back in?
[00:35] <daftykins> so me and the cat are playing charades, the clue is 'an activity'
[00:35] <daftykins> https://www.dropbox.com/s/x3h0sdkah33ahuo/IMG_20140418_013334.jpg
[00:36] <shauno> multiple times :)
[00:36] <daftykins> i've already guessed rowing
[00:36] <daftykins> and falling down a well
[00:36] <shauno> prostrate?  your cat may be buddhist
[00:37] <daftykins> i feel silly, i'm unfamiliar with that word
[00:38] <shauno> 1) lying stretched out on the ground with one's face downwards.
[00:38] <diddledan> isn't that in a dude's bum?
[00:38] <shauno> " especially in reverence or submission."
[00:38] <shauno> that's prostate.  the missing R is incredibly important
[00:39] <shauno> (see also: important vs impotent)
[00:40] <daftykins> lol.
[00:41] <shauno> eg, http://nickyloh.com/wp-content/uploads/2011/07/Tibet0035.jpg   they're wearing 'shoes' on their hands because the ascend the entire moutain in this position
[00:41] <daftykins> wellity wellity
[00:44] <shauno> strange strange day.      I've brought in some huge clients.  apple. microsoft, ericson, walmart, etc
[00:46] <shauno> 5 minutes way too often, up to an hour on exactly the wrong day, which set it off
[00:47] <daftykins> :(
[00:47] <daftykins> legit reason?
[00:47] <shauno> I've been told I can appeal it, but I'm torn between that, and acting like a 12yo and flipping the bird
[00:48] <shauno> no legit reason.  I'm an insomniac.  have been as long as I remember.  6am shifts are difficult
[00:48] <daftykins> damn yeah :S
[00:49] <daftykins> seems to be us three nightowls meet quite often
[00:49] <daftykins> i'm tempted to quote Macbeth i think it is by asking, since i'll be away for the weekend, "when shall we three meet again?" :D
[00:49] <shauno> just a weird one because I've had an abnormally strong year
[00:49] <daftykins> does seem like they should be lenient on such minor transgressions given that
[00:50] <daftykins> especially being so... school like about it
[00:50] <daftykins> have you spoken one on one with whoever's the decider?
[00:50] <shauno> I'm still thinking about that.  I only found out today
[00:51] <daftykins> ah
[00:51] <daftykins> guess it depends on your relationship with them if it's worth a try or not
[00:51] <shauno> the 'problem' is our manager's manager.  it's his training I was quite (almost an hour) late for.
[00:51] <daftykins> doh
[00:51] <shauno> and ... he's german.  'late' doesn't translate into german
[00:51] <daftykins> hehe
[00:52] <diddledan> I don't think they have an equivalent word
[00:52] <jpds> Oh, they do.
[00:52] <diddledan> jpds: insults aren't quite the same
[00:52] <shauno> 'dead' is probably the equivalent.  if you think about it, 'late' and 'late and synomnym in english
[00:53] <jpds> "absolute Wahnsinn".
[00:54] <shauno> it's just a weird situation.  especially since they already took 1/5th of my bonus for the same reason.  and without tooting my own horn too much, I am the alpha nerd on the team
[00:55] <daftykins> :D
[00:55] <daftykins> shauno: hope it works out
[00:56] <daftykins> right i really have to go, have a good easter all \o
[00:56] <diddledan> nn
[00:57] <shauno> have a fun trip :)
[00:58] <daftykins> ty ^_^
[01:00] <popey> daftykins: safe travells
[05:26] <mapps> Wwe ae tottenham
[05:26] <mapps> :D
[05:26] <mapps> in Islington atm
[08:16] <Myrtti> morning and top of the day to you
[08:17] <mapps> morning
[08:18] <Myrtti> I'm trying to find out where can I find a pci express wifi card that's half height and supported by Linux...
[08:21] <Myrtti> ah, I think I've found one
[08:59] <TheProphet[S]> Hi all
[09:02] <TheProphet[S]> I am trying to connect to my wireless network from recovery, but I can't get Dhcp to work. dhclient wlan0 - v just ends with no dhcpoffers received, no working leases in persistent database -  sleeping
[09:08] <TheProphet[S]> Iwconfig shows I am connected to the network but there's no Internet connection
[09:13] <TheProphet[S]> Has anyone got any idea what the problem could be? I need the Internet to fix the installation
[09:16] <dwatkins> TheProphet[S]: does "iwconfig list" show the SSID of your access point?
[09:18] <TheProphet[S]> iwconfig wlan0 does yes
[09:19] <TheProphet[S]> dawkins: I can see the correct ssid and encryption key
[09:19] <dwatkins> I guess you could set the IP address manually, but it should be provided by the local DHCP server (assuming it's running etc.)
[09:21] <dwatkins> iirc, the key needs to be the hex equivalent of the passphrase, but I could be wrong about that
[09:21] <TheProphet[S]> Trying to ping Google Dns <IP_ADDRESS> it says host unreachable
[09:21] <dwatkins> have you manually configured your IP address, TheProphet[S]?
[09:21] <TheProphet[S]> No I haven't
[09:22] <dwatkins> if you know the network range, you could set the IP address by hand, but I suspect it's not connected successfully to your wifi because of the type of security
[09:23] <dwatkins> you might also have to stop networkmanager
[09:23] <AndChat|213761> Sorry I'm back
[09:27] <TheProphet[S]> Hey dwatkins sorry I'm back now
[09:28] <TheProphet[S]> I should be able to ping an ip if I'm connected to the network right?
[09:28] <dwatkins> that depends on many things, TheProphet[S] - try pinging a local address first, such as your router
[09:29] <dvrr> Hi  good morning everyone
[09:31] <brobostigon> morning boys and girls.
[09:33] <TheProphet[S]> Morning
[09:34] <TheProphet[S]> dwatkins even my router is unreachable sorry
[09:35] <TheProphet[S]> I thought I did things properly but it can't be
[09:35] <TheProphet[S]> I'm gonna try it again
[09:38] <TheProphet[S]> From recovery mode dropped to root shell and logged in as my user
[09:39] <TheProphet[S]> Remounted root fs to rw
[09:42] <TheProphet[S]> Ifconfig wlan0 up and iwconfig wlan0 essid... key... Done
[09:44] <TheProphet[S]> It's not just "key" right? I'm forgetting something
[09:45] <dwatkins> it depends on the format of key you're using
[09:46] <dwatkins> this might help, TheProphet[S] - http://stackoverflow.com/questions/14119446/iwconfig-connect-network-via-wifi-on-terminal
[09:47] <TheProphet[S]> Thanks dwatkins I was reading that and it seems I need to use wpa-supplicant
[10:08] <dvrr> how to redirect all pages (website) to maintenance page
[10:15] <TheProphet[S]> dwatkins I managed to get it to work with wpa_supplicant thanks for your help
[12:23] <brobostigon> goo.gl/J6pGU5  :)
[12:27] <MartijnVdS> brobostigon: I think I saw that one on Fidonet once in the 90s :P
[12:27] <brobostigon> ah, :)
[12:57] <MooDoo> howdy all
[12:58] <brobostigon> hi MooDoo
[13:06] <MooDoo> how are you brobostigon ?
[13:06] <brobostigon> not bad, and you MooDoo ?
[13:07] <MooDoo> yeah ok thanks, just made sure all machines were trusty, everything fine.
[13:08] <bigcalm> Good morning peeps :)
[13:08]  * bigcalm hugs nvidia
[13:08] <MooDoo> howdy bigcalm
[13:08] <brobostigon> :)
[13:34] <ahayzen_> Hi, I'm trying to install ubuntu-restricted-extras and it wants to remove oxideqt-codecs is this ok to be removed?
[13:35] <brobostigon> !oxideqt-codecs
[13:36] <brobostigon> !info oxideqt-codecs
[13:37] <ahayzen_> brobostigon, i think it has come down with the new QML web browser that is installed by default?
[13:37] <brobostigon> which ubuntu version are you using?
[13:37] <ahayzen_> brobostigon, trusty
[13:37] <brobostigon> !info oxideqt-codecs trusty
[13:38] <brobostigon> nominally answers the question.
[13:39] <ahayzen_> brobostigon, bit strange on a clean image u can't install ubuntu-restricted-extras without breaking the new web browser that is used for the webapps?
[13:40] <ahayzen_> brobostigon, unless one of the packages in the restricted-extras will replace it? i see it wants to install things like oxideqt-codecs-extra
[13:40] <brobostigon> that would be a fair presumption.
[13:41] <ahayzen_> brobostigon, this is what it wants to do http://pastebin.ubuntu.com/7275721/
[13:42] <ahayzen_> it just looks much worse in USC when that dialog appears stating it is going to remove things lol
[13:43] <ahayzen_> brobostigon, i'll take a punt and see what happens thanks for ur help
[13:43] <brobostigon> those nominally look like the right packages.
[15:27] <NET||abuse> Hi guys, trying to use preseed to build an ubuntu vm, but can't get past "Select your location" automatically..
[15:29] <NET||abuse> anyone know what d-i option in preseed is needed, or boot_command option is needed?
[15:32] <NET||abuse> i've tried this in the boot command        keyboard-configuration/modelcode=SKIP keyboard-configuration/layout=uk keyboard-configuration/variant=uk console-setup/ask_detect=false
[15:51] <NET||abuse> figured out en_UK is not locale, only language, en_GB is locale... duh
[15:51] <NET||abuse> sorted
[18:30] <mapps> urgh
[18:30] <mapps> feel rough
[18:30] <mapps> the horrid next day feeling:)
[18:31]  * penguin42 worries what mapps did yesterday - Trusty release party?
[18:33] <bashrc_> too much release partying
[18:33] <mapps> haha
[18:33] <mapps> too much partying
[18:33] <popey> evening
[18:33] <mapps> usual routine
[18:34] <mapps> evening popey
[18:34] <mapps> some day i'll learn..30 this year;p shouldve leant by now
[18:40] <penguin42> 30 years of partying or just 30 years?
[18:45] <mapps> wekk
[18:45] <mapps> 30years old
[18:45] <mapps> so just 30years
[18:45] <penguin42> youngster :-)
[18:45] <mapps> party time began at uni
[18:45] <mapps> haha
[18:45] <mapps> young,,,,whenever i gi out im the oldest git there
[18:45] <mapps> 17/18 year olds everywhere
[18:46] <mapps> and there's old perv mapps
[19:04] <bashrc> 30 years of partying.  woohoo
[21:33] <daubers> Evening
[21:37] <popey> yo
[22:01] <Azelphur> popey: question...why on earth do you have to "buy" steam in the software centre?
[22:09] <popey> Azelphur:  bug 968974
[22:09] <Azelphur> fun
[22:11] <Azelphur> so basically, been a bug for years and isn't gonna get fixed :P
[22:20] <popey> Azelphur: patches welcome


[00:05] <bdmurray> Is there a reason that its possible to report bugs about packages not in Ubuntu?  For example if you go to https://edge.launchpad.net/ubuntu/+source/automake1.11/ it is not available in Ubuntu but a PPA
[00:05] <bdmurray> However, if you click on Bugs then File a Bug you can report a bug about this non-ubuntu package
[00:09] <synic> a package isn't required to be in Ubuntu to make use of launchpad
[00:19] <wgrant> synic: It is to file bugs about it in Ubuntu.
[00:20] <bdmurray> Well it ends up raising an error if you actually go to file the bug
[00:20] <wgrant> Right.
[00:20] <wgrant> I filed a bug about that years ago.
[00:20] <wgrant> And it is still fixed.
[00:20] <synic> oh, heh
[00:20] <wgrant> (in that you can't actually file a bug)
[00:20] <wgrant> Odd that the button shows up, though.
[00:21] <bdmurray> well and the bug listing for Ubuntu shows up too
[00:21] <wgrant> Bug #157342
[02:54] <mhall1191> okay, my first attempt at both packaging and uploading to a PPA
[02:54] <mhall1191> I got the packaging working, and I think I dput okay
[02:54] <mhall1191> I get: Successfully uploaded packages.
[02:54] <mhall1191> Not running dinstall.
[02:55] <mhall1191> but still no package in https://launchpad.net/~mhall119/+archive/ppa
[03:01] <hggdh> mhall1191, it takes a bit for them to appear
[03:01] <mhall1191> oh, so I'm just being impatient?
[03:02] <wgrant> mhall1191: You need to wait up to 5 minutes.
[03:02] <wgrant> If it's not there after 5 minutes, and you don't have an email from Launchpad, you probably didn't sign the package properly.
[03:02] <mhall1191> so, it launchpad building the binary?
[03:02] <wgrant> You'll get an email before it starts doing that.
[03:02] <mhall1191> it says the signature is good
[03:02] <wgrant> The key is associated with your Launchpad account?
[03:03] <mhall1191> okay, got an email: Unable to find distroseries: unstable
[03:03] <mhall1191> wgrant: yes
[03:03] <wgrant> So, your changelog says 'unstable'. But that's not an Ubuntu release.
[03:04] <mhall1191> okay, must be from reading debian's documentation
[03:04] <mhall1191> what would it be for Ubuntu, "intrepid" or "jaunty"?
[03:05] <mhall1191> something like that?
[03:05] <wgrant> Exactly.
[03:06] <mhall1191> okay, rebuild and try again, thanks
[03:08] <mhall1191> dput -f to make it upload again?
[03:08] <wgrant> Yes.
[03:09] <mhall1191> okay
[03:09] <mhall1191> trying it again
[03:10] <mhall1191> qimo-usplash_1.0.0.dsc: Unknown section 'X11'
[03:10] <wgrant> x11, not X11.
[03:11] <mhall1191> thanks
[03:11] <mhall1191> noob mistakes
[03:11] <mhall1191> I appreciate the help though
[03:11] <wgrant> np
[03:16] <mhall1191> woo hoo, Accepted!
[03:16] <mhall1191> thanks again wgrant
[03:16] <wgrant> mhall1191: Excellent.
[03:16] <wgrant> Now, let's see if it builds...
[03:17] <mhall1191> https://launchpad.net/~mhall119/+archive/ppa shows 1 source package, 0 binary
[03:17] <wgrant> You've hit the build farm at a bad time.
[03:17] <wgrant> Right now there are lots of builds, and not many builders.
[03:18] <wgrant> If you expand the source package row and click on the builds, you'll get an estimate of the starting time.
[03:18] <mhall119|eeepc> sorry my laptop battery was dying
[03:19] <mhall119|eeepc> had to switch
[03:19] <wgrant> Ah.
[03:19] <wgrant> 12:17:48 < wgrant> You've hit the build farm at a bad time.
[03:19] <wgrant> 12:17:57 < wgrant> Right now there are lots of builds, and not many builders.
[03:19] <wgrant> 12:18:27 < wgrant> If you expand the source package row and click on the builds, you'll get an estimate of the starting time.
[03:22] <mhall119|eeepc> :(
[03:22] <mhall119|eeepc> build failed
[03:22] <wgrant> Indeed.
[03:22] <wgrant> Faily obvious fix.
[03:22] <wgrant> Build-Depend on whatever provides pngtousplash.
[03:24] <mhall119|eeepc> ah, okay
[03:24] <mhall119|eeepc> I'll have to find that
[03:26] <wgrant> mhall119|eeepc: You might want to look at https://wiki.ubuntu.com/PbuilderHowto. That will let you test the build-dependencies locally.
[03:27] <mhall119|eeepc> thanks
[05:07] <sanmarcos> does launchpad only support Bazaar as source control?
[05:10] <mwhudson> yes
[05:23] <mrooney> Anyone know if webhooks are a plan / current request for launchpad code hosting? So I can tell launchpad to POST to a given URL on commit like a post commit hook, triggering a build or something?
[05:27] <mwhudson> mrooney: we'd like something like that, but i don't think there's any decision made about what the mechanism would be
[05:27] <mwhudson> (maybe XMPP?)
[05:28] <mrooney> The general solution seems to be an HTTP POST because of its simplicity and how well understood HTTP already is
[05:28] <thumper> mrooney: file a bug on launchpad-code
[05:28] <mrooney> plus plenty of things already listen on http and can perform actions over them
[05:29] <mrooney> I haven't looked at github but I know it has that feature, I think it uses HTTP
[05:29] <thumper> mrooney: provide examples if you can
[05:29] <mrooney> thumper: okay. thanks!
[05:32] <micahg> I got an error on uploading to my ppa that 2 original source tarballs are different
[05:33] <micahg> if I delete the current package in tehre, will it solve the problem?
[05:34] <wgrant> micahg: Possibly, but that's a very bad idea.
[05:34] <wgrant> micahg: It might solve it after a day or two, but you shouldn't do that sort of thng.,
[05:34] <micahg> ugh
[05:34] <wgrant> Why would the orig.tar.gz differ?
[05:35] <micahg> idk
[05:36] <wgrant> By definition they should not differ.
[05:36] <wgrant> Or they are not the orig.tar.gz.
[05:36] <micahg> 1 know
[05:36] <micahg> I know
[05:36] <micahg> right
[05:36] <micahg> I think the one I uploaded originally is not the original
[05:36] <micahg> I got it directly from the source instead of from ubuntu
[05:37] <micahg> wgrant: here's what I got
[05:37] <micahg> http://pastebin.ubuntu.com/238145/
[05:37] <wgrant> If the Ubuntu one is different from upstream but has the same version, there is something wrong.
[05:38] <wgrant> (not unlikely, and it does happen, but it shouldn't)
[05:39] <micahg> so, what should I do now
[05:39] <micahg> I checked the help page and it says to regenerate the tarball
[05:39] <wgrant> Work out what the difference is
[05:39] <wgrant> If you really do need the new one, change the version number.
[05:40] <wgrant> (eg. add +repack1 if it's just a repack, or +dfsg1 if it's removing some non-free stuff)
[05:42] <micahg> I'm pulling in down now
[05:43] <micahg> is there a command that will spit out the differences between tarballs?
[05:44] <wgrant> I'd just unpack them and diff -Nur
[05:46] <micahg> ah
[05:46] <micahg> I found it
[05:46] <micahg> the one I built has -orig appended to the folder
[05:47] <wgrant> This is why we grab the tarball from upstream.
[05:47] <micahg> I did :)
[05:48] <micahg> ok
[05:48] <micahg> so what to do now?
[05:49] <wgrant> Who has the right tarball?
[05:49] <wgrant> Ubuntu or you?
[05:49] <wgrant> And which one is already in your PPA?
[05:50] <micahg> Ubuntu and mine
[05:50] <wgrant> you cannot both have a different right tarball.
[05:51] <wgrant> There is at most one correct tarball in existence, unless upstream is crazy.
[05:51] <micahg> Ubuntu has the right one and mine is in my ppa :)(
[05:51] <lifeless> micahg: if they are both right why are they different?
[05:51] <wgrant> Ah.
[05:51] <wgrant> I see.
[05:51] <micahg> lifeless: in essence both are correct, they contain the same files
[05:51] <wgrant> The tarball content is the same, except for that directory name?
[05:52] <micahg> yes
[05:52] <lifeless> micahg: then they are different; choose one and use it.
[05:52] <rafiu> ping
[05:52] <wgrant> rafiu: Failed.
[05:52] <rafiu> wgrant: send
[05:52] <wgrant> micahg: What is this new thing you are trying to upload with the Ubuntu tarball? I'd probably rebuild it to reference your version of the tarball instead.
[05:53] <micahg> hmmm
[05:53] <rafiu> anyone here familiar with the process for migrating to launchpad from trac once we've converted trac tickets to xml?
[05:53] <micahg> I think I'll just upload without the source :)
[05:53] <wgrant> micahg: Watch out for the hash in the .dsc.
[05:53] <micahg> ah
[05:53] <wgrant> rafiu: You need a Launchpad Bugs developer. They are in Europe, so are hopefully all asleep.
[05:54] <rafiu> asleep!?
[05:54] <wgrant> micahg: You might need to move the Ubuntu tarball out of the way, grab the one from your PPA, then debuild -S again.
[05:54] <rafiu> space invaders not supposed to sleep
[06:07] <micahg> wgrant: it accepted it this time :)
[06:07] <wgrant> micahg: Excellent.
[06:08] <micahg> although, I don't know if it'll even fix the problem I was having, but that's another story :)
[06:09] <mrooney> thumper: okay, I filed bug 407234, here's to hoping!
[06:09] <thumper> mrooney: do you think they should be configurable on a branch by branch basis?
[06:10] <mrooney> thumper: I'm up in the air, I think by project basis is a great simple, first step
[06:10] <mrooney> Plus if it passes the branch name, the listener can conditionally act if desired
[06:10] <thumper> mrooney: you don't really want it submitting for any branch associated with the project, surely
[06:10] <wgrant> By project doesn't make sense.
[06:11] <mrooney> neither makes sense for all purposes, project is the most simple and powerful
[06:11] <wgrant> Project is more complicated.
[06:11] <mrooney> why's that?
[06:11] <wgrant> If it's per-branch, there is no need for a special way to send the branch identifier.
[06:12] <thumper> mrooney: if you are a developer, I'd be happy to mentor this change in
[06:12] <mrooney> if I have a build server I may not want to register a new hook each time I branch a release. also I may want to do things on new branches made by others
[06:12] <mrooney> thumper: sure!
[06:12] <mrooney> wgrant: I think both might coexist in an ideal world?
[06:12] <mrooney> So you can have either or both
[06:13] <mrooney> thumper: I have yet to look at LP code but am moderately experienced with python and programming in general
[06:13] <thumper> mrooney: first up we'd have to get agreement on the right way to do it
[06:14] <thumper> mrooney: whether based on branch or project
[06:14] <thumper> mrooney: branch may be more flexible as it could work with +junk and package branches
[06:14] <thumper> mrooney: although we could move this to the bug report
[06:14] <mrooney> yeah, do you agree having both is not contradictory?
[06:15] <thumper> mrooney: having both is more work, and we would be able to get branch in more easily I believe
[06:15] <thumper> mrooney: although we'd have to work out who hits the hooks
[06:15] <thumper> mrooney: the scanner, or something else
[06:15] <mrooney> oh okay
[06:15] <thumper> we have infrastructure around branch jobs
[06:16] <wgrant> A job seems nicer, but overkill...
[06:16] <thumper> perhaps
[06:16] <thumper> however I'm EODing now
[06:16] <wgrant> But emails use it now, don't they?
[06:16] <thumper> wgrant: revision emails? yes
[06:17] <thumper> actually... the response time from the post leads me to think a job would be better
[06:17] <wgrant> Right.
[06:19] <mwhudson> should be a job
[06:19] <mwhudson> created by the scanner i guess
[06:20] <mrooney> well, the hookah library does it asynchronously so if that was used, a lot of the problems are taken care of like that, retrying with timeouts, et cetera
[06:20] <thumper> mwhudson: abreed
[06:20] <thumper> agreed
[06:20] <thumper> mrooney: there is a lot of infrastructure in LP that you'll soon learn about :)
[06:21] <mrooney> how fun :)
[06:21] <mrooney> if you think branch is easier to land, I'm fine with looking at that first
[06:21] <thumper> mrooney: I've updated the bug and offered mentorship (never done that before)
[06:21] <mrooney> hooray
[06:21] <thumper> mrooney: it is going to need a db patch
[06:21] <mrooney> yeah
[06:21] <thumper> mrooney: and that always takes more to get in
[06:21] <thumper> mrooney: but I can help with that too
[06:21] <mrooney> I think there will be some cool project wide hooks though that can be done
[06:22] <thumper> mrooney: first step, get the code
[06:22] <mrooney> a hook to call on a new branch creation for example, that would be neat
[06:22] <mrooney> okay, I'm throwing some more info in the description
[06:22] <mrooney> have you added anything that I'll stomp over?
[06:22]  * thumper is done for the day
[06:22] <thumper> mrooney: no
[06:23] <thumper> mrooney: I add comments, not updated the description
[06:23] <thumper> ciao
[06:23] <mrooney> good night, thanks for your help and suggestions, hopefully we can work together soon :)
[06:30] <wgrant> What's the replication lag threshold?
[06:31] <wgrant> And are there two replicas?
[06:31] <wgrant> I'm seeing some very inconsistent data here.
[06:31] <wgrant> Some of which makes no sense.
[06:32] <wgrant> Some of it is explained by replication issues (eg. the build page reporting that the build has not yet started, while the builder says otherwise), but other stuff isn't (eg. build start timestamps moving around as I refresh the page).
[06:33] <wgrant> See, now the build page says that it has been building for 7 seconds, when I first saw it hit the builder more than three minutes ago.
[06:35] <wgrant> Hmmm. Maybe the i386 buildd I hit is just broken and keeps dieing quickly and silently.
[06:35] <wgrant> Aha, the build has finally stuck.
[06:38] <mrooney> Man the automated translation export is so cool and exciting
[06:39] <mrooney> combined with automated import, Launchpad is basically an automated magical translation factory
[06:39] <wgrant> An open source one, too.
[06:40] <mrooney> yeah but things are more magical if you don't look at the source :)
[06:54] <mrooney> now it just needs to create a template automatically and I will be blown away
[06:55] <mrooney> it seems pretty doable, just run xgettext on the file pattern of the users choosing
[06:56] <wgrant> I'm not sure that template autogeneration is a good idea...
[06:56] <mrooney> oh? why's that?
[06:57] <wgrant> Good question.
[06:57] <wgrant> I can't actually see much wrong with it, except that it's always been done the other way.
[06:58] <wgrant> Which I presume there's a reason for.
[06:58] <mrooney> I think the reason is because there isn't yet a solution. Most repositories are passive things which sit there and hold your files.
[06:59] <mrooney> Until you have a system like Launchpad to do it for you, that's the only way to do it
[07:00] <mrooney> generate the template, find translators, give them template, collect translation files, integrate them. Those are the steps, basically
[07:00] <wgrant> LP would then automatically commit the template too?
[07:00] <mrooney> Launchad has now basically automated all but the first, right?
[07:00] <mrooney> Maybe.
[07:01] <mrooney> Do you even need the template in your code?
[07:01] <mrooney> It is autogenerated so there's no information loss to not have it. Couldn't LP store it internally wherever it currently does for Rosetta?
[07:02] <mrooney> From a programmer's perspective when you wrap your strings with gettext, you are saying, "I want translations for these strings". So I don't see why you couldn't have something smart enough to hide the stuff you don't care about, and just deliver translations
[07:27] <poolie> wgrant: i'm wonder what you think of bug 407189
[07:28] <wgrant> poolie: I wondered that myself.
[07:28] <wgrant> I'm not sure.
[07:28] <wgrant> It's hard.
[07:54] <noodles775> Hey poolie, thanks for the feedback re. ppa-index ideas. I was wondering whether you got to take a look at the new mockup? I tried to ensure that it deals with a number of your points?
[07:54] <poolie> thanks for listening
[07:54] <poolie> i hadn't clicked the new one yet but i can look now
[07:54] <noodles775> Thanks! https://dev.launchpad.net/VersionThreeDotO/Soyuz/PPAUI#Idea%202.%20Re-focusing%20the%20purpose
[07:56] <poolie> noodles775: it looks nice
[07:57] <mrooney> dear launchpad, I honor your achievements with this blog post: http://mrooney.blogspot.com/2009/07/launchpad-is-now-automatic-magical.html
[07:57] <poolie> I really like the top part, including
[07:57] <poolie> the "owned by %s"
[07:57] <poolie> mpt would point out that "read about installing" is a poor hyperlink text :)
[07:57] <noodles775> Yeah, kinda necessary when people can name their PPA "Official Mozilla Security PPA" if they like.
[07:58] <noodles775> Yes, I' just used what's on the current one... good point. I'll update it.
[07:58] <poolie> so i can see where you're going but i still have concerns about the "currently updates only ..."
[07:58] <noodles775> Yes, I'd done this version before your latest email...
[07:58] <poolie> firstly that it's just a point-in-time thing
[07:59] <poolie> and also that even for quite well focussed ppas there might just be quite a few packages
[07:59] <poolie> most of which the user doesn't care about or recognize
[07:59] <noodles775> what would be the problem when there were, say, 15 pkgs?
[07:59] <poolie> because packages are smaller than the end user's idea of applications
[08:00] <poolie> i guess basically i don't understand what this gives you beyond the package list down the bottom
[08:02] <noodles775> The aim was that it summarises information for a decision. Ie. if there were 15 pkgs, it would say "This PPA updates 15 packages on your system. You can browse those packages below and subscribe to be notified of new packages..blah"
[08:02] <poolie> sounds a bit like filler to be frank
[08:02] <noodles775> So I guess it is only ever summarising information that is present in the table.
[08:02] <noodles775> Yeah, ok. You're not the only one to question the duplication :)
[08:03] <poolie> how about instead: make it obvious that your can subscribe
[08:03] <poolie> make it obvious what the packages are
[08:03] <poolie> and use the space maybe for some stats like
[08:03] <poolie> 15 packgase
[08:03] <poolie> 23 uploads in the last month
[08:03] <poolie> 4 packages building and 3 waiting to build
[08:04] <poolie> oh, and i'll tell you what, the nice thing is that the build counts gives you a nice way to show developers what happened to their stuff
[08:04] <poolie> without necessarily having a portlet
[08:04] <noodles775> Great idea (the building stats will be present for owners/admins etc. already - see the note on the mockup).
[08:05] <noodles775> Hmm... were you against the build-summary-status only displaying for owners/admin etc.? (see note bottom left of mockup.)
[08:05] <poolie> because one of the issues you have to struggle with here is that you fire off with dput and then things become a bit invisible
[08:05] <poolie> i am against that actually
[08:05] <noodles775> Yep, as in you think it should always be visible?
[08:05] <poolie> i think generally, everyone should see the same page unless there's a good reason otherwise (like private data etc)
[08:06] <poolie> otherwise you get this "that's funny, why can't you see it" reaction
[08:06] <noodles775> Yes, good point.
[08:06] <poolie> mm
[08:06] <poolie> and it seems possible that there'll be an interaction like this
[08:06] <poolie> dev: ok i've uploaded a fix to the ppa, please try it
[08:06] <poolie> user: i can't see it
[08:07] <poolie> well, this will probably happen anyhow, but at least showing that stuff is building or waiting may help
[08:07] <noodles775> Why wouldn't they be able to see it? (ie. the latest uploads with their state?)
[08:07] <poolie> my mistake, they would see it there
[08:07] <noodles775> ah ok.
[08:08] <poolie> oh, the other big reason why people should see data they we don't expect them to use in this context -
[08:08] <poolie> it helps them learn what the system can do
[08:08] <noodles775> +1
[08:08] <poolie> people will probably see someone else's ppa before they create their own
[08:09] <noodles775> Great... thats excellent feedback, thanks! Anything else? (I'll try to do a v3 sometime later today).
[08:09] <noodles775> s/thats/that's
[08:09] <poolie> so the thing i meant by a timeline view is something like this - above or below the package list, have something a bit like a bug activity view
[08:09] <poolie> with items like
[08:10] <poolie> firefox-3.5-thoaeu-1234124-1234-124 by _Martin Pool_ at 2009-07-31 12:22 **waiting to build**
[08:10] <poolie>  * firefox now starts much faster
[08:10] <poolie>  * no more bugs
[08:11] <noodles775> OK - so people can see what changed in the latest upload, yeah, that is helpful info.
[08:11] <poolie> so then it's like an overall changelog for this ppa, not a timeline of builds as such, but a timeline of packages, including the current state of those uploads, whether they succeeded, failed or whatever
[08:11] <poolie> right, and so you get a sense of what kind of work's being done here
[08:12] <poolie> hm
[08:12] <poolie> i wonder if "You can update your system" is making too much of an assumption people are running karmic?
[08:12] <poolie> some people on Windows will find these pages through a google search :)
[08:12] <poolie> hilarity ensues :)
[08:13] <noodles775> heh, yes, we could make that "You can update your Ubuntu <distroseries> ..." when we autodetect...
[08:13] <poolie> more seriously people on jaunty will probably get stuck
[08:13] <noodles775> and present something else when it' pre-karmic that is more direct.
[08:13] <poolie> also remember people may be browsing from one system but ssh'd to another
[08:14] <poolie> so of course you need a way around autodetection
[08:14] <noodles775> Yes, but those people would surely know to look at the technical details (key/apt-get url), don't you think?
[08:27] <poolie> yes, as long as there's a drop-down to get the right system within that it's fine
[08:39] <sianis> hi
[08:39] <sianis> https://code.launchpad.net/~mvo - this page gives me timeout all day
[08:40] <wgrant> sianis: Known bug, and it's hopefully fixed. Try https://code.edge.launchpad.net/~mvo instead.
[08:40] <sianis> wgrant: thx
[08:44] <sianis> https://code.edge.launchpad.net/~mvo/ddtp-ubuntu/ddtp-ubuntu - why didn't launchpad put translations here?
[08:44] <wgrant> That's amusing.
[08:48] <wgrant> It could also do with having its whoami configured properly...
[09:08] <wgrant> sianis: The code seems pretty clearly right. I wonder if the right series is setup up for commits.
[09:35] <didrocks> dpm: to add new language available to be translated, even with the automatic launchpad import, do I have to add new blank .po file or can the user say "I want to translate in this language!" (https://translations.launchpad.net/quickly)
[09:37] <dpm> didrocks: if I'm not mistaken, you don't have to do anything, the user can easily create the new translation in the following way: depending on the language selected on his/her LP profile, only the translations for/his/her language will be shown in the +translate page, so even if the translation is empty, he/she should be able to create one with simply entering the first translation. jtv might be able to tell you more, but in fact, we can try this just no
[09:37] <dpm> wgrant, I'll create the Catalan translation :), give me a sec...
[09:38] <jtv> no need to create anything at all.
[09:38] <jtv> exactly what dpm said
[09:38] <didrocks> dpm: awesome, thanks for the clarification :)
[09:40] <didrocks> ok, it works. I added a new language to my profile and I can see it
[09:40] <didrocks> I just have now to see why it doesn't work this branch for automatic exporting translation: ~quickly/quickly/quickly-po
[09:41] <jtv> didrocks: what's not working?
[09:42] <dpm> didrocks: there you go, you should now have a Catalan .po file as well (it's not finished, I've just translated a few strings). Regarding automatic translation exports, jtv is the one to talk to
[09:42] <didrocks> dpm: yes, I can see it, thanks :)
[09:43] <didrocks> jtv: I try to add it to this page: https://translations.edge.launchpad.net/quickly/0.x/+link-translations-branch
[09:43] <didrocks> I just get "There is 1 error"
[09:44] <jtv> didrocks: did you pick the branch from the "Choose..." picker?
[09:44] <sianis> wgrant: mvo reviewd the settings, coldy you or somebody run an export again?
[09:44] <didrocks> jtv: I can't find it as well from the "Choose..." picker
[09:45] <didrocks> jtv: but the branch exists: https://edge.launchpad.net/~quickly/quickly/quickly-po
[09:46] <jtv> didrocks: team-owned branches don't quite work yet.  :(  Can you make yourself the owner of the branch, then set it as the translations branch, then make the team the owner again?
[09:47] <didrocks> jtv: this workaround works well. Thanks! Something to put in a FAQ ;)
[09:48] <jtv> didrocks: something to fix.  :(
[09:48] <didrocks> also :)
[09:48] <didrocks> (but in the meanwhile)
[09:48] <didrocks> jtv and dpm : thanks for your support
[09:48] <jtv> didrocks: no worries, hope you enjoy the feature.  Let me know if there's anything else.
[09:48] <dpm> didrocks: np, you're welcome :)
[09:49] <didrocks> jtv: I will! It seems to be a really cool feature (rosetta is the "unkown part of launchpad" where I didn't get until now)
[09:52] <jtv> didrocks: I've updated the blog post to link to the bug.
[13:20] <thekorn> hi, the graphs in the 'last modified' column of code overview pages like https://code.edge.launchpad.net/zeitgeist are all the same,
[13:20] <thekorn> is this an already known issue?
[13:22] <thekorn> nm, found it, it's bug 407006, did not know they are called sparklines ;)
[14:11] <wgrant> cprov: I ran into some strange build issues earlier this evening.
[14:12] <cprov> wgrant: can I see the buildlog ?
[14:12] <wgrant> cprov: Not an issue inside the build. It was very strange.
[14:12] <wgrant> Basically, an i386 got dispatched to aluminium several times.
[14:12] <wgrant> Each time, it sat building for 30ish seconds.
[14:12] <wgrant> Then restarted silentl.
[14:13] <cprov> wgrant: maybe because aluminium wasn't able to fetch the chroot+files in time?
[14:13] <wgrant> After about 6 minutes of trying, it finally caught and built fine.
[14:13] <cprov> wgrant: in those cases the UI lies for few seconds ...
[14:13] <RainCT> Hey
[14:14] <cprov> wgrant: were you able to view any relevant part of the buildlog tail (on the builder page) ?
[14:14] <wgrant> cprov: There wasn't any.
[14:14] <wgrant> cprov: I suspect the slave was still resuming.
[14:15] <RainCT> https://code.edge.launchpad.net/~thekorn/zeitgeist/flexible.engine.backend/+merge/9499 -I'm wondering, what does the "(community)" there mean?
[14:15] <cprov> wgrant: exactly, resuming or trying to fetch build files, then timed out
[14:15] <wgrant> cprov: So that's expected behaviour?
[14:15] <cprov> wgrant: they are blindly reset, in those circumstances
[14:15] <cprov> wgrant: not ideal, but yes, expected.
[14:15] <wgrant> cprov: OK, thanks.
[14:16] <cprov> wgrant: we should move the job to the next builder, I guess.
[14:16] <cprov> wgrant: it happens 'by accident' when the queue is full
[14:16] <wgrant> cprov: What do you mean?
[14:17] <wgrant> RainCT: It means something is broken, as it thinks you're not a member of the target's review team, when you clearly are.
[14:17] <wgrant> RainCT: I've seen this problem in a couple of other places.
[14:17] <cprov> wgrant: it seems that some builders don't cope with the timeouts we established for some periods
[14:18] <cprov> wgrant: after some time, they work normally, it's a race on resuming, I suspect.
[14:18] <wgrant> cprov: Right.
[14:18] <wgrant> So, it didn't cause any problems, but was really confusing while watching the build.
[14:19] <wgrant> Started 30 seconds ago... refresh... started 2 seconds ago...
[14:19] <cprov> wgrant: yes, it's very WTF, because the master keeps hammering a builder that is not working while the others are IDLE
[14:20] <RainCT> wgrant: ok then, just making sure you know about it :)
[14:20] <wgrant> RainCT: I'd file a bug, so Code people can look at it.
[14:29] <RainCT> ok, done (#407347), thx
[14:39] <ronny> whoever manages the bzr overlay for gentoo on lp - he failed at making it accessible to the rest of the world
[15:42] <NCommander> Can an LP admin bump the size of mp PPA
[15:43] <NCommander> *my
[15:48] <jpds> NCommander: It would probably be best to file a question against Launchpad so that they can track the request.
[15:49] <deryck> NCommander, yes, what jpds said.  File a question, and I can get it assigned for you.
[15:50] <NCommander> deryck, which project should I file it again
[15:50] <NCommander> *against
[15:52] <deryck> NCommander, https://answers.edge.launchpad.net/launchpad-project
[15:53] <NCommander> deryck, https://answers.edge.launchpad.net/soyuz/+question/78744
[15:59] <deryck> NCommander, it's assigned now, and the appropriate group pinged.
[16:25] <aboSamoor> Hi, I am trying to login to stackoverflow using launchpad open id, I did not use stack overflow for more than 6 months. It is not working it wants to create new user my launchpad open id !
[16:33] <aboSamoor> Hi, I am trying to login to stackoverflow using launchpad open id, I did not use stack overflow for more than 6 months. It is not working it wants to create new user my launchpad open id !
[16:38] <aboSamoor> can anyone help me ?
[16:44] <epsy> http://bazaar.launchpad.net/~armagetronad-dev/armagetronad/config_tournament_server/annotate/head%3A/ladle.cfg
[16:44] <epsy> what happened there?
[16:45] <aboSamoor> epsy, do you know who can I ask regarding open id support ?
[16:45] <deryck> aboSamoor, I haven't logged into stackoverflow before, but don't you have to associate your account on stack overflow with your LP account?
[16:45] <epsy> what are you trying to do?
[16:46] <epsy> ah, stackoverflow is a website?
[16:46] <deryck> aboSamoor, my guess is it wants to create a new stack overflow account because the site doesn't know which account your open id relates to.
[16:49] <aboSamoor> deryck, I created an account in SO using launchpad openid, what I can remember that my id was id.launchpad.net/~rmyeid and after a while it changed launchpad.net/~rmyeid and I can not access my account again !
[16:50] <deryck> aboSamoor, what is your user name on Launchpad?
[16:50] <aboSamoor> deryck, rmyeid
[16:52] <deryck> aboSamoor, and when you went to SO did you try to provide -- https://launchpad.net/~rmyeid -- as your open id login?
[16:54] <aboSamoor> deryck, I tried and it gives me that it is the first time so it will make a new user account !
[16:55] <deryck> aboSamoor, Stack Overflow tells you it is your first time and wants you to create a new Stack Overflow account?  Is that correct?
[16:56] <aboSamoor> deryck, yeah
[16:56] <deryck> aboSamoor, yeah, this is what I was saying earlier.  Stack Overflow doesn't associate your open id with any account that they have.  I'm not sure why that is, but it's on Stack Overflow's end, not Launchpad's.
[16:58] <aboSamoor> deryck, sorry, I am not that technical person what do you suggest to do ?
[16:59] <mhall119|work> help!
[17:00] <deryck> aboSamoor, I think you need to contact someone with Stack Overflow about the problem.
[17:00] <mhall119|work> okay, I uploaded a source package which finally (after some tweaking) was accepted, but the build failed because I lacked build-depends
[17:00] <mhall119|work> so, I added the build-depends, but now I can't get the package accepted again
[17:00] <mhall119|work> this is the email I get: http://paste.ubuntu.com/239489/
[17:01] <mhall119|work> do I need to change the version number and re-submit?
[17:02] <mhall119|work> my only changes were to debian/control
[17:02] <aboSamoor> deryck, thanks very much I will use IRC conversation to explain the problem to the SO guys :)
[17:12] <deryck> mhall119|work, does the info here help:  https://help.launchpad.net/Packaging/UploadErrors  ?
[17:15] <mb74> please can someone tell me how to make a kernel-package whic
[17:16] <mb74> which can be uploaded to launchpad?
[17:16] <mb74> how do i have to setup make-kpkg?
[17:18] <mhall119|work> deryck: nope
[17:18] <mhall119|work> deryck: I had it working previously, up to the point where it tried to build a binary
[17:18] <mhall119|work> I'm trying to fix the build now
[17:20] <mhall119|work> my ppa setup is right, my gpg keys are right
[17:20] <mhall119|work> it just doesn't like me uploading the package again
[17:20] <mhall119|work> changing the version in debian/changelog has allowed it
[17:20] <mhall119|work> do you have to change the version every time a build fails?
[17:23] <deryck> mhall119|work, sorry, soyuz isn't my area.  Maybe cprov could help explain?
[17:24] <maxb> mhall119|work: You can retry a failed build through the web interface. If you want to change the source in any way whatsoever, then yes you need to increment the version.
[17:24] <mhall119|work> maxb: is the debian/control file considred source?
[17:25] <maxb> Of course it is - it's part of the source package you upload
[17:25] <mhall119|work> ok
[17:25] <mhall119|work> so, what would be the point in retrynig a build through the web interface, if nothing has changed?
[17:26] <mhall119|work> presumably if it wouldn't build the first time, trying again without fixing anything will cause it to fail the second time
[17:31] <mhall119|work> are there any good tutorials covering how to handle meta-packages and non-code packages?
[17:32] <maxb> mhall119|work: A build may fail because of an issue with a package that it depends on. After that dependency is fixed, the build may be able to retry successfully
[17:32] <mhall119|work> ah, okay, that makes sense
[17:32] <mhall119|work> thanks for taking the time to explain all this to me maxb
[17:33] <maxb> mhall119|work: I'm not sure how you'd write a tutorial on meta-packages or non-code packages. They're really just packages that happen to be of certain kinds
[17:40] <mhall119|work> maxb: I meant, what do I do with debian/rules when nothing is being compiled?
[17:41] <mhall119|work> like, if I just have a GDM theme and other artowkr
[17:42] <maxb> mhall119|work: If you think about a debian/rules file, it does other things than compile the package. So you do all the rest, you just don't compile anything
[17:42] <maxb> There is https://wiki.ubuntu.com/MOTU/School/PackagingWithoutCompiling
[17:42] <mhall119|work> thanks
[17:43] <mhall119|work> ah, that looks like exactly what I'm looking for, thanks again maxb
[17:44] <mhall119|work> okay, I'm going to lunch while I wait for launchpad to compile my package
[17:45] <cprov> maxb: thanks for helping mhall119|work ... perfect explanation, as usual.
[17:47] <mhall119|work> yes, maxb deserves a raise for that
[17:47] <maxb> :-)
[17:47] <rafiu> any Launchpad Bugs devs around? need to migrate tickets from trac to LP (i have xml conversion ready)
[17:48] <mrevell> rafiu: gmb is the person to speak to but he's having some IRC issues, AFAIK
[17:49] <gmb> rafiu: Hi. As mrevell says my connection is a bit unstable at the moment. Normally I deal with bug imports but I'm going to be unavailable next week. Are you happy to wait until the week after that or would you rather get it done sooner?
[17:52] <mb74> nobody here who can tell me how to create a kernel source package for uploading to launchpad?
[17:53] <maxb> mb74: It's a fairly specialised topic
[17:54] <aboSamoor> what are the ubuntu websites that use openid ?
[17:54] <maxb> I assume from the way you're asking that "take the existing ubuntu source package and modify it" does not suit you
[17:54] <maxb> aboSamoor: several different wiki installations, REVU, ...
[17:55] <aboSamoor> maxb, I just discovered that ubuntuforums accept launchpad openid, I meant to ask if brainstorm, launchpad itself accept openid ?
[17:56] <maxb> launchpad itself provided openid identities for its registered users, but does not itself accept external openid identities
[17:57] <maxb> erm, I mean provides, not provided
[18:01] <SamB> yeah
[18:01] <SamB> I use mine to comment on Precocious ;-)
[18:02] <rafiu> gmb: if it's not going to put you out too much, the sooner the better
[19:04] <mhall119|work> just wanted to say thanks again to maxb, I got my first binary packages built and in my PPA
[20:33] <mhall119|work> is lpia the ARM arch?
[21:45] <geser> mhall119|work: no, lpia = low-power intel architecture, it's similar to i686
[21:45] <mhall119|work> oh, ok


[06:29]  * ojwb wonders how to get mythtv to realise tvnz6 has been replaced by u
[06:30] <ojwb> i seem to get u schedules but listed under tvnz6
[09:03] <Hoggs> ojwb: Have you tried turning it off and on again?
[09:57] <ojwb> Hoggs: in fact I have
[09:58] <ojwb> also tried running --configure on the grabber
[11:20] <hads> ojwb: Use mythweb to edit the channel xmltvid to u.freeviewnz.tv and change the name.
[11:21] <hads> And edit your ~/.mythtv/$SOURCE.xmltv to replace the tvnz6 line with u
[17:53] <ajmitch> morning
[18:58] <ibeardslee> morning
[19:20] <Atamira> mornin
[19:56] <chilts> morning
[20:18] <mwhudson> morning
[21:19] <thumper> morning


[08:34] <elacheche> Morning!
[08:50] <Dro> Morning!!
[08:59] <davlefou> Bonjour, vendredi matin, glace au café!
[09:10] <elacheche> :)
[09:10] <Dro> vendredi glace, café c'est tout
[09:38] <elacheche> Guys! I'll animate a Docker Workshop next weekend during an event orgnized by FREEWAYS.. I'm doing it as Ubuntu-tn member.. I'm waiting for the event official announcement to share the news on the ML..
[09:39] <elacheche> It's not a u-tn event, they just came to me asking for a docker workshop and I told them that I'll be doing it as a U-tN member, not other title(s)
[13:48] <nzoueidi> Cool elacheche :D
[13:48] <nzoueidi> Where the event will be held?
[13:50] <elacheche> Afaik, sesame university.. I'll share the info on the ML as soon as it'll go public with all the needed info..
[14:08] <nzoueidi> Alright