[08:23] <dholbach> good morning
[08:34] <Laney> hiya
[08:37] <nigelb> Morning!
[12:07] <Greenberet> hello, i want to package some custom scripts into an *.deb. I have already the directory structure with ./debian/control ./debian/compat and so on. But where do I have to put my scripts so that "debuild -us -uc -b -ai386" will import them?
[12:11] <akheron> Greenberet: in your own directory, debian/scripts/ for example, and then make dh_install install them to /usr/bin/ or wherever
[12:12] <Greenberet> thx i will try
[12:42] <Greenberet> it works =) thx for your help akheron
[15:24] <l3on> Hi all... someone of you knows some reason why I souldn't merge binutils-z80 ?
[15:24] <l3on> I'm doing it..
[15:27] <lgp171188> Hi, I am getting started on Debian/Ubuntu packaging. And one of the things that I thought I could package was 'pony-mode', an emacs mode for Django, that is not yet in Debian repositories, but I love using it. Though the packaging guide tells a lot about packaging process, I couldn't understand/find out where to start with this. The source code for this software is hosted on Github. I am not sure if it should be packaged for Debian or
[15:27] <lgp171188> directly for Ubuntu. Should I create a source package or a binary package or both. Would love some help/guidance on this.
[15:28] <lgp171188> And I hope I am asking in the correct channel :-)
[15:31] <geser> lgp171188: I don't time right now to answer all your questions but you need to build a source package (both Debian and Ubuntu build the binary packages from the source package) and it sounds like the package would be also useful for Debian too (so both Debian and Ubuntu (and other Debian-based distributions) can profit from your packaging)
[15:31] <l3on> Sorry I meant "resolvconf"
[15:34] <tumbleweed> lgp171188: it doesn't make much difference whether you are packaging for debian or ubuntu
[15:34] <tumbleweed> lgp171188: but yes, getting it into Ubuntu via debian is the ideal solution
[15:35] <tumbleweed> l3on: I know there are other things that need to happen on resolvconf too (someone had an upstratification patch that should probably be looked at)
[15:36] <l3on> I made the package... we could try it and the repackage again when a new version will come.. or not?
[15:36] <lgp171188> tumbleweed: Hmmm, makes sense. But I am still kind of confused about whether source and/or binary package should be built since the code for the module is hosted on Github.
[15:38] <tumbleweed> l3on: no, I mean there are things that need to happen to it in Ubuntu (besides merging)
[15:39] <tumbleweed> lgp171188: right, it doesn't look like the developer has made any releases yet (this is becoming rather common :/ the ruby mentality... )
[15:39] <l3on> tumbleweed, ah ok... :)
[15:40] <tumbleweed> lgp171188: I'd just start by grabbing a tarball of the current master tip
[15:41] <l3on> tumbleweed, I can use this log as comment in bug report?
[15:41] <l3on> bug 894417
[15:41] <tumbleweed> lgp171188: name it something like pony-mode_0+git20111124.orig.tar.gz (I'm using 0+git20111124-1 as the debian version)
[15:42] <tumbleweed> lgp171188: later, we can add a script to automatically build a .orig.tar.gz from the git branch, but for now, just get a working package going
[15:42] <tumbleweed> l3on: sorry, I don't understand that question
[15:42]  * tumbleweed has to go out now
[15:42] <l3on> ok, forget :)
[15:42] <Laney> speak to the last merger
[15:44] <lgp171188> tumbleweed: ok, let me try that and get back :-)
[15:48] <l3on> Laney, in m.u.com was written: "feel free to take"
[15:48] <Laney> ok
[16:06] <lgp171188> tumbleweed: What do you mean by saying "it doesn't look like the developer has made any releases yet". Isn't the source code available? I can't understand.
[16:14] <lgp171188> tumbleweed: And the author has marked the existing code as 0.3, so shouldn't we be naming the tarball as pony-mode0.3-0ubuntu1.orig.tar.gz instead of +git<today's date> ?
[17:09] <g0twig> hey
[17:09] <g0twig> is here the team that makes the 12.04 iso´s ?
[17:11] <cjwatson> g0twig: probably easier to just ask your question directly, as there's a lot of stuff in the images and it's dealt with by lots of different people
[17:12] <g0twig> I want to build my own image based on ubuntu with seed´s
[17:13] <g0twig> like the ubuntu builds are made
[17:13] <cjwatson> shnatsel was working on some third-party documentation for that recently; our own documentation for that unfortunately kind of sucks
[17:13] <cjwatson> for third-party builds it's probably simplest to use live-build
[17:14] <g0twig> cjwatson: jeah I know that from shnatsel. But I heard that it doesnt realy works for him.
[17:14] <cjwatson> I left feedback on his google doc
[17:14] <g0twig> cjwatson: why do the people that are doing the builds not help him
[17:14] <g0twig> cjwatson: gottag link for me?
[17:14] <g0twig> "gotta"
[17:14] <cjwatson> I did that by leaving feedback on his google doc!
[17:15] <cjwatson> sorry, not easily, ask him?
[17:15] <g0twig> cjwatson: he sent me a link already, but I forgot it.
[17:15] <g0twig> cjwatson: or I lost it, what ever :/ so you, too?
[17:15] <cjwatson> TBH I'm not keen on inflicting the build system we use on others; live-build is much better at being customisable easily by third parties
[17:16] <cjwatson> ours is optimised for dealing with lots of flavours on lots of architectures at scale with low maintenance
[17:16] <cjwatson> which is not what most people need
[17:16] <cjwatson> the code's in lp:ubuntu-cdimage and the livecd-rootfs package, but deploying it is fairly complex
[17:18] <g0twig> cjwatson: I noted that
[17:18] <g0twig> cjwatson: :/
[17:18] <g0twig> I would like to help the elementary OS team with it
[17:19] <g0twig> to build their iso´s. I already helped them with Jupiter, what was made with live-build, so trough chroot (?), but it was not a good way.
[17:19] <cjwatson> I don't see what's wrong with them using live-build
[17:19] <g0twig> maybe I should ask the people from debian?
[17:19] <cjwatson> or maybe livecd-rootfs
[17:19] <cjwatson> which is built on top of Debian's tools
[17:19] <g0twig> cjwatson: does "live-cd" use chroot?
[17:19] <cjwatson> yes
[17:20] <cjwatson> there's no sensible way to build a live filesystem without chrooting at some point; I don't understand how else you think it should be done?
[17:20] <g0twig> cjwatson: but the ubuntu build system does also use chroot, right :P?
[17:20] <g0twig> cjwatson: yes
[17:20] <cjwatson> chroot is hardly a major design feature, it's just one tool ...
[17:21] <g0twig> cjwatson: elementary wants an arm build..
[17:21] <cjwatson> so they'll need an arm builder to build it on
[17:21] <g0twig> cjwatson: do you know how mint does their iso´s? it can´t be live-cd :/?
[17:21] <cjwatson> I neither know nor care, they impose a burden on Ubuntu
[17:22] <cjwatson> (e.g. they don't take care to redirect their bugs away from us)
[17:22] <cjwatson> the Ubuntu builds work by building the live filesystem on machines of the appropriate architecture, and then assembling those filesystems on a central system
[17:22] <cjwatson> so livecd-rootfs (which uses live-build) is used on ARM just as it is on any other architecture
[17:22] <g0twig> cjwatson: elementary also discussed to become a spin of ubuntu..
[17:24] <cjwatson> of course if you're building for multiple architectures you can't *just* build everything in a chroot (well, you could with user-mode emulation, but it would be very slow); but chroots are certainly involved, just on the other end of ssh to a machine of the appropriate architecture
[17:26] <cjwatson> https://wiki.ubuntu.com/RecognizedDerivatives has the criteria for becoming a flavour that we build
[17:27] <g0twig> cjwatson: thanks for your support
[18:01] <timonia> hello ubuntu community. Can anyone help me find and fix my first bug :). I don't have any prior experience and lot of theoretical knowledge :( . By fixing bugs I wish to learn the practical aspects of programming :)
[18:06] <timonia> anyone?
[18:06] <EvilResistance> timonia, if i may ask, what's your background?  because theoretical knowledge without prior experience in specific coding languages might make some things difficult...
[18:07] <EvilResistance> as well, you sometimes run into conflicting coding styles
[18:07] <EvilResistance> but that's less likely ;P
[18:09] <timonia> EvilResistance, i have experience but not on a large codebase. btw I know C/C++ have a good command over algorithms and I can read and understand code. But never contributed to any open source project before
[18:10] <timonia> So i wish to start from Ubuntu which I guess I love the most amongst all the FOSS I use
[18:11] <timonia> EvilResistance, and best of all if that I am motivated and willing to learn things :0
[18:11] <EvilResistance> :P
[18:11] <timonia> :)
[18:12] <timonia> so any suggestions?
[18:12] <EvilResistance> then you've got most of the coding background needed for most of the things i've seen.  although... i'm not an MOTU, nor do i have the ability right now to troll through the bugs (stuck on IRSSI on a CLI only machine)
[18:12] <EvilResistance> if i had any suggestions i'd throw them your way
[18:13] <micahg> timonia: http://developer.ubuntu.com/packaging/html/fixing-a-bug.html, you might also want to look for the bitesize tag on harvest (mentioned at the beginning of the link), thanks for your interest!
[18:15] <timonia> micahg, thankyou
[18:16] <micahg> timonia: if you run into any issues, feel free to ask here
[18:16] <timonia> I will :)
[18:22] <chrisccoulson> is anyone finnish in here?
[18:24] <nigelb> chrisccoulson: You probably want jussi. He's australian, but shown know something finnish :)
[18:25] <chrisccoulson> nigelb, ah, thanks
[18:25] <chrisccoulson> i was just wondering why finnish people install the mozvoikko extension in firefox :)
[18:25] <nigelb> chrisccoulson: :)
[18:25] <nigelb> Ugh, also s/shown/should/g
[18:26] <EvilResistance> nigelb, whats the g at the end there?
[18:26] <EvilResistance> denotes something about case or whatnot?
[18:26] <nigelb> g I think means all instances.
[18:26] <micahg> "globally"
[18:26] <nigelb> Aha!
[18:27] <nigelb> Thanks micahg :)
[18:27] <ajmitch> launchpad bug listing is looking a bit different today
[18:27] <nigelb> custom bug listing landed?
[18:28] <ajmitch> at least in beta, so maybe it's only on for some teams
[18:28] <nigelb> yeah, its probably open to beta testers now
[18:28] <nigelb> Its an amazing feature :)
[18:29] <ajmitch> though the cog to change columns isn't the most visible when I've just woken up :)
[18:30] <nigelb> File a bug!
[18:30] <nigelb> :)
[18:30] <ajmitch> I'll have to, I can't sort by the columns that I added!
[20:02] <sladen> chrisccoulson: lots of FI people: mika, antti, jussi, vesar, tjaalton, amitk, …