[08:40] <zetheroo> according to this ' The production Launchpad.net site runs on Ubuntu 12.04 LTS' - is this still true? https://dev.launchpad.net/Running
[08:45] <zetheroo> what I would really like to know is if a launchpad setup can be run on 14.04 or even 16.04
[09:17] <cjwatson> zetheroo: Yes, it's still true at the moment for various reasons, but at least 14.04 should mostly work.
[09:22] <zetheroo> cjwatson: ok, but 16.04 would be too new ?
[09:34] <cjwatson> zetheroo: I don't have definite information on that.
[09:35] <cjwatson> It may well be OK, but I haven't tested.
[09:36] <zetheroo> I tried it just now and it didn't go so well http://paste.ubuntu.com/23123491/
[09:36] <zetheroo> so I am giving 14.04 a shot now
[09:38] <cjwatson> Ah, certainly some of the dependent PPAs may not be ready .
[09:38] <cjwatson> If you aren't ready to cope with that kind of thing, you'd be best off matching our setup.
[09:39] <cjwatson> I hope we'll at least get onto 14.04 in a few months (we have until April ...)
[09:42] <zetheroo> ok, if 14.04 doesn't do it I am back to 12.04 ;)
[09:46] <zetheroo> is 12.04 still getting security updates?
[09:47] <cjwatson> Yes
[09:47] <cjwatson> Until April
[09:50] <zetheroo> ok
[09:54] <zetheroo> so in 14.04 when I do './rocketfuel-setup' I get '-bash: ./rocketfuel-setup: Permission denied', so I try with sudo and get 'sudo: ./rocketfuel-setup: command not found'
[09:58] <cjwatson> I wouldn't have expected sudo to help, or to be desirable even if it did help.  Don't run Launchpad code under sudo.
[09:58] <zetheroo> ok
[09:59] <cjwatson> Perhaps you have the code on a noexec filesystem?
[09:59] <cjwatson> Or perhaps you didn't chmod +x it?
[09:59] <zetheroo> ach, stupid me ... yes chmod -x was the thing
[09:59] <cjwatson> +x, but yes.
[10:00] <zetheroo> yes, that :D
[10:01] <cjwatson> Now you get to wait for ages.
[10:01] <cjwatson> (Hopefully you have it in a container.)
[10:03] <zetheroo> yep, running a dedicated VM for it
[11:11] <zetheroo> at the command 'make schema' I get the following errors at the end:
[11:11] <zetheroo> psycopg2.ProgrammingError: permission denied to create role
[11:11] <zetheroo> make[1]: *** [create] Error 1
[11:11] <zetheroo> make[1]: Leaving directory `/home/launchpad/launchpad/lp-branches/devel/database/schema'
[11:11] <zetheroo> make: *** [schema] Error 2
[11:13] <cjwatson> that sounds like you might not have run utilities/launchpad-database-setup properly
[11:13] <cjwatson> (note the warning attached to it)
[11:16] <zetheroo> I did perform './utilities/launchpad-database-setup $USER' before 'make schema'
[11:17] <cjwatson> Probably worth checking output closely for errors.
[11:17] <cjwatson> It all worked fine last time I did this only a month or two ago.
[11:18] <zetheroo> http://paste.ubuntu.com/23123797/
[11:18] <zetheroo> ends with 'Looks like everything went ok.' :)
[11:18] <wgrant> zetheroo: Your POSIX user cannot be named "launchpad".
[11:19] <wgrant> Well, not with the default setup scripts.
[11:19] <zetheroo> oh, I guess that was a default and I just hit Enter
[11:19] <wgrant> Since "make schema" will try to create a postgres user called "launchpad", but launchpad-database-setup has already done that given your POSIX username.
[11:20] <wgrant> No LP setup stuff creates POSIX users, so I doubt it was a default.
[11:21] <zetheroo> the only time I recall being asked for a username was when I performed the './rocketfuel-setup' command
[11:21] <zetheroo> What is your Launchpad username? [launchpad]
[11:21] <wgrant> It was when you created the user that you're currently logged in as.
[11:21] <zetheroo> and I just hit Enter
[11:21] <wgrant> Before you ran any Launchpad setup scripts.
[11:21] <cjwatson> And that prompt is asking for your username on launchpad.net.
[11:21] <cjwatson> Which is not "launchpad".
[11:22] <zetheroo> so my local Ubuntu user cannot be 'launchpad'?
[11:23] <wgrant> Not with the default setup scripts.
[11:23] <zetheroo> ok
[11:23] <wgrant> Since launchpad-database-setup creates a postgres user matching your POSIX user, but LP expects to be able to create a "launchpad" user of its own.
[11:23] <zetheroo> is this why I had the last errors?
[11:23] <wgrant> Yes.
[11:24] <wgrant> I suspect that security.py revoked superuser privileges from the "launchpad" role.
[11:24] <zetheroo> ok, then i may as well start again with a fresh install :)
[11:26] <zetheroo> can the hostname be launchpad ? :D
[11:38] <wgrant> zetheroo: That shouldn't be a problem.
[11:38] <wgrant> I haven't tested it, but nobody's run into that before.
[11:38] <zetheroo> ok, I'll choose another hostname just to be sure
[11:49] <zetheroo> so when I am asked for my Launchpad username ... what's the benefit of placing it in here?
[11:49] <wgrant> It uses it to download code over bzr+ssh rather than http, which is usually a lot faster.
[11:49] <wgrant> http doesn't allow the server to use any intelligence.
[11:52] <zetheroo> ok
[11:59] <cjwatson> Also rocketfuel-setup sets things up so that "bzr push" pushes code branches to the right place, for when people are sending branches to us for merging.
[12:00] <cjwatson> Nowadays I think that could actually just use lp:~/launchpad etc. rather than lp:~${lpusername}/launchpad etc., but that's not how it's written at the moment.
[12:01] <wgrant> Does ~ actually work for branch lookups?
[12:01] <wgrant> That code is rather specialised.
[12:01] <cjwatson> Usually does for me.
[12:01] <wgrant> It's not often that I learn something about Launchpad.
[12:01] <cjwatson> Wouldn't swear it works in every case, but I reasonably often do bzr push lp:~/thing/name
[12:02] <zetheroo> I am totally new to all this, so it's all Greek to me :)
[12:28] <Saviq> hi, can someone please enable arm builds on ppa:jenkaas-hackers/tools? they can be virt I think
[12:30] <wgrant> Saviq: You can do that yourself on the "Change details" page.
[12:30] <wgrant> Assuming you own the PPA.
[12:37] <zetheroo> even though I put in my launchpad ID I still see this in the output : 'You have not informed bzr of your Launchpad ID ...'
[12:41] <Saviq> wgrant, yeah I don't, not an admin of that team, will grab one of them, thanks
[13:15] <zetheroo> now that it's running, ow do I access the site in a remote browser?
[13:20] <cjwatson> https://dev.launchpad.net/Running/RemoteAccess
[13:20] <zetheroo> maybe this is not what I thought it was ... I was looking for a way to host a local repository of pre-built packages
[13:20] <cjwatson> Launchpad is massive overkill for that
[13:20] <zetheroo> ok
[13:20] <cjwatson> Did you consider reprepro?
[13:20] <zetheroo> Launchpad was the first thing I tried
[13:21] <cjwatson> There are a few things of that kind of shape in the Ubuntu archive
[13:21] <zetheroo> ok, so no 'official' way
[13:22] <cjwatson> Or you could use launchpad.net to do the builds and mirror them locally
[13:23] <zetheroo> I was thinking of something like Poudriere (FreeBSD)
[13:24] <cjwatson> These days I normally just throw things at Launchpad since life's too short, but I've used sbuild and reprepro in the past.  Was a while ago.
[13:24] <zetheroo> ok
[13:24] <cjwatson> There may be a more closely-integrated thing around now.
[13:26] <zetheroo> well if launchpad can do it all ... sounds good
[13:37] <dobey> hmm, getting lots of timeouts just trying to change status on a simple bug right now
[13:37] <xnox> yeah
[13:38] <HeOS> Hello! Is there a problem with launchpad? I can't add my comment to a bug - I face the 'Timeout error' with an advice to try do it some later...
[13:40] <zetheroo> isn't the login process in launchpad kinda weird? When I want to login I am taken to this Ubuntu One site which after I login just lands me on a Personal details page with some other settings ... so then I have to manually re-enter launchpad.net into the address bar - is that how it's meant to work!?
[13:42] <zetheroo> and then when I go back to launchpad.net I see that I am still not logged in - so I click on login again and am taken back to Ubuntu One with a Personal Data Request, so I click the 'Yes, log me in' button and then it redirects back to launchpad.net and I am finally logged into launchpad. Thing is that I had to do this all before already so why do I have to authorize it again?
[13:43] <dobey> that sounds like maybe your browser did something weird
[13:49] <cjwatson> HeOS: this happens every so often due to some internal postgresql maintenance job that we haven't entirely tracked down, but it always goes away in about ten minutes
[13:49] <HeOS> cjwatson, got it, thanks.)
[13:50] <HeOS> It works fine right now.