[03:36] <mRMans> ping wgrant  when you are back and got a second.  It is about using 14.04 for building lp compared to to 12.04 and changing the apache conf files
[05:37] <wgrant> mRMans: Launchpad doesn't run on Ubuntu 14.04 LTS today.
[05:37] <wgrant> There are Apache config incompatibilities plus some other issues.
[05:37] <wgrant> We recommend Ubuntu 12.04 LTS instead.
[05:40] <mRMans> wgrant,  hello
[05:40] <mRMans> I made a LXC that is 12.04 and built but can not seem to get it in a browser
[05:40] <mRMans> last thing that I did was make run
[05:41] <mRMans> and it is hanging at 2014-12-21T22:22:51 INFO root Startup time: 8.001 sec real, 7.720 sec CPU
[05:41] <wgrant> That indicates that startup is complete.
[05:41] <mRMans> yeah but I can not see it in a browser on local or portforwarding via tomato
[05:41] <wgrant> "can not see it"?
[05:41] <wgrant> What exactly are you trying, and what goes wrong?
[05:42] <mRMans> meaning that It can not load in the browser
[05:42] <mRMans> just says connecting and never does
[05:42] <wgrant> Load what?
[05:42] <mRMans> google chrome tools says that it is just waiting to resolve
[05:42] <wgrant> What's the URL you're using?
[05:43] <wgrant> Have you set your /etc/hosts?
[05:43] <mRMans> looking at etc host in the LXC now
[05:43] <mRMans> thanks wgrant for your time
[05:43] <wgrant> If it's hanging on name resolution, that suggests your /etc/hosts is misconfigured.
[05:43] <wgrant> Which URL were you using?
[05:44] <mRMans> the name of the lxc container
[05:44] <wgrant> Ensure you've followed https://dev.launchpad.net/Running/RemoteAccess
[05:44] <mRMans> lpNew
[05:44] <mRMans> yeah
[05:44] <wgrant> You need to use a correct hostname.
[05:44] <wgrant> Launchpad uses vhosts extensively.
[05:44] <wgrant> So it'll want to be launchpad.dev.
[05:45] <mRMans> ok
[05:45] <mRMans> yeah I tried to point the browser to http://lpNew:8087/ but get nothing looking at hosts now
[05:45] <wgrant> 8087 is only a local port
[05:45] <mRMans> looks like this
[05:45] <wgrant> 80 and 443 are the interesting ones.
[05:45] <mRMans> 127.0.0.88      launchpad.dev answers.launchpad.dev archive.launchpad.dev api.launchpad.dev bazaar.launchpad.dev bazaar-internal.launchpad.dev blueprints.launchpad.dev bugs.launchpad.dev code.launchpad.$
[05:45] <wgrant> Right.
[05:46] <wgrant> Put that in your system's /etc/hosts, except with the container's IP address rather than 127.0.0.88
[05:46] <mRMans> that is ok if it is only local I have someone at the office ATM
[05:47] <mRMans> so you are saying replace 127.0.0.88 with the avahi name ? example:  <lxc host name>      launchpad.dev answers.launchpad.dev archive.launchpad.dev api.launchpad.dev bazaar.launchpad.dev bazaar-internal.launchpad.dev blueprints.launchpad.dev bugs.launchpad.dev code.launchpad.$
[05:47] <wgrant> No, normal /etc/hosts format.
[05:47] <mRMans> ok
[05:47] <wgrant> The first field is the IP address.
[05:48] <wgrant> The following fields are hostnames that should resolve to that IP address.
[05:50] <mRMans> If i just point my browser to 127.0.0.88 or any of the host names then I still got "nothing" back in the browser
[05:50] <mRMans> restart the lxc networking ?
[05:50] <wgrant> 127.0.0.88 on 127.0.0.0/8 -- it's a loopback address, valid only within the container.
[05:51] <mRMans> ohh
[05:52] <mRMans> cigarettes coffee and beer oh my ! Thanks wgrant
[05:52] <wgrant> :)
[05:52] <mRMans> wgrant is there a blueprint for lp-dev in 14.04 ?
[05:52] <mRMans> what is the main issues ?
[05:52] <mRMans> besides apache 2.4 that is
[05:53] <wgrant> The main issue is the Apache config, but I believe there are also some other minor bits and pieces that will be broken. We do not run the test suite on 14.04 yet.
[05:53] <mRMans> is there a sprint ?
[05:54] <wgrant> A sprint?
[05:55] <mRMans> like a sprint to get it done by a certain time
[05:56] <mRMans> or a milestone maybe it is called
[05:57] <wgrant> Launchpad.net won't be upgraded from 12.04 for at least several months, so I can't give a definite timeline.
[05:57] <mRMans> Also last question is there armhf that I could build as a lot of my in-house packages are armhf
[05:57] <mRMans> odroid stuff ^^
[05:58] <mRMans> like in the LXC can I just pass -a armhf ? seems to error out
[05:58] <mRMans> s|LXC| LXC build|g
[05:59] <mRMans> I was using reprepro wannabuild and buildd before trying to move to LP
[05:59] <wgrant> A local Launchpad instance is a lot of work to maintain. And you can't run a buildd in an LXC containre.
[06:00] <wgrant> But you can create cross-architecture containers.
[06:00] <mRMans> Cool !
[06:00] <mRMans> so like a mounted chroot then
[06:00] <mRMans> with g++ ect
[06:00] <mRMans> or am I going down the wrong path ?
[06:01] <wgrant> What exactly are you trying to do?
[06:01] <wgrant> Running a local Launchpad instance is probably not the easiest way to achieve your goal.
[06:02] <mRMans> I want to use dput or something like that to build all armhf i386 amd64 and ppc builds of everything on a cron or something
[06:02] <mRMans> of the in-house packages
[06:03] <mRMans> like openzwave stuff a lot of Qt Libs that I have made.  Some backup ec2 scripts ect
[06:04] <mRMans> so that end users can use PPA for there systems and I do not need to use crons to update the packages.  As that is whta is going on atm
[06:04] <mRMans> what *
[06:05] <wgrant> Why did you need cronjobs if you were using reprepro already?
[06:05] <mRMans> to run checks on incoming
[06:05] <wgrant> Launchpad PPAs and reprepro repositories are just normal apt repositorys. There's nothing particularly special about PPAs.
[06:05] <wgrant> Ah
[06:05] <wgrant> Well, you have to do that with Launchpad too :)
[06:07] <mRMans> I see
[06:07] <wgrant> What improvements do you want over your current reprepro+wannabuild+buildd infrastructure?
[06:08] <mRMans> how do you trigger with upload to say build/launch a new LXC to build a package from something like ubuntu-minimal ?
[06:08] <wgrant> Launchpad.net provides private PPAs as a commercial service, which would certainly be much easier for you. But running your own Launchpad is a complicated endeavour.
[06:08] <wgrant> We don't build in LXC containers.
[06:08] <mRMans> bugs translations and many other things
[06:08] <wgrant> Launchpad.net builds packages with launchpad-buildd, which handles chroots itself.
[06:09] <mRMans> there is also jenkings running for all the Java stuff that we do. I want to merge into one framework
[06:09] <mRMans> but that also means lots of debian dirs
[06:10] <mRMans> with config ect files
[06:10] <mRMans> kinda trying to see if there is anything that can "do it all"
[06:10] <wgrant> Launchpad doesn't maintain your debian directories for you.
[06:11] <mRMans> also needs to be for debian and Ubuntu
[06:11] <wgrant> You still need to create the source packages.
[06:11] <wgrant> Ah, Launchpad.net cannot build packages for Debian today, just Ubuntu.
[06:11] <wgrant> But a local Launchpad instance could do Debian as well, if you have the expertise.
[06:12] <mRMans> aka make debootstrap debian and Ubuntu as we were using just Ubuntu but (no offense) but maintaining debian seems to be a little bit easy.
[06:12] <wgrant> Howso?
[06:13] <mRMans> like when I got the job and looked at servers and embeded systems there was no "common theme" example some were raring some were lucid
[06:13] <mRMans> lots of upgrades
[06:13] <wgrant> Anybody distributing a system with a non-LTS release is probably wrong :)
[06:13] <wgrant> Unfortunately many ARM vendors do that :(
[06:14] <mRMans> everything is now trusty that was once whatever which is nice.  But Have spun up my own armhf debian jessie and wheezy
[06:14] <mRMans> Your telling me ROTFLMAO
[06:14] <mRMans> would also like to automate building img also
[06:14] <mRMans> in due time
[06:16] <mRMans> but just tring to look at all the options that are out there. Looked at suse builder that mer uses and what not. Which is nice.  But would like to take all of this put it together and see what comes out of it
[06:17] <mRMans> in other words we make a lot of armhf img per week but everytime I upgrade say a simple bash script package I have to upload to builder wait for cron to run.  or every time I make a IMG .... Now that is a mess
[06:18] <mRMans> maybe I should make some sorta tool (qt or gtk ) that is used to do diff's and what not to update the img
[06:18] <mRMans> not sure how to make all that automated.