[00:14] <wgrant> Loggerhead has been 500ing for me a lot lately.
[00:24] <thumper> mthaddon: codebounce?
[00:25] <mthaddon> thumper: no problems atm as far as nagios can tell
[00:26] <thumper> mthaddon: thanks for checking
[00:26] <mthaddon> thumper: although I did have to restart it over the weekend
[00:26] <mthaddon> (so had probably been down for a bit)
[00:29] <mwhudson> wgrant: but it works if you retry, right?
[00:29] <mwhudson> i've seen that a few times
[00:34] <wgrant> mwhudson: Eventually.
[00:35] <wgrant> It always fails immediately (so it's probably not a timeout), but sometimes works after several refreshes.
[00:35]  * wgrant has to run.
[02:21] <bjsnider> is there a config.log type thing for build failures in a ppa? i need in-depth information on why something is not building. more information than what is in the buildfailure.txt file
[02:22] <wgrant> bjsnider: You can only see what's in the log.
[02:22] <wgrant> So you'll need to get it to dump stuff to stdout/err
[02:22] <bjsnider> you mean what's in the buildfailure.txt file?
[02:23] <wgrant> The build log that Launchpad gives you.
[02:23] <bjsnider> right
[02:23] <bjsnider> i need to know during the configure check where it's looking for something and why it can't find it
[02:23] <wgrant> bjsnider: Can you not reproduce it in pbuilder or sbuild locally?
[02:24] <bjsnider> i could if i could add a ppa as a source in pbuilder
[02:24] <wgrant> You can.
[02:24] <wgrant> Just add it to sources.list.
[02:24] <bjsnider> it depends on a package that does not exist anywhere in ubuntu
[02:24] <wgrant> There might even be a commandline option for it.
[02:24] <bjsnider> what sources.list?
[02:25] <wgrant> Inside the pbuilder.
[02:25] <bjsnider> well, let's say i can do that. is there a detailed log in pbuilder?
[02:25] <wgrant> There is a commandline option to pbuilder to give you a shell in the tarball, and another to rebuild the tarball after you make changes.
[02:26] <wgrant> I would get a shell in the clean pbuilder environment, build the package with debuild -b, and then poke around in the failed build directory.
[02:26] <bjsnider> what is the -b switch doing?
[02:26] <bjsnider> oh, you mean build
[02:26] <bjsnider> i always just type "build"
[02:26] <wgrant> -b is binary-only.
[02:27] <bjsnider> well, all i need is the configure check
[02:27] <wgrant> Best to try a full build. You should always be test-building before you upload, anyway.
[02:27] <bjsnider> i try to do that
[02:29] <bjsnider> i don't see where pbuilder stores its config files
[02:29] <wgrant> Which are you looking for? sources.list?
[02:30] <bjsnider> right
[02:30] <wgrant> It's in the tarball.
[02:30] <wgrant> So you need to use pbuilder --login, plus some other option which I forget to make it save the changes afterwards.
[02:31] <wgrant> My memory is a bit hazy, as I haven't used pbuilder for a couple of years.
[02:31] <bjsnider> it'snot documented in the cloud, that i could find
[02:31] <RAOF> --login --save-after-login
[02:51] <bjsnider> wgrant, why don't you use pbuilder anymore?
[02:51] <wgrant> bjsnider: I use sbuild.
[02:51] <bjsnider> never heard of it sir
[02:51] <wgrant> It's what the buildds use.
[02:51] <wgrant> Or, similar to it.
[02:52] <wgrant> It uses LVM, so it's cheaper to start.
[02:52] <wgrant> Plus it reuses my development schroots.
[02:58] <persia> Hrm?  Doesn't pbuilder reuse the chroots as well?  I favour sbuild/schroot over pbuilder/pbuilder --login, but I didn't think they were that different in functionality.
[02:59] <wgrant> persia: I use schroot for other things than just building.
[02:59] <persia> I also.  I just thought that pbuilder --login would achieve the same, when not using --save-after-login
[02:59] <wgrant> Ah, right, but pbuilder's aren't persistent.
[03:00] <persia> Although I don't know if there is an equivalent to schroot -p
[03:00]  * ajmitch never got round to setting up schroot & sbuild properly
[03:00] <wgrant> persia: pbuilder doesn't do schroot -b either, AFAICT.
[03:00] <wgrant> And I need that.
[03:00] <persia> Ah.  I understand.  My schroot's also aren't persistent: I always use snapshots.
[03:00] <wgrant> I do too, but these snapshots often live for months.
[03:01] <persia> ajmitch, If you have LVM, and a few gig free, mk-sbuild-lv from ubuntu-dev-tools does it for you.
[03:01] <ajmitch> oh, it was put in there? useful
[03:01]  * wgrant remembers the pain of figuring it all out before mk-sbuild-lv was around.
[03:01] <ajmitch> I take it that you mean a few GB unallocated in LVM
[03:01] <ajmitch> which I don't appear to have right now
[03:02] <persia> ajmitch, well, a few gig unallocated somewhere.  Adding it to LVM isn't so much :)
[03:02] <persia> lvresize?
[03:03] <ajmitch> that takes work, including shrinking a large filesystem :)
[03:03] <ajmitch> I think I may wait until I get some new drives
[03:03] <ajmitch> 1TB drives are looking rather cheap
[03:04]  * ajmitch guesses we're getting increasingly off-topic for here
[03:05] <bjsnider> wgrant, is it possible for a configure check to failbecause althought he file it's looking for is present, that file contains a number of things not recognized, ie. it's too different?
[03:05] <bjsnider> i don't know if i'm making any sense there
[03:05] <wgrant> bjsnider: I have no idea what build system you are talking about.
[03:05] <wgrant> Anything is possible.
[03:05] <bjsnider> pbuilder
[03:06] <wgrant> That's not a build system.
[03:06] <wgrant> autoconf, SCons, distutils?
[03:06] <wgrant> s/autoconf/autotools/
[03:06] <bjsnider> in other words, let's say that i run the configure script
[03:06] <bjsnider> it finds suchandsuch.h
[03:06] <wgrant> Ah, autotools. I am running away now.
[03:07] <bjsnider> but it's supposed to check inside that file for certain things. and the file is so different from what it used to be when this program was released that the configure check fails?
[03:07] <wgrant> Quite possible.
[03:07] <bjsnider> but
[03:08] <bjsnider> when i run ./configure --prefix=/usr right here outside pbuilder or anything else everything works fine
[03:08] <wgrant> You are probably missing a build-dependency.
[03:09] <bjsnider> where, in pbuilder?
[03:09] <wgrant> In debian/control.
[03:11] <bjsnider> well, it is complaining about X11/Xlib.h being missing
[03:12] <wgrant> You need to have libx11-dev in your Build-Depends line.
[03:13] <bjsnider> if you're right i must have it installed on this system right now
[03:13] <bjsnider> and i do
[03:18] <bjsnider> wgrant, how do i generate an aclocal.m4 file?
[03:18] <wgrant> bjsnider: Probably by running aclocal.
[03:18] <wgrant> But I am deliberately ignorant of many of autotools' intricacies.
[03:18] <bjsnider> deliberately
[03:20] <bjsnider> you have nothing but bottomless contempt for anyone that would use it?
[03:21] <wgrant> Not quite.
[03:29] <micahg> how often do ppas update their package lists?
[03:29] <wgrant> micahg: You mean the Packages files on ppa.launchpad.net?
[03:29] <micahg> yes
[03:30] <wgrant> Every 5 minutes.
[03:30] <micahg> ok
[03:30] <micahg> thansk
[03:30] <bjsnider> it worked. wgrant, you are a steely-eyed missile man, sir.
[03:30] <wgrant> bjsnider: Excellent.
[03:52] <bjsnider> wgrant, is it possible to have a patch applied after make but before make install?
[03:55] <wgrant> bjsnider: If you write the rules file properly.
[03:55] <wgrant> But you probably don't want to do that.
[04:34] <bjsnider> wgrant, stupid question, but you know the numebrs at the start of a patcch file name? where do those come from? who decides what the number should be?
[04:40] <lifeless> bjsnider: whoever makes it
[04:40] <lifeless> they are usuaully ordering instructions
[05:54] <mwhudson> wgrant: has your launchpad account been fixed yet
[05:54] <mwhudson> ?
[06:00] <wgrant> mwhudson: Oh yeah, days ago.
[06:00] <mwhudson> oh ok
[06:00] <wgrant> You would have heard a lot more from me otherwise :P
[06:00]  * mwhudson grumbles about people not cc:ing feedback@ when they fix things
[06:00] <mwhudson> wgrant: yes, that's what i was thinking, good to be sure though
[06:00] <wgrant> ~d.filoni asked a few times over the weekend.
[06:01] <wgrant> And emailed feedback@ some days ago.
[06:01] <wgrant> And is still dead.
[06:01] <wgrant> mwhudson: The email hadn't been forwarded to stub at the time he fixed mine.
[06:02] <mwhudson> yeah, i see a question from him too
[06:02] <mwhudson> i'll assign it to stub
[06:17] <mwhudson> Current incident: Unable to log into Launchpad? Email feedback@launchpad.net | https://launchpad.net/ | Help contact: - | Join https://launchpad.net/~launchpad-users | Channel logs: http://irclogs.ubuntu.com | Open Sourcing: https://dev.launchpad.net/OpenSourcing
[06:17] <mwhudson> gar!
[07:26] <RenatoSilva> is there a way to give a lp branch to someone?
[07:26] <RenatoSilva> or share...
[07:26] <RAOF_> Change the owner.
[07:26] <persia> RenatoSilva, How do you mean "give"?
[07:27] <RenatoSilva> RAOF_: I can't put any value there
[07:27] <RenatoSilva> RAOF_: only my teams
[07:27] <persia> For sharing, just give them the URL, and bzr branch ought do the right thing.
[07:27] <RenatoSilva> persia: I mean to give others permission to push in the branch
[07:28] <persia> That needs a team.  Just push to lp:${team-name}/${product}/${branch}
[07:28] <RenatoSilva> persia: I'm kind of doing a starting work, then I want to yield it to other person
[07:28] <RenatoSilva> persia: any team name or do I need to create the team previously?
[07:29] <RenatoSilva> persia: it would be kind of temp team
[07:29] <persia> Well, any team to which you belong (otherwise you won't have permission to push there).
[07:29] <persia> Perhaps you don't need it.
[07:29] <RenatoSilva> persia: why
[07:29] <persia> Just do the work, then publish the branch, then let them pull the branch, and continue the work from there.
[07:29] <persia> It's only when there is parallel development that merging matters.  If it's a simple handoff, it's fairly clean.
[07:30] <RenatoSilva> persia: maybe, I just have to tell them to continue, they may think I will be responsible to finish the work
[07:30] <persia> Right.
[07:30] <RenatoSilva> persia: actually it's a small change, isn't it better to just attach a patch to the bug?
[07:30] <persia> So, when you do the handover, make them branch, and publish their branch.  Then mark yours as "Abandoned".
[07:31] <persia> RenatoSilva, Depends on the project.  Each project has different ways they prefer to receive patches.  If you're creating one, you get to determine the rules.
[07:32] <RenatoSilva> persia: bzr-java-lib
[07:32] <RenatoSilva> persia: I'll create a branch as I think they would do anyway with my patch
[07:33] <persia> The bzr guys tend to use bzr, yes :)
[07:34] <RenatoSilva> persia: I just feel a bit uncomformtable with pushing the whole lib just to publish a small change...
[07:34] <RenatoSilva> how do I query saved locations?
[07:34] <persia> The library isn't in bzr already?
[07:34] <RenatoSilva> in bzr? what do you mean?
[07:35] <persia> You're uncomfortable with pushing a whole library.
[07:35] <persia> Therefore, I presume that the library is not already in bzr, or you could push a stacked branch.
[07:35] <persia> (or if it's in bzr for non-LP, then this isn't the best place to ask)
[07:37] <RenatoSilva> persia: what does it mean "in bzr"? using bzr?
[07:37] <RenatoSilva> btw what's a stacked branch?
[07:37] <persia> Does there exist a prior bzr repository on LP for this library?
[07:37] <RenatoSilva> yes
[07:37] <RenatoSilva> I branched it
[07:38] <persia> Right.  So when you push your branch, it will stack, and you won't be pushing the entire thing.
[07:38] <RenatoSilva> Created new stacked branch referring to /~verterok/bzr-java-lib/bzr-java-lib
[07:38] <RenatoSilva> what's that?
[07:38] <persia> It means it only contains your changes, rather than the entire branch.
[07:38] <RenatoSilva> so it pushes only my revisions?
[07:38] <RenatoSilva> great!
[07:39] <RenatoSilva> persia: but if I need something like diff between the branches, then it will start accessing the main branch, right?
[07:40] <RenatoSilva> or log
[07:40] <persia> Right.  You have a copy of the main branch locally, and LP has a copy of the main branch locally, so everyone is happy.
[07:40] <RenatoSilva> ok got it
[07:41] <RenatoSilva> I mean, if the main branch is deleted or renamed, mine will be broken
[07:42] <persia> That goes beyond my understanding of LP.  Maybe.
[07:43] <RenatoSilva> ok thanks!
[07:43]  * RenatoSilva has been receiving a few server errors from lp's loggerhead these days
[07:48] <jml> what does greyed out branding on the person page imply?
[08:45] <mwhudson> jml: deactivated person i think
[08:45] <mwhudson> or more likely right now, a damaged person from the email snafu
[09:55] <wgrant> jml: It says in the title 'X does not use Launchpad'. Unclaimed, deactivated, suspended or broken person, as mwhudson says.
[10:03] <jml> mwhudson, wgrant: thanks. I noticed the HTML title eventually.
[10:07] <wgrant> Or the greyed-out image could just be the user trying to confuse you. *cough* lifeless.
[10:11] <wgrant> bigjools: Is exposing ISPR in the API feasible?
[10:11] <bigjools> wgrant: it's feasible, but why?
[10:12] <wgrant> bigjools: Uploader/maintainer information, for one thing.
[10:12] <bigjools> we can put that on the publication
[10:12] <wgrant> I guess so.
[10:13] <wgrant> Looks like bug #372704.
[10:13] <bigjools> I don't mind exposing SPR if it's really wanted, but you have to consider that it needs additional navigation, which removes some of the appeal for users IMO
[10:14] <bigjools> that should be an easy one to fix
[10:14]  * bigjools might do it today
[10:14] <wgrant> bigjools: I don't see how the extra navigation is a problem, but the additional requests might be.
[10:15] <wgrant> As much as I hate stuffing those things in ISPPH, it's certainly more efficient.
[10:15] <bigjools> well by navigation, I mean having to find a separate object
[10:16] <bigjools> and yes, there is no resource URL for them anyway
[10:17] <wgrant> It'd be great if you could do that soon.
[10:18] <james_w> http://pypi.python.org/pypi/Hatta
[10:18] <james_w> a possibility for wiki support in LP?
[10:23] <rowinggolfer> so last night, having misplaced my dev laptop, I used my son's computer. told bzr who I was, created an ssh key, and pushed some new code to the main trunk of my project.
[10:23] <rowinggolfer> this thought has struck me.....
[10:23] <rowinggolfer> perhaps I am missing something, but
[10:24] <rowinggolfer> what is there to stop someone doing exactly the same thing and pushing some malicious code into my project..
[10:24] <rowinggolfer> masquerading as myself?
[10:24] <wgrant> jml: I suspect that rather than the person in bug #394947 being a not-fully-registered account, it had its email addresses stolen last week. The user needs to be emailed manually, as LP won't be emailing them.
[10:24] <noodles775> rowinggolfer: I'm hoping you had to add your new key to your lp account first?
[10:24] <rowinggolfer> noodles775: I did.
[10:25] <noodles775> rowinggolfer: so that's what should stop someone pretending to be you... they need to have a key that only you should have...
[10:26] <wgrant> bzr does have a revision-signing feature which uses an OpenPGP key.
[10:28] <rowinggolfer> noodles775: ok... they need a key I get that.
[10:29] <rowinggolfer> but you see my point?
[10:30]  * wgrant doesn't.
[10:31] <wgrant> Your key is password-protected, and should only be on systems that you control.
[10:31] <wgrant> Same as any other credential.
[10:31] <bigjools> rowinggolfer: you logged into your LP account, nobody else can do that unless you hand over your password
[10:31] <rowinggolfer> bigjools: ah.. gotcha.
[10:32] <rowinggolfer> knew I was missing something.
[10:32] <bigjools> :)
[10:32] <rowinggolfer> registering the key is done over ssl connection...
[10:33] <rowinggolfer> thanks fellas. I am at peace again.
[10:33] <rowinggolfer> although I need to harden up my launchpad password :)
[10:47] <rowinggolfer> ok. changed my password from "password" to "PaSsWoRd". no-one will guess that ;)
[16:38] <Jeruvy> I'm having trouble downloading the CoC in ff3.5?
[16:45] <Jeruvy> ah nvm, it seems to be a plugin issue.
[16:46] <rowinggolfer> is the coc a plugin?
[16:49] <Jeruvy> rowinggolfer: no the code of conduct, its a text file.  Sorry its for ubuntu I should have mentioned that.  I confirmed nothing was downloading, so I killed all my plugins and it works.
[16:50] <rowinggolfer> Jeruvy: I have signed the coc.
[16:50] <Jeruvy> rowinggolfer: thats what I'm trying to do atm :)
[16:51] <mbt> kkubasik: Are you around?
[16:51] <RoAkSoAx> hey guys. Who has rights to upload to PPA. All members on a team or just administrators?
[16:53] <beuno> RoAkSoAx, all members of the team that owns that PPA
[16:53] <RoAkSoAx> beuno, ok awesome thanks :)
[17:04] <slayton> can you setup pbuilder to pull packages from a ppa?
[17:05] <bigjools> beuno, RoAkSoAx: and as of our next release, you can give arbitrary third parties upload permissions as well
[17:05] <RoAkSoAx> bigjools, that's perfect :)
[17:06] <bigjools> yes I know, we rock :)
[17:06] <RoAkSoAx> bigjools, any plans on restricting upload rights to members on a team?
[17:07] <bigjools> RoAkSoAx: no, there isn't.  You can work around that now with this new feature.
[17:08] <RoAkSoAx> bigjools, ok cool then
[17:46] <slayton> why the long build times on launchpad?  I just uploaded a package that says it won't build for 11 hours
[17:49] <bigjools> slayton: it looks like we're missing a few builders, I don't know why, but I expect they'll be back soon enough
[17:52] <maxb> slayton: https://launchpad.net/builders <-- as you can see there, the queue is large
[19:39] <Fauli> Hi everyone.
[19:40] <Fauli> After having used the Bazaar launchpad-login plugin, I always receive errors with bzr.
[19:40] <Fauli> bzr: ERROR: Server sent an unexpected error: ('error', "<Fault -1: 'OOPS-1284XMLP17'>")
[19:44] <Fauli> ubottu does not help me, I have no login....
[19:49] <Xhema> who can approve my translation queue here? https://translations.launchpad.net/shqipoffice/+imports
[21:04] <james_w> Fauli: hey, my hunch is that you were hit by a problem the other day that corrupted the accounts of a few people
[21:04] <james_w> Fauli: are you able to log in to the web UI ok?
[21:23] <Fauli> james_w: I will try to relogin...currently it is working fine.
[21:24] <Fauli> james_w: Yes, logging in works fine.
[21:24] <james_w> Fauli: do you have a preferred email address set?
[21:25] <RenatoSilva> How to generate a diff again for a merge proposal?
[21:26] <Fauli> james_w: "Currently you don't have a contact address in Launchpad." means I don't
[21:26] <Fauli> ?
[21:26] <james_w> I guess so
[21:26] <james_w> I suspect if you set one then you may find that it will work again
[21:27] <james_w> otherwise an LP dev may be able to tell you if you were hit by that problem and put it right
[21:30] <Fauli> james_w: Ok, I cannot select my "normal" addresses as  LP contact, just some secondary ones. If I try to add the primary ones I get a "this email address is already registered, although I cannot find it anywhere"
[21:30] <Fauli> Move that quote sign.
[21:31] <james_w> Fauli: sounds to me like you were hit by that problem then, but I'm just guessing, sorry
[21:31] <james_w> the advice that was in the topic until a few hours ago was to email "feedback@launchpad.net" if that was the case
[21:32] <Fauli> james_w: Will LP admins know what I am talking about or is there a key word I should use?
[21:32] <james_w> I'm not sure what the keyword would be, sorry
[21:32] <james_w> I'm sure they are all aware of the problem though
[21:33] <james_w> Fauli: did you file a bug on bzr about this a couple of days ago?
[21:33] <Fauli> james_w: Yes, it just vanished...
[21:34] <james_w> I thought it sounded familiar, but I can't find it either
[21:34] <james_w> that might be related
[21:34] <Fauli> https://answers.launchpad.net/launchpad/+question/76327 is what I did today.
[21:40] <Fauli> james_w: Thanks for your help I wrote an email to them.
[21:40] <james_w> np
[21:42] <mxpxpod> I don't want to sound impatient, but how would I speed up the creation of a project group?  We're trying to evaluate launchpad and it seems like the creation of our project group is taking a long time
[22:17] <qwebirc_sucks> http://bazaar.launchpad.net/~renatosilva/bzr-xmloutput/encoding-fixes/annotate/head:/tests/test_service.py --> Internal Server Error. Different machines, has been happening these days
[22:18] <beuno> mwhudson, around yet  ^
[22:18] <beuno> hrm
[22:18] <beuno> annotate seems to be broken
[22:18] <qwebirc_sucks> is it happening to you too?
[22:18] <beuno> qwebirc_sucks, yes
[22:31] <mwhudson> beuno: hello
[22:31] <mwhudson> beuno: bounce on refresh
[22:31] <mwhudson> (probably)
[23:35] <james_w> why can't I use created_since_date in a getPublishedSources call?
[23:35] <james_w> the apidoc says that I can
[23:35] <james_w> I get "ValueError: Unrecognized parameter(s): 'create_since_date'" if I try
[23:36] <LarstiQ> james_w: typo missing a 'd'
[23:36] <james_w> nice
[23:36] <james_w> thanks LarstiQ :-)
[23:36] <LarstiQ> gladly :)
[23:42] <kb9vqf> FYI, we're really down on builders today...