[02:52] <infinity> @pilot out
[04:45] <lifeless> bryce: oh, and freedesktop.org watches are borked too ><
[04:51] <Sarvatt> lifeless: fdo bugzilla has been up and down all night if its recent, they're moving servers
[04:51] <lifeless> Sarvatt: not recent
[04:51] <lifeless> Sarvatt: another gem hidden in the lp bugtracker
[07:04] <raju> hello i have a samsung mobile , am i able to install Ubuntu in that ?
[13:42] <stgraber> pitti: just saw you uploaded a new calibre, cool! Now with the new wxwidgets2.8 I just uploaded, I should be able to install calibre and still be pycentral free ;)
[13:44] <ogra_> isnt calibre a Qt app ?
[13:44] <ogra_> at least it used to be
[13:46] <stgraber> ogra_: oh, indeed, so that was another Edubuntu package that was depending on wxwidgets2.8. Calibre was bringing pysupport or pycentral in Edubuntu because of python-cherrypy3 which I converted a few days ago
[13:46] <ogra_> ah
[15:12] <Eren> debian maintainer's guide states that the package is installed temporarily under "debian/package" directory
[15:12] <Eren> is it different in ubuntu?
[15:13] <Eren> I've looked at the source of gtk+ package, and accordingly to *.install files, it's stated as "debian/install/shared/usr/share/... usr/share"
[15:14] <tumbleweed> Eren: not different on ubuntu
[15:15] <Eren> tumbleweed: is it specific to gtk+ then?
[15:17] <tumbleweed> Eren: I don't know the gtk+ package, but I'm assuming it's using debian/install as a staging area, where most packages use debian/tmp as the staging area
[15:17] <tumbleweed> when you build multiple binaries from one source package, you usually build into debian/tmp, and then use dh_install to move them into the binary package directories
[15:20] <Eren> tumbleweed: thanks. When building packages, how is ubuntu different than ubuntu? I'm currently learning how to package *.deb and I would like to know how ubuntu is differentiated from debian in terms of package management
[15:21] <Eren> ops, how is debian different than ubuntu* :)
[15:24] <tumbleweed> Eren: there aren't any differences you need to worry about, yet
[15:25] <Eren> tumbleweed: when should I worry?
[15:26] <tumbleweed> when you run into them. But you almost certainly won't
[15:28] <Eren> okie, thanks. I'll keeping debian maintainer's guide, and debian policy as main documents then
[15:29] <tumbleweed> the biggest difference you are likely to run into is that ubuntu won't include the upstream changelog in the deb
[15:29] <tumbleweed> (and only part of the debian/ubuntu changelog)
[15:31] <Eren> tumbleweed: so, debian includes upstream chanlog in /usr/share/doc/<package>
[15:31] <tumbleweed> yes
[15:32] <jtaylor> doko: something is weird with python2.7
[15:33] <jtaylor> python2.7-dev is now 10 times larger than before
[15:36] <tumbleweed> looks like the 3 static libraries balooned
[15:36] <jtaylor> can't tell I'm still downloading ._.
[15:37]  * tumbleweed was just looking at the build log
[15:38] <jtaylor> a forgot debc output is in there
[15:41] <doko> that's the lto sections
[15:43] <jtaylor> so its going to stay like this?
[19:17] <jtaylor> omg python3 is now 18.7mb
[19:22] <jtaylor> doko: is that static library /usr/lib/libpython3.2mu.a intentionally in python3 and not python3-dev?
[19:22] <jtaylor> 3.2
[19:25] <doko> jtaylor, no, will fix
[19:25] <jtaylor> thx, my poor internet connection thanks you :)
[19:49] <trism> Is it intentional that the debug version of dbus-daemon is being installed instead of the production version in both the dbus packages in oneiric and precise? (you can see the binary be installed once from build/bus then overwritten by build-debug/bus in the logs).
[19:58] <trism> Moving --exec-prefix=/ from the common_configure_flags to the non-debug build flags in override_dh_auto_configure in debian/rules seems to fix it if it is a bug. Only noticed it because it was causing weird aborts in make check for the dbus-python code. (at a part that shouldn't be enabled in the production build)
[21:38] <wyuka_> hi
[21:38] <wyuka_> is there a page explaining how live installation actually works?
[21:39] <wyuka_> in detail?
[21:41] <infinity> wyuka_: What level of detail are you looking for?
[21:42] <infinity> wyuka_: "Copy the read-only FS from the livecd to the target filesystem; run d-i components in target to configure it" is the short answer.
[21:42] <infinity> wyuka_: Significantly more detail than that means documenting everything each d-i component can/does do, which I'm not sure is worth the effort.
[21:43] <infinity> wyuka_: There's also the "remove some packages we don't want" phase, and optionally "install more packages than the livecd had installed".