[00:10] tkamppeter: I at least used to be an HTTP expert, although I'm pretty rusty these days. I've posted an analysis to the bug with reference to the governing RFC. [00:17] dinexi: I could be wrong but I think the openssl mod had a license issue. [00:19] Ampelbein: Hm... that's bad. Do you know if it is included in the source package? [00:20] Ampelbein: Silly me. Nope, it shouldn't be there. So what to do? Build this thing myself? [00:22] dinexi: I don't know, maybe ask a question on https://answers.launchpad.net/ecryptfs/+addquestion? [00:23] Ampelbein: did it already. But transformed it to bug because there is a bug in the manpages then. :( But it is the worst news for today. [00:24] dinexi: kirkland is one of the authors of the software [00:24] using debian preseed, im trying to enable all repos in sources.list by adding this multiselect: [00:25] d-i mirror/udeb/components multiselect main, restricted, universe, multiverse [00:25] (maverick) [00:25] but its not working [00:25] * kirkland waves [00:25] only main and restricted show up === chuck_ is now known as zul [00:26] mainly for this project -> http://linuxcoe.sourceforge.net/ [00:26] kirkland: dinexi had a question about the openssl mod in ecryptfs-utils and if it got removed. [00:26] Ampelbein: dinexi: right, Ubuntu and Debian's policies prevent us from linking gpl code against the openssl libraries [00:26] which is to say our policy of respecting the license we're given? :) [00:27] Ampelbein: dinexi: so, yes, you would need to build it yourself, until such time as we rewrite the code to use a different library that is GPL-compatible [00:27] are preseeding server installs supported on ubuntu? [00:27] kirkland: ok, thanks for the explanation. [00:28] jcole: certainly, but this is not a support channel and the people who are most intimately familiar with the installer are not around, it being past their bedtime; you might try #ubuntu [00:28] slangasek: it's a tough situation to explain to someone who cares not about internal license politics :-) -- but yes, of course, you are correct [00:29] Ampelbein: dinexi: http://www.openssl.org/support/faq.html#LEGAL2 and http://people.gnome.org/~markmc/openssl-and-the-gpl.html [00:29] kirkland: thanks! but I have two questions. 1) it is very easy to change the manpage, why it can't be done? 2) can I build the package from the source from the ubuntu repos? [00:29] kirkland: thanks a lot! [00:29] slangasek: can you give me an irc filter for all the "smart" people in #ubuntu so i dont see all 1500 users [00:30] dinexi: yes, i think you can; i have not done it in a very, very long time, but I think you merely need the openssl-dev packages installed on your system when you build/install ecryptfs-utils [00:30] dinexi: i *think* that the ./configure auto detects the presence of openssl and links it in [00:30] dinexi: like i said, been a long time since i did that [00:30] jcole: afraid I don't know such a filter :) [00:31] slangasek: *sigh* ok here goes... [00:31] jcole: #ubuntu-installer [00:31] (I will help you there) [00:32] cjwatson: thanks! [00:37] kirkland: sorry for the newbie question. I am in /var/cache/apt-build/build/ecryptfs-utils-83, made the change in the debian/rules file. What should I do now to build the package? [00:39] [00:46] dinexi: #ubuntu-motu is usually the best place to ask package building questions, but I'll give you a couple of hints here ... [00:47] dinexi: mkdir foo; cd foo; apt-get source ecryptfs-utils; sudo apt-get build-dep ecryptfs-utils; # make your changes here; dch -i ; debuild [00:49] kirkland: Thank you very much. debuild was a blocker. [00:49] dinexi: no problem; good luck === dendrobates is now known as dendro-afk [00:55] kirkland: didn't that change quite a while ago? [00:55] Chipzz: huh? [00:55] at least that's what I was told the last time I redirected someone to #ubuntu-motu regarding packaging questions [00:57] kirkland: #ubuntu-motu being the place to redirect ppl to if they have packaging questions; they're not "OT" here anymore [00:57] Chipzz: oh, really? i guess i missed that policy change then [00:59] kirkland: maybe I misunderstood (but don't think I did); but that change is several months old already (at least 3 or 4 months I think) [01:01] kees: ping [01:07] Hi there, I have a weird (packaging?) issue with munin-node on 10.04 [01:07] when installing the package the file /etc/munin/munin-node.conf is missing [01:08] even though dpkg think the file is there [01:08] I have tried purging and reinstalling without success [01:08] dsalvetti: file is in the package [01:09] any suggestion on what I could try next to find out where the issue is? [01:10] micahg: yes I've confirmed that with dpkg -c /var/cache/apt/... [01:11] dpkg --status also report the config file being present [01:11] but it's not there and because of that munin-node fails to start properly [01:17] dsalvetti: maybe try #ubuntu-server, I don't see any bugs or questions filed on launchpad for it [01:19] dsalvetti: oh, you could try #ubuntu-cloud [01:21] micahg: thank you, I'll try [01:32] hallyn, hey... I'm here on irc if you want to chat a bit about those bugs btw === rickspencer3 is now known as greatcthulu === greatcthulu is now known as greatcthulhu === greatcthulhu is now known as rickspencer3 [02:46] slangasek: I tried a test rebuild of ia32-libs last night...and nothing seemed to break?! [04:38] YokoZar: er, define "break"? [04:39] YokoZar: is everything from /usr/lib/i386-linux-gnu getting copied into /usr/lib32? [05:04] slangasek: so, the -dev packages will ship .a files in /usr/lib/$triplet/libFOO.a but not be Multi-Arch? [05:12] kees: yes, because they're not reliably co-installable; that's something we need to go back and visit in round 2 [05:12] some headers, for instance, contain arch-specific info, and we'll need to pick those apart [05:14] okay, cool. but they will still move to the triplet because they're built from the same --libdir target, etc. [05:16] yep [05:21] slangasek: uhm... does -dbg packages need the Pre-Depends? [05:21] no, because they don't need to be found by ld.so [05:23] (it doesn't hurt to have it added, I think, because the substitution will just be empty... but I haven't been bothering) [05:26] okay, that's what I suspected. [05:26] multiarch tiff passes the security team's regression test suite. ;) [05:27] I should hope so :) [05:28] * kees suddenly realizes he has to teach his system about i386 tuples to test coinstallability [05:29] hmm, I don't have that part written up yet, do I [05:29] 'APT::Architectures { "amd64"; "i386"; };' in apt.conf, and 'foreign-architecture i386' in dpkg.cfg === dendro-afk is now known as dendrobates [05:30] slangasek: do I need a i686-linux-gnu.conf in /etc/ld.so.conf.d too? [05:30] no, libc6:i386 adds that [05:30] ah-ha, righto [05:32] is something like /etc/apt/apt.conf.d/60multiarch and /etc/dpkg/dpkg.cfg.d/60multiarch sane? [05:34] sure [05:36] oh whoops, didn't actually add Multi-arch: same. har har [05:36] :-) [05:37] slangasek: btw, I added this section quickly: http://wiki.debian.org/Multiarch/Implementation#Usingmultiarch [05:37] ok [05:38] heh, vim syntax needs updating! :) [05:38] eventually I think that should be its own page, but that's great for now [05:38] oh? updating for what? [05:38] syntax hilighting "Multi-Arch:" correctly :) [05:38] ah :) [06:00] slangasek: okay... what am I doing wrong? The "Multi-Arch: same" field doesn't seem to be making it's way into the binary package. *scratch head* [06:00] kees: pastebin? [06:01] kees: or control.in? :) [06:02] wait, no, I know what stupid thing I did. disregard. :) [06:03] slangasek: What changes will be needed from the LP/buildd end, and when? [06:04] I guess we'll need a new sbuild resolver. [06:04] wgrant: nothing at all this cycle [06:04] wgrant: s/ resolver// [06:04] "this cycle" being natty? [06:04] yeah [06:04] But that's over in a month :) [06:04] yeah ;) [06:04] IE, please file bugs now so LP has time? :-) [06:05] wgrant: we'll need to sit down at UDS and start figuring out what a sensible policy should even be for permitting cross-build-deps [06:05] slangasek: Yeah. === _LibertyZero is now known as LibertyZero [06:07] slangasek: I mean fetch and build completed and the package built, although it probably is missing some things now [06:07] Stupid question: why is it "from debian_bundle import deb822" in lucid, when in wheezy it's "from debian import deb822"? [06:08] YokoZar: yes, I expect a lot of libs are either just plain missing, or installed to the wrong path [06:09] twb: someone changed their mind about the name? [06:10] I just ran into it because