| dupingping | hi everyone. | 02:47 |
|---|---|---|
| dupingping | I built a launchpad.dev server on my local. | 02:47 |
| dupingping | And it shows me "Module zope.publisher.publish, line 132, in publish | 02:48 |
| dupingping | result = publication.callObject(request, obj) | 02:48 |
| dupingping | Module lp.services.webapp.servers, line 1508, in callObject | 02:48 |
| dupingping | raise NotFound(self, '', request) | 02:48 |
| dupingping | what should i do? | 02:48 |
| wgrant | dupingping: Which URL are you accessing? | 02:58 |
| wgrant | That can indicate that you're using an unrecognised domain. | 02:58 |
| dupingping | yes, at the local lan, vm server. | 02:59 |
| wgrant | Launchpad uses vhosts extensively, so you can't access it by IP address or the machine's hostname. | 03:00 |
| wgrant | You need to use https://launchpad.dev/[...], or one of the recognised subdomains. | 03:00 |
| wgrant | https://dev.launchpad.net/Running/RemoteAccess | 03:00 |
| dupingping | oh, I did not use vhost. I installed it directly on my local pc. | 03:00 |
| wgrant | The Launchpad application will only respond to domains that it knows about. | 03:01 |
| wgrant | So you need to edit /etc/hosts (or a local DNS zone). | 03:01 |
| dupingping | oh, yes, let me try now. | 03:02 |
| wgrant | eg. I run LP in an LXC container, so in my host's /etc/hosts: | 03:02 |
| wgrant | 10.0.3.45 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.dev feeds.launchpad.dev keyserver.launchpad.dev lists.launchpad.dev ppa. launchpad.dev private-ppa.launchpad.dev testopenid.dev translations.launchpad.dev xmlrpc-private.launchpad.dev | 03:02 |
| wgrant | xmlrpc.launchpad.dev | 03:02 |
| dupingping | yes, It works as http://localhost:8085 in my PC. | 03:02 |
| wgrant | utilities/rocketfuel-setup automatically configures /etc/hosts, if you used that script. | 03:03 |
| dupingping | yes, i used it, rocketfuel-setup. | 03:04 |
| wgrant | Does https://launchpad.dev/ work? | 03:04 |
| dupingping | And how to register an account on that server? | 03:04 |
| dupingping | yes, work. | 03:04 |
| wgrant | The initial dev database has certain preconfigured accounts. You can log in as eg. admin@canonical.com for an admin account, no-priv@canonical.com for an unprivileged account, and various others that can be found in the "emailaddress" table. | 03:05 |
| dupingping | yes, let me try. | 03:05 |
| dupingping | oh, It shows me an error, I'll pastebinit soon. | 03:13 |
| wgrant | Possibly an OpenID TLS cert issue, we'll see. | 03:14 |
| blr | dupingping: there's also a script for generating new accounts/users in utilities/make-lp-user | 03:16 |
| dupingping | blr, yes, let me try. | 03:17 |
| dupingping | please look, http://paste.ubuntu.com/13613443 | 03:19 |
| wgrant | dupingping: Try going back to the homepage and logging in again. | 03:21 |
| wgrant | I've seen that before on the very first session on a fresh DB, and then it works a second time. | 03:21 |
| dupingping | wgrant: yes, let me try again. | 03:22 |
| dupingping | wgrant: it's run on same PC but from another one. the launchpad.dev/+login page shows me You don't have permission to access /+login on this ... | 03:38 |
| wgrant | dupingping: Edit the ACLs in /etc/apache2/sites-available/local-launchpad | 03:39 |
| dupingping | wgrant: thank you, I did it. And I want to know how to build bootable iso image from many source packages? | 03:55 |
| dupingping | please help me. | 03:55 |
| dupingping | I just found launchpad-buildd script. I think that it's just a wrapper for debian livefs project. | 03:55 |
| wgrant | There are many steps between where you are now and bootable images. | 03:56 |
| wgrant | https://dev.launchpad.net/Soyuz/HowToUseSoyuzLocally documents some of them. | 03:56 |
| dupingping | yes, let me try, the steps. wgrant: | 03:56 |
| wgrant | dupingping: But if you're just looking to build images, a full Launchpad really isn't the easiest way to do that. | 03:57 |
| dupingping | wgrant: yes, And I think that i should build a local server same as launchpad.net to develop launchpad. | 03:59 |
| wgrant | Right, if you want to develop Launchpad then that totally makes sense. | 04:00 |
| wgrant | But I wouldn't necessarily start by building ISOs; that's a big chunk of complex infrastructure. | 04:00 |
| dupingping | wgrant: So, please help me. | 04:01 |
| wgrant | dupingping: If you want to develop Launchpad, ISO building is not a good first thing to work on. And if you just want to build ISOs, your own Launchpad is not a good way to do that. | 04:04 |
| dupingping | wgrant: yes, but I could not understand how to run the launchpad.net fully. | 04:06 |
| dupingping | And without fully understand, I could not join to develop launchpad.net | 04:06 |
| dupingping | *develop* may contribute. | 04:07 |
| wgrant | ISO building relies on all of the things described on HowToUseSoyuzLocally. | 04:07 |
| dupingping | So i wanted to fully duplicate the launchpad.net to my local PC. | 04:07 |
| wgrant | Understand all of that first, and then you can eventually move up to building ISOs. | 04:07 |
| dupingping | wgrant: yes. | 04:07 |
| dupingping | wgrant: yes. | 04:15 |
| dupingping | wgrant: what is the source build project of the launchpad.net? | 04:16 |
| dupingping | e.g. launchpad-buildd build iso image from binary packages. | 04:16 |
| dupingping | I mean that build binary packages steps. | 04:16 |
| dupingping | from source packages. | 04:17 |
| dupingping | wgrant: let's guess about following point. | 04:20 |
| dupingping | If i modified libc package, so many packages needs to be rebuilt. | 04:21 |
| dupingping | then how can i get the packages list to be rebuilt? | 04:21 |
| dupingping | to get distro iso image. | 04:22 |
| dupingping | wgrant: make sense? | 04:22 |
| wgrant | dupingping: launchpad-buildd builds several different things, including binary packages and live images. | 04:33 |
| dupingping | wgrant: yes. then it detects source depends packages? | 04:34 |
| wgrant | dupingping: A glibc change doesn't require the entire world to be rebuilt. | 04:34 |
| dupingping | wgrant: yes, right. it's just an example. If i modify a frequently used function's parameter. | 04:35 |
| dupingping | how can i detect source packages that use it? | 04:35 |
| wgrant | Launchpad has no facilities for automatically doing that. | 04:35 |
| wgrant | You'd use external tools to analyse the archive. | 04:35 |
| dupingping | external tools? | 04:36 |
| dupingping | I'm sure i can detect dependency tree of binary packages. Is there a tool for source packages? | 04:37 |
| wgrant | There are no fundamental differences between the two. | 04:37 |
| dupingping | So is there a tool to do it? | 04:39 |
| wgrant | It depends on exactly what you're going to do, but regardless it's not within Launchpad's remit. | 04:41 |
| dupingping | wgrant: yes, i see. | 04:45 |
| cjwatson | wgrant: Could you glance over my post-review changes to https://code.launchpad.net/~cjwatson/launchpad/limit-debdiff/+merge/278187 ? | 10:59 |
| wgrant | cjwatson: I assume debdiff doesn't do anything silly like uncompressing the tarball onto disk before extracting it? | 11:05 |
| wgrant | >1GiB single files are unlikely, but uncompressed tarballs are plausible. | 11:05 |
| cjwatson | wgrant: It may call dpkg-source, which I don't *think* does that, but you never know. Maybe I should bump that to 10GiB; the main purpose is just to defend against running haetae out of disk. | 11:22 |
| cjwatson | wgrant: There were 22 diffs in dogfood's DB over 1GiB. They must all have taken quite some time to generate (I didn't check). | 11:22 |
| * cjwatson bumps that | 11:27 | |
| === jelmer_ is now known as jelmer | ||
| === jelmer is now known as Guest88376 | ||
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!